So here are the basics of the entire situation, I do have a new ticket in with Centova - but maybe one of you guys will see something:
I had been running my Centova on a Kimsufi/OVH server. The server itself never actually went down in the entire time that I have had it in my possession and been monitoring it. However, every 80 to 120 hours the web service for Centova went down, and in order to bring it back up, I was forced to reboot the server. This solved the problem for another 80 to 120 hours or so.
Centova support escalated the issue to a dev.
He was kind enough to look at my logs, and found all sorts of Kernel errors, which he diagnosed as a serious hardware issue with the server. The listing of the errors is in the above response.
I contacted my DC, and they said there were no hardware issues with the server. We also upgraded the Kernels to the current stable version 3.12.9 (according to Kernel.org - rebooted the server - and the webservice crashed some 88 hours later. We then rolled back the Kernels to 2.6.34 - rebooted - and again the webservice crashed near the 100 hour mark.
As this point, I decided to chalk it up to being a bad server - contrary to what the DC was telling me
On Wed, 1/22, I contracted Centova to migrate over from my OVH/Kimsufi Server to my Online.Net server. This job was completed approx 10pm EST on 1/22.
Everything appeared to be running great for a few days.
But today, 1/26, at 12:58 EST, the Webservice monitor reported that it was down. I checked Streams.CentralSocial3d.com:2199 and received:
502 Bad Gateway
cc-web/1.2.9
However, the monitor on just the server IP address showed the server was up and running running fine.. I was able to ping the server, but unable to reach the Centova Panel. The problem again appears to be the web service only.
Ironically, this down time occurred 84 hours and 55 minutes from the migration to the new server. Which happens to be in the same window of time that the other servers web service would go down on a consistent basis.
I was forced to reboot several times to get the web service to come back up. On the 3rd reboot it did. And it is now running flawlessly again. However, judging by what I saw today, I would fully expect the web service to crash again between Wednesday night and Friday night.
I desperately need to fine a solution to this problem
Here are all the logs. (They are based on Paris time - so the time that the server went down would be between 18:53 and 18:58. I cannot get a specific minute because my monitor checks the web service and the server once every 5 minutes.
CC-AppServer Logs:
http://brooketv.net/cc-appserver.loghttp://brooketv.net/cc-appserver.log.1.loghttp://brooketv.net/cc-appserver.log.2.loghttp://brooketv.net/cc-appserver.log.3.logCC-Web Logs:
http://brooketv.net/cc-web.loghttp://brooketv.net/cc-web.log.1.loghttp://brooketv.net/cc-web.log.2.loghttp://brooketv.net/cc-web.log.3.logVar/logs:
Jan 20 - 26
http://brooketv.net/messages-20140126.txtJane 26th - current
http://brooketv.net/messagesnew.txtIf any of you see anything jump out at you, Id appreciate your input. I really need to get to the bottom of this problem.
Thanks!