4 Jan 2022 |
TheFrenchGhosty | I'm trying to find what code 159 is for postgres | 14:26:41 |
wanion20 | Code 159 is postgress error code? | 14:26:56 |
wanion20 | I thought its docker error code | 14:27:00 |
TheFrenchGhosty | yes | 14:27:01 |
TheFrenchGhosty | oh maybe | 14:27:14 |
wanion20 | the service thats exiting is invidious_invidious and not invidious_postgres | 14:27:19 |
wanion20 | wait let me reconfirm | 14:27:24 |
Samantaz Fox | yeah, it's invidious | 14:27:36 |
wanion20 | invidious_invidious_1 exited with code 159 | 14:27:38 |
TheFrenchGhosty | wanion20: Let's try something:
Remove/comment everything related to autoheal
| 14:27:56 |
Samantaz Fox | https://forums.docker.com/t/unable-to-run-aarch64-containers-from-armv7-docker/67187 | 14:27:57 |
Samantaz Fox | doesn't help much :/ | 14:28:03 |
wanion20 | In reply to @thefrenchghosty:pussthecat.org
wanion20: Let's try something:
Remove/comment everything related to autoheal
Okay will do that brb | 14:28:21 |
Samantaz Fox | Exit Code 139: Indicates failure as container received SIGSEGV | 14:28:29 |
TheFrenchGhosty | In reply to @samantazfox:pussthecat.org
Exit Code 139: Indicates failure as container received SIGSEGV
it's 159 | 14:28:42 |
TheFrenchGhosty | In reply to @samantazfox:pussthecat.org
Exit Code 139: Indicates failure as container received SIGSEGV
* it's 159 | 14:28:48 |
Samantaz Fox | Ah, oops | 14:28:54 |
wanion20 | In reply to @samantazfox:pussthecat.org
Exit Code 139: Indicates failure as container received SIGSEGV
Yes I googled the codes. It goes from 1 to 139 to 143 | 14:29:31 |
wanion20 | theres no 159 🙈 | 14:29:47 |
TheFrenchGhosty | In reply to @wanion20:matrix.org theres no 159 🙈 I couldn't find anything either | 14:30:02 |
Samantaz Fox | Exit code of contained command otherwise | 14:30:18 |
Samantaz Fox | Ah | 14:30:22 |
TheFrenchGhosty | In reply to @samantazfox:pussthecat.org
Exit code of contained command otherwise
meaning? | 14:30:31 |
Samantaz Fox | invidious exited with code 159 | 14:31:01 |
wanion20 | In reply to @thefrenchghosty:pussthecat.org
wanion20: Let's try something:
Remove/comment everything related to autoheal
pi@senpi:~/Docker-Services/invidious $ docker-compose up --remove-orphans
Removing orphan container "invidious_autoheal_1"
invidious_postgres_1 is up-to-date
Creating invidious_invidious_1 ... done
Attaching to invidious_postgres_1, invidious_invidious_1
postgres_1 |
postgres_1 | PostgreSQL Database directory appears to contain a database; Skipping initialization
postgres_1 |
postgres_1 | 2022-01-04 14:29:04.904 UTC [1] LOG: listening on IPv4 address "0.0.0.0", port 5432
postgres_1 | 2022-01-04 14:29:04.904 UTC [1] LOG: listening on IPv6 address "::", port 5432
postgres_1 | 2022-01-04 14:29:04.953 UTC [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
postgres_1 | 2022-01-04 14:29:05.065 UTC [28] LOG: database system was shut down at 2022-01-04 14:15:35 UTC
postgres_1 | 2022-01-04 14:29:05.100 UTC [1] LOG: database system is ready to accept connections
invidious_invidious_1 exited with code 159
invidious_invidious_1 exited with code 0
invidious_invidious_1 exited with code 159
invidious_invidious_1 exited with code 159
invidious_invidious_1 exited with code 159
invidious_invidious_1 exited with code 159
invidious_invidious_1 exited with code 159
invidious_invidious_1 exited with code 159
invidious_invidious_1 exited with code 159
| 14:31:01 |
wanion20 | In reply to @samantazfox:pussthecat.org invidious exited with code 159 Do we have a documentation for error codes? | 14:31:15 |
TheFrenchGhosty | So invidious is crashing | 14:31:17 |
wanion20 | for invidious i mean | 14:31:21 |
TheFrenchGhosty | for whatever reason | 14:31:21 |
Samantaz Fox | wanion20 what's your invidious log level? | 14:31:38 |