Topic: Is it okay to run bash iRedMail.sh after following the upgrading steps
==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====
- iRedMail version (check /etc/iredmail-release): 1.6.0 (initially 1.4.0. I followed the upgrade tutorials up to 1.6.0 so this number was updated manually)
- Deployed with iRedMail Easy or the downloadable installer? I Forgot.
- Linux/BSD distribution name and version: CentOS SELinux 8 x64
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): PGSQL
- Web server (Apache or Nginx): Nginx
- Manage mail accounts with iRedAdmin-Pro? No.
- [IMPORTANT] Related original log or error message is required if you're experiencing an issue.
====
The initial version I installed was iRedMail 1.4.0.
I have followed all the upgrade steps from 1.4.1 all the way up to 1.6.0.
But then when I ran:
# sudo service sogod restart
Resulting in:
Redirecting to /bin/systemctl restart sogod.service
Failed to restart sogod.service: Unit sogod.service not found.
However, I did not notice that Sogo wasn't fully installed as I was doing the upgrade. Why?
Firstly, because I have never used Sogo until now.
Secondly, because all the tables in PGSQL exist, all the table upgrades were successful (from 1.4.1 to 1.6.0 upgrade steps).
So, the question is:
Is it okay for me to re-install sogo by running
bash /iRedMail-1.4.0/iRedMail.sh
Or is it better that I download iRedMail-1.6.0 first and run:
bash /iRedMail-1.6.0/iRedMail.sh
Because I'm afraid if I run from the iRedMail-1.4.0 I will need to redo all the upgrade steps from 1.4.1 to 1.6.0 but if I run from the iRedMail-1.6.0, I'm afraid that the whole database is going to get rewritten.
Thank you!
----
Spider Email Archiver: On-Premises, lightweight email archiving software developed by iRedMail team. Supports Amazon S3 compatible storage and custom branding.