Zentyal Forum, Linux Small Business Server
Zentyal Server => Installation and Upgrades => Topic started by: xenothan on May 01, 2010, 12:29:30 pm
-
Hi
My ebox server has been running fine for over am onth now, however this morning when I truiwed to login via the web UI I get the following error
For security reasons your session has expired due to inactivity
I then rebootred the server, and found that I couldn't even get to the https://localhost/ page.
I am unable to access the webui at all now, and am stressing that I will have to reload everything...
If anyone has some ideas as to how to go about resolving this, pelase assist.
Thanks
-
Any ideas guys?
-
Is this a clean install of 1.4, so that the console GUI is installed? If so, is that also not available? If so, did you try /etc/init.d/ebox apache restart?
-
it will be wise of you, to look into the logs and into firewall via tty, Maybe someone messed with your settings. I've had a situation like this when my coleague thinked that he is all knowing and started to noose around. From then i had the "auto login" funtion disabled on ebox
Keep us posted and best regards.
Bogdan
-
I have found from experience, that if you are using the HTTP Proxy in Transparent mode, the WebUI will become unavailable if Squid or DansGuardian goes down.
From the console, or via SSH, run "sudo /etc/init.d/ebox squid restart"
Also - patience. I have found my eBox takes a looong time to fully come up after a restart. I am hoping this will be improved in 2.0
Kind regards,
Geoff
-
Is this a clean install of 1.4, so that the console GUI is installed?
Wow! :) I'm on 1.4-1 without X. Where this funny thing is?
Upd
Or did U mean not "console" but a Xwindow-based GUI with Firefox?
-
I too have run into this - my problem is that root has run out of space. The VM only has 2.something GB assigned to it.
Making space solves the problem
-
Wow! :) I'm on 1.4-1 without X. Where this funny thing is?
Upd
Or did U mean not "console" but a Xwindow-based GUI with Firefox?
I mean the physical console (http://en.wikipedia.org/wiki/System_console)--the keyboard, mouse and display attached to the physical machine. And the GUI is the local GUI available via the console, as opposed to the remote GUI we've always had. :)
-
I too have run into this - my problem is that root has run out of space. The VM only has 2.something GB assigned to it.
Making space solves the problem
I have run into this exact same problem.
What exactly did you do to make more space?
-
I too have run into this - my problem is that root has run out of space. The VM only has 2.something GB assigned to it.
Making space solves the problem
I have run into this exact same problem.
What exactly did you do to make more space?
I finally figured it out.
/var/log/collectd.log was over 1.1 GB!!! I removed that log and restarted. All is well.
-
I too have run into this - my problem is that root has run out of space. The VM only has 2.something GB assigned to it.
Making space solves the problem
I have run into this exact same problem.
What exactly did you do to make more space?
I finally figured it out.
/var/log/collectd.log was over 1.1 GB!!! I removed that log and restarted. All is well.
Wow, that did it for me sans the reboot. I wasnt able to log in and then removed that file and it let me in without issue.
Thanks for the help!
-
So, I need to know what to do to fix this permanently. It seems like the collectd.log file doesn't have a fifo buffer, or else it's just so big that's it's filling up the root partition. Is this directly related to the Logs setup under Core->Logs->configure logs? I have events and openvpn enabled and set to purge logs older than one week.
-
Here's the permanent fix: http://trac.ebox-platform.com/changeset/18284
Just comment that line, remove the collectd.log file and /etc/init.d/ebox monitor restart
This fix will be released asap in the next 1.5 version