ZoneMinder Forums

I had problem with the state fields in 1.22.0 - which was fixed in 1.22.1 - but now I've upgraded to 1.22.2 I'm encountering similar behavior, but not quite the same. Before, the "enabled" state wasn't being saved in the sql database.

But this time, I've checked the database and my "Night" state is:

1:Modect:1,2:Modect:1,8:Modect:1,9:Modect:1,10:Modect:1,11:Modect:1,13:Record:1,14:Record:1,15:Record:1,16:Record:1,17:Record:1,18:Record:1,19:Record:1,20:None:0,22:Modect:1,23:Modect:1,24:None:0,25:Record:1,26:Record:1

Which looks ok to me (I know two are set to None). However, when I use

zmpkg.pl night

To switch to Night recording mode, only the first 10 entries are enabled. All cameras are switched to their correct operation, but any camera from 11 onwards (in my list) is italicised and has the Enabled button unticked.
I can then manually re-enable each camera and it works fine, but that's not automatic...

BTW, when saving a state - I guess I'm using the correct method. Click "Running" at the top, select the state I want to save as, then click Save?

Is there any outstanding issues with this bit of the code still? Am I only discovering it because of the relatively large number of cameras I have linked?

<bump>

Any thoughts on this?

Also had an issue today that may be related. apache2 had died and was refusing to start with

(98)Address already in use: make_sock: could not bind to address [::]:80
no listening sockets available, shutting down

Obviously something locking the port, so:

whip:/etc/apache2# netstat -lnp | grep ':80'
tcp6 0 0 :::80 :::* LISTEN 13285/perl

pid 13285 revealed

13285 ? S 1:03 /usr/bin/perl -wT /usr/local/bin/zmdc.pl startup

zmdc.pl wouldn't respond to a kill, I had to use kill -9 to stop it so apache2 could come up.

Any ideas to either issue? Not sure whether it's the upgrade to 1.22.2 or more likely, the coincide of adding four new cameras to the system. (Actual load is ok, runs 0.54 through 1.8 )

I think we need PHil to confirm if he changed anythin gregarding states. But he is on HOliday at the moent. I have a 1.22.2 system i can ket you have access to and play with to see if thats affected too if you like

I am not aware of any issues with run states at present. It is odd that the first few all work. Can you try manually editing the saved state string and moving the 11th entry to be 2nd or something. Then see if that entry works and it's the new 11th that doesn't work or the original one.