Arch Linux

Al.Piotrowicz

Member

Registered: 2017-08-07

Posts: 116

Undesirable dbus-daemon systemd service behaviour

Hello community,

Im experiencing an irritating systemd dbus-daemon.service behaviour. Every time I open the particular apps like firefox, file-roller etc. it is in some kind starting hostnamed.service and produces unwanted gibberish output into system log:

dbus-daemon[664]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.447' (uid=1000 pid=1398 comm="/usr/lib/firefox/firefox ")
systemd[1]: dev-mapper-swap.swap: Cannot add dependency job, ignoring: Unit dev-mapper-swap.swap not found.
systemd[1]: dev-mapper-swap.swap: Cannot add dependency job, ignoring: Unit dev-mapper-swap.swap not found.
systemd[1]: dev-mapper-swap.swap: Cannot add dependency job, ignoring: Unit dev-mapper-swap.swap not found.
systemd[1]: dev-mapper-swap.swap: Cannot add dependency job, ignoring: Unit dev-mapper-swap.swap not found.
systemd[1]: Starting Hostname Service...
dbus-daemon[664]: [system] Successfully activated service 'org.freedesktop.hostname1'
systemd[1]: Started Hostname Service.

I just dont want to get it triggered, but if its caused by systemd "design" it has to be a way to redirect the output into /dev/null. Tried to read systemd manual but its over my skills, sorry. How to get rid of these irritating messages?

My 2nd question:

Is it safe to rename the swap mapper device into dev-mapper-swap? Right now in my setup it does generate dev-disk-by\x2did-dm\x2duuid\x2dCRYPT\x2dPLAIN\x2dswap.swap unit from /dev/disk/by-id/dm-uuid-CRYPT-PLAIN-swap placed in my fstab file.
It does complain every time regardless the service type about "unit swap not found" thing.

Thanks for help. Regards.

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 21,723

Re: Undesirable dbus-daemon systemd service behaviour

What's the output of

hostnamectl

? What's in your /etc/hosts? Have you followed https://wiki.archlinux.org/index.php/Ne … e_hostname ?

Al.Piotrowicz

Member

Registered: 2017-08-07

Posts: 116

Re: Undesirable dbus-daemon systemd service behaviour

Nothing fancy or magical here :

[user@box ~]$ hostnamectl 
Static hostname: box
Icon name: computer-desktop
Chassis: desktop
Machine ID: 5cf693ad42df5b596fbc083e942f4326
Boot ID: eb930051b66747aea9578e4d719030d2
Operating System: Arch Linux
Kernel: Linux 4.15.1-2-ARCH
Architecture: x86-64

------------------------------------------------------------------

[user@box ~]$ cat /etc/hosts
#
# /etc/hosts: static lookup table for host names
#

#<ip-address>	<hostname.domain.org>	<hostname>
127.0.0.1	localhost.localdomain	localhost
::1		localhost.localdomain	localhost
192.168.0.2	testowy.localdomain	box
# End of file

Yes I did follow the most of arch wiki tutorials, that one too, but I strongly doubt it has any impact on Dbus daemon service trigger.

seth

Member

Registered: 2012-09-03

Posts: 51,175

Re: Undesirable dbus-daemon systemd service behaviour

systemctl status systemd-hostnamed.service
cat /etc/nsswitch.conf

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Al.Piotrowicz

Member

Registered: 2017-08-07

Posts: 116

Re: Undesirable dbus-daemon systemd service behaviour

systemctl status systemd-hostnamed.service
cat /etc/nsswitch.conf

[user@box ~]$ systemctl status systemd-hostnamed.service
● systemd-hostnamed.service - Hostname Service
   Loaded: loaded (/usr/lib/systemd/system/systemd-hostnamed.service; static; vendor preset: disabled)
   Active: inactive (dead)
     Docs: man:systemd-hostnamed.service(8)
           man:hostname(5)
           man:machine-info(5)
           https://www.freedesktop.org/wiki/Software/systemd/hostnamed

lut 10 10:27:50 box systemd[1]: Starting Hostname Service...
lut 10 10:27:50 box systemd[1]: Started Hostname Service.
lut 10 10:40:47 box systemd[1]: Starting Hostname Service...
lut 10 10:40:47 box systemd[1]: Started Hostname Service.
lut 10 10:41:43 box systemd[1]: Starting Hostname Service...
lut 10 10:41:43 box systemd[1]: Started Hostname Service.
lut 10 11:15:51 box systemd[1]: Starting Hostname Service...
lut 10 11:15:51 box systemd[1]: Started Hostname Service.
lut 10 11:16:42 box systemd[1]: Starting Hostname Service...
lut 10 11:16:42 box systemd[1]: Started Hostname Service.

------------------------------------------------------------------------------------- 

[user@box ~]$ cat /etc/nsswitch.conf
# Name Service Switch configuration file.
# See nsswitch.conf(5) for details.

passwd: files mymachines systemd
group: files mymachines systemd
shadow: files

publickey: files

hosts: files mymachines resolve [!UNAVAIL=return] dns myhostname
networks: files

protocols: files
services: files
ethers: files
rpc: files

netgroup: files

seth

Member

Registered: 2012-09-03

Posts: 51,175

Re: Undesirable dbus-daemon systemd service behaviour

So it's starting and starting and starting - and still dead.
What if you explicitly start it?

systemctl start systemd-hostnamed.service

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Al.Piotrowicz

Member

Registered: 2017-08-07

Posts: 116

Re: Undesirable dbus-daemon systemd service behaviour

lut 10 11:49:00 box sudo[14023]:     user : TTY=pts/2 ; PWD=/home/user ; USER=root ; COMMAND=/usr/bin/systemctl start systemd-hostnamed.service
lut 10 11:49:00 box sudo[14023]: pam_unix(sudo:session): session opened for user root by (uid=0)
lut 10 11:49:00 box systemd[1]: dev-mapper-swap.swap: Cannot add dependency job, ignoring: Unit dev-mapper-swap.swap not found.
lut 10 11:49:00 box systemd[1]: dev-mapper-swap.swap: Cannot add dependency job, ignoring: Unit dev-mapper-swap.swap not found.
lut 10 11:49:00 box systemd[1]: dev-mapper-swap.swap: Cannot add dependency job, ignoring: Unit dev-mapper-swap.swap not found.
lut 10 11:49:00 box systemd[1]: dev-mapper-swap.swap: Cannot add dependency job, ignoring: Unit dev-mapper-swap.swap not found.
lut 10 11:49:00 box systemd[1]: Starting Hostname Service...
lut 10 11:49:00 box systemd[1]: Started Hostname Service.
lut 10 11:49:00 box sudo[14023]: pam_unix(sudo:session): session closed for user root

-----------------------------------------------------------------------------

[user@box ~]$ systemctl status systemd-hostnamed.service 
● systemd-hostnamed.service - Hostname Service
   Loaded: loaded (/usr/lib/systemd/system/systemd-hostnamed.service; static; vendor preset: disabled)
   Active: inactive (dead)
     Docs: man:systemd-hostnamed.service(8)
           man:hostname(5)
           man:machine-info(5)
           https://www.freedesktop.org/wiki/Software/systemd/hostnamed

lut 10 10:41:43 box systemd[1]: Starting Hostname Service...
lut 10 10:41:43 box systemd[1]: Started Hostname Service.
lut 10 11:15:51 box systemd[1]: Starting Hostname Service...
lut 10 11:15:51 box systemd[1]: Started Hostname Service.
lut 10 11:16:42 box systemd[1]: Starting Hostname Service...
lut 10 11:16:42 box systemd[1]: Started Hostname Service.
lut 10 11:47:48 box systemd[1]: Starting Hostname Service...
lut 10 11:47:49 box systemd[1]: Started Hostname Service.
lut 10 11:49:00 box systemd[1]: Starting Hostname Service...
lut 10 11:49:00 box systemd[1]: Started Hostname Service.

Seems pointless, but something definitely is wrong here.