On 12/31/2015 06:13 PM, david wrote:
At 08:40 PM 12/28/2015, you wrote:
On 12/28/2015 10:01 PM, david wrote:
Folks
I've been having lots of problems with Centos 7 on Raspberry Pi 2. The network seems to work for a while after a bootstrap, but then dies. The command systemctl restart network always fails. This occurs after installation and updates.
I wonder of others have had this issue, or is my RPI2 defective? It's connected to my internal network by a wire-connection to a working Centos 6 gateway. I posted the results of journalctl earlier, so won't bother reposting.
No problems on my Cubieboard2: medon.htt-consult.com that has been up 4 1/2 days. The only messages on Network that I see are:
messages-20151227:Dec 24 09:46:33 medon NetworkManager[523]: <info> nameserver '2001:558:feed::2' messages-20151227:Dec 24 09:46:33 medon NetworkManager[523]: <info> nameserver '2001:558:feed::1' messages-20151227:Dec 24 09:46:33 medon NetworkManager[523]: <info> (eth0): DHCPv6 state changed unknown -> bound messages-20151227:Dec 24 09:46:33 medon NetworkManager[523]: <info> Policy set 'eth0' (eth0) as default for IPv6 routing and DNS. messages-20151227:Dec 24 09:46:33 medon NetworkManager[523]: <info> (eth0): DHCPv6 client pid 1395 exited with status 0 messages-20151227:Dec 24 09:46:33 medon NetworkManager[523]: <info> (eth0): DHCPv6 state changed bound -> done
which was when I booted it up in my production rack.
Is this the right mail=list to detect if and when the issue is addressed?
Hopefully others with RPi2 will chime in and it will be here.
Robert, and others
In one of those Eureka moments, I believe I understand why my network is failing. Examination of the "journalctl" output led me to the following:
- Chronyd is a REPLACEMENT for ntp
- Running both of them at the same time leads to ntpd disabling the
ethernet link.
If I'm right, perhaps a note should be added into the Arm web page so other dummies like me don't make the same mistake.
For extra bonus points, I wonder if someone could answer the question:
- Is it OK to use chrony instead of ntp on Centos 6&7 on i386/x86_64
systems? Should I change over?
I am leaving my C6 (really RSEL6) servers as is with NTP.
all my C7 are using Chrony.