|
Bugzilla – Full Text Bug Listing |
| Summary: | systemd-random-seed-load.service failed | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 12.3 | Reporter: | David Kerkhof <dutchkind> |
| Component: | Basesystem | Assignee: | E-mail List <bnc-team-screening> |
| Status: | RESOLVED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | fcrozat, jnelson-suse |
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | x86-64 | ||
| OS: | openSUSE 12.3 | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
David Kerkhof
2013-04-07 10:37:42 UTC
After reboot I run: systemctl status systemd-random-seed-load.service
systemd-random-seed-load.service - Load Random Seed
Loaded: loaded (/etc/systemd/system/systemd-random-seed-load.service; static)
Active: failed (Result: exit-code) since Sun, 2013-04-07 12:38:40 CEST; 44s ago
Process: 531 ExecStart=/lib/systemd/systemd-random-seed load (code=exited, status=203/EXEC)
CGroup: name=systemd:/system/systemd-random-seed-load.service
Apr 07 12:38:40 dklinux-lt.dknet systemd[1]: systemd-random-seed-load.service: main process exited, code=exited, status=203/EXEC
Apr 07 12:38:40 dklinux-lt.dknet systemd[1]: Failed to start Load Random Seed.
Apr 07 12:38:40 dklinux-lt.dknet systemd[1]: Unit systemd-random-seed-load.service entered failed state
Booting with systemd debug enabled gives me this: 2013-04-07T16:51:18.802604+02:00 dklinux-lt systemd[275]: Failed at step EXEC spawning /lib/systemd/systemd-random-seed: No such file or directory 2013-04-07T16:51:18.802734+02:00 dklinux-lt systemd[1]: systemd-random-seed-load.service: main process exited, code=exited, status=203/EXEC 2013-04-07T16:51:18.802743+02:00 dklinux-lt systemd[1]: Failed to start Load Random Seed. Hope this helps to solve the problem hmm, why do you have /etc/systemd/system/systemd-random-seed-load.service in the first place ? Try removing this file, it is overriding the packaged version of the file which has the correct path for the binary. Why I have that file? Good question, because it was not removed during a zypper dup from 12.2 to 12.3? This is an installation that may go back as far as 11.3 or before, always upgraded. So there may be something that didn't upgrade correctly this time. And yes, removing that /etc/systemd/system/systemd-random-seed-load.service removed the error altogether and I see at boot that /var/lib/random-seed has the boot time stamp, so it seems to work. Thanks. Maybe it is something that should have been removed by the newer rpm? /etc/systemd/system/systemd-random-seed-load.service is not created by systemd package (I've check in the package history and we never created this file in 11.4, 12.1, 12.2, 12.3) and upgrading the package shouldn't remove file in /etc/systemd/system just because they are there (maybe sysadmin put them here for a reason). Well, in that case, I don't know. But I upgraded my laptop and desktop and they both have (had) the same thing, though both have an encrypted swap. But I remember I had problems in the beginning of systemd with the encrypted /tmp that I was using at that time which didn't get mounted rw for users, or something like that and you were involved and provided a version of some systemd packages to try. Could it be that it was in those packages? I myself have never created systemd stuff before, so I am sure it wasn't me, for the rest I have hardly any repos enabled, only packman, google-talkplugin and KDE:Extra (from which I have only two small packages installed) I do not find the file when looking in yast software, so no idea. But maybe I am the only user, so, for me it is fixed. ahh, that must be that, I remember now, I probably asked you to do some tests. Closing as FIXED. I have the same problem
Happened on upgrade from 12.2 to 12.3.
Looking at the timestamp of the file /etc/systemd/system/systemd-random-seed-load.service, "15 Sep 2012", it didn't happen recently.
I am very nearly sure I didn't change anything, and I have no encrypted FS on this machine.
turnip:~ # systemctl status systemd-random-seed-load.service
systemd-random-seed-load.service - Load Random Seed
Loaded: loaded (/etc/systemd/system/systemd-random-seed-load.service; static)
Active: failed (Result: exit-code) since Wed, 2013-05-01 15:13:02 CDT; 4s ago
Process: 9959 ExecStart=/lib/systemd/systemd-random-seed load (code=exited, status=203/EXEC)
CGroup: name=systemd:/system/systemd-random-seed-load.service
May 01 15:13:02 turnip.local systemd[1]: Starting Load Random Seed...
May 01 15:13:02 turnip.local systemd[1]: systemd-random-seed-load.service: main process exited, code=exited, status=203/EXEC
May 01 15:13:02 turnip.local systemd[1]: Failed to start Load Random Seed.
May 01 15:13:02 turnip.local systemd[1]: Unit systemd-random-seed-load.service entered failed state
turnip:~ # ls /lib/systemd/systemd-random-seed
ls: cannot access /lib/systemd/systemd-random-seed: No such file or directory
turnip:~ # ls -la /etc/systemd/system/systemd-random-seed-load.service
-rw-r--r-- 1 root root 573 Sep 15 2012 /etc/systemd/system/systemd-random-seed-load.service
turnip:~ # cat !$
cat /etc/systemd/system/systemd-random-seed-load.service
# This file is part of systemd.
#
# systemd is free software; you can redistribute it and/or modify it
# under the terms of the GNU General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
[Unit]
Description=Load Random Seed
DefaultDependencies=no
Wants=local-fs.target
Conflicts=shutdown.target
After=systemd-readahead-collect.service systemd-readahead-replay.service
Before=sysinit.target shutdown.target
[Service]
Type=oneshot
ExecStart=/lib/systemd/systemd-random-seed load
turnip:~ #
Same cause created the same effect. Remove /etc/systemd/system/systemd-random-seed-load.service file and everything will be fine. |