Well, I did a complete new install off NS7 in ProxMox (2 processor cores / 5GB memory / virtual HD of 1TB)
Updated all components in software center
Installed the following packages:
- Backup
- Dutch language
- Email
- NextCloud
- SOGo groupware
Configured the new server (hostname, certificate and accounts provider-LDAP)
Followed the upgrade with rsync instructions in the documentation:
screen rsync-upgrade sourceserver port
Had to rerun 2 or 3 times because of errors (timeouts and such - probably because destination and source server are running respectively on ProxMox and ESXi using the same NFS server).
Finally finished the rsync-upgrade, rebooted for good measure.
Issued the ‘final’ command:
screen rsync-upgrade -u sourceserver port
All seemed well until an error message occurred telling me that the ‘post-restore-config’ did not complete successfully . . . .
Contents of restore-config.log:
2017-06-08 16:44:32 - START - Restore config started
2017-06-08 16:44:33 - STEP - pre-restore-config done
2017-06-08 16:44:38 - STEP - restore-config-execute done
2017-06-08 16:45:40 - STEP - restore-config-reinstall done
2017-06-08 16:54:01 - ERROR - Event post-restore-config failed - 256
After this message, the network interfaces on the destination server were down, obvious since source and destination have the seem IP-address after the upgrade, but probably something to mention in the admin manual.
/var/log/messages does not seem to reveal anything suspicious
After the upgrade IMAP/SMTP seemed to be fine, SOGo is not.
/var/log/sogo/sogo.log:
Jun 08 16:00:05 sogod [1628]: vmem size check enabled: shutting down app when vmem > 512 MB. Currently at 312 MB
Jun 08 16:00:06 sogod [1628]: <0x0x7ff225ec93d0[SOGoProductLoader]> SOGo products loaded from ‘/usr/lib64/GNUstep/SOGo’:
Jun 08 16:00:06 sogod [1628]: <0x0x7ff225ec93d0[SOGoProductLoader]> AdministrationUI.SOGo, Appointments.SOGo, CommonUI.SOGo, Contacts.SOGo, ContactsUI.SOGo, MailPartViewers.SOGo, Mailer.SOGo, MailerUI.SOGo, MainUI.SOGo, PreferencesUI.SOGo, SchedulerUI.SOGo, ActiveSync.SOGo
Jun 08 16:00:07 sogod [1628]: All products loaded - current memory usage at 357 MB
Jun 08 16:00:07 sogod [1628]: <0x0x7ff225fbfe80[WOWatchDog]> listening on 127.0.0.1:20000
Jun 08 16:00:07 sogod [1628]: <0x0x7ff225fbfe80[WOWatchDog]> watchdog process pid: 1628
Jun 08 16:00:07 sogod [1628]: <0x0x7ff223208980[WOWatchDogChild]> watchdog request timeout set to 60 minutes
Jun 08 16:00:07 sogod [1628]: <0x0x7ff225fbfe80[WOWatchDog]> preparing 10 children
Jun 08 16:00:07 sogod [1628]: <0x0x7ff225fbfe80[WOWatchDog]> child spawned with pid 1667
Jun 08 16:00:07 sogod [1628]: <0x0x7ff225fbfe80[WOWatchDog]> child spawned with pid 1668
Jun 08 16:00:07 sogod [1628]: <0x0x7ff225fbfe80[WOWatchDog]> child spawned with pid 1669
Jun 08 16:00:07 sogod [1628]: <0x0x7ff225fbfe80[WOWatchDog]> child spawned with pid 1670
Jun 08 16:00:07 sogod [1628]: <0x0x7ff225fbfe80[WOWatchDog]> child spawned with pid 1671
Jun 08 16:00:07 sogod [1628]: <0x0x7ff225fbfe80[WOWatchDog]> child spawned with pid 1672
Jun 08 16:00:07 sogod [1628]: <0x0x7ff225fbfe80[WOWatchDog]> child spawned with pid 1673
Jun 08 16:00:07 sogod [1628]: <0x0x7ff225fbfe80[WOWatchDog]> child spawned with pid 1674
Jun 08 16:00:07 sogod [1628]: <0x0x7ff225fbfe80[WOWatchDog]> child spawned with pid 1675
Jun 08 16:00:07 sogod [1628]: <0x0x7ff225fbfe80[WOWatchDog]> child spawned with pid 1676
2017-06-08 16:00:07.891 sogod[1673:1673] ERROR: could not open MySQL4 connection to database ‘sogo’: Can’t connect to local MySQL server through socket ‘/var/lib/mysql/mysql.sock’ (2)
Jun 08 16:00:07 sogod [1673]: [ERROR] <0x0x7ff225f916d0[GCSChannelManager]> could not open channel <MySQL4Channel[0x0x7ff226023f10] connection=0x(null)> for mysql://localhost/sogo/sogo_user_profile
Jun 08 16:00:07 sogod [1673]: [WARN] <0x0x7ff225f916d0[GCSChannelManager]> will prevent opening of this channel 5 seconds after 2017-06-08 16:00:07 +0200
So, my second try at upgrading to NS7 wasn’t successful either so far.