ZoneMinder Forums

Is there a way to mark this as solved?

Great rockedge, it worked! It was indeed set to 1.

What is strange about this is that I didn't change this settings recently. Maybe only after the update ZoneMinder started "caring" about this.

It seems we have a clue!

[Thu May 25 12:51:43.548484 2017] [:error] [pid 7679] [client XXX.XXX.XXX.XXX:63418] PHP Notice: A session had already been started - ignoring session_start() in /usr/share/zoneminder/www/index.php on line 128, referer: https://mydomain/zm/index.php

Right now it was stopped, I don't know why. But "service zoneminder stop,start or restart" works as usual. I started it again. Running zmupdate.pl: Database already at version 1.30.4, update aborted. I changed the ownership, but since I did a test with 777 permissions, it should't do any difference ...

My current permissions for /etc/zm/zm.conf are 740. Owner is root:www-data. I changed for 777 for a test with no success.

Some time ago I had the disk space problem too. This is not the case now.

About the keyboard, there is a difference between when the password is incorrect and this case, when the logging in message appears and then returns to login page.

I tested in Chrome, Firefox and Internet Explorer and it happens in all of them.

About the database update, I'm not sure how I could check it, but the upgrade process (via apt-get dist-upgrade) ended successfully.

Could it be php related? The newer Ubuntu uses php7, but I'm still on php5.

Hi rockedge, thanks for your help. Yes, that's the case, it reports logging in. I also tried a wrong password to confirm this diference. I forgot to mention that the problem started on two different installations at the same time: my local server and on my amazon EC2 account. That's what leads me to ...

Anyone could help with this issue?

Hello. I'm running Zoneminder in an Ubuntu Server 14.04. When I try to log in to the web interface, it returns to the same log in page. I am not sure, but it seems this started happening after a zoneminder upgrade. Some time ago, this problem happened and it was due to lack of disk space. This isn't ...