Container not reachable, looking like not fully started

Questions/problems on Docker
Post Reply
tjareson
Posts: 2
Joined: Wed May 20, 2020 1:33 pm

Container not reachable, looking like not fully started

Post by tjareson » Wed May 20, 2020 2:01 pm

Hello,

I have a problem where I have spent like a full day on to understand, but didn't find a solution yet.
I've installed and started an onlyoffice documentserver container with:

Code: Select all

docker run -i -t -d --restart=always --name onlyoffice -p 8099:80 -e "JWT_ENABLED=true" -e "JWT_SECRET=xxxxxxxxxxxxxxxxxxxxxxxxx" onlyoffice/documentserver
The container starts and is shown without problem also in portainer. Just that it is not reachable on port 8099.
If I do netstat -l on the host, the port 8099 shows up to be listened on.
It starts to get weird when I try to do the simplest test: telnet 127.0.0.1 8099
it connects but I get an immediate Connection closed by foreign host.

(I have another installation where it is installed exactly the same way, if I connect for a test via telnet the connection remains until typing something.)

If I look into the container I only find 18 processes running. (In the other installation it is usually over 30 services in an more or less unused running onlyoffice container...)

Checking the logs of the container shows a problem with mqrabbit:

Code: Select all

* Starting PostgreSQL 10 database server                                [ OK ] 
 * Starting RabbitMQ Messaging Server rabbitmq-server                            * FAILED - check /var/log/rabbitmq/startup_\{log, _err\}
                                                                         [fail]
Starting redis-server: redis-server.
Waiting for connection to the localhost host on port 5672
Waiting for connection to the localhost host on port 5672
[repeating endless...]
The rabbit startup log says:

Code: Select all

/usr/sbin/rabbitmq-server: 33: /usr/sbin/rabbitmq-server: Cannot fork
That all happens inside the container. Anyone any clue what the issue is here?
The same container version runs on a different server without any problem. Is there any prerequisites the container installation is missing, which is not mentioned in the docs?

Environment:
Onlyoffice documentserver docker version is latest pulled today.
Host Ubuntu 18.04.4 LTS server with docker community, Version:19.03.9, API version: 1.40, Go version: go1.13.10
Beside docker, nginx, mariadb and ufw there is nothing else installed on the host. I'm able to install docker container like portainer or nextcloud which are running without any problems.
Setup is with nginx as reverse proxy, ssl implemented by letsencrypt.

Tjareson.

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

Re: Container not reachable, looking like not fully started

Post by Carl » Wed May 20, 2020 4:09 pm

Hello Tjareson,

Have you tried reinstalling the container? Please make sure that the latest version 5.5.1 is installed.

Let me know the results.

tjareson
Posts: 2
Joined: Wed May 20, 2020 1:33 pm

Re: Container not reachable, looking like not fully started

Post by tjareson » Wed May 20, 2020 5:27 pm

Yes, I've reinstalled a couple of times today incl. deleting the image and pull it again.
I've investigated a bit further.
"Cannot fork" can also have a link with maximum of task.

What I've tried further:

Code: Select all

systemctl set-property docker.service TasksMax=infinity
cat /lib/systemd/system/docker.service shows accordingly:

Code: Select all

# Comment TasksMax if your systemd version does not support it.
# Only systemd 226 and above support this option.
TasksMax=infinity
Unfortunately that didn't change the problem (after restart docker, restart server).

systemctl status docker out is:

Code: Select all

● docker.service - Docker Application Container Engine
   Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
  Drop-In: /etc/systemd/system.control/docker.service.d
           └─50-TasksMax.conf
   Active: active (running) since Wed 2020-05-20 17:48:23 CEST; 1h 35min ago
     Docs: https://docs.docker.com
 Main PID: 420 (dockerd)
    Tasks: 49
I wonder what the part 50-TasksMax.conf is relating to?
Especially because of that tasks is already 49.

And why is it only an issue of the onlyoffice container and not for nextcloud for instance, which has a lot of running services as well...

Tjareson

Post Reply