failed systemctl services?

Michael D. Setzer II mikes at kuentos.guam.net
Mon May 4 16:45:54 UTC 2015


On 4 May 2015 at 11:51, Matthew Miller wrote:

Date sent:      	Mon, 4 May 2015 11:51:08 -0400
From:           	Matthew Miller <mattdm at fedoraproject.org>
To:             	Community support for Fedora users 
<users at lists.fedoraproject.org>
Copies to:      	"Michael D. Setzer II" <mikes at kuentos.guam.net>
Subject:        	Re: failed systemctl services?

> On Mon, May 04, 2015 at 07:57:57AM -0700, stan wrote:
> > > Is there a process that automatically will try to restart failed
> > > systemctl services, or would it be worth creating something to do so?
> > > Perhaps in cron.hourly? 
> > I'm no expert, but my understanding is that there is not.
> 
> Actually, *systemd* is that process. That's one of its huge features
> missing in the old init system. Take a look at the man page for
> systemd.service — search for "Restart=".
> 

As a test, just check the 20 machines in my classroom after a restart, and 
found that 2 of the machines had a total of 3 services that had failed after the 
reboot. Created a script to test restarting the failed services, and it seemed to 
work fine.

systemctl restart `systemctl --state=failed | grep failed | cut -f 2 -d\  `

In both machine cases, the systemctl then reported everything was working.

The vboxdrv issue earlier would have just failed again, since the modules 
would still be missing. 




> However, we don't configure most things that way out of the box... yet.
> There was discussion about this three years ago, reopened a year ago...
> 
> https://fedorahosted.org/fpc/ticket/191
> 
> and the current guidelines 
> 
> https://fedoraproject.org/wiki/Packaging:Systemd?rd=Packaging:Guidelines:Systemd#Automatic_restarting
> 
> but as far as I know there hasn't been a big effort to bring existing
> services in line. (Seems like a worthwhile project if anyone's
> interested.)
> 
> > 
> > > Might be these are harmless, but not sure.
> > 
> > It doesn't seem harmless that services that the user expects to be
> > started, and are configured properly, fail.
> > 
> > It would be good if you opened a bugzilla against systemd for an RFE
> > requesting such a utility.
> > -- 
> > users mailing list
> > users at lists.fedoraproject.org
> > To unsubscribe or change subscription options:
> > https://admin.fedoraproject.org/mailman/listinfo/users
> > Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
> > Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
> > Have a question? Ask away: http://ask.fedoraproject.org
> 
> -- 
> Matthew Miller
> <mattdm at fedoraproject.org>
> Fedora Project Leader


+----------------------------------------------------------+
  Michael D. Setzer II -  Computer Science Instructor      
  Guam Community College  Computer Center                  
  mailto:mikes at kuentos.guam.net                            
  mailto:msetzerii at gmail.com
  http://www.guam.net/home/mikes
  Guam - Where America's Day Begins                        
  G4L Disk Imaging Project maintainer 
  http://sourceforge.net/projects/g4l/
+----------------------------------------------------------+

http://setiathome.berkeley.edu (Original)
Number of Seti Units Returned:  19,471
Processing time:  32 years, 290 days, 12 hours, 58 minutes
(Total Hours: 287,489)

BOINC at HOME CREDITS
ROSETTA     28926945.864031   |   SETI        51036191.422589
ABC         16613838.513356   |   EINSTEIN    59683310.706700



More information about the users mailing list