You are not logged in.

#1 2015-10-18 09:27:47

SprinkleberryMuffin
Member
Registered: 2015-10-18
Posts: 4

[Solved] systemd-rfkill.socket Failed to Start. (ENOENT)

I have quite a unique setup. I run a small website, and for easy of management of various services (dhcp, dns, mail, database, ldap), I use lxc.
The host OS is Fedora 20. (I inherited it from the last guy who runs this...),  and all the lxc-containers are arch.

Yesterday I updated systemd via pacman -Syu (I have backups), and everything else seems to be running.
Except for this.

    UNIT                  LOAD   ACTIVE SUB    DESCRIPTION
    ● systemd-rfkill.socket loaded failed failed Load/Save RF Kill Switch Status /dev/rfkill Watch

systemctl status systemd-rfkill.socket gives me this

    ● systemd-rfkill.socket - Load/Save RF Kill Switch Status /dev/rfkill Watch
       Loaded: loaded (/usr/lib/systemd/system/systemd-rfkill.socket; static; vendor preset: disabled)
       Active: failed (Result: resources)
         Docs: man:systemd-rfkill.socket(8)
       Listen: /dev/rfkill (Special)

    Oct 18 09:16:46 test systemd[1]: systemd-rfkill.socket: Failed to listen on sockets: No such file or directory
    Oct 18 09:16:46 test systemd[1]: Failed to listen on Load/Save RF Kill Switch Status /dev/rfkill Watch.
    Oct 18 09:16:46 test systemd[1]: systemd-rfkill.socket: Unit entered failed state.


The interesting part is that this only occurs in some containers. Two containers (which were done by my predecessor, are A-OK and have no issues). It is only the newer containers which I created which have this issue. The older containers were the mail and the ldap containers.
The newer containers are database (just mariadb installed), and dns + dhcp (just dnsmasq installed).

This might be a lxc issue tho...

As far as I understand it, in a headless server as this, (without any wireless links) it is safe enough to simply disable the systemd-rfkill service.
Am I right?
Also.... could anyone elaborate as to what exactly is a `state` which rfkill recovers from and stores to? (File format). I was unable to find it.

Please advice.

Note: The services that the container provides appear to be functional, so the containers are live ATM.


[Update]

This happens even when I spawn a new container. (nothing installed)

I created new container via

    lxc-create -n test -t archlinux

Last edited by SprinkleberryMuffin (2015-10-18 11:36:47)

Offline

#2 2015-10-18 10:11:25

mauritiusdadd
Member
From: Benevento, Italy
Registered: 2013-10-27
Posts: 776

Re: [Solved] systemd-rfkill.socket Failed to Start. (ENOENT)

SprinkleberryMuffin wrote:

could anyone elaborate as to what exactly is a `state` which rfkill recovers from and stores to? (File format). I was unable to find it.

man page to the rescue wink

man man systemd-rfkill.socket wrote:

DESCRIPTION
       systemd-rfkill.service is a service that restores the RF kill switch state at early boot and saves it on each change. On disk, the RF
       kill switch state is stored in /var/lib/systemd/rfkill/.

The state of a device indicates if and how the device is blocked/unblocked. The directory /var/lib/systemd/rfkill contains a file for each rfkill device on your system and each file contains a number which indicates the state of the device (usually 0 means unblocked and 1 means blocked). For example my wireless adapter has an rfkill device interface under /sys/devices/platform/samsung/rfkill/rfkill0, so systemd-rfkill will store the state of the device in /var/lib/systemd/rfkill/platform-samsung:wlan:

# rfkill list 0
0: samsung-wlan: Wireless LAN
	Soft blocked: no
	Hard blocked: no
# cat "/sys/devices/platform/samsung/rfkill/rfkill0/name"
samsung-wlan
# cat "/sys/devices/platform/samsung/rfkill/rfkill0/soft"
0
# cat "/var/lib/systemd/rfkill/platform-samsung:samsung-wlan" 
0

As for the error message, I don't think you can modify the state of a rfkill device and probably the interface is not even exposed to the container so I think you can just ignore the error message.


registered linux user #588260github

-- When you have eliminated the impossible, whatever remains, however improbable, must be the truth -- Spock | Sherlock Holmes

Offline

#3 2015-10-18 10:18:29

SprinkleberryMuffin
Member
Registered: 2015-10-18
Posts: 4

Re: [Solved] systemd-rfkill.socket Failed to Start. (ENOENT)

Yes, rfkill is not exposed to a container.


0 & 1.....
Damn...
I expected something a bit more complex than that. tongue


If possible, could I somehow suppress the error then? I don't like seeing failed units.


Thanks for the quick reply @mauritiusdadd

Offline

#4 2015-10-18 10:58:24

mauritiusdadd
Member
From: Benevento, Italy
Registered: 2013-10-27
Posts: 776

Re: [Solved] systemd-rfkill.socket Failed to Start. (ENOENT)

You're welcome smile

Maybe you can try to mask the socket file (I never tried it on a socket, so you have to try it yourself).


registered linux user #588260github

-- When you have eliminated the impossible, whatever remains, however improbable, must be the truth -- Spock | Sherlock Holmes

Offline

#5 2015-10-18 11:38:45

SprinkleberryMuffin
Member
Registered: 2015-10-18
Posts: 4

Re: [Solved] systemd-rfkill.socket Failed to Start. (ENOENT)

Masking the socket file works.
Masked the systemd-rfkill service as well.
(Because it makes no sense in a lxc container.)


Would there be any problems that you foresee here?


None of the devices on the physical machine use WiFi or Bluetooth.

Offline

#6 2015-10-18 14:07:39

mauritiusdadd
Member
From: Benevento, Italy
Registered: 2013-10-27
Posts: 776

Re: [Solved] systemd-rfkill.socket Failed to Start. (ENOENT)

SprinkleberryMuffin wrote:

Would there be any problems that you foresee here?

None: if there are no other errors in your journal then it should be fine.


registered linux user #588260github

-- When you have eliminated the impossible, whatever remains, however improbable, must be the truth -- Spock | Sherlock Holmes

Offline

#7 2015-10-18 21:26:59

Jristz
Member
From: America/Santiago
Registered: 2011-06-11
Posts: 1,020

Re: [Solved] systemd-rfkill.socket Failed to Start. (ENOENT)

I get the problem and I'm NOT in a container, I don't think that mask the files is a propper solution, so for me the [solved] is a lie


Well, I suppose that this is somekind of signature, no?

Offline

#8 2015-10-18 21:38:03

SprinkleberryMuffin
Member
Registered: 2015-10-18
Posts: 4

Re: [Solved] systemd-rfkill.socket Failed to Start. (ENOENT)

That is indeed a problem then.....
Strangely, some two of my containers worked fine with it and rest did not.


There is indeed something going on with systemd-rfkill.

Offline

#9 2015-10-19 06:20:08

mauritiusdadd
Member
From: Benevento, Italy
Registered: 2013-10-27
Posts: 776

Re: [Solved] systemd-rfkill.socket Failed to Start. (ENOENT)

Jristz wrote:

I get the problem and I'm NOT in a container, I don't think that mask the files is a propper solution, so for me the [solved] is a lie

Well, can you give us some more information, for example can you please post the output of the following commands?

$ systemctl status --all systemd-rfkill.socket
$ systemctl status --all systemd-rfkill.service
$ pacman -Qi rfkill
$ which rfkill

registered linux user #588260github

-- When you have eliminated the impossible, whatever remains, however improbable, must be the truth -- Spock | Sherlock Holmes

Offline

#10 2015-10-24 03:44:23

Jristz
Member
From: America/Santiago
Registered: 2011-06-11
Posts: 1,020

Re: [Solved] systemd-rfkill.socket Failed to Start. (ENOENT)

I find my problem, my HD is have some bad sectors and just the rfkill was corrupted (alongside some files in home and some packages) I reinstall the file (and check is was ok) and now work.

thanks anyway.


Well, I suppose that this is somekind of signature, no?

Offline

Board footer

Powered by FluxBB