Zentyal Forum, Linux Small Business Server
Zentyal Server => Installation and Upgrades => Topic started by: 3dge14 on March 14, 2011, 10:16:12 pm
-
Running Zentyal 2.0.16 (as of 3/11/11)
I came in Monday and I have no access to the Zentyal through the https web interface. I can only access the machine through a remote terminal. I have the server scheduled to automatically update at 20:39, could an automatic update Sat or Sun night have caused the apache module to crash?
I've tried restarting the apache module manually and checked /var/log/ebox/ebox.log and error.log to no avail. The server is used for file sharing and authenticating (these services are also still working) and I have 50+ users connecting to the shared drives.
Thanks
-
Have you tested if all modules are running?
sudo /etc/init.d/ebox module status
Where module is an ebox module name.
To get a list of installed modules, replace module by an unexistent module name and you get an error and a list of valide modules names.
Test one by one and restart any stopped module:
sudo /etc/init.d/ebox module restart
-
Thanks so much for the reply. The issue has been solved by a simple (nervous) reboot. Sorry to have wasted anyone's time. You see i had several users connected so I had to wait for after-hours.
I didn't know about that command to check the status of the modules, that was helpful. I did try to restart the apache module and it would hang in the terminal but its all back now.
Thanks again
-
Hi,
Me too, having the same problem at my Zentyal.
What I resolved this problem is to create a con job.
My con job will restart the events and logs module every morning at 7.30am.
So far everything work fine.