Search found 4 matches
- Sun Aug 04, 2019 1:44 pm
- Forum: Installation and Upgrade
- Topic: Simultaneous ZCS 8.6 > 8.8.12 & Ubuntu 14.04LTS to 16.04 to 18.04 Upgrade
- Replies: 3
- Views: 3641
Re: Simultaneous ZCS 8.6 > 8.8.12 & Ubuntu 14.04LTS to 16.04 to 18.04 Upgrade
I wanted to update everyone. The ZExtras Migration wouldn't install on the broken server, so it was more or less a no-go. So, for what it's worth, I rebuilt a Ubuntu 16.04 VM and reinstalled Zimbra on it. I loosely followed this guide (here: https://syslint.com/blog/tutorial/zimbra-server-migration-...
- Sat Apr 20, 2019 9:33 am
- Forum: Installation and Upgrade
- Topic: Simultaneous ZCS 8.6 > 8.8.12 & Ubuntu 14.04LTS to 16.04 to 18.04 Upgrade
- Replies: 3
- Views: 3641
Re: Simultaneous ZCS 8.6 > 8.8.12 & Ubuntu 14.04LTS to 16.04 to 18.04 Upgrade
Hi Folks, For Issue 2 above, still don't have any working stats, and service status is offline. I noticed in the last logfile above that it references my Gateway IP (192.168.10.254) at the very end. Is that normal? I would expect it to reference the IP of the Zimbra server, or the IP of the computer...
- Sat Apr 06, 2019 11:35 am
- Forum: Installation and Upgrade
- Topic: Installing Zimbra 8.8.12_GA_3794 on Ubuntu 18.04
- Replies: 33
- Views: 59089
Re: Installing Zimbra 8.8.12_GA_3794 on Ubuntu 18.04
I thought I would add, literally changing the line: s|(^destination mail [b]{[/b] file\("/var/log/mail"\); };)|#$1|; to: s|(^destination mail [b]\{[/b] file\("/var/log/mail"\); };)|#$1|; ...corrected this for me. This is line 190 in the file /opt/zimbra/libexec/zmsyslogsetup. It ...
- Thu Apr 04, 2019 5:53 pm
- Forum: Installation and Upgrade
- Topic: Simultaneous ZCS 8.6 > 8.8.12 & Ubuntu 14.04LTS to 16.04 to 18.04 Upgrade
- Replies: 3
- Views: 3641
Simultaneous ZCS 8.6 > 8.8.12 & Ubuntu 14.04LTS to 16.04 to 18.04 Upgrade
So let's get it out there- this was really dumb, caused by a miscommunication, and a junior admin not snapping the virtual server prior to attempting anything. Ugh. So, the do-release-upgrade command was run twice in succession on an Ubuntu 14.04 box, updating it first to 16.04 LTS and then to 18.0...