Re: [systemd-devel] machinectl login machine fails systemd 219
On Wed, 2015-04-22 at 22:25 +0200, Lennart Poettering wrote: On Fri, 17.04.15 18:40, Keller, Jacob E (jacob.e.kel...@intel.com) wrote: On Wed, 2015-04-15 at 00:07 +0200, Stefan Tatschner wrote: On Di, 2015-04-14 at 21:56 +, 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 ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] machinectl login machine fails systemd 219
On Fri, 17.04.15 18:40, Keller, Jacob E (jacob.e.kel...@intel.com) wrote: On Wed, 2015-04-15 at 00:07 +0200, Stefan Tatschner wrote: On Di, 2015-04-14 at 21:56 +, 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 -- Lennart Poettering, Red Hat ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] machinectl login machine fails systemd 219
On Wed, 2015-04-15 at 00:07 +0200, Stefan Tatschner wrote: On Di, 2015-04-14 at 21:56 +, 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. Any specific tips for debugging it? Regards, Jake ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] machinectl login machine fails systemd 219
On Fri, 2015-04-17 at 18:40 +, Keller, Jacob E wrote: On Wed, 2015-04-15 at 00:07 +0200, Stefan Tatschner wrote: On Di, 2015-04-14 at 21:56 +, 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. Any specific tips for debugging it? Regards, Jake ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel For reference, here is the output of systemd-machined if I set SYSTEMD_LOG_LEVEL=debug Apr 17 15:08:42 jbrandeb-host.jf.intel.com systemd[1]: Starting Virtual Machine and Container Registration Service... Apr 17 15:08:42 jbrandeb-host.jf.intel.com systemd-machined[21619]: Sent message type=method_call sender=n/a destination=org.freedesktop.DBus object=/org/freedesktop/DBus interface=org.freedesktop.DBus member=Hello cookie=1 reply_cookie=0 error=n/a Apr 17 15:08:42 jbrandeb-host.jf.intel.com systemd-machined[21619]: Got message type=method_return sender=org.freedesktop.DBus destination=:1.636 object=n/a interface=n/a member=n/a cookie=1 reply_cookie=1 error=n/a Apr 17 15:08:42 jbrandeb-host.jf.intel.com systemd-machined[21619]: Sent message type=method_call sender=n/a destination=org.freedesktop.DBus object=/org/freedesktop/DBus interface=org.freedesktop.DBus member=AddMatch cookie=2 reply_cookie=0 error=n/a Apr 17 15:08:42 jbrandeb-host.jf.intel.com systemd-machined[21619]: Sent message type=method_call sender=n/a destination=org.freedesktop.DBus object=/org/freedesktop/DBus interface=org.freedesktop.DBus member=AddMatch cookie=3 reply_cookie=0 error=n/a Apr 17 15:08:42 jbrandeb-host.jf.intel.com systemd-machined[21619]: Sent message type=method_call sender=n/a destination=org.freedesktop.DBus object=/org/freedesktop/DBus interface=org.freedesktop.DBus member=AddMatch cookie=4 reply_cookie=0 error=n/a Apr 17 15:08:42 jbrandeb-host.jf.intel.com systemd-machined[21619]: Sent message type=method_call sender=n/a destination=org.freedesktop.DBus object=/org/freedesktop/DBus interface=org.freedesktop.DBus member=AddMatch cookie=5 reply_cookie=0 error=n/a Apr 17 15:08:42 jbrandeb-host.jf.intel.com systemd-machined[21619]: Sent message type=method_call sender=n/a destination=org.freedesktop.systemd1 object=/org/freedesktop/systemd1 interface=org.freedesktop.systemd1.Manager member=Subscribe cookie=6 reply_cookie=0 error=n/a Apr 17 15:08:42 jbrandeb-host.jf.intel.com systemd-machined[21619]: Sent message type=method_call sender=n/a destination=org.freedesktop.DBus object=/org/freedesktop/DBus interface=org.freedesktop.DBus member=RequestName cookie=7 reply_cookie=0 error=n/a Apr 17 15:08:42 jbrandeb-host.jf.intel.com systemd-machined[21619]: Sent message type=method_call sender=n/a destination=org.freedesktop.systemd1 object=/org/freedesktop/systemd1/unit/nspawn_40gitbucket_2eservice interface=org.freedesktop.DBus.Properties member=Get cookie=8 reply_cookie=0 error=n/a Apr 17 15:08:42 jbrandeb-host.jf.intel.com systemd[1]: Started Virtual Machine and Container Registration Service. Apr 17 15:08:42 jbrandeb-host.jf.intel.com systemd-machined[21619]: New machine gitbucket. Apr 17 15:08:42 jbrandeb-host.jf.intel.com systemd-machined[21619]: Sent message type=signal sender=n/a destination=n/a object=/org/freedesktop/machine1 interface=org.freedesktop.machine1.Manager member=MachineNew cookie=9 reply_cookie=0 error=n/a Apr 17 15:08:42 jbrandeb-host.jf.intel.com systemd-machined[21619]: systemd-machined running as pid 21619 Apr 17 15:08:42 jbrandeb-host.jf.intel.com systemd-machined[21619]: Got message type=signal sender=org.freedesktop.DBus destination=:1.636 object=/org/freedesktop/DBus interface=org.freedesktop.DBus member=NameAcquired cookie=2 reply_cookie=0 error=n/a Apr 17 15:08:42 jbrandeb-host.jf.intel.com systemd-machined[21619]: Got message type=signal sender=org.freedesktop.DBus destination=:1.636 object=/org/freedesktop/DBus interface=org.freedesktop.DBus member=NameAcquired cookie=7 reply_cookie=0 error=n/a Apr 17 15:08:42 jbrandeb-host.jf.intel.com systemd-machined[21619]: Got message type=method_call sender=:1.635
[systemd-devel] machinectl login machine fails systemd 219
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. Thanks for the help. Regards, Jake ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] machinectl login machine fails systemd 219
On Di, 2015-04-14 at 21:56 +, 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 ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
