Zoneminder just... died? 1.28.107

[McFuzz]

I have 1.28.107 deployed on Ubuntu 14.03 LTS deployed on a virtual machine. Over the weekend, ZoneMinder just died - no rhyme or reason... this is the syslog excerpt:

Code: Select all

Nov 26 07:14:44 BigBrother zma_m5[3066]: INF [ShopCam_4: 184417 - Gone back into alarm state]
Nov 26 07:14:44 BigBrother zma_m5[3066]: INF [ShopCam_4: 184419 - Gone into alert state]
Nov 26 07:15:00 BigBrother zmwatch[3042]: INF [Analysis daemon for  ShopCam_4 needs restarting, time since last analysis 15 seconds (1448550900-1448550885)]
Nov 26 07:15:02 BigBrother zmvideo[7643]: INF [Creating video file New_Event-r1-s1.avi for event 146910]
Nov 26 07:20:22 BigBrother zmaudit[3035]: INF [Filesystem event '5/145021' does not exist in database]
Nov 26 08:00:01 BigBrother CRON[11519]: (root) CMD (/usr/bin/zmpkg.pl All_record)
Nov 26 08:00:01 BigBrother zmpkg[11520]: INF [Sanity checking States table...]

The cron job at 8 changes from motion detection to constant record - and that's when it completely died. Not sure what else I can look for but, anyone has a clue as to what may have happened?

[asker]

When you say 'died' what does it mean? No more logs after that last line?
1. What happens if you stop/restart ZM
2. What happens if you manually change to All_record state from command line or via web console?
3. Are you able to connect to mysql? is it running? That specific line connects to mysql right after printing that log

[bbunge]

Did this happen after an update to Ubuntu?

[McFuzz]

Sorry for the delayed response gents:

When you say 'died' what does it mean? No more logs after that last line?
1. What happens if you stop/restart ZM
2. What happens if you manually change to All_record state from command line or via web console?
3. Are you able to connect to mysql? is it running? That specific line connects to mysql right after printing that log

1. Actually nothing - it would not respond to any service stop/start/restart commands.
2. See above - UI was inaccessible
3. I didn't think of doing so but I did not see any indication of sql crapping out.

After a reboot - it started working just fine.

Did this happen after an update to Ubuntu?

Negative - the box has had an uptime of about 60 days at that point.