Re: [report] "gateway" installation for amd64 dual NIC machine using 2019-05-13 image.
Dear Holger Levsen,
On 5/15/19 8:18 PM, Holger Levsen wrote:
*many* thanks for your detailed installation reports! Very nice to see.
Also many thanks to Wolfgang, for his extensive replies!
Great thank from me, too!
I'll just comment on one tiny aspect:
On Wed, May 15, 2019 at 07:39:31PM +0900, hoxp18 wrote:
And I also felt boot up is so slow. That might have common root.
this could be related to
https://daniel-lange.com/archives/152-Openssh-taking-minutes-to-become-available,-booting-takes-half-an-hour-...-because-your-server-waits-for-a-few-bytes-of-randomness.html
Thank you for telling me very interesting article.
It never occurred to me.
My "main server" tends to take 20~30 sec after the message,
[ OK ] Started Login Service.
FYI:
firstuser$ sudo journalctl | grep -E "(rng|random)"
53:06 kernel: random: get_random_bytes_called from
start_kernel+0x93/0x531 with crng_init=0
53:06 kernel: random: drng done (trusting CPU's manufacture)
53:27 named[PID]: built with '... --with-pkcs11=/usr/lib/softhsm2.so
--with-randomdev=/dev/random
53:27 kadmind: Seeding random number generator
Perhaps it has something random related, as you pointed.
In addition to that, though it may be simple my mistakes,
sometimes "first user" login refused, saying "wrong password."
to quote from there:
The typical issue is:
[ 4.428797] EXT4-fs (vda1): mounted filesystem with ordered data mode. Opts: data=ordered
[ 130.970863] random: crng init done
can you run "sudo dmesg" and see if this is the cause of the problem?
firstuser$ sudo dmesg | grep EXT4-fs
EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null)
(dm-0): re-mounted. Opts: (null)
(dm-0): re-mounted. Opts: errors=remount-ro
(nvme0n1p1): mounted filesystem with ordered data mode. Opts: (null)
and since I add data=writeback for some mount points,
(dm-6): mounted filesystem with writeback data mode. Opts:data=writaback
...
Those logs are in almost same timestamp.
After those, around nslcd, there are many "Can't contact LDAP server",
ldap_start_tls_s() failed
failed tp bind to LDAP server ldap://ldap.intern: Can't contact ...
no available LDAP server found, sleeping 1 seconds
These starts at 20:38:58, finished at 20:39:47, with
nslcd: <passwd(all)> connected to LDAP server ldap://ldap.intern
Apology for shortend (non-RAW) logs.
Regards.
Reply to: