I tried the upgrade last week from 4.2 to 5.0. The server was running in production.
Ubuntu is still on 14.04 as uname -a still says :
Linux magnaczen 3.19.0-80-generic #88~14.04.1-Ubuntu SMP Fri Jan 13 14:54:07 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
We were only using AD + Shared SMB files before. The AD has the remote desktop broken + the /home/user are inaccessible from windows.
Beside the webservice is totally down only giving
Internal Server Error
Even though the debug mode is activated.
Since i created a backup from the webservice i hope i can easily revert it ?
Is there a way through the terminal to use the .tar file provided ? Do i simply put the etc files back in place ? I don't want to mess with the server anymore ...
Here is the result of the dpklg -l | grep "Zentyal"
ii bind9 2:9.9.5.dfsg-3+zentyal amd64 Internet Domain Name Server
ii bind9-host 2:9.9.5.dfsg-3+zentyal amd64 Version of 'host' bundled with BIND 9.X
ii bind9utils 2:9.9.5.dfsg-3+zentyal amd64 Utilities for BIND
ii dnsutils 2:9.9.5.dfsg-3+zentyal amd64 Clients provided with BIND
ii language-pack-zentyal-fr 4.2 all Zentyal translations for language French
ii libbind9-90 2:9.9.5.dfsg-3+zentyal amd64 BIND9 Shared Library used by BIND
ii libdns100 2:9.9.5.dfsg-3+zentyal amd64 DNS Shared Library used by BIND
ii libhtml-mason-perl 1:1.52+zentyal1 all HTML::Mason Perl module
ii libisc95 2:9.9.5.dfsg-3+zentyal amd64 ISC Shared Library used by BIND
ii libisccc90 2:9.9.5.dfsg-3+zentyal amd64 Command Channel Library used by BIND
ii libisccfg90 2:9.9.5.dfsg-3+zentyal amd64 Config File Handling Library used by BIND
ii liblwres90 2:9.9.5.dfsg-3+zentyal amd64 Lightweight Resolver Library used by BIND
ii libtrycatch-lite-perl 1.003002+zentyal3 amd64 first class try catch semantics for Perl - lite version
ii libwbclient0:amd64 4:4.3.4-zentyal1 amd64 Samba winbind client library
ii python-samba 4:4.3.4-zentyal1 amd64 Python bindings for Samba
ii samba 4:4.3.4-zentyal1 amd64 SMB/CIFS file, print, and login server for Unix
ii samba-common 4:4.3.4-zentyal1 all common files used by both the Samba server and client
ii samba-common-bin 4:4.3.4-zentyal1 amd64 Samba common files used by both the server and the client
ii samba-dsdb-modules 4:4.3.4-zentyal1 amd64 Samba Directory Services Database
ii samba-libs:amd64 4:4.3.4-zentyal1 amd64 Samba core libraries
ii samba-vfs-modules 4:4.3.4-zentyal1 amd64 Samba Virtual FileSystem plugins
ii winbind 4:4.3.4-zentyal1 amd64 service to resolve user and group information from Windows NT servers
ii zentyal 4.2 all Zentyal - Core metapackage
ii zentyal-common 4.2 all Zentyal - Common Library
ii zentyal-core 4.2.5 all Zentyal - Core
ii zentyal-dns 4.2.1 all Zentyal - DNS Server
ii zentyal-firewall 4.2 all Zentyal - Firewall
ii zentyal-network 4.2.2 all Zentyal - Network Configuration
ii zentyal-ntp 4.2 all Zentyal - NTP Service
ii zentyal-objects 4.2 all Zentyal - Network Objects
ii zentyal-samba 4.2.3 all Zentyal - Domain Controller and File Sharing
ii zentyal-services 4.2 all Zentyal - Network Services
ii zentyal-software 4.2 all Zentyal - Software Management
I also get from the cron an email every hour this error :
Content-Type: text/plain; charset=ANSI_X3.4-1968
X-Cron-Env: <SHELL=/bin/sh>
X-Cron-Env: <PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin>
X-Cron-Env: <HOME=/root>
X-Cron-Env: <LOGNAME=root>
Message-Id: <20170301151704.093B91B606D5@magnaczen.magnaczen.fr>
Date: Wed, 1 Mar 2017 16:17:04 +0100 (CET)
run-parts: /etc/cron.hourly/90zentyal-manage-logs exited with return code 25
Here is the tail /var/log/zentyal/error.log2017/02/21 16:50:55 [error] 1976#0: *6863 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 10.87.56.98, server: , request: "GET /Dashboard/WidgetJSON?module=sysinfo&widget=modules HTTP/1.1", upstream: "uwsgi://unix:///run/zentyal-webadmin/webadmin.sock:", host: "10.87.56.252:8443", referrer: "https://10.87.56.252:8443/Dashboard/Index"
2017/02/21 16:50:56 [error] 1976#0: *6856 upstream prematurely closed connection while reading response header from upstream, client: 10.87.56.98, server: , request: "GET /Dashboard/WidgetJSON?module=sysinfo&widget=processes HTTP/1.1", upstream: "uwsgi://unix:///run/zentyal-webadmin/webadmin.sock:", host: "10.87.56.252:8443", referrer: "https://10.87.56.252:8443/Dashboard/Index"
2017/02/21 16:50:56 [error] 1976#0: *6909 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 10.87.56.98, server: , request: "GET /Dashboard/WidgetJSON?module=network&widget=interfaces HTTP/1.1", upstream: "uwsgi://unix:///run/zentyal-webadmin/webadmin.sock:", host: "10.87.56.252:8443", referrer: "https://10.87.56.252:8443/Dashboard/Index"
2017/02/21 16:50:56 [error] 1976#0: *6861 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 10.87.56.98, server: , request: "GET /Dashboard/WidgetJSON?module=sysinfo&widget=general HTTP/1.1", upstream: "uwsgi://unix:///run/zentyal-webadmin/webadmin.sock:", host: "10.87.56.252:8443", referrer: "https://10.87.56.252:8443/Dashboard/Index"
2017/02/21 16:51:26 [error] 1976#0: *6862 upstream prematurely closed connection while reading response header from upstream, client: 10.87.56.98, server: , request: "GET /Dashboard/WidgetJSON?module=remoteservices&widget=ccConnection HTTP/1.1", upstream: "uwsgi://unix:///run/zentyal-webadmin/webadmin.sock:", host: "10.87.56.252:8443", referrer: "https://10.87.56.252:8443/Dashboard/Index"
2017/02/21 16:51:26 [error] 1976#0: *6863 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 10.87.56.98, server: , request: "GET /Dashboard/WidgetJSON?module=sysinfo&widget=links HTTP/1.1", upstream: "uwsgi://unix:///run/zentyal-webadmin/webadmin.sock:", host: "10.87.56.252:8443", referrer: "https://10.87.56.252:8443/Dashboard/Index"
2017/02/21 16:51:26 [error] 1976#0: *6856 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 10.87.56.98, server: , request: "GET /Dashboard/WidgetJSON?module=network&widget=interfaces HTTP/1.1", upstream: "uwsgi://unix:///run/zentyal-webadmin/webadmin.sock:", host: "10.87.56.252:8443", referrer: "https://10.87.56.252:8443/Dashboard/Index"
2017/02/21 16:51:26 [error] 1976#0: *6909 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 10.87.56.98, server: , request: "GET /Dashboard/WidgetJSON?module=sysinfo&widget=general HTTP/1.1", upstream: "uwsgi://unix:///run/zentyal-webadmin/webadmin.sock:", host: "10.87.56.252:8443", referrer: "https://10.87.56.252:8443/Dashboard/Index"
2017/02/21 16:51:26 [error] 1976#0: *6861 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 10.87.56.98, server: , request: "GET /Dashboard/WidgetJSON?module=sysinfo&widget=processes HTTP/1.1", upstream: "uwsgi://unix:///run/zentyal-webadmin/webadmin.sock:", host: "10.87.56.252:8443", referrer: "https://10.87.56.252:8443/Dashboard/Index"
2017/02/21 16:51:26 [error] 1976#0: *6860 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 10.87.56.98, server: , request: "GET /Dashboard/WidgetJSON?module=sysinfo&widget=modules HTTP/1.1", upstream: "uwsgi://unix:///run/zentyal-webadmin/webadmin.sock:", host: "10.87.56.252:8443", referrer: "https://10.87.56.252:8443/Dashboard/Index"
The weird part is that error.log is not having anything new for a week.
The exit code 25 maybe linked.
I also had to add a gateway to the conf files since it seems to disappear during the update.