服务启动Zimbra服务无法正常启动
2013-05-30 20:52
113 查看
最近一直在学习服务启动之类的问题,今天正好有机会和大家共享一下.
1. 问题描述
1) zimbra服务状态:
2) zimbra的/var/log/mail.log日记信息如下:
每日一道理
只有启程,才会到达理想和目的地,只有拼搏,才会获得辉煌的成功,只有播种,才会有收获。只有追求,才会品味堂堂正正的人。
2.解决方法
需要更新文件/opt/zimbra/conf/localconfig.xml中zimbra的UIDs,然后重新执行上述步调进行修复就能够了
注:zimbra的UID可以在 /etc/passwd文件查询
文章结束给大家分享下程序员的一些笑话语录: 一位程序员去海边游泳,由于水性不佳,游不回岸了,于是他挥着手臂,大声求.救:“F1,F1!”
---------------------------------
原创文章 By
服务和启动
---------------------------------
1. 问题描述
1) zimbra服务状态:
zimbra@mail:~$ zmcontrol status Host mail.example.com antispam Running antivirus Running ldap Running logger Running mailbox Stopped zmmailboxdctl is not running. mta Running snmp Running spell Running stats Running zmconfigd Running zimbra@mail:~$
2) zimbra的/var/log/mail.log日记信息如下:
每日一道理
只有启程,才会到达理想和目的地,只有拼搏,才会获得辉煌的成功,只有播种,才会有收获。只有追求,才会品味堂堂正正的人。
Mar 7 20:12:20 mail zimbramon[10875]: 10875:info: Starting snmp via zmcontrol Mar 7 20:12:20 mail zimbramon[10875]: 10875:info: Starting spell via zmcontrol Mar 7 20:12:20 mail zimbramon[10875]: 10875:info: Starting mta via zmcontrol Mar 7 20:12:21 mail postfix/postfix-script[12799]: warning: not owned by root: /opt/zimbra/postfix-2.7.7.3z/conf/main.cf Mar 7 20:12:21 mail postfix/postfix-script[12800]: warning: not owned by root: /opt/zimbra/postfix-2.7.7.3z/conf/master.cf Mar 7 20:12:21 mail postfix/postfix-script[12801]: warning: not owned by root: /opt/zimbra/postfix-2.7.7.3z/conf/master.cf.in Mar 7 20:12:21 mail postfix/postfix-script[12817]: starting the Postfix mail system Mar 7 20:12:21 mail postfix/master[12818]: daemon started -- version 2.7.7, configuration /opt/zimbra/postfix-2.7.7.3z/conf Mar 7 20:12:21 mail saslauthd[12826]: detach_tty : master pid is: 12826 Mar 7 20:12:21 mail saslauthd[12826]: ipc_init : listening on socket: /opt/zimbra/cyrus-sasl-2.1.23.3z/state/mux Mar 7 20:12:21 mail zimbramon[10875]: 10875:info: Starting stats via zmcontrol Mar 7 20:12:37 mail zmmailboxdmgr[13978]: status requested Mar 7 20:12:37 mail zmmailboxdmgr[13978]: stale pid 12479 found in /opt/zimbra/log/zmmailboxd_manager.pid: No such process Mar 7 20:12:37 mail zmmailboxdmgr[13978]: assuming no other instance is running Mar 7 20:12:37 mail zmmailboxdmgr[13978]: file /opt/zimbra/log/zmmailboxd.pid does not exist Mar 7 20:12:37 mail zmmailboxdmgr[13978]: assuming no other instance is running Mar 7 20:12:37 mail zmmailboxdmgr[13978]: no manager process is running Mar 7 20:12:37 mail zmmailboxdmgr[13986]: status requested Mar 7 20:12:37 mail zmmailboxdmgr[13986]: stale pid 12479 found in /opt/zimbra/log/zmmailboxd_manager.pid: No such process Mar 7 20:12:37 mail zmmailboxdmgr[13986]: assuming no other instance is running Mar 7 20:12:37 mail zmmailboxdmgr[13986]: file /opt/zimbra/log/zmmailboxd.pid does not exist Mar 7 20:12:37 mail zmmailboxdmgr[13986]: assuming no other instance is running Mar 7 20:12:37 mail zmmailboxdmgr[13986]: no manager process is running Mar 7 20:12:38 mail zmmailboxdmgr[14215]: status requested Mar 7 20:12:38 mail zmmailboxdmgr[14215]: stale pid 12479 found in /opt/zimbra/log/zmmailboxd_manager.pid: No such process Mar 7 20:12:38 mail zmmailboxdmgr[14215]: assuming no other instance is running Mar 7 20:12:38 mail zmmailboxdmgr[14215]: file /opt/zimbra/log/zmmailboxd.pid does not exist Mar 7 20:12:38 mail zmmailboxdmgr[14215]: assuming no other instance is running Mar 7 20:12:38 mail zmmailboxdmgr[14215]: no manager process is running Mar 7 20:13:39 mail zmmailboxdmgr[14460]: status requested Mar 7 20:13:39 mail zmmailboxdmgr[14460]: stale pid 12479 found in /opt/zimbra/log/zmmailboxd_manager.pid: No such process Mar 7 20:13:39 mail zmmailboxdmgr[14460]: assuming no other instance is running Mar 7 20:13:39 mail zmmailboxdmgr[14460]: file /opt/zimbra/log/zmmailboxd.pid does not exist Mar 7 20:13:39 mail zmmailboxdmgr[14460]: assuming no other instance is running Mar 7 20:13:39 mail zmmailboxdmgr[14460]: no manager process is running Mar 7 20:13:39 mail zmmailboxdmgr[14468]: status requested Mar 7 20:13:39 mail zmmailboxdmgr[14468]: stale pid 12479 found in /opt/zimbra/log/zmmailboxd_manager.pid: No such process Mar 7 20:13:39 mail zmmailboxdmgr[14468]: assuming no other instance is running Mar 7 20:13:39 mail zmmailboxdmgr[14468]: file /opt/zimbra/log/zmmailboxd.pid does not exist Mar 7 20:13:39 mail zmmailboxdmgr[14468]: assuming no other instance is running Mar 7 20:13:39 mail zmmailboxdmgr[14468]: no manager process is running Mar 7 20:14:04 mail zmmailboxdmgr[14923]: status requested Mar 7 20:14:04 mail zmmailboxdmgr[14923]: stale pid 12479 found in /opt/zimbra/log/zmmailboxd_manager.pid: No such process Mar 7 20:14:04 mail zmmailboxdmgr[14923]: assuming no other instance is running Mar 7 20:14:04 mail zmmailboxdmgr[14923]: file /opt/zimbra/log/zmmailboxd.pid does not exist Mar 7 20:14:04 mail zmmailboxdmgr[14923]: assuming no other instance is running Mar 7 20:14:04 mail zmmailboxdmgr[14923]: no manager process is running
2.解决方法
1) As root - # mv /opt/zimbra/mailboxd/etc/keystore /root/keystore.old 2) As root - # /opt/zimbra/bin/zmcertmgr deploycrt self 3) As root - /opt/zimbra/libexec/zmfixperms --verbose --extended 4) Login as the zimbra and restart all of zimbra 修复后的zimbra服务状态如下:
zimbra服务启动后,若还不能畸形拜访,出现如下图所示景象:
需要更新文件/opt/zimbra/conf/localconfig.xml中zimbra的UIDs,然后重新执行上述步调进行修复就能够了
注:zimbra的UID可以在 /etc/passwd文件查询
文章结束给大家分享下程序员的一些笑话语录: 一位程序员去海边游泳,由于水性不佳,游不回岸了,于是他挥着手臂,大声求.救:“F1,F1!”
---------------------------------
原创文章 By
服务和启动
---------------------------------
相关文章推荐
- Zimbra服务无法正常启动
- Zimbra服务无法正常启动
- MySQL之前一直正常使用,更新了一下系统之后出现“MySQL 服务无法启动,发生系统错误 1067 ”
- Linux 下 apache mysql等服务修改默认端口后无法正常启动解决办法
- 浅析Win8/8.1下安装SQL Server 2005 出现服务项无法正常启动解决方案
- mysql服务无法正常启动
- mysql服务无法正常启动
- Avira AntiVir 造成 SqlServer 服务无法正常启动问题的解决
- 【spring cloud】服务启动后正常,但是无法上线,一直处于down状态
- CTSSD服务无法正常启动:Failure 4 in trying to open SV key PROCL-4/PROCL-5 clsctss_r_av2
- 安装hbase后重启服务,发现zookeeper在某台机器上无法正常启动
- 解决windows下APACHE服务无法正常启动问题
- Linux下MySQL服务突然无法正常启动
- tomcat脚本启动正常,服务无法启动,特定错误代码1
- SQLServer安装正常服务启动正常却无法连接
- Linux下apache服务启动,本机访问正常,局域网内其他机器无法访问(已解决)
- cvsnt服务无法正常启动
- oracle服务监听启动正常,但无法连接
- OracleOraDb10g_home1iSQL*Plus服务无法正常启动的解决方法
- SQL服务无法正常启动及数据库卸载