Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - vstryer

Pages: [1]
1
News and Announcements / Re: Usage of eBox Platform
« on: August 25, 2009, 03:08:25 pm »
I have no poll to suggest, but I cannot use ebox though I still really would like to, because it will not work on my vserver (http://forum.ebox-platform.com/index.php?topic=752); apparently I need a real physical server on a local network, no?

2
Sorry, but I refuse to give up. I hope I am not spamming people and pretty soon I will have run out of ideas. For now: does this excerpt from the installation
Code: [Select]
pkill: invalid user name: ebox
Lege Gruppe »ebox« (GID 110) an ...
Fertig.
Warning: The home dir /var/lib/ebox/ you specified already exists.
Lege Systembenutzer »ebox« (UID 106) an ...
Lege neuen Benutzer »ebox« (UID 106) mit Gruppe »ebox« an ...
Das Home-Verzeichnis »/var/lib/ebox/« existiert bereits. Kopiere keine Dateien aus »/etc/skel«.
adduser: Warning: The home directory `/var/lib/ebox/' does not belong to the user you are currently creating.
look good to anyone?

3
I tried opening a ticket about this, but got the following error:
Code: [Select]
Submission rejected as potential spam (IP <my ip> blacklisted by bsb.empty.us, sc.surbl.org) - so my activity here marks me a spammer? This just cannot get any worse :-(

4
Even though I mostly seem to be talking to myself, maybe this will lead to something. Decades of psychotherapy can't be wrong, huh?

Now, another reinstall later, this time I took ebox 1.0 from the PPA. Installed ebox and ebox-network (and the dependencies). Now when I pretend to want to enable the network module, ebox informs me what it will do, see attached screenshot.

But /etc/network/interfaces is never changed, it looks exactly the same pre- and post-chrash. So is that the problem? Maybe ebox doesn't have the necessary rights?

The Dashboard gives me a list of network devices: bond0, shaper0, dummy0, eql, eth0, gre0, ip6tnl0.

5

Interestingly, what happens when I install ebox and ebox-network from the Hardy repos (NOT the eBox PPA!) the same thing happens, even without enabling the network module!!!

I was connected via ssh and forgot to add the PPA and the last thing I can see before everything froze is:
Code: [Select]
Richte ebox-network ein (0.11.99-0ubuntu1) ...
Could PLEASE some Hero explain to me what's going on? Everybody seems so happy with ebox, but this is clearly a MAJOR bug!

6
Well, I did a reinstall. And /etc/network/interfaces was not altered by the ebox-network module, it's the same before and after enabling.

So, what else can/should I check?

7
Still, thank you for your fast reply ;-)

Since I will have to reinstall the server anyway can someone please tell me which files exactly ebox modifies upon enabling the network module, so I can do a thorough before/after comparison?

Oh, and one more thingTM: during installation of ebox and the modules (and the dependencies) I was warned multiple time the the kernel I am using does not support multicast. Could that be related somehow? I cannot imagine how, but who knows...

Btw, does the network module enable DHCP? In my setup (vserver) this of course would be not so good.

8
I did consider starting a new topic, but this is exactly my problem here, maybe I have enough patience to get it solved.

I have Ubuntu 8.04 LTS running on a vserver. I updates all the packages and installed ebox and all modules from the PPA.

After switchin on the network module (which I need for a mail server, obviously) and hitting "Save changes", the webserver never came back to life. I cannot even log on via ssh, so its something deep. I can log on now via some "rescue system" mechanism my host has installed and tell you I am running kernel 2.6.16.37-domU-v1 and this is what my /etc/networking/interfaces looks like:
Code: [Select]
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
auto eth0
iface eth0 inet static
 address <my static ip>
 netmask 255.255.255.0
 up route add -host <some ip> dev eth0
 up route add default gateway <same ip>

ebox warned me about making some changes before I hit save and I thought it was something to do with the network interfaces, but this file looks good to my mildly educated eyes. And I have not (knowingly) enabled any firewall

Up until this... well, frankly, killing experience I was most exited about ebox - I have been trying to use confixx (my host includes it for free), but had to find out that it makes more problems than it solves.

@quadrox: you didn't by chance find out what the problem was/is? Considering the amount of time that has passed it seems to be something very deep and unrelated to versions of either Ubuntu or ebox...

@javi: anything I can try? I really would love to be able to use ebox...

trying to use the hint with iptables I found out that iptables was not installed and that I cannot install it with apt-get - for I have not Internet connection :-(

Pages: [1]