Re: Processes dont stop when stopping Apache
Albert Leidinger <albert.leidinger-kt1KeoM4Q/BvMmomy+XrYrNldLUNz+W/@public.gmane.org>
| Newsgroups | gmane.comp.web.fastcgi.devel |
|---|---|
| Message-ID | <[email protected]> |
Hi Sujay! >I am getting the following error when I tried to take a dump from a shared >memory segment. The process is getting killed in between. > >[Wed May 11 02:01:59 2005] [warn] FastCGI: server >"/usr/share/httpd/cgi-bin/dump.cgi" (pid 29781) terminated due to uncaught >signal '9' (Killed) >[Wed May 11 02:01:59 2005] [warn] FastCGI: server >"/usr/share/httpd/cgi-bin/dump.cgi" restarted (pid 29904) > > I guess thats just the same problem you posted some weeks ago? It was about writing 1.5 G to disk before stopping the process. Is this I typo or did you mean 1.5 GigaByte? Or am I just dumb and dont get IT-Slang? 8( Im just a DIY-Hacker, so my IT-knowledge isnt very good. But I guess writing 1.5G to a disk takes some time. Could it be, that Apache and the FCGI process manager dont want to wait that long? How do they divide hanging processes from some that dont hang but take much time to shut down? When they dont make a difference ... Just an idea. Give some more data to your problem! Is at least some data written to your file? How much? When do you dump the data? I guess when Apache is stopping? I, myself would be very interested to see how you managed to dump the data when stopping Apache. In my perl-Script it doesnt work as it should. I now get the signals and the processes dont run after stopping Apache, but the scripts seem just terminating in the middle of the loop. So the code after the loop to free the shared memory isnt executed. greetings Albert ___________________________________ fastcgi-developers mailing list http://fastcgi.com/fastcgi-developers/