Nextcloud upgrade fails from 0.43

Trying to update from 0.43 to 0.48 today I’ve been blocked from nextcloud


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...
expired old bayes database entries in 30 seconds
181313 entries kept, 1239343 deleted
token frequency: 1-occurrence tokens: 64.03%
token frequency: less than 8 occurrences: 17.75%
Installing Nginx (web server)...
Installing Roundcube (webmail)...
Updating database schema (2018021600)... [OK]
Updating database schema (2018122300)... [OK]
Updating database schema (2019092900)... [OK]
Installing Nextcloud (contacts/calendar)...
Upgrading Nextcloud --- backing up existing installation, configuration, and database to directory to /home/user-data/owncloud-backup/2020-09-17-09:24:15...
Upgrades from Mail-in-a-Box prior to v0.28 (dated July 30, 2018) with Nextcloud < 13.0.6 (you have ownCloud 8 or 9) are not supported. Upgrade to Mail-in-a-Box version v0.30 first. Setup aborting.

rebooting and logging into web interface i see that mailinabox is at 0.48

I don’t use nextcloud and everything seems fine until now but i would like to see a “clean” update

Any suggestions ?

How did you get to v 0.43 in the first place? Was that the version you initially installed MiaB with? Or did you run MiaB before on Ubuntu 14.04?

If i remember well i started using Miab with a < 0.30 version, then followed the guidelines to upgrade to > 0.40 using a backup and restore.

the vps is now running 18.04.3 LTS

and if i exec again the command to upgrade it stuck in the same place

both webpanel and the command below says I’m on version 0.48 also if the setup has been aborted…

Mail-in-a-Box Version:  v0.48

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)...
Installing Nextcloud (contacts/calendar)...
Upgrading Nextcloud --- backing up existing installation, configuration, and database to directory to /home/user-data/owncloud-backup/2020-09-17-10:19:11...
Upgrades from Mail-in-a-Box prior to v0.28 (dated July 30, 2018) with Nextcloud < 13.0.6 (you have ownCloud 8 or 9) are not supported. Upgrade to Mail-in-a-Box version v0.30 first. Setup aborting.

You should have a look at this post:

Regards.

Let me thinking about:

I read:

If u have already running MiaB v0.40 jump in at 6)

And I’m currently at 0.48 ( not sure if everything is ok with my 0.48 but… )

and then

9) repeat steps 7) & 8) for every MiaB-Version were a major Nexcloud update is included

And i have no idea about how many releases are needed.

For sure the solution is near to remove nextcloud/owncloud but…

Question

As long as i don’t use use nextcloud… can i delete some folder manually ( brrr ) and then execute

curl -s https://mailinabox.email/setup.sh | sudo -E bash

I am just trying to upgrade to latest version from v0.40
and looking through the tree versions


and here it is:

#v0.41
~/mailinabox/management/backup.py
mv ./mailinabox ./mailinabox.v40
sudo git clone -b v0.41 https://github.com/mail-in-a-box/mailinabox.git
cd mailinabox
sudo git checkout
sudo setup/start.sh

  • Upgraded Nextcloud from 13.0.6 to 14.0.6.

#v0.42
~/mailinabox/management/backup.py
mv ./mailinabox ./mailinabox.v41
sudo git clone -b v0.42 https://github.com/mail-in-a-box/mailinabox.git
cd mailinabox
sudo git checkout
sudo setup/start.sh

  • Upgraded Nextcloud from 14.0.6 to 15.0.8 (with Contacts from 2.1.8 to 3.1.1 and Calendar from 1.6.4 to 1.6.5).

#v0.42b
~/mailinabox/management/backup.py
mv ./mailinabox ./mailinabox.v42
sudo git clone -b v0.42b https://github.com/mail-in-a-box/mailinabox.git
cd mailinabox
sudo git checkout
sudo setup/start.sh

  • Upgraded Nextcloud from 14.0.6 to 15.0.8 (with Contacts from 2.1.8 to 3.1.1 and Calendar from 1.6.4 to 1.6.5).

#v0.43
~/mailinabox/management/backup.py
mv ./mailinabox ./mailinabox.v42b
sudo git clone -b v0.43 https://github.com/mail-in-a-box/mailinabox.git
cd mailinabox
sudo git checkout
sudo setup/start.sh

  • Upgraded Roundcube to 1.3.10.

v0.44
~/mailinabox/management/backup.py
mv ./mailinabox ./mailinabox.v43
sudo git clone -b v0.44 https://github.com/mail-in-a-box/mailinabox.git
cd mailinabox
sudo git checkout
sudo setup/start.sh

  • Upgraded Nextcloud from 15.0.8 to 17.0.2 (with Contacts from 3.1.1 to 3.1.6 and Calendar from 1.6.5 to 1.7.1)

#v0.45
~/mailinabox/management/backup.py
mv ./mailinabox ./mailinabox.v44
sudo git clone -b v0.45 https://github.com/mail-in-a-box/mailinabox.git
cd mailinabox
sudo git checkout
sudo setup/start.sh

  • Upgraded Nextcloud from 17.0.2 to 17.0.6 (with Contacts from 3.1.6 to 3.3.0 and Calendar from 1.7.1 to v2.0.3)

#v0.46

#v0.47

#v0.48

I’m a bit scared about doing so many updates on a server that hosts many gb of email and that is currently running 0.48 :-/

I will search for a way to bypass the nextcloud issue

I have done it yesterday.

First of all, I have made a full back up after every major version upgrade (deleted the old backup files first), but it has been taking a loot of time as my MIAB is now about 30GB in size, so I skipped it and only used incremental backups.

All working now.
See my post here:

Thank you very much for that reply.
There is still something that is puzzling me.
You have done these starting from 0.27. Instead my server now says that I’m on 0.48 (with nextcloud issues)

I guess that I will not able to run something to “upgrade” to 0.41 from 0.48

maybe i should snapshot my vps and try on the snapshotted version all these steps :slight_smile:
I’m thinking…

best regard

I am not sure i you can now DOWNGRADE to smaller version of MIAB.

Take a snapshot and try …

I have downloaded the snapshot for both v0.30 and 0.40 just in case, but it was not needed at the end …plus the backups on the MIAB for each version …