Want me to take a look at it?
Sometimes a second pair of eyeballs will yeild the answer. I would still bet it's the process kill time of 5 minutes that's doing it.
Have you watched the processes, and done a top to see what's happening as they run? If you find they are being killed at the same time point, it's the process daemon.
Have you looked at any error messages? Is the program losing contact with the MySQL database for some reason? (process time-out?)
Once the program starts, there really is no reason for it to stop, unless:
1) runs out of disk space
2) runs out of pre-determined limits on time, cpu and/or memory usage
3) hit's an error that is reportable in the error.log for http, or the screen for telnet.
4) hit's a 'stop' somewhere in the code, left over from debugging.
5) hit's a 'permissions' problem in creating files or directories (easily fixed by chmod -R 777 top_dir_name), but this is usually reported correctly in #3
Beyond that, the program is in a loop, executing the same code, over and over, so it's not really doing 'new' things. It's eating memory, diskspace, CPU, and dealing with permissions. Most like it's #2, no matter what your ISP is telling you.
I'd be happy to take a look at it, tracked it down to #2 on more servers than any other problem.
http://www.postcards.com
FAQ: http://www.postcards.com/FAQ/LinkSQL/
Sometimes a second pair of eyeballs will yeild the answer. I would still bet it's the process kill time of 5 minutes that's doing it.
Have you watched the processes, and done a top to see what's happening as they run? If you find they are being killed at the same time point, it's the process daemon.
Have you looked at any error messages? Is the program losing contact with the MySQL database for some reason? (process time-out?)
Once the program starts, there really is no reason for it to stop, unless:
1) runs out of disk space
2) runs out of pre-determined limits on time, cpu and/or memory usage
3) hit's an error that is reportable in the error.log for http, or the screen for telnet.
4) hit's a 'stop' somewhere in the code, left over from debugging.
5) hit's a 'permissions' problem in creating files or directories (easily fixed by chmod -R 777 top_dir_name), but this is usually reported correctly in #3
Beyond that, the program is in a loop, executing the same code, over and over, so it's not really doing 'new' things. It's eating memory, diskspace, CPU, and dealing with permissions. Most like it's #2, no matter what your ISP is telling you.
I'd be happy to take a look at it, tracked it down to #2 on more servers than any other problem.
http://www.postcards.com
FAQ: http://www.postcards.com/FAQ/LinkSQL/
