OpenVZ Forum: Support » Install FUSE: Networking dead in the water

Home » General » Support » Install FUSE: Networking dead in the water

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

Install FUSE: Networking dead in the water [message #15080]

Wed, 18 July 2007 07:35

wilf
Messages: 30
Registered: January 2007
Location: UK

Member

Hello everyone (again)

You must be getting tired of my endless requests for help Smile

For another customer, I want to install FUSE/sshfs. For various reasons of my own making, it was a tough install but all that is now resolved.
I did remember to add disable-kernel-module to my uses and I saw configure add --disable-kernel-module as a flag when FUSE was compiled. I am running...

ve_base # uname -a
Linux ve_base 2.6.18-028stab035 #1 SMP Tue Jul 10 12:59:23 BST 2007 x86_64 Dual Core AMD Opteron(tm) Processor 280 AuthenticAMD GNU/Linux

The instance could be pinged and could ping the outside world before the FUSE and sshfs install. Now ping reports

ve_base # vzctl enter 503
entered into VE 503
ebs / # ping 192.168.1.2
connect: Network is unreachable
ebs / # ifconfig -a
lo        Link encap:Local Loopback
          LOOPBACK  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
          BROADCAST POINTOPOINT 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)

all other instances can still see the network.

I noticed that during the emerge of FUSE, it pulled back the 2.6.20 kernel against which to compile glib. This might be a red herring, but I can't see how using 2.6.20 libs to talk to a 2.6.18 kernel is going to be too helpful.

I will be very grateful for any constructive suggestions as it is holding me back from implementing a major upgrade.

Best Regards, and thanks,

Paul.

Report message to a moderator

Re: Install FUSE: Networking dead in the water [message #15084 is a reply to message #15080]

Wed, 18 July 2007 12:01

dev
Messages: 1693
Registered: September 2005
Location: Moscow

Senior Member

does VE restart help bringing networking bringing back?
I guess something happened with routes, but not sure how FUSE could do it Smile

http://static.openvz.org/userbars/openvz-developer.png

Report message to a moderator

Re: Install FUSE: Networking dead in the water [message #15085 is a reply to message #15084]

Wed, 18 July 2007 12:16

wilf
Messages: 30
Registered: January 2007
Location: UK

Member

Hi Kirill,

Thanks for responding,

dev wrote on Wed, 18 July 2007 13:01

does VE restart help bringing networking bringing back?

Nope. Interestingly the instance take a *lot* longer to shut down now.

ve_base ~ # time vzctl stop 503
Stopping VE ...
VE was stopped
VE is unmounted

real    2m0.689s
user    0m0.017s
sys     0m0.051s

I installed syslog-ng in the hope it might help nail down where lies the problem. Here is the entire log (Hey! it's a young system Smile

)

Jul 16 16:36:24 ebs syslog-ng[3294]: syslog-ng version 1.6.11 starting
Jul 16 16:36:24 ebs syslog-ng[3294]: Changing permissions on special file /dev/tty12
Jul 16 16:36:26 ebs sshd[3667]: Server listening on :: port 22.
Jul 16 16:36:26 ebs sshd[3667]: error: Bind to port 22 on 0.0.0.0 failed: Address already in use.
Jul 16 16:36:26 ebs cron[3693]: (CRON) STARTUP (V5.0)
Jul 16 16:36:26 ebs init: no more processes left in this runlevel
Jul 16 16:40:01 ebs cron[3709]: (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons )
Jul 16 16:40:01 ebs sSMTP[3717]: Unable to locate mail
Jul 16 16:40:01 ebs sSMTP[3717]: Cannot open mail:25
Jul 16 16:40:01 ebs cron[3708]: (root) MAIL (mailed 170 bytes of output but got status 0x0001 )
Jul 16 16:40:07 ebs shutdown[3792]: shutting down for system halt
Jul 16 16:40:07 ebs init: Switching to runlevel: 0
Jul 16 16:40:08 ebs sshd[3667]: Received signal 15; terminating.
Jul 16 16:40:08 ebs syslog-ng[3294]: syslog-ng version 1.6.11 going down
Jul 16 16:40:58 ebs syslog-ng[7295]: syslog-ng version 1.6.11 starting
Jul 16 16:40:58 ebs syslog-ng[7295]: Changing permissions on special file /dev/tty12
Jul 16 16:40:59 ebs sshd[7670]: Server listening on :: port 22.
Jul 16 16:40:59 ebs sshd[7670]: error: Bind to port 22 on 0.0.0.0 failed: Address already in use.
Jul 16 16:40:59 ebs cron[7696]: (CRON) STARTUP (V5.0)
Jul 16 16:40:59 ebs init: no more processes left in this runlevel
Jul 16 16:43:24 ebs init: Trying to re-exec init
Jul 16 16:43:24 ebs init: no more processes left in this runlevel
Jul 16 16:49:39 ebs shutdown[9975]: shutting down for system halt
Jul 16 16:49:40 ebs init: Switching to runlevel: 0
Jul 16 16:49:40 ebs rc: WARNING:  Adding critical service checkroot to the boot runlevel
Jul 16 16:49:40 ebs rc: WARNING:  Adding critical service modules to the boot runlevel
Jul 16 16:49:40 ebs rc: WARNING:  Adding critical service checkfs to the boot runlevel
Jul 16 16:49:40 ebs rc: WARNING:  Adding critical service localmount to the boot runlevel
Jul 16 16:49:40 ebs rc: WARNING:  Adding critical service clock to the boot runlevel
Jul 16 16:49:40 ebs sshd[7670]: Received signal 15; terminating.
Jul 16 16:49:41 ebs rc-scripts: Cannot default to dhcp as there is no dhcp module loaded
Jul 16 16:49:41 ebs rc-scripts: No configuration for stop
Jul 16 16:49:42 ebs rc-scripts: Cannot default to dhcp as there is no dhcp module loaded
Jul 16 16:49:42 ebs rc-scripts: No configuration for stop
Jul 16 16:49:42 ebs syslog-ng[7295]: syslog-ng version 1.6.11 going down

Quote:

I guess something happened with routes, but not sure how FUSE could do it Smile

Me neither - but it seemed to install/upgrade a whole lot of stuff. Does networking use any of the routines in glib?

Best Regards, Paul.

Report message to a moderator

Re: Install FUSE: Networking dead in the water [message #15108 is a reply to message #15080]

Thu, 19 July 2007 09:00

Vasily Tarasov
Messages: 1345
Registered: January 2006

Senior Member

Hello,

You wrote:

Quote:

Now ping reports ... all other instances can still see the network.

So as far as I understand the current problem is the following: you have the VE which can't ping certain hosts? So, let's try to solve this particular problem, without taking attention on FUSe Wink

Can you post here the output of the following command on HN and in VE:

# ip a l
# ip r l
# sysctl net.ipv4.ip_forward
# iptables -L -nv
# iptables -t NAT -L -nv

Thanks you,
Vasily

Report message to a moderator

Re: Install FUSE: Networking dead in the water [message #15110 is a reply to message #15080]

Thu, 19 July 2007 09:26

wilf
Messages: 30
Registered: January 2007
Location: UK

Member

Hi Vasily,

Thanks for trying to help.

I have cerated a new instance and I am just bringing the entire gentoo instance up to date with an

emerge -DNeva world

. It has 111 packages to retrieve and build so it may be a while Smile

When it's done, I'll run the commands.

I've been talking to a colleague and we think that it may not be FUSE - it might be the installation of sshfs. This opens the possibility of still using FUSE with another fs module, so I am going to install FUSE alone and see if I still have networking.

I now suspect it has nothing to do with OpenVZ, whereas earlier I had no idea.

I'll post when I have results.

Thanks again

Best Regards, Paul.

Report message to a moderator

Re: Install FUSE: Networking dead in the water [message #15167 is a reply to message #15110]

Fri, 20 July 2007 11:11

wilf
Messages: 30
Registered: January 2007
Location: UK

Member

Hi Vasily,

Just keeping you up to date, you can see my Gentoo post - which refers to OpenVz here.

Best Regards, Paul.

Report message to a moderator

Previous Topic:	SOLVED 3Ware 8006-2LP
Next Topic:	Not able to start vps

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Mon Jul 13 17:00:50 GMT 2026

Total time taken to generate the page: 0.42185 seconds