Big servers problems!

skynet

New member
Joined
Oct 14, 2008
Messages
2
I'm experiencing more downtime than uptime lately.
For unknown reason my server just stops responding. First that happened I just restarted it and it worked ok, but now even that doesn't help! I've found out that when this happens my apache error log gets quite big, here a few lines I ussualy get:

Argument "" isn't numeric in numeric gt (>) at /home/admin/domains/mydomain/public_html/Templates/index.temp line 753.
Argument "" isn't numeric in numeric gt (>) at /home/admin/domains/mydomain/public_html/Templates/index.temp line 754.
Argument "" isn't numeric in numeric gt (>) at /home/admin/domains/mydomain/public_html/Templates/index.temp line 755.
Argument "" isn't numeric in numeric gt (>) at /home/admin/domains/mydomain/public_html/Templates/index.temp line 756.

and so on...

And sometimes I get these errors as well:

[Tue Oct 14 08:45:56 2008] [warn] child process 7434 still did not exit, sending a SIGTERM
[Tue Oct 14 08:45:56 2008] [warn] child process 7435 still did not exit, sending a SIGTERM
[Tue Oct 14 08:45:56 2008] [warn] child process 7436 still did not exit, sending a SIGTERM

etc...

Site is run on apache 2.2.8, mysql5 and perl. I'm not an expert on dealing with servers, but so far the site was working ok, and I didn't do any major changes, just a few html lines.
Any help will be greatly appreciated!
 
How big are your servers? Mine are only 1U.

You are going to have to get whoever designed your site to look at the problem. Only they are going to know exactly what that error means. A general answer is that there is probably an error in some php code somewhere. You or somebody needs to look at those lines in the index.temp file.
 
Hehe.

I'm trying to contact the programmer, but he seems very busy. If he didn't respond to this in over a week, I doubt he will now.
Almost every line in index.temp and every other .temp gets this error. Kinda frustrating.
Ussualy works for a day then goes kaput :P
 
Hard to give real good advice without someone actually taking a look at the server, but the root problem looks to me like a programming one.
 
Back
Top