Issues within the upgrade to v56

I’ve got a weird issue, when updating to v56 from v55 I get an issue with installing roundcube:

Updating system packages...
Installing system packages...
Initializing system random number generator...
Firewall is active and enabled on system startup
Installing nsd (DNS server)...
Installing Postfix (SMTP server)...
Installing Dovecot (IMAP server)...
Installing OpenDKIM/OpenDMARC...
Installing SpamAssassin...
Installing Roundcube (webmail)...

FAILED: wget -O /tmp/roundcube.tgz https://github.com/roundcube/roundcubemail/releases/download/1.5.2/roundcubemail-1.5.2-complete.tar.gz
-----------------------------------------
--2022-02-15 14:15:22--  https://github.com/roundcube/roundcubemail/releases/download/1.5.2/roundcubemail-1.5.2-complete.tar.gz
Resolving github.com (github.com)... failed: Temporary failure in name resolution.
wget: unable to resolve host address 'github.com'

After this, nothing works anymore. If I change my /etc/resolv.conf I see it’s changed to 127.0.0.1 and not 192.168.0.1.

When I do:

n@mail:~$ sudo nano /etc/resolv.conf
sudo: unable to resolve host mail.server.extension: Resource temporarily unavailable

Any idea what’s changed?

Please use code blocks in your post.

Is it better now? :slight_smile:

Did you previously change anything? I’m pretty sure resolv.conf is normally 127.0.0.1.

Nope, changed nothing.

Something is really off, I installed a new VPS on my proxmox server at home:

And yes, networking did work, and I could ping. But when starting the installation, not anymore.

Installing nsd (DNS server)...

FAILED: apt-get -y -o Dpkg::Options::=--force-confdef -o Dpkg::Options::=--force-confnew install nsd ldnsutils openssh-client
-----------------------------------------
Reading package lists...
Building dependency tree...
Reading state information...
openssh-client is already the newest version (1:7.6p1-4ubuntu0.6).
The following NEW packages will be installed:
  ldnsutils libldns2 nsd
0 upgraded, 3 newly installed, 0 to remove and 4 not upgraded.
Need to get 1,010 kB of archives.
After this operation, 3,155 kB of additional disk space will be used.
Err:1 http://be.archive.ubuntu.com/ubuntu bionic/universe amd64 nsd amd64 4.1.17-1build1
  Temporary failure resolving 'be.archive.ubuntu.com'
Ign:2 http://be.archive.ubuntu.com/ubuntu bionic-updates/main amd64 libldns2 amd64 1.7.0-3ubuntu4.1
Ign:3 http://be.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 ldnsutils amd64 1.7.0-3ubuntu4.1
Err:2 http://be.archive.ubuntu.com/ubuntu bionic-updates/main amd64 libldns2 amd64 1.7.0-3ubuntu4.1
  Temporary failure resolving 'be.archive.ubuntu.com'
Err:3 http://be.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 ldnsutils amd64 1.7.0-3ubuntu4.1
  Temporary failure resolving 'be.archive.ubuntu.com'
E: Failed to fetch http://be.archive.ubuntu.com/ubuntu/pool/universe/n/nsd/nsd_4.1.17-1build1_amd64.deb  Temporary failure resolving 'be.archive.ubuntu.com'
E: Failed to fetch http://be.archive.ubuntu.com/ubuntu/pool/main/l/ldns/libldns2_1.7.0-3ubuntu4.1_amd64.deb  Temporary failure resolving 'be.archive.ubuntu.com'
E: Failed to fetch http://be.archive.ubuntu.com/ubuntu/pool/universe/l/ldns/ldnsutils_1.7.0-3ubuntu4.1_amd64.deb  Temporary failure resolving 'be.archive.ubuntu.com'
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
-----------------------------------------

MiaB is developed assuming an environment identical to a hosted VPS service.

Yeah, I understand but it’s running over 2 years now without any issue. Even updates from 54 to 55 did work.

Hi - I don’t know what how much networking you know, and what you’ve tried so far, so please forgive any insultingly obvious advice :slight_smile: The error message is what I’d be looking at … it couldn’t resolve be.archive.ubuntu.com, if you can sort that, it should be ok.

Things I’d check up front:

  • can you ping any remote server (try ping www.google.com)? If no responses, you’ve got a more general problem.
  • just try again, could have been a genuine short-term network problem.
  • (on your box) try nslookup be.archive.ubuntu.com and see if you get responses from ping be.archive.ubuntu.com

If that’s all ok, try manually executing the failing command (you’ll need sudo). That lets you see what’s happening and isolate the problem, and should not interfere with subsequent MIAB installs/upgrades when you run it again.

  • sudo apt-get -y -o Dpkg::Options::=--force-confdef -o Dpkg::Options::=--force-confnew install nsd ldnsutils openssh-client

Hi Andrew,

Thanks for your reply. Well, if I start with the upgrade, it stops at Roundcube, then, if I ping nothing pings anymore. I didn’t try nslookup yet. As you can see, there are two different scenario’s, one with the production version, when I upgrade it won’t work anymore, and the new one with a fresh installation. But both fails. Only thing I know is I replaced the router with pfsense. Maybe it’s that, but my technical skills are not that great :slight_smile:

1 Like

A fresh MIAB install should be very easy, the only think I’ve had to do is reboot the server after install/upgrade (makes sure everything has come up cleanly).

Look at things logically - on a clean machine:

  1. Do you get ping replies from IP address? I use ping 8.8.8.8 - google’s DNS servers are unlikely to be down! (You should see a series of replies.)
  2. Can you resolve a name, eg. nslookup www.google.com? (You’d expect to see an non-authoritative answer with an IP address.)
  3. Can you get requests out and data back, eg. wget https://mailinabox.email/setup.sh (You should see the setup.sh file in your local directory.)

If any of that fails, the install hasn’t a chance. If all that works, run the install command. After the install, all those tests should still work. (Remember: various TCP and UDP ports must be open at your router, and at your ISP.)

(After install) have a look in /etc/mailinabox.conf - that contains the IP addresses used for the setup.

I’m wondering if your local router setup is incorrect. Perhaps it’s giving your MIAB server incorrect gateway or DNS server info.

Tried the update again:

Private IP Address: 192.168.0.125
Mail-in-a-Box Version:  v56

Updating system packages...
Installing system packages...
Initializing system random number generator...
Firewall is active and enabled on system startup
Installing nsd (DNS server)...
Installing Postfix (SMTP server)...
Installing Dovecot (IMAP server)...
Installing OpenDKIM/OpenDMARC...
Installing SpamAssassin...
Installing Nginx (web server)...
Installing Roundcube (webmail)...

FAILED: wget -O /tmp/roundcube.tgz https://github.com/roundcube/roundcubemail/releases/download/1.5.2/roundcubemail-1                                       .5.2-complete.tar.gz
-----------------------------------------
--2022-02-18 21:36:35--  https://github.com/roundcube/roundcubemail/releases/download/1.5.2/roundcubemail-1.5.2-compl                                       ete.tar.gz
Resolving github.com (github.com)... failed: Temporary failure in name resolution.
wget: unable to resolve host address ‘github.com’
-----------------------------------------
server@mail:~$ ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=58 time=14.8 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=58 time=28.2 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=58 time=18.3 ms
64 bytes from 8.8.8.8: icmp_seq=4 ttl=58 time=18.3 ms
^C
--- 8.8.8.8 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3003ms
rtt min/avg/max/mdev = 14.835/19.929/28.228/5.000 ms
server@mail:~$ nslookup www.google.com
Server:         127.0.0.1
Address:        127.0.0.1#53

** server can't find www.google.com: SERVFAIL

server@mail:~$ wget https://mailinabox.email/setup.sh
--2022-02-18 21:37:51--  https://mailinabox.email/setup.sh
Resolving mailinabox.email (mailinabox.email)... failed: Temporary failure in name resolution.
wget: unable to resolve host address ‘mailinabox.email’

And again, before the update I can do these things, ping, nslookup, etc.

OK, when MiaB is updating, it is changing the /etc/resolv.conf to 127.0.0.1 which will stop the installation at roundcube. When I put it back to 192.168.0.1 (running DNS server) it will work again. But how can I install the update and skip /etc/resolv.conf is being changed? chatr +i won’t work.

I fixed it, problem was pfsense blocking external DNS request :wink:

Might be worth posting your symptoms and solution … sure to be someone else out there who’ll have a similar problem :slight_smile:

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