-
How to use GitHub
Steps to reproduce
Expected behaviorOnlyOffice starting and listening Actual behaviorerror Log and waiting for a localhost connection Host OSdebian 10 Nextcloud AIO versionNextcloud AIO v1.7.1 Current channellatest Other valuable infoclick hereapachenc: getaddrinfo for host "nextcloud-aio-nextcloud" port 9000: Temporary failure in name resolution nextcloudApplying other settings... redis1:C 30 Aug 2022 00:12:26.949 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo database
The database cluster will be initialized with locale "en_US.utf8". Data page checksums are disabled. fixing permissions on existing directory /var/lib/postgresql/data ... ok Success. You can now start the database server using: initdb: warning: enabling "trust" authentication for local connections /usr/local/bin/docker-entrypoint.sh: running /docker-entrypoint-initdb.d/init-user-db.sh
2022-08-30 00:12:24.638 CEST [35] LOG: received fast shutdown request PostgreSQL init process complete; ready for start up. 2022-08-30 00:12:24.771 CEST [13] LOG: starting PostgreSQL 14.5 on x86_64-pc-linux-musl, compiled by gcc (Alpine 11.2.1_git20220219) 11.2.1 20220219, 64-bit ###talk Loading plugin 'libjanus_sip.so'... Running Janus as a daemon
|
Beta Was this translation helpful? Give feedback.
Replies: 14 comments 20 replies
-
|
I could track it down to here but I have no clue whats it means root@privacy:/# cat /var/log/rabbitmq/startup_err |
Beta Was this translation helpful? Give feedback.
-
|
After I restart the container, because its broken I get the same docker error
root@privacy:/# cat /var/log/rabbitmq/startup_err |
Beta Was this translation helpful? Give feedback.
-
|
Just to make sure that an excessive amout of restarting the container doesnt change the result here the third restart with these result:
So as it seems every restart brings a diffrent error message Just so you know in startup_log, there is nothing EDIT: <0.51.0> =SUPERVISOR REPORT==== 29-Aug-2022::22:40:56.025384 === =ERROR REPORT==== 29-Aug-2022::22:40:56.027283 === =CRASH REPORT==== 29-Aug-2022::22:40:56.027586 === =SUPERVISOR REPORT==== 29-Aug-2022::22:40:56.053139 === |
Beta Was this translation helpful? Give feedback.
-
|
Sorry, but I cannot reproduce this issue. For me the onlyoffice logs looks like this: |
Beta Was this translation helpful? Give feedback.
-
|
Also we simply reuse the official onlyoffice container so this is nothing we can fix on our side if the container simply does not start. See https://github.com/nextcloud/all-in-one/blob/main/Containers/onlyoffice/Dockerfile |
Beta Was this translation helpful? Give feedback.
-
|
So I have a suspion that is has something to do with docker max user process or max process for docker service. I need to look further into it. I just dont understand why this is only related to nextcloud. I had no issues so far with other docker stacks or container. |
Beta Was this translation helpful? Give feedback.
-
I don't think so.
I don't understand either why you have so many problems with it. |
Beta Was this translation helpful? Give feedback.
This comment has been hidden.
This comment has been hidden.
-
|
To add on to this, I tried after giving up with onlyoffice, another aio installation without onlyoffice. Only to find out that the inizial bootup kinda works, just proxying wasnt working 100%. After updating and restarting the stack my nextcloud container died and stayed dead |
Beta Was this translation helpful? Give feedback.
-
|
I have quite a collection of bugs and after 1 or 2 weeks of trying to get a new nextcloud up and running I start to lose sanity. It shouldnt be that hard. Just for context reason, I have a maschine with nginx proxying 13 webadresses from a local docker network and I am trying to force the aio into the local docker network with no success. It just want to pop new container with a seperate network. |
Beta Was this translation helpful? Give feedback.
-
Can you provide the logs?
I've only seen one bug report of you until now that I can reproduce.
I agree!
Yes, this is not possible. Did you read and followed https://github.com/nextcloud/all-in-one/blob/main/reverse-proxy.md? |
Beta Was this translation helpful? Give feedback.
-
Sadly no logs, they are lost
Yeah because they were random and not the same each time I restarted the containers
yes I did, the post 825 or smth was really helpful |
Beta Was this translation helpful? Give feedback.
-
|
I got new information, after removing AIO and portainer nextcloud, the instance launched by portainer, magical fixed it self my hyposis is that portainer has something to do with it. Because 2 or 3 other of my container died with similar issues. After the portainer removal it all got back to normal. Has something to do with linux and ulimite -u or ulimit -a. my host maschine has unlimited setup. Idk about AIO or portainer ulimit setup and because 3 diffrent os are accessing the same docker socket it caused some weird stuff |
Beta Was this translation helpful? Give feedback.
-
|
Another suspion from me is I have debian 10 installed and lts is running out soonish. docker could maybe not support it anymore and i need to move to debian 11 |
Beta Was this translation helpful? Give feedback.
-
|
yes, maybe upgrading already solves the issue... |
Beta Was this translation helpful? Give feedback.
-
|
Out of my experience I dont do any funny stuff with docker socket, that thing is holy now for me. |
Beta Was this translation helpful? Give feedback.
-
|
If I have time in a couple of days I can try to reproduce the issue mentioned here by doing a debian 10 install with portainer and aio and see if I get the same results On a testing maschine of course |
Beta Was this translation helpful? Give feedback.
-
|
Error response from daemon: Cannot restart container nextcloud-aio-nextcloud: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error running hook #0: error running hook: exit status 2, stdout: , stderr: runtime/cgo: runtime/cgo: pthread_create failed: Resource temporarily unavailable goroutine 0 [idle]: goroutine 1 [running, locked to thread]: rax 0x0 I found something new |
Beta Was this translation helpful? Give feedback.
-
Current setup:Docker-compose:version: "3.8" services: nextcloud-aio-database: nextcloud-aio-nextcloud: nextcloud-aio-redis: nextcloud-aio-collabora: nextcloud-aio-talk: nextcloud-aio-clamav: volumes: networks: .env/confIs full with data just to lazy to paste and pleeb it |
Beta Was this translation helpful? Give feedback.
-
|
Just starting a collection of errors ~$ docker restart nextcloud-aio-nextcloud |
Beta Was this translation helpful? Give feedback.
-
|
So I starting, slowly but surely to unpack the mysterie [02-Sep-2022 00:27:30] NOTICE: [pool www] 'user' directive is ignored when FPM is not running as root 502 Bad Gatewayopen (truncated...) #0 /var/www/html/3rdparty/guzzlehttp/guzzle/src/Middleware.php(69): GuzzleHttp\Exception\RequestException::create(Object(GuzzleHttp\Psr7\Request), Object(GuzzleHttp\Psr7\Response), NULL, Array, NULL) |
Beta Was this translation helpful? Give feedback.
-
|
So I thought |
Beta Was this translation helpful? Give feedback.
-
|
Just to add on docker-compose up -d is not a problem but docker restart nextcloud_aio_nextcloud or whatever the container is named is an issue $ docker-compose up -d |
Beta Was this translation helpful? Give feedback.
-
|
I have no clue at all whats going on anymore. Seems like a not nextcloud issue but I cant pin it down because I dont have any issue with anything on the system if I dont use the docker container from nextcloud. It seems. |
Beta Was this translation helpful? Give feedback.
-
|
Ohh and sometime I have error "-bash: fork: retry: Resource temporarily unavailable" which points to https://stackoverflow.com/questions/34452302/how-to-increase-maximum-number-of-jvm-threads-linux-64bit/43157379#43157379 https://www.linuxquestions.org/questions/showthread.php?p=5784946#post5784946 which is quite weird, I only have 25 container and they all are talking about system limit. I dont think I touched any limit. I have 48 GB of RAM only using 5 GB atm. 10 cores which are 0.6% used, sometimes 5%. The only thing that makes sense is my hoster is doing something wierd with my container (vserver) or nextcloud is spawning an absurd amout of process that hits my limits. |
Beta Was this translation helpful? Give feedback.
-
|
To add on to this a new error occured $ docker-compose down |
Beta Was this translation helpful? Give feedback.
-
|
https://stackoverflow.com/questions/70087344/python-in-docker-runtimeerror-cant-start-new-thread Answer to the issue |
Beta Was this translation helpful? Give feedback.
-
|
docker version Server: Docker Engine - Community weird |
Beta Was this translation helpful? Give feedback.
-
|
Just for reference $ ulimit |
Beta Was this translation helpful? Give feedback.
-
|
|
Beta Was this translation helpful? Give feedback.
-
|
You could probably try to switch the hoster and see if it fixes your problems. Because I remember a guy that had problem with AIO and switched the hoster, then it worked. Afterwards he found out that hist former host wasn't really supporting docker on their VPS. |
Beta Was this translation helpful? Give feedback.
-
|
that sounds like a good idea, lemme have a look for good alternatives |
Beta Was this translation helpful? Give feedback.
-
|
Just to close this case https://www.strato.de/faq/server/prozesse-vs-threads-bei-linux-v-servern/ this is the solution ... |
Beta Was this translation helpful? Give feedback.
-
|
all right, marked the thread as solved 👍 |
Beta Was this translation helpful? Give feedback.
You could probably try to switch the hoster and see if it fixes your problems.
Because I remember a guy that had problem with AIO and switched the hoster, then it worked. Afterwards he found out that hist former host wasn't really supporting docker on their VPS.