[GH-ISSUE #145] After docker-compose up HA Proxy not configured #84

Closed
opened 2026-02-26 09:36:07 +03:00 by kerem · 11 comments
Owner

Originally created by @chrsch on GitHub (Dec 12, 2018).
Original GitHub issue: https://github.com/ONLYOFFICE/Docker-DocumentServer/issues/145

Bug report

What is the current behavior?
After "docker-compose up -d" I can see all containers running (docker ps). But on my ip:80 there is no OO Document Server available. I checked haproxy by visiting my ip:1936 and noticed there are no frontends and backends setup.

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem.

  1. Get the docker-compose.yml
  2. Run docker-compose up -d

What is the expected behavior?
After containers are started the document server is available from ip:80

Did this work in previous versions of DocumentServer?
Unknown

DocumentServer Docker tag:
onlyoffice/documentserver:latest

Host Operating System:
Ubuntu 18 LTS / Docker CE

Originally created by @chrsch on GitHub (Dec 12, 2018). Original GitHub issue: https://github.com/ONLYOFFICE/Docker-DocumentServer/issues/145 Bug report **What is the current behavior?** After "docker-compose up -d" I can see all containers running (docker ps). But on my ip:80 there is no OO Document Server available. I checked haproxy by visiting my ip:1936 and noticed there are no frontends and backends setup. **If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem.** 1. Get the docker-compose.yml 2. Run docker-compose up -d **What is the expected behavior?** After containers are started the document server is available from ip:80 **Did this work in previous versions of DocumentServer?** Unknown **DocumentServer Docker tag:** onlyoffice/documentserver:latest **Host Operating System:** Ubuntu 18 LTS / Docker CE
kerem 2026-02-26 09:36:07 +03:00
Author
Owner

@ShockwaveNN commented on GitHub (Dec 12, 2018):

@chrsch Hi, could you look to logs those services?
I tried it myself and seems there is a problem with repeating error
onlyoffice-documentserver_1 | Waiting for connection to the localhost host on port 5432
Not sure if this is a same problem like yours

<!-- gh-comment-id:446636726 --> @ShockwaveNN commented on GitHub (Dec 12, 2018): @chrsch Hi, could you look to logs those services? I tried it myself and seems there is a problem with repeating error `onlyoffice-documentserver_1 | Waiting for connection to the localhost host on port 5432` Not sure if this is a same problem like yours
Author
Owner

@chrsch commented on GitHub (Dec 12, 2018):

@ShockwaveNN No I don't see such errors in the logs. For me it is basically haproxy seems to not be setup correctly. There are no frontends/ backends available if I visit ip:1936 (haproxy stats page).

<!-- gh-comment-id:446750032 --> @chrsch commented on GitHub (Dec 12, 2018): @ShockwaveNN No I don't see such errors in the logs. For me it is basically haproxy seems to not be setup correctly. There are no frontends/ backends available if I visit ip:1936 (haproxy stats page).
Author
Owner

@agolybev commented on GitHub (Dec 13, 2018):

Hi, I've tested it yesterday. It works for me.

<!-- gh-comment-id:446878263 --> @agolybev commented on GitHub (Dec 13, 2018): Hi, I've tested it yesterday. It works for me.
Author
Owner

@ShockwaveNN commented on GitHub (Dec 13, 2018):

@chrsch Ok, another question.
What is state of logs of onlyoffice-postgres container (docker-compose logs onlyoffice-postgresql)
We can confirm there is some trouble with ERROR: relation "checkissupportonconflict" does not exist at character 13 error

<!-- gh-comment-id:447021945 --> @ShockwaveNN commented on GitHub (Dec 13, 2018): @chrsch Ok, another question. What is state of logs of `onlyoffice-postgres` container (`docker-compose logs onlyoffice-postgresql`) We can confirm there is some trouble with `ERROR: relation "checkissupportonconflict" does not exist at character 13` error
Author
Owner

@chrsch commented on GitHub (Dec 13, 2018):

@ShockwaveNN
I looked at the postgres container logs, the error is there:

PostgreSQL init process complete; ready for start up.

LOG:  database system was shut down at 2018-12-12 21:22:04 UTC
LOG:  MultiXact member wraparound protections are now enabled
LOG:  database system is ready to accept connections
LOG:  autovacuum launcher started
LOG:  incomplete startup packet
LOG:  incomplete startup packet
ERROR:  relation "checkissupportonconflict" does not exist at character 13
STATEMENT:  INSERT INTO checkIsSupportOnConflict (id) VALUES(1) ON CONFLICT DO NOTHING;
ERROR:  relation "checkissupportonconflict" does not exist at character 13
STATEMENT:  INSERT INTO checkIsSupportOnConflict (id) VALUES(1) ON CONFLICT DO NOTHING;
ERROR:  relation "checkissupportonconflict" does not exist at character 13
STATEMENT:  INSERT INTO checkIsSupportOnConflict (id) VALUES(1) ON CONFLICT DO NOTHING;
ERROR:  relation "checkissupportonconflict" does not exist at character 13
STATEMENT:  INSERT INTO checkIsSupportOnConflict (id) VALUES(1) ON CONFLICT DO NOTHING;
ERROR:  relation "checkissupportonconflict" does not exist at character 13
STATEMENT:  INSERT INTO checkIsSupportOnConflict (id) VALUES(1) ON CONFLICT DO NOTHING;
LOG:  database system was interrupted; last known up at 2018-12-12 21:22:06 UTC
LOG:  incomplete startup packet
FATAL:  the database system is starting up
FATAL:  the database system is starting up
LOG:  database system was not properly shut down; automatic recovery in progress
LOG:  redo starts at 0/17039C0
LOG:  invalid record length at 0/172C438
LOG:  redo done at 0/172C410
LOG:  last completed transaction was at log time 2018-12-12 21:22:08.012204+00
LOG:  incomplete startup packet
LOG:  MultiXact member wraparound protections are now enabled
LOG:  database system is ready to accept connections
LOG:  autovacuum launcher started
LOG:  database system was shut down at 2018-12-12 21:45:45 UTC
LOG:  MultiXact member wraparound protections are now enabled
LOG:  database system is ready to accept connections
LOG:  autovacuum launcher started
LOG:  incomplete startup packet
LOG:  incomplete startup packet
<!-- gh-comment-id:447024182 --> @chrsch commented on GitHub (Dec 13, 2018): @ShockwaveNN I looked at the postgres container logs, the error is there: ``` PostgreSQL init process complete; ready for start up. LOG: database system was shut down at 2018-12-12 21:22:04 UTC LOG: MultiXact member wraparound protections are now enabled LOG: database system is ready to accept connections LOG: autovacuum launcher started LOG: incomplete startup packet LOG: incomplete startup packet ERROR: relation "checkissupportonconflict" does not exist at character 13 STATEMENT: INSERT INTO checkIsSupportOnConflict (id) VALUES(1) ON CONFLICT DO NOTHING; ERROR: relation "checkissupportonconflict" does not exist at character 13 STATEMENT: INSERT INTO checkIsSupportOnConflict (id) VALUES(1) ON CONFLICT DO NOTHING; ERROR: relation "checkissupportonconflict" does not exist at character 13 STATEMENT: INSERT INTO checkIsSupportOnConflict (id) VALUES(1) ON CONFLICT DO NOTHING; ERROR: relation "checkissupportonconflict" does not exist at character 13 STATEMENT: INSERT INTO checkIsSupportOnConflict (id) VALUES(1) ON CONFLICT DO NOTHING; ERROR: relation "checkissupportonconflict" does not exist at character 13 STATEMENT: INSERT INTO checkIsSupportOnConflict (id) VALUES(1) ON CONFLICT DO NOTHING; LOG: database system was interrupted; last known up at 2018-12-12 21:22:06 UTC LOG: incomplete startup packet FATAL: the database system is starting up FATAL: the database system is starting up LOG: database system was not properly shut down; automatic recovery in progress LOG: redo starts at 0/17039C0 LOG: invalid record length at 0/172C438 LOG: redo done at 0/172C410 LOG: last completed transaction was at log time 2018-12-12 21:22:08.012204+00 LOG: incomplete startup packet LOG: MultiXact member wraparound protections are now enabled LOG: database system is ready to accept connections LOG: autovacuum launcher started LOG: database system was shut down at 2018-12-12 21:45:45 UTC LOG: MultiXact member wraparound protections are now enabled LOG: database system is ready to accept connections LOG: autovacuum launcher started LOG: incomplete startup packet LOG: incomplete startup packet ```
Author
Owner

@ShockwaveNN commented on GitHub (Dec 13, 2018):

@chrsch Ok, so we can confirm this issue, we got some troubles. We're trying to understand what happening

<!-- gh-comment-id:447025812 --> @ShockwaveNN commented on GitHub (Dec 13, 2018): @chrsch Ok, so we can confirm this issue, we got some troubles. We're trying to understand what happening
Author
Owner

@ShockwaveNN commented on GitHub (Dec 14, 2018):

@chrsch could you try to reinit compose several times - seems this problem not related with relation "checkissupportonconflict" does not exist at character 13
I was able to reproduce your issue once, but since when - everything is fine. Seems issue have something with starting orders and timeouts of startup process

<!-- gh-comment-id:447332300 --> @ShockwaveNN commented on GitHub (Dec 14, 2018): @chrsch could you try to reinit compose several times - seems this problem not related with `relation "checkissupportonconflict" does not exist at character 13` I was able to reproduce your issue once, but since when - everything is fine. Seems issue have something with starting orders and timeouts of startup process
Author
Owner

@chrsch commented on GitHub (Dec 14, 2018):

@ShockwaveNN I'll give it a try and report back. I managed to get it running on Docker @ Mac Mojave and Docker @ Ubuntu 16 LTS. So this seems to be related to Ubuntu 18 LTS in some way. Maybe this info helps figuring out what's going on.

<!-- gh-comment-id:447441652 --> @chrsch commented on GitHub (Dec 14, 2018): @ShockwaveNN I'll give it a try and report back. I managed to get it running on Docker @ Mac Mojave and Docker @ Ubuntu 16 LTS. So this seems to be related to Ubuntu 18 LTS in some way. Maybe this info helps figuring out what's going on.
Author
Owner

@ShockwaveNN commented on GitHub (Dec 17, 2018):

@chrsch I'm not sure it is related to Ubuntu 18, we don't know exact reason but seems problem just occurs randomly, so you're just unlucky on Ubuntu 18

<!-- gh-comment-id:447747909 --> @ShockwaveNN commented on GitHub (Dec 17, 2018): @chrsch I'm not sure it is related to Ubuntu 18, we don't know exact reason but seems problem just occurs randomly, so you're just unlucky on Ubuntu 18
Author
Owner

@hypervtechnics commented on GitHub (Dec 10, 2019):

has this been solved? i am having this issue too.

<!-- gh-comment-id:564215856 --> @hypervtechnics commented on GitHub (Dec 10, 2019): has this been solved? i am having this issue too.
Author
Owner

@igwyd commented on GitHub (Nov 1, 2024):

HAproxy is no longer used in our docker-compose.yml, we will close it

<!-- gh-comment-id:2451713401 --> @igwyd commented on GitHub (Nov 1, 2024): HAproxy is no longer used in our docker-compose.yml, we will close it
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/Docker-DocumentServer-ONLYOFFICE#84
No description provided.