ZoneMinder Console - Stopped - v1.25.0

[dogmeat206]

I got ZoneMinder installed on CentOS 6.

The page comes up but the status at the top says

'ZoneMinder Console - Stopped - v1.25.0'.

I see this in the log file, under the zmpkg filter.

2011-10-11 15:59:52.311820 zmpkg 20056 ERR Unable to run "/usr/local/bin/zmdc.pl startup", output is "Starting server" zmpkg.pl
2011-10-11 15:59:41.508670 zmpkg 20056 INF Command: start zmpkg.pl

Under filter, zmf, I see this and it repeats constantly.

2011-10-11 16:34:19.365990 zmf 19788 INF Frame server socket open, awaiting images zmf.cpp 86
2011-10-11 16:34:19.015321 zmf 19788 ERR Incomplete read of frame image data, 15960 bytes only zmf.cpp 243

In the filter line zmdc, I see this......

2011-10-11 15:59:54.095650 zmdc 20072 FAT Can't bind: Address already in use zmdc.pl
2011-10-11 15:59:52.299920 zmdc 20070 FAT Can't connect: Permission denied zmdc.pl
2011-10-11 15:59:42.087660 zmdc 20072 INF Server starting at 11/10/11 15:59:42 zmdc.pl

And under zma_m1 (which is one of the two cameras)

2011-10-11 16:36:25.748200 zma_m1 19795 ERR Can't write frame: Broken pipe zm_event.cpp 322
2011-10-11 16:36:23.120173 zma_m1 19795 ERR Can't write frame: Broken pipe zm_event.cpp 322
2011-10-11 16:36:16.740839 zma_m1 19795 ERR Can't write frame: Broken pipe zm_event.cpp 322
2011-10-11 16:36:16.340012 zma_m1 19795 ERR Can't write frame: Broken pipe zm_event.cpp 322
2011-10-11 16:35:50.451198 zma_m1 19795 ERR Can't write frame: Broken pipe zm_event.cpp 322
2011-10-11 16:35:50.070829 zma_m1 19795 ERR Can't write frame: Broken pipe zm_event.cpp 322
2011-10-11 16:35:47.447494 zma_m1 19795 ERR Can't write frame: Broken pipe zm_event.cpp 322
2011-10-11 16:35:46.860680 zma_m1 19795 ERR Can't write frame: Broken pipe zm_event.cpp 322
2011-10-11 16:35:39.609774 zma_m1 19795 ERR Can't write frame: Broken pipe zm_event.cpp 322
2011-10-11 16:35:19.352843 zma_m1 19795 ERR Can't write frame: Broken pipe zm_event.cpp 322
2011-10-11 16:34:19.205333 zma_m1 19795 ERR Can't write frame: Broken pipe zm_event.cpp 322
2011-10-11 16:33:13.785811 zma_m1 19795 INF Monitor-1: 15000 - Processing at 5.00 fps zm_monitor.cpp 1055


The bad thing about it is that I can't get Montage mode running if the Console status at the top shows stopped.

If I click on it, and select start, it stays in the 'stopped' state.


Any ideas guys?

[dogmeat206]

Looking back in the 1.24.x area, I noticed a post on similar things.


The fact that the 'Console' was in a constant stopped state. Ref here,

http://www.zoneminder.com/forums/viewto ... 21&t=18194

Turning SELinux to permissive instead of enforcing fixed the issue there.

Now I am faced with a bunch of blank video screens.

I am working with a AXIS M3014 Network Camera. Two to be exact.

I am wanting to stream H264 with ffmpeg to ZoneMinder.....

Anyone know?

[dogmeat206]

Still receiving error,

2011-10-11 18:47:07.421548 web_php 2254 ERR socket_sendto( /tmp/zm/zms-244828s.sock ) failed: No such file or directory includes/functions.php 2322

[gjpc]

does www-data:www-data own your /tmp/zm directory?

[dogmeat206]

No, Apache does.


This is what zoneminder had set it to on install.

[clipo]

I've got the same error,

ZM 1.25 on CentOS 6,

I have disabled SELinux and all seems to be working ok now,

[JEL]

similar problem here v1.25.0 Suse 12.1 SELinux off

cron shuts down at ~07:15 which gave no indication of an error. It starts again right after
and zm would not start anymore


syslog:
Dec 11 07:12:49 xal9001 zmc_dvideo0[7336]: INF [IR-oben: 308000 - Capturing at 9.90 fps]
Dec 11 07:14:07 xal9001 zma_m1[8251]: INF [IR-oben: 186000 - Processing at 9.90 fps]
Dec 11 07:14:30 xal9001 zmc_dvideo0[7336]: INF [IR-oben: 309000 - Capturing at 9.90 fps]
Dec 11 07:14:59 xal9001 zma_m3[10347]: INF [Dom: 1615 - Gone into alarm state]
Dec 11 07:15:00 xal9001 zma_m3[10347]: INF [Dom: 1615 - Opening new event 279, alarm start]
Dec 11 07:15:01 xal9001 /USR/SBIN/CRON[10881]: (root) CMD (/sbin/shutdown -h)
Dec 11 07:15:01 xal9001 systemd-shutdownd[10899]: Creating /run/nologin, blocking further logins...
Dec 11 07:15:01 xal9001 cron[3461]: postdrop: warning: unable to look up public/pickup: No such file or directory
Dec 11 07:15:10 xal9001 zma_m3[10347]: INF [Dom: 1618 - Gone into alert state]
Dec 11 07:15:48 xal9001 zma_m1[8251]: INF [IR-oben: 187000 - Processing at 9.90 fps]
Dec 11 07:16:01 xal9001 haveged: haveged stopping due to signal 15
Dec 11 07:16:01 xal9001 kernel: Kernel logging (proc) stopped.
Dec 11 07:16:01 xal9001 rsyslogd: [origin software="rsyslogd" swVersion="5.8.5" x-pid="683" x-info="XXXdeletedXXX for forums sake] exiting on signal 15.
Dec 11 07:17:15 xal9001 kernel: imklog 5.8.5, log source = /proc/kmsg started.

zm log:
2011-12-11 06:17:51.821420 zmpkg 4305 INF Command: stop zmpkg.pl
2011-12-11 06:17:51.810120 zmpkg 4297 INF Command: start zmpkg.pl
2011-12-11 06:15:48.685149 zma_m1 8251 INF IR-oben: 187000 - Processing at 9.90 fps zm_monitor.cpp 1055
2011-12-11 06:15:10.444332 zma_m3 10347 INF Dom: 1618 - Gone into alert state zm_monitor.cpp 1382
2011-12-11 06:14:59.961819 zma_m3 10347 INF Dom: 1615 - Opening new event 279, alarm start zm_monitor.cpp 1346
2011-12-11 06:14:59.321183 zma_m3 10347 INF Dom: 1615 - Gone into alarm state zm_monitor.cpp 1326
2011-12-11 06:14:30.428952 zmc_dvideo0 7336 INF IR-oben: 309000 - Capturing at 9.90 fps zm_monitor.cpp 2598
2011-12-11 06:14:07.410920 zma_m1 8251 INF IR-oben: 186000 - Processing at 9.90 fps zm_monitor.cpp 1055
2011-12-11 06:12:49.288928 zmc_dvideo0 7336 INF IR-oben: 308000 - Capturing at 9.90 fps zm_monitor.cpp 2598

Interesting:
AND I noticed that the settings in options were reset to the default values
and not the values I set a couple hours ago.
e.g. DIR_EVENTS is again 'events' - that caught my eyes as the disk usage was too high
all of a sudden.
I'll go deeper to find the problem instead of restarting and probably confusing/messing up
the database.

Solving the above problem might solve this problem.