'
> config/unicorn_launcher: line 71: kill: (6195) - No such process
> config/unicorn_launcher: line 15: kill: (6195) - No such process
> (6190) exiting
> ok: run: redis: (pid 6038) 94s
>
> ```
---
### Author:  [@Falco](https://meta.discourse.org/u/Falco)
#### Post date: [August 14, 2023, 8:10pm UTC](https://meta.discourse.org/t/argumenterror-directory-for-pid-unicorn-pid-not-writable/274948/8 "2023-08-14T20:10:05Z")
This looks like a folder permission issue. This is kinda weird as that folder in inside the container filesystem, and not mounted from the host.
You can try entering the running container and tweaking the folder permissions manually. If you need help with that, can you please share the output of
```plaintext
docker exec -it app ls -lah /var/www/discourse/tmp/pids
```
---
### Author:  [@facorread](https://meta.discourse.org/u/facorread)
#### Post date: [August 15, 2023, 8:08pm UTC](https://meta.discourse.org/t/argumenterror-directory-for-pid-unicorn-pid-not-writable/274948/9 "2023-08-15T20:08:44Z")
```plaintext
docker exec -it app chown discourse.www-data /var/www/discourse/tmp/pids
docker exec -it app chmod g+w /var/www/discourse/tmp/pids
./launcher rebuild app
```
---
### Author:  [@jeanas](https://meta.discourse.org/u/jeanas)
#### Post date: [August 16, 2023, 8:49pm UTC](https://meta.discourse.org/t/argumenterror-directory-for-pid-unicorn-pid-not-writable/274948/10 "2023-08-16T20:49:08Z")
I’m installing from scratch yet again and trying to pay more attention to the log messages from the app build this time.
I see these:
```plaintext
153:C 16 Aug 2023 20:24:11.676 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
153:C 16 Aug 2023 20:24:11.676 # Redis version=7.0.7, bits=64, commit=00000000, modified=0, pid=153, just started
153:C 16 Aug 2023 20:24:11.676 # Configuration loaded
153:M 16 Aug 2023 20:24:11.677 * monotonic clock: POSIX clock_gettime
153:M 16 Aug 2023 20:24:11.677 # Warning: Could not create server TCP listening socket *:6379: bind: Address already in use
153:M 16 Aug 2023 20:24:11.678 # Failed listening on port 6379 (TCP), aborting.
```
Also this:
```plaintext
I, [2023-08-16T20:24:26.172936 #1] INFO -- : > cd /var/www/discourse && su discourse -c 'yarn install --frozen-lockfile && yarn cache clean'
warning " > @glint/environment-ember-loose@1.0.2" has unmet peer dependency "@glimmer/component@^1.1.2".
warning " > @glint/environment-ember-template-imports@1.0.2" has unmet peer dependency "ember-template-imports@^3.0.0".
warning " > @mixer/parallel-prettier@2.0.3" has unmet peer dependency "prettier@^2.0.0".
warning Resolution field "babel-plugin-ember-template-compilation@2.0.0" is incompatible with requested version "babel-plugin-ember-template-compilation@^2.0.1"
warning Resolution field "unset-value@2.0.1" is incompatible with requested version "unset-value@^1.0.0"
warning " > babel-plugin-debug-macros@0.4.0-pre1" has unmet peer dependency "@babel/core@^7.0.0".
warning "workspace-aggregator-d7aa52aa-3a92-43f5-97ca-2c6c21fe43f0 > discourse > @uppy/aws-s3@3.0.6" has incorrect peer dependency "@uppy/core@^3.1.2".
warning "workspace-aggregator-d7aa52aa-3a92-43f5-97ca-2c6c21fe43f0 > discourse > @uppy/aws-s3-multipart@3.1.3" has incorrect peer dependency "@uppy/core@^3.1.2".
warning "workspace-aggregator-d7aa52aa-3a92-43f5-97ca-2c6c21fe43f0 > discourse > @uppy/xhr-upload@3.1.1" has incorrect peer dependency "@uppy/core@^3.1.2".
warning "workspace-aggregator-d7aa52aa-3a92-43f5-97ca-2c6c21fe43f0 > discourse > @uppy/aws-s3 > @uppy/xhr-upload@3.3.0" has incorrect peer dependency "@uppy/core@^3.2.1".
```
(I’ll try the manual permission changes when it finishes building.)
---
### Author:  [@jeanas](https://meta.discourse.org/u/jeanas)
#### Post date: [August 16, 2023, 9:02pm UTC](https://meta.discourse.org/t/argumenterror-directory-for-pid-unicorn-pid-not-writable/274948/11 "2023-08-16T21:02:05Z")
Before chowning + chmodding:
```plaintext
root@ubuntu-app:/var/www/discourse# ls -lah /var/www/discourse/tmp/pids
total 8.0K
drwxr-xr-x 2 root root 4.0K Aug 16 20:47 .
drwxr-xr-x 6 root root 4.0K Aug 16 20:53 ..
```
After:
```plaintext
root@ubuntu-app:/var/www/discourse# ls -lah /var/www/discourse/tmp/pids
total 16K
drwxrwxr-x 1 discourse www-data 4.0K Aug 16 20:58 .
drwxr-xr-x 1 root root 4.0K Aug 16 20:53 ..
-rw-r--r-- 1 discourse www-data 5 Aug 16 20:58 unicorn.pid
```
Now the tail of `./launcher logs app` looks like this:
```plaintext
ok: run: redis: (pid 5790) 184s
ok: run: postgres: (pid 6154) 0s
supervisor pid: 6155 unicorn pid: 6159
config/unicorn_launcher: line 71: kill: (6159) - No such process
config/unicorn_launcher: line 15: kill: (6159) - No such process
(6155) exiting
ok: run: redis: (pid 5790) 188s
ok: run: postgres: (pid 6176) 0s
supervisor pid: 6177 unicorn pid: 6181
config/unicorn_launcher: line 71: kill: (6181) - No such process
config/unicorn_launcher: line 15: kill: (6181) - No such process
(6177) exiting
ok: run: redis: (pid 5790) 192s
timeout: down: postgres: 1s, normally up, want up
ok: run: redis: (pid 5790) 200s
timeout: down: postgres: 0s, normally up, want up
ok: run: redis: (pid 5790) 208s
timeout: down: postgres: 1s, normally up, want up
ok: run: redis: (pid 5790) 215s
timeout: down: postgres: 0s, normally up, want up
ok: run: redis: (pid 5790) 223s
timeout: down: postgres: 1s, normally up, want up
ok: run: redis: (pid 5790) 230s
timeout: down: postgres: 1s, normally up, want up
ok: run: redis: (pid 5790) 238s
ok: run: postgres: (pid 6264) 0s
supervisor pid: 6260 unicorn pid: 6266
config/unicorn_launcher: line 71: kill: (6266) - No such process
config/unicorn_launcher: line 15: kill: (6266) - No such process
(6260) exiting
ok: run: redis: (pid 5790) 244s
ok: run: postgres: (pid 6283) 0s
supervisor pid: 6284 unicorn pid: 6288
```
My browser reports an HTTPS issue with the site, and when I choose the “dangerous” option to bypass, I get the nginx “bad gateway” page.
---
### Author:  [@Godmar\_Back](https://meta.discourse.org/u/Godmar_Back)
#### Post date: [August 21, 2023, 6:42pm UTC](https://meta.discourse.org/t/argumenterror-directory-for-pid-unicorn-pid-not-writable/274948/12 "2023-08-21T18:42:08Z")
I’m having this same issue with the current git.
Rebuilding the container after the `chown` and `chmod` will undo their effects.
---
### Author:  [@Godmar\_Back](https://meta.discourse.org/u/Godmar_Back)
#### Post date: [August 21, 2023, 7:03pm UTC](https://meta.discourse.org/t/argumenterror-directory-for-pid-unicorn-pid-not-writable/274948/13 "2023-08-21T19:03:51Z")
I’m having the same issue. The [last time Discourse broke](https://meta.discourse.org/t/how-to-track-down-failure-of-discourse-upstream-inside-container-resulting-in-502-bad-gateway/256099) was because of an undetected issue with plugins. I’m using these:
```plaintext
- git clone https://github.com/discourse/docker_manager.git
- git clone https://github.com/tfpk/discourse-reveal-anonymous.git
- git clone https://github.com/discourse/discourse-push-notifications.git
- git clone https://github.com/discourse/discourse-data-explorer.git
- git clone https://github.com/discourse/discourse-solved.git
- git clone https://github.com/discourse/discourse-math.git
```
Can we compare notes? Are there any known issues right now with these plugins?
---
### Author:  [@Godmar\_Back](https://meta.discourse.org/u/Godmar_Back)
#### Post date: [August 21, 2023, 7:31pm UTC](https://meta.discourse.org/t/argumenterror-directory-for-pid-unicorn-pid-not-writable/274948/14 "2023-08-21T19:31:53Z")
Here’s more info. In the gunicorn stderr, I see:
```plaintext
/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/activerecord-7.0.7/lib/active_record/connection_adapters/postgresql_adapter.rb:87:in `rescue in new_client': connection to server on socket "/var/run/postgresql/.s.PGSQL.5432" failed: No such file or directory (ActiveRecord::ConnectionNotEstablished)
Is the server running locally and accepting connections on that socket?
```
In the PG log, I see:
```plaintext
2023-08-21 19:24:00.721 UTC [1681] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2023-08-21 19:24:00.728 UTC [1681] LOG: could not open configuration file "/etc/postgresql/13/main/pg_hba.conf": Permission denied
2023-08-21 19:24:00.728 UTC [1681] FATAL: could not load pg_hba.conf
2023-08-21 19:24:00.741 UTC [1681] LOG: database system is shut down
```
further:
```plaintext
# ls -l /etc/postgresql/13/main/pg_hba.conf
-rw-r----- 1 root root 4846 Aug 21 19:05 /etc/postgresql/13/main/pg_hba.conf
```
What user is postgres running under inside the container? With the above permissions, it has to be `root` or someone in group `root`
Ok, so I did `chmod o+r /etc/postgresql/13/main/pg_hba.conf` and now the container is up again.
This is all a bit concerning - why isn’t the recommended installation method not working out of the box? My plugin status currently includes the ones listed above except [data explorer](https://meta.discourse.org/t/32566?silent=true) which I disabled since it had caused the failure the last time.
Crosslinking to
> [@Filesystem permission issues after upgrade to 3.1.0](https://meta.discourse.org/t/filesystem-permission-issues-after-upgrade-to-3-1-0/274654):
>
> I upgraded from 3.0.x to 3.1.0 today. Updaring via the web UI failed, so I did git pull ./launcher rebuild app which finished fine, but all I got was an “invalid gateway” error when visiting the site. I tracked this down to filesystem permission errors: /var/www/discourse/tmp/pids was not writable, fixing that lead to /etc/postgresql/13/main/pg\_hba.conf not being readable. Having fixed those made the site work, but user avatars were missing. Again a temporary directoyr was missing, so I ma…
which reports similar symptoms.
Update: I changed the `git` command in the `cmd` section of the app.yml file to use `sudo` as described in the linked post.
I am declaring this failure to be intermittent. In 3 tries (between each I completely wiped the `shared` directory) it succeeded once and failed twice. When it fails, manually fixing the three permissions in question and then restarting the container resulted in what appears to be a working system. Better logging and better self tests would be nice in order to detect failing container bootstraps.
---
### Author:  [@StanD](https://meta.discourse.org/u/StanD)
#### Post date: [August 22, 2023, 2:50am UTC](https://meta.discourse.org/t/argumenterror-directory-for-pid-unicorn-pid-not-writable/274948/15 "2023-08-22T02:50:53Z")
Changing the permissions on `/var/www/discourse/tmp/pids` and `/etc/postgre/13/main/pg_hba.conf` does not work for me.
I had changed my plugin list before the rebuild but even after restoring the plugin list I get the same `ArgumentError`. Are we sure it is the plugins list that is causing it?
After starting the container I see files written to the `pids` directory. My launcher log stops after this
```plaintext
ok: down: unicorn: 0s, normally up
run-parts: executing /etc/runit/3.d/10-redis
ok: down: redis: 0s, normally up
run-parts: executing /etc/runit/3.d/99-postgres
run-parts: executing /etc/runit/1.d/00-ensure-links
run-parts: executing /etc/runit/1.d/00-fix-var-logs
run-parts: executing /etc/runit/1.d/01-cleanup-web-pids
run-parts: executing /etc/runit/1.d/anacron
run-parts: executing /etc/runit/1.d/cleanup-pids
Cleaning stale PID files
run-parts: executing /etc/runit/1.d/copy-env
Started runsvdir, PID is 35
ok: run: redis: (pid 52) 0s
ok: run: postgres: (pid 55) 0s
supervisor pid: 42 unicorn pid: 75
```
Anything else I can look at?
---
### Author:  [@DarthLasciel](https://meta.discourse.org/u/DarthLasciel)
#### Post date: [August 22, 2023, 2:50pm UTC](https://meta.discourse.org/t/argumenterror-directory-for-pid-unicorn-pid-not-writable/274948/17 "2023-08-22T14:50:46Z")
I have the same issue described in this thread. Tried to install discourse today on a new server, failed because of missing write permission.
The “Fix” with chown/chmod does not work for me, the permission is reset again on ./launcher rebuild app
---
### Author:  [@Falco](https://meta.discourse.org/u/Falco)
#### Post date: [August 22, 2023, 3:52pm UTC](https://meta.discourse.org/t/argumenterror-directory-for-pid-unicorn-pid-not-writable/274948/18 "2023-08-22T15:52:46Z")
So you managed to reproduce this on a brand new install? That’s very useful information, as I can’t reproduce by updating an existing one.
---
### Author:  [@DarthLasciel](https://meta.discourse.org/u/DarthLasciel)
#### Post date: [August 22, 2023, 4:31pm UTC](https://meta.discourse.org/t/argumenterror-directory-for-pid-unicorn-pid-not-writable/274948/19 "2023-08-22T16:31:17Z")
Yes, tried to install discourse by just following the guide and thought i’ve gone mad, since everything “seemed” to work but i only get a “502” error.
I tried changing the permissions within the container without rebuilding. Now i get this:
```plaintext
ok: run: redis: (pid 50) 4677s
ok: run: postgres: (pid 12224) 0s
supervisor pid: 12215 unicorn pid: 12226
config/unicorn_launcher: line 71: kill: (12226) - No such process
config/unicorn_launcher: line 15: kill: (12226) - No such process
(12215) exiting
ok: run: redis: (pid 50) 4686s
ok: run: postgres: (pid 12249) 0s
supervisor pid: 12240 unicorn pid: 12251
config/unicorn_launcher: line 71: kill: (12251) - No such process
config/unicorn_launcher: line 15: kill: (12251) - No such process
(12240) exiting
ok: run: redis: (pid 50) 4695s
timeout: down: postgres: 1s, normally up, want up
ok: run: redis: (pid 50) 4703s
ok: run: postgres: (pid 12279) 0s
supervisor pid: 12275 unicorn pid: 12281
```
I have a second server, set up exactly like this one, running for over a year. That one just works, stopping the container, doing a git pull, rebuild and start also just worked
---
### Author:  [@StanD](https://meta.discourse.org/u/StanD)
#### Post date: [August 22, 2023, 5:15pm UTC](https://meta.discourse.org/t/argumenterror-directory-for-pid-unicorn-pid-not-writable/274948/20 "2023-08-22T17:15:16Z")
Adding this as a data point since I don’t see it in this topic.
Do you see a `fatal: detected dubious ownership...` message in the unicorn log? I am getting this message.
Adding `/var/www/discourse` as `safe.directory` to the `gitconfig` has no effect for my install.
---
### Author:  [@Falco](https://meta.discourse.org/u/Falco)
#### Post date: [August 22, 2023, 5:23pm UTC](https://meta.discourse.org/t/argumenterror-directory-for-pid-unicorn-pid-not-writable/274948/21 "2023-08-22T17:23:56Z")
> [@DarthLasciel](#):
>
> Yes, tried to install discourse by just following the guide and thought i’ve gone mad, since everything “seemed” to work but i only get a “502” error.
So I just got a brand new droplet running Ubuntu 22.04, ran the install guide and it came up just fine. Can’t reproduce this issue in either an old or a new install.
What distro were you running?
> [@StanD](#):
>
> Do you see a `fatal: detected dubious ownership...` message in the unicorn log? I am getting this message.
Nothing like this in a brand new install:
```plaintext
root@test-install:/var/discourse# cat /var/discourse/shared/standalone/log/rails/unicorn.std*
I, [2023-08-22T17:16:33.594602 #2982] INFO -- : Refreshing Gem list
I, [2023-08-22T17:16:38.624384 #2982] INFO -- : listening on addr=127.0.0.1:3000 fd=10
I, [2023-08-22T17:16:43.003213 #2982] INFO -- : starting 1 supervised sidekiqs
I, [2023-08-22T17:16:47.070059 #2982] INFO -- : master process ready
I, [2023-08-22T17:16:50.490722 #3068] INFO -- : worker=0 ready
I, [2023-08-22T17:16:52.394685 #3077] INFO -- : worker=1 ready
I, [2023-08-22T17:16:53.139229 #3085] INFO -- : worker=2 ready
I, [2023-08-22T17:16:53.518292 #3097] INFO -- : worker=3 ready
Loading Sidekiq in process id 3059
```
[Next page](https://meta.discourse.org/t/argumenterror-directory-for-pid-unicorn-pid-not-writable/274948.md?page=2)