Description of problem: six services fail after boot: [root@mga6-64 alain4]# systemctl --failed UNIT LOAD ACTIVE SUB DESCRIPTION ● configure-printer@usb-006-002.service loaded failed failed Configure Plugged-In Printer ● dhcpd.service loaded failed failed DHCPv4 Server Daemon ● network.service loaded failed failed LSB: Bring up/down networking ● ntpdate.service loaded failed failed Set time via NTP ● speech-dispatcherd.service loaded failed failed Speech-Dispatcher, common interface to speech synthesizers ● systemd-udev-settle.service loaded failed failed udev Wait for Complete Device Initialization LOAD = Reflects whether the unit definition was properly loaded. ACTIVE = The high-level unit activation state, i.e. generalization of SUB. SUB = The low-level unit activation state, values depend on unit type. 6 loaded units listed. I can restart two of them, say: ntpdate.service systemd-udev-settle.service but not in a permanent way: they fail again after the next boot Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3.
furthermore: [root@mga6-64 alain4]# systemctl restart dhcpd.service Job for dhcpd.service failed because the control process exited with error code. See "systemctl status dhcpd.service" and "journalctl -xe" for details. [root@mga6-64 alain4]# systemctl restart speech-dispatcherd.service Job for speech-dispatcherd.service failed because the control process exited with error code. See "systemctl status speech-dispatcherd.service" and "journalctl -xe" for details. [root@mga6-64 alain4]# systemctl restart configure-printer@usb-006-002.service [root@mga6-64 alain4]# systemctl status configure-printer@usb-006-002.service ● configure-printer@usb-006-002.service - Configure Plugged-In Printer Loaded: loaded (/usr/lib/systemd/system/configure-printer@.service; static; vendor preset: disabled) Active: failed (Result: exit-code) since Thu 2020-01-09 13:09:46 CET; 12s ago Process: 8452 ExecStart=/usr/lib/udev/udev-configure-printer add usb-006-002 (code=exited, status=1/FAILURE) Main PID: 8452 (code=exited, status=1/FAILURE) janv. 09 13:09:46 mga6-64 udev-configure-printer[8452]: add usb-006-002 janv. 09 13:09:46 mga6-64 udev-configure-printer[8452]: device devpath is /devices/pci0000:00/0000:00:1a.1/usb6/6-1 janv. 09 13:09:46 mga6-64 udev-configure-printer[8452]: Device vendor/product is 03F0:4211 janv. 09 13:09:46 mga6-64 udev-configure-printer[8452]: MFG:HP MDL:Officejet 7300 series SERN:MY59EN80020407 serial:MY59EN80020407 janv. 09 13:09:46 mga6-64 udev-configure-printer[8452]: CheckAndInstallDrivers() janv. 09 13:09:46 mga6-64 udev-configure-printer[8452]: CheckInstalledDrivers() janv. 09 13:09:46 mga6-64 udev-configure-printer[8452]: MissingDriver() janv. 09 13:09:46 mga6-64 udev-configure-printer[8452]: FAIL HERE janv. 09 13:09:46 mga6-64 systemd[1]: configure-printer@usb-006-002.service: Main process exited, code=exited, status=1/FAILURE janv. 09 13:09:46 mga6-64 systemd[1]: configure-printer@usb-006-002.service: Failed with result 'exit-code'. [root@mga6-64 alain4]# systemctl restart network.service.service Failed to restart network.service.service: Unit network.service.service not found.
Peter Please give some background to this. You have flagged it 'Release media or process'. Meaning? Did this happen on first re-boot after an install? Or after an upgrade? Or after some updates to an existing M7 system? Or... Are all the failed services shown in 'MCC-System-Control System Services-Control Services by Enbling/Disabling them' as being to start at startup?
Keywords: (none) => NEEDINFOCC: (none) => lewyssmith
(In reply to Lewis Smith from comment #2) > Peter > Please give some background to this. You have flagged it 'Release media or > process'. Meaning? because I didn't know how to flag it > Did this happen on first re-boot after an install? > Or after an upgrade? > Or after some updates to an existing M7 system? > Or... after the migration from M6 to M7 notice that the line: configure-printer@usb-006-002.service appears only when my printer HP-Officejet-7310 is on; this is related to bug 25369 > > Are all the failed services shown in 'MCC-System-Control System > Services-Control Services by Enbling/Disabling them' as being to start at > startup? no, there are many services indicated as "stopped" although they are quoted "as being to start at startup" I can't list them there are too many but globally, my systems work well
Unsure what component is involved, so assigning globally, CC base-system group.
Component: Release (media or process) => RPM PackagesAssignee: bugsquad => pkg-bugsCC: lewyssmith => basesystemKeywords: NEEDINFO => (none)Summary: six services fail after boot => After M6-M7 upgrade six services fail after boot
Mageia 7 is EOL since July 1st 2021. There will not have any further bugfix for this release. You are encouraged to upgrade to Mageia 8 as soon as possible. @reporter, if this bug still apply with Mageia 8, please let us know it. @packager, if you work on the Mageia 7 version of your package, please check the Mageia 8 package if issue is also present. In this case, please fix the Mageia 8 version instead. This bug report will be closed OLD if there is no further notice within 1st September 2021.
Hi bug reporter and hi assignee and others involved, Please reopen this bug report if it is still valid for Mageia 8 or 9(cauldron), and change "Version:" in the upper left of this report accordingly. This report is being closed as OLD because it was filed against Mageia 7, for which support ended on June 30th 2021. Thanks, Marja
Resolution: (none) => OLDStatus: NEW => RESOLVED