| View previous topic :: View next topic |
| Author |
Message |
schmandel
n00b
Joined: 30 Aug 2006
Posts: 13
|
 Posted: Wed Aug 30, 2006 3:00 pm Post subject: Cannot start or stop net.eth* services on running server |
 |
|
I customarily selectively apply emerge updates daily after testing them on a workstation box of similar hardware ( Tyan Dual Athlon motherboards ).
Total score today is one box down, one still up but will fail if rebooted.
Both boxes are now giving the following message when an attempt to start or stop the net.eth* services is made.
/etc/init.d/net.eth3: line 34: /lib/rcscripts/net.modules.d/helpers.d/functions: No such file or directory
* Stopping
* no interface module has been loaded
The workstation is now completely off the network due to reboot. The server is still running. The issue was not detected until I attempted to stop/start one of the 4 interfaces.
Line 34 in net.lo is:
source ${MODULES_DIR}/helpers.d/functions
The fully expanded directory is
/lib/rcscripts/net.modules.d/helpers.d
This directory is empty on both boxes.
My backups prior to 8/26/2006 show files in the directory. I have restored and replaced just these files:
lnx3 helpers.d # pwd
/lib/rcscripts/net.modules.d/helpers.d
lnx3 helpers.d # ll
total 32
-rw-r--r-- 1 root root 4454 Jul 13 23:39 config-system
-rwxr-xr-x 1 root root 258 Jul 13 23:39 dhclient-ifconfig
-rwxr-xr-x 1 root root 258 Jul 13 23:39 dhclient-iproute2
-rwxr-xr-x 1 root root 1396 Jul 13 23:39 dhclient-udhcpc-wrapper
-rw-r--r-- 1 root root 2282 Jul 13 23:39 functions
-rwxr-xr-x 1 root root 2042 Jul 13 23:39 udhcpc-ifconfig
-rwxr-xr-x 1 root root 2180 Jul 13 23:39 udhcpc-iproute2
lnx3 helpers.d #
I now get a different message:
Now
* Stopping
* no interface module has been loaded
I believe this may have something to do with a recent baselayout update on 8/26, but I'm guessing.
HELP! If I lose my server I lose a lot. The workstation can be worked around, that is why I use it for testing updates first. I did not recycle interfaces or reboot as part of my testing, hence I didn't detect the issue until I rebooted the workstation, it had the first error message as well in the startup sequence.
[/glep] |
|
| Back to top |
|
 |
wynn
Advocate
Joined: 01 Apr 2005
Posts: 2421
Location: UK
|
| Posted: Wed Aug 30, 2006 3:09 pm Post subject: |
|
|
Yes, this is the baselayout upgrade from 1.11.15-r3 to 1.24.4-rX.
This error seems usually to be due to having the /etc/init.d/net.ethX not symlinks to /etc/init.d/net.lo. If you delete /etc/init.d/net.eth* and replace each one by a symlink to net.lo things should work again.
Apparently (according to Uberlord, a baselayout developer) net.eth* should have been symlinks for some time now.
_________________
The avatar is jorma, a "duck" from "Elephants Dream": the film and all the production materials have been made available under a Creative Commons Attribution 2.5 License, see orange.blender.org for details. |
|
| Back to top |
|
|
schmandel
n00b
Joined: 30 Aug 2006
Posts: 13
|
| Posted: Wed Aug 30, 2006 11:36 pm Post subject: |
|
|
Yes, I saw that "Resolution" elsewhere here. It doesn't apply here. All devices are symlinks to net.lo .
Judging by what happened to the (nearly) identically configured test workstation I used, I am totally screwed if this server goes down, as I will have no network at all. Not even net.lo came up on the workstation.
It seems like every time I apply baselayout updates it turns into a bughunt, and the last time I checked, the Linux platform is not supposed to work just like Windows doesn't. 
So, if anyone has any ideas I would be welcome. I'm not far from a full restore of the server, and we all know that's not a good place to be.
We have a thunderstorm outside right now. Perhaps my next post may come by means of a fresh install of Debian/Ubuntu, more likely I'll go to tape and and put the search for alternatives on my To Do list.
I actually moved away from Fedora over a year ago because of the bifurcation of the Redhat products into a production-grade manageable version and a "We can test anything we want on the people who do free downloads, screw 'em" version, A.K.A. Fedora. 
BTW, if anyone has any ideas other than a full restore I would really appreciate hearing from you. Thanks for your consideration. |
|
| Back to top |
|
|
wynn
Advocate
Joined: 01 Apr 2005
Posts: 2421
Location: UK
|
| Posted: Thu Aug 31, 2006 2:06 pm Post subject: |
|
|
| Quote: | Yes, I saw that "Resolution" elsewhere here. It doesn't apply here. All devices are symlinks to net.lo
...
Line 34 in net.lo is:
source ${MODULES_DIR}/helpers.d/functions |
Having got the hors d'oevres out of the way, let's get on to the main course 
/etc/init.d/net.lo here (sys-apps/baselayout-1.12.4-r7) doesn't have this line in it at all. The lines around 34 are | Code: | # Define where our modules are
MODULES_DIR="${svclib}/net"
# Make some wrappers to fudge after/before/need/use depend flags.
# These are callbacks so MODULE will be set.
after() {
eval "${MODULE}_after() { echo \"$*\"; }"
}
before() {
eval "${MODULE}_before() { echo \"$*\"; }"
}
need() {
eval "${MODULE}_need() { echo \"$*\"; }"
}
|
so I think your baselayout upgrade is incomplete. Would you like to emerge sys-apps/baselayout again and then check net.lo â the timestamp of net.lo before and after the emerge will probably be enough to see if it has been replaced.
_________________
The avatar is jorma, a "duck" from "Elephants Dream": the film and all the production materials have been made available under a Creative Commons Attribution 2.5 License, see orange.blender.org for details. |
|
| Back to top |
|
|
schmandel
n00b
Joined: 30 Aug 2006
Posts: 13
|
| Posted: Fri Sep 01, 2006 4:48 am Post subject: |
|
|
Yes, tried that as well, but, here's the resolution:
I Googled around until I found a copy of net.lo that was different that mine and smelled newer. Replaced the file, case closed.
Funky? - Yes. Not recommended? - Yes. Better than doing a restore from 2006/08/25? - heck yeah!
Why etc-update didn't update net.lo on two machines I'll never know, or at least I'm unlikely to take the time to figure it out.
If this was one system, I could safely assume I fat-fingered etc-update, but to blow this on both the test desktop machine and the server is more than I could imagine doing, particularly given I fear and respect etc-update, and know which config files I have localized vs. which I use in the generic form.
Thanks everyone for all the help on this, I was getting a bit stressed after I realized that if the server went down for any reason I would lose all the network connectivity, and this is a busy place with 4 interfaces 
Linux rocks! baselayout updates scare me  |
|
| Back to top |
|
|
sr66
n00b
Joined: 30 May 2005
Posts: 56
|
| Posted: Sat Sep 02, 2006 11:13 pm Post subject: |
|
|
I had the same problem.
I moved net.lo to net.lo.old and then reemerged baselayout and everything got fixed.
The file size of net.lo became bigger.
When I remerged the emerge process suggested that I run this command
/bin/ls /etc/init.d/net.* | grep -v '/net.lo$' | xargs -n1 ln -sfvn net.lo
This might be because net.lo.old was not symlinked? don't know....
everything is working fine now. Thanks Wynn! |
|
| Back to top |
|
|
wynn
Advocate
Joined: 01 Apr 2005
Posts: 2421
Location: UK
|
| Posted: Sun Sep 03, 2006 9:59 am Post subject: |
|
|
| Quote: | | Code: | | /bin/ls /etc/init.d/net.* | grep -v '/net.lo$' | xargs -n1 ln -sfvn net.lo |
|
Very interesting, you can learn a lot about Bash in these forums.
| Code: | | /bin/ls /etc/init.d/net.* |
lists all the entries in /etc/init.d beginning "net." â using "/bin/ls" bypasses any aliases (and colouring?) that you may have for "ls".
removes the "net.lo" entry (strictly, the line ending ".../net.lo")
The result of all this is then passed to "ln" to create a symlink: "-sf" creates a symlink and overwrites any existing file with the same name, "v" is our old friend in need, verbose, which shows the name of the file before linking it. "n" I think I shall have to leave to you to read up in the ln manpage â you will see why if you do. "xargs -n1" runs the "ln" command once with each entry in the list of entries passed from the preceding two commands.
_________________
The avatar is jorma, a "duck" from "Elephants Dream": the film and all the production materials have been made available under a Creative Commons Attribution 2.5 License, see orange.blender.org for details. |
|
| Back to top |
|
|
Shockwaver
Tux's lil' helper
Joined: 04 Jul 2005
Posts: 123
|
| Posted: Sun Sep 03, 2006 11:52 am Post subject: |
|
|
Sorry to up a so old post but i got the same problem .. and.. i'm a noob 
Problem is that with this issue my only net interface is down and i'm not able to bring it up (..../net.eth0 start).. it doesn't even work ifconfig.. it means that i cannot re-emerge baselayout.. i even got other errors during boot all linked to net.modules.. what should i do? |
|
| Back to top |
|
|
ova
Retired Dev
Joined: 06 Nov 2003
Posts: 120
Location: Russia, Moscow
|
| Posted: Sun Sep 03, 2006 2:10 pm Post subject: |
|
|
| Shockwaver wrote: |
Problem is that with this issue my only net interface is down and i'm not able to bring it up (..../net.eth0 start).. it doesn't even work ifconfig... what should i do? |
Check what baselayout versions you have in /usr/portage/distfiles:
| Code: |
ls /usr/portage/distfiles/baselayout*
|
and try to install that version. If you do not any baselayout there then you have to configure networking manually with ifconfig. |
|
| Back to top |
|
|
|
Networking & Security
