bug#34580: Service ssh-daemon could not be started

Well, now that I actually test it - yes. But I said it had not because the 'herd status ssh-daemon' message indicated that it isn't running: root@janus ~# herd status ssh-daemon Status of ssh-daemon: It is stopped. It is enabled. Provides (ssh-daemon). Requires (syslogd loopback). Conf

bug#34580: Service ssh-daemon could not be started

Hi Brant, Thanks for sending the log! "Brant Gardner" skribis: > 284 09:31:59 socket(AF_UNIX, SOCK_DGRAM|SOCK_CLOEXEC, 0) = 4 <0.13> > 284 09:31:59 connect(4, {sa_family=AF_UNIX, sun_path="/dev/log"}, 110) = 0 > <0.14> > 284 09:31:59 sendto(4, "<38>Oct 9 09:31:59 sshd[284]: Serv

bug#34580: Service ssh-daemon could not be started

I went looking for the pid to answer Ludo's question and didn't find strace, and the ssh command line was wrong so I got suspicious. After searching a bit, I found the problem: I'm an idiot. 'make' apparently did not succeed after all and I simply failed to catch it. I went back and re-execut

bug#34580: Service ssh-daemon could not be started

Hi Danny! Danny Milosavljevic skribis: > So we could have a one-shot service "term-auto" which checks /proc/cmdline > (which can't change until the next reboot anyway), and if there's a serial > console, register a new (normal) service "term-ttyACM0" or whatever. > Otherwise > it would just no

bug#34580: Service ssh-daemon could not be started

Danny Milosavljevic skribis: > On second thought, maybe it would be easiest to make term-auto "succeed" when > it can't find that serial console. Shepherd would think everything is a-ok > and > nobody would tell it any better :P Well, that’s true! :-) Ludo’.

bug#34580: Service ssh-daemon could not be started

On second thought, maybe it would be easiest to make term-auto "succeed" when it can't find that serial console. Shepherd would think everything is a-ok and nobody would tell it any better :P pgpX_bhuaNlLm.pgp Description: OpenPGP digital signature

bug#34580: Service ssh-daemon could not be started

Hi everyone, On Sat, 28 Sep 2019 19:44:16 +0200 Ludovic Courtès wrote: > ‘term-auto’ is actually something that doesn’t start; it’s confusing, we > should present it differently, maybe as a one-shot service. term-auto automatically provides a shell on the console if that is a serial console. M

bug#34580: Service ssh-daemon could not be started

Hi, "pelzflorian (Florian Pelz)" skribis: > Perhaps /tmp is the wrong directory to store such an early log? No, that’s fine. /tmp is accessible at that point. > I have a Guix virtual machine where ssh-daemon, httpd, php-fpm and > term-auto cannot be started on boot. ‘term-auto’ is actually

bug#34580: Service ssh-daemon could not be started

"Brant Gardner" skribis: > Okay, I did those steps exactly: > > - clone > - patch -p1 < your-patch > - ./bootstrap > - ./configure --localstatedir=/var > - make check > - sudo -E ./pre-inst-env guix system reconfigure /path/to/myconfig.scm > - reboot > > I had no issues or errors at

bug#34580: Service ssh-daemon could not be started

On Sat, Sep 28, 2019 at 07:38:49AM -0500, Brant Gardner wrote: > Hi Ludo; > > Okay, I did those steps exactly: > > - clone > - patch -p1 < your-patch > - ./bootstrap > - ./configure --localstatedir=/var > - make check > - sudo -E ./pre-inst-env guix system reconfigure /path/to/myconfi

bug#34580: Service ssh-daemon could not be started

Hi Ludo; Okay, I did those steps exactly: - clone - patch -p1 < your-patch - ./bootstrap - ./configure --localstatedir=/var - make check - sudo -E ./pre-inst-env guix system reconfigure /path/to/myconfig.scm - reboot I had no issues or errors at any step and on reboot ssh-daemon tr

bug#34580: Service ssh-daemon could not be started

Hi Brant, "Brant Gardner" skribis: > Going to show my ignorance here - I've contributed some packages by > making things in a 'guix environment' and then extracting patches, but > what you need me to do is activate a configuration change in a 'live' > guix install (and on a service rather than a

bug#34580: Service ssh-daemon could not be started

Hi Ludo; Going to show my ignorance here - I've contributed some packages by making things in a 'guix environment' and then extracting patches, but what you need me to do is activate a configuration change in a 'live' guix install (and on a service rather than a package, also new-ish to me) so

bug#34580: Service ssh-daemon could not be started

Hi Brand, "Brant Gardner" skribis: > I'll cheerfully do the experiment, but I don't know how - can you direct me > for how to add strace where you need it to a booting system? You could try something like the patch below. When ‘ssh-daemon’ fails to start, you’ll have to make sure to grab /tmp

bug#34580: Service ssh-daemon could not be started

I'll cheerfully do the experiment, but I don't know how - can you direct me for how to add strace where you need it to a booting system? -- Brant Gardner On Tue, Sep 24, 2019, at 03:08, Ludovic Courtès wrote: > Hi Brant, > > "Brant Gardner" skribis: > > > The most useful thing I could find in

bug#34580: Service ssh-daemon could not be started

Hi Brant, "Brant Gardner" skribis: > The most useful thing I could find in the logs: > > Sep 19 15:30:46 localhost sshd[261]: Server listening on 0.0.0.0 port 22. > Sep 19 15:31:19 localhost shepherd[1]: Service ssh-daemon could not be > started. > Sep 19 15:39:58 localhost sshd[585]: Server li

bug#34580: Service ssh-daemon could not be started

Adding my nickel here, I observed the exact same behavior yesterday. I have several Guix System instances, this is currently the only one that has exhibited the problem of ssh failing to start and logging no messages about it. Networking: (static-networking-service "enp1s0" "192.168.1.253" #

bug#34580: Service ssh-daemon could not be started

On Thu, Mar 14, 2019 at 06:11:21PM -0400, Leo Famulari wrote: > Reinstallation did not help. Hm, it's working now! It did not work after installing Guix System 0.16.0 but after I updated to the latest (pull & reconfigure) it started to work. Quite strange... signature.asc Description: PGP signat

bug#34580: Service ssh-daemon could not be started

On Wed, Feb 20, 2019 at 05:51:54PM -0500, Leo Famulari wrote: > For now I am still using Shepherd 0.3 on that machine :/ Since a few days ago this workaround no longer works :( > I plan to reinstall from scratch soon. Reinstallation did not help. signature.asc Description: PGP signature

bug#34580: Service ssh-daemon could not be started

Hi Andreas, I have nothing to contribute, unfortunately, except to confirm that I continue to see this problem. I have seen it for months. At this point, I actually can't remember a time when SSH didn't fail to start in this mysterious manner. I'll see if I can reproduce the issue in a VM... N

bug#34580: Service ssh-daemon could not be started

On Thu, Feb 21, 2019 at 12:08:07AM +0100, Andreas Enge wrote: > It looks as if ssh-keygen takes too long; this is called from > openssh-activation in services/ssh.scm, with a comment > "Generate missing host keys". Are these regenerated at each boot? > If yes, is there a race condition, one action

bug#34580: Service ssh-daemon could not be started

On Wed, Feb 20, 2019 at 05:51:54PM -0500, Leo Famulari wrote: > On Wed, Feb 20, 2019 at 11:48:02PM +0100, Andreas Enge wrote: > > I suppose so. I would be happy to provide further information, but there is > > not much to see in the log files. I grepped for "ssh" in /var/log/messages. The failure

bug#34580: Service ssh-daemon could not be started

On Wed, Feb 20, 2019 at 11:48:02PM +0100, Andreas Enge wrote: > I suppose so. I would be happy to provide further information, but there is > not much to see in the log files. Yes, there is not much to go on. For now I am still using Shepherd 0.3 on that machine :/ I plan to reinstall from scrat

bug#34580: Service ssh-daemon could not be started

On Wed, Feb 20, 2019 at 05:21:58PM -0500, Leo Famulari wrote: > I wonder if this is another instance of ? I suppose so. I would be happy to provide further information, but there is not much to see in the log files. Andreas

bug#34580: Service ssh-daemon could not be started

On Tue, Feb 19, 2019 at 10:21:26PM +0100, Andreas Enge wrote: > Hello, > > twice in a row at work (on harbourfront) and now twice in a row at home > (on dover) I am in a situation where sshd does not start on Guix machines. > Networking is available (the machines can be pinged), and I have to log

bug#34580: Service ssh-daemon could not be started

Hello, twice in a row at work (on harbourfront) and now twice in a row at home (on dover) I am in a situation where sshd does not start on Guix machines. Networking is available (the machines can be pinged), and I have to log in via a console and execute "herd start ssh-daemon" by hand. Here is t