Errors after upgrade onlyoffice-controlpanel

Update/Migration/Backup issues
Post Reply
raketkos
Posts: 1
Joined: Mon Oct 19, 2020 5:39 pm

Errors after upgrade onlyoffice-controlpanel

Post by raketkos » Mon Oct 19, 2020 5:52 pm

Hey. On Ubuntu 16.04 I updated onlyoffice-control panel with the command "apt upgrade onlyoffice-controlpanel", now the logs are full of errors:
/var/www/onlyoffice/.pm2/pm2.log:
...
2020-10-19T16:44:42: PM2 log: App [sso-auth:1] starting in -fork mode-
2020-10-19T16:44:42: PM2 log: App [sso-auth:1] online
2020-10-19T16:44:47: PM2 log: App [sso-auth:1] exited with code [0] via signal [SIGINT]
2020-10-19T16:44:47: PM2 log: App [sso-auth:1] starting in -fork mode-
2020-10-19T16:44:47: PM2 log: App [sso-auth:1] online
2020-10-19T16:44:50: PM2 log: App [control-panel:0] exited with code [1] via signal [SIGINT]
2020-10-19T16:44:50: PM2 log: App [control-panel:0] starting in -fork mode-
2020-10-19T16:44:50: PM2 log: App [control-panel:0] online
2020-10-19T16:44:53: PM2 log: App [sso-auth:1] exited with code [0] via signal [SIGINT]
2020-10-19T16:44:53: PM2 log: App [sso-auth:1] starting in -fork mode-
2020-10-19T16:44:53: PM2 log: App [sso-auth:1] online
2020-10-19T16:44:58: PM2 log: App [sso-auth:1] exited with code [0] via signal [SIGINT]
2020-10-19T16:44:58: PM2 log: App [sso-auth:1] starting in -fork mode-
2020-10-19T16:44:58: PM2 log: App [sso-auth:1] online
2020-10-19T16:44:59: PM2 log: App [control-panel:0] exited with code [1] via signal [SIGINT]
2020-10-19T16:44:59: PM2 log: App [control-panel:0] starting in -fork mode-
2020-10-19T16:44:59: PM2 log: App [control-panel:0] online
...
/var/www/onlyoffice/.pm2/logs/control-panel-error-0.log:
...
Warning: connect.session() MemoryStore is not
designed for a production environment, as it will leak
memory, and will not scale past a single process.
Error: listen EADDRINUSE: address already in use :::8082
at Server.setupListenHandle [as _listen2] (net.js:1317:16)
at listenInCluster (net.js:1365:12)
at Server.listen (net.js:1451:7)
at Function.listen (/var/www/onlyoffice/controlpanel/www/node_modules/express/lib/application.js:618:24)
at Object.<anonymous> (/var/www/onlyoffice/controlpanel/www/server.js:24:20)
at Module._compile (internal/modules/cjs/loader.js:1015:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1035:10)
at Module.load (internal/modules/cjs/loader.js:879:32)
at Function.Module._load (internal/modules/cjs/loader.js:724:14)
at Object.<anonymous> (/usr/lib/node_modules/pm2/lib/ProcessContainerFork.js:27:21) {
code: 'EADDRINUSE',
errno: 'EADDRINUSE',
syscall: 'listen',
address: '::',
port: 8082
}
...
/var/www/onlyoffice/.pm2/logs/sso-auth-error-1.log:
...
Warning: connect.session() MemoryStore is not
designed for a production environment, as it will leak
memory, and will not scale past a single process.
Error: listen EADDRINUSE: address already in use :::9834
at Server.setupListenHandle [as _listen2] (net.js:1317:16)
at listenInCluster (net.js:1365:12)
at Server.listen (net.js:1451:7)
at Object.<anonymous> (/var/www/onlyoffice/controlpanel/services/sso.auth/app.js:89:12)
at Module._compile (internal/modules/cjs/loader.js:1015:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1035:10)
at Module.load (internal/modules/cjs/loader.js:879:32)
at Function.Module._load (internal/modules/cjs/loader.js:724:14)
at Object.<anonymous> (/usr/lib/node_modules/pm2/lib/ProcessContainerFork.js:27:21)
at Module._compile (internal/modules/cjs/loader.js:1015:30) {
code: 'EADDRINUSE',
errno: 'EADDRINUSE',
syscall: 'listen',
address: '::',
port: 9834
}
...
netstat -lpn | grep '9834\|8082'
tcp6 0 0 :::9834 :::* LISTEN 1044/node
tcp6 0 0 :::8082 :::* LISTEN 1046/node

ps -auxww | grep '1044\|1046'
onlyoff+ 1044 0.7 0.3 651460 59984 ? Ssl 16:51 0:03 /usr/bin/node /var/www/onlyoffice/controlpanel/services/sso.auth/app.js
onlyoff+ 1046 2.1 0.4 1729064 81196 ? Ssl 16:51 0:09 /usr/bin/node /var/www/onlyoffice/controlpanel/www/server.js

Carl
Posts: 472
Joined: Thu Apr 12, 2018 10:00 am

Re: Errors after upgrade onlyoffice-controlpanel

Post by Carl » Fri Nov 13, 2020 7:51 am

Hello,

Sorry for the delayed reply.

Is the issue still relevant? Please note that we strongly recommend to update ONLYOFFICE Workspace only with the installation script with an additional parameter -u true:
bash workspace-install.sh -u true

Post Reply