| Summary: | The irda service does not start during the initialization phase. | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Sébastien B. <sb.cw> |
| Component: | Installer | Assignee: | Kernel and Drivers maintainers <kernel> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | lovaren, mageia, marja11 |
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | irda-utils? kernel? | CVE: | |
| Status comment: | |||
|
Description
Sébastien B.
2017-03-26 19:32:01 CEST
Hello,
systemctl status irda.service
â irda.service - Irda Support
Loaded: loaded (/usr/lib/systemd/system/irda.service; enabled; vendor preset: enabled)
Active: failed (Result: resources) since dim. 2017-03-26 19:27:00 CEST; 36s ago
Process: 1229 ExecStart=/usr/sbin/irattach ${DEVICE} ${OPTIONS} (code=exited, status=0/SUCCESS)
Process: 1063 ExecStartPre=/sbin/modprobe -qab ircomm-tty irtty-sir irnet (code=exited, status=0/SUCCESS)
mars 26 19:27:00 localhost.localdomain systemd[1]: Starting Irda Support...
mars 26 19:27:00 localhost.localdomain systemd[1]: irda.service: PID file /var/run/irattach.pid not readable (yet?) after start: No such file or directory
mars 26 19:27:00 localhost.localdomain systemd[1]: irda.service: Daemon never wrote its PID file. Failing.
mars 26 19:27:00 localhost.localdomain systemd[1]: Failed to start Irda Support.
mars 26 19:27:00 localhost.localdomain systemd[1]: irda.service: Unit entered failed state.
mars 26 19:27:00 localhost.localdomain systemd[1]: irda.service: Failed with result 'resources'
Regards,
Sébastien B.
Wildly guessing this is a kernel issue (besides, there is no registered irda-utils maintainer), so assigning tot the kernel maintainers. Please reassign if I'm wrong. Assignee:
bugsquad =>
kernel Hello, That can, perhaps help: http://forums.fedoraforum.org/showthread.php?t=281384 "it's only a Pid path confusion between the init script and systemd. if your service config file has another path that systemd standard path (/var/run/httpd for systemd) so it will complain. the solution is to set PidFile in httpd.conf as /var/run/httpd/httpd.pid" Regards, Sébastien B. I have that issue as well during the boot sequence. CC:
(none) =>
hamnisdude Hello,
After the update of the kernel, the error message is different:
systemctl status irda.service
â irda.service - Irda Support
Loaded: loaded (/usr/lib/systemd/system/irda.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since mer. 2017-03-29 05:45:48 CEST; 9min ago
Process: 1269 ExecStart=/usr/sbin/irattach ${DEVICE} ${OPTIONS} (code=exited, status=0/SUCCESS)
Process: 1093 ExecStartPre=/sbin/modprobe -qab ircomm-tty irtty-sir irnet (code=exited, status=0/S
Main PID: 1274 (code=exited, status=1/FAILURE)
mars 29 05:45:48 localhost.localdomain systemd[1]: Starting Irda Support...
mars 29 05:45:48 localhost.localdomain systemd[1]: irda.service: PID file /var/run/irattach.pid not
mars 29 05:45:48 localhost.localdomain systemd[1]: Started Irda Support.
mars 29 05:45:48 localhost.localdomain irattach[1274]: tcgetattr: Input/output error
mars 29 05:45:48 localhost.localdomain irattach[1274]: Stopping device /dev/ttyS2
mars 29 05:45:48 localhost.localdomain systemd[1]: irda.service: Main process exited, code=exited, s
mars 29 05:45:48 localhost.localdomain systemd[1]: irda.service: Unit entered failed state.
mars 29 05:45:48 localhost.localdomain systemd[1]: irda.service: Failed with result 'exit-code'.
Regards,
Sébastien B.
same here, during boot i see the service failing CC:
(none) =>
mageia Hello, Is what new information is available for this bug? Regards, Sébastien B. Resolved. we can close this as fixed then ? Based on comment 8 and no response for 5 years...closing as FIXED. Status:
NEW =>
RESOLVED |