ZoneMinder Forums

Hello,

I have a ZoneMinder installation running and have the problem, that after a certain amount of time (usually one day), I'm not able to access the monitors. (Also the ZMNinja App is not able to connect)

The login in the Browers is like:
- Enter username/password
- Click login
=> Long waiting without progress (simply a white page)

I find the following log entries:
/var/log/messages:Feb 26 18:21:58 zoneminder web_php[5040]: INF [Login successful for user "admin"]
/var/log/syslog:Feb 26 18:21:58 zoneminder web_php[5040]: INF [Login successful for user "admin"]
/var/log/apache2/error.log:[Tue Feb 26 18:21:58.892776 2019] [:error] [pid 5040] [client 192.168.0.50:50400] INF [Login successful for user "admin"], referer: https://zoneminder.b2tr.de/zm/
In dmsg are a log of these lines: gspca_main: ISOC data error: [31] len=0, status=-18

About the System:
It is installed within a KVM Virtual Machine (2GB memory, 100G HDD, 2cpu-cores).
I have 3 USB-Cams as Video-Sources
It is installed on Debian9: 4.9.0-8-amd64 #1 SMP Debian 4.9.144-3.1 (2019-02-19) x86_64 GNU/Linux
ZoneMinder from package: 2:1.30.4-dmo1+deb9u2

In the log-file I do not find any clue (or maybe I'm missing a log file to look at).

Has anybody a clue for me?

You may be running out of memory depending upon the camera resolution you are using. Your database needs extra resources after it runs a while. You also should create another user besides admin with full permissions then delete admin. Also, I do not recommend running on a VM for other than testing.

The resolutions of the cameras are relatively low, but I will try a higher memory setting. Then I'll see, if the problem will resolve.

simply a white page typically means a serious error like running out of memory. The apache logs should have the answer. The memory is how much is used by php. A typical install will limit it to 128Mb. You can edit /etc/php/apache2/php.ini to change it. Look for memory_limit.

The increase of the memory resolved the problem for me.

I found the matching error log in the apache log files, which I missed to look at.

Thanks for all your help