ONLYOFFICE Docs v6.4 with conditional formatting, new scaling options, and WOPI protocol support
ONLYOFFICE Docs v6.4 released

Random 502 errors and socket errors on Centos8

2021/09/16 16:48:34 [crit] 1282#1282: *2 connect() to unix:/var/run/onlyoffice/onlyoffice.socket failed (2: No such file or directory) while connecting to upstream, client: 10.1.1.254, server: , request: “GET /TenantLogo.ashx?logotype=3 HTTP/2.0”, upstream: “fastcgi://unix:/var/run/onlyoffice/onlyoffice.socket:”, host: “forscotland.com:7443”, referrer: “https://forscotland.com:7443/Management.aspx?type=1

in /var/log/onlyoffice/nginx.error.log

Im seeing a LOT of these on a fresh install on Centos8 having used bash install-RedHat.sh -it GROUPS

The browser often says 502 App crash but if I refresh once or twice it then works.

socket info
ls -lat /var/run/onlyoffice/
total 0
drwxr-xr-x 2 onlyoffice nginx 80 Sep 16 17:10 .
srw-rw-rw- 1 onlyoffice onlyoffice 0 Sep 16 17:10 onlyofficeApiSystem.socket
srw-rw-rw- 1 onlyoffice onlyoffice 0 Sep 16 17:10 onlyoffice.socket
drwxr-xr-x 42 root root 1240 Sep 16 16:44 .

Thanks

Ivan

Hello ivan.

Please provide us with additional information about your installation.

  1. Point us to the guide which you used for installation. Am I right that you used this one via installation script? Installing ONLYOFFICE Groups for Red Hat, CentOS, and derivatives - ONLYOFFICE
  2. Please provide us with whole Community server logs folder. It’s located here: /var/log/onlyoffice/

Hi Alexandre. yes, used that installer. I reproduced the issue, doing a straight install again, and the logs are here https://forscotland.com/LOGS.tar.gz . I altered the listener from 80 to 8090 by editing /etc/nginx/conf.d/onlyoffice* and rebooting . Happy to do what I can to help resolve this with you. Thanks. Ivan PS did notice MYSQL errors too. This may be tied into the native password changes in mysql 8. the mysql password IS stored in /var/www/onlyoffice/Services/ASC.UrlShortener/config/config.json
and I CAN connect t onlyoffice and show tables.

Hello Ivan. Please go to the host and run mono -V . Please show us the result.

Morning Alexandre.

[root@onlyoffice ~]# mono -V
Mono JIT compiler version 6.8.0.123 (tarball Mon May 11 19:47:40 UTC 2020)
Copyright (C) 2002-2014 Novell, Inc, Xamarin Inc and Contributors. www.mono-project.com
TLS: __thread
SIGSEGV: altstack
Notifications: epoll
Architecture: amd64
Disabled: none
Misc: softdebug
Interpreter: yes
LLVM: yes(610)
Suspend: hybrid
GC: sgen (concurrent by default)

Just FYI

[root@onlyoffice ~]# rpm -qa|grep -i mono
libmonoboehm-2_0-1-6.8.0.123-0.xamarin.2.epel8.x86_64
mono-winforms-6.8.0.123-0.xamarin.2.epel8.x86_64
mono-winfxcore-6.8.0.123-0.xamarin.2.epel8.x86_64
libmonosgen-2_0-devel-6.8.0.123-0.xamarin.2.epel8.x86_64
mono-webserver-hyperfastcgi-0.4-7.noarch
gnu-free-mono-fonts-20120503-18.el8.0.1.noarch
libmono-2_0-1-6.8.0.123-0.xamarin.2.epel8.x86_64
mono-data-6.8.0.123-0.xamarin.2.epel8.x86_64
mono-locale-extras-6.8.0.123-0.xamarin.2.epel8.x86_64
mono-data-sqlite-6.8.0.123-0.xamarin.2.epel8.x86_64
liberation-mono-fonts-2.00.3-7.el8.noarch
libmono-llvm0-6.8.0.123-0.xamarin.2.epel8.x86_64
mono-mvc-6.8.0.123-0.xamarin.2.epel8.x86_64
monodoc-core-6.8.0.123-0.xamarin.2.epel8.x86_64
dejavu-sans-mono-fonts-2.35-7.el8.noarch
urw-base35-nimbus-mono-ps-fonts-20170801-10.el8.noarch
mono-llvm-tools-6.0+mono20190708165219-0.xamarin.1.epel8.x86_64
mono-extras-6.8.0.123-0.xamarin.2.epel8.x86_64
mono-core-6.8.0.123-0.xamarin.2.epel8.x86_64
mono-reactive-6.8.0.123-0.xamarin.2.epel8.x86_64
mono-web-6.8.0.123-0.xamarin.2.epel8.x86_64
libmono-2_0-devel-6.8.0.123-0.xamarin.2.epel8.x86_64
mono-complete-6.8.0.123-0.xamarin.2.epel8.x86_64
mono-devel-6.8.0.123-0.xamarin.2.epel8.x86_64
libmonosgen-2_0-1-6.8.0.123-0.xamarin.2.epel8.x86_64
mono-data-oracle-6.8.0.123-0.xamarin.2.epel8.x86_64
libmonoboehm-2_0-devel-6.8.0.123-0.xamarin.2.epel8.x86_64
mono-wcf-6.8.0.123-0.xamarin.2.epel8.x86_64

According to the provided logs, the situation with the temporary unavailability of the portal (502 error) is related to the fall of the Mono service.

We know about this situation and we are working on it. The portal itself is recovering after fall of Mono service. As a workaround solution, you can use Windows installation since Windows installation doesn’t use Mono service.

Sorry for inconvenience.

Thanks for the update Alexandre, I’ll use my old docker based install util then.

LOVE the product.

Ivan

1 Like

Is there any estimate when a mono fix will be shared? Happy to help you test it on Centos8 baremetal

Unfortunately, I cannot provide you with approximate frames of fixing the situation at the moment. We are still working on it.