David Meireles wrote:
Hello again,
> Hi. That apt mess happened with me when using Ubutnu Server to
> install eBox... Like they say on the website, you've got to use the
> Ubuntu Alternate CD for the "regular" distro.
Can't really do that for OpenVZ, because OpenVZ uses templates for
VPS-creation.
> What happens if you run "dpkg-reconfigure ebox-*"?
That actually messes up network-settings :(
(I converted ebox-network to a rpm-package, then installed it,
then manually installed ebox-samba deb, and then eventually
apt-get -f install did finish without errors)
# ifconfig
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
venet0 Link encap:UNSPEC HWaddr
00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet addr:127.0.0.1 P-t-P:127.0.0.1 Bcast:0.0.0.0
Mask:255.255.255.255
UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1
RX packets:1956 errors:0 dropped:0 overruns:0 frame:0
TX packets:2128 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:297282 (290.3 KB) TX bytes:1237545 (1.1 MB)
venet0 should be an 192.168.1.* address, which it had.
Anyway, i wonder about all the error-messages :
2008/11/04 13:27:58 ERROR> Error.pm:182 Error::throw - /usr/bin/sudo -p
sudo: status ebox.smbd 2> /var/lib/ebox/tmp/stderr raised the following
sudo error: sudo: status: command not found
I've seen that error before months ago.
2008/11/04 13:29:07 ERROR> Error.pm:182 Error::throw - /usr/bin/sudo -p
sudo: /sbin/modprobe 8021q 2> /var/lib/ebox/tmp/stderr raised the
following sudo error: sudo: /sbin/modprobe: command not found
2008/11/04 13:29:08 ERROR> Sudo.pm:185 EBox::Sudo::_rootError - root
command /sbin/vconfig set_name_type VLAN_PLUS_VID_NO_PAD failed.
Error output: WARNING: Could not open /proc/net/vlan/config. Maybe you
need to load the 8021q module, or maybe you are not using PROCFS??
ERROR: trying to set name type for VLAN subsystem, error: Package not
installed
What i find problematic with eBox usage, is that it tries to control all the
network-settings, even before the admin does configure anything!
That's exactly what i am not looking for.
I've had enough grey hairs from a server running LDAP (set up by someone
else) where any problems with LDAP leads to a situation of either :
- cannot log in at all
- having to wait 10 minutes before the boot-process is finished
I like eBox for the easy interface it gives for setting up a PDC inside
a VPS
(so i have full control on the host itself),
that means that my 2 other co-workers could
also add and delete users, without having to give them an ssh-account
with sudo and command-line scripts to work with.
Of course i could test eBox on a stand-alone server, but that makes
things much less flexible. With OpenVZ in use on 2 or more servers
it's relatively easy to move things around. When 1 server would break
down it's pretty easy to have things running again on the other server.
But i think i'll try Mandrive MC again, http://mds.mandriva.org/
and also test Fedora Directory Server.
I did try Zivios, pretty new, looks very good
http://www.zivios.org/screenshots/index
but it's in early stages of development, still promising though!
Kind regards,
A.
_______________________________________________
Ebox-user mailing list
[email protected]
https://lists.warp.es/mailman/listinfo/ebox-user
