Installer crashing on RNG

lane_ftw · February 6, 2024, 9:07pm

Ubuntu 22.04 LXC Proxmox 8
I’m using the server template. I installed this to another CT using the same template a few weeks ago, I have no idea why this is failing.
Literally the only thing I did before running the installer was apt install curl
Truncated syslog.

Primary Hostname: box.DOMAIN.com
Public IP Address: 
Private IP Address: 192.168.1.131
Mail-in-a-Box Version:  v67

Updating system packages...
Installing system packages...
Initializing system random number generator...
root@mail:/var/log# cat syslog
Feb  6 14:54:21 mail pollinate[15144]: client sent challenge to [https://entropy.ubuntu.com/]
Feb  6 14:54:21 mail ntpd[15018]: Soliciting pool server 192.48.105.15
Feb  6 14:54:22 mail pollinate[15144]: client verified challenge/response with [https://entropy.ubuntu.com/]
Feb  6 14:54:22 mail pollinate[15144]: client hashed response from [https://entropy.ubuntu.com/]
Feb  6 14:54:22 mail pollinate[15144]: client successfully seeded [/dev/urandom]
Feb  6 14:54:22 mail ntpd[15018]: Soliciting pool server 45.33.103.94
Feb  6 14:54:22 mail ntpd[15018]: Soliciting pool server 172.233.153.85
Feb  6 14:54:22 mail ntpd[15018]: Soliciting pool server 138.68.201.49
Feb  6 14:54:22 mail ntpd[15018]: Soliciting pool server 185.125.190.56
Feb  6 14:54:23 mail ntpd[15018]: Soliciting pool server 185.125.190.58
Feb  6 14:54:23 mail ntpd[15018]: Soliciting pool server 135.148.100.14
Feb  6 14:54:23 mail ntpd[15018]: Soliciting pool server 104.167.241.197
Feb  6 14:54:23 mail ntpd[15018]: Soliciting pool server 162.159.200.123
Feb  6 14:54:24 mail ntpd[15018]: Soliciting pool server 91.189.91.157
Feb  6 14:54:24 mail ntpd[15018]: Soliciting pool server 204.93.207.12
Feb  6 14:54:24 mail ntpd[15018]: Soliciting pool server 2620:8d:c000::f
Feb  6 14:54:24 mail ntpd[15018]: Soliciting pool server 108.61.73.243
Feb  6 14:54:27 mail ntpd[15018]: adj_systime: Operation not permitted
Feb  6 14:58:16 mail systemd-resolved[13584]: System hostname changed to 'box.DOMAIN.com'.
Feb  6 14:58:30 mail pollinate[16759]: system was previously seeded at [2024-02-06 14:54:22.131463624 -0600]
Feb  6 14:58:30 mail pollinate[16759]: client sent challenge to [https://entropy.ubuntu.com/]
Feb  6 14:58:31 mail pollinate[16759]: client verified challenge/response with [https://entropy.ubuntu.com/]
Feb  6 14:58:31 mail pollinate[16759]: client hashed response from [https://entropy.ubuntu.com/]
Feb  6 14:58:31 mail pollinate[16759]: client successfully seeded [/dev/urandom]

KiekerJan · February 6, 2024, 9:18pm

It might well be this doesn’t work well without a public ip address. Is bind9 installed and running properly after you have run the setup?

lane_ftw · February 6, 2024, 9:23pm

Not sure what you mean about a public IP.
Just tried it in a privileged CT, same thing.

root@mail:~# ps aux | grep bind9
root       15281  0.0  0.0   3480  1920 pts/3    S+   15:22   0:00 grep --color=auto bind9

root@mail:~# ps aux
USER         PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
root           1  0.0  0.1 166812 12032 ?        Ss   15:17   0:03 /lib/systemd/systemd --system --deserialize 21
root         243  0.0  0.0   3884  2432 ?        Ss   15:17   0:00 /usr/sbin/cron -f -P
message+     244  0.0  0.0   8784  4736 ?        Ss   15:17   0:00 @dbus-daemon --system --address=systemd: --nofork --nopidfile --s
root         248  0.0  0.0  15292  7296 ?        Ss   15:17   0:00 /lib/systemd/systemd-logind
root         250  0.0  0.0   2816  1920 pts/0    Ss+  15:17   0:00 /sbin/agetty -o -p -- \u --noclear --keep-baud console 115200,384
root         251  0.0  0.0   2816  1792 pts/1    Ss+  15:17   0:00 /sbin/agetty -o -p -- \u --noclear --keep-baud tty1 115200,38400,
root         252  0.0  0.0   2816  1920 pts/2    Ss+  15:17   0:00 /sbin/agetty -o -p -- \u --noclear --keep-baud tty2 115200,38400,
root         423  0.0  0.1  17184 10880 ?        Rs   15:17   0:00 sshd: root@pts/3
root         426  0.0  0.0  16596  8704 ?        Ss   15:17   0:00 /lib/systemd/systemd --user
root         427  0.0  0.0  21108  4588 ?        S    15:17   0:00 (sd-pam)
root         449  0.0  0.0   5392  4480 pts/3    Ss   15:17   0:00 -bash
root        3521  0.0  0.2 110172 22016 ?        Ssl  15:20   0:00 /usr/bin/python3 /usr/share/unattended-upgrades/unattended-upgrad
root        3737  0.0  0.1 292636 20352 ?        Ssl  15:20   0:00 /usr/libexec/packagekitd
root        3741  0.0  0.0 234500  7296 ?        Ssl  15:20   0:00 /usr/libexec/polkitd --no-debug
root        8896  0.0  0.1  32084 19072 ?        Ss   15:21   0:00 /usr/bin/python3 /usr/bin/networkd-dispatcher --run-startup-trigg
root       13373  0.0  0.0  41228  4496 ?        Ss   15:21   0:00 /usr/lib/postfix/sbin/master -w
postfix    13374  0.0  0.0  41556  7040 ?        S    15:21   0:00 pickup -l -t unix -u -c
postfix    13375  0.0  0.0  41600  7168 ?        S    15:21   0:00 qmgr -l -t unix -u
systemd+   13647  0.0  0.0  16148  8192 ?        Ss   15:21   0:00 /lib/systemd/systemd-networkd
systemd+   13652  0.0  0.1  25560 13664 ?        Ss   15:21   0:00 /lib/systemd/systemd-resolved
root       13654  0.0  0.1  23028 10880 ?        S<s  15:21   0:00 /lib/systemd/systemd-journald
root       15085  0.0  0.0  75792  5884 ?        Ssl  15:21   0:00 /usr/sbin/ntpd -p /var/run/ntpd.pid -g -u 111:118
syslog     15206  0.0  0.0 222408  5248 ?        Ssl  15:21   0:00 /usr/sbin/rsyslogd -n -iNONE
root       15282  0.0  0.0   7064  2944 pts/3    R+   15:23   0:00 ps aux

Bind9 didn’t seem to be installed, so I tried
apt install bind9
which worked, re ran setup and still crashing.

KiekerJan · February 6, 2024, 9:27pm

There’s no public ip address

I’m not sure of the bind9 process name. Could you try sudo systemctl status bind9

lane_ftw · February 6, 2024, 9:31pm

Oh, I removed it. Sorry for confusion.
After installing bind9 and confirming it’s running with systmctl

root@mail:~# sudo systemctl status bind9
* named.service - BIND Domain Name Server
     Loaded: loaded (/lib/systemd/system/named.service; enabled; vendor preset: enabled)
     Active: active (running) since Tue 2024-02-06 15:26:28 CST; 1min 51s ago
       Docs: man:named(8)
    Process: 15532 ExecStart=/usr/sbin/named $OPTIONS (code=exited, status=0/SUCCESS)
   Main PID: 15533 (named)
      Tasks: 10 (limit: 18715)
     Memory: 6.3M
        CPU: 41ms
     CGroup: /system.slice/named.service
             `-15533 /usr/sbin/named -u bind

Feb 06 15:26:28 mail.DOMAIN.com named[15533]: network unreachable resolving './DNSKEY/IN': 2001:500:1::53#53
Feb 06 15:26:28 mail.DOMAIN.com named[15533]: network unreachable resolving './NS/IN': 2001:500:1::53#53
Feb 06 15:26:28 mail.DOMAIN.com named[15533]: network unreachable resolving './DNSKEY/IN': 2001:7fe::53#53
Feb 06 15:26:28 mail.DOMAIN.com named[15533]: network unreachable resolving './NS/IN': 2001:7fe::53#53
Feb 06 15:26:28 mail.DOMAIN.com named[15533]: managed-keys-zone: Initializing automatic trust anchor management for zone '.'; DN>
Feb 06 15:26:28 mail.DOMAIN.com named[15533]: resolver priming query complete: success
Feb 06 15:26:28 mail.DOMAIN.com named[15533]: checkhints: b.root-servers.net/A (170.247.170.2) missing from hints
Feb 06 15:26:28 mail.DOMAIN.com named[15533]: checkhints: b.root-servers.net/A (199.9.14.201) extra record in hints
Feb 06 15:26:28 mail.DOMAIN.com named[15533]: checkhints: b.root-servers.net/AAAA (2801:1b8:10::b) missing from hints
Feb 06 15:26:28 mail.DOMAIN.com named[15533]: checkhints: b.root-servers.net/AAAA (2001:500:200::b) extra record in hints

IPv6 problem maybe?

lane_ftw · February 6, 2024, 9:33pm

Yeah, seems to be IPv6. Turned it on and it’s working now.
First application I’ve used that’s NEEDED IPv6.
Thanks for your help!

FOR THOSE IN THE FUTURE:
MIAB v67
It still crashes first time even with IPv6 enabled on CT creation, and does not install bind9 before it does crash.
My command history to make it work starting from CT creation, commands are run as root:

apt install curl
curl -s https://mailinabox.email/setup.sh | sudo -E bash
#IT FAILS AT RNG HERE
apt install bind9
reboot
#May be able to systemctl stop/start bind9 here rather than rebooting
curl -s https://mailinabox.email/setup.sh | sudo -E bash
#You may be able to substitute the curl command for just 'mailinabox'

Testing on privileged CT now, will edit after testing unprivileged.
Tried installing bind9 before installing MIAB, still crashes.
Everything seems to work on an unprivileged CT.

system · February 13, 2024, 9:34pm

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.