Page 1 of 1
ZM 1.24.2 and Rimax IPcam 7100 support: can you help me?
Posted: Mon Jul 06, 2009 2:48 pm
by skyhook
I have installed ZM 1.24.2 (compiled from repository) on Ubuntu 9.04 server.
I configured my Rimax IPcam 7100 as desribed in manual, but still not working.
Here can find the manual,
http://www.rimax.net/Drivers/Manuel%20d ... 0RIMAX.pdf
See page 13 and 14...
http://ip:port/snapshot.jpg?account=admin?password=password
http://admin:password@ip:port/video.cgi
This cam is like Aviosys 9060-I or Grandtec IP CAM...
Anyone can helo me to setup ZM for this IP CAM?
Where can I find ZM logs?
TNX!
Posted: Mon Jul 06, 2009 8:27 pm
by kingofkya
what linux distro are you running ?
Posted: Mon Jul 06, 2009 8:29 pm
by skyhook
...as above, Ubuntu 9.04 server...
Posted: Mon Jul 06, 2009 8:30 pm
by skyhook
Posted: Mon Jul 06, 2009 8:32 pm
by kingofkya
wopes ok the logs are in /tmp there named zmc zma etc..
Posted: Mon Jul 06, 2009 8:53 pm
by skyhook
root@ubuntu:/tmp# ls -l /tmp
totale 20
-rw-r--r-- 1 www-data www-data 0 2009-07-06 16:13 zmaudit.log
-rw-r--r-- 1 www-data www-data 2689 2009-07-06 16:15 zmdc.log
srwxr-xr-x 1 www-data www-data 0 2009-07-06 16:17 zmdc.sock
-rw-r--r-- 1 www-data www-data 66 2009-07-06 16:13 zmfilter.log
-rw-r--r-- 1 www-data www-data 58 2009-07-06 16:13 zmpkg.log
drwxr-xr-x 2 www-data www-data 4096 2009-07-06 16:36 zmswap-m1
-rw-r--r-- 1 www-data www-data 0 2009-07-06 16:13 zmupdate.log
-rw-r--r-- 1 www-data www-data 1383 2009-07-06 16:15 zmwatch.log
Log to investigate?
Posted: Mon Jul 06, 2009 11:06 pm
by cordel
First go into options -> Debug -> and turn debug on and you can restrict it to zmc_ the capture damon.
Then look for the logs as set under options -> Paths -> PATH_LOGS
which in you case are obviously in /tmp.
You will want to look at the debug logs that will now only contain entries from the zmc damon as set above and this should give you a better idea what is going on.
This should also be applicable for any distro, which is why I put full instructions here.
Posted: Tue Jul 07, 2009 5:19 am
by skyhook
cordel wrote:First go into options -> Debug -> and turn debug on and you can restrict it to zmc_ the capture damon.
Then look for the logs as set under options -> Paths -> PATH_LOGS
which in you case are obviously in /tmp.
You will want to look at the debug logs that will now only contain entries from the zmc damon as set above and this should give you a better idea what is going on.
This should also be applicable for any distro, which is why I put full instructions here.
Code: Select all
root@ubuntu:/tmp# tail -f zmdc.log
07/07/2009 07:16:26.655320 zmdc[10332].ERR ['zmc -m 1' exited abnormally, exit status 255]
07/07/2009 07:17:06.034428 zmdc[10332].INF [Starting pending process, zmc -m 1]
07/07/2009 07:17:06.082969 zmdc[10332].INF ['zmc -m 1' starting at 09/07/07 07:17:06, pid = 10388]
07/07/2009 07:17:06.627161 zmdc[10332].ERR ['zmc -m 1' exited abnormally, exit status 255]
07/07/2009 07:18:26.057312 zmdc[10332].INF [Starting pending process, zmc -m 1]
07/07/2009 07:18:26.106972 zmdc[10332].INF ['zmc -m 1' starting at 09/07/07 07:18:26, pid = 10390]
07/07/2009 07:18:26.652305 zmdc[10332].ERR ['zmc -m 1' exited abnormally, exit status 255]
07/07/2009 07:21:06.006067 zmdc[10332].INF [Starting pending process, zmc -m 1]
07/07/2009 07:21:06.054957 zmdc[10332].INF ['zmc -m 1' starting at 09/07/07 07:21:06, pid = 10631]
07/07/2009 07:21:06.576529 zmdc[10332].ERR ['zmc -m 1' exited abnormally, exit status 255]
This error msg can help us?
Posted: Tue Jul 07, 2009 6:16 am
by cordel
No the debug logs can though, zmdc.og is a more general log. The debug logs only work after you turn them on and set the level.
Posted: Tue Jul 07, 2009 7:08 am
by skyhook
cordel wrote:No the debug logs can though, zmdc.og is a more general log. The debug logs only work after you turn them on and set the level.
Here a tipical log from my ZM
http://rapidshare.com/files/252902981/z ... 14771.html
Posted: Tue Jul 07, 2009 8:00 am
by cordel
Might try turning the debug level down to somewhere between 3 and 5. Setting it at 9, well, I will be here a while trying to find the useful bits for you
Code: Select all
07/07/09 08:56:05.526875 zmc_m1[14771].DB3-zm_remote_camera_http.cpp/105 [Connected to host, socket = 3]
07/07/09 08:56:05.526991 zmc_m1[14771].DB3-zm_remote_camera_http.cpp/126 [Request sent]
07/07/09 08:56:05.583625 zmc_m1[14771].DB3-zm_remote_camera_http.cpp/171 [Expecting 57 bytes]
07/07/09 08:56:05.583708 zmc_m1[14771].DB3-zm_remote_camera_http.cpp/196 [Read 57 bytes]
07/07/09 08:56:05.583741 zmc_m1[14771].DB6-zm_remote_camera_http.cpp/614 [HTTP/1.1 200 OK
system busy , snapshot failed.
]
07/07/09 08:56:05.583789 zmc_m1[14771].DB6-zm_remote_camera_http.cpp/622 [Got http header 'HTTP/1.1 200 OK
system busy , snapshot failed.
']
07/07/09 08:56:05.583827 zmc_m1[14771].DB6-zm_remote_camera_http.cpp/614 [system busy , snapshot failed.
]
07/07/09 08:56:05.583855 zmc_m1[14771].DB6-zm_remote_camera_http.cpp/641 [Got ignored header 'system busy , snapshot failed.
']
07/07/09 08:56:05.583886 zmc_m1[14771].DB3-zm_remote_camera_http.cpp/775 [Unable to extract entire header from stream, continuing]
07/07/09 08:56:05.586409 zmc_m1[14771].DB3-zm_remote_camera_http.cpp/166 [Socket closed]
07/07/09 08:56:05.586508 zmc_m1[14771].DB3-zm_remote_camera_http.cpp/775 [Unable to extract entire header from stream, continuing]
07/07/09 08:56:05.586627 zmc_m1[14771].INF-zm_signal.cpp/72 [Got signal 11 (Segmentation fault), crashing]
07/07/09 08:56:05.586960 zmc_m1[14771].ERR-zm_signal.cpp/84 [Signal address is 0xdf8d1e0c, from 0x807c99f]
07/07/09 08:56:05.587679 zmc_m1[14771].ERR-zm_signal.cpp/122 [Backtrace: /usr/local/bin/zmc [0x807c99f]]
07/07/09 08:56:05.587862 zmc_m1[14771].ERR-zm_signal.cpp/122 [Backtrace: /usr/local/bin/zmc [0x807c99f]]
07/07/09 08:56:05.587979 zmc_m1[14771].ERR-zm_signal.cpp/122 [Backtrace: /usr/local/bin/zmc [0x807dc2a]]
07/07/09 08:56:05.588127 zmc_m1[14771].ERR-zm_signal.cpp/122 [Backtrace: /usr/local/bin/zmc [0x808073a]]
07/07/09 08:56:05.588402 zmc_m1[14771].ERR-zm_signal.cpp/122 [Backtrace: /usr/local/bin/zmc [0x806eac4]]
07/07/09 08:56:05.588543 zmc_m1[14771].ERR-zm_signal.cpp/122 [Backtrace: /usr/local/bin/zmc [0x804d428]]
07/07/09 08:56:05.588679 zmc_m1[14771].ERR-zm_signal.cpp/122 [Backtrace: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe5) [0xb7062775]]
07/07/09 08:56:05.588815 zmc_m1[14771].ERR-zm_signal.cpp/122 [Backtrace: /usr/local/bin/zmc [0x804cc61]]
07/07/09 08:56:05.588949 zmc_m1[14771].INF-zm_signal.cpp/125 [Backtrace complete, please execute the following command for more information]
07/07/09 08:56:05.589102 zmc_m1[14771].INF-zm_signal.cpp/126 [addr2line -e /usr/local/bin/zmc 0x807c99f 0x807c99f 0x807dc2a 0x808073a 0x806eac4 0x804d428 0xb7062775 0x804cc61]
Posted: Tue Jul 07, 2009 8:04 am
by cordel
My guess would be that the path you have setup is not actually returning a stream. The camera is closing the connection after the first request.
Also I just noted you above post and link to another cam that is simular.
Because it looks the same has no weight as the firmware can be and often is different and it's the firmware that decides how the API for the cam works and how it sends images.
Since the other user for the other cam had to change code in ZM before compiling, if this cam is sending the same image format, it will never work with ZM with out hacking the code before compile time which means the cam is likely doing something that is not expected.
Posted: Tue Jul 07, 2009 1:55 pm
by skyhook
Posted: Tue Jul 07, 2009 3:01 pm
by skyhook
The problem seem "Can't shmget, probably not enough shared memory space free: Invalid argument"
Splved according Wiki...
http://www.zoneminder.com/wiki/index.ph ... esolutions.
Posted: Tue Jul 07, 2009 6:12 pm
by cordel
If you have the error "Can't shmget, probably not enough shared memory space free" in your log, then yes you should fix it as we have outlined in the FAQ so that you have enough. Though I didn't see that in the log you posted for me.
