Bug 702153 - Several services errored following upgrade
Summary: Several services errored following upgrade
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: systemd
Version: 15
Hardware: i686
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Lennart Poettering
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-04 22:06 UTC by cam
Modified: 2011-08-31 00:36 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-08-31 00:36:05 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 695588 0 unspecified CLOSED Bluetooth is always disabled 2021-02-22 00:41:40 UTC

Internal Links: 695588

Description cam 2011-05-04 22:06:20 UTC
Description of problem:
The system was upgraded from F14 to F15 using preupgrade and there were several problems with systemd services afterwards.

Most of the problems were not immediately noticeable but caused harder to diagnose problems later on.

Version-Release number of selected component (if applicable):
systemd-26-1.fc15.i686


How reproducible:
seems common amongst other bug reporters

Steps to Reproduce:
1.upgrade F14->F15 using preupgrade
2.check logs
3.check systemctl --all

Actual results:
[root@newt ~]# systemctl --all|grep error
dbus-org.bluez.service    error  inactive dead          dbus-org.bluez.service
dbus-org....Avahi.service error  inactive dead          dbus-org.freedesktop.Avahi.service
distcache.service         error  inactive dead          distcache.service
tgtd.service              error  inactive dead          tgtd.service
abrtd.target              error  inactive dead          abrtd.target
cgconfig.target           error  inactive dead          cgconfig.target


Expected results:
no errors

Additional info:
https://bugzilla.redhat.com/show_bug.cgi?id=696278
 - NetworkManager not started

https://bugzilla.redhat.com/show_bug.cgi?id=699198
 - rsyslog not started

https://bugzilla.redhat.com/show_bug.cgi?id=696815
 - dbus-org.freedesktop.Avahi.service failed to load

Comment 1 cam 2011-05-14 16:50:42 UTC
I reinstalled the system from scratch, using the F15 live CD to rule out issues from the upgrade.

I get:

[root@sulaco ~]# systemctl --all|grep error
dbus-org.bluez.service    error  inactive dead          dbus-org.bluez.service
tgtd.service              error  inactive dead          tgtd.service
abrtd.target              error  inactive dead          abrtd.target
cgconfig.target           error  inactive dead          cgconfig.target

from a fresh install.

Comment 2 Peter Trenholme 2011-06-01 19:44:12 UTC
In a "default" installation, the cgconfig service start will fail because the default configuration file (/etc/cgconfig.conf) is shipped with all lines (including the default grouping) commented out. The service start should, I think, not post a "failed" when it has nothing to do.

Note that the parser will fail if the default groups are specified, but that's a different bug, already reported.

Comment 3 Lennart Poettering 2011-08-31 00:36:05 UTC
(In reply to comment #1)
> I reinstalled the system from scratch, using the F15 live CD to rule out issues
> from the upgrade.
> 
> I get:
> 
> [root@sulaco ~]# systemctl --all|grep error
> dbus-org.bluez.service    error  inactive dead          dbus-org.bluez.service
> tgtd.service              error  inactive dead          tgtd.service
> abrtd.target              error  inactive dead          abrtd.target
> cgconfig.target           error  inactive dead          cgconfig.target
> 
> from a fresh install.

This is not a bug. It just means that some services are referenced by other services but couldn't be found. Which is completely OK for example when a service A wants to be started after a service B but it doesn't really matter whether B is around or not. systemctl by default hides these services if they aren't found. With "--all" you unhide them, but that doesn't make them a problem.

So there's nothign wrong here.


Note You need to log in before you can comment on or make changes to this bug.