ZoneMinder Forums

ZoneMinder V1.24.3 downloaded 29/Dec/2010
Logitech QuickCam 4000

Processing through getting ZM working on a Trixbox Centos 5.5.
I can get video through to ZM and can set Zones but it appears the analysis daemon is crashing. The log shows;

Jan 1 20:18:39 hans zmwatch[5577]: INF [Restarting analysis daemon for Qcam, time since last analysis 10 seconds (1293884319-1293884309)]
Jan 1 20:18:39 hans zmdc[5526]: INF ['zma -m 5' starting at 11/01/01 20:18:39, pid = 5682]
Jan 1 20:18:39 hans zmwatch[5577]: INF ['zma -m 5' starting at 11/01/01 20:18:39, pid = 5682]
Jan 1 20:18:39 hans zmdc[5682]: INF ['zma -m 5' started at 11/01/01 20:18:39]
Jan 1 20:18:39 hans zma_m5[5682]: INF [Debug Level = 0, Debug Log = <none>]
Jan 1 20:18:39 hans zma_m5[5682]: INF [In mode 5/1, warming up]
Jan 1 20:18:39 hans zma_m5[5682]: INF [Got signal 11 (Segmentation fault), crashing]
Jan 1 20:18:39 hans zma_m5[5682]: ERR [Signal address is 0x8, from 0x8068e12]
Jan 1 20:18:39 hans zma_m5[5682]: ERR [Backtrace: /usr/local/bin/zma [0x8068e12]]
Jan 1 20:18:39 hans zma_m5[5682]: ERR [Backtrace: /usr/local/bin/zma [0x8068e12]]
Jan 1 20:18:39 hans zma_m5[5682]: ERR [Backtrace: /usr/local/bin/zma [0x8070749]]
Jan 1 20:18:39 hans zma_m5[5682]: ERR [Backtrace: /usr/local/bin/zma [0x804c5c1]]
Jan 1 20:18:39 hans zma_m5[5682]: ERR [Backtrace: /lib/libc.so.6(__libc_start_main+0xdc) [0x8a2e9c]]
Jan 1 20:18:39 hans zma_m5[5682]: ERR [Backtrace: /usr/local/bin/zma [0x804c251]]
Jan 1 20:18:39 hans zma_m5[5682]: INF [Backtrace complete, please execute the following command for more information]
Jan 1 20:18:39 hans zma_m5[5682]: INF [addr2line -e /usr/local/bin/zma 0x8068e12 0x8068e12 0x8070749 0x804c5c1 0x8a2e9c 0x804c251]
Jan 1 20:18:39 hans zmdc[5526]: ERR ['zma -m 5' exited abnormally, exit status 11]

Any suggestions of where to look?

Happy New Year and Decade
Thanks

Richard

Can you run the addr2line command shown in the log you just pasted?
This should help finding the source for the segmentation fault.

Actually I did when the Seg Error report came but I neglected to post - sorry. Here is the output;


~]# addr2line -e /usr/local/bin/zma 0x8068e12 0x8068e12 0x8070749 0x804c5c1 0x8a2e9c 0x804c251
/root/Zoneminder-svn/zm/src/zm_monitor.cpp:225
/root/Zoneminder-svn/zm/src/zm_monitor.cpp:225
/root/Zoneminder-svn/zm/src/zm_monitor.cpp:1238
/root/Zoneminder-svn/zm/src/zma.cpp:119
??:0
??:0

All this seems to be pointing to this line in zm_monitor.cpp;
225-> if ( shared_data->state == ALARM || shared_data->state == ALERT )


Could this be a memory allocation issue?



Richard

It appears that ZoneMinder is trying to check the state of the monitors linked to the current monitor. can you unlink all monitors from that monitor and other monitors?

Also, Please enable debugging in zoneminder's options (level 9), it will place debugging files in /tmp/ and then upload the latest log file to here or the contents of "cat thefile | grep -i link" I want to check something in regard to linked monitors, it seems you aren't the only person with this problem.

mastertheknife