I noticed quite a long time to login to some of my systems via ssh (or scp).
Investigating lead me to find out that the '50-motd-news' file
(/etc/update-motd.d/50-motd-news) was the primary cost.
In line 108 [1] it does something like:
curl --connect-timeout "5" --max-time "5" -A "..." -o - https://motd.ubuntu.com
The systems I'm seeing this on are in a lab and do not have access to https://motd.ubuntu.com.
The way the lab is configured, they just end up timing out. So every scp or ssh connection
or other path to trigger update-motd will cost 5 seconds.
I noticed quite a long time to login to some of my systems via ssh (or scp). motd.d/ 50-motd- news) was the primary cost.
Investigating lead me to find out that the '50-motd-news' file
(/etc/update-
In line 108 [1] it does something like: /motd.ubuntu. com
curl --connect-timeout "5" --max-time "5" -A "..." -o - https:/
The systems I'm seeing this on are in a lab and do not have access to https:/ /motd.ubuntu. com.
The way the lab is configured, they just end up timing out. So every scp or ssh connection
or other path to trigger update-motd will cost 5 seconds.
-- /git.launchpad. net/~usd- import- team/ubuntu/ +source/ base-files/ tree/update- motd.d/ 50-motd- news?h= applied/ ubuntu/ zesty#n108
[1] https:/
ProblemType: Bug ature: User Name 4.10.0- 21.23-generic 4.10.11 Zone: nova 256color DIR=<set> .etc.update- motd.d. 50-motd- news: 2017-05- 19T01:10: 25.572110
DistroRelease: Ubuntu 17.04
Package: base-files 9.6ubuntu13
ProcVersionSign
Uname: Linux 4.10.0-21-generic x86_64
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
Date: Fri May 19 01:11:30 2017
Ec2AMI: ami-0000004f
Ec2AMIManifest: FIXME
Ec2Availability
Ec2InstanceType: m1.small
Ec2Kernel: unavailable
Ec2Ramdisk: unavailable
ProcEnviron:
TERM=xterm-
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: base-files
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile.