Re: ssh-daemon service fails to auto start
On Mon, Feb 12, 2018 at 09:02:44PM +0100, Martin Castillo wrote: > > On 06.02.2018 21:01, Leo Famulari wrote: > > On Sat, Jan 27, 2018 at 11:08:23PM +0100, Martin Castillo wrote: > >> my configuration is (similar to) desk,nossh.scm. > > > > Can you share the QEMU command line you use to run desk,nossh.scm? > > > > qemu-system-x86_64 -m 2048 -smp 2 -enable-kvm \ > -net nic,model=virtio \ > -net user,hostfwd=tcp::5561-: \ > -drive file=guixsd.img I built desk,nossh.scm like this: $ guix --version guix (GNU Guix) 63298f14c9679735c6c930e10b0e83391f01 [...] # No grafts to save disk space while debugging. Never do that in # production! $ guix system vm-image ~/tmp/desk-nossh.scm --no-grafts [...] /gnu/store/b3drd7s1mfsnmlc9j63dz5djni9k0y3v-qemu-image I copied the image file out of the store, made it writeable, and then ran it with your qemu invocation from above (QEMU 2.10.2 from Guix), and the SSHD was running after boot. Did you do anything differently? signature.asc Description: PGP signature
Re: ssh-daemon service fails to auto start
On 06.02.2018 21:01, Leo Famulari wrote: > On Sat, Jan 27, 2018 at 11:08:23PM +0100, Martin Castillo wrote: >> my configuration is (similar to) desk,nossh.scm. > > Can you share the QEMU command line you use to run desk,nossh.scm? > qemu-system-x86_64 -m 2048 -smp 2 -enable-kvm \ -net nic,model=virtio \ -net user,hostfwd=tcp::5561-: \ -drive file=guixsd.img -- GPG: 7FDE 7190 2F73 2C50 236E 403D CC13 48F1 E644 08EC signature.asc Description: OpenPGP digital signature
Re: ssh-daemon service fails to auto start
Martin Castillo writes: > On 29.01.2018 18:00, Ludovic Courtès wrote: >> Hi Martin, >> >> Martin Castillo skribis: >> >>> i have a problem with the ssh-service. I want it to autostart on system >>> boot. >>> >>> my configuration is (similar to) desk,nossh.scm. >> >> I tried this config in ‘guix system vm’ and sshd is automatically >> started on boot, as can be seen with ‘herd status ssh-daemon’ etc. >> >> Does this config work for you in ‘guix system vm’? > > No. > > >> Could you check /var/log/shepherd.log? It will tell you which services, >> besides sshd, failed to start. >> >> ‘ssh-daemon’ depends only on ‘syslogd’, so as long as ‘syslogd’ is >> started, ‘ssh-daemon’ should start. >> > > I checked /var/log/shepherd.log. Only user-homes and ssh-daemon could > not be started. > > Has this maybe to do with missing randomness to create keys? (Even > though there are already server keys.) > > Maybe shepherd should store the output of launched programs? Is that > really not possible? I can't be the first one to need that. > > Martin I have experienced this problem as well. SSH daemon fails to start, but unfortunately Shepherd has nothing useful to say about why. If I ever find a way to reproduce it reliably, I'll share that info. I think multiple people have reported this problem on IRC. It can't be a coincidence... -- Chris signature.asc Description: PGP signature
Re: ssh-daemon service fails to auto start
On Sat, Jan 27, 2018 at 11:08:23PM +0100, Martin Castillo wrote: > my configuration is (similar to) desk,nossh.scm. Can you share the QEMU command line you use to run desk,nossh.scm? signature.asc Description: PGP signature
Re: ssh-daemon service fails to auto start
On 29.01.2018 18:00, Ludovic Courtès wrote: > Hi Martin, > > Martin Castillo skribis: > >> i have a problem with the ssh-service. I want it to autostart on system >> boot. >> >> my configuration is (similar to) desk,nossh.scm. > > I tried this config in ‘guix system vm’ and sshd is automatically > started on boot, as can be seen with ‘herd status ssh-daemon’ etc. > > Does this config work for you in ‘guix system vm’? No. > Could you check /var/log/shepherd.log? It will tell you which services, > besides sshd, failed to start. > > ‘ssh-daemon’ depends only on ‘syslogd’, so as long as ‘syslogd’ is > started, ‘ssh-daemon’ should start. > I checked /var/log/shepherd.log. Only user-homes and ssh-daemon could not be started. Has this maybe to do with missing randomness to create keys? (Even though there are already server keys.) Maybe shepherd should store the output of launched programs? Is that really not possible? I can't be the first one to need that. Martin -- GPG: 7FDE 7190 2F73 2C50 236E 403D CC13 48F1 E644 08EC
Re: ssh-daemon service fails to auto start
Hi Martin, Martin Castillo skribis: > i have a problem with the ssh-service. I want it to autostart on system > boot. > > my configuration is (similar to) desk,nossh.scm. I tried this config in ‘guix system vm’ and sshd is automatically started on boot, as can be seen with ‘herd status ssh-daemon’ etc. Does this config work for you in ‘guix system vm’? > Can someone with more insight tell me, why sshd won't autostart? > shepherd tells me only 'ssh-daemon could not be started'. Thank you > shepherd, very helpful! :-) Could you check /var/log/shepherd.log? It will tell you which services, besides sshd, failed to start. ‘ssh-daemon’ depends only on ‘syslogd’, so as long as ‘syslogd’ is started, ‘ssh-daemon’ should start. You can view the dependency graph of Shepherd services with: guix system shepherd-graph config.scm | dot -Tpdf > graph.pdf HTH! Ludo’.
