Arch Linux

Kirill Bugaev

Member

Registered: 2018-08-03

Posts: 173

Some systemd services doesn't start on boot due to timeout

smb.service, mariadb.service and php-fpm.service doesn't start on system boot.
php-fpm example:

$ journalctl
...
Aug 02 07:57:42 toshibanb php-fpm[475]: [NOTICE] fpm is running, pid 475
Aug 02 07:57:42 toshibanb php-fpm[475]: [NOTICE] ready to handle connections
Aug 02 07:57:42 toshibanb php-fpm[475]: [NOTICE] systemd monitor interval set to 10000ms
Aug 02 07:57:42 toshibanb php-fpm[475]: [NOTICE] Terminating ...
Aug 02 07:57:42 toshibanb php-fpm[475]: [NOTICE] exiting, bye-bye!
Aug 02 07:57:42 toshibanb systemd[1]: php-fpm.service: Start operation timed out. Terminating.
Aug 02 07:57:42 toshibanb systemd[1]: php-fpm.service: Failed with result 'timeout'.
Aug 02 07:57:42 toshibanb systemd[1]: Failed to start The PHP FastCGI Process Manager.
...

Have the same issues with mariadb and smb. Of course everything starts OK manually after boot.
Guys on StackExchange advice to change Type=notify to Type=forking in systemd service files, but it means that I should check this files on every update of my ArchLinux system. Does another solution exist?

Last edited by Kirill Bugaev (2019-08-02 03:50:11)