Re: [Xen-users] Debian 7 Dom0, Debian 8 DomU: Failed to start Login Service

[Charles <charles@xxxxxxxxxxxxxxxxxxxx>]

Thanks PryMar56/Mark :-)

Your suspicion about dbus was correct:

root@web2:~# dpkg -l dbus openssh-server
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/ ...
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name           Version      Architecture Description
+++-==============-============-============-=================================
un  dbus           <none>       <none>       (no description available)
ii  openssh-server 1:6.7p1-3    amd64        secure shell (SSH) ...

The output of the two commands you asked for is at
http://pastebin.com/9SmdQxnh

After running "apt-get install dbus" and rebooting, the "Failed to start
Login Service" boot message was fixed (ssh from the Dom0 to web2's IP
address did not work until sshd_config was relaxed but that is another
story).

Would you like any further investigation?

Best

Charles

On 22/02/15 02:06, Mark Pryor wrote:
> For boot to stall at systemd-logind means that dbus is missing and not
> installed.
> 
> This also explains why ssh is not listening.
> 
> Verify you have these packages:
> dpkg -l dbus
> dpkg -l openssh-server
> 
> While you are in domU console, can you paste:
> sudo journalctl -n800 | grep -Pi 'login|Reach|dbus|ssh'
> sudo systemctl list-unit-files | grep login | sort
> 
> regards,
> PryMar56
> 
> 
> On Saturday, February 21, 2015 8:51 AM, Charles
> <charles@xxxxxxxxxxxxxxxxxxxx> wrote:
> 
> 
> Hello Xen Users :-)
> 
> Can this bug be triggered by Xen?  It is unlikely Debian 8 has such an
> obvious bug.
> 
> Boot message: [FAILED] Failed to start Login Service.
> 
> What was done ...
> 
> On an established production Dom0 running Debian 7 Wheezy with multiple
> DomUs, all running Debian 7 Wheezy, created a DomU and installed Debian
> 8 (= Jessie aka testing) in it with:
> 
> xen-create-image \
>     --broadcast=192.168.42.255 \
>     --dist=testing \
>     --fs=ext4 \
>     --gateway=192.168.42.100 \
>     --hostname web2.hidden.org \
>     --ip=192.168.42.103 \
>     --lvm=blav2 \
>     --memory=2G \
>     --mirror=http://ftp.de.debian.org/debian/ \
>     --netmask=255.255.255.0 \
>     --size=30G \
>     --vifname=vif103.0
> 
> Edited the resulting /etc/xen/web2.hidden.org.cfg:
> 
> # diff /etc/xen/web2.hidden.org.cfg{.org,}
> 9a10
>> extra      = 'ipv6.disable=1'
> 13c14
> < memory      = '2G'
> ---
>> memory      = '2048'
> 38c39
> < vif        = [ 'ip=192.168.42.103
> ,mac=00:16:3E:E3:6D:F7,vifname=vif103.0' ]
> ---
>> vif        = [ 'ip=192.168.42.103, mac=00:16:3E:E3:6D:F7,
> script=/etc/xen/scripts/vif-bridge, vifname=vif103.0' ]
> 
> Created the DomU:
> 
> # cd /etc/xen && xl create web2.hidden.org.cfg
> 
> Was able to ping it but not to ssh into it.  Used xl console to connect
> to the console where saw the message above.
> 
> This was the second attempt; three weeks ago we saw the same error.
> 
> What to do?
> 
> Best
> 
> Charles
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxx
> http://lists.xen.org/xen-users
> 
> 

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users