"systemctl start php5-fpm.service" failes due to timeout of systemd-tty-ask-password-agent

Bug #1451346 reported by Alexander Löhner
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
systemd (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

I've filed this bug also already on the bugtracker of systemd here:
--> https://bugs.freedesktop.org/show_bug.cgi?id=90294

But for your information and maybe because it is more Ubuntu related than systemd related, here is the whole bug description again:

I've recently upgraded my Ubuntu box from 14.04 to 15.04 where systemd is now used as the default.

Unfortunatly starting or restarting of service php5-fpm doesn't work. It hangs 3 minutes and then it gets a timeout.

This seems to be caused by a process "/bin/systemd-tty-ask-password-agent --watch" which was called by "systemctl start php5-fpm.service".

It seems to wait for user input, but there is nothing to submit such an input.

Following the outputs of various things in cronological order:

~ $ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 15.04
Release: 15.04
Codename: vivid

~ $ ps auxwww --forest
   -> http://pastebin.com/LkbmNtKi

~ $ systemctl list-jobs
~ $ systemctl show
   -> http://pastebin.com/WaUGmnMV

~ $ systemctl start php5-fpm.service
Job for php5-fpm.service failed. See "systemctl status php5-fpm.service" and "journalctl -xe" for details.
~ $

during the command above runs, I've also created some output:
~ $ ps auxwww --forest
~ $ systemctl list-jobs
~ $ systemctl show
   -> http://pastebin.com/kxzhNTLT

After 3 minutes the start failed with a timeout and then:

~ $ systemctl status php5-fpm.service
~ $ systemctl list-jobs
~ $ systemctl show
~ $ lsb_release -a
~ $ dpkg -l | grep ii | grep systemd
~ $ ps aux | grep -i systemd
  -> http://pastebin.com/eCgb4Y0W

If you need further information, please let me know.

Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1451346/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

tags: added: bot-comment
tags: added: vivid
affects: ubuntu → systemd (Ubuntu)
Revision history for this message
Alexander Löhner (alex-mieland) wrote :

by the way: The try above was made just right after a complete reboot.

Starting the service manually with...

~ $ /usr/sbin/php5-fpm --nodaemonize --fpm-config /etc/php5/fpm/php-fpm.conf

...works.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in systemd (Ubuntu):
status: New → Confirmed
Revision history for this message
Lukas Brückner (2-me-8) wrote :

I can confirm this issue. But I believe it is related to the version from ondrej (https://launchpad.net/~ondrej/+archive/ubuntu/php5-5.6).

Reverting to version 5.6.4+dfsg-4ubuntu6 (the one packaged with 15.04) resolved the problem. Over at his issue tracker there is a similar bug posted. https://github.com/oerdnj/deb.sury.org/issues/65

Revision history for this message
Alexander Löhner (alex-mieland) wrote :

I can confirm that what Lukas has written in comment #4. After removing the PPA from Ondrej and downgading PHP5 to the official version from the ubuntu repositories, everything works.

So this is Ondrejs problem.

Changed in systemd (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.