So, zm is finally up and running. It looks good, you can see my tools and stuff. i have one of the cheapy ebay four port cards with only one chip.
anywho, so it was working and recording video properly, as long as there was only one camera connected at a time. As soon as more than one was connected, boom... whenever zm starts, it freezes my comp. Total lock up.
upgraded everything. Still freezes.
turned off all monitors and it still freezes when starting zm
I have no idea what to do or what to check. tired of rebooting. Any suggestions are appreciated. Awesome program though, wish I knew a little more.
frozen on startup
Ok. I'm working on it. Tried reformatting and starting over from scratch. it's still doing it.
Running FC4 on an intel 4 machine. nothing special about it. Like I said, it worked fine until trying to access two cameras on a four port 1 chip 878a card. Now zm freezes whenever starting.
var/logs/messages shows the following right before freeze
Jun 28 00:12:16 localhost zmpkg[3495]: INF [Command: start]
Jun 28 00:12:17 localhost zmdc[3507]: INF [Server starting at 06/06/28 00:12:17]
Jun 28 00:12:21 localhost zmdc[3530]: INF ['zmfilter.pl' started at 06/06/28 00:12:21]
Jun 28 00:12:21 localhost zmdc[3507]: INF ['zmfilter.pl' starting at 06/06/28 00:12:21, pid = 3530]
Jun 28 00:12:21 localhost zmfilter[3530]: INF [Scanning for events]
Jun 28 00:12:21 localhost zmdc[3535]: INF ['zmaudit.pl -c' started at 06/06/28 00:12:21]
Jun 28 00:12:21 localhost zmdc[3507]: INF ['zmaudit.pl -c' starting at 06/06/28 00:12:21, pid = 3535]
Jun 28 00:12:22 localhost zmaudit[3535]: INF [Filesystem monitor '1' does not exist in database]
Jun 28 00:12:22 localhost zmaudit[3535]: INF [deleting]
Jun 28 00:12:22 localhost zmdc[3507]: INF ['zmwatch.pl' starting at 06/06/28 00:12:22, pid = 3542]
Jun 28 00:12:22 localhost zmdc[3542]: INF ['zmwatch.pl' started at 06/06/28 00:12:22]
Jun 28 00:12:22 localhost zmwatch[3542]: INF [Watchdog starting]
Jun 28 00:12:22 localhost zmwatch[3542]: INF [Watchdog pausing for 30 seconds]
Jun 28 00:12:22 localhost zmdc[3546]: INF ['zmupdate.pl -c' started at 06/06/28 00:12:22]
Jun 28 00:12:22 localhost zmdc[3507]: INF ['zmupdate.pl -c' starting at 06/06/28 00:12:22, pid = 3546]
Jun 28 00:12:23 localhost Update agent starting at 06/06/28 00:12:23
Jun 28 00:12:23 localhost zmupdate[3546]: INF [Checking for updates]
Jun 28 00:12:24 localhost zmupdate[3546]: INF [Got version: '1.22.2']
zmc --device /dev/video0 returns immediately and tvtime shows a clear picture.
Running FC4 on an intel 4 machine. nothing special about it. Like I said, it worked fine until trying to access two cameras on a four port 1 chip 878a card. Now zm freezes whenever starting.
var/logs/messages shows the following right before freeze
Jun 28 00:12:16 localhost zmpkg[3495]: INF [Command: start]
Jun 28 00:12:17 localhost zmdc[3507]: INF [Server starting at 06/06/28 00:12:17]
Jun 28 00:12:21 localhost zmdc[3530]: INF ['zmfilter.pl' started at 06/06/28 00:12:21]
Jun 28 00:12:21 localhost zmdc[3507]: INF ['zmfilter.pl' starting at 06/06/28 00:12:21, pid = 3530]
Jun 28 00:12:21 localhost zmfilter[3530]: INF [Scanning for events]
Jun 28 00:12:21 localhost zmdc[3535]: INF ['zmaudit.pl -c' started at 06/06/28 00:12:21]
Jun 28 00:12:21 localhost zmdc[3507]: INF ['zmaudit.pl -c' starting at 06/06/28 00:12:21, pid = 3535]
Jun 28 00:12:22 localhost zmaudit[3535]: INF [Filesystem monitor '1' does not exist in database]
Jun 28 00:12:22 localhost zmaudit[3535]: INF [deleting]
Jun 28 00:12:22 localhost zmdc[3507]: INF ['zmwatch.pl' starting at 06/06/28 00:12:22, pid = 3542]
Jun 28 00:12:22 localhost zmdc[3542]: INF ['zmwatch.pl' started at 06/06/28 00:12:22]
Jun 28 00:12:22 localhost zmwatch[3542]: INF [Watchdog starting]
Jun 28 00:12:22 localhost zmwatch[3542]: INF [Watchdog pausing for 30 seconds]
Jun 28 00:12:22 localhost zmdc[3546]: INF ['zmupdate.pl -c' started at 06/06/28 00:12:22]
Jun 28 00:12:22 localhost zmdc[3507]: INF ['zmupdate.pl -c' starting at 06/06/28 00:12:22, pid = 3546]
Jun 28 00:12:23 localhost Update agent starting at 06/06/28 00:12:23
Jun 28 00:12:23 localhost zmupdate[3546]: INF [Checking for updates]
Jun 28 00:12:24 localhost zmupdate[3546]: INF [Got version: '1.22.2']
zmc --device /dev/video0 returns immediately and tvtime shows a clear picture.
bad hard drive
ok, so here's the deal. The hard drive apparently took a poop right in the area where the zm web files were so that everythyme it started, the kernel would panic as it was reading that area of the hard drive. Strange coincidence.
Anyway, the fix was to boot in single user mode (init 1 at root prompt), and umount the media partition and e2fsck -fcb <drive>
this forced a surface check and recorded bad blocks. Problem solved. Hopefully zm didn't cause the bad blocks since I'm going to try multiple cameras again. Does this mean i'm sadomasochistic?
Anyway, the fix was to boot in single user mode (init 1 at root prompt), and umount the media partition and e2fsck -fcb <drive>
this forced a surface check and recorded bad blocks. Problem solved. Hopefully zm didn't cause the bad blocks since I'm going to try multiple cameras again. Does this mean i'm sadomasochistic?
