- Can you provide the output of $zmprov gs zimbraServiceEnabled
Answer: ERROR: service.PROXY_ERROR (error while proxying request to target server: HTTP/1.1 404 Not Found)
- Do you see /opt/zimbra/jetty/webapps/service, /opt/zimbra/jetty/webapps/zimbra, /opt/zimbra/jetty/webapps/zimbraAdmin?
Answer: Yes
Zimbra 8.5.0 and centos 7 not working after reboot
-
- Posts: 30
- Joined: Sat Sep 13, 2014 3:36 am
-
- Posts: 30
- Joined: Sat Sep 13, 2014 3:36 am
Zimbra 8.5.0 and centos 7 not working after reboot
output zmmailboxd.out
OpenJDK 64-Bit Server VM warning: ignoring option PermSize=128m; support was removed in 8.0
OpenJDK 64-Bit Server VM warning: ignoring option MaxPermSize=350m; support was removed in 8.0
OpenJDK 64-Bit Server VM warning: .hotspot_compiler file is present but has been ignored. Run with -XX:CompileCommandFile=.hotspot_compiler to load the file.
2014-08-27 23:50:05.332:INFO::main: Logging initialized @1432ms
JettyMonitor monitoring thread pool qtp509886383{STOPPED,10
Zimbra server reserving server socket port=110 bindaddr=null ssl=false
Zimbra server reserving server socket port=995 bindaddr=null ssl=false
Zimbra server reserving server socket port=143 bindaddr=null ssl=false
Zimbra server reserving server socket port=993 bindaddr=null ssl=false
Zimbra server reserving server socket port=7025 bindaddr=null ssl=false
2014-08-27 23:50:06.048:INF:ejs.SetUIDListener:main: Setting umask=027
2014-08-27 23:50:06.048:INF:ejs.SetUIDListener:main: Current rlimit_nofiles (soft=524288, hard=524288)
2014-08-27 23:50:06.048:INF:ejs.SetUIDListener:main: Set rlimit_nofiles (soft=65536, hard=65536)
2014-08-27 23:50:06.083:INF:ejs.SetUIDListener:main: Opened ServerConnector@59ec2012{HTTP/1.1}{localhost:80}
2014-08-27 23:50:06.083:INF:ejs.SetUIDListener:main: Opened ServerConnector@4b952a2d{SSL-http/1.1}{0.0.0.0:443}
2014-08-27 23:50:06.083:INF:ejs.SetUIDListener:main: Opened ServerConnector@73846619{SSL-http/1.1}{0.0.0.0:7071}
2014-08-27 23:50:06.084:INF:ejs.SetUIDListener:main: Opened ServerConnector@29ca901e{HTTP/1.1}{0.0.0.0:7072}
2014-08-27 23:50:06.084:INF:ejs.SetUIDListener:main: Setting GID=996
2014-08-27 23:50:06.096:INF:ejs.SetUIDListener:main: Setting UID=997
2014-08-27 23:50:06.101:INF:ejs.Server:main: jetty-9.1.5.v20140505
2014-08-27 23:50:06.404:WARN:oejs.SecurityHandler:main: Path with uncovered http methods: /
2014-08-27 23:50:06.423:INFO:oejsh.ContextHandler:main: Started o.e.j.w.WebAppContext@45afc369{/zimlet,[file:/opt/zimbra/jetty-distribution-9.1.5.v20140505/webapps/zimlet/, file:/opt/zimbra/zimlets-deployed/],AVAILABLE}{/zimlet}
2014-08-27 23:50:06.429:INFO:ejs.AbstractNCSARequestLog:main: Opened /opt/zimbra/log/access_log.2014-08-27
2014-08-27 23:50:06.444:INFO:ejs.ServerConnector:main: Started ServerConnector@59ec2012{HTTP/1.1}{localhost:80}
2014-08-27 23:50:06.550:INFO:ejs.ServerConnector:main: Started ServerConnector@4b952a2d{SSL-http/1.1}{0.0.0.0:443}
2014-08-27 23:50:06.554:INFO:ejs.ServerConnector:main: Started ServerConnector@73846619{SSL-http/1.1}{0.0.0.0:7071}
2014-08-27 23:50:06.555:INFO:ejs.ServerConnector:main: Started ServerConnector@29ca901e{HTTP/1.1}{0.0.0.0:7072}
2014-08-27 23:50:06.555:INFO:ejs.Server:main: Started @2686ms
OpenJDK 64-Bit Server VM warning: ignoring option PermSize=128m; support was removed in 8.0
OpenJDK 64-Bit Server VM warning: ignoring option MaxPermSize=350m; support was removed in 8.0
OpenJDK 64-Bit Server VM warning: .hotspot_compiler file is present but has been ignored. Run with -XX:CompileCommandFile=.hotspot_compiler to load the file.
2014-08-27 23:50:05.332:INFO::main: Logging initialized @1432ms
JettyMonitor monitoring thread pool qtp509886383{STOPPED,10
Zimbra server reserving server socket port=110 bindaddr=null ssl=false
Zimbra server reserving server socket port=995 bindaddr=null ssl=false
Zimbra server reserving server socket port=143 bindaddr=null ssl=false
Zimbra server reserving server socket port=993 bindaddr=null ssl=false
Zimbra server reserving server socket port=7025 bindaddr=null ssl=false
2014-08-27 23:50:06.048:INF:ejs.SetUIDListener:main: Setting umask=027
2014-08-27 23:50:06.048:INF:ejs.SetUIDListener:main: Current rlimit_nofiles (soft=524288, hard=524288)
2014-08-27 23:50:06.048:INF:ejs.SetUIDListener:main: Set rlimit_nofiles (soft=65536, hard=65536)
2014-08-27 23:50:06.083:INF:ejs.SetUIDListener:main: Opened ServerConnector@59ec2012{HTTP/1.1}{localhost:80}
2014-08-27 23:50:06.083:INF:ejs.SetUIDListener:main: Opened ServerConnector@4b952a2d{SSL-http/1.1}{0.0.0.0:443}
2014-08-27 23:50:06.083:INF:ejs.SetUIDListener:main: Opened ServerConnector@73846619{SSL-http/1.1}{0.0.0.0:7071}
2014-08-27 23:50:06.084:INF:ejs.SetUIDListener:main: Opened ServerConnector@29ca901e{HTTP/1.1}{0.0.0.0:7072}
2014-08-27 23:50:06.084:INF:ejs.SetUIDListener:main: Setting GID=996
2014-08-27 23:50:06.096:INF:ejs.SetUIDListener:main: Setting UID=997
2014-08-27 23:50:06.101:INF:ejs.Server:main: jetty-9.1.5.v20140505
2014-08-27 23:50:06.404:WARN:oejs.SecurityHandler:main: Path with uncovered http methods: /
2014-08-27 23:50:06.423:INFO:oejsh.ContextHandler:main: Started o.e.j.w.WebAppContext@45afc369{/zimlet,[file:/opt/zimbra/jetty-distribution-9.1.5.v20140505/webapps/zimlet/, file:/opt/zimbra/zimlets-deployed/],AVAILABLE}{/zimlet}
2014-08-27 23:50:06.429:INFO:ejs.AbstractNCSARequestLog:main: Opened /opt/zimbra/log/access_log.2014-08-27
2014-08-27 23:50:06.444:INFO:ejs.ServerConnector:main: Started ServerConnector@59ec2012{HTTP/1.1}{localhost:80}
2014-08-27 23:50:06.550:INFO:ejs.ServerConnector:main: Started ServerConnector@4b952a2d{SSL-http/1.1}{0.0.0.0:443}
2014-08-27 23:50:06.554:INFO:ejs.ServerConnector:main: Started ServerConnector@73846619{SSL-http/1.1}{0.0.0.0:7071}
2014-08-27 23:50:06.555:INFO:ejs.ServerConnector:main: Started ServerConnector@29ca901e{HTTP/1.1}{0.0.0.0:7072}
2014-08-27 23:50:06.555:INFO:ejs.Server:main: Started @2686ms
-
- Zimbra Alumni
- Posts: 113
- Joined: Sat Sep 13, 2014 1:20 am
Zimbra 8.5.0 and centos 7 not working after reboot
[quote user="ckruijntjens"]- Can you provide the output of $zmprov gs zimbraServiceEnabled
Answer: ERROR: service.PROXY_ERROR (error while proxying request to target server: HTTP/1.1 404 Not Found)
[/QUOTE]
Oops I should have mentioned to use the -l switch since /service is not enabled
$zmprov -l gs `zmhostname` zimbraServiceEnabled
Answer: ERROR: service.PROXY_ERROR (error while proxying request to target server: HTTP/1.1 404 Not Found)
[/QUOTE]
Oops I should have mentioned to use the -l switch since /service is not enabled
$zmprov -l gs `zmhostname` zimbraServiceEnabled
-
- Posts: 30
- Joined: Sat Sep 13, 2014 3:36 am
Zimbra 8.5.0 and centos 7 not working after reboot
zimbraServiceEnabled: amavis zimbraServiceEnabled: antivirus zimbraServiceEnabled: antispam zimbraServiceEnabled: opendkim zimbraServiceEnabled: logger zimbraServiceEnabled: mailbox zimbraServiceEnabled: mta zimbraServiceEnabled: dnscache zimbraServiceEnabled: stats zimbraServiceEnabled: snmp zimbraServiceEnabled: spell zimbraServiceEnabled: ldap
Sent from my iPhone using Tapatalk
Sent from my iPhone using Tapatalk
-
- Zimbra Alumni
- Posts: 113
- Joined: Sat Sep 13, 2014 1:20 am
Zimbra 8.5.0 and centos 7 not working after reboot
OK, that explains things on one level since there are missing values; but does not explain how they could have possibly been removed between the time the system was working and when you rebooted and found it not working. An 8.5.0 GA system would never have worked if the initial install did not set them.
What I suggest is manually adding the values in question and see how that goes. Then keep an eye on things and see if they mysteriously disappear later. Based on earlier comments in this thread I've tried to repro by using zmtlsctl and other CLI tools that might incorrectly affect these attributes, but so far no luck.
$zmprov -l ms `zmhostname` +zimbraServiceEnabled service
$zmprov -l ms `zmhostname` +zimbraServiceEnabled zimbra
$zmprov -l ms `zmhostname` +zimbraServiceEnabled zimbraAdmin
$zmprov -l ms `zmhostname` +zimbraServiceEnabled zimlet
$zmmailboxdctl restart
What I suggest is manually adding the values in question and see how that goes. Then keep an eye on things and see if they mysteriously disappear later. Based on earlier comments in this thread I've tried to repro by using zmtlsctl and other CLI tools that might incorrectly affect these attributes, but so far no luck.
$zmprov -l ms `zmhostname` +zimbraServiceEnabled service
$zmprov -l ms `zmhostname` +zimbraServiceEnabled zimbra
$zmprov -l ms `zmhostname` +zimbraServiceEnabled zimbraAdmin
$zmprov -l ms `zmhostname` +zimbraServiceEnabled zimlet
$zmmailboxdctl restart
-
- Posts: 30
- Joined: Sat Sep 13, 2014 3:36 am
Zimbra 8.5.0 and centos 7 not working after reboot
Thanx it Works but after a reboot it is not. Im am going back to centos 6.5 and zimbra 8.0.7 things are working then. Zimbra 8.5 is to buggy in my opinion. Thanx for the help. Im questoning if more people have these problems??
Sent from my iPhone using Tapatalk
Sent from my iPhone using Tapatalk
-
- Posts: 1
- Joined: Sat Sep 13, 2014 3:57 am
Zimbra 8.5.0 and centos 7 not working after reboot
[quote user="ckruijntjens"]Im questoning if more people have these problems??
[/QUOTE]
Yes i am more people :) i have this problem too, its VERY annoying, specially since this is the only thread i think with a 50% fix. As ckruijntjens mentioned, after a zimbra restart its reset again and have to enable them manually again, please bring out patch asap. this is not workable.
[/QUOTE]
Yes i am more people :) i have this problem too, its VERY annoying, specially since this is the only thread i think with a 50% fix. As ckruijntjens mentioned, after a zimbra restart its reset again and have to enable them manually again, please bring out patch asap. this is not workable.
-
- Posts: 2
- Joined: Sat Sep 13, 2014 3:57 am
Zimbra 8.5.0 and centos 7 not working after reboot
I agree, whole 8.5.0 is crap. For example, i have ssh port not 22, but 100 and after update "Configure -> Servers -> mail.domain.tld" stop working. (zmserverips ..... with Error code: service.FAILURE Details:soap:Receiver)
Yes - i know:
zmprov mcf zimbraRemoteManagementPort 100
I tried:
ssh -vi .ssh/zimbra_identity -o strictHostKeyChecking=no zimbra@mail.domain.tld -p 100
And it works OK, so problem is not in sshd. I have disabled SElinux, firewall is OK, rights are OK, i tried generating new ssh keys, zmfixperms, ... i read Mail Queue Monitoring - Zimbra :: Wiki but nothing works.
In /var/log/secure is:
Aug 28 11:02:25 router sshd[12963]: Accepted publickey for zimbra from 192.168.1.254 port 56146 ssh2
Aug 28 11:02:26 router sshd[12963]: pam_unix(sshd:session): session opened for user zimbra by (uid=0)
Aug 28 11:02:28 router sshd[12969]: Received disconnect from 192.168.1.254: 11: Closed due to user request.
Aug 28 11:02:28 router sshd[12963]: pam_unix(sshd:session): session closed for user zimbra
So in sshd is really no problem.
I thought that update something broke, so i make clean install (./install -u, remove all from /opt, reboot, ./install) and still this error. In addition in clean install i cannot create new domain.
Problem is only in 8.5.0 when i downgrade from backup everything works.
I really love this project and Zimbra developers are for me heroes, but version 8.5.0 is not final version, it is not even beta, it is heavy alpha. This errors are shame.
Sorry for my bad english - i hope that you understand me
Yes - i know:
zmprov mcf zimbraRemoteManagementPort 100
I tried:
ssh -vi .ssh/zimbra_identity -o strictHostKeyChecking=no zimbra@mail.domain.tld -p 100
And it works OK, so problem is not in sshd. I have disabled SElinux, firewall is OK, rights are OK, i tried generating new ssh keys, zmfixperms, ... i read Mail Queue Monitoring - Zimbra :: Wiki but nothing works.
In /var/log/secure is:
Aug 28 11:02:25 router sshd[12963]: Accepted publickey for zimbra from 192.168.1.254 port 56146 ssh2
Aug 28 11:02:26 router sshd[12963]: pam_unix(sshd:session): session opened for user zimbra by (uid=0)
Aug 28 11:02:28 router sshd[12969]: Received disconnect from 192.168.1.254: 11: Closed due to user request.
Aug 28 11:02:28 router sshd[12963]: pam_unix(sshd:session): session closed for user zimbra
So in sshd is really no problem.
I thought that update something broke, so i make clean install (./install -u, remove all from /opt, reboot, ./install) and still this error. In addition in clean install i cannot create new domain.
Problem is only in 8.5.0 when i downgrade from backup everything works.
I really love this project and Zimbra developers are for me heroes, but version 8.5.0 is not final version, it is not even beta, it is heavy alpha. This errors are shame.
Sorry for my bad english - i hope that you understand me
Zimbra 8.5.0 and centos 7 not working after reboot
I to have the same problem.
Ubuntu 14.04 and Zimbra 8.5.
Ubuntu 14.04 and Zimbra 8.5.
-
- Advanced member
- Posts: 197
- Joined: Sat Sep 13, 2014 3:52 am
- ZCS/ZD Version: Zimbra Collaboration 8.7
Zimbra 8.5.0 and centos 7 not working after reboot
Hi guys,
I did a multiple upgrades and in any of them I had this problem. Could you please try to re-install again Zimbra 8.5.0, launch again the /install.sh script and follow all the steps, after that reboot and tell us.
Best regards
I did a multiple upgrades and in any of them I had this problem. Could you please try to re-install again Zimbra 8.5.0, launch again the /install.sh script and follow all the steps, after that reboot and tell us.
Best regards
Who is online
Users browsing this forum: No registered users and 9 guests