FS#71013 - [iodine] Problem with iodined.service

Attached to Project: Community Packages
Opened by Josef Miegl (miegl) - Tuesday, 25 May 2021, 10:35 GMT
Last edited by Felix Yan (felixonmars) - Saturday, 28 January 2023, 10:04 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Felix Yan (felixonmars)
Morten Linderud (Foxboron)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
The iodined.service provided by the Arch package doesn't start iodined anymore.
The problem is that the service file has Type=Forking, introduced in https://github.com/archlinux/svntogit-community/commit/f86ca7ab64b1dd93635de848282426d7609f6108

systemd[1]: iodined.service: start operation timed out. Terminating.
systemd[1]: iodined.service: Failed with result 'timeout'.

Changing Type to Type=Simple fixes the problem.

Additional info:
* package version(s)
iodine 0.7.0-5
* config and/or log files etc.
iodined.service

Steps to reproduce:
Try to start iodined.service, get:

systemd[1]: iodined.service: start operation timed out. Terminating.
systemd[1]: iodined.service: Failed with result 'timeout'.
This task depends upon

Closed by  Felix Yan (felixonmars)
Saturday, 28 January 2023, 10:04 GMT
Reason for closing:  Fixed
Additional comments about closing:  0.7.0-6
Comment by loqs (loqs) - Tuesday, 25 May 2021, 15:31 GMT
Have you tried adding systemd to makedepends and changing the service type to notify?
Comment by Felix Yan (felixonmars) - Thursday, 25 August 2022, 19:24 GMT
@Foxboron The only fork() call in the source code is guarded with `!defined(__GLIBC__)`, and upstream repository has no mention of Type=forking anywhere. It looks like that  FS#42843  isn't valid at all?

@loqs I don't see sd_notify related code at all, so probably systemd support is only used for socket activation here.
Comment by Nimrod Maclomhair (nimrod_mack) - Thursday, 17 November 2022, 10:59 GMT
I noticed that the service file tries to start iodined running in foreground by specifying the option -f. Removing that option will make systemd start the service properly again, it seems.
Comment by Felix Yan (felixonmars) - Saturday, 28 January 2023, 10:03 GMT
I can confirm that removing -f works for me too. I have implemented this in iodine 0.7.0-6.

Loading...