Page 1 of 1

GUI Console says "Stopped" but is actually "Running"...

Posted: Wed Jan 14, 2015 7:01 pm
by cgutierrez
Hi! I recently upgraded a Zoneminder 1.27 system running on Fedora 21 x64 to Zoneminder 1.28. For the most part, the upgrade went well and the system *is* up and running. There is just one glitch... for some reason, the console thinks that Zoneminder is "Stopped" and accordingly the links to cycle, monitor and view the cameras are not active.

If I call the scripts directly with the proper view=cycle or view=watch, etc. I am able to view the corresponding view perfectly.

Also, if I run /usr/local/bin/zmdc.pl check ... this returns "running" as it should. daemonCheck() in functions.php should be returning True.

The httpd logs did not show anything that caught my eye as an error.

I have included a screenshot of my console and the zmdc.pl check run. (The high number of events in each monitor pre-date this upgrade...)

I think I must have ignored something obvious while upgrading... but what? ;)

Thanks,

Carlos

Re: GUI Console says "Stopped" but is actually "Running"...

Posted: Wed Jan 14, 2015 7:10 pm
by cgutierrez
I'm having difficulty uploading those screenshots to the forum... :\

Re: GUI Console says "Stopped" but is actually "Running"...

Posted: Wed Jan 14, 2015 7:23 pm
by cgutierrez
GUI Console thinks it is stopped...

Image

http://23.253.220.18/20150114_100629.jpg

Re: GUI Console says "Stopped" but is actually "Running"...

Posted: Wed Jan 14, 2015 7:25 pm
by cgutierrez
But Zoneminder is actually running and running well...

Image

Re: GUI Console says "Stopped" but is actually "Running"...

Posted: Sat Jan 17, 2015 1:11 am
by knight-of-ni
Many distros have started using private, tmpfs folders for /tmp that reside in memory rather than a traditional folder on your local disk.
This causes problems with zoneminder. Specifically, systemd and the web ui can disagree on the running/stopped status.

The way to avoid this is to set ZM_TMPDIR to something other than "/tmp" when building. Zoneminder now defaults to /var/tmp, but I don't remember if that change made it into 1.28.0 or not.

Re: GUI Console says "Stopped" but is actually "Running"...

Posted: Mon Jan 19, 2015 4:15 am
by cgutierrez
Thanks for replying...

I checked my CMakeCache.txt file and I had already compiled with:

//Location of temporary files, default: /tmp/zm
ZM_TMPDIR:PATH=/var/tmp/zm


But then, I checked all the other paths and found that I also had:

//Location of Unix domain socket files, default /var/run/zm
ZM_SOCKDIR:PATH=/var/run/zm


but on the web interface, on my Zoneminder options, I had:

PATH_SOCKS Path to the various Unix domain socket files that ZoneMinder uses (?) /var/tmp/zm

So I changed /var/tmp/zm to /var/run/zm, saved, and systemctl start zoneminder ...

And now the GUI Console is happy and shows Running! :D

Re: GUI Console says "Stopped" but is actually "Running"...

Posted: Tue Jan 20, 2015 9:36 pm
by JoseCoronaMX
Hi!

I have the same problem, can you help me?
I run shmz (centos) from a AsteriskNOW img and my links to live video (Monitor) are missing and my console stay always on stopped.
Any suggestions?

Thanks!

Can you unlock me the upload imgs*

Re: GUI Console says "Stopped" but is actually "Running"...

Posted: Thu Jan 14, 2016 9:03 pm
by mrd
Old thread, but I see this running on Ubuntu 14.04 with ZM 1.28.107, which seems to be logging to /tmp/zm