Results 1 to 4 of 4
Hello Community
I'm having terrible problems with a VServer. I installed OpenSuse 11.0 and as far as I know the server is virtualized by xen.
Since a few days I ...
- 04-21-2009 #1Just Joined!
- Join Date
- Apr 2009
- Posts
- 4
Network Problem on a virtaulized Server
Hello Community
I'm having terrible problems with a VServer. I installed OpenSuse 11.0 and as far as I know the server is virtualized by xen.
Since a few days I can't get the network working; I got the following messages while booting:
Error Messages according to /etc/log/messagesSettings ifcfg:Code:myserver:~ # /etc/init.d/network start Hint: you may set mandatory devices in /etc/sysconfig/network/config Setting up network interfaces: lo RTNETLINK answers: Invalid argument Cannot enable interface lo. interface lo is not up lo failed eth0 RTNETLINK answers: Invalid argument Cannot enable interface eth0. interface eth0 is not up Checking for network time protocol daemon (NTPD): unused eth0 failed Setting up service network . . . . . . . . . . . . . . done.
Lately I figured out that if I start the network manually with:Code:myserver:/etc/sysconfig/network # less ifcfg-eth0 BOOTPROTO='static' BROADCAST='' ETHTOOL_OPTIONS='' IPADDR='78.143.34.138' MTU='' NAME='Xen Virtual Ethernet card 0' NETMASK='255.255.255.128' NETWORK='' REMOTE_IPADDR='' STARTMODE='auto' UNIQUE='+jsg.Sd+ykfyvlK4' USERCONTROL='no' _nm_name='bus-none-vif-0'
"ifconfig eth0.... netmask ... up"
and
"ifup eth0"
same for "lo"
it works fine.
But the network wont work automatically after a reboot or with "/etc/init.d/network restart"
The support cound't help me any further; there solution is: reinstalling the VServer and use another distribution. I'm not very happy with this suggestion, as it tooks me quit a while to set up apache, sql, a propper mail server and many more.
Does anybody have an idea where the problem could be located - or could advise me through the problem?
btw; I have to commit, that I'm still a Linux "newbie" so I'm really glad for any help.
Thanks in advance.
Cheers
lemmi
- 04-21-2009 #2
Sounds like the /etc/init.d/network script is damaged or miss configured.
Are yo sure you are booting to the xen kernel??
- 04-22-2009 #3Just Joined!
- Join Date
- Apr 2009
- Posts
- 4
- 04-22-2009 #4Just Joined!
- Join Date
- Apr 2009
- Posts
- 4
difference in /etc/init.d/network
I just checked the differences for the file /etc/init.d/network with an old version end of mars. is it worth, trying to copy the old one back?
btw, I did the changes below (without exactly knowing what i'm doiingCode:myserver:/home/lemmi # diff /etc/init.d/network /.snapshots/weekly.1/localhost/etc/init.d/network 113,115c113,115 < test "$MODE" = onboot && return 1 < test "$FIREWALL" != yes && return 2 < /sbin/SuSEfirewall2 -q status &>/dev/null || return 3 --- > test "$MODE" = onboot && return -1 > test "$FIREWALL" != yes && return -2 > /sbin/SuSEfirewall2 -q status &>/dev/null || return -3 381c381 < ipip|sit|gre|dummy) --- > ipip|sit|gre) 404,407c404 < #lemmi < # eth|tr|wlan) < eth) ;; < tr|wlam) --- > eth|tr|wlan) 517,518c514 < debug && printf " %-9s returned %s\n" $IFACE $RET || \ < printf " %-9s\n" $IFACE --- > debug && printf " %-9s returned %s\n" $IFACE $RET 577a574 > ifconfig $IFACE 192.168.178.2 netmask 255.255.255.0 broadcast 192.168.178.255 580,581c577 < debug && printf " %-9s returned %s\n" $IFACE $RET || \ < printf " %-9s\n" $IFACE --- > debug && printf " %-9s returned %s\n" $IFACE $RET 705,706c701 < debug && printf " %-9s returned %s\n" $IFACE $RET || \ < printf " %-9s\n" $IFACE --- > debug && printf " %-9s returned %s\n" $IFACE $RET 769,770c764 < debug && printf " %-9s returned %s\n" $IFACE $RET || \ < printf " %-9s\n" $IFACE --- > debug && printf " %-9s returned %s\n" $IFACE $RET 816,817c810 < debug && printf " %-9s returned %s\n" $IFACE $RET || \ < printf " %-9s\n" $IFACE --- > debug && printf " %-9s returned %s\n" $IFACE $RET

Code:< #lemmi < # eth|tr|wlan) < eth) ;; < tr|wlam)


Reply With Quote
