Network Solutions problems: Difference between revisions

From ShawnReevesWiki
Jump to navigationJump to search
Xeentav (talk | contribs)
Created page with '==2010-07-27:MySQL== One NetSol mysql server (the commonly problematic "mysqlv1") is dropping connection or not connecting. Here is the error as reported by PHP: :Warning: mysql_…'
 
No edit summary
Line 3: Line 3:
:Warning: mysql_pconnect() [function.mysql-pconnect]: Lost connection to MySQL server at 'reading initial communication packet', system error: 104 in /data/2/0/137/91/137091/user/138855/htdocs/Connections/ETONewsConnect.php on line 9
:Warning: mysql_pconnect() [function.mysql-pconnect]: Lost connection to MySQL server at 'reading initial communication packet', system error: 104 in /data/2/0/137/91/137091/user/138855/htdocs/Connections/ETONewsConnect.php on line 9
:Fatal error: Lost connection to MySQL server at 'reading initial communication packet', system error: 104 in /data/2/0/137/91/137091/user/138855/htdocs/Connections/ETONewsConnect.php on line 9
:Fatal error: Lost connection to MySQL server at 'reading initial communication packet', system error: 104 in /data/2/0/137/91/137091/user/138855/htdocs/Connections/ETONewsConnect.php on line 9
;update, 7-28: NetSol sent an e-mail that the problem is now 'resolved.' I checked the site, and sometimes the database server takes over 30 seconds to respond.

Revision as of 19:27, 28 July 2010

2010-07-27:MySQL

One NetSol mysql server (the commonly problematic "mysqlv1") is dropping connection or not connecting. Here is the error as reported by PHP:

Warning: mysql_pconnect() [function.mysql-pconnect]: Lost connection to MySQL server at 'reading initial communication packet', system error: 104 in /data/2/0/137/91/137091/user/138855/htdocs/Connections/ETONewsConnect.php on line 9
Fatal error: Lost connection to MySQL server at 'reading initial communication packet', system error: 104 in /data/2/0/137/91/137091/user/138855/htdocs/Connections/ETONewsConnect.php on line 9
update, 7-28
NetSol sent an e-mail that the problem is now 'resolved.' I checked the site, and sometimes the database server takes over 30 seconds to respond.