Long standing machine problem - think I found something

Issues related to hardware problems
Post Reply
lightman47
Posts: 1100
Joined: 2014/05/21 20:16:00
Location: Central New York, USA

Long standing machine problem - think I found something

Post by lightman47 » 2019/12/04 19:16:47

I have a single {up to date} "nemesis" machine for which I've inquired here a few times trying to figure out it's "squirrely" nature, but never knew the right questions to ask. Every couple months I sit down, SSH in, and pour through logs trying to figure out 'what the heck', but to little avail. Largely, I suspect networking issues (NetworkManager). Today, my latest excursion, may finally be a hint -

notice that in ifconfig (below) the active/working interface is "enp4s0" - (previously had both on-board cards go bad (one at a time) and recently plugged in this card.

Please also notice that in the 'network-scripts' directory, that device does not exist!

QUESTION: What did I blow and how to correct it now?

Thank you. If you need more details I'll happily supply.

Code: Select all

# ifconfig
enp4s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.xxx.xx.181  netmask 255.255.255.0  broadcast 192.xxx.xx.255
        inet6 {deleted}  prefixlen 64  scopeid 0x20<link>
        ether {deleted} txqueuelen 1000  (Ethernet)
        RX packets 17758  bytes 18545973 (17.6 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 9698  bytes 2777690 (2.6 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 17  memory 0xfbce0000-fbd00000  

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        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

virbr0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet 192.xxx.122.1  netmask 255.255.255.0  broadcast 192.168.122.255
        ether (deleted}  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

wlp6s0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether (deleted}  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

Code: Select all

network-scripts]# ls -la
total 288
drwxr-xr-x. 2 root root  4096 Sep 17 12:05 .
drwxr-xr-x. 6 root root  4096 Nov 25 02:01 ..
-rw-r--r--. 1 root root   372 Jun 13  2018 ifcfg-Auto_whatcausesdat
-rw-r--r--. 1 root root   373 Mar 16  2017 ifcfg-Auto_whatcausesdat~
-rw-r--r--. 1 root root   315 Aug 24 13:28 ifcfg-enp2s0
-rw-r--r--. 1 root root   316 Jul 19 13:15 ifcfg-enp2s0~
-rw-r--r--. 1 root root   326 Jan  9  2018 ifcfg-enp7s4
-rw-r--r--. 1 root root   309 Jan  8  2018 ifcfg-enp7s4~
-rw-r--r--. 1 root root   254 Mar 29  2019 ifcfg-lo
-rw-r--r--. 1 root root   240 Aug 19 10:45 ifcfg-Wired_connection_1
lrwxrwxrwx. 1 root root    24 Sep 17 12:04 ifdown -> ../../../usr/sbin/ifdown
-rwxr-xr-x. 1 root root   654 Mar 29  2019 ifdown-bnep
-rwxr-xr-x. 1 root root  6532 Mar 29  2019 ifdown-eth
-rwxr-xr-x. 1 root root  6190 Aug  9 10:31 ifdown-ib
-rwxr-xr-x. 1 root root   781 Mar 29  2019 ifdown-ippp
-rwxr-xr-x. 1 root root  4540 Mar 29  2019 ifdown-ipv6
lrwxrwxrwx. 1 root root    11 Sep 17 12:04 ifdown-isdn -> ifdown-ippp
-rwxr-xr-x. 1 root root  2130 Mar 29  2019 ifdown-post
-rwxr-xr-x. 1 root root  1068 Mar 29  2019 ifdown-ppp
-rwxr-xr-x. 1 root root   870 Mar 29  2019 ifdown-routes
-rwxr-xr-x. 1 root root  1456 Mar 29  2019 ifdown-sit
-rwxr-xr-x. 1 root root  1621 Mar 17  2017 ifdown-Team
-rwxr-xr-x. 1 root root  1556 Mar 17  2017 ifdown-TeamPort
-rwxr-xr-x. 1 root root  1462 Mar 29  2019 ifdown-tunnel
lrwxrwxrwx. 1 root root    22 Sep 17 12:04 ifup -> ../../../usr/sbin/ifup
-rwxr-xr-x. 1 root root 12415 Mar 29  2019 ifup-aliases
-rwxr-xr-x. 1 root root   910 Mar 29  2019 ifup-bnep
-rwxr-xr-x. 1 root root 13475 Mar 29  2019 ifup-eth
-rwxr-xr-x. 1 root root 10114 Aug  9 10:31 ifup-ib
-rwxr-xr-x. 1 root root 12075 Mar 29  2019 ifup-ippp
-rwxr-xr-x. 1 root root 11893 Mar 29  2019 ifup-ipv6
lrwxrwxrwx. 1 root root     9 Sep 17 12:04 ifup-isdn -> ifup-ippp
-rwxr-xr-x. 1 root root   650 Mar 29  2019 ifup-plip
-rwxr-xr-x. 1 root root  1064 Mar 29  2019 ifup-plusb
-rwxr-xr-x. 1 root root  4997 Mar 29  2019 ifup-post
-rwxr-xr-x. 1 root root  4154 Mar 29  2019 ifup-ppp
-rwxr-xr-x. 1 root root  2001 Mar 29  2019 ifup-routes
-rwxr-xr-x. 1 root root  3303 Mar 29  2019 ifup-sit
-rwxr-xr-x. 1 root root  1755 Mar 17  2017 ifup-Team
-rwxr-xr-x. 1 root root  1876 Mar 17  2017 ifup-TeamPort
-rwxr-xr-x. 1 root root  2711 Mar 29  2019 ifup-tunnel
-rwxr-xr-x. 1 root root  1836 Mar 29  2019 ifup-wireless
-rwxr-xr-x. 1 root root  5419 Mar 29  2019 init.ipv6-global
-rw-------. 1 root root    21 Mar 16  2017 keys-Auto_whatcausesdat
-rw-r--r--. 1 root root 20671 Mar 29  2019 network-functions
-rw-r--r--. 1 root root 31027 Mar 29  2019 network-functions-ipv6
Remember - importing/building packages will likely "byte you in the butt" come update time, long after you'd forgotten you did that! Use repos whenever possible.

User avatar
TrevorH
Forum Moderator
Posts: 28512
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Re: Long standing machine problem - think I found something

Post by TrevorH » 2019/12/04 22:33:49

grep enp4s0 /etc/sysconfig/network-scripts/ifcfg-*
CentOS 6 will die in November 2020 - migrate sooner rather than later!
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 is dead, do not use it.
Full time Geek, part time moderator. Use the FAQ Luke

lightman47
Posts: 1100
Joined: 2014/05/21 20:16:00
Location: Central New York, USA

Re: Long standing machine problem - think I found something

Post by lightman47 » 2019/12/04 22:38:12

Code: Select all

[root@machinename ~]# grep enp4s0 /etc/sysconfig/network-scripts/ifcfg-*
[root@machinename ~]# 
I now suspect my problems began after the first motherboard card went bad and I 'disabled it' in the GUI, switching to the other MB card. This process was repeated when the second MB card died and I plugged in the current card mentioned above.
Remember - importing/building packages will likely "byte you in the butt" come update time, long after you'd forgotten you did that! Use repos whenever possible.

User avatar
TrevorH
Forum Moderator
Posts: 28512
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Re: Long standing machine problem - think I found something

Post by TrevorH » 2019/12/04 23:02:47

Your first step is to clean up that directory. Any file that starts with the characters ifcfg- will be used so all of those files are currently being read. If you want to rename them out of the way, use a name that doesn't start with ifcfg- (or route/rule).
CentOS 6 will die in November 2020 - migrate sooner rather than later!
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 is dead, do not use it.
Full time Geek, part time moderator. Use the FAQ Luke

lightman47
Posts: 1100
Joined: 2014/05/21 20:16:00
Location: Central New York, USA

Re: Long standing machine problem - think I found something

Post by lightman47 » 2019/12/04 23:32:11

OK - renamed the 2 old "enp" files to "oldifcfg-enp..." and deleted the 2 with the trailing tilde.

ifcfg-Wired_connection_1 - is the currently used adapter (contents below). Curiously, it has no "NM MANAGED" line (or whatever the appropriate label). I checked my DHCP assignments for the MAC address. to verify this was the case. Will finding, and adding the correct NM line and changing this file's name fix everything do you suppose?

Code: Select all

HWADDR={deleted}
TYPE=Ethernet
PROXY_METHOD=none
BROWSER_ONLY=no
BOOTPROTO=dhcp
DEFROUTE=yes
IPV4_FAILURE_FATAL=no
IPV6INIT=no
NAME="Wired connection 1"
UUID=a4918216-eb0a-322f-9f9f-b5d7216942e7
ONBOOT=yes
AUTOCONNECT_PRIORITY=-999
new listing

Code: Select all

network-scripts]# ls -la
total 280
drwxr-xr-x. 2 root root  4096 Dec  4 18:16 .
drwxr-xr-x. 6 root root  4096 Nov 25 02:01 ..
-rw-r--r--. 1 root root   372 Jun 13  2018 ifcfg-Auto_whatcausesdat
-rw-r--r--. 1 root root   373 Mar 16  2017 ifcfg-Auto_whatcausesdat~
-rw-r--r--. 1 root root   254 Mar 29  2019 ifcfg-lo
-rw-r--r--. 1 root root   240 Aug 19 10:45 ifcfg-Wired_connection_1
lrwxrwxrwx. 1 root root    24 Sep 17 12:04 ifdown -> ../../../usr/sbin/ifdown
-rwxr-xr-x. 1 root root   654 Mar 29  2019 ifdown-bnep
-rwxr-xr-x. 1 root root  6532 Mar 29  2019 ifdown-eth
-rwxr-xr-x. 1 root root  6190 Aug  9 10:31 ifdown-ib
-rwxr-xr-x. 1 root root   781 Mar 29  2019 ifdown-ippp
-rwxr-xr-x. 1 root root  4540 Mar 29  2019 ifdown-ipv6
lrwxrwxrwx. 1 root root    11 Sep 17 12:04 ifdown-isdn -> ifdown-ippp
-rwxr-xr-x. 1 root root  2130 Mar 29  2019 ifdown-post
-rwxr-xr-x. 1 root root  1068 Mar 29  2019 ifdown-ppp
-rwxr-xr-x. 1 root root   870 Mar 29  2019 ifdown-routes
-rwxr-xr-x. 1 root root  1456 Mar 29  2019 ifdown-sit
-rwxr-xr-x. 1 root root  1621 Mar 17  2017 ifdown-Team
-rwxr-xr-x. 1 root root  1556 Mar 17  2017 ifdown-TeamPort
-rwxr-xr-x. 1 root root  1462 Mar 29  2019 ifdown-tunnel
lrwxrwxrwx. 1 root root    22 Sep 17 12:04 ifup -> ../../../usr/sbin/ifup
-rwxr-xr-x. 1 root root 12415 Mar 29  2019 ifup-aliases
-rwxr-xr-x. 1 root root   910 Mar 29  2019 ifup-bnep
-rwxr-xr-x. 1 root root 13475 Mar 29  2019 ifup-eth
-rwxr-xr-x. 1 root root 10114 Aug  9 10:31 ifup-ib
-rwxr-xr-x. 1 root root 12075 Mar 29  2019 ifup-ippp
-rwxr-xr-x. 1 root root 11893 Mar 29  2019 ifup-ipv6
lrwxrwxrwx. 1 root root     9 Sep 17 12:04 ifup-isdn -> ifup-ippp
-rwxr-xr-x. 1 root root   650 Mar 29  2019 ifup-plip
-rwxr-xr-x. 1 root root  1064 Mar 29  2019 ifup-plusb
-rwxr-xr-x. 1 root root  4997 Mar 29  2019 ifup-post
-rwxr-xr-x. 1 root root  4154 Mar 29  2019 ifup-ppp
-rwxr-xr-x. 1 root root  2001 Mar 29  2019 ifup-routes
-rwxr-xr-x. 1 root root  3303 Mar 29  2019 ifup-sit
-rwxr-xr-x. 1 root root  1755 Mar 17  2017 ifup-Team
-rwxr-xr-x. 1 root root  1876 Mar 17  2017 ifup-TeamPort
-rwxr-xr-x. 1 root root  2711 Mar 29  2019 ifup-tunnel
-rwxr-xr-x. 1 root root  1836 Mar 29  2019 ifup-wireless
-rwxr-xr-x. 1 root root  5419 Mar 29  2019 init.ipv6-global
-rw-------. 1 root root    21 Mar 16  2017 keys-Auto_whatcausesdat
-rw-r--r--. 1 root root 20671 Mar 29  2019 network-functions
-rw-r--r--. 1 root root 31027 Mar 29  2019 network-functions-ipv6
-rw-r--r--. 1 root root   315 Aug 24 13:28 oldifcfg-enp2s0
-rw-r--r--. 1 root root   326 Jan  9  2018 oldifcfg-enp7s4
Remember - importing/building packages will likely "byte you in the butt" come update time, long after you'd forgotten you did that! Use repos whenever possible.

lightman47
Posts: 1100
Joined: 2014/05/21 20:16:00
Location: Central New York, USA

Re: Long standing machine problem - think I found something

Post by lightman47 » 2019/12/05 12:49:09

WELL - it's now using the new ifcfg-enp4s0 but things are still 'wonky'. I copied in all the pertinent info from the connection it was using (Wired_connection_1), renamed Wired_connection_1 and rebooted. Still NFS shares take a long time to mount; indeed they eventually mount as usual, but long after they all failed in /var/log/messages.

I was hoping ... heh.
Remember - importing/building packages will likely "byte you in the butt" come update time, long after you'd forgotten you did that! Use repos whenever possible.

User avatar
TrevorH
Forum Moderator
Posts: 28512
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Re: Long standing machine problem - think I found something

Post by TrevorH » 2019/12/05 13:14:56

Your latest ls still shows ifcfg-Auto_whatcausesdat~ and if you've edited any of them since I suspect you'll have others. Looks like you use an editor that creates backup copies and appends a ~ to the old names. That doesn't work well for ifcfg- files.
CentOS 6 will die in November 2020 - migrate sooner rather than later!
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 is dead, do not use it.
Full time Geek, part time moderator. Use the FAQ Luke

lightman47
Posts: 1100
Joined: 2014/05/21 20:16:00
Location: Central New York, USA

Re: Long standing machine problem - think I found something

Post by lightman47 » 2019/12/05 15:41:05

Yeh - emacs.

OK - will do a little more cleanup.

EDIT:

Would I have better luck running the network service instead? It's been a long time so I'll have to experiment with setting it up after disabling NetworkManager.
Remember - importing/building packages will likely "byte you in the butt" come update time, long after you'd forgotten you did that! Use repos whenever possible.

Post Reply

Return to “CentOS 7 - Hardware Support”