New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade from v0.24 to v0.30 fails #1596
Comments
Why not export all your emails using something like imapsync and move the data over to a newly installed MiaB instance? You would avoid package upgrade problems because you'd be starting from a fresh Ubuntu install, though I imagine moving across all the data and making sure nothing is lost would take some effort. Edit: have you tried making a MiaB backup and then restoring it on a newly installed MiaB instance? It might work. |
The Ubuntu version used then is EndofLife meaning that the packages needed are no longer available in the repository. |
In theory this will not work as to do a proper restore onto v0.40+ the backup needs to be from v0.29 or v0.30. |
Since DigitalOcean is hosting my server, I'll take a snapshot of my current server (just in case...). Then spin up a new miab server using a fresh ubuntu 18.04 installation and restoring the backup files that I copied above. Does that make sense? |
It makes sense, but it may not work. The problem will be the huge gap in NextCloud versions between MiaB v0.24 and v0.30. This is what @JoshData wrote on the subject:
If it does not work I can suggest two possible remedies ... First, if DO has Ubuntu 14.04 still available for installation, which I doubt, reinstall on that first as the packages should be up to date ... again, if 14.04 is even still available. Then upgrade MiaB to v0.30. After which you will have to do the entire process again to migrate to Ubuntu 18.04. |
You're right - DO doesn't have a 14.04 server for installation. I'm still confused... Why can't I backup (to an external server) all the emails, secret_key.txt and SSL keys on my 14.04 MIAB server, then create a shinny new 18.04 x64 Ubuntu server running v0.40 MIAB. When I get that running, simply copy my saved emails and SSL keys onto the new server. I don't use OwnCloud/NextCloud. I just run an email server. Thanks. |
You can. Nextcloud is the component that requires upgrades through intermediate versions. If you're not using it, I believe a backup+restore upgrade from any Mail-in-a-Box version to any later Mail-in-a-Box version will work fine. |
Thanks Josh. My server is hosted by Digital Ocean, so I'll take a snapshot of my current MIAB server before I do anything. |
I think I have a workable plan now, so this thread can be closed. |
When I try to upgrade from v0.24 to v0.30, I get the following error:
Primary Hostname: xxxxxxxxxxxx
Public IP Address: xxxxxxxxxxxxx
Mail-in-a-Box Version: v0.30
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)...
FAILED: apt-get -y -o Dpkg::Options::=--force-confdef -o Dpkg::Options::=--force-confnew install nginx php7.0-cli php7.0-fpm
Reading package lists...
Building dependency tree...
Reading state information...
E: Unable to locate package php7.0-cli
E: Couldn't find any package by regex 'php7.0-cli'
E: Unable to locate package php7.0-fpm
E: Couldn't find any package by regex 'php7.0-fpm'
I can ssh to my mailinabox server, but when I run:
/root/mailinabox/management/status_checks.py
I get this error:
-bash: /root/mailinabox/management/status_checks.py: /usr/local/lib/mailinabox/env/bin/python: bad interpreter: No such file or directory
At the moment I'm stuck. The mail function works (I can send and receive mail).
BTW: I just use mail, not any of the other features.
Can I revert back to v0.24?
Thanks
The text was updated successfully, but these errors were encountered: