You are not logged in.

#1 2018-12-11 09:54:34

majed17
Member
Registered: 2018-12-11
Posts: 37

ssh blocks access until service restart [solved]

Health be upon you, this happens after rebooting.
after reading many threads, i suspect the problem is that the home directory is on a different partition.
/etc/fstab

/dev/sda1           	/         	ext4      	rw,relatime	0 1

# UUID=20263103-4931-43c0-ba44-f9a15fec0172
/dev/sda5           	/home     	ext4      	rw,relatime	0 2

[em]# UUID=f3b30b3a-765e-4cec-aeb5-efca50646482
/dev/sda2           	none      	swap      	defaults,pri=-2	0 0

i'm logging from a user who is in the wheel group.

root ALL=(ALL) ALL
ameen ALL=(ALL) ALL

## Uncomment to allow members of group wheel to execute any command
# %wheel ALL=(ALL) ALL]

## Same thing without a password
%wheel ALL=(ALL) NOPASSWD: ALL

sshd_config

PermitRootLogin yes
#PermitRootLogin without-password

so if i reboot, i have to restart the sshd service to log in as ameen, otherwise it says connection refused even though
netstat -ln |grep 22

tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN
tcp6       0      0 :::22                   :::*                    LISTEN

who knows the solution?

Last edited by majed17 (2018-12-12 12:35:32)

Offline

#2 2018-12-11 15:00:02

RoundCube
Member
Registered: 2016-05-14
Posts: 42

Re: ssh blocks access until service restart [solved]

Maybe installing haveged helps.

Last edited by RoundCube (2018-12-11 15:00:18)

Offline

#3 2018-12-12 05:46:37

majed17
Member
Registered: 2018-12-11
Posts: 37

Re: ssh blocks access until service restart [solved]

what is that anyway?
and installing it didn't help.
I tried disabling ntpd and rebooting but with no avail.
Anything else?

Offline

#4 2018-12-12 05:50:55

jasonwryan
Anarchist
From: .nz
Registered: 2009-05-09
Posts: 30,426
Website

Re: ssh blocks access until service restart [solved]

1. Please edit your post and use code tags when pasting to the boards: https://wiki.archlinux.org/index.php/Co … s_and_code

2. It increases the entropy available to the system for cryptographic exchanges, a known issue with recent kernels

3. Please paste the full journal output for a failed session.

4. Try the -lts kernel and see if you can reproduce.


Moving to NC...


Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438

Offline

#5 2018-12-12 06:20:35

majed17
Member
Registered: 2018-12-11
Posts: 37

Re: ssh blocks access until service restart [solved]

Dec 12 09:13:06 ntp.rup systemd-logind[297]: New session 1 of user root.
Dec 12 09:13:06 ntp.rup systemd[1]: Created slice User Slice of UID 0.
Dec 12 09:13:06 ntp.rup systemd[1]: Starting User Runtime Directory /run/user/0...
Dec 12 09:13:06 ntp.rup systemd[1]: Started User Runtime Directory /run/user/0.
Dec 12 09:13:06 ntp.rup audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user-runtime-dir@0 comm="systemd" exe>
Dec 12 09:13:06 ntp.rup systemd[1]: Starting User Manager for UID 0...
Dec 12 09:13:06 ntp.rup kernel: audit: type=1130 audit(1544595186.129:30): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user-runti>
Dec 12 09:13:06 ntp.rup systemd[338]: pam_unix(systemd-user:session): session opened for user root by (uid=0)
Dec 12 09:13:06 ntp.rup kernel: audit: type=1006 audit(1544595186.159:31): pid=338 uid=0 old-auid=4294967295 auid=0 tty=(none) old-ses=429>
Dec 12 09:13:06 ntp.rup systemd[338]: Starting D-Bus User Message Bus Socket.
Dec 12 09:13:06 ntp.rup systemd[338]: Listening on p11-kit server.
Dec 12 09:13:06 ntp.rup systemd[338]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers).
Dec 12 09:13:06 ntp.rup systemd[338]: Listening on GnuPG network certificate management daemon.
Dec 12 09:13:06 ntp.rup systemd[338]: Reached target Paths.
Dec 12 09:13:06 ntp.rup systemd[338]: Reached target Timers.
Dec 12 09:13:06 ntp.rup systemd[338]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
Dec 12 09:13:06 ntp.rup systemd[338]: Listening on GnuPG cryptographic agent and passphrase cache.
Dec 12 09:13:06 ntp.rup systemd[338]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
Dec 12 09:13:06 ntp.rup systemd[338]: Listening on D-Bus User Message Bus Socket.
Dec 12 09:13:06 ntp.rup systemd[338]: Reached target Sockets.
Dec 12 09:13:06 ntp.rup systemd[338]: Reached target Basic System.
Dec 12 09:13:06 ntp.rup audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user@0 comm="systemd" exe="/usr/lib/s>
Dec 12 09:13:06 ntp.rup systemd[1]: Started User Manager for UID 0.
Dec 12 09:13:06 ntp.rup kernel: audit: type=1130 audit(1544595186.239:32): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user@0 com>
Dec 12 09:13:06 ntp.rup systemd[1]: Started Session 1 of user root.
Dec 12 09:13:06 ntp.rup login[299]: ROOT LOGIN ON tty1
Dec 12 09:13:06 ntp.rup systemd[338]: Reached target Default.
Dec 12 09:13:06 ntp.rup systemd[338]: Startup finished in 78ms.
Dec 12 09:13:25 ntp.rup sudo[345]:     root : TTY=tty1 ; PWD=/root ; USER=root ; COMMAND=/usr/bin/systemctl restart sshd
Dec 12 09:13:25 ntp.rup sudo[345]: pam_unix(sudo:session): session opened for user root by root(uid=0)
Dec 12 09:13:25 ntp.rup sshd[298]: Received signal 15; terminating.
Dec 12 09:13:25 ntp.rup systemd[1]: Stopping OpenSSH Daemon...
Dec 12 09:13:25 ntp.rup systemd[1]: Stopped OpenSSH Daemon.
Dec 12 09:13:25 ntp.rup audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=sshd comm="systemd" exe="/usr/lib/syst>
Dec 12 09:13:25 ntp.rup kernel: audit: type=1131 audit(1544595205.170:33): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=sshd comm=>
Dec 12 09:13:25 ntp.rup systemd[1]: Started OpenSSH Daemon.
Dec 12 09:13:25 ntp.rup audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=sshd comm="systemd" exe="/usr/lib/sys>
Dec 12 09:13:25 ntp.rup kernel: audit: type=1130 audit(1544595205.176:34): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=sshd comm=>
Dec 12 09:13:25 ntp.rup sudo[345]: pam_unix(sudo:session): session closed for user root
Dec 12 09:13:25 ntp.rup sshd[348]: Server listening on 0.0.0.0 port 22.
Dec 12 09:13:25 ntp.rup sshd[348]: Server listening on :: port 22.
Dec 12 09:13:32 ntp.rup sshd[349]: Accepted keyboard-interactive/pam for ameen from 172.16.10.14 port 6317 ssh2
Dec 12 09:13:32 ntp.rup sshd[349]: pam_unix(sshd:session): session opened for user ameen by (uid=0)
Dec 12 09:13:32 ntp.rup kernel: audit: type=1006 audit(1544595212.246:35): pid=349 uid=0 old-auid=4294967295 auid=1000 tty=(none) old-ses=>
Dec 12 09:13:32 ntp.rup systemd-logind[297]: New session 3 of user ameen.
Dec 12 09:13:32 ntp.rup systemd[1]: Created slice User Slice of UID 1000.
Dec 12 09:13:32 ntp.rup systemd[1]: Starting User Runtime Directory /run/user/1000...
Dec 12 09:13:32 ntp.rup systemd[1]: Started User Runtime Directory /run/user/1000.
Dec 12 09:13:32 ntp.rup audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user-runtime-dir@1000 comm="systemd" >
Dec 12 09:13:32 ntp.rup kernel: audit: type=1130 audit(1544595212.290:36): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user-runti>
Dec 12 09:13:32 ntp.rup systemd[1]: Starting User Manager for UID 1000...
Dec 12 09:13:32 ntp.rup systemd[353]: pam_unix(systemd-user:session): session opened for user ameen by (uid=0)
Dec 12 09:13:32 ntp.rup kernel: audit: type=1006 audit(1544595212.306:37): pid=353 uid=0 old-auid=4294967295 auid=1000 tty=(none) old-ses=>
Dec 12 09:13:32 ntp.rup systemd[353]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers).
Dec 12 09:13:32 ntp.rup kernel: audit: type=1130 audit(1544595212.366:38): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user@1000 >
Dec 12 09:13:32 ntp.rup audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user@1000 comm="systemd" exe="/usr/li>
Dec 12 09:13:32 ntp.rup systemd[353]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
Dec 12 09:13:32 ntp.rup systemd[353]: Reached target Paths.
Dec 12 09:13:32 ntp.rup systemd[353]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
Dec 12 09:13:32 ntp.rup systemd[353]: Listening on p11-kit server.
Dec 12 09:13:32 ntp.rup systemd[353]: Reached target Timers.
Dec 12 09:13:32 ntp.rup systemd[353]: Starting D-Bus User Message Bus Socket.
Dec 12 09:13:32 ntp.rup systemd[353]: Listening on GnuPG cryptographic agent and passphrase cache.
Dec 12 09:13:32 ntp.rup systemd[353]: Listening on GnuPG network certificate management daemon.
Dec 12 09:13:32 ntp.rup systemd[353]: Listening on D-Bus User Message Bus Socket.
Dec 12 09:13:32 ntp.rup systemd[353]: Reached target Sockets.
Dec 12 09:13:32 ntp.rup systemd[353]: Reached target Basic System.
Dec 12 09:13:32 ntp.rup systemd[1]: Started User Manager for UID 1000.
Dec 12 09:13:32 ntp.rup systemd[1]: Started Session 3 of user ameen.
Dec 12 09:13:32 ntp.rup systemd[353]: Reached target Default.
Dec 12 09:13:32 ntp.rup systemd[353]: Startup finished in 56ms.

what is the -lts kernel? i hope you don't mean to recompile all over again (N)

Offline

#6 2018-12-12 06:28:18

jasonwryan
Anarchist
From: .nz
Registered: 2009-05-09
Posts: 30,426
Website

Re: ssh blocks access until service restart [solved]


Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438

Offline

#7 2018-12-12 06:59:56

majed17
Member
Registered: 2018-12-11
Posts: 37

Re: ssh blocks access until service restart [solved]

did a pacman -S linux-lts and then pacman -Syu which said everything is up to date and then rebooted, and the problem persists... thank you for your patience.

Offline

#8 2018-12-12 07:14:10

jasonwryan
Anarchist
From: .nz
Registered: 2009-05-09
Posts: 30,426
Website

Re: ssh blocks access until service restart [solved]

Did you actually boot into -lts? Was the journal output the same for that kernel?

Please paste the output of `systemctl list-unit-files --state=enabled`.


Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438

Offline

#9 2018-12-12 07:29:23

majed17
Member
Registered: 2018-12-11
Posts: 37

Re: ssh blocks access until service restart [solved]

it used to be

Linux version 4.19.4-arch1-1-ARCH (builduser@heftig-22537) (gcc version 8.2.1 20180831 (GCC)) #1 SMP PREEMPT Fr>
Dec 10 17:09:03 ntp.rup kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=f4e52854-6fc1-4cbc-be51-0af8101b7f65 rw quiet

now it is

Linux version 4.19.8-arch1-1-ARCH (builduser@heftig-1129) (gcc version 8.2.1 20181127 (GCC)) #1 SMP PREEMPT Sat>
Dec 12 10:16:06 ntp.rup kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=f4e52854-6fc1-4cbc-be51-0af8101b7f65 rw quiet

journalctl:

Dec 12 10:16:14 ntp.rup audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=ntpd comm="systemd" exe="/usr/lib/systemd/>
Dec 12 10:16:14 ntp.rup systemd[1]: Started Network Time Service.
Dec 12 10:16:14 ntp.rup systemd[1]: Reached target Multi-User System.
Dec 12 10:16:14 ntp.rup systemd[1]: Reached target Graphical Interface.
Dec 12 10:16:14 ntp.rup systemd[1]: Startup finished in 5.855s (kernel) + 11.069s (userspace) = 16.924s.
Dec 12 10:16:14 ntp.rup ntpd[333]: proto: precision = 0.088 usec (-23)
Dec 12 10:16:14 ntp.rup ntpd[333]: switching logging to file /var/log/ntp.log
Dec 12 10:16:14 ntp.rup nrpe[313]: Starting up daemon
Dec 12 10:16:14 ntp.rup nrpe[313]: Server listening on 0.0.0.0 port 5666.
Dec 12 10:16:14 ntp.rup nrpe[313]: Server listening on :: port 5666.
Dec 12 10:16:14 ntp.rup nrpe[313]: Listening for connections on port 5666
Dec 12 10:16:14 ntp.rup nrpe[313]: Allowing connections from: 127.0.0.1,172.16.10.14
Dec 12 10:16:23 ntp.rup systemd-networkd[252]: ens32: Configured
Dec 12 10:16:39 ntp.rup kernel: random: crng init done
Dec 12 10:16:39 ntp.rup kernel: random: 7 urandom warning(s) missed due to ratelimiting
Dec 12 10:16:39 ntp.rup sshd[316]: Server listening on 0.0.0.0 port 22.
Dec 12 10:16:39 ntp.rup sshd[316]: Server listening on :: port 22.
Dec 12 10:16:41 ntp.rup login[319]: pam_unix(login:session): session opened for user zouhairy by LOGIN(uid=0)
Dec 12 10:16:41 ntp.rup kernel: kauditd_printk_skb: 1 callbacks suppressed
Dec 12 10:16:41 ntp.rup kernel: audit: type=1006 audit(1544599001.146:22): pid=319 uid=0 old-auid=4294967295 auid=1000 tty=tty1 old-ses=4294967>
Dec 12 10:16:41 ntp.rup systemd-logind[317]: New session 1 of user zouhairy.
Dec 12 10:16:41 ntp.rup systemd[1]: Created slice User Slice of UID 1000.
Dec 12 10:16:41 ntp.rup systemd[1]: Starting User Runtime Directory /run/user/1000...
Dec 12 10:16:41 ntp.rup systemd[1]: Started User Runtime Directory /run/user/1000.
Dec 12 10:16:41 ntp.rup audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user-runtime-dir@1000 comm="systemd" exe=">
Dec 12 10:16:41 ntp.rup systemd[1]: Starting User Manager for UID 1000...
Dec 12 10:16:41 ntp.rup kernel: audit: type=1130 audit(1544599001.196:23): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user-runtime-di>
Dec 12 10:16:41 ntp.rup systemd[336]: pam_unix(systemd-user:session): session opened for user zouhairy by (uid=0)
Dec 12 10:16:41 ntp.rup kernel: audit: type=1006 audit(1544599001.213:24): pid=336 uid=0 old-auid=4294967295 auid=1000 tty=(none) old-ses=42949>
Dec 12 10:16:41 ntp.rup systemd[336]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers).
Dec 12 10:16:42 ntp.rup kernel: audit: type=1130 audit(1544599001.296:25): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user@1000 comm=>
Dec 12 10:16:41 ntp.rup audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user@1000 comm="systemd" exe="/usr/lib/sys>
Dec 12 10:16:41 ntp.rup login[319]: LOGIN ON tty1 BY zouhairy
Dec 12 10:16:41 ntp.rup systemd[336]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
Dec 12 10:16:41 ntp.rup systemd[336]: Reached target Timers.
Dec 12 10:16:41 ntp.rup systemd[336]: Listening on GnuPG network certificate management daemon.
Dec 12 10:16:41 ntp.rup systemd[336]: Starting D-Bus User Message Bus Socket.
Dec 12 10:16:41 ntp.rup systemd[336]: Listening on p11-kit server.
Dec 12 10:16:41 ntp.rup systemd[336]: Reached target Paths.
Dec 12 10:16:41 ntp.rup systemd[336]: Listening on GnuPG cryptographic agent and passphrase cache.
Dec 12 10:16:41 ntp.rup systemd[336]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
Dec 12 10:16:41 ntp.rup systemd[336]: Listening on D-Bus User Message Bus Socket.
Dec 12 10:16:41 ntp.rup systemd[336]: Reached target Sockets.
Dec 12 10:16:41 ntp.rup systemd[336]: Reached target Basic System.
Dec 12 10:16:41 ntp.rup systemd[1]: Started User Manager for UID 1000.
Dec 12 10:16:41 ntp.rup systemd[1]: Started Session 1 of user zouhairy.
Dec 12 10:16:41 ntp.rup systemd[336]: Reached target Default.
Dec 12 10:16:41 ntp.rup systemd[336]: Startup finished in 85ms.
Dec 12 10:17:04 ntp.rup sudo[345]: zouhairy : TTY=tty1 ; PWD=/home/ameen ; USER=root ; COMMAND=/usr/bin/systemctl restart sshd
Dec 12 10:17:04 ntp.rup sudo[345]: pam_unix(sudo:session): session opened for user root by ameen(uid=0)
Dec 12 10:17:04 ntp.rup sshd[316]: Received signal 15; terminating.
Dec 12 10:17:04 ntp.rup systemd[1]: Stopping OpenSSH Daemon...
Dec 12 10:17:04 ntp.rup systemd[1]: Stopped OpenSSH Daemon.
Dec 12 10:17:04 ntp.rup audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=sshd comm="systemd" exe="/usr/lib/systemd/s>
Dec 12 10:17:04 ntp.rup kernel: audit: type=1131 audit(1544599024.193:26): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=sshd comm="syst>
Dec 12 10:17:04 ntp.rup systemd[1]: Started OpenSSH Daemon.
Dec 12 10:17:04 ntp.rup audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=sshd comm="systemd" exe="/usr/lib/systemd/>
Dec 12 10:17:04 ntp.rup kernel: audit: type=1130 audit(1544599024.200:27): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=sshd comm="syst>
Dec 12 10:17:04 ntp.rup sudo[345]: pam_unix(sudo:session): session closed for user root
Dec 12 10:17:04 ntp.rup sshd[348]: Server listening on 0.0.0.0 port 22.
Dec 12 10:17:04 ntp.rup sshd[348]: Server listening on :: port 22.
Dec 12 10:18:19 ntp.rup sshd[349]: Accepted keyboard-interactive/pam for ameen from 172.17.11.17 port 9555 ssh2
Dec 12 10:18:19 ntp.rup sshd[349]: pam_unix(sshd:session): session opened for user ameen by (uid=0)
Dec 12 10:18:19 ntp.rup kernel: audit: type=1006 audit(1544599099.380:28): pid=349 uid=0 old-auid=4294967295 auid=1000 tty=(none) old-ses=42949>
Dec 12 10:18:19 ntp.rup systemd-logind[317]: New session 3 of user ameen.
Dec 12 10:18:19 ntp.rup systemd[1]: Started Session 3 of user ameen.
lines 19844-19887/19887 (END)

$ systemctl list-unit-files --state=enabled

UNIT FILE                             STATE
autovt@.service                       enabled
dbus-org.freedesktop.network1.service enabled
getty@.service                        enabled
nrpe.service                          enabled
ntpd.service                          enabled
sshd.service                          enabled
systemd-networkd-wait-online.service  enabled
systemd-networkd.service              enabled
systemd-networkd.socket               enabled
remote-fs.target                      enabled

10 unit files listed.

Offline

#10 2018-12-12 08:26:10

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 24,759

Re: ssh blocks access until service restart [solved]

For the haveged solution to work you will also have to enable its service. Also you aren't booting into the LTS kernel, check your boot loader to config to configure a proper entry for the LTS kernel if you intend to test that.

Last edited by V1del (2018-12-12 08:26:24)

Offline

#11 2018-12-12 09:11:54

majed17
Member
Registered: 2018-12-11
Posts: 37

Re: ssh blocks access until service restart [solved]

Well i enabled haveged and the problem is gone! But, out of interest, to boot from the lts kernel, i would need to execute grubconfig -o ... something like that?

Offline

#12 2018-12-12 09:55:27

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 24,759

Re: ssh blocks access until service restart [solved]

Offline

#13 2018-12-12 10:42:24

majed17
Member
Registered: 2018-12-11
Posts: 37

Re: ssh blocks access until service restart [solved]

well thank you, i am now lts. does that mean long term support?

Offline

#14 2018-12-12 12:22:25

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 24,759

Re: ssh blocks access until service restart [solved]

Yes, however if that is something you want to run in the long term or not is something you will have to decide for yourself, especially newer hardware support is likely lacking if the LTS kernel is older (the current one is a year old and there have been quite a few threads talking about issues that happened because people coupled newer hardware with the LTS kernel, that had been fixed in the stable queue for a while already) and other bigger improvements that aren't being backported might be missing (e.g. there were quite a few power saving improvements in 4.15, and on an anecdotal note, the 4.18 kernel was the first kernel I could safely say my hardware was fully supported in, others had a minor crash in the ath10k driver once every boot that managed to resolve itself, however it hasn't happened anymore since 4.18). However 4.19 is slated to be the next LTS after its stable run is over, so this will relevantly change soon.

However as this veers off the original threads cause, if your original issue is resolved, could you mark it as such by ediitng your title with [SOLVED] or similar, you might have to shorten a few unnecessary parts, maybe rewrite it to something like ssh blocking connection or similar.

Offline

#15 2018-12-12 12:47:37

majed17
Member
Registered: 2018-12-11
Posts: 37

Re: ssh blocks access until service restart [solved]

Well then, lts is gone! i was thinking i upgraded to the better version big_smile

Offline

#16 2018-12-12 13:03:40

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 24,759

Re: ssh blocks access until service restart [solved]

Well it somewhat protects you from regressions that future versions might bring (though occasionally there might be a backported fix which has the regression, so you aren't entirely guaranteed protected from this) and it's seldom a bad idea to have a backup kernel for testing different behaviours or in the case that something goes really pear shaped with a normal stable release. If you can afford the disk space there's no inherent harm in having it installed.

Offline

#17 2018-12-13 11:01:24

majed17
Member
Registered: 2018-12-11
Posts: 37

Re: ssh blocks access until service restart [solved]

this is just a back up server, so i decided to try a new distribution for it, if it crashes, it wouldn't be a disaster. Gentoo and here are much better support than ubuntu and open suse, where mainly trolls hang out big_smile

Offline

Board footer

Powered by FluxBB