Project

General

Profile

Actions

Bug #30624

closed

Connection Problem

Added by Thoren Wiemann over 12 years ago. Updated over 11 years ago.

Status:
Closed
Priority:
Could have
Assignee:
-
Category:
Database API (Doctrine DBAL)
Target version:
-
Start date:
2011-10-07
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
4.5
PHP Version:
5.2
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

After the upgrade from Version 4.4.X to 4.5.6 there are several problems with the connection to the database, see attached screenshots.

First Error Text:

Oops, an error occured!

Datebae Error: The current username, passwort or host was not accepted when the connection to the database was attempted to be >established!

Second Error Text:

Connection Problem

Sorry, but an error occurred while connecting to the server. Please check your network connection.

After the above error message appears, changes will not be stored.


Files

typo_2011-10-07_140553.png (2.43 KB) typo_2011-10-07_140553.png Thoren Wiemann, 2011-10-07 14:32
typo_2011-10-07_140535.png (28.7 KB) typo_2011-10-07_140535.png Thoren Wiemann, 2011-10-07 14:32
typodbinstall2011-10-07_152239.png (9.16 KB) typodbinstall2011-10-07_152239.png Thoren Wiemann, 2011-10-07 15:41
Actions #1

Updated by Chris topher over 12 years ago

  • Status changed from New to Needs Feedback
  • Target version deleted (4.5.7)

I am rather sure this is no bug, but a configuration issue.

This problem can be caused by a wrong value for mysql_pconnect.
Search in the Install Tool and make sure you have set the right value for the settings, which you have on your server.

Actions #2

Updated by Thoren Wiemann over 12 years ago

Thanks for the fast response!

I've just check the install tool and there is no problem with the database connection (see attached screenshot).
It`s an intermittent failure, not constant.

Thank you very much in advance!

Actions #3

Updated by Steffen Gebert over 12 years ago

  • Category changed from Backend User Interface to Database API (Doctrine DBAL)
  • Priority changed from Must have to Could have

Nevertheless, this looks like your MySQL is not reliable (or the connection to it). Is it a new server and do other sites work?

Actions #4

Updated by Christian Kuhn over 12 years ago

  • Status changed from Needs Feedback to Closed

Closed.

This is no core problem: The database connection works. Please check your system setup, maybe number of maximum connections in mysql is not high enough or something like that.

Actions #5

Updated by Vincent Mans over 12 years ago

This problem still occurs in 4.6.0 and 4.6.1, when trying to update translations in EM. no_pconnect TRUE or FALSE makes no difference. I have plenty DB connections. Tried several BE admin users accounts and browsers FF & Chrome. It happens 100% of the attempts.

Never experienced this issue before, it's new for me since 4.6.x.

Message, as known:
"Connection Problem
Sorry, but an error occurred while connecting to the server. Please check your network connection."

This config setting doesn't help anymore:
$GLOBALS['TYPO3_CONF_VARS']['EXT']['showOldModules'] = TRUE;

So I guess, many people are left with essential functions not working and not able to bypass it... do you like the Drupal approach that much? ;-) You can't close this issue with "it's not a core problem" because it's the em code that invokes the problem, the solution should be different.

Actions #6

Updated by Vincent Mans over 12 years ago

Additionally: using PHP 5.3.5

Actions #7

Updated by Vincent Mans over 12 years ago

In the meantime tried it on a completely different server (the other one was Gentoo, this is Ubuntu) with hardly active connections so plenty of space. The same problem occurs. PHP5.3.2.

So, is it a bug or not? I do think so.

Actions #8

Updated by Vincent Mans over 12 years ago

Found some descriptions with Firebug:

e._flyweights is undefined
[Afbreken op deze fout] (function(){var h=Ext.util,j=Ext.each,...lclick",this.onNodeDblClick,this)}});

Ext.EventManager is undefined
[Afbreken op deze fout] window.undefined=window.undefined;Ext=...window.attachEvent("onunload",a)}})();

Actions #9

Updated by Björn Biege over 11 years ago

Why this ticket is closed?
Same Problem in 2 systems after update from 4.6 to 4.7 on different Servers.

Actions #10

Updated by Thorsten Kahler over 11 years ago

There was no hint that the problems described here were caused by TYPO3.

If you have any information which points to TYPO3 we would be happy, because it could help solve a yet unknown issue. If the problem only occurs during EM updates, please try to increase the MySQL setting wait_timeout: fetching the extension list might take some time.

Actions

Also available in: Atom PDF