Hi.
On Fedora Core 4, when trying to view a stream from a network camera, this what the log file shows:
Corrupt JPEG data: premature end of data segment
Invalid JPEG file structure: two SOI markers
'zmc -m 1' crashed at 05/10/09 23:50:13, exit status 1
'zmc -m 1' started at 05/10/09 23:50:13
'zmc -m 1' starting at 05/10/09 23:50:13, pid = 8852
'zmc -m 1' stopping at 05/10/09 23:50:33
'zmc -m 1' died at 05/10/09 23:50:33
Starting pending process, zmc -m 1
'zmc -m 1' started at 05/10/09 23:50:38
'zmc -m 1' starting at 05/10/09 23:50:38, pid = 8864
Corrupt JPEG data: premature end of data segment
Invalid JPEG file structure: two SOI markers
'zmc -m 1' crashed at 05/10/09 23:50:50, exit status 1
Use of uninitialized value in hash element at /usr/local/bin/zmdc.pl line 346, <CLIENT> line 1.
'zmc -m 1' started at 05/10/09 23:50:54
'zmc -m 1' starting at 05/10/09 23:50:54, pid = 8902
Corrupt JPEG data: premature end of data segment
Invalid JPEG file structure: two SOI markers
'zmc -m 1' crashed at 05/10/09 23:51:04, exit status 1
Use of uninitialized value in hash element at /usr/local/bin/zmdc.pl line 346, <CLIENT> line 1.
Use of uninitialized value in hash element at /usr/local/bin/zmdc.pl line 346, <CLIENT> line 1.
'zmc -m 1' started at 05/10/09 23:52:52
'zmc -m 1' starting at 05/10/09 23:52:52, pid = 8959
'zmc -m 1' stopping at 05/10/09 23:53:02
'zmc -m 1' died at 05/10/09 23:53:09, signal 8
Use of uninitialized value in hash element at /usr/local/bin/zmdc.pl line 346, <CLIENT> line 1.
'zmc -m 1' started at 05/10/09 23:53:19
'zmc -m 1' starting at 05/10/09 23:53:19, pid = 8969
'zmc -m 1' stopping at 05/10/09 23:53:30
'zmc -m 1' died at 05/10/09 23:53:36, signal 8
Use of uninitialized value in hash element at /usr/local/bin/zmdc.pl line 346, <CLIENT> line 1.
'zmc -m 1' started at 05/10/09 23:53:47
'zmc -m 1' starting at 05/10/09 23:53:47, pid = 8979
On another PC, with Fedora Core 4, all works fine. Any idea about this one?
Thanks.
zmc crashes each second
I came across something last week about the sis chipsets that had me deside that I didn't want to get them any more. I don't remember if it was compatiblity with linux or hardware but I do recall that it had something to do with networking and maybe the way it handles the pci bus.
I'd give ya the link if I could remember what it was.
Have you tried adding the sis drivers? : http://www.sis.com/download/
By the way nice to see ya back around
Regards,
Cordel
I'd give ya the link if I could remember what it was.
Have you tried adding the sis drivers? : http://www.sis.com/download/
By the way nice to see ya back around
Regards,
Cordel
Hi Cordel.
Thanks man - it's very nice to feel welcomed .
Phil - I think that this one goes to you - I ran the zmc with gdb, and discovered a pesky segfault:
Program received signal SIGSEGV, Segmentation fault.
0x08066c4e in RemoteCamera::GetResponse (this=0xeddc8b0)
at zm_remote_camera.cpp:820
820 subheaders[n_subheaders++] = subheader_ptr;
Looks like a memory leak? But wait - things are becoming even more stranger, when running the zmc with DBG_LEVEL set on 9, after a while the following segfault appears:
Program received signal SIGSEGV, Segmentation fault.
0x006804aa in vfprintf () from /lib/libc.so.6
Got my head scratching on it. BTW, all happes on FC4, with GCC4 (perhaps my previous post about GCC4 was a little too much optimisitic ).
Thanks man - it's very nice to feel welcomed .
Phil - I think that this one goes to you - I ran the zmc with gdb, and discovered a pesky segfault:
Program received signal SIGSEGV, Segmentation fault.
0x08066c4e in RemoteCamera::GetResponse (this=0xeddc8b0)
at zm_remote_camera.cpp:820
820 subheaders[n_subheaders++] = subheader_ptr;
Looks like a memory leak? But wait - things are becoming even more stranger, when running the zmc with DBG_LEVEL set on 9, after a while the following segfault appears:
Program received signal SIGSEGV, Segmentation fault.
0x006804aa in vfprintf () from /lib/libc.so.6
Got my head scratching on it. BTW, all happes on FC4, with GCC4 (perhaps my previous post about GCC4 was a little too much optimisitic ).
- zoneminder
- Site Admin
- Posts: 5215
- Joined: Wed Jul 09, 2003 2:07 pm
- Location: Bristol, UK
- Contact:
Hi,
Another report from the land of FC4 + ZM adventures .
Sometimes the zmc allocates a shared memory, but then it can't connect to it. The ipcs command shows the allocated segements, but also that no one connected to it (0 nattch). The syslog shows the following message - can't shmget...probably not enough shared memory:Permission denied. The owner of these shmem segments is apache of course, but zmc still can't connect for some reason.
Another report from the land of FC4 + ZM adventures .
Sometimes the zmc allocates a shared memory, but then it can't connect to it. The ipcs command shows the allocated segements, but also that no one connected to it (0 nattch). The syslog shows the following message - can't shmget...probably not enough shared memory:Permission denied. The owner of these shmem segments is apache of course, but zmc still can't connect for some reason.