Failed to start Service discover server for Zextras

Hi @horizon,

please try this command and copy/paste the output :

zmcontrol -v 

zmprov gs `zmhostname` zimbraServiceEnabled

Hi, @mgabo

Is this command available in Zimbra too?

ZCS9(by zextras) failed to start zimbra.service(LSB) timeout.

Hi @funifuni ,

your problem seems to be related to systemd timeout and not for service error or misconfiguration but you need to verify on journal what is the service that is took a long time to startup.

If you are going to run manually a start for your service and you have no problem probably you need to fix systemd timeout.

I suggest you to play with this parameters on systemd :

/etc/systemd/system.conf

DefaultTimeoutStartSec=90s
DefaultTimeoutStopSec=90s

@mgabo

Thank you for your reply.

I will try it later.

In this matter, that is zimbra repository's inconsistency, I am scared that I do reboot...but,

Certainly manually start was no problem. I will edit system.conf more longer time.

I appreciate your help.thanks.

In relation to:

Only at boot time of the Ubuntu server I can see an error:

Failed to start Service discover server for Zextras

~$ zmcontrol -v
Release 22.5.1 Community Edition.

:~$ zmprov gs `zmhostname` zimbraServiceEnabled

zimbraServiceEnabled: amavis
zimbraServiceEnabled: antivirus
zimbraServiceEnabled: antispam
zimbraServiceEnabled: opendkim
zimbraServiceEnabled: memcached
zimbraServiceEnabled: directory-server
zimbraServiceEnabled: mta
zimbraServiceEnabled: service
zimbraServiceEnabled: zimbra
zimbraServiceEnabled: zimbraAdmin
zimbraServiceEnabled: zimlet
zimbraServiceEnabled: mailbox
zimbraServiceEnabled: logger
zimbraServiceEnabled: stats
zimbraServiceEnabled: proxy

@mgarbo I tried Default timeoutStartSec=1200s and Default timeoutStopSec=300s

but systemctl status zimbra----------failed.

How settings Do you think the best Sec?

If you know, please tell me.

Hi @funifuni,

There is no best sec as it depends on so many factors. In your case, the important point is to find out why carbonio start doesn't work. Looking into your system log (mailbox.log) or even sharing it here would be a good idea.

I also talked to @mgarbo and he speculated that the problem might be related to upgrading an old release of Carbonio CE to a new one like a beta version to the RC. In these scenarios we strictly recommended users perform a fresh install of Carbonio CE.

Hello

that is not correct. I executed a fresh installation with the current version of Carbonio CE on Ubuntu 20.

Same result: Failed to start Service discover server for Zextras 

This is a standalone server. All is working fine execpt the discover server fails to start.

Please suggest how to resolve

Hello @horizon, @funifuni

Have you tried inspecting the logs after the failure? Check journalctl -xe  (you can add -f to see what's happening in real time when executing the start) and you will find the reason why  service discover does not start. I f you share we might be able to help

~# journalctl -xe
--
-- A start job for unit carbonio-proxy-sidecar.service has finished successfull>
--
-- The job identifier is 5931.
Oct 04 12:44:39 mail multipathd[661]: sda: add missing path
Oct 04 12:44:39 mail multipathd[661]: sda: failed to get udev uid: Invalid argu>
Oct 04 12:44:39 mail multipathd[661]: sda: failed to get sysfs uid: Invalid arg>
Oct 04 12:44:39 mail multipathd[661]: sda: failed to get sgio uid: No such file>
Oct 04 12:44:39 mail consul[10535]: Error connecting to Consul agent: Error loa>
Oct 04 12:44:39 mail systemd[1]: carbonio-proxy-sidecar.service: Main process e>
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- An ExecStart= process belonging to unit carbonio-proxy-sidecar.service has e>
--
-- The process' exit code is 'exited' and its exit status is 1.
Oct 04 12:44:39 mail systemd[1]: carbonio-proxy-sidecar.service: Failed with re>
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- The unit carbonio-proxy-sidecar.service has entered the 'failed' state with >
lines 2281-2303/2303 (END)
--
-- A start job for unit carbonio-proxy-sidecar.service has finished successfully.
--
-- The job identifier is 5931.
Oct 04 12:44:39 mail multipathd[661]: sda: add missing path
Oct 04 12:44:39 mail multipathd[661]: sda: failed to get udev uid: Invalid argument
Oct 04 12:44:39 mail multipathd[661]: sda: failed to get sysfs uid: Invalid argument
Oct 04 12:44:39 mail multipathd[661]: sda: failed to get sgio uid: No such file or directory
Oct 04 12:44:39 mail consul[10535]: Error connecting to Consul agent: Error loading token file: open /etc/zextras/ca>
Oct 04 12:44:39 mail systemd[1]: carbonio-proxy-sidecar.service: Main process exited, code=exited, status=1/FAILURE
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- An ExecStart= process belonging to unit carbonio-proxy-sidecar.service has exited.
--
-- The process' exit code is 'exited' and its exit status is 1.
Oct 04 12:44:39 mail systemd[1]: carbonio-proxy-sidecar.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- The unit carbonio-proxy-sidecar.service has entered the 'failed' state with result 'exit-code'.

~# journalctl -u service-discover.service
-- Logs begin at Wed 2022-02-09 11:23:22 CET, end at Tue 2022-10-04 12:56:45 CEST. --
Sep 29 14:01:04 mail systemd[1]: Starting Service discover server for Zextras...
Sep 29 14:01:05 mail service-discoverd[757]: panic: runtime error: invalid memory address or nil pointer dereference
Sep 29 14:01:05 mail service-discoverd[757]: [signal SIGSEGV: segmentation violation code=0x1 addr=0x50 pc=0x5faf61]
Sep 29 14:01:05 mail service-discoverd[757]: goroutine 1 [running]:
Sep 29 14:01:05 mail service-discoverd[757]: github.com/go-ldap/ldap/v3.(*Conn).nextMessageID(...)
Sep 29 14:01:05 mail service-discoverd[757]: /home/agent/go/pkg/mod/github.com/go-ldap/ldap/v3@v3.2.4/conn.go:282
Sep 29 14:01:05 mail service-discoverd[757]: github.com/go-ldap/ldap/v3.(*Conn).doRequest(0x0, 0x6c8ca0, 0xc0000f9cc0, 0x40, 0x40, 0x65cd20)
Sep 29 14:01:05 mail service-discoverd[757]: /home/agent/go/pkg/mod/github.com/go-ldap/ldap/v3@v3.2.4/request.go:26 +0x61
Sep 29 14:01:05 mail service-discoverd[757]: github.com/go-ldap/ldap/v3.(*Conn).SimpleBind(0x0, 0xc0000f9cc0, 0x0, 0x0, 0x0)
Sep 29 14:01:05 mail service-discoverd[757]: /home/agent/go/pkg/mod/github.com/go-ldap/ldap/v3@v3.2.4/bind.go:65 +0x99
Sep 29 14:01:05 mail service-discoverd[757]: github.com/go-ldap/ldap/v3.(*Conn).Bind(0x0, 0xc00008e7c0, 0x1e, 0xc000016c65, 0x9, 0xc000126120, 0x1)
Sep 29 14:01:05 mail service-discoverd[757]: /home/agent/go/pkg/mod/github.com/go-ldap/ldap/v3@v3.2.4/bind.go:104 +0x85
Sep 29 14:01:05 mail service-discoverd[757]: bitbucket.org/zextras/service-discover/cli/lib/zimbra.connect(0xc000060660, 0xc0000e9d00, 0x466887, 0x401ab0, 0xc0000e9d88, 0x0)
Sep 29 14:01:05 mail service-discoverd[757]: /tmp/cli/lib/zimbra/ldap.go:139 +0x1be
Sep 29 14:01:05 mail service-discoverd[757]: bitbucket.org/zextras/service-discover/cli/lib/zimbra.(*ldapContext).QueryAllServersWithService(0xc000060660, 0x67bdfd, 0x10, 0x0, 0x0, 0x0, 0x0, 0x0)
Sep 29 14:01:05 mail service-discoverd[757]: /tmp/cli/lib/zimbra/ldap.go:73 +0x74
Sep 29 14:01:05 mail service-discoverd[757]: main.queryAllServiceDiscoverServers(0x6cbe78, 0xc000060660, 0x0, 0xc000060660, 0xc00001c750, 0x12)
Sep 29 14:01:05 mail service-discoverd[757]: /tmp/service-discoverd/service-discoverd.go:283 +0x4a
Sep 29 14:01:05 mail service-discoverd[757]: main.runServiceDiscoverDaemon(0x6cd548, 0x83df48, 0xc000012040, 0x2, 0x2)
Sep 29 14:01:05 mail service-discoverd[757]: /tmp/service-discoverd/service-discoverd.go:115 +0x4c5
Sep 29 14:01:05 mail service-discoverd[757]: main.main()
Sep 29 14:01:05 mail service-discoverd[757]: /tmp/service-discoverd/service-discoverd.go:83 +0x5d
Sep 29 14:01:05 mail systemd[1]: service-discover.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
Sep 29 14:01:05 mail systemd[1]: service-discover.service: Failed with result 'exit-code'.
Sep 29 14:01:05 mail systemd[1]: Failed to start Service discover server for Zextras.
Sep 29 14:01:20 mail systemd[1]: service-discover.service: Scheduled restart job, restart counter is at 1.
Sep 29 14:01:20 mail systemd[1]: Stopped Service discover server for Zextras.
Sep 29 14:01:20 mail systemd[1]: Starting Service discover server for Zextras...
Sep 29 14:01:20 mail service-discoverd[1203]: local service-discover server NOT present in ldap/zimbraServiceEnabled attribute mail.ourname.nl
Sep 29 14:01:20 mail systemd[1]: service-discover.service: Main process exited, code=exited, status=236/SMACK_PROCESS_LABEL
Sep 29 14:01:20 mail systemd[1]: service-discover.service: Failed with result 'exit-code'.
Sep 29 14:01:20 mail systemd[1]: Failed to start Service discover server for Zextras.
Sep 29 14:01:35 mail systemd[1]: service-discover.service: Scheduled restart job, restart counter is at 2.
Sep 29 14:01:35 mail systemd[1]: Stopped Service discover server for Zextras.
Sep 29 14:01:35 mail systemd[1]: Starting Service discover server for Zextras...
Sep 29 14:01:35 mail service-discoverd[1797]: local service-discover server NOT present in ldap/zimbraServiceEnabled attribute mail.ourname.nl
Sep 29 14:01:35 mail systemd[1]: service-discover.service: Main process exited, code=exited, status=236/SMACK_PROCESS_LABEL
Sep 29 14:01:35 mail systemd[1]: service-discover.service: Failed with result 'exit-code'.
Sep 29 14:01:35 mail systemd[1]: Failed to start Service discover server for Zextras.
Sep 29 14:01:51 mail systemd[1]: service-discover.service: Scheduled restart job, restart counter is at 3.
Sep 29 14:01:51 mail systemd[1]: Stopped Service discover server for Zextras.
Sep 29 14:01:51 mail systemd[1]: Starting Service discover server for Zextras...
Sep 29 14:01:51 mail service-discoverd[2969]: local service-discover server NOT present in ldap/zimbraServiceEnabled attribute mail.ourname.nl
Sep 29 14:01:51 mail systemd[1]: service-discover.service: Main process exited, code=exited, status=236/SMACK_PROCESS_LABEL
Sep 29 14:01:51 mail systemd[1]: service-discover.service: Failed with result 'exit-code'.
Sep 29 14:01:51 mail systemd[1]: Failed to start Service discover server for Zextras.

journalctl -f:

Oct 04 13:16:47 mail systemd[1]: Starting Service discover server for Zextras...
Oct 04 13:16:47 mail service-discoverd[40674]: local service-discover server NOT present in ldap/zimbraServiceEnabled attribute mail.ourname.nl
Oct 04 13:16:47 mail systemd[1]: service-discover.service: Main process exited, code=exited, status=236/SMACK_PROCESS_LABEL
Oct 04 13:16:47 mail systemd[1]: service-discover.service: Failed with result 'exit-code'.
Oct 04 13:16:47 mail systemd[1]: Failed to start Service discover server for Zextras.
Oct 04 13:16:50 mail multipathd[661]: sda: add missing path
Oct 04 13:16:50 mail multipathd[661]: sda: failed to get udev uid: Invalid argument
Oct 04 13:16:50 mail multipathd[661]: sda: failed to get sysfs uid: Invalid argument
Oct 04 13:16:50 mail multipathd[661]: sda: failed to get sgio uid: No such file or directory
Oct 04 13:16:55 mail systemd[1]: carbonio-mta-sidecar.service: Scheduled restart job, restart counter is at 142.
Oct 04 13:16:55 mail systemd[1]: Stopped Carbonio mta sidecar proxy.
Oct 04 13:16:55 mail systemd[1]: Started Carbonio mta sidecar proxy.
Oct 04 13:16:55 mail consul[40696]: Error connecting to Consul agent: Error loading token file: open /etc/carbonio/mta/service-discover/token: no such file or directory
Oct 04 13:16:55 mail systemd[1]: carbonio-mta-sidecar.service: Main process exited, code=exited, status=1/FAILURE
Oct 04 13:16:55 mail systemd[1]: carbonio-mta-sidecar.service: Failed with result 'exit-code'.
Oct 04 13:16:55 mail systemd[1]: carbonio-mailbox-sidecar.service: Scheduled restart job, restart counter is at 142.
Oct 04 13:16:55 mail systemd[1]: Stopped Mailbox carbonio proxy sidecar.

@horizon it seems that you doesn't completed the installation or missed some steps.

I installed many times carbonio CE without problem.

Sep 29 1405 mail service-discoverd[757]: github.com/go-ldap/ldap/v3.(*Conn).nextMessageID(...)

This errors means that you cannot contact ldap.

After you installed carbonio with "apt" (ubuntu) or "dfn" (centos like), step 3, did you run this command?

carbonio-bootstrap

Please read carefully the installation guide https://docs.zextras.com/carbonio-ce/html/installation.html , if you missed one of steps in this guide you will fail to start it.

just to be sure, I did a fresh installation, exactly according to https://docs.zextras.com/carbonio-ce/html/installation.html

After the installation, this is the status:

~$ zmcontrol status
Host mail.xxxx.nl
amavis Running
antispam Running
antivirus Running
directory-server Running
logger Running
mailbox Running
memcached Running
mta Running
opendkim Running
proxy Running
service webapp Running
stats Running
zimbra webapp Running
zimbraAdmin webapp Running
zimlet webapp Running
zmconfigd Running

During the boot process of Ubuntu, I still see that the discover server fails to start with same error syntax.