OpenSHH, cannot start

[hkjz]

huh,
i just had still unsolved problem with containers
viewtopic.php?f=78&t=49990&sid=25c67823 ... 8&start=10

so i've started VB, with Ubuntu Server, Server started (btw. is it that it never have GNU, just pure Linux?)
with a wish to connect them through SSH

I've downloaded on both systems - host MX and Machine UServer

Code: Select all

sudo apt install openssh-server

and wanted to check the

Code: Select all

systemctl status ssh

UServer works fine, it is Active (hehe i cannot copy text from there here),

but MX does not

Code: Select all

$ systemctl status ssh
Failed to get properties: No such interface ''

$ systemctl start ssh
Failed to start ssh.service: Unknown unit: ssh.service
See system logs and 'systemctl status ssh.service' for details.

although enable works

Code: Select all

$ sudo systemctl enable ssh
Synchronizing state of ssh.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable ssh

but I've got stuck

[timkb4cq]

systemctl is a systemd command.
MX does not, by default, use systemd.

The equivalent commands for sysvinit are:
sudo service ssh start
sudo service ssh status

[hkjz]

:))
thanks
most probably good to know


place to research about this topic, can be found here
https://mxlinux.org/wiki/system/systemd/

[venik212]

MX Linux users are urged to stay away from systemd. In trying to use ssh, I tried:
sudo service ssh start and sudo service ssh status which are the recommended replacement ssh commands under sysvinit, but both returned an error:
ssh: unrecognized service

What's going on?

[SwampRabbit]

MX Linux users are urged to stay away from systemd. In trying to use ssh, I tried:
sudo service ssh start and sudo service ssh status which are the recommended replacement ssh commands under sysvinit, but both returned an error:
ssh: unrecognized service

What's going on?

Just to be clear we don't "urge" anyone to stay away from anything they want to use.
We give users the actual choice to use whatever init system they want.

Did you check to see if openssh-server is installed?

[venik212]

Sorry-- I think the words I read were: "We strongly recommend.." or something to this effect In any event, when I got the error message openssh-server was, in fact, installed, so I was puzzled. However, I found that using Warpinator to transfer files between machines was much easier, so the issue is no longer pressing.

[eriefisher]

Going from memory here, I believe you need to start the daemon, sshd on the server side. It will listen for connection requests.

[figueroa]

When you install the OpenSSH server on MX, the sshd (server daemon) starts automatically and will be restarted every time you boot. You can confirm this from the terminal by entering the following:

Code: Select all

ps ax | grep sshd

and if you see a line with sshd, the server is running and, by default, listening for a connection on port 22.

You can adjust the settings for the server, i.e. default port, by editing the file at /etc/ssh/sshd_config

[SwampRabbit]

Sorry-- I think the words I read were: "We strongly recommend.." or something to this effect In any event, when I got the error message openssh-server was, in fact, installed, so I was puzzled. However, I found that using Warpinator to transfer files between machines was much easier, so the issue is no longer pressing.

No need to be sorry, I actually just checked and we state

MX Linux ships with systemd present but disabled by default. The MX Linux team strongly urges users to remain with this configuration which uses sysvinit instead.

So yes I guess that can be misunderstood, but the way I take it and understand our stance is that we are trying to focus on what I underlined. And this is because everything is tested under sysvinit, not everything is tested under systemd, and for the average user it benefits them to stick with our default.

But that you for bringing it up, we can look at rephrasing it maybe.

[venik212]

Thanks for your response. The ssh issue is not so important for me-- other issues (screwed up return from suspend, for instance-- are much more annoying. I did find a way around that one, too, but it is surprising and annoying to have a fresh installation of a highly regarded OS, and then have to trick it with workarounds. On the other hand, I guess that is the price I have to pay for being Ubuntu/Mint free...;-)