* [ptxdist] systemd 232
@ 2016-11-28 17:02 Clemens Gruber
2016-11-29 8:46 ` Michael Olbrich
0 siblings, 1 reply; 5+ messages in thread
From: Clemens Gruber @ 2016-11-28 17:02 UTC (permalink / raw)
To: ptxdist
Hi,
did you already start working on updating systemd to version 232?
Thanks,
Clemens
PS: Any comments on the nginx patch yet? :)
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [ptxdist] systemd 232
2016-11-28 17:02 [ptxdist] systemd 232 Clemens Gruber
@ 2016-11-29 8:46 ` Michael Olbrich
2016-12-01 16:00 ` Clemens Gruber
0 siblings, 1 reply; 5+ messages in thread
From: Michael Olbrich @ 2016-11-29 8:46 UTC (permalink / raw)
To: ptxdist
Hi,
On Mon, Nov 28, 2016 at 06:02:51PM +0100, Clemens Gruber wrote:
> did you already start working on updating systemd to version 232?
I've started with it. But new systemd versions require more testing than
most packages.
> PS: Any comments on the nginx patch yet? :)
It's in my local testing branch. I'll comment on it later.
Michael
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [ptxdist] systemd 232
2016-11-29 8:46 ` Michael Olbrich
@ 2016-12-01 16:00 ` Clemens Gruber
2016-12-05 8:49 ` Michael Olbrich
0 siblings, 1 reply; 5+ messages in thread
From: Clemens Gruber @ 2016-12-01 16:00 UTC (permalink / raw)
To: ptxdist
Hi,
On Tue, Nov 29, 2016 at 09:46:14AM +0100, Michael Olbrich wrote:
> Hi,
>
> On Mon, Nov 28, 2016 at 06:02:51PM +0100, Clemens Gruber wrote:
> > did you already start working on updating systemd to version 232?
>
> I've started with it. But new systemd versions require more testing than
> most packages.
I just tried the ptxdist master version of systemd 232.
Looking good except for one problem:
rc-once.service: Main process exited, code=killed, status=15/TERM
rc-once.service: Unit entered failed state.
rc-once.service: failed with result 'signal'.
Because I am not doing anything different in /etc/rc.once.d/*, I assume
this has something to do with the update from 231 to 232.
Can you reproduce this?
For the record, in rc.once.d I have: ldconfig, machine-id and openssh.
Is there something in /lib/systemd/systemd-rc-once which could cause
this on systemd 232?
Thanks,
Clemens
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [ptxdist] systemd 232
2016-12-01 16:00 ` Clemens Gruber
@ 2016-12-05 8:49 ` Michael Olbrich
2016-12-05 13:47 ` Clemens Gruber
0 siblings, 1 reply; 5+ messages in thread
From: Michael Olbrich @ 2016-12-05 8:49 UTC (permalink / raw)
To: ptxdist
Hi,
On Thu, Dec 01, 2016 at 05:00:19PM +0100, Clemens Gruber wrote:
> On Tue, Nov 29, 2016 at 09:46:14AM +0100, Michael Olbrich wrote:
> > On Mon, Nov 28, 2016 at 06:02:51PM +0100, Clemens Gruber wrote:
> > > did you already start working on updating systemd to version 232?
> >
> > I've started with it. But new systemd versions require more testing than
> > most packages.
>
> I just tried the ptxdist master version of systemd 232.
>
> Looking good except for one problem:
> rc-once.service: Main process exited, code=killed, status=15/TERM
> rc-once.service: Unit entered failed state.
> rc-once.service: failed with result 'signal'.
>
> Because I am not doing anything different in /etc/rc.once.d/*, I assume
> this has something to do with the update from 231 to 232.
>
> Can you reproduce this?
>
> For the record, in rc.once.d I have: ldconfig, machine-id and openssh.
>
> Is there something in /lib/systemd/systemd-rc-once which could cause
> this on systemd 232?
I'm not aware of anything that would cause this. I just tried this
combination in my qemu test BSP and it works without problems.
Do you get a emergency shell? Anything else in the journal? How long does
it take to get the error? Maybe the service is killed by a timeout.
Michael
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [ptxdist] systemd 232
2016-12-05 8:49 ` Michael Olbrich
@ 2016-12-05 13:47 ` Clemens Gruber
0 siblings, 0 replies; 5+ messages in thread
From: Clemens Gruber @ 2016-12-05 13:47 UTC (permalink / raw)
To: ptxdist
Hi,
On Mon, Dec 05, 2016 at 09:49:23AM +0100, Michael Olbrich wrote:
> Hi,
>
> On Thu, Dec 01, 2016 at 05:00:19PM +0100, Clemens Gruber wrote:
> > I just tried the ptxdist master version of systemd 232.
> >
> > Looking good except for one problem:
> > rc-once.service: Main process exited, code=killed, status=15/TERM
> > rc-once.service: Unit entered failed state.
> > rc-once.service: failed with result 'signal'.
> >
> > Because I am not doing anything different in /etc/rc.once.d/*, I assume
> > this has something to do with the update from 231 to 232.
> >
> > Can you reproduce this?
> >
> > For the record, in rc.once.d I have: ldconfig, machine-id and openssh.
> >
> > Is there something in /lib/systemd/systemd-rc-once which could cause
> > this on systemd 232?
>
> I'm not aware of anything that would cause this. I just tried this
> combination in my qemu test BSP and it works without problems.
>
> Do you get a emergency shell? Anything else in the journal? How long does
> it take to get the error? Maybe the service is killed by a timeout.
>
> Michael
Thanks for your help, no emergency shell and nothing else in the
journal, looked like a normal boot except for that failed unit.
But I just noticed that the rc-once.service file in ptxdist projectroot
changed since I copied (and modified) it to add a dependency on rngd.service:
Mine did not have the IgnoreOnIsolate=true line. Adding it, solved the
problem!
Clemens
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2016-12-05 13:47 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-11-28 17:02 [ptxdist] systemd 232 Clemens Gruber
2016-11-29 8:46 ` Michael Olbrich
2016-12-01 16:00 ` Clemens Gruber
2016-12-05 8:49 ` Michael Olbrich
2016-12-05 13:47 ` Clemens Gruber
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox