Zimbra docs "Connection refused"

Discuss your pilot or production implementation with other Zimbra admins or our engineers.
Post Reply
User avatar
winproof
Posts: 22
Joined: Thu Aug 29, 2019 10:38 pm
ZCS/ZD Version: 9.0.0_GA_3976

Zimbra docs "Connection refused"

Post by winproof »

Hello
i'm testing zimbra network edition (8.8.15_GA_3847), installed on ubuntu 18.04 LTS, on Vmware workstation 14 Pro, with dnsmasq.
all is ok.

now i try to add zimbra docs, installation is ok, no error, ldap doc server account correctly added.
zimlet "com_zextras_docs" installed and activated in default COS
proxy re-generated and restarted whitout problems.

but when i try to create a doc (via web), doc is created, the editing windows open but is blank/empty.

mailbox.log :

Code: Select all

2019-08-30 00:55:19,649 INFO  [qtp961409111-513:https://pc-serv.xxxxxxxxxxx.com/service/soap/CreateNewEmptyDocumentRequest] [name=test2@xxxxxxxxxxx.com;mid=6;ip=192.168.1.51;port=33906;ua=ZimbraWebClient - GC76 (Win)/8.8.15_GA_3847;soapId=12ebc8aa;] mailop - Adding Document test2.odt: id=257, folderId=16, folderName=Briefcase
2019-08-30 00:55:19,672 INFO  [qtp961409111-513:https://pc-serv.xxxxxxxxxxx.com/service/soap/CreateNewEmptyDocumentRequest] [name=test2@xxxxxxxxxxx.com;mid=6;ip=192.168.1.51;port=33906;ua=ZimbraWebClient - GC76 (Win)/8.8.15_GA_3847;soapId=12ebc8aa;] soap - CreateNewEmptyDocumentRequest elapsed=29
2019-08-30 00:55:19,692 WARN  [qtp961409111-203:https://pc-serv.xxxxxxxxxxx.com/service/extension/wopi-proxy/account/efdceb54-1c03-4678-99d0-e5ca7baef1f9/item_id/257] [] extensions - No available docs server for user test2@xxxxxxxxxxx.com, response to user: 503/retry
2019-08-30 00:55:19,704 WARN  [qtp961409111-13:https://pc-serv.xxxxxxxxxxx.com/service/extension/wopi-proxy/account/efdceb54-1c03-4678-99d0-e5ca7baef1f9/item_id/257/preview] [] extensions - No available docs server for user test2@xxxxxxxxxxx.com, response to user: 503/retry
2019-08-30 00:55:20,467 INFO  [nioEventLoopGroup-2-1] [] extensions - Trying to connect to http://zdocs.xxxxxxxxxxx.com:9980
2019-08-30 00:55:20,468 WARN  [nioEventLoopGroup-2-2] [] extensions - Unable to connect to ws://zdocs.xxxxxxxxxxx.com:9980/lool/adminws/?#, retrying in 30s: Connection refused: zdocs.xxxxxxxxxxx.com/192.168.1.52:9980
zdocs ldap-test is ok

zdocs status :

Code: Select all

systemctl status zimbra-docs-server
● zimbra-docs-server.service - Zimbra Docs Server
   Loaded: loaded (/lib/systemd/system/zimbra-docs-server.service; enabled; vendor preset: enabled)
   Active: active (running) since Thu 2019-08-29 22:58:15 UTC; 3min 1s ago
 Main PID: 4149 (loolwsd)
    Tasks: 4 (limit: 4632)
   CGroup: /system.slice/zimbra-docs-server.service
           └─4149 /opt/zimbra/docs/lool/bin/loolwsd --version --o:sys_template_path=/opt/zimbra/docs/generated/systemplate --o:child_root_path=/opt/zimbra/docs/generated/child-roots --o:file_server_root_path=/opt/zimbra/docs/lool/share/loolwsd
           
août 29 22:58:15 zdocs systemd[1]: Started Zimbra Docs Server.
août 29 22:58:16 zdocs loolwsd[4149]: /opt/zimbra/docs/lool/bin/loolforkit: error while loading shared libraries: libPocoCrypto.so.60: cannot open shared object file: No such file or directory
zxsuite docs getServices :

Code: Select all

services
            module
                could_start                                                 false
                could_stop                                                  true
                running                                                     true
            wopi
                could_start                                                 false
                could_stop                                                  true
                running                                                     true
            docs-iframe-redirector
                could_start                                                 false
                could_stop                                                  true
                running                                                     true
            soap
                could_start                                                 false
                could_stop                                                  true
                running                                                     true
            token-provider
                could_start                                                 false
                could_stop                                                  true
                running                                                     true
            cluster-status-provider
                could_start                                                 false
                could_stop                                                  true
                running                                                     true
zxsuite docs status :

Code: Select all

servers
                id                                                          75d19bb3-89ed-4279-9759-024b96a04ac4
                name                                                        zdocs.xxxxxxxxxx.com
                hostname                                                    zdocs.xxxxxxxxxx.com
                status                                                      offline
Can i have a little help? :)
thanks

PS: sorry for my english, i'm french :)
Top
User avatar
winproof
Posts: 22
Joined: Thu Aug 29, 2019 10:38 pm
ZCS/ZD Version: 9.0.0_GA_3976

Re: Zimbra docs "Connection refused"

Post by winproof »

ok, i've try a lots of things, no result.

first i've try 8.8.15 and zimbra docs on ubuntu 16.04, it's work.

on 18.04, i've try to play with dns, disable systemd-resolved, systemd-network and cloud-init to return to classic system (/etc/network/interface and resolv.conf), same problem.

try with normal dns config for 18.04 (via netplan and systemd-resolved), with a separated dns server, idem.

so, what to do now???

error message in mailbox (Connection refused) seems to mean that it's not a name resolution problem.

i've check firewall, all is open.

zimlet or ldap problem?
Top
User avatar
fs.schmidt
Outstanding Member
Outstanding Member
Posts: 278
Joined: Sat Sep 13, 2014 3:37 am
Location: Brazil
Contact:
Contact fs.schmidt

Re: Zimbra docs "Connection refused"

Post by fs.schmidt »

Hello,

Once you are using Network Edition, have you opened a ticket with zimbra support?
Top
User avatar
winproof
Posts: 22
Joined: Thu Aug 29, 2019 10:38 pm
ZCS/ZD Version: 9.0.0_GA_3976

Re: Zimbra docs "Connection refused"

Post by winproof »

hello
thanks for your answer, thanks to this i've discover that i can open a ticket with trial licence :D
so i open one now :mrgreen:
Top
User avatar
cyus
Posts: 4
Joined: Fri May 31, 2019 8:41 am

Re: Zimbra docs "Connection refused"

Post by cyus »

Hi!
I've the same problem.
I'm testing new ZCS 8.8.15 and ZCS 8.8.15 p1 versions at the lab prior to upgrading several of our customer installations.
The details: ZCS 8.8.15 p1 CentOS 7.6 single server. Zdocs server running Ubuntu 18.04 LTS, clean install, same error:

Code: Select all

root@u18zdocs:~# zdocs ldap-test
Trying to connect to LDAP...OK

Code: Select all

root@u18zdocs:~# systemctl status zimbra-docs-server.service
● zimbra-docs-server.service - Zimbra Docs Server
   Loaded: loaded (/lib/systemd/system/zimbra-docs-server.service; enabled; vendor preset: enabled)
   Active: active (running) since Wed 2019-09-04 06:38:51 UTC; 2min 33s ago
 Main PID: 11699 (loolwsd)
    Tasks: 4 (limit: 4915)
   CGroup: /system.slice/zimbra-docs-server.service
           └─11699 /opt/zimbra/docs/lool/bin/loolwsd --version --o:sys_template_path=/opt/zimbra/docs/generated/systemplate --o:child_root_path=/opt/zimbra/docs/generated/child-roots --o:file_server_root_path=/opt/zimbra/docs/lool/shar

sep 04 06:38:51 u18zdocs.xxx.xxx systemd[1]: Started Zimbra Docs Server.
sep 04 06:38:52 u18zdocs.xxx.xxx loolwsd[11699]: /opt/zimbra/docs/lool/bin/loolforkit: error while loading shared libraries: libPocoCrypto.so.60: cannot open shared object file: No such file or directory

Code: Select all

[zimbra@zcs1-8815 ~]$ zxsuite docs getServices
        services                                
            module                                  
                could_start                                                 false
                could_stop                                                  true
                running                                                     true
            wopi                                    
                could_start                                                 false
                could_stop                                                  true
                running                                                     true
            docs-iframe-redirector                  
                could_start                                                 false
                could_stop                                                  true
                running                                                     true
            soap                                    
                could_start                                                 false
                could_stop                                                  true
                running                                                     true
            token-provider                          
                could_start                                                 false
                could_stop                                                  true
                running                                                     true
            cluster-status-provider                 
                could_start                                                 false
                could_stop                                                  true
                running                                                     true

Code: Select all

[zimbra@zcs1-8815 ~]$ zxsuite docs status
        servers                                 
                id                                                          55b75231-75e6-41a1-b080-229631490572
                name                                                        u18zdocs
                hostname                                                    u18zdocs.xxx.xxx
                status                                                      offline
Regards.
Top
User avatar
winproof
Posts: 22
Joined: Thu Aug 29, 2019 10:38 pm
ZCS/ZD Version: 9.0.0_GA_3976

Re: Zimbra docs "Connection refused"

Post by winproof »

in mailbox.log, do you have the same error than me?

Code: Select all

2019-09-04 15:54:33,830 WARN  [nioEventLoopGroup-2-3] [] extensions - Unable to connect to ws://zdocs.xxxxxxxxxxxxxxx.com:9980/lool/adminws/?#, retrying in 30s: Connection refused:  zdocs.xxxxxxxxxxxxxxx.com/192.168.1.52:9980
Top
sheehanje
Posts: 20
Joined: Sat Sep 13, 2014 2:25 am

Re: Zimbra docs "Connection refused"

Post by sheehanje »

I am having the same issue. After installing Zimbra Docs server, we are unable to use high-fidelity preview and also lost functionality of editing and creating docs in briefcase (a core functionality of our production environment).

We've recently upgraded to 8.8.15 (and installed patch 1).

I've opened up a ticket - but I am getting the same type of errors in syslog on the Docs server, and mailbox.log on the mailbox servers. Hoping for a quick resolution, or at least instructions on how to revert back.
Top
User avatar
fs.schmidt
Outstanding Member
Outstanding Member
Posts: 278
Joined: Sat Sep 13, 2014 3:37 am
Location: Brazil
Contact:
Contact fs.schmidt

Re: Zimbra docs "Connection refused"

Post by fs.schmidt »

sheehanje wrote:I am having the same issue. After installing Zimbra Docs server, we are unable to use high-fidelity preview and also lost functionality of editing and creating docs in briefcase (a core functionality of our production environment).

We've recently upgraded to 8.8.15 (and installed patch 1).

I've opened up a ticket - but I am getting the same type of errors in syslog on the Docs server, and mailbox.log on the mailbox servers. Hoping for a quick resolution, or at least instructions on how to revert back.

Hello,

We have updated a couple environments to 8.8.15 P1 and we are NOT facing this issue, but we are running docs on Centos 7.6.

I would try to run

Code: Select all

/opt/zimbra/libexec/zmproxyconfgen
as zimbra user on the Zimbra Colalboration server and then restart the proxy server to see if it solves the issue.

Coul you confirm that docs is listening on port 9980?
Top
sheehanje
Posts: 20
Joined: Sat Sep 13, 2014 2:25 am

Re: Zimbra docs "Connection refused"

Post by sheehanje »

I ended up backing it out for now. We have a department that has critical need for Briefcase and they couldn't edit anything with docs enabled. I'm going to spin up a small test environment and see where it goes.

We are at patch 1. I'm wondering if the issue may be related to having a mix of Ubuntu 16.04 and now a couple Ubuntu 18.04 (docs and a new mailbox server) in the mix.

We moved most of our servers from Ubuntu 14.04 to 16.04 and Zimbra 8.6 to 8.8.15. I didn't expect it to go off without a hitch - for the most part the upgrade has been seamless to the users - but we've been fighting with some of the newer NG features.
Top
User avatar
winproof
Posts: 22
Joined: Thu Aug 29, 2019 10:38 pm
ZCS/ZD Version: 9.0.0_GA_3976

Re: Zimbra docs "Connection refused"

Post by winproof »

hi
/opt/zimbra/libexec/zmproxyconfgen
as zimbra user on the Zimbra Colalboration server and then restart the proxy server to see if it solves the issue.
already try (it's a part of the install process), not change
Coul you confirm that docs is listening on port 9980?
apparently no :D

Code: Select all

root@zdocs:~# netstat -paunt
Connexions Internet actives (serveurs et établies)
Proto Recv-Q Send-Q Adresse locale          Adresse distante        Etat       PID/Program name
tcp        0      0 127.0.0.53:53           0.0.0.0:*               LISTEN      655/systemd-resolve
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      922/sshd
tcp        0      0 127.0.0.1:9981          0.0.0.0:*               LISTEN      1470/loolwsd
tcp        0     64 192.168.1.52:22         192.168.1.50:8551       ESTABLISHED 1315/sshd: test [pr
udp        0      0 127.0.0.53:53           0.0.0.0:*                           655/systemd-resolve
Top
Post Reply

Return to “Administrators”