'Could not connect to database'

[#1]

I'm still getting the problem using phpBB on Rumpus.

[#2]

Had it once today again, though on humbug.
Needed to load the page once.
This is better to previous, where it needed to be re-loaded several times.

[#3]

I raised a ticket and the reply was...
'We are currently investigating an intermittent problem with the SQL servers as part of an internal Problem (ID 46165) and hope to have this matter resolved shortly.'
Watch this space

[#4]

Have been getting the following intermittent error for the past week or so when trying to connect to CGI
Connect DB Error: Can't connect to MySQL server on 'rumpus' (4) Cause #2
Why do I get the feeling that Plus net is run by a couple of geeks from a shed at the bottom of the garden
Cheers
Alistair

[#5]

Same feeling coming up, though I know it is a highly specialised work:

Database Error
The current username, password or host was not accepted when the connection to the database was attempted to be established!

Again.
Re-loading had no effect so far (5 times re-loaded page!!!).
This concerns the cms with a high number of database-requests per page.
The second cms I use works, though it has only a couple of pages so far.
This problem was never there before until ca. 10 to 14 days ago. So somebody at PlusNet has fiddled around on the MySQL-server(s), and then all the problems appeared......

[#6]

The connection error message saga to humbug continues:
The current username, password or host was not accepted when the connection to the database was attempted to be established!
Database Error

Any timescale until when this will be repaired?

[#7]

Quote from: ffupi

Anyone else having this problem, or is it only us few?

Yes it's happening on my CMS site running Joomla1.0.12 occasionally.
Getting timeouts after Joomla tries to access database info, also javascript editor times out too.

[#8]

Quote from: flabbio

I raised a ticket and the reply was... 'We are currently investigating an intermittent problem with the SQL servers as part of an internal Problem (ID 46165) and hope to have this matter resolved shortly.' Watch this space

Quite handy that response, isn't it!  At least they're consistent with their responses 
Should we open tickets again or sit tight?  It is intermittent but it is very annoying - especially if you create a post and then click save only to find out that there's been a database error!

[#9]

Can we view the status of Internal Problem (ID 46165)
anywhere on the PN portal? 

[#10]

Nope.

[#11]

Just got this message

Quote

Unable to establish connection to MySQL 2002 : Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)

Getting timed out a lot - time for some high tech WD40 to be injected into the system.
On rumpus

[#12]

I'm still having this problem. Error message from php is:
Warning: mysql_connect(): Can't connect to MySQL server on 'rumpus.force9.net' (4)
The error is preceded by a long pause, so it seems like something is timing out somewhere. Usually pressing Refresh clears it.

[#13]

I've been having this problem for some time too. PlusNet aren't particularly bothered about fixing it at the moment (annoyingly), however on Monday a member of staff set up a script to try and connect to each MySQL server once a minute; he showed me the results yesterday and at times the failure rates have been as high as 20%, so I believe he's going to try and use his statistics to push the priority of this problem up for us. So hopefully it won't be too long now before it's fixed.

[#14]

Sounds good.  We could help if everyone that read this thread raised a ticket. 

[#15]

This problem was raised in the PUGIT database on 10th Sept as issue 365
Current status is:
1) It remains unacknowledged by PlusNet.
2) No votes so far to help raise it's priority.
Voting in PUGIT does help raise the problem profile within PlusNet.
Get on over there and make your vote count?
MauriceC