![]() Core Shell aksing me for a password (seems it don't accept a key exchange algorithm). I can't connect by ssh key to sort of older debian linux servers (maybe Jessie, maybe Stretch), but there is no problem with connecting from macos standard Terminal app. Is it possible to download from some archive?Ģ). I would like to downgrade to an older version of CS. (and already typed a few letters for filter ). Ctrl+F to place cursor into the search field. waiting 3-5 sec while opening profile list window. ![]() My usual work process with Core shell now:Ĭtrl+T.50-landscape-sysinfo prints out interesting system stats (and also if you're low on space!), and 99-esm prints out messages related to Ubuntu Extended Security Maintenanceįinally you can create a script with echo '/usr/bin/landscape-sysinfo' > info.sh & chmod +x info.sh and get that printout upon request. Neither 50-landscape-sysinfo and 99-esm are crucial. All the remaining files about 2 seconds altogether. ![]() ![]() 50-landscape-sysinfo took about 5 seconds to execute and 99-esm about 3 seconds. I think that is the one which causes the biggest delay.Īfter reenabling most of the files I came to the conclusion thatĥ0-landscape-sysinfo and 99-esm were the cause for my troubles. I may start to enable scripts in that folder selectively, to see which are less harmful, but specially calling landscape-sysinfo is very slow, and 50-landscape-sysinfo does call that command. This is a server based on an "energy-efficient" N3150 CPU which has a lot of work to do 24/7, so I think that collecting all this motd-data was just too much for it. So I cd'd into /etc/update-motd.d and ran a sudo chmod -x * in order to inhibit PAM to run all the files which generate this dynamic Message Of The Day, which includes system load and if packages need to be upgraded, and this solved the issue. The line /etc/update-motd.d made me suspicious, apparently the process waits for the result of the stuff that is in /etc/update-motd.d So I continued investigating, and ran sshd with strace ( sudo strace /usr/sbin/sshd -ddd -p 44321). So please don't consider this to be an answer, but a first step to start finding out what's wrong. I have no clue why, and I'm also not leaving UsePAM at no, because I do not know which the side-effects are, but this lets me continue investigating. Not related to UseDNS or any other setting, only UsePAM affects this problem on my system. I noticed that when I change UsePAM yes to UsePAM no then this issue is resolved. Googling that isn't really helpful, but the server logs are better: debug3: mm_send_keystate: Finished sending state ĭebug1: monitor_read_log: child log fd closedĭebug3: PAM: sshpam_store_conv called with 1 messages Start a second ssh server on another port on the machine that has the problem, do so in debug mode, which won't make it fork and will print out debug messages: sudo /usr/sbin/sshd -ddd -p 44321Ĭonnect to that server from another machine in verbose mode: ssh -vvv -p 44321 client outputs the following lines right before starting to sleep: debug1: Entering interactive session. Note that this command isn't available on all systems, the landscape-common package installs it. If that's the case, you may be able to disable the execution of /etc/update-motd.d/50-landscape-sysinfo, which does call that command, by chmod -x-ing it. TLDR: Run landscape-sysinfo and check if that command takes a long time to finish it's the system information printout on a new SSH login. Note: This started as a "How to debug", tutorial, but ended up being the solution that helped me on an Ubuntu 16.04 LTS server.
0 Comments
Leave a Reply. |