Bug 806584

Summary:	Starting/Stopping ser service in Fedora 17 fails
Product:	[Fedora] Fedora	Reporter:	Michal Ambroz <rebus>
Component:	ser	Assignee:	Andreas Thienemann <andreas>
Status:	CLOSED WONTFIX	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	17	CC:	andreas, gregor
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-07-31 18:33:08 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Michal Ambroz 2012-03-25 01:32:31 UTC

Description of problem:
Starting/Stopping ser service in Fedora 17 fails. In connection with a fact that the service is enabled automatically after installation this results in 4 minutes delay of whole the boot sequence as systemd waits till the starting finishes.


Version-Release number of selected component (if applicable):
ser-0.9.6-22.fc17.x86_64

How reproducible:
100%

Steps to Reproduce:
1. yum -y install ser
2. reboot machine
  
Actual results:
The boot sequence will hang for couple of minutes with strange messages "Sendmail started, Sendmail stopped, Sendmail started, Sendmail stopped"


Expected results:
Service ser should start or fail to start smoothly.

Additional info:
snippet from /var/log/messages

Mar 25 00:52:58 mixer modem-manager[1119]: <info>  (ttyS0) serial port closed
Mar 25 00:53:06 mixer NetworkManager[1000]: <info> (wlan0): IP6 addrconf timed out or failed.
Mar 25 00:53:06 mixer NetworkManager[1000]: <info> Activation (wlan0) Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
Mar 25 00:53:06 mixer NetworkManager[1000]: <info> Activation (wlan0) Stage 4 of 5 (IPv6 Configure Timeout) started...
Mar 25 00:53:06 mixer NetworkManager[1000]: <info> Activation (wlan0) Stage 4 of 5 (IPv6 Configure Timeout) complete.
Mar 25 00:53:59 mixer chronyd[1051]: Selected source 81.0.235.220
Mar 25 00:57:40 mixer systemd[1]: ser.service operation timed out. Terminating.
Mar 25 00:57:40 mixer systemd[1]: Unit ser.service entered failed state.

Comment 1 Thomas Moschny 2012-09-26 17:08:48 UTC

Fixed wrong component.

Comment 2 Fedora End Of Life 2013-07-03 19:42:49 UTC

This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '17'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 17's end of life.

Bug Reporter:  Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 17 is end of life. If you 
would still like  to see this bug fixed and are able to reproduce it 
against a later version  of Fedora, you are encouraged  change the 
'version' to a later Fedora version prior to Fedora 17's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 3 Fedora End Of Life 2013-07-31 18:33:12 UTC

Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.