View previous topic :: View next topic |
Author |
Message |
GFCCAE6xF Apprentice
Joined: 06 Aug 2012 Posts: 295
|
Posted: Sat Jul 27, 2013 1:26 pm Post subject: |
|
|
@Fred Krogh
Have you installed a network application to replace the *.lo which is built in to OpenRC when using oldnet?
There are a few available, most popular are (imo) net-misc/dhcpcd and net-misc/networkmanager. |
|
Back to top |
|
|
Fred Krogh Veteran
Joined: 07 Feb 2005 Posts: 1036 Location: Tujunga, CA
|
Posted: Sat Jul 27, 2013 3:07 pm Post subject: |
|
|
Looks like it's only xdm that starts. NetworkManager exits with error code 1. systemctl status NetworkManager gives Quote: | NetworkManager.service - Network Manager
Loaded: loaded (/usr/lib64/systemd/system/NetworkManager.service; enabled)
Active: active (running) since Sat 2013-07-27 14:27:53 PDT; 4min 6s ago
Main PID: 1463 (NetworkManager)
CGroup: /system.slice/NetworkManager.service
└─1463 /usr/sbin/NetworkManager --no-daemon
Jul 27 14:30:05 mon1 NetworkManager[1463]: <info> Activation (eth2) Stage 4 of 5 (IPv4 Configure Timeout) complete.
Jul 27 14:30:05 mon1 NetworkManager[1463]: <info> Activation (eth1) Stage 4 of 5 (IPv4 Configure Timeout) started...
Jul 27 14:30:05 mon1 NetworkManager[1463]: <info> (eth1): device state change: ip-config -> failed (reason 'ip-config-unavailable') [70 120 5]
Jul 27 14:30:05 mon1 NetworkManager[1463]: <info> Marking connection 'Wired connection 4' invalid.
Jul 27 14:30:05 mon1 NetworkManager[1463]: <warn> Activation (eth1) failed for connection 'Wired connection 4'
Jul 27 14:30:05 mon1 NetworkManager[1463]: <info> Activation (eth1) Stage 4 of 5 (IPv4 Configure Timeout) complete.
Jul 27 14:30:05 mon1 NetworkManager[1463]: <info> (eth2): device state change: failed -> disconnected (reason 'none') [120 30 0]
Jul 27 14:30:05 mon1 NetworkManager[1463]: <info> (eth2): deactivating device (reason 'none') [0]
Jul 27 14:30:05 mon1 NetworkManager[1463]: <info> (eth1): device state change: failed -> disconnected (reason 'none') [120 30 0]
Jul 27 14:30:05 mon1 NetworkManager[1463]: <info> (eth1): deactivating device (reason 'none') [0] | Apache2 fails not recognizing that fastcgi is being used. I have the usual in /etc/conf.d/apache2 do evidently systemd needs something more.
I have added a file /usr/lib64/systemd/system/mysqld.service Quote: | [Unit]
Description=mySQL Server
After=network.target
[Service]
Type=simple
ExecStart=/usr/sbin/mysqld --defaults-file=/etc/mysql/my.cnf --basedir=/usr --datadir=/var/lib/mysql --pid-file=/var/run/mysqld/mysqld.pid --socket=/var/run/mysqld/mysqld.sock
ExecStop=/bin/kill -15 $MAINPID
PIDFile=/var/run/mysqld/mysql.pid
Restart=always
[Install]
WantedBy=multi-user.target | which I found on the internet. systrl status mysqld gives Quote: | mysqld.service - mySQL Server
Loaded: loaded (/usr/lib64/systemd/system/mysqld.service; enabled)
Active: failed (Result: start-limit) since Sat 2013-07-27 14:27:54 PDT; 4min 42s ago
Process: 1639 ExecStop=/bin/kill -15 $MAINPID (code=exited, status=1/FAILURE)
Process: 1636 ExecStart=/usr/sbin/mysqld --defaults-file=/etc/mysql/my.cnf --basedir=/usr --datadir=/var/lib/mysql --pid-file=/var/run/mysqld/mysqld.pid --socket=/var/run/mysqld/mysqld.sock (code=exited, status=1/FAILURE)
Main PID: 1636 (code=exited, status=1/FAILURE)
CGroup: /system.slice/mysqld.service
Jul 27 14:27:54 mon1 systemd[1]: mysqld.service: control process exited, code=exited status=1
Jul 27 14:27:54 mon1 systemd[1]: Unit mysqld.service entered failed state.
Jul 27 14:27:54 mon1 systemd[1]: mysqld.service holdoff time over, scheduling restart.
Jul 27 14:27:54 mon1 systemd[1]: Stopping mySQL Server...
Jul 27 14:27:54 mon1 systemd[1]: Starting mySQL Server...
Jul 27 14:27:54 mon1 systemd[1]: mysqld.service start request repeated too quickly, refusing to start.
Jul 27 14:27:54 mon1 systemd[1]: Failed to start mySQL Server.
Jul 27 14:27:54 mon1 systemd[1]: Unit mysqld.service entered failed state | In this case the datadir is not correct. It is defined in /etc/mysql/my.cnf so evidently systemd needs something to look here? Perhaps this and the fastcgi problem are in reality the same problem? |
|
Back to top |
|
|
Fred Krogh Veteran
Joined: 07 Feb 2005 Posts: 1036 Location: Tujunga, CA
|
Posted: Sat Jul 27, 2013 3:43 pm Post subject: |
|
|
rorgoroth -- I'm not sure I understand. I have enabled NetworkManager.service and networkmanager is installed.. If this is not the sort of thing you are thinking of could you provice a little more detail? Thanks |
|
Back to top |
|
|
Fred Krogh Veteran
Joined: 07 Feb 2005 Posts: 1036 Location: Tujunga, CA
|
Posted: Sat Jul 27, 2013 4:26 pm Post subject: |
|
|
I just ran udevadm test /block/sda, the result shows lots of rules files being read from /lib64/udev/rules.d/*, but /lib64 does not even exist on my machine, unless preceded by /usr. It seems peculiar to me that there is not reference to /etc/udev/rules.d. |
|
Back to top |
|
|
Fred Krogh Veteran
Joined: 07 Feb 2005 Posts: 1036 Location: Tujunga, CA
|
Posted: Sat Jul 27, 2013 5:30 pm Post subject: |
|
|
Another clue?? When I run udevadm test net, at the end it says unable to open device 'sysnet'. I have no idea what this could mean. |
|
Back to top |
|
|
Fred Krogh Veteran
Joined: 07 Feb 2005 Posts: 1036 Location: Tujunga, CA
|
Posted: Sat Jul 27, 2013 6:12 pm Post subject: |
|
|
I'm running out of stupid things to try. I noted that what I wanted to call net0, was called emp4s0. And for net1, and net2, the 4 changed to 5 and 6. So I tried using these names throughout /etc in place of the net? names I was trying to use. This had no effect on results. I think I must be doing something really dumb, but I'm blind to what it might be. I just ran udevadm test net, and this time the /etc/udev/rules.d showed up. But still getting the error "unable to open device `/sysnet'. That now shows up in a google search now, but it is from my earlier posted message!! |
|
Back to top |
|
|
Fred Krogh Veteran
Joined: 07 Feb 2005 Posts: 1036 Location: Tujunga, CA
|
Posted: Sat Jul 27, 2013 8:34 pm Post subject: |
|
|
Signs of progress, but still no outside internet. It took me forever to see that I had () where I should have had {}. My only entry in /etc/udev/rules.d is 81-persistent-net.rules which contains Quote: | SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:e0:4c:68:e4:0c". NAME="net0"
SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:e0:4c:68:e5:12", NAME="net1"
SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:e0:4c:68:e4:0d", NAME="net2" | Now ifconfig shows[ (emp11s0 and em7s0 not shown as they shouldn't matter) Quote: | enp4s0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether 00:e0:4c:68:e4:0c txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
loop txqueuelen 0 (Local Loopback)
RX packets 184 bytes 5915 (5.7 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 184 bytes 5915 (5.7 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
net1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.2.3 netmask 255.255.255.0 broadcast 192.168.2.255
ether 00:e0:4c:68:e5:12 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
net2: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.0.3 netmask 255.255.255.0 broadcast 192.168.0.255
ether 00:e0:4c:68:e4:0d txqueuelen 1000 (Ethernet)
RX packets 42 bytes 2520 (2.4 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 3 bytes 126 (126.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 | The only problem is enp4s0 which should be net0. I'm hoping someone has an idea how this could happen. |
|
Back to top |
|
|
Fred Krogh Veteran
Joined: 07 Feb 2005 Posts: 1036 Location: Tujunga, CA
|
Posted: Sat Jul 27, 2013 9:09 pm Post subject: |
|
|
I've tried changing net0 to netx and putting it last in 81--persistent-net.rules, and this gave no difference. I suspect that perhaps I've changed an eth0 to netx someplace in /etc where I should not have, or perhaps missed a place in some other directory where it should have been changed? |
|
Back to top |
|
|
trigggl Apprentice
Joined: 26 Aug 2007 Posts: 250 Location: Arkansas
|
Posted: Sat Jul 27, 2013 9:22 pm Post subject: |
|
|
Don't know if this is hijacking or off-topic, but the news item "2013-03-29-udev-upgrade" scared me into masking >=sys-fs/udev-200 until the smoke clears and I'm reasonably confident I can upgrade all of my systems without complication or network problems. I've been happily computing with sys-fs/udev-197-r8, but now there's an update to virtual/udev to 200. The update is now trying to replace udev-197 with systemd-204. Will it be more complicated for me to allow systemd to install or just unmask the udev upgrade? Will I have the same complications with systemd as I will have with udev?
Is there some actual benefit to all these changes?
I'm going to go ahead and use my daughter's computer as the guinea pig for a udev update. Will hold off on a systemd test for now. _________________ Greg |
|
Back to top |
|
|
Fred Krogh Veteran
Joined: 07 Feb 2005 Posts: 1036 Location: Tujunga, CA
|
Posted: Sat Jul 27, 2013 9:50 pm Post subject: |
|
|
Speaking of hijacking, I would never have used this thread had I realized all the prolbems I wold have. I've moved my questions about getting applications started to https://forums.gentoo.org/viewtopic-p-7359174.html#7359174. I'm still hoping someone will have some ideas for how 2 out of 3 interface names get set, but one doesn't. |
|
Back to top |
|
|
jburns Veteran
Joined: 18 Jan 2007 Posts: 1214 Location: Massachusetts USA
|
Posted: Sat Jul 27, 2013 10:54 pm Post subject: |
|
|
Status of my systemd update
The following commands gave me a working deskyop Code: | systemctl disable xdm.service
systemctl start kdm |
The following command should start kde on the next boot Code: | systemctl enable kdm.service |
The following commands gave me a working network connection using networkmanager Code: | systemctl start NetworkManager-dispatcher
systemctl enable NetworkManager-dispatcher
systemctl enable NetworkManager.service
systemctl start NetworkManager.service |
|
|
Back to top |
|
|
Fred Krogh Veteran
Joined: 07 Feb 2005 Posts: 1036 Location: Tujunga, CA
|
Posted: Sun Jul 28, 2013 2:12 am Post subject: |
|
|
I tried your sequence and get exactly the same result. I suspect most don't have more than one network card. I can't imagine why 2 work and one does not. |
|
Back to top |
|
|
miket Guru
Joined: 28 Apr 2007 Posts: 488 Location: Gainesville, FL, USA
|
Posted: Sun Jul 28, 2013 6:08 am Post subject: |
|
|
trigggl wrote: | Is there some actual benefit to all these changes?
I'm going to go ahead and use my daughter's computer as the guinea pig for a udev update. Will hold off on a systemd test for now. |
I set up a cheapo computer just to try all this stuff out. I set it up with early userspace to mount a root LVM partition. AII of the device drivers are compiled into the kernel. This makes for a very fast boot and no race conditions that might arise in the interaction of module loading and the enumeration of network interfaces. On this same computer I can confirm that eudev works very well. I get my truly predictable interface name of eth0 and flawless mounting of a separate /usr partition. |
|
Back to top |
|
|
devsk Advocate
Joined: 24 Oct 2003 Posts: 2995 Location: Bay Area, CA
|
Posted: Sun Jul 28, 2013 6:18 am Post subject: |
|
|
Wow! This seems like a big fail. How the heck devs release the packages which break someone's boot or network setup without any kind of documentation or announcements? At least I haven't seen any news about udev and systemd on 'eselect' and what a gentoo user should do to get a sane working system.
I don't care about the politics. I just need a working system. So, just remove udev and emerge'ing systemd resolves all issues? What happens to openrc boot scripts? Do they go away? Does systemd provide a openrc plugin? Does it work with it? |
|
Back to top |
|
|
Fred Krogh Veteran
Joined: 07 Feb 2005 Posts: 1036 Location: Tujunga, CA
|
Posted: Sun Jul 28, 2013 5:30 pm Post subject: Internet now working |
|
|
I posted the stuff below in the wrong thread thanks to working on a small screen with lots of windows open.
Good news! I finally have a working internet, albeit without shorewall, apache or mysql working. The problem (at least most of it) was having a "." where I should have had a "," in my 81-persistent-net.rules. I hang my head in shame. I've started another thread concerning the problems with applications. Without a firewall I'm still not using my main machine (hence no email). For now I'm leaving this thread. Apologies for wasting so much space on what should not have been that hard to resolve. I fear that systemd is still not something I can get working due to the applications I need. |
|
Back to top |
|
|
GFCCAE6xF Apprentice
Joined: 06 Aug 2012 Posts: 295
|
Posted: Sun Jul 28, 2013 5:58 pm Post subject: Re: Internet now working |
|
|
Fred Krogh wrote: | I fear that systemd is still not something I can get working due to the applications I need. |
Help fix them by finding and testing service files, or at the very least report or bump bugs asking for status updates because they work fine and are supplied in every other distro. They should work here too, you have to help out a little sometimes
Also, about the network thing, I thought I read that you was trying to use the built in openrc network with systemd, my bad |
|
Back to top |
|
|
Fred Krogh Veteran
Joined: 07 Feb 2005 Posts: 1036 Location: Tujunga, CA
|
Posted: Sun Jul 28, 2013 6:16 pm Post subject: |
|
|
I thought I was done here, but on a reboot all the network cards were mixed up as was supposed to be a problem without persistent net rules, but had never happened to me before. I changed 81-persistent-net.rules to 11-persistent-net.rules and it came up correctly. I have no idea what the correct value should be, and at this point whether that is a permanent fix. |
|
Back to top |
|
|
devsk Advocate
Joined: 24 Oct 2003 Posts: 2995 Location: Bay Area, CA
|
Posted: Sun Jul 28, 2013 6:55 pm Post subject: |
|
|
Is systemd also replacing openrc? Why is systemd not blocking openrc and vice versa if so?
If not, can I continue to use openrc for system boot after systemd is installed? How do I make sure that that part works without an unbootable system needing livecd rescue? |
|
Back to top |
|
|
trigggl Apprentice
Joined: 26 Aug 2007 Posts: 250 Location: Arkansas
|
Posted: Sun Jul 28, 2013 7:23 pm Post subject: |
|
|
The upgrade to the latest udev went surprisingly well on my daughter's computer. I went ahead and upgraded the other two computers while I was at it. I guess this will simplify adding a second network card or wifi once I get used to it.
The news items and help websites are so verbose it makes it sound scary, but most of us just need to backup/delete the persistent net rules, find out what our device is going to be called and update configs and scripts accordingly. For most people, just update /etc/conf.d/net and make the sym link to the new device name. If you have the old name in the default runlevel, delete it and if you're using openrc, you don't even need to add the new one. As long as you have the sym link correct and, if applicable, the net file updated, it will be started. You can get it all setup before rebooting. This page makes it pretty straightforward:
http://wiki.gentoo.org/wiki/Udev/upgrade
You can always print it out before rebooting. It's no harder than following the handbook to install.
Since I unmasked the latest udev, systemd wasn't auto selected and not an issue. _________________ Greg |
|
Back to top |
|
|
Fred Krogh Veteran
Joined: 07 Feb 2005 Posts: 1036 Location: Tujunga, CA
|
Posted: Sun Jul 28, 2013 11:24 pm Post subject: |
|
|
I'm back, but not booting with systemd anymore. I tried booting about 5 times getting my network cards assigned to different ports each time. Ifconfig showed it was using my net0, net1, net2, etc. names, but there was nothing persistent about them. I don't give up easily, but this together with not even being able to get shorewall working was enough to do it. |
|
Back to top |
|
|
devsk Advocate
Joined: 24 Oct 2003 Posts: 2995 Location: Bay Area, CA
|
Posted: Mon Jul 29, 2013 5:56 am Post subject: |
|
|
trigggl wrote: | The upgrade to the latest udev went surprisingly well on my daughter's computer. I went ahead and upgraded the other two computers while I was at it. I guess this will simplify adding a second network card or wifi once I get used to it.
The news items and help websites are so verbose it makes it sound scary, but most of us just need to backup/delete the persistent net rules, find out what our device is going to be called and update configs and scripts accordingly. For most people, just update /etc/conf.d/net and make the sym link to the new device name. If you have the old name in the default runlevel, delete it and if you're using openrc, you don't even need to add the new one. As long as you have the sym link correct and, if applicable, the net file updated, it will be started. You can get it all setup before rebooting. This page makes it pretty straightforward:
http://wiki.gentoo.org/wiki/Udev/upgrade
You can always print it out before rebooting. It's no harder than following the handbook to install.
Since I unmasked the latest udev, systemd wasn't auto selected and not an issue. | That does not address systemd vs. openrc issue at all. Does anybody know what am I supposed to do with respect to which of these two will boot my system and how they inter-operate? |
|
Back to top |
|
|
trigggl Apprentice
Joined: 26 Aug 2007 Posts: 250 Location: Arkansas
|
Posted: Mon Jul 29, 2013 1:13 pm Post subject: |
|
|
devsk wrote: | trigggl wrote: | The upgrade to the latest udev went surprisingly well on my daughter's computer. I went ahead and upgraded the other two computers while I was at it. I guess this will simplify adding a second network card or wifi once I get used to it.
The news items and help websites are so verbose it makes it sound scary, but most of us just need to backup/delete the persistent net rules, find out what our device is going to be called and update configs and scripts accordingly. For most people, just update /etc/conf.d/net and make the sym link to the new device name. If you have the old name in the default runlevel, delete it and if you're using openrc, you don't even need to add the new one. As long as you have the sym link correct and, if applicable, the net file updated, it will be started. You can get it all setup before rebooting. This page makes it pretty straightforward:
http://wiki.gentoo.org/wiki/Udev/upgrade
You can always print it out before rebooting. It's no harder than following the handbook to install.
Since I unmasked the latest udev, systemd wasn't auto selected and not an issue. | That does not address systemd vs. openrc issue at all. Does anybody know what am I supposed to do with respect to which of these two will boot my system and how they inter-operate? |
It did however address the issue that the OP was facing. _________________ Greg |
|
Back to top |
|
|
ulenrich Veteran
Joined: 10 Oct 2010 Posts: 1480
|
Posted: Mon Jul 29, 2013 2:29 pm Post subject: |
|
|
Fred Krogh wrote: | Quote: | SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:e0:4c:68:e4:0c", NAME="net0"
SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:e0:4c:68:e5:12", NAME="net1"
SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:e0:4c:68:e4:0d", NAME="net2" |
|
If "net0" is in use of the kernel name space your rule does nothing. Probably random due sequence.
What might work:
1.As you see, /usr/lib64/udev/rules.d/80-net-name-slot.rules :
Code: | IMPORT{cmdline}="net.ifnames"
ENV{net.ifnames}=="0", GOTO="net_name_slot_end" |
change CMDLINE , e.g. by /etc/default/grub
Code: | GRUB_CMDLINE_LINUX="net.ifnames=0" |
Or
2. /etc/udev/rules.d/80-net-name-slot.rules
just to over rule /usr/lib/udev/rules.d/80-net-name-slot.rules |
|
Back to top |
|
|
Fred Krogh Veteran
Joined: 07 Feb 2005 Posts: 1036 Location: Tujunga, CA
|
Posted: Mon Jul 29, 2013 2:37 pm Post subject: |
|
|
Thanks for this. At one point I had replaced net0 by netx, while leaving the others the same. Due to other problems netx and net0 seemed to work the same way. I'll give this a try at some point. But booting with systemd which was what I was trying to do is not something I'll try again for awhile. I never managed to get shorewall, mysql, or apache to work and I need them all. |
|
Back to top |
|
|
ulenrich Veteran
Joined: 10 Oct 2010 Posts: 1480
|
Posted: Mon Jul 29, 2013 2:49 pm Post subject: |
|
|
@Fred, you should open seperate threads for seperat issues.
That way you'll propably get the solution,
because otherwise it is hard to guess
what the important problem might be.
What is that hindered me to answer soonishly ... |
|
Back to top |
|
|
|