[ Date Index ][
Thread Index ]
[ <= Previous by date / thread ] [ Next by date / thread => ]
On 23.11.2003 13:04 mike@xxxxxxxxxxxxx wrote: > G'day all, > > I have a bit of code... > > log="/log/x25dl1.log"; > while true > do > x25dl1 2>&1 >> $log > status=$? > dd=`date +"%d-%b-%Y %H:%M:%S"|tr [:lower:] [:upper:]` > echo "$dd [$$] FATAL: x25dl1 has died. Status = $status">>$log > sleep 5 > done > > In the log file I get... > 22-NOV-2003 19:00:02 [688] FATAL: x25dl1 has died. Status = 141 > > I can't find what the status of 141 is. Any ideas? > > x25dl1 is a c program. > If it was perl I would have said it was a SIGPIPE error, which would make sense since it uses sockets to communicate. OK, more on this. x25dl1 is a forking process (In more ways than one!!) The process that dies is the parent, when it dies it takes all the children with it. This could be bad, in that the children might actually be doing something at the time. I think there might be a problem with a child that is causing the parent to die, does that help/make sense? There is another problem. The children send and receive via sockets, it sends data to a another process and then waits for the other process to reply. Sometime the other process never answers and the x25dl1 child sits there for ever waiting for data that is never going to appear (why I am not sure yet, but I am working on that) In the mean time I have a process that runs from cron every 15 minutes and kills off x25dl1 children that have been running for more than 15 minutes. This is just to reduce the clutter, if the child is still running after about 15 seconds something has gone wrong. Could this kill process be causing a problem? I.E. causing the parent to die, I don't see a link as yet, but I am beginning to wonder. The log file shows that the parent dies at either 00,15,30,45 minutes past the hour which is when the kill process runs. But it also dies with the same error outside these times as well. -- 'ooroo Mike...(:)-) --------------------------------------------------- Email: mike@xxxxxxxxxxxxx o You need only two tools. o ///// A hammer and duct tape. If it /@ `\ /) ~ doesn't move and it should use > (O) X< ~ Fish!! the hammer. If it moves and `\___/' \) ~ shouldn't, use the tape. \\\ --------------------------------------------------- -- The Mailing List for the Devon & Cornwall LUG Mail majordomo@xxxxxxxxxxxx with "unsubscribe list" in the message body to unsubscribe.