The script (EBox.pm) is referring to user ebox and group ebox, that do not exist yet.
I also found that the ebox user needs to control the /var/log/ebox directory (chown -R ebox:ebox /var/log/ebox). After fixing those, the startup script fails with the "apache is not a valid module name" error. Kinda funny, since the startup script seems to remove the apache module from the list, and then pushes it at the end. Resulting in the apache is not a valid module name. Remarking the push apache in the startup script at least ensures ebox installs, but the the ebox-network module hangs with an "Can't call method "setIfaceDHCP" on an undefined value at /usr/share/ebox-network /ebox-netcfg-import line 105, <FD> line 9." Playing around with that file, only produces errors somewhere else, so it seems that the whole network configuration has not been set correctly. (I hardcoded eth0 in the ebox-netcfg-import.pm on line 105 to run into errors in the setIfaceDHCP method in the Network.pm since $self->ifaceIsExternal($name) has not been defined). Hope this helps. -- eBox configure fails https://bugs.launchpad.net/bugs/127353 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
