Forum Buglets

[DiverCTHunter]

The SQL-Beastie reappears:

I got these when trying to view posts that had a : (colon) character in the topic.

viewtopic/t81180/Suddenly-Aerophagia.html
[phpBB Debug] PHP Notice: in file /viewtopic.php on line 30: include_once(/var/www/vhosts/cpaptalk3/global/classes/api/class.CpapAPIPart.php): failed to open stream: No such file or directory
[phpBB Debug] PHP Notice: in file /viewtopic.php on line 30: include_once(): Failed opening '/var/www/vhosts/cpaptalk3/global/classes/api/class.CpapAPIPart.php' for inclusion (include_path='.:/usr/share/pear:/usr/share/php')
Fatal error: Class 'CpapAPIPart' not found in /var/www/vhosts/cpaptalk3/httpdocs/viewtopic.php on line 31


viewtopic.php?f=1&t=80813&p=738339&hili ... ts#p738339
[phpBB Debug] PHP Notice: in file /viewtopic.php on line 30: include_once(/var/www/vhosts/cpaptalk3/global/classes/api/class.CpapAPIPart.php): failed to open stream: No such file or directory
[phpBB Debug] PHP Notice: in file /viewtopic.php on line 30: include_once(): Failed opening '/var/www/vhosts/cpaptalk3/global/classes/api/class.CpapAPIPart.php' for inclusion (include_path='.:/usr/share/pear:/usr/share/php')
Fatal error: Class 'CpapAPIPart' not found in /var/www/vhosts/cpaptalk3/httpdocs/viewtopic.php on line 31

and this, when I tried to post the errors
posting.php?mode=post&f=1&sid=23ee7d64b ... 560c33f00a
Warning: mysql_connect(): Lost connection to MySQL server at 'reading initial communication packet', system error: 110 in /var/www/vhosts/cpaptalk3/global/classes/class.database.php on line 104 [2012-08-21 16:44:11] <0d7086e> Could not connect to MySQL server (db1.usx.core):

[johnnygoodman]

Thanks for the report. Ticket number is 13440. If you don't hear back in 2 days, please bump this thread.

Johnny

[sam_cpap]

Hi guys,

This was related to an update that I was rolling out to (hopefully) fix the other mysql errors you were having. The errors you reported then shouldn't rear their heads again now.

Thanks, for the report, and let us know if you guys have any other issues.

Sam.

[johnnygoodman]

Pasting in the discussion on this ticket...

Sam says:

The first two were related to svn not updating cleanly (it had to switch to the new redmine server, and didn't update properly, then got out of sync).

Those warnings were because the code in one place had checked out, but not in other places.

This has been resolved now, and future SVN updates will be clean.

The SQL error, I'm not certain about - it looks like the same thing that we released this code to avoid (i.e. it was trying to hit db1, and the connection timed out).

Robert replies:

agreed, number 3 is a dupe of the existing db connection issues. closing ticket

Ticket closes.

We continue to work the SQL errors but the first two errors, relating to svn pushes, are resolved.

Johnny