The first thought that pops up (which assumes a unix system;
if not skip this part) is that you're hitting some sort of
resource limit on the system. If you are running this from
the command line, check 'limit cputime' in csh/tcsh or
'ulimit -t' in bash/ksh. Also, if the problem is occurring
when you log out, you'll need to 'nohup' your program, to
prevent it from being sent SIGHUP when you log out.. it's
run like 'nohup ./perl_program args'.
If the above doesn't help, there are unfortunately several
things that could be causing it outside of perl. As
mentioned above, it could be MySQL with the problem. The
best advice I can give is to do some verbose debugging in
the script: write out to a logfile, check every return code
from all system calls and MySQL calls, write success
messages for every part that succeeds, etc. Try putting
an END block in your perl code to trap the time that it's
dying, and see if it's doing so at a regular interval.
Hope this helps. | [reply] |
That's definitely a possibility. On my personal linux
machine, it never dies. On the web server, it is dying
aproximately once every ten minutes or so. I will do some
more research and see if that's the case, but that's what
I am thinking.
Thanks for the tips!
| [reply] |
Does your script maintain a persistant connection to MySQL (or any other applications) or
does it make a new connection every time?
If it does have presistant connections it could be that the connection is breaking
(from the other side) and that is killing your application. Have you tried running your
application as a command line process (not a daemon) and seeing if it reports any errors when it dies? | [reply] |
We've run it from the command line and even in the Windows
environment to see if it behaves differently. It is not a
persistent connection to the database, and on my personal
linux box it hasn't died yet. It's just occuring on the
actual server (which the sysadmins have restricted access
to so that I can't run it as commandline there).
There aren't any differences between the OS's, so I'm going
to have to dig a little on it. Thanks...
| [reply] |