Updates caused connmand error: Failed to open file “/proc/net/pnp”

rogerthat · 2017-06-27 01:25:11

I ran a system update (pacman -Syu) today since maybe a month or so, and now I have errors in the journal:

journalctl -p 3 -xb

connmand[294]: __connman_inet_get_pnp_nameservers: Cannot read /proc/net/pnp Failed to open file “/proc/net/pnp”: No such file or directory
connmand[294]: get_nfs_server_ip: File /proc/net/pnp doesn't exist
connmand[294]: get_nfs_server_ip: File /proc/net/pnp doesn't exist
connmand[294]: get_nfs_server_ip: File /proc/net/pnp doesn't exist
connmand[294]: get_nfs_server_ip: File /proc/net/pnp doesn't exist
connmand[294]: get_nfs_server_ip: Failed to set domainname to lan

Internet connectivity is still working (via wifi). Not sure how to troubleshoot?

Thanks!

Last edited by rogerthat (2018-02-10 13:01:28)

seth · 2017-06-27 07:26:05

/proc/net/pnp is a kernel provided nameserver, this is usually tied to an NFS root device (ie. you boot from network)
https://www.kernel.org/doc/Documentatio … fsroot.txt

If you don't know what all of this is, this is likely some sort of false positive by connmand

rogerthat · 2018-02-09 21:00:11

I have the same issue since many months, and it's not resolved.
How do I troubleshoot these errors?
Wifi works, but these errors at boot time are disconcerting.

I am not using NFS, so would like to know why this is even popping up.

Last edited by rogerthat (2018-02-10 02:31:33)

seth · 2018-02-09 21:22:26

Sanity check:

systemctl list-units | grep -iE '(wicd|conn|net|dhcp|wpa)'

rogerthat · 2018-02-09 23:42:36

seth wrote:

Sanity check:

systemctl list-units | grep -iE '(wicd|conn|net|dhcp|wpa)'

Results contain:
sys-devices... for PCI Express Ethernet controller
sys-devices... for Wireless LAN Controller
sys-subsystem... for PCI Express Ethernet controller
sys-subsystem... for Wireless LAN Controller
connman-vpn.service
connman.service
wpa_supplicant.service
network.target

So, is it sane?

jasonwryan · 2018-02-09 23:51:21

Yes.

Please use code tags when pasting to the boards: https://wiki.archlinux.org/index.php/Co … s_and_code

And edit your thread title to specifically refer to your issue: https://wiki.archlinux.org/index.php/Co … ow_to_post

You may want to open a bug report upstream on the connman tracker about this.

seth · 2018-02-09 23:52:08

idk because you dropped the status fields and redacted devices, https://bbs.archlinux.org/viewtopic.php?id=57855
You're probably using connman case of VPN? Did you see https://wiki.archlinux.org/index.php/Co … domainname ?

rogerthat · 2018-02-10 02:16:45

Thanks for the help, guys.
I can't copy/paste, so that's why I abbreviated the message. Here it is in full this time...

systemctl list-units | grep -iE '(wicd|conn|net|dhcp|wpa)'

sys-devices-pci0000:00-0000:00:1c.0-0000:01:00.0-net-enp1s0.device  loaded active plugged   RTL8101/2/6E PCI Express Fast Ethernet controller                            
sys-devices-pci0000:00-0000:00:1c.1-0000:02:00.0-net-wlp2s0.device  loaded active plugged   RTL8187SE Wireless LAN Controller (MN54G2 / MS-6894 Wireless Mini PCIe Card) 
sys-subsystem-net-devices-enp1s0.device                             loaded active plugged   RTL8101/2/6E PCI Express Fast Ethernet controller                            
sys-subsystem-net-devices-wlp2s0.device                             loaded active plugged   RTL8187SE Wireless LAN Controller (MN54G2 / MS-6894 Wireless Mini PCIe Card) 
connman-vpn.service                                                 loaded active running   ConnMan VPN service                                                          
connman.service                                                     loaded active running   Connection service                                                           
wpa_supplicant.service                                              loaded active running   WPA supplicant                                                               
network.target                                                      loaded active active    Network

Last edited by rogerthat (2018-02-10 02:31:01)

jasonwryan · 2018-02-10 02:25:32

rogerthat wrote:

I didn't open this thread so I can't change the title.

Yours is the first post, so yes, you did open it. Please change the title.

rogerthat · 2018-02-10 02:30:21

seth wrote:

You're probably using connman case of VPN? Did you see https://wiki.archlinux.org/index.php/Co … domainname ?

Hmm. Yes, I had seen that before and done that before. I added:

CapabilityBoundingSet=... CAP_SYS_ADMIN

in /usr/lib/systemd/system/connman.service.

But it seems it has disappeared! In an upgrade perhaps?
I've put it back, and it fixed the last line in the error message.
But I still have these errors:

connmand[256]: __connman_inet_get_pnp_nameservers: Cannot read /proc/net/pnp Failed to open file “/proc/net/pnp”: No such file or directory
connmand[256]: get_nfs_server_ip: File /proc/net/pnp doesn't exist
connmand[256]: get_nfs_server_ip: File /proc/net/pnp doesn't exist
connmand[256]: get_nfs_server_ip: File /proc/net/pnp doesn't exist
connmand[256]: get_nfs_server_ip: File /proc/net/pnp doesn't exist

NOTE: I am not using any VPN.

jasonwryan wrote:

Yours is the first post, so yes, you did open it. Please change the title.

Wow! Indeed I did. LOL. I didn't remember it.

Last edited by rogerthat (2018-02-10 13:02:52)

jasonwryan · 2018-02-10 02:36:07

rogerthat wrote:

LOL. I didn't remember it.

For the third and final time, change the title. I will not ask again.

rogerthat · 2018-02-10 02:42:48

jasonwryan wrote:

rogerthat wrote:
LOL. I didn't remember it.
For the third and final time, change the title. I will not ask again.

Thanks for the help, but I'm reading an angry tone here. If the title still doesn't match what you think it should be, why don't you give me a suggestion? I did my best. There is a length limit, so...

Last edited by rogerthat (2018-02-10 02:43:14)

rogerthat · 2018-02-10 02:48:35

jasonwryan wrote:

You may want to open a bug report upstream on the connman tracker about this.

How would I do that exactly? Not sure what that means.

Like this?
https://01.org/jira/browse/CM-690

Last edited by rogerthat (2018-02-10 03:01:49)

seth · 2018-02-10 09:43:47

Looked up the source; It's caused by https://git.kernel.org/pub/scm/network/ … d0bd52c2a7
So instead of silently failing and causing an error later when strying to split a null string, you now get this error message which you can fully ignore if you don't care about an NFS root.

Trilby · 2018-02-10 11:29:18

rogerthat wrote:

If the title still doesn't match what you think it should be, why don't you give me a suggestion?

I'd suggest fixing the typos. pnp != php. Only one of those two could I have useful input on, and that's what drew me to this thread. But this thread has no connection at all to php.

(I originally also though connmand was also a typo. I guess it's not. It aggravates me to no end that despite `connman` being clearly distiguishable from the word "command", the name of the daemon for the former is very hard for my brain to process correctly).

Last edited by Trilby (2018-02-10 11:31:11)

rogerthat · 2018-02-10 13:04:26

seth wrote:

Looked up the source; It's caused by https://git.kernel.org/pub/scm/network/ … d0bd52c2a7
So instead of silently failing and causing an error later when strying to split a null string, you now get this error message which you can fully ignore if you don't care about an NFS root.

Great. Thank you for the research and explanations, Seth!

Arch Linux

#1 2017-06-27 01:25:11

Updates caused connmand error: Failed to open file “/proc/net/pnp”

#2 2017-06-27 07:26:05

Re: Updates caused connmand error: Failed to open file “/proc/net/pnp”

#3 2018-02-09 21:00:11

Re: Updates caused connmand error: Failed to open file “/proc/net/pnp”

#4 2018-02-09 21:22:26

Re: Updates caused connmand error: Failed to open file “/proc/net/pnp”

#5 2018-02-09 23:42:36

Re: Updates caused connmand error: Failed to open file “/proc/net/pnp”

#6 2018-02-09 23:51:21

Re: Updates caused connmand error: Failed to open file “/proc/net/pnp”

#7 2018-02-09 23:52:08

Re: Updates caused connmand error: Failed to open file “/proc/net/pnp”

#8 2018-02-10 02:16:45

Re: Updates caused connmand error: Failed to open file “/proc/net/pnp”

#9 2018-02-10 02:25:32

Re: Updates caused connmand error: Failed to open file “/proc/net/pnp”

#10 2018-02-10 02:30:21

Re: Updates caused connmand error: Failed to open file “/proc/net/pnp”

#11 2018-02-10 02:36:07

Re: Updates caused connmand error: Failed to open file “/proc/net/pnp”

#12 2018-02-10 02:42:48

Re: Updates caused connmand error: Failed to open file “/proc/net/pnp”

#13 2018-02-10 02:48:35

Re: Updates caused connmand error: Failed to open file “/proc/net/pnp”

#14 2018-02-10 09:43:47

Re: Updates caused connmand error: Failed to open file “/proc/net/pnp”

#15 2018-02-10 11:29:18

Re: Updates caused connmand error: Failed to open file “/proc/net/pnp”

#16 2018-02-10 13:04:26

Re: Updates caused connmand error: Failed to open file “/proc/net/pnp”

Board footer