Couldn’t make it work on a test server on VirtualBox using a self-signed certificate and Nextcloud 12.0.5.
Document server on port 8082 showed as working but nextcloud reported:
Error PHP file_get_contents(https://server.example.com:8082/coauthoring/CommandService.ashx): failed to open stream: operation failed at /usr/share/nextcloud/apps/onlyoffice/lib/documentservice.php#351
After some fiddling and a reboot nextcloud finally saved the https://fqdn:8082/
after several retries, but editing a document brings a blank page below the nextcloud top navigation bar. I bet I’m doing something wrong (to be continued in the morning).
Some excerpts from logs follow (including some warnings/errors from dependent packages that maybe could be obviated)
yum install (SELinux warnings/errors excluded):
ValueError: Port @tcp/3000 is not defined
ValueError: Port tcp/8000 already defined
ValueError: Port tcp/8080 already defined
warning: %post(onlyoffice-documentserver-5.0.7-38.x86_64) scriptlet failed, exit status 1
Non-fatal POSTIN scriptlet failure in rpm package onlyoffice-documentserver-5.0.7-38.x86_64
/var/log/messages:
Mar 17 00:36:33 server esmith::event[4210]: Action: /etc/e-smith/events/actions/generic_template_expand SUCCESS [0.193144]
Mar 17 00:36:33 server esmith::event[4210]: could not change directory to "/root"
Mar 17 00:36:34 server esmith::event[4210]: CREATE DATABASE
Mar 17 00:36:34 server esmith::event[4210]: could not change directory to "/root"
Mar 17 00:36:34 server esmith::event[4210]: CREATE ROLE
Mar 17 00:36:34 server esmith::event[4210]: could not change directory to "/root"
Mar 17 00:36:34 server esmith::event[4210]: GRANT
Mar 17 00:36:34 server esmith::event[4210]: Created symlink from /etc/systemd/system/multi-user.target.wants/supervisord.service to /usr/lib/systemd/system/supervisord.service.
Mar 17 00:36:34 server systemd: Reloading.
Mar 17 00:36:34 server esmith::event[4210]: Created symlink from /etc/systemd/system/multi-user.target.wants/rabbitmq-server.service to /usr/lib/systemd/system/rabbitmq-server.service.
Mar 17 00:36:34 server systemd: Reloading.
Mar 17 00:36:34 server systemd: Starting RabbitMQ broker...
Mar 17 00:36:34 server systemd: Cannot find unit for notify message of PID 4276.
Mar 17 00:36:34 server systemd: Cannot find unit for notify message of PID 4277.
Mar 17 00:36:34 server systemd: rabbitmq-server.service: Got notification message from PID 4279, but reception only permitted for main PID 4263
Mar 17 00:36:35 server systemd: Cannot find unit for notify message of PID 4300.
Mar 17 00:36:35 server systemd: rabbitmq-server.service: Got notification message from PID 4301, but reception only permitted for main PID 4263
Mar 17 00:36:35 server systemd: Cannot find unit for notify message of PID 4302.
Mar 17 00:36:41 server esmith::event[4210]: Trying to establish RabbitMQ connection... OK
Mar 17 00:36:43 server esmith::event[4210]: ValueError: Port tcp/9999 already defined
/var/log/onlyoffice/documentserver/gc/err.log:
events.js:160
throw er; // Unhandled 'error' event
^
error: terminating connection due to administrator command
at Connection.parseE (/var/www/onlyoffice/documentserver/server/DocService/node_modules/pg/lib/connection.js:567:11)
at Connection.parseMessage (/var/www/onlyoffice/documentserver/server/DocService/node_modules/pg/lib/connection.js:391:17)
at Socket.<anonymous> (/var/www/onlyoffice/documentserver/server/DocService/node_modules/pg/lib/connection.js:129:22)
at emitOne (events.js:96:13)
at Socket.emit (events.js:188:7)
at readableAddChunk (_stream_readable.js:176:18)
at Socket.Readable.push (_stream_readable.js:134:10)
at TCP.onread (net.js:547:20)
/var/log/redis/redis.log:
5176:M 17 Mar 00:36:52.997 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
5176:M 17 Mar 00:36:52.997 # Server started, Redis version 3.2.10
5176:M 17 Mar 00:36:52.997 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
5176:M 17 Mar 00:36:52.997 # WARNING you have Transparent Huge Pages (THP) support enabled in your kernel. This will create latency and memory usage issues with Redis. To fix this issue run the command 'echo never > /sys/kernel/mm/transparent_hugepage/enabled' as root, and add it to your /etc/rc.local in order to retain the setting after a reboot. Redis must be restarted after THP is disabled.
5176:M 17 Mar 00:36:52.997 * DB loaded from disk: 0.000 seconds
5176:M 17 Mar 00:36:52.997 * The server is now ready to accept connections on port 6379
var/log/supervisor/supervisord.log:
2018-03-17 00:36:44,436 CRIT Supervisor running as root (no user in config file)