Hi dear All,
Here I have a terrible problem that does not permit me to administer the Zimbra CS - admin page not starting, port 7071 not listen. Is there a way to debug the problem, somebody to help?
zimbraAdmin console not accessible
Re: zimbraAdmin console not accessible
From the logs I can see errors, like:
Jan 20 12:48:25 mail zimbra[1050]: #011Starting zmconfigd...Failed.
Jan 20 12:48:25 mail zimbra[1050]: Starting zmconfigd.../opt/zimbra/bin/zmconfigdctl: line 82: kill: (682397) - No such process
Jan 20 12:48:25 mail zimbra[1050]: failed.
Jan 20 12:51:40 mail systemd[1]: zimbra.service: start operation timed out. Terminating.
Jan 20 12:51:40 mail systemd[1]: zimbra.service: Failed with result 'timeout'.
Jan 20 12:51:40 mail systemd[1]: Failed to start LSB: Zimbra mail service.
At the same time, there is:
Jan 20 12:54:32 mail zimbra[1050]: #011Starting zimbraAdmin webapp...Done.
But the port 7071 is not open:
[root@mail rsyslog]# nmap localhost
Starting Nmap 7.70 ( https://nmap.org ) at 2023-01-20 14:05 EET
Nmap scan report for localhost (127.0.0.1)
Host is up (0.0000080s latency).
Not shown: 981 closed ports
PORT STATE SERVICE
22/tcp open ssh
25/tcp open smtp
53/tcp open domain
110/tcp open pop3
111/tcp open rpcbind
143/tcp open imap
443/tcp open https
465/tcp open smtps
587/tcp open submission
631/tcp open ipp
993/tcp open imaps
995/tcp open pop3s
5222/tcp open xmpp-client
5269/tcp open xmpp-server
7025/tcp open vmsvc-2
8080/tcp open http-proxy
8443/tcp open https-alt
10024/tcp open unknown
10025/tcp open unknown
Nmap done: 1 IP address (1 host up) scanned in 1.59 seconds
Jan 20 12:48:25 mail zimbra[1050]: #011Starting zmconfigd...Failed.
Jan 20 12:48:25 mail zimbra[1050]: Starting zmconfigd.../opt/zimbra/bin/zmconfigdctl: line 82: kill: (682397) - No such process
Jan 20 12:48:25 mail zimbra[1050]: failed.
Jan 20 12:51:40 mail systemd[1]: zimbra.service: start operation timed out. Terminating.
Jan 20 12:51:40 mail systemd[1]: zimbra.service: Failed with result 'timeout'.
Jan 20 12:51:40 mail systemd[1]: Failed to start LSB: Zimbra mail service.
At the same time, there is:
Jan 20 12:54:32 mail zimbra[1050]: #011Starting zimbraAdmin webapp...Done.
But the port 7071 is not open:
[root@mail rsyslog]# nmap localhost
Starting Nmap 7.70 ( https://nmap.org ) at 2023-01-20 14:05 EET
Nmap scan report for localhost (127.0.0.1)
Host is up (0.0000080s latency).
Not shown: 981 closed ports
PORT STATE SERVICE
22/tcp open ssh
25/tcp open smtp
53/tcp open domain
110/tcp open pop3
111/tcp open rpcbind
143/tcp open imap
443/tcp open https
465/tcp open smtps
587/tcp open submission
631/tcp open ipp
993/tcp open imaps
995/tcp open pop3s
5222/tcp open xmpp-client
5269/tcp open xmpp-server
7025/tcp open vmsvc-2
8080/tcp open http-proxy
8443/tcp open https-alt
10024/tcp open unknown
10025/tcp open unknown
Nmap done: 1 IP address (1 host up) scanned in 1.59 seconds
Re: zimbraAdmin console not accessible
Is there anybody alive?
I have investigated a bit and found, that the server is responding on the 7071 port, although it is not shown with the command nmap localhost. So, this is an important update! But nevertheless, the console is not working.
Next what I've found is that the browser loads a page, byt it remains invisible. While inspecting found a continuously increasing counter for "Exception in launch(): undefined" and one more error that says:
Admin_all.js.zgz?v=220121005234:1232
Uncaught TypeError: Cannot read properties of undefined (reading 'toLowerCase')
at Admin_all.js.zgz?v=22012100523454
Next step was opening in Internet Explorer mode and ... Voila!!! IE mode showed the page.
So, I'm assuming that zimbra uses some old jetty routines that are not accepted by up-to-day browsers. There is no other explanation for this.
BTW, I have a second server for other domain, its zimbraAdmin console is opening with no issues. The difference is that this server is updated to the patch 33. So, I will apply this patch to the server with broken admin console and will see what happens.
Will update this tomorrow.
I have investigated a bit and found, that the server is responding on the 7071 port, although it is not shown with the command nmap localhost. So, this is an important update! But nevertheless, the console is not working.
Next what I've found is that the browser loads a page, byt it remains invisible. While inspecting found a continuously increasing counter for "Exception in launch(): undefined" and one more error that says:
Admin_all.js.zgz?v=220121005234:1232
Uncaught TypeError: Cannot read properties of undefined (reading 'toLowerCase')
at Admin_all.js.zgz?v=22012100523454
Next step was opening in Internet Explorer mode and ... Voila!!! IE mode showed the page.
So, I'm assuming that zimbra uses some old jetty routines that are not accepted by up-to-day browsers. There is no other explanation for this.
BTW, I have a second server for other domain, its zimbraAdmin console is opening with no issues. The difference is that this server is updated to the patch 33. So, I will apply this patch to the server with broken admin console and will see what happens.
Will update this tomorrow.
Re: zimbraAdmin console not accessible
Update to the issue.
The problem is gone... I didn't updated yet, but the admin console became available in Edge, not in Firefox. Is it because I've set IECompatibility for the site?
But in case I access the console by IP-address - it opens in Firefox as well. So, the problem seems to be linked to the routing.
I guess, the case can be closed. Thanks to all for supporting.
The problem is gone... I didn't updated yet, but the admin console became available in Edge, not in Firefox. Is it because I've set IECompatibility for the site?
But in case I access the console by IP-address - it opens in Firefox as well. So, the problem seems to be linked to the routing.
I guess, the case can be closed. Thanks to all for supporting.