[systemd-devel] machinectl login <machine> fails systemd 219

Keller, Jacob E jacob.e.keller at intel.com
Wed Apr 22 14:13:21 PDT 2015


On Wed, 2015-04-22 at 22:25 +0200, Lennart Poettering wrote:
> On Fri, 17.04.15 18:40, Keller, Jacob E (jacob.e.keller at intel.com) wrote:
> 
> > On Wed, 2015-04-15 at 00:07 +0200, Stefan Tatschner wrote:
> > > On Di, 2015-04-14 at 21:56 +0000, Keller, Jacob E wrote:
> > > > Failed to get machine PTY: Message did not receive a reply (timeout 
> > > > by message bus)
> > > > 
> > > > I get a notification on the machine itself that it started container
> > > > getty and then stopped it.
> > > > 
> > > > It worked earlier so I am not sure what changed. No one on google 
> > > > seems
> > > > to have this specific error.
> > > 
> > > There is a patch which fixes this problem:
> > > http://lists.freedesktop.org/archives/systemd-devel/2015
> > > -February/028603.html
> > > 
> > > git log --grep tells me that is has been already commited as
> > > f2273101c21bc59a390379e182e53cd4f07a7e71:
> > > 
> > > http://cgit.freedesktop.org/systemd/systemd/commit/?id=f2273101c21bc59a
> > > 390379e182e53cd4f07a7e71
> > > 
> > > 
> > > Stay tuned,
> > > Stefan
> > 
> > I still seem to have this issue with this. I am currently working on
> > compiling upstream git of systemd so I can try running machined from
> > there. Will let you know results.
> 
> Are you sure you updated both the client machinectl and the machined
> daemon and restarted it?
> 
> This works fine here with current git...
> 
> Lennart
> 

I probably didn't update both client and daemon. I'll double check
that :)

Regards,
Jake


More information about the systemd-devel mailing list