Faruque Ahmed : MCP, MCSA, MCSE, MCTS, MCIT, CCNA, OCA, OCP, GCP

1

---

/var/log/zimbra.log

/opt/zimbra/log/mailbox.log

su – zimbra

zmcontrol status

zmcontrol restart

# vi /opt/zimbra/common/conf/main.cf

https://www.zimbra.com/docs/os/6.0.10/administration_guide/A_app-command-line.13.13.html

admin Login page does not load

su - zimbra

zmprov ms `zmhostname` +zimbraServiceEnabled mailbox

zmmailboxd start

*** move/rename the httpd.pid file as httpd.pid.bk

root@server [~]# cd /usr/local/apache/logs/

root@server [/usr/local/apache/logs]# mv httpd.pid httpd.pid.bak

root@server [/usr/local/apache/logs]# /etc/init.d/httpd restart

Be sure that the apache service is running :

# /etc/init.d/httpd status

zmtlsctl https

****Disable HTTPS Access

zmtlsctl http

zmcontrol restart

How to set zimbra login redirect http to https

# su – zimbra

# zmtlsctl redirect

# zmcontrol stop

# zmcontrol start

*****solve Zimbra zmconfigd not running/starting

$ zmconfigdctl status

***Problem with IPv6

# net.ipv6.conf.all.disable_ipv6 = 1

# net.ipv6.conf.default.disable_ipv6 = 1

# net.ipv6.conf.lo.disable_ipv6 = 1

# sysctl -p

# su - zimbra

$ zmconfigdctl restart

# cat /opt/zimbra/log/zmconfigd.pid

32500

# rm /opt/zimbra/log/zmconfigd.pid

# su - zimbra -c "zmconfigdctl restart"

****Zimbra Admin and Web Client not load, it is blank

zmprov ms `zmhostname` +zimbraServiceEnabled service

zmprov ms `zmhostname` +zimbraServiceEnabled zimbra

zmprov ms `zmhostname` +zimbraServiceEnabled zimbraAdmin

zmprov ms `zmhostname` +zimbraServiceEnabled zimlet

zmcontrol restart

--------- OR --------

zmprov ms $(zmhostname) +zimbraServiceEnabled service

zmprov ms $(zmhostname) +zimbraServiceEnabled zimbra

zmprov ms $(zmhostname) +zimbraServiceEnabled zimbraAdmin

zmprov ms $(zmhostname) +zimbraServiceEnabled zimlet

zmcontrol restart

-------------------

Zimbra services stop due to stale PID

Problem

Sometimes Zimbra services are stop due to stale PIDs. You can see those Stale PIDs in /var/log/zimbra.log file like this:

11:38:03 zlog zmmailboxdmgr[28932]: assuming no other instance is running

11:38:03 zlog zmmailboxdmgr[28932]: no manager process is running

11:38:03 zlog zmmailboxdmgr[28949]: stale pid 27322 found in /opt/zimbra/log/zmmailboxd_manager.pid: No such process

Solution

This can be fix after restart the Zimbra serveices:

zmcontrol restart

If you are still facing the same issue then you need to remove it manually. Please follow the below steps to remove it manually

1) Stop the Zimbra services.

su - zimbra

zmcontrol stop

2) Check if any process is still running for the 'zimbra' user then kill it.

[Run as ROOT user]

ps -elf | grep -i zimbra

kill -9 <pid>

3) Check the remove stale PID files.

[Run as ROOT user]

ls -ltr /opt/zimbra/log/*.pid

rm /opt/zimbra/log/*.pid # Press Y to confirm the file deletion.

4) Now start Zimbra services.

su - zimbra

zmcontrol start

Web Client not load

working before without issue before the upgrade.

You can also check that you are facing the issue described here, if you also run the next commands and see this results

zmmailbox -z -m account@example.com gaf ERROR: service.PROXY_ERROR (error while proxying request to target server: HTTP/1.1 404 Not Found)

zmprov fc all ERROR: service.INVALID_REQUEST (invalid request: can only be used with SOAP)

Another way to check and debug this error, is by trying to load the Web Client from the Zimbra Server

curl -v http://localhost:80 * Rebuilt URL to: http://localhost:80/ * Trying ::1... * connect to ::1 port 80 failed: Connection refused * Trying 127.0.0.1... * Connected to localhost (127.0.0.1) port 80 (#0) > GET / HTTP/1.1 > Host: localhost > User-Agent: curl/7.49.1 > Accept: */* > < HTTP/1.1 404 Not Found < Date: Sun, 24 Jul 2016 20:09:19 GMT < Content-Type: text/html < Content-Length: 440 < <HTML> <HEAD> <TITLE>Error 404 - Not Found</TITLE> <BODY> <H2>Error 404 - Not Found.</H2> No context on this server matched or handled this request.<BR>Contexts known to this server are: <ul><li><a href="/zimlet">/zimlet ---> o.e.j.w.WebAppContext@6973b51b{/zimlet,[file:///opt/zimbra/jetty-distribution-9.3.5.v20151012/webapps/zimlet/, file:///opt/zimbra/zimlets-deployed/],AVAILABLE}{/zimlet}</a></li> </ul><hr> </BODY> </HTML> * Connection #0 to host localhost left intact

Resolution

Run the next simple commands to fix the issue:

zmprov ms `zmhostname` +zimbraServiceEnabled service zmprov ms `zmhostname` +zimbraServiceEnabled zimbra zmprov ms `zmhostname` +zimbraServiceEnabled zimbraAdmin zmprov ms `zmhostname` +zimbraServiceEnabled zimlet zmcontrol restart

Additional Content

- Thank you to DualBoot to debug the issue and came with a solution on the Forums - https://forums.zimbra.org/viewtopic.php?f=15&t=59852&start=20#p269440

Verified Against: Zimbra Collaboration 8.7.1, 8.7, 8.6

Zimbra web client loading and not login

I accessed the zimbra via ssh and activated my domain which was suspended with the following command:

Unlock/Active domain Zimbra Mail Server

zmprov -l md worldcm.net zimbraDomainStatus active

zmmailboxdctl restart

After enabling domain I went back to access my admin console normally required.

---

Page updated

Google Sites

Report abuse