[systemd-devel] Socket activated SSHD service showing up as a failure when the client connection fReply-To:

Roger Qiu roger.qiu at polycademy.com
Wed Jul 16 20:37:12 PDT 2014


You  mean something like this:

```
$ cat /nix/store/wr8r8jrj204q3i0v4vfav8m63ssnv8w1-unit/sshd at .service
[Unit]
Description=SSH Daemon

[Service]
Environment="LD_LIBRARY_PATH=/nix/store/sk3017fxx2vhj69saizk5634y3w6hqhn-systemd-212/lib"
Environment="LOCALE_ARCHIVE=/nix/store/5jxnz56h6ya1wy0dvcll65vkkx9679g4-glibc-locales-2.19/lib/locale/locale-archive"
Environment="PATH=/nix/store/2wc50fcn54axkg2kk71jm2r5h0w5rbh6-openssh-6.6p1/bin:/nix/store/qlg0baw29r7fj4isc2x47c05d8q7br2j-gawk-4.1.0/bin:/nix/store/xdswdgz11w9lm9n9bzb6spl7dj45s2x2-coreutils-8.21/bin:/nix/store/sls52f6fkpqfs0kj4w0k525v57zrsz9x-findutils-4.4.2/bin:/nix/store/937i66g191shz0hwzll61vmi0zvy3gwy-gnugrep-2.14/bin:/nix/store/93wabgii15q4d74fqgcpfka1qy42igr4-gnused-4.2.2/bin:/nix/store/sk3017fxx2vhj69saizk5634y3w6hqhn-systemd-212/bin:/nix/store/2wc50fcn54axkg2kk71jm2r5h0w5rbh6-openssh-6.6p1/sbin:/nix/store/qlg0baw29r7fj4isc2x47c05d8q7br2j-gawk-4.1.0/sbin:/nix/store/xdswdgz11w9lm9n9bzb6spl7dj45s2x2-coreutils-8.21/sbin:/nix/store/sls52f6fkpqfs0kj4w0k525v57zrsz9x-findutils-4.4.2/sbin:/nix/store/937i66g191shz0hwzll61vmi0zvy3gwy-gnugrep-2.14/sbin:/nix/store/93wabgii15q4d74fqgcpfka1qy42igr4-gnused-4.2.2/sbin:/nix/store/sk3017fxx2vhj69saizk5634y3w6hqhn-systemd-212/sbin"


X-StopIfChanged=false
ExecStart=/nix/store/2wc50fcn54axkg2kk71jm2r5h0w5rbh6-openssh-6.6p1/sbin/sshd 
-i -f /nix/store/ai2a554az21b5zhd1kamcznbim4gd924-sshd_config
ExecStartPre=/nix/store/i5wnidc4707k3pgcbhyjq3qb4ajgyx5n-unit-script/bin/sshd at -pre-start
KillMode=process
StandardInput=socket
SuccessExitStatus=255
```

If I add that in, what about the normal exit status of "0"? Would that 
override the successful exit code of 0?

Thanks,
Roger

On 17/07/2014 12:55 PM, Zbigniew Jędrzejewski-Szmek wrote:
> On Thu, Jul 17, 2014 at 12:53:01PM +1000, Roger Qiu wrote:
>> Hello,
>>
>> This is the log of the status codes:
>>
>> ```
>>sshd at 3-10.0.2.15:22-10.0.2.2:51014.service - SSH Daemon (10.0.2.2:51014)
>>     Loaded: loaded
>> (/nix/store/wr8r8jrj204q3i0v4vfav8m63ssnv8w1-unit/sshd at .service)
>>     Active: failed (Result: exit-code) since Thu 2014-07-17 02:24:01
>> UTC; 2min 21s ago
>>    Process: 3102 ExecStart=/nix/store/2wc50fcn54axkg2kk71jm2r5h0w5rbh6-openssh-6.6p1/sbin/sshd
>> -i -f /nix/store/ai2a554az21b5zhd1kamcznbim4gd924-sshd_config
>> (code=exited, status=255)
>>    Process: 3100 ExecStartPre=/nix/store/i5wnidc4707k3pgcbhyjq3qb4ajgyx5n-unit-script/bin/sshd at -pre-start
>> (code=exited, status=0/SUCCESS)
>>   Main PID: 3102 (code=exited, status=255)
>>
>> Jul 17 02:23:55 matrix-node systemd[1]: Started SSH Daemon (10.0.2.2:51014).
>> Jul 17 02:24:01 matrix-node systemd[1]:
>> sshd at 3-10.0.2.15:22-10.0.2.2:51014.service: main process exited,
>> code=exited, status=255/n/a
>> Jul 17 02:24:01 matrix-node systemd[1]: Unit
>> sshd at 3-10.0.2.15:22-10.0.2.2:51014.service entered failed state.
>> ```
>>
>> Perhaps it's 255?
> That looks like -1, but whatever. Does it work if
> you add SuccessExitStatus=255?
>
> Zbyszek



More information about the systemd-devel mailing list