502 Gatway error Every 2 days or so

Read 29537 times
If you got your 'Service.txt' file into /usr/sbin, all you have to do now is rename it, like this:

    mv /usr/sbin/Service.txt /usr/sbin/service
    chmod u+x /usr/sbin/service

[ds5950]$ usermod -G psacln,centovacast centovacast
-bash: usermod: command not found
[ds5950]$ sudo usermod -G psacln,centovacast centovacast
usermod: group 'psacln' does not exist

[ds5950]$ cd to /var/log/
-bash: cd: to: No such file or directory
[ds5950]$ sudo cd to /var/log/
sudo: cd: command not found

[ds5950]$ su - centovacast -s /bin/bash
Password:
su: Authentication failure
[ds5950]$ sudo /usr/local/centovacast/bin/ccmanage cronjob all
[INF] Cron job startup at 2013-05-30 00:53:31
[INF] Starting job: checkprocesses
[INF] Checking for crashed applications...
[INF] Completed job: checkprocesses
[INF] Starting job: pollhosts
[INF] Completed job: pollhosts
Result: OK Complete


[ds5950]$ sudo ps aux | grep cron
root      2855  0.0  0.0 192388  1092 ?        Ss   May29   0:00 /usr/sbin/cron
asapcpu1 24776  0.0  0.0 152408   844 pts/0    S+   00:53   0:00 grep cron
[ds5950]$ sudo kill -9 2855
[ds5950]$ sudo ps aux | grep cron
asapcpu1 24795  0.0  0.0 155324   844 pts/0    S+   00:54   0:00 grep cron
[ds5950]$
If you got your 'Service.txt' file into /usr/sbin, all you have to do now is rename it, like this:

    mv /usr/sbin/Service.txt /usr/sbin/service
    chmod u+x /usr/sbin/service

I did the renaming and it overwrote the old one and it went threw the Kill -9 and all that jazz, and it worked just fine, now I am restarting the server and in less then 2 days we shall see if it crashes, which i fear it will. ;_(
From what I gave, I could only go by with what our servers are.  So with the errors you are getting, I can only assume we dont have the same type.

cat /proc/version

Linux version 2.6.32-5-amd64 (Debian 2.6.32-46)
CrossFire-Hosting LLC.
Co-Owner
From what I gave, I could only go by with what our servers are.  So with the errors you are getting, I can only assume we dont have the same type.

cat /proc/version

Linux version 2.6.32-5-amd64 (Debian 2.6.32-46)

This is my server:

Linux version 3.2.34-grsec-2.9.1-rc1+ (root@womb) (gcc version 4.6.2 (Debian 4.6.2-5) ) #53 SMP Mon Nov 19 17:51:08 PST 2012
I just logged into my server and i got this:

http://prntscr.com/17hmnf

and i get this on every server:

http://prntscr.com/17hnag

Could this be my problem all along and if so, how do i fix it?

Reason: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '109998.9' at line 1


So then I also did this:


[DBG] End account check
[INF] Completed job: checkprocesses
[INF] Starting job: hourlymaint
[INF] Performing hourly maintenance...
[INF] Completed job: hourlymaint
[INF] Starting job: pollhosts
[DBG] Polling host Local server ...
[DBG] Updated status cache
[INF] Completed job: pollhosts
Result: OK Complete

[ds5950]$ sudo ps aux | grep cron
root     10182  0.0  0.0 156696  1092 ?        Ss   02:24   0:00 /usr/sbin/cron
asapcpu1 27550  0.0  0.0 177680   848 pts/0    SN+  17:07   0:00 grep cron
[ds5950]$ sudo kill -9 10182
[ds5950]$ sudo ps aux | grep cron
asapcpu1 27582  0.0  0.0 171364   848 pts/0    SN+  17:08   0:00 grep cron
[ds5950]$ sudo service crond stop
[ds5950]$ sudo service crond start
[ds5950]$ sudo ps aux | grep cron
asapcpu1 27591  0.0  0.0 130952   848 pts/0    SN+  17:09   0:00 grep cron

Interesting enough, when i just restarted the server it did not come back on so i have to get support from the Server Provider and they had to manually reboot it to bring it back up.
However! this time Centova had to be Recovered, because it never came back up.

Also I do want to point out that I first had this on a VPS and then i had to move it to a dedicated server. and THAT is when i started to have this Cron Job problem.

Is there a way to check a Log that tells me when the system goes down? I know there is a pattern to the crashes but I need to know exact times. Like a service logger?
Last Edit: May 30, 2013, 06:00:09 pm by asapcpu
So again I woke up to a Crond Error, and I don't know why being there is only 1 running

http://prntscr.com/17lst8

It could be something else other than more than 1 crond running.

Might I suggest that you contact Centova via Ticket support, and have one of them take a gander at your server.
CrossFire-Hosting LLC.
Co-Owner
I have sent in a Few tickets to Centova, and they are firm that it is not their software.

If you can read this: https://secure.centova.com/pages/helpdesk/ticket/view/id/ZR1-MOG8-423


also I'm looking in the log and I would like to know what this is.

http://prntscr.com/17ptt6
by the looks of it you need to create a user / group  centovacast

If it cant find / get the uid, then that user doesnt exist.

Maybe tryin doin a google to create user / groups on linux.


And sorry, only you can view your support tickets ;)
CrossFire-Hosting LLC.
Co-Owner
I got this error while syncing the playlist manually, under options button in media library, manual library update while on the phone with a client, we both got the Gateway timeout and were not able to access web panel for about 2 minutes, the music kept playing on both our ends, after a couple of refreshes it cleared up
My Auto DJ
Orlando, FL USA
Quality SHOUTcast Hosting http://myautodj.com
SHOUTcast Widgets http://shoutcastwidgets.com
got the Gateway timeout and were not able to access web panel for about 2 minutes, the music kept playing on both our ends, after a couple of refreshes it cleared up

this is the same thing that happenes to me, the music is okay and everyone can stream just fine but anything pertaining to the web panel is Dead.
Today the stream will go down at 2:15 AM so i did a check on it and was wondering which one should i kill of the Cron Jobs noted here?

http://prntscr.com/18nb77

One is Root User and the other is the login user.

for now I'm going to kill the Root Crond for now and see what happenes

and now:

[ds5950]$ sudo kill -9 21830
[ds5950]$ sudo ps aux | grep cron
asapcpu1  6224  0.0  0.0 117624   844 pts/0    SN+  17:44   0:00 grep cron
[ds5950]$ sudo /usr/local/centovacast/sbin/fixperms
chown: invalid user: `root.ccuser'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `ccuser'
chgrp: invalid group: `ccuser'
chown: invalid user: `root.ccuser'
chown: invalid user: `ccuser.ccuser'
chown: invalid user: `ccuser.ccuser'
chown: invalid user: `ccuser.ccuser'
chown: invalid user: `ccuser.ccuser'
chown: invalid user: `ccuser.ccuser'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chgrp: invalid group: `centovacast'
chown: invalid user: `ccuser:nogroup'
chown: invalid group: `nobody:ccuser'
chown: invalid user: `ccuser.ccuser'
chown: invalid user: `root.centovacast'
chown: invalid user: `centovacast.centovacast'
chown: invalid user: `centovacast.centovacast'
[ds5950]$


And this was working okay just yesterday.
okay new error,

http://prntscr.com/18rpm3

any ideas?
UPDATE:

I have found a way to prevent the system from crashing but it makes NO SENSE to me at all!

Firstly I login to the system and i get an error

http://prntscr.com/17hmnf

Then I log in threw SSL and i Run this command:

sudo /usr/local/centovacast/bin/ccmanage cronjob all

And I get an error on every Stream:

Error:  Could not execute query
File:   /usr/local/centovacast/system/class_LogProcessor.php:235
Query:  SELECT *,INET_NTOA(ipaddress) AS ipaddress FROM visitorstats_sessions WHERE accountid=202 AND resumedata<>'' ORDER BY starttime ASC LIMIT 0,109998.9
Reason: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '109998.9' at line 1
Call:   $SQL->select_query()


After that is done I can run the same command again and I get this:

[ds5950]$ sudo /usr/local/centovacast/bin/ccmanage cronjob all
[INF] Cron job startup at 2013-06-12 12:57:09
[INF] Starting job: checkprocesses
[INF] Checking for crashed applications...
[INF] Completed job: checkprocesses
Result: OK Complete

And the server does not Crash. in 2 days this process will start all over again and if i keep on it the server will not crash and the system does not need to be re-installed each time.

I have submited a ticket to Centova But so far it's not going anywhere!

Any and all help is appreciated and Many thanks for further assistance.