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

[Roger Qiu]

I've googled around and saw that 255 error code comes up a lot. But most 
resources talked about "ssh" not necessarily the "sshd". If we ignore 
255 code, is it possible we're also ignoring some other real errors, and 
not just the client failing the connection? Basically I would like sshd 
to report an error,  if it is indeed an error from the host's side, not 
the client's side.

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