ebox webinterface not working properly

Bug #521453 reported by stop
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ebox (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: ebox

Ebox does not seem to be working correctly in lucid.
The system seems up and running but the webinterface is not working properly. A lot of links are not responsive (they do nothing), It is not possible to change any setting or save anyting

ProblemType: Bug
Architecture: amd64
Date: Sat Feb 13 19:17:06 2010
DistroRelease: Ubuntu 10.04
InstallationMedia: Ubuntu-Server 10.04 "Lucid Lynx" - Alpha amd64 (20100114)
Package: ebox 1.3.5-0ubuntu2
PackageArchitecture: all
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-13.18-server
SourcePackage: ebox
Uname: Linux 2.6.32-13-server x86_64

Revision history for this message
stop (whoopwhoop) wrote :
Revision history for this message
stop (whoopwhoop) wrote :

Nearly all of it got fixed with today's updates (so that's good). Only the user corner is not functioning: logging in at https://name:8888 will give you: Internal Server Error...

Revision history for this message
Todor Andreev (toshko3) wrote :

Same to me: The user corner is not functioning: logging in at https://name:8888 will give you: Internal Server Error...
Also the WAN Failover does not bring up the default gateway after it has failed and then succeeded back.

Revision history for this message
vroetman (vroetman) wrote :

regarding the user corner problem, I found that if I delete the contents of /var/lib/ebox-usercorner/sids then it works again.

When a user logs out, their file in that space is usually deleted. I'm not exactly sure the problem, but it was giving me errors (in /var/log/ebox-usercorner/error.log) about
Could not open /var/lib/ebox-usercorner/sids/user_name
where the file user_name (and some others) were remaining there. Perhaps the users didn't log out and the server was reset or something.

Revision history for this message
dino99 (9d9) wrote :

Closing that outdated report as EOL has been reached long time ago

Changed in ebox (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.