systemd post-install failure
Booting master today I had a systemd fault. Enabling debugging I captured the (attached) output. The gist of which is:
.....
Spawned /lib/systemd/system-generators/systemd-system-update-generator as 81
.....
Received SIGCHLD from PID 81 (n/a).
Got SIGCHLD for process 90 (systemd-sysctl)
Child 90 died (code=exi
So, looking into systemd-system-update-generator, it seems this is what takes card of the post install scripts, which I know we're having problems with.
Is there anything I can do to help?
Cheers,
Signature · 5 lines
Jack Mitchell ([email protected]) Embedded Systems Engineer http://www.embed.me.uk --
Quoted 6 lines · Jack Mitchell
Booting master today I had a systemd fault. Enabling debugging I captured the (attached) output. The gist of which is:
So, looking into systemd-system-update-generator, it seems this is what takes card of the post install scripts, which I know we're having problems with.
Not quite - the system update generator would be used if we were using systemd's native systemd update protocol, which we're not. This generator shouldn't do anything unless you've got a symlink /system-update (see
http://freedesktop.org/wiki/Software/systemd/SystemUpdates for the details).
Ross
Quoted 7 lines · Ross
Quoted 6 lines · Jack Mitchell
Booting master today I had a systemd fault. Enabling debugging I captured the (attached) output. The gist of which is:
So, looking into systemd-system-update-generator, it seems this is what takes card of the post install scripts, which I know we're having problems with.
Quoted 8 lines
Not quite - the system update generator would be used if we were using systemd's native systemd update protocol, which we're not. This generator shouldn't do anything unless you've got a symlink /system-update (see
http://freedesktop.org/wiki/Software/systemd/SystemUpdates for the details).Ross
Ah, ok then, I don't have a /system-update. So square one, any ideas why this would have suddenly flagged up? I was building and booting fine on Wed/Thurs. That was the only useful bit of the debug log I could determine...
Signature · 5 lines
Jack Mitchell ([email protected]) Embedded Systems Engineer http://www.embed.me.uk --
Quoted 4 lines · Jack Mitchell
Ah, ok then, I don't have a /system-update. So square one, any ideas why this would have suddenly flagged up? I was building and booting fine on Wed/Thurs. That was the only useful bit of the debug log I could determine...
That log isn't massively useful, can you explain exactly what isn't working?
Ross
Quoted 8 lines · Ross
Quoted 4 lines · Jack Mitchell
Ah, ok then, I don't have a /system-update. So square one, any ideas why this would have suddenly flagged up? I was building and booting fine on Wed/Thurs. That was the only useful bit of the debug log I could determine...
That log isn't massively useful, can you explain exactly what isn't working?
Ross
Tell me about it, I boot, systemd crashes, I get a capture of the serial log up to where it crashed.
I've managed to get a tiny little bit more output that may shed a little bit more information.
_*scrap that*_
My power supply was crapping out on me, so when the going got a bit tough the cpu required some more amps and bam, dead system.
Sorry for the noise. Should have checked that earlier.
Signature · 5 lines
Jack Mitchell ([email protected]) Embedded Systems Engineer http://www.embed.me.uk --