zms processes won't die
Posted: Sat Jan 22, 2005 2:32 am
Okay, I'm sure most forum-regulars around here are rolling their eyes at me and thinking -- "haven't you run a search?? We've dealt with this before..."
Well, unfortunately everything I've found so far (after hours of searching) has lead me nowhere and I am beginning to wonder if this issue has not been resolved yet.
I am running the LiveCD 1.19.5 zoneminder version happily on a ~700mhz Celeron machine / 256mb ram (I know, it was a throw-together machine). All works fine and dandy until you begin to look at image streams. The zms process gets started... but never dies. Each new image stream spawns a new process, each taking a healthy share of CPU load with them.
I nearly fried the machine before I realized this is what was going on... it would just progressively get slower and slowwwwer until I couldn't even log in via SSH. I finally managed to after waiting minutes to log on and issue a reboot.
Here's the details:
- Running 1.19.5 (as mentioned above)
- Apache 2.0.48
From the searching I did do, I gathered that this was a known issue and it was supposed to have been resolved already by this Apache release. Unfortunately, I can attest that this is not the case. I've run a few experiments while watching the system's status via top and I've managed to bode well by identifying and manually killing the rogue zms processes.
Am I incorrect as far as the status of this bug? Is it not resolved on the Apache end?
If anyone else has run into this, I would greatly appreciate any info as to how you might have navigated your way around it.
Many thanks !!!
Well, unfortunately everything I've found so far (after hours of searching) has lead me nowhere and I am beginning to wonder if this issue has not been resolved yet.
I am running the LiveCD 1.19.5 zoneminder version happily on a ~700mhz Celeron machine / 256mb ram (I know, it was a throw-together machine). All works fine and dandy until you begin to look at image streams. The zms process gets started... but never dies. Each new image stream spawns a new process, each taking a healthy share of CPU load with them.
I nearly fried the machine before I realized this is what was going on... it would just progressively get slower and slowwwwer until I couldn't even log in via SSH. I finally managed to after waiting minutes to log on and issue a reboot.
Here's the details:
- Running 1.19.5 (as mentioned above)
- Apache 2.0.48
From the searching I did do, I gathered that this was a known issue and it was supposed to have been resolved already by this Apache release. Unfortunately, I can attest that this is not the case. I've run a few experiments while watching the system's status via top and I've managed to bode well by identifying and manually killing the rogue zms processes.
Am I incorrect as far as the status of this bug? Is it not resolved on the Apache end?
If anyone else has run into this, I would greatly appreciate any info as to how you might have navigated your way around it.
Many thanks !!!