ONLYOFFICE
Ubuntu 18 // Docker onlyoffice // 502 bad gateway // no onlyoffice.sock
Hello everyone, I have weird problem, have two identical servers on Ubuntu 18 running docker installed Onlyoffice, there are 3 containers:
- community server container
- document server container
- mysql server container In one of theses servers, suddenly, that means after night or after few days, or week im getting 502 nginx error, bad gateway. docker exec -it 709f57dd8e95 bash logged with this command to container, i found that something maybe stopped working, because there is no onlyoffice.sock in /var/run/onlyoffice directory... maybe someone have clue ? If i restart containers each, nothing change, if i restart all virtual machine, after 15-20min starting everything to work... inside community container, monoserve, nginx or mysql service restart doesnt helped...
Hi @prosportas. This is a mono failure that stops the monoserve service. But it should start automatically. If it doesn't start - check if you have enough system requirements, errors in web.log and web.api.log files, and monoserve status after restart?
Hi @prosportas. This is a mono failure that stops the monoserve service. But it should start automatically. If it doesn't start - check if you have enough system requirements, errors in web.log and web.api.log files, and monoserve status after restart?
VM has 8GB ram, 8 Cores and 80GB disk on ssd. Interesting, but inside community container if i restart monoserve service, doesnt solve problem, still no onlyoffice.sock..
with docker logs -f container_ID im getting this log:
- service monoserve restart Starting monoserve... OK
- service monoserveApiSystem restart Starting monoserveApiSystem... OK
- '[' false == true ']'
- service onlyofficeRadicale restart Starting onlyofficeRadicale... OK
- service onlyofficeSocketIO restart Starting onlyofficeSocketIO... OK
- service onlyofficeThumb restart Starting onlyofficeThumb... OK
- service onlyofficeFeed restart Starting onlyofficeFeed... OK
- service onlyofficeIndex restart Starting onlyofficeIndex... OK
- service onlyofficeJabber restart Starting onlyofficeJabber... OK
- service onlyofficeMailAggregator restart Starting onlyofficeMailAggregator... OK
- service onlyofficeMailWatchdog restart Starting onlyofficeMailWatchdog... OK
- service onlyofficeMailCleaner restart Starting onlyofficeMailCleaner... OK
- service onlyofficeNotify restart Starting onlyofficeNotify... OK
- service onlyofficeBackup restart Starting onlyofficeBackup... OK
- service onlyofficeStorageMigrate restart Starting onlyofficeStorageMigrate... OK
- service onlyofficeUrlShortener restart Starting onlyofficeUrlShortener... OK
- service elasticsearch restart
- Stopping Elasticsearch Server [ OK ]
- Starting Elasticsearch Server sysctl: setting key "vm.max_map_count": Read-only file system [fail]
- service god restart Restarting god... The server is not available (or you do not have permissions to access it) OK
- '[' SERVER == SERVER ']'
- mv /app/onlyoffice/config/nginx/prepare-onlyoffice /etc/nginx/sites-enabled/onlyoffice
- service nginx reload
- Reloading nginx nginx [ OK ]
but now working everything... on other identical server in this section showing [OK] ( not [fail] ):
- Starting Elasticsearch Server sysctl: setting key "vm.max_map_count": Read-only file system [fail]
How did you installed this containers? Did you mounted a folder on host machine? We recommend use our installation scripts.
How did you installed this containers? Did you mounted a folder on host machine? We recommend use our installation scripts.
Installation was made by onlyoffice helpcenter instructions "Installing ONLYOFFICE Docs Community Edition for Docker on a local server" with alternative installation - https://download.onlyoffice.com/install/workspace-install.sh I want to mantion that this server was installed maybe year ago, maybe more and works fine, this situation annoying about two months.. and no solution..
Can the load on this server be higher? Sorry, but mono drops happen, we can't do anything about it, we try to minimize it. Or we can recommend you to use the Windows version. You can also try to increase the RAM.
When throwing Nginx 502 errror and no onlyoffice.sock, there is only onlyofficeApiSystem.sock, inside container --status-all and god status showing ( in server only 10 active users...) very anoying problem: [ ? ] binfmt-support [ + ] cron [ - ] dbus [ - ] elasticsearch [ + ] god [ ? ] hwclock.sh [ + ] monoserve [ + ] monoserveApiSystem [ + ] mysql [ + ] nginx [ + ] nginx-debug [ + ] onlyofficeBackup [ + ] onlyofficeFeed [ + ] onlyofficeIndex [ + ] onlyofficeJabber [ + ] onlyofficeMailAggregator [ + ] onlyofficeMailCleaner [ + ] onlyofficeMailWatchdog [ + ] onlyofficeNotify [ + ] onlyofficeRadicale [ + ] onlyofficeSocketIO [ + ] onlyofficeStorageMigrate [ + ] onlyofficeThumb [ + ] onlyofficeUrlShortener [ - ] procps [ + ] redis-server [ + ] rsyslog [ - ] unattended-upgrades [ - ] x11-common
onlyoffice: elasticsearch: up monoserve: up monoserveApiSystem: up nginx: up onlyofficeBackup: up onlyofficeFeed: up onlyofficeIndex: up onlyofficeJabber: up onlyofficeMailAggregator: up onlyofficeMailCleaner: up onlyofficeMailWatchdog: up onlyofficeNotify: up onlyofficeRadicale: up onlyofficeSocketIO: up onlyofficeStorageMigrate: up onlyofficeThumb: up onlyofficeUrlShortener: up redis: up
after restart god, monoserve no changes...
I also face the same problem. In the Docker container, I can see the following error in the /var/log/nginx/error.log file.
connect() to unix:/var/run/onlyoffice/onlyoffice.socket failed
My container doesn't have the monoserve service.
root@a6442efdf9d3:~# service monoserve status
monoserve: unrecognized service
I'm using the latest community-server Docker image.
Hello @linuxbabe this error means that the mono has crashed.
connect() to unix:/var/run/onlyoffice/onlyoffice.socket failed
In version 11.0 we changed all service to systemctl, and now you need look at systemctl status monoserve.
Thanks for your reply @Carazyda However, I'm using the Docker version, not the deb/rpm package. Is the Docker version not maintained anymore?
https://hub.docker.com/r/onlyoffice/communityserver/
We have an old Ubuntu server running the Docker version installed 4 years ago. I'd like to use the deb package, but I don't want to lose the data. Can I switch from the Docker version to deb package installation without losing data?