[GH-ISSUE #171 ] Waiting for connection to the localhost host on port 5432 #97

Author

Owner

@ShockwaveNN commented on GitHub (Jul 11, 2019):

Hi, could you show exact command to run it via docker

@ShockwaveNN commented on GitHub (Jul 11, 2019): Hi, could you show exact command to run it via docker

kerem commented

Author

Owner

@pwepwe973 commented on GitHub (Jul 11, 2019):

Hello thank you for your answer
la commande sur le site de /hub.docker.com/r/onlyoffice/documentserver

sudo docker run -i -t -d -p 80:80 \
    -v /app/onlyoffice/DocumentServer/logs:/var/log/onlyoffice  \
    -v /app/onlyoffice/DocumentServer/data:/var/www/onlyoffice/Data  onlyoffice/documentserver

@pwepwe973 commented on GitHub (Jul 11, 2019): Hello thank you for your answer la commande sur le site de /hub.docker.com/r/onlyoffice/documentserver ``` sudo docker run -i -t -d -p 80:80 \ -v /app/onlyoffice/DocumentServer/logs:/var/log/onlyoffice \ -v /app/onlyoffice/DocumentServer/data:/var/www/onlyoffice/Data onlyoffice/documentserver ```

kerem commented

Author

Owner

@ShockwaveNN commented on GitHub (Jul 11, 2019):

@pwepwe973 I checked you command and everything seems fine for me. Please check content of mounted folders and try to run it without them, maybe some persmissions errors

@ShockwaveNN commented on GitHub (Jul 11, 2019): @pwepwe973 I checked you command and everything seems fine for me. Please check content of mounted folders and try to run it without them, maybe some persmissions errors

kerem commented

Author

Owner

@pwepwe973 commented on GitHub (Jul 11, 2019):

ok i try it

@pwepwe973 commented on GitHub (Jul 11, 2019): ok i try it

kerem commented

Author

Owner

@pwepwe973 commented on GitHub (Jul 11, 2019):

in folders onlyffice to create folders but there are no files in it

@pwepwe973 commented on GitHub (Jul 11, 2019): in folders onlyffice to create folders but there are no files in it

kerem commented

Author

Owner

@ShockwaveNN commented on GitHub (Jul 12, 2019):

@pwepwe973 I think there is some permission problems on your host with those mounts

@ShockwaveNN commented on GitHub (Jul 12, 2019): @pwepwe973 I think there is some permission problems on your host with those mounts

kerem commented

Author

Owner

@pwepwe973 commented on GitHub (Jul 18, 2019):

hello
how to correct this problem? because normally the docker should be able to write in this folder

@pwepwe973 commented on GitHub (Jul 18, 2019): hello how to correct this problem? because normally the docker should be able to write in this folder

kerem commented

Author

Owner

@ShockwaveNN commented on GitHub (Jul 18, 2019):

Did you try

Please check content of mounted folders and try to run it without them, maybe some persmissions errors

I was not able to reproduce your error, sorry

@ShockwaveNN commented on GitHub (Jul 18, 2019): Did you try > Please check content of mounted folders and try to run it without them, maybe some persmissions errors I was not able to reproduce your error, sorry

kerem commented

Author

Owner

@ShockwaveNN commented on GitHub (Sep 25, 2019):

This issue was closed due to no response.

@ShockwaveNN commented on GitHub (Sep 25, 2019): This issue was closed due to no response.

kerem commented

Author

Owner

@ykzk commented on GitHub (Oct 21, 2019):

I had the same issue upgrading from an old version. The problem was that I was mounting /etc/onlyoffice and it was empty; thus, read_setting() could not read the configuration from the /etc/onlyoffice/documentserver/local.json file, making the start-up script run-document-server.sh fail to run the services.
Hope this helps.

@ykzk commented on GitHub (Oct 21, 2019): I had the same issue upgrading from an old version. The problem was that I was mounting `/etc/onlyoffice` and it was empty; thus, `read_setting()` could not read the configuration from the `/etc/onlyoffice/documentserver/local.json` file, making the start-up script `run-document-server.sh` fail to run the services. Hope this helps.

kerem commented

Author

Owner

@muzhix commented on GitHub (May 28, 2021):

I had the same issue after changed the access policy of my centos server.
The nc command was blocked in my server, so the /app/ds/run-document-server.sh was stucked at line 167, waiting_for_connection(). Just skip the connection check.

167 waiting_for_connection(){
168   echo "skip connection to the $1 host on port $2"
169   #until nc -z -w 3 "$1" "$2"; do
170   #  >&2 echo "Waiting for connection to the $1 host on port $2"
171   #  sleep 1
172   #done
173 }

Hope this helps.

@muzhix commented on GitHub (May 28, 2021): I had the same issue after changed the access policy of my centos server. The `nc` command was blocked in my server, so the `/app/ds/run-document-server.sh` was stucked at line 167, `waiting_for_connection()`. Just skip the connection check. ``` 167 waiting_for_connection(){ 168 echo "skip connection to the $1 host on port $2" 169 #until nc -z -w 3 "$1" "$2"; do 170 # >&2 echo "Waiting for connection to the $1 host on port $2" 171 # sleep 1 172 #done 173 } ``` Hope this helps.

kerem commented

Author

Owner

@PeterMalkin commented on GitHub (Dec 26, 2021):

Same issue here. Just trying to run the latest image exhibits the same behavior

docker run -it -p 80:80 -v pwd:/var/www/onlyoffice -v pwd/data:/var/www/onlyoffice/Data -v pwd/documentserver:/var/www/onlyoffice/documentserver onlyoffice/documentserver

@PeterMalkin commented on GitHub (Dec 26, 2021): Same issue here. Just trying to run the latest image exhibits the same behavior docker run -it -p 80:80 -v `pwd`:/var/www/onlyoffice -v `pwd`/data:/var/www/onlyoffice/Data -v `pwd`/documentserver:/var/www/onlyoffice/documentserver onlyoffice/documentserver

kerem commented

Author

Owner

@ShockwaveNN commented on GitHub (Dec 27, 2021):

@PeterMalkin original issue is quite old and not figured out

Please try to run image without any volume mounts and see if it run correctly and create a new issue if got troubles with more description of your problem

@ShockwaveNN commented on GitHub (Dec 27, 2021): @PeterMalkin original issue is quite old and not figured out Please try to run image without any volume mounts and see if it run correctly and create a new issue if got troubles with more description of your problem

kerem commented

Author

Owner

@dreua commented on GitHub (Dec 27, 2021):

Just in case you are using selinux: Use bind mounts | Docker Documentation #configure-the-selinux-label

@dreua commented on GitHub (Dec 27, 2021): Just in case you are using selinux: [Use bind mounts | Docker Documentation #configure-the-selinux-label](https://docs.docker.com/storage/bind-mounts/#configure-the-selinux-label)

kerem commented

Author

Owner

@PeterMalkin commented on GitHub (Dec 27, 2021):

The latest container runs fine without any volumes mounted. I still cannot connect to the port correctly, but I believe it is a different issue and should not be conflated with this.

Just for the record, mounting the following volumes from docker-compose file works fine to start the container up:

  onlyoffice:
    image: onlyoffice/documentserver
    restart: unless-stopped
    volumes:
      - "/onlyoffice/logs:/var/log/onlyoffice"
      - "/onlyoffice/data:/var/www/onlyoffice/Data"
      - "/onlyoffice/lib:/var/lib/onlyoffice/"
      - "/onlyoffice/rabbitmq:/var/lib/rabbitmq"
      - "/onlyoffice/redis:/var/lib/redis"
      - "/onlyoffice/postgresql:/var/lib/postgresql"
    ports:
      - "8888:80"

@PeterMalkin commented on GitHub (Dec 27, 2021): The latest container runs fine without any volumes mounted. I still cannot connect to the port correctly, but I believe it is a different issue and should not be conflated with this. Just for the record, mounting the following volumes from docker-compose file works fine to start the container up: ```yaml onlyoffice: image: onlyoffice/documentserver restart: unless-stopped volumes: - "/onlyoffice/logs:/var/log/onlyoffice" - "/onlyoffice/data:/var/www/onlyoffice/Data" - "/onlyoffice/lib:/var/lib/onlyoffice/" - "/onlyoffice/rabbitmq:/var/lib/rabbitmq" - "/onlyoffice/redis:/var/lib/redis" - "/onlyoffice/postgresql:/var/lib/postgresql" ports: - "8888:80" ```

kerem commented

Author

Owner

@ShockwaveNN commented on GitHub (Dec 28, 2021):

I think it's permission issue with some mounts, probably /var/lib/postgresql - maybe host system got some incorrect permissions on some folder
Disable mounts one by one until you got working DocumentServer and find problem mount and after that take a look at permission of this folder or tempraly make it 777 to be sure (not to forget revert back after)

@ShockwaveNN commented on GitHub (Dec 28, 2021): I think it's permission issue with some mounts, probably `/var/lib/postgresql` - maybe host system got some incorrect permissions on some folder Disable mounts one by one until you got working DocumentServer and find problem mount and after that take a look at permission of this folder or tempraly make it 777 to be sure (not to forget revert back after)

kerem commented

Author

Owner

@sandav-pablo commented on GitHub (Jan 10, 2022):

I had the same issue after changed the access policy of my centos server. The nc command was blocked in my server, so the /app/ds/run-document-server.sh was stucked at line 167, waiting_for_connection(). Just skip the connection check.
167 waiting_for_connection(){
168   echo "skip connection to the $1 host on port $2"
169   #until nc -z -w 3 "$1" "$2"; do
170   #  >&2 echo "Waiting for connection to the $1 host on port $2"
171   #  sleep 1
172   #done
173 }
Hope this helps.

Thanks, this solved the problem in my case. Don't really know what caused nc to stop working or if it was all image update related, but editing the script and mounting read only did the trick!

@sandav-pablo commented on GitHub (Jan 10, 2022): > I had the same issue after changed the access policy of my centos server. The `nc` command was blocked in my server, so the `/app/ds/run-document-server.sh` was stucked at line 167, `waiting_for_connection()`. Just skip the connection check. > > ``` > 167 waiting_for_connection(){ > 168 echo "skip connection to the $1 host on port $2" > 169 #until nc -z -w 3 "$1" "$2"; do > 170 # >&2 echo "Waiting for connection to the $1 host on port $2" > 171 # sleep 1 > 172 #done > 173 } > ``` > > Hope this helps. Thanks, this solved the problem in my case. Don't really know what caused nc to stop working or if it was all image update related, but editing the script and mounting read only did the trick!

kerem commented

Author

Owner

@happyliuxq commented on GitHub (Jul 8, 2022):

hello,I also encountered this problem，docker inside error:Waitting for connection to the localhost host on port 5672 arm64 system，help！

@happyliuxq commented on GitHub (Jul 8, 2022): hello,I also encountered this problem，docker inside error:Waitting for connection to the localhost host on port 5672 arm64 system，help！ ![image](https://user-images.githubusercontent.com/93078973/177900575-b92a2d57-4c3a-4a6b-9b79-18ac02a532fe.png)

kerem commented

Author

Owner

@ShockwaveNN commented on GitHub (Jul 8, 2022):

@happyliuxq Sorry, but we still not able to reproduce wthis problem, it has something to do with with postgresql start, maybe something unusual on your host system, but I've no idea why this happened

@ShockwaveNN commented on GitHub (Jul 8, 2022): @happyliuxq Sorry, but we still not able to reproduce wthis problem, it has something to do with with postgresql start, maybe something unusual on your host system, but I've no idea why this happened

kerem commented

Author

Owner

@russlank commented on GitHub (Feb 26, 2023):

Huh! ... it seems that all guys have their machines unusual!!!

@russlank commented on GitHub (Feb 26, 2023): Huh! ... it seems that all guys have their machines unusual!!!

kerem commented

Author

Owner

@Midnight1938 commented on GitHub (May 14, 2023):

Facing the same error, but this time with Podman

@Midnight1938 commented on GitHub (May 14, 2023): Facing the same error, but this time with Podman

kerem commented

Author

Owner

@pwepwe973 commented on GitHub (Jun 28, 2023):

hello

after 2 years without this problem again back on the same machine

Starting PostgreSQL 14 database server
Error: /usr/lib/postgresql/14/bin/pg_ctl /usr/lib/postgresql/14/bin/pg_ctl start -D /var/lib/postgresql/14/main -l /var/log/postgresql/postgresql-14-main.log -s -o -c config_file="/etc/postgresql/14/main/postgresql.conf" exited with status 1:
2023-06-28 12:59:15.075 UTC [304] FATAL: could not load private key file "/etc/ssl/private/ssl-cert-snakeoil.key": SSL error code 2147483661
2023-06-28 12:59:15.075 UTC [304] LOG: database system is shut down
pg_ctl: could not start server
Examine the log output.
...fail!
Starting RabbitMQ Messaging Server rabbitmq-server
...done.
Waiting for connection to the localhost host on port 5432
Waiting for connection to the localhost host on port 5432
Waiting for connection to the localhost host on port 5432
Waiting for connection to the localhost host on port 5432
Waiting for connection to the localhost host on port 5432
Waiting for connection to the localhost host on port 5432
Waiting for connection to the localhost host on port 5432
Waiting for connection to the localhost host on port 5432
Waiting for connection to the localhost host on port 5432
Waiting for connection to the localhost host on port 5432
Waiting for connection to the localhost host on port 5432
Waiting for connection to the localhost host on port 5432
Waiting for connection to the localhost host on port 5432
Waiting for connection to the localhost host on port 5432
Waiting for connection to the localhost host on port 5432
Waiting for connection to the localhost host on port 5432

@pwepwe973 commented on GitHub (Jun 28, 2023): hello after 2 years without this problem again back on the same machine * Starting PostgreSQL 14 database server * Error: /usr/lib/postgresql/14/bin/pg_ctl /usr/lib/postgresql/14/bin/pg_ctl start -D /var/lib/postgresql/14/main -l /var/log/postgresql/postgresql-14-main.log -s -o -c config_file="/etc/postgresql/14/main/postgresql.conf" exited with status 1: 2023-06-28 12:59:15.075 UTC [304] FATAL: could not load private key file "/etc/ssl/private/ssl-cert-snakeoil.key": SSL error code 2147483661 2023-06-28 12:59:15.075 UTC [304] LOG: database system is shut down pg_ctl: could not start server Examine the log output. ...fail! * Starting RabbitMQ Messaging Server rabbitmq-server ...done. Waiting for connection to the localhost host on port 5432 Waiting for connection to the localhost host on port 5432 Waiting for connection to the localhost host on port 5432 Waiting for connection to the localhost host on port 5432 Waiting for connection to the localhost host on port 5432 Waiting for connection to the localhost host on port 5432 Waiting for connection to the localhost host on port 5432 Waiting for connection to the localhost host on port 5432 Waiting for connection to the localhost host on port 5432 Waiting for connection to the localhost host on port 5432 Waiting for connection to the localhost host on port 5432 Waiting for connection to the localhost host on port 5432 Waiting for connection to the localhost host on port 5432 Waiting for connection to the localhost host on port 5432 Waiting for connection to the localhost host on port 5432 Waiting for connection to the localhost host on port 5432

kerem commented

Author

Owner

@pwepwe973 commented on GitHub (Jul 6, 2023):

hello ?

@pwepwe973 commented on GitHub (Jul 6, 2023): hello ?

kerem commented

Author

Owner

@pwepwe973 commented on GitHub (Jul 14, 2023):

après tout plusieurs années à utiliser onlyoffice ces 2 ou 3 semaines a essayer de trouver la solution ce soir j'ai décider d’abandonner cette application car découragé la dernière fois il c'est répare tout seul comme ça et là malgré toute mes tentatives rien à faire, il ne fonctionne pas même lançon avec volumes etc.. bon ben merci pour ces bon moment sniff je vais chercher une alternative

@pwepwe973 commented on GitHub (Jul 14, 2023): après tout plusieurs années à utiliser onlyoffice ces 2 ou 3 semaines a essayer de trouver la solution ce soir j'ai décider d’abandonner cette application car découragé la dernière fois il c'est répare tout seul comme ça et là malgré toute mes tentatives rien à faire, il ne fonctionne pas même lançon avec volumes etc.. bon ben merci pour ces bon moment sniff je vais chercher une alternative

kerem commented

Author

Owner

@shuguang101 commented on GitHub (Aug 3, 2023):

Please reopen this issue, I have encountered this problem with podman rootless container.

podman version 4.6.0
podman-compose version 1.0.6
onlyoffice/documentserver:7.4 or onlyoffice/documentserver:7.3

First run podman-compose up, wait for hours, then run podman-compose down & up several times, the following folder/file permission will be changed to root.root, this will cause postgresql failed to start (postgres user is used to run postgresql). This is strange because I haven't mounted any volume to persistent these folder/file:

/var/log/postgresql
/etc/ssl/private/ssl-cert-snakeoil.key

The podman-compose yml file I used is as follows:
  oods:
    image: onlyoffice/documentserver:7.3 or 7.4
    container_name: xxx-oods
    logging:
      options:
        max-size: "15m"
        max-file: "30"
    networks:
      - xxx-net
    environment:
      - JWT_ENABLED=true

@shuguang101 commented on GitHub (Aug 3, 2023): Please reopen this issue, I have encountered this problem with podman rootless container. podman version 4.6.0 podman-compose version 1.0.6 onlyoffice/documentserver:7.4 or onlyoffice/documentserver:7.3 First run podman-compose up, wait for hours, then run podman-compose down & up several times, the following folder/file permission will be changed to root.root, this will cause postgresql failed to start (postgres user is used to run postgresql). This is strange because I haven't mounted any volume to persistent these folder/file: ``` /var/log/postgresql /etc/ssl/private/ssl-cert-snakeoil.key ``` ``` The podman-compose yml file I used is as follows: oods: image: onlyoffice/documentserver:7.3 or 7.4 container_name: xxx-oods logging: options: max-size: "15m" max-file: "30" networks: - xxx-net environment: - JWT_ENABLED=true ```

kerem commented

Author

Owner

@pwepwe973 commented on GitHub (Jan 6, 2024):

Starting PostgreSQL 14 database server * Error: /usr/lib/postgresql/14/bin/pg_ctl /usr/lib/postgresql/14/bin/pg_ctl start -D /var/lib/postgresql/14/main -l /var/log/postgresql/postgresql-14-main.log -s -o -c config_file="/etc/postgresql/14/main/postgresql.conf" exited with status 1:
2024-01-06 00:32:00.694 UTC [315] FATAL: could not load private key file "/etc/ssl/private/ssl-cert-snakeoil.key": SSL error code 2147483661
2024-01-06 00:32:00.694 UTC [315] LOG: database system is shut down
pg_ctl: could not start server
Examine the log output.

[fail]

Starting RabbitMQ Messaging Server rabbitmq-server
[ OK ]
Starting redis-server: redis-server.
Waiting for connection to the localhost host on port 5432

@pwepwe973 commented on GitHub (Jan 6, 2024): * Starting PostgreSQL 14 database server * Error: /usr/lib/postgresql/14/bin/pg_ctl /usr/lib/postgresql/14/bin/pg_ctl start -D /var/lib/postgresql/14/main -l /var/log/postgresql/postgresql-14-main.log -s -o -c config_file="/etc/postgresql/14/main/postgresql.conf" exited with status 1: 2024-01-06 00:32:00.694 UTC [315] FATAL: could not load private key file "/etc/ssl/private/ssl-cert-snakeoil.key": SSL error code 2147483661 2024-01-06 00:32:00.694 UTC [315] LOG: database system is shut down pg_ctl: could not start server Examine the log output. [fail] * Starting RabbitMQ Messaging Server rabbitmq-server [ OK ] Starting redis-server: redis-server. Waiting for connection to the localhost host on port 5432

kerem commented

Author

Owner

@Feriman22 commented on GitHub (Jan 16, 2025):

I have noticed that PostgreSQL is not running at the moment, so I have to start it manually. I'm using Docker.

docker exec "$CONTAINER_NAME" service postgresql start

It solved the issue for me.

@Feriman22 commented on GitHub (Jan 16, 2025): I have noticed that PostgreSQL is not running at the moment, so I have to start it manually. I'm using Docker. `docker exec "$CONTAINER_NAME" service postgresql start` It solved the issue for me.

kerem commented

Author

Owner

@nook24 commented on GitHub (Feb 10, 2025):

Had a similar issue. Delete all the docker volumes and restarting the container resolved the issue for me.

@nook24 commented on GitHub (Feb 10, 2025): Had a similar issue. Delete all the docker volumes and restarting the container resolved the issue for me.

kerem commented