Zoneminder white screen of death !!!

Forum for questions and support relating to 1.33.x development only.
Locked
Serverman2020
Posts: 2
Joined: Sat Apr 06, 2019 8:50 pm

Zoneminder white screen of death !!!

Post by Serverman2020 »

Hello all,

I’m fairly new to zoneminder and intermediate with Linux. I’ve just installed a brand new Ubuntu 18.01 server with zoneminder and I am having a very strange problem.

Originally zoneminder was working completely and I could access it via the web browser. It worked perfectly for 2 months.

Very recently when I have tried to login I am met with the WSOD. I did not change anything system (updates etc) related and use this sever for zoneminder only.

The strange part is I can still view my cameras via the zoneminder app on iOS. The cameras are still recording and I can view the videos.

Does anyone have any thoughts? Would be much appreciated.

I would like to avoid a fresh install since I’ve got all my filters and preferences sorted. Thanks
rockedge
Posts: 1173
Joined: Fri Apr 04, 2014 1:46 pm
Location: Connecticut,USA

Re: Zoneminder white screen of death !!!

Post by rockedge »

make sure /etc/zm has the correct permissions and ownership for the apache user. can you look in your php error log?
Serverman2020
Posts: 2
Joined: Sat Apr 06, 2019 8:50 pm

Re: Zoneminder white screen of death !!!

Post by Serverman2020 »

Thanks for your quick response. Upon further inspection I found that the system time was not correct. Here in the UK we entered British Summer Time, where all the clocks go forward by one hour. For some reason, my Ubuntu Install did not sync up correctly to the NTP!

Once I updated this, all systems were go!

Just out of curiosity, does anyone know why PHP/ Zoneminder fail if the system time is incorrect?
User avatar
iconnor
Posts: 2903
Joined: Fri Oct 29, 2010 1:43 am
Location: Toronto
Contact:

Re: Zoneminder white screen of death !!!

Post by iconnor »

It is supposed to complain, not give a whitescreen of death. I will have to do some testing.

Likely there was an error message logged in your apache logs.
Locked