Goodnight
I attach the error log ZoneMinder
thanks
After upgrade to 1.29, crashing daily
-
AndresCT46
- Posts: 3
- Joined: Wed Aug 03, 2016 12:41 am
Re: After upgrade to 1.29, crashing daily
- Attachments
-
- zm-log.html.zip
- (4.53 KiB) Downloaded 146 times
Re: After upgrade to 1.29, crashing daily
I have subscribed to this topic since i am encountering the same problems.
Re: After upgrade to 1.29, crashing daily
I'm not providing any solutions, but just what I've observed so far on my particular issue with daily crashes.
I'm not sure if I'm getting the same thing, but I also upgraded from 1.28 to 1.29. The resource savings is very nice. I also get crashes almost daily. However, I have noticed, that it's only when I load the web interface. I'll immediately start it again, and it works fine. I also noticed that it doesn't crash before I log in, as all the event from before that specific time are there. I also believe that I checked via "service zoneminder status" before I logged into the web interface and it showed as stopped. This leads me to believe that ZM is still functioning correctly, it's just not getting it's status correctly. I will checked via top (I like htop), next time this happens to confirm if any zmc processes are live. Additionally, I've checked the syslog and all zm logs, and only issue I can find is a very seldom buffer overrun and what seems to be a shared memory error. My /run/shm was at 86%, so I increased it size in the mean time to test that.
Update: So, it did it's "crash" again. I checked htop, and the ZMC instances are still running. However, the web interface and "service zoneminder status" both show as stopped. After I started zoneminder again, the zmc instances were killed and relaunched.
I'm not sure if I'm getting the same thing, but I also upgraded from 1.28 to 1.29. The resource savings is very nice. I also get crashes almost daily. However, I have noticed, that it's only when I load the web interface. I'll immediately start it again, and it works fine. I also noticed that it doesn't crash before I log in, as all the event from before that specific time are there. I also believe that I checked via "service zoneminder status" before I logged into the web interface and it showed as stopped. This leads me to believe that ZM is still functioning correctly, it's just not getting it's status correctly. I will checked via top (I like htop), next time this happens to confirm if any zmc processes are live. Additionally, I've checked the syslog and all zm logs, and only issue I can find is a very seldom buffer overrun and what seems to be a shared memory error. My /run/shm was at 86%, so I increased it size in the mean time to test that.
Update: So, it did it's "crash" again. I checked htop, and the ZMC instances are still running. However, the web interface and "service zoneminder status" both show as stopped. After I started zoneminder again, the zmc instances were killed and relaunched.