Bug 589640 – net-analyzer/munin munin-node: Couldn't fork: [Inappropriate ioctl for device] at /usr/lib64/perl5/vendor_perl/5.20.2/Net/Server/Daemonize.pm line 182.

• Product: Gentoo Linux
• Status: RESOLVED TEST-REQUEST

[Description nikarul 2016-07-25 02:02:26 UTC]

For awhile now, munin-node has failed to start.  I've tried running perl-cleaner, clearing the config files out and unmerging/remerging munin, no luck.  The only clue is in the munin-node.log file:


2016/07/24-21:55:36 Couldn't fork: [Inappropriate ioctl for device] at /usr/lib64/perl5/vendor_perl/5.20.2/Net/Server/Daemonize.pm line 182.

  at line 158 in file /usr/lib64/perl5/vendor_perl/5.20.2/Net/Server.pm
2016/07/24-21:55:36 Server closing!


However, I understand that ENOTTY could be a leftover errno from ioctls performed by perl when opening files, so I'm not sure what the actual problem is.

[Comment 1 nikarul 2016-08-02 12:45:37 UTC]

I had enabled the "ithreads" use flag for perl for one of my projects, and it appears to be the source of the problems.  Once I rebuilt without ithreads, munin-node started and appeared to run normally.

[Comment 2 Hans de Graaff 2017-07-22 06:53:38 UTC]

(In reply to nikarul from comment #1)
> I had enabled the "ithreads" use flag for perl for one of my projects, and
> it appears to be the source of the problems.  Once I rebuilt without
> ithreads, munin-node started and appeared to run normally.

I just tried this with munin 2.0.33 and perl 5.24.1 with ithreads and had no problems starting munin-node.

You reported this for perl 5.20.2 and you don't mention the munin version. Perhaps something got fixed in the meantime?

Could you test this again with more recent versions and re-open if this is still a problem?