[systemd-devel] systemd-fsckd: Couldn't connect to plymouth: Connection refused

Sat Mar 14 13:37:03 PDT 2015

This is the full log I got when I tried to mount the device:

Mar 14 20:46:08 morfikownia polkitd(authority=local)[1266]: Registered Authentication Agent for unix-process:11439:94979 (system bus name :1.41 [/usr/bin/pkttyagent --notify-fd 5 --fallback], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8)
Mar 14 20:46:08 morfikownia systemd[1]: Starting Cryptography Setup for grafi...
Mar 14 20:46:08 morfikownia cryptdisks_start[11444]: Starting crypto disk...grafi (starting)...
Mar 14 20:46:11 morfikownia cryptdisks_start[11444]: grafi (started)...done.
Mar 14 20:46:11 morfikownia systemd[1]: Started Cryptography Setup for grafi.
Mar 14 20:46:11 morfikownia systemd[1]: Found device /dev/mapper/grafi.
Mar 14 20:46:11 morfikownia systemd[1]: Starting File System Check on /dev/mapper/grafi...
Mar 14 20:46:11 morfikownia systemd[1]: Started File System Check Daemon to report status.
Mar 14 20:46:11 morfikownia systemd[1]: Starting File System Check Daemon to report status...
Mar 14 20:46:12 morfikownia systemd-fsck[11515]: grafi has been mounted 22 times without being checked, check forced.
Mar 14 20:46:12 morfikownia systemd-fsckd[11517]: Couldn't connect to plymouth: Connection refused
Mar 14 20:46:12 morfikownia systemd-fsckd[11517]: Couldn't connect to plymouth: Connection refused
Mar 14 20:46:12 morfikownia systemd-fsckd[11517]: Couldn't connect to plymouth: Connection refused
Mar 14 20:46:12 morfikownia systemd-fsckd[11517]: Couldn't connect to plymouth: Connection refused
Mar 14 20:46:12 morfikownia systemd-fsckd[11517]: Couldn't connect to plymouth: Connection refused
Mar 14 20:46:12 morfikownia systemd-fsckd[11517]: Couldn't connect to plymouth: Connection refused
Mar 14 20:46:12 morfikownia systemd-fsckd[11517]: Couldn't connect to plymouth: Connection refused
Mar 14 20:46:12 morfikownia systemd-fsckd[11517]: Couldn't connect to plymouth: Connection refused
Mar 14 20:46:12 morfikownia systemd-fsckd[11517]: Couldn't connect to plymouth: Connection refused
Mar 14 20:46:12 morfikownia systemd-fsckd[11517]: Couldn't connect to plymouth: Connection refused
Mar 14 20:46:12 morfikownia systemd-fsckd[11517]: Couldn't connect to plymouth: Connection refused
Mar 14 20:46:12 morfikownia systemd-fsckd[11517]: Couldn't connect to plymouth: Connection refused
Mar 14 20:46:12 morfikownia systemd-fsckd[11517]: Couldn't connect to plymouth: Connection refused
Mar 14 20:46:13 morfikownia systemd-fsckd[11517]: Couldn't connect to plymouth: Connection refused
Mar 14 20:46:13 morfikownia systemd-fsck[11515]: grafi: 21194/1966080 files (4.9% non-contiguous), 7743265/7863808 blocks
Mar 14 20:46:13 morfikownia systemd-fsckd[11517]: Couldn't connect to plymouth: Connection refused
Mar 14 20:46:13 morfikownia systemd[1]: Started File System Check on /dev/mapper/grafi.
Mar 14 20:46:13 morfikownia systemd[1]: Mounting /media/Grafi...
Mar 14 20:46:13 morfikownia systemd[1]: Mounted /media/Grafi.
Mar 14 20:46:13 morfikownia kernel: EXT4-fs (dm-6): mounted filesystem with ordered data mode. Opts: errors=remount-ro,commit=10
Mar 14 20:46:13 morfikownia polkitd(authority=local)[1266]: Unregistered Authentication Agent for unix-process:11439:94979 (system bus name :1.41, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus)

That's an encrypted partition, and I open it sometimes after I log into
the system because most of the time I don't need it, and I don't want
it to be mounted at boot automatically.

The device works well after mounting, but what about the systemd-fsckd
message? Is there a way to get rid of that?

I can't use the systemd-cryptsetup at grafi.service file directly because
I use the keyscript=/lib/cryptsetup/scripts/decrypt_derived option in
the /etc/crypttab file, and as far as I know, systemd isn't able to use
that option, so I had to change the service file a little bit, and it
looks like this:

[Unit]
Description=Cryptography Setup for %I
Documentation=man:cryptdisks_start man:cryptdisks_stop man:systemd-cryptsetup-generator(8) man:systemd-cryptsetup at .service(8)
SourcePath=/etc/crypttab
DefaultDependencies=no
IgnoreOnIsolate=true
Before=systemd-fsck at dev-mapper-grafi.service media-Grafi.mount umount.target 
After=dev-disk-by\x2duuid-d314ed20\x2dffaf\x2d4a18\x2d98a7\x2d91538e79d981.device cryptsetup-pre.target systemd-fsck-root.service
BindsTo=dev-mapper-%i.device
BindsTo=dev-disk-by\x2duuid-d314ed20\x2dffaf\x2d4a18\x2d98a7\x2d91538e79d981.device
Conflicts=umount.target

[Service]
Type=oneshot
RemainAfterExit=yes
TimeoutSec=30
ExecStart=/usr/sbin/cryptdisks_start %i
ExecStop=/usr/sbin/cryptdisks_stop %i

[Install]
WantedBy=cryptsetup.target

It's basically the same file which was generated by
systemd-cryptsetup-generator . I only changed Exec lines so it could
use the debian tools that can open the device using the keyscript
option. I don't know if that is related in any way to this problem,
but I inform you just in case.

The two other files look linke this:

# cat systemd-fsck at dev-mapper-grafi.service

[Unit]
Description=File System Check on %f
Documentation=man:systemd-fsck at .service(8)
DefaultDependencies=no
BindsTo=%i.device
After=systemd-readahead-collect.service systemd-readahead-replay.service %i.device systemd-fsck-root.service
Before=shutdown.target

[Service]
Type=oneshot
RemainAfterExit=yes
ExecStart=/lib/systemd/systemd-fsck %f
StandardOutput=journal+console
TimeoutSec=0

# cat media-Grafi.mount

[Unit]
SourcePath=/etc/fstab
Documentation=man:fstab(5) man:systemd-fstab-generator(8)
RequiresOverridable=systemd-fsck at dev-mapper-grafi.service
After=systemd-fsck at dev-mapper-grafi.service systemd-cryptsetup at grafi.service

[Mount]
What=/dev/mapper/grafi
Where=/media/Grafi
Type=ext4
Options=defaults,nofail,errors=remount-ro,commit=10

[Install]
WantedBy=basic.target

Basically I just open the container (and mount it) via
media-Grafi.mount and close it (and unmount) using systemd-cryptsetup at grafi.service ,
and of course once in a while the fsck counter hits 20 and checks
the file system. So the whole process works well, but apparently
there's something wrong with plymouth and systemd-fsckd , and I don't
know if it's because of the setup or something else that I could fix.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 801 bytes
Desc: OpenPGP digital signature
URL: <http://lists.freedesktop.org/archives/systemd-devel/attachments/20150314/dbc4fa2f/attachment.sig>