You are not logged in.
I'm finding the systemd-hostnamed.service isnt working
$ sudo systemctl --state=failed
[sudo] password for kevdog:
UNIT LOAD ACTIVE SUB DESCRIPTION
● systemd-hostnamed.service loaded failed failed Hostname Service
LOAD = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB = The low-level unit activation state, values depend on unit type.
1 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.
$ sudo systemctl status systemd-hostnamed.service
● systemd-hostnamed.service - Hostname Service
Loaded: loaded (/usr/lib/systemd/system/systemd-hostnamed.service; static)
Active: failed (Result: timeout) since Tue 2014-12-16 23:11:36 CST; 10min ago
Docs: man:systemd-hostnamed.service(8)
man:hostname(5)
man:machine-info(5)
http://www.freedesktop.org/wiki/Software/systemd/hostnamed
Main PID: 4584
Dec 16 23:08:35 orphan systemd[1]: systemd-hostnamed.service start operation timed out. Terminating.
Dec 16 23:10:06 orphan systemd[1]: systemd-hostnamed.service stop-final-sigterm timed out. Killing.
Dec 16 23:11:36 orphan systemd[1]: systemd-hostnamed.service still around after final SIGKILL. Entering failed mode.
Dec 16 23:11:36 orphan systemd[1]: Failed to start Hostname Service.
Dec 16 23:11:36 orphan systemd[1]: Unit systemd-hostnamed.service entered failed state.
Dec 16 23:11:36 orphan systemd[1]: systemd-hostnamed.service failed.
I found this addressed in this topic:
https://github.com/ev3dev/ev3dev/issues/189
Within this page they state:
Confirmed that removing PrivateNetwork=yes from the service file works as a workaround. Maybe need to enable CONFIG_NAMESPACES=y and CONFIG_NET_NS=y kernel modules
I removed the PrivateNetwork=yes from the service file, however this didn't seem to work. I did not enable the kernel modules. I am currently running the following kernel: 3.17.6-1-ARCH
Thanks
Offline