LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Networking
User Name
Password
Linux - Networking This forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.

Notices


Reply
  Search this Thread
Old 01-28-2014, 10:30 AM   #1
paul.proteus
LQ Newbie
 
Registered: Jan 2014
Posts: 4

Rep: Reputation: Disabled
No network after upgrade - "Failed to open statefile"


I am a Debian user.

A couple days ago, I did a dist-upgrade to move from squeeze to wheezy.

When I rebooted, I found that I had no networking capabilities.

I get a number of network-related error messages, but this one comes up first so I assume that the other problems derive from this one:

Configuring network interfaces...:
"failed to open statefile /run/network/ifstate: No such file or directory"


I'm not sure what to make of this message.

Nor do I know why there would be a difference between squeeze and wheezy in this regard.

If anyone has any ideas on how I can diagnose and fix this problem, I would be very appreciative.

Thanks.
 
Old 01-28-2014, 12:42 PM   #2
smallpond
Senior Member
 
Registered: Feb 2011
Location: Massachusetts, USA
Distribution: Fedora
Posts: 4,258

Rep: Reputation: 1309Reputation: 1309Reputation: 1309Reputation: 1309Reputation: 1309Reputation: 1309Reputation: 1309Reputation: 1309Reputation: 1309Reputation: 1309
What do you get when you run "ifconfig -a" from the command line?
 
Old 01-28-2014, 01:56 PM   #3
paul.proteus
LQ Newbie
 
Registered: Jan 2014
Posts: 4

Original Poster
Rep: Reputation: Disabled
output from ifconfig -a:

eth2 Link encap:Ethernet HWaddr 00:19:d1:6c:a4:dc
BROADCAST MULTICAST 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:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

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)
 
Old 01-29-2014, 02:18 AM   #4
paul.proteus
LQ Newbie
 
Registered: Jan 2014
Posts: 4

Original Poster
Rep: Reputation: Disabled
statefile issue resolved but now have problem with ifup

I was able to resolve the problem with statefile by using this workaround that was recommended by someone who had encountered the same problem:

by modifying /etc/init.d/networking and adding a line [ -d /run/network ] || mkdir /run/network immediately on line 53 immediately after start)

But now I still have no network on startup: the "configuring interfaces" step says that eth2 is not recognized. Same result if I run ifup manually.

However, it seems from the output below that ifconfig does recognize eth2.

Don't ifup and ifconfig get the hardware information from the same source ?

==========================================================================

Quote:
Originally Posted by paul.proteus View Post
output from ifconfig -a:

eth2 Link encap:Ethernet HWaddr 00:19:d1:6c:a4:dc
BROADCAST MULTICAST 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:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

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)
 
Old 01-29-2014, 03:48 PM   #5
paul.proteus
LQ Newbie
 
Registered: Jan 2014
Posts: 4

Original Poster
Rep: Reputation: Disabled
Resolved - problem was in the /etc/network/interfaces file

Fixed the problem.

In the /etc/network/interfaces file, I had inadvertently commented out this line:

iface eth2 inet dhcp

smallpond, thanks for your help.

===========================================


Quote:
Originally Posted by paul.proteus View Post
I was able to resolve the problem with statefile by using this workaround that was recommended by someone who had encountered the same problem:

by modifying /etc/init.d/networking and adding a line [ -d /run/network ] || mkdir /run/network immediately on line 53 immediately after start)

But now I still have no network on startup: the "configuring interfaces" step says that eth2 is not recognized. Same result if I run ifup manually.

However, it seems from the output below that ifconfig does recognize eth2.

Don't ifup and ifconfig get the hardware information from the same source ?

==========================================================================
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] Samba "oplock break failed" error - cannot open files on SMB share from network rylan76 Linux - Software 3 04-10-2013 09:29 AM
ifup:failed to open statefile linuxserv.user Debian 1 09-17-2012 07:50 AM
Failed to open statefile KaRt Linux - Newbie 2 08-02-2012 01:42 AM
Failed to overwrite statefile "Read only file-system" Bviper Linux - Networking 5 01-05-2010 08:40 PM
ssh -D "channel 6: open failed: administratively prohibited: open failed" 1veedo Linux - Networking 1 06-24-2009 10:23 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Networking

All times are GMT -5. The time now is 07:47 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration