=== JanC is now known as Guest34481
=== JanC_ is now known as JanC
[16:43] <Azoff> Hello
[16:45] <Azoff> I've got a server running Ubuntu 14.04 LTS (upstart 1.12.1-0ubuntu4.2) where I get 'start cryptdisks' to hang without any output to the screen or any other response. Ctrl+C terminates it, so it's not a zombie process
[16:46] <Azoff> Background: The server can boot a basic system on an unencrypted partition. Once booted, I can ssh to the server and unlock a partition that contains the configuration files (linked from /etc/) that allows me to mount a few other data partitions. All these data partions are encrypted.
[16:47] <Azoff> I've been using the layout for a few years, but recently got into trouble issuing '/etc/init.d/cryptdisks restart'.
[16:47] <Azoff> I've traced the issue as far as I can see that cryptsetup thinks it's done with the stuff it's supposed to do, but 'start' never returns
[16:50] <Azoff> running strace on 'start cryptdisks' ends with the following 3 syscalls repeating over and over again until stalled at poll(): poll() = 1, recvmsg() = -1, clock_gettime() = 0
[16:50] <Azoff> any idea what I could try next to find out why it's stuck there?
=== JanC_ is now known as JanC
[16:53] <Azoff> Hi JanC 
[18:30] <Azoff> Ok, some more details. It looks like dbus_pending_call_block(pending_call) never returns, and the error_handler or reply_handler is neither called. Could it be due to that the conf-file does not contain anything but 'task' and 'pre-start script'?
[18:31] <Azoff> :q
[19:22] <AnrDaemon> Azoff: It is a wonder the job even tried to start.
[19:56] <Azoff> AnrDaemon: ok? How so?
[19:56] <Azoff> Just for the record, I've not written this conf-file.
[19:57] <AnrDaemon> Without start script or exec, the behavior is undefined, IIRC.
[19:57] <AnrDaemon> And any undefined behavior is a can of worms, typically.
[20:01] <Azoff> ok? this is the default conf for cryptdisks (cryptsetup) in ubuntu since at least 14.04
[20:01] <Azoff> have you seen the conf?
=== balkamos_ is now known as balkamos