Problem with Networking - VENET Interfaces not Configured [message #30715] |
Wed, 04 June 2008 16:47 |
sjdean
Messages: 30 Registered: May 2008
|
Member |
|
|
Hi,
Im having a few problems with networking.
This is what I see. The VPS venet0 interface doesn't have an IP, and the venet0 doesn't appear to be bridged to the ethernet card on eth1.
The VE doesn't seem to bring up venet0 or venet0:0 (indeed why I have two - Im not sure).
Trying to restart the network services on the VE from the VPS gives:
"Bringing up interface venet0: Error, some other host already uses address 127.0.0.1."
venet0 seems assigned 127.0.0.1 while venet0:0 10.0.0.32 (my chosen ip), which means if it can't bring up venet0 then I would imagine it can't load venet0:0
Even if I change the IP of venet0 on the VE to something unused, it still gives the same error.
What this means, is that I can't ping the IP of 10.0.0.32 from either the network or the VPS.
Here's more info:
Kernel
Quote: | Linux rutsey.blargle.local 2.6.24-ovz005.1 #1 SMP Mon May 12 16:38:09 MSD 2008 i 686 athlon i386 GNU/Linux
|
Setting IP Address With VZCTL
Quote: | Adding IP address(es): 10.0.0.32
SIOCADDRT: No such device
Saved parameters for VE 102
|
VPS ifcofnig
Quote: | venet0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 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)
VPS Route
Destination Gateway Genmask Flags Metric Ref Use Iface
10.0.0.32 * 255.255.255.255 UH 0 0 0 venet0
|
VE Scripts and Files
Quote: | [root@rutsey sysconfig]# cat network
NETWORKING="yes"
GATEWAY="192.0.2.1"
HOSTNAME="collins.blargle.local"
|
lo on ve
Quote: | [root@rutsey network-scripts]# cat ifcfg-lo
DEVICE=lo
IPADDR=127.0.0.1
NETMASK=255.0.0.0
NETWORK=127.0.0.0
# If you're having problems with gated making 127.0.0.0/8 a martian,
# you can change this to something else (255.255.255.255, for example)
BROADCAST=127.255.255.255
ONBOOT=yes
NAME=loopback
|
venet0 on ve
Quote: | [root@rutsey network-scripts]# cat ifcfg-venet0
DEVICE=venet0
BOOTPROTO=static
ONBOOT=yes
IPADDR=127.0.0.1
NETMASK=255.255.255.255
BROADCAST=0.0.0.0
|
venet0:0 on ve
Quote: | [root@rutsey network-scripts]# cat ifcfg-venet0:0
DEVICE=venet0:0
ONBOOT=yes
IPADDR=10.0.0.32
NETMASK=255.255.255.255
|
Network Stop
Quote: | [root@rutsey etc]# vzctl exec 102 service network stop
Shutting down loopback interface: [ OK ]
Cannot find device "sit0"
|
Network Start
Quote: | [root@rutsey etc]# vzctl exec 102 service network start
Bringing up loopback interface: Error, some other host already uses address 127.0.0.1.
[FAILED]
Bringing up interface venet0: Error, some other host already uses address 127.0.0.1.
[FAILED]
RTNETLINK answers: File exists
RTNETLINK answers: File exists
RTNETLINK answers: File exists
RTNETLINK answers: File exists
RTNETLINK answers: File exists
RTNETLINK answers: File exists
RTNETLINK answers: File exists
RTNETLINK answers: File exists
RTNETLINK answers: File exists
Let me know if you need more.
|
Im trying the fedora-9-i386 template.
Any thoughts?
Cheers
Simon
|
|
|
|
|
|
|
|
|
|
|
|
|
Re: Problem with Networking - VENET Interfaces not Configured [message #30821 is a reply to message #30818] |
Sat, 07 June 2008 13:27 |
sjdean
Messages: 30 Registered: May 2008
|
Member |
|
|
/var/lot/messages:
Jun 7 13:40:46 rutsey kernel: CT: 101: started
Jun 7 13:40:46 rutsey kernel: CT: 102: started
Jun 7 13:40:48 rutsey kernel: CT: 103: started
Jun 7 13:40:49 rutsey kernel: CT: 101: stopped
Jun 7 13:40:56 rutsey kernel: CT: 101: started
Jun 7 13:40:59 rutsey kernel: CT: 101: stopped
(Problematic Container is 101)
Here is some further information from /var/log/vzctl.log:
2008-06-07T14:22:49+0100 vzctl : Setting CPU units: 1000
2008-06-07T14:22:49+0100 vzctl : WARNING: Settings were not saved and will be resetted to original values on next start (use --save flag)
2008-06-07T14:22:49+0100 vzctl : VE 101 : Starting VE ...
2008-06-07T14:22:49+0100 vzctl : VE 101 : VE is mounted
2008-06-07T14:22:49+0100 vzctl : VE 101 : Adding IP address(es): 10.0.0.34
2008-06-07T14:22:50+0100 vzctl : VE 101 : Warning: add_ip action script is not specified
2008-06-07T14:22:50+0100 vzctl : VE 101 : Setting CPU units: 1000
2008-06-07T14:22:50+0100 vzctl : VE 101 : Configure meminfo: 65536
2008-06-07T14:22:50+0100 vzctl : VE 101 : Warning: set_hostname action script is not specified
2008-06-07T14:22:50+0100 vzctl : VE 101 : Warning: set_dns action script is not specified
2008-06-07T14:22:50+0100 vzctl : VE 101 : VE start in progress...
2008-06-07T14:22:50+0100 vzctl : VE 102 : Starting VE ...
2008-06-07T14:22:50+0100 vzctl : VE 102 : VE is mounted
2008-06-07T14:22:50+0100 vzctl : VE 102 : Adding IP address(es): 10.0.0.32
2008-06-07T14:22:51+0100 vzctl : VE 102 : Setting CPU units: 1000
2008-06-07T14:22:51+0100 vzctl : VE 102 : Configure meminfo: 65536
2008-06-07T14:22:51+0100 vzctl : VE 102 : Set hostname: lifeson.blargle.local
2008-06-07T14:22:51+0100 vzctl : VE 102 : File resolv.conf was modified
2008-06-07T14:22:51+0100 vzctl : VE 102 : VE start in progress...
2008-06-07T14:22:51+0100 vzctl : VE 103 : Starting VE ...
2008-06-07T14:22:51+0100 vzctl : VE 103 : VE is mounted
2008-06-07T14:22:51+0100 vzctl : VE 103 : Adding IP address(es): 10.0.0.31
2008-06-07T14:22:52+0100 vzctl : VE 103 : Setting CPU units: 1000
2008-06-07T14:22:52+0100 vzctl : VE 103 : Configure meminfo: 65536
2008-06-07T14:22:52+0100 vzctl : VE 103 : Set hostname: peart.blargle.local
2008-06-07T14:22:52+0100 vzctl : VE 103 : File resolv.conf was modified
2008-06-07T14:22:52+0100 vzctl : VE 103 : VE start in progress...
2008-06-07T14:23:05+0100 vzctl : VE 101 : Starting VE ...
2008-06-07T14:23:05+0100 vzctl : VE 101 : VE is unmounted
2008-06-07T14:23:05+0100 vzctl : VE 101 : VE is mounted
2008-06-07T14:23:05+0100 vzctl : VE 101 : Adding IP address(es): 10.0.0.34
2008-06-07T14:23:05+0100 vzctl : VE 101 : Warning: add_ip action script is not specified
2008-06-07T14:23:05+0100 vzctl : VE 101 : Setting CPU units: 1000
2008-06-07T14:23:05+0100 vzctl : VE 101 : Configure meminfo: 65536
2008-06-07T14:23:05+0100 vzctl : VE 101 : Warning: set_hostname action script is not specified
2008-06-07T14:23:05+0100 vzctl : VE 101 : Warning: set_dns action script is not specified
2008-06-07T14:23:05+0100 vzctl : VE 101 : VE start in progress...
I'd be happy to get anything else you need, but I havent a clue where Im searching (that's why I ask if it's possible to increase the debugging level...).
But let me know what you need, and I'll provide.
To recap again though:
Fedora Core 8 i686 host on an AMD Athlon 64 3500 system, guest os is supposed to be Smoothwall 3.0. I took a tar of this from a system installed on KVM/Qemu and used this as my template.
I've edited as much as I can, following the instructions regarding to create a VE from a Physical Host. Perhaps there's something I've left out, but Im guessing for it to go down as quickly as it does and not log any messages in its own area, there must be something very significantly wrong. Remember, this particular guest goes down in about 2 seconds.
Cheers
Simon
[Updated on: Sat, 07 June 2008 13:29] Report message to a moderator
|
|
|
|
|
|
|
Re: Problem with Networking - VENET Interfaces not Configured [message #30837 is a reply to message #30828] |
Sun, 08 June 2008 13:09 |
sjdean
Messages: 30 Registered: May 2008
|
Member |
|
|
I've got a little more info by the way.
If I try to do a vzctl enter immediately after a vzctl start, I get:
Unable to get tty name: Bad file descriptor
smoothwall (root) / $ got signal 9
exited from VE 104
Performing an strace, I find:
[pid 22793] readlink("/proc/self/fd/5", 0x92f9fa0, 4095) = -1 ENOENT (No such file or directory)
[pid 22793] write(2, "Unable to get tty name", 22) = 22
[pid 22793] write(2, ": Bad file descriptor", 21) = 21
[pid 22793] write(2, "\n", 1) = 1
[pid 22793] ioctl(5, SNDCTL_TMR_TIMEBASE or TCGETS, {B38400 opost isig icanon echo ...}) = 0
[pid 22793] readlink("/proc/self/fd/5", 0x92f9fa0, 4095) = -1 ENOENT (No such file or directory)
There were a few devices missing from 104, console, core, fd, full, kmem, mem and port. I've generated these as best I could.
And here's some output after I managed to perform a very quick ls -al on /proc inside the VE:
smoothwall (root) / $ ls -al /proc
total 8
dr-xr-xr-x 2 root root 4096 Jun 8 13:32 ./
drwxr-xr-x 16 root root 4096 Jun 7 17:36 ../
And finally, if I try ps ax:
Error, do this: mount -t proc none /proc
Maybe there's something up with the proc folder?
Nearly got those files ready.
they work out at about 60 Meg each.
Cheers
Simon
|
|
|
Re: Problem with Networking - VENET Interfaces not Configured [message #30840 is a reply to message #30828] |
Sun, 08 June 2008 21:36 |
sjdean
Messages: 30 Registered: May 2008
|
Member |
|
|
I did some chobbling around with rc.sysinit on the guest for a bit of fun, and copied some bits from a Working Fedora 8 template I put together.
And it works now.
I think it was down to /proc not being mounted correctly.
That's resolved. Just a bit of a shame at the moment that the software doesn't seem to like me using venet0:0 devices - doesn't even show up in its screens.
Im not saying that's a flaw, and indeed, Im sure I could probably rewrite bits of their code if I can find the time.
Indeed, there's a file called interfaces.cgi which readS:
sub display_interface
{
my ( $settings, $prefix ) = @_;
my $interface = $settings{"${prefix}_DEV"};
return if ($interface !~ /eth[0123]/ );
my $ifconfig_details = &pipeopen('/sbin/ifconfig', $interface);
.
.
.
.
Place a # before that return and it brings out the details for the interface. What a load of waffle. Bad bad bad bad bad hard coded rubbish. I wonder where else there might be hard coded stuff?
Cheers
Simon
|
|
|