### Author:  [@gmoirod](https://meta.discourse.org/u/gmoirod)
#### Post date: [June 18, 2023, 5:05pm UTC](https://meta.discourse.org/t/problems-while-updating-from-3-0-3-to-3-0-4-error-523/268815/1 "2023-06-18T17:05:15Z")
Hey there !
I run into an issue while trying to upgrade my install with `launcher` utility.
I get an error 523 when the build container try to change ownership on uploaded images…
Any thought ?
Here is the log :
```plaintext
$ sudo ./launcher rebuild app
x86_64 arch detected.
WARNING: containers/app.yml file is world-readable. You can secure this file by running: chmod o-rwx containers/app.yml
Ensuring launcher is up to date
Fetching origin
Launcher is up-to-date
Stopping old container
+ /usr/bin/docker stop -t 600 app
app
2.0.20230502-0058: Pulling from discourse/base
Digest: sha256:fa95da36c3d3a582d644b139ec678f5778d745697454bc86f598c689031b30aa
Status: Image is up to date for discourse/base:2.0.20230502-0058
docker.io/discourse/base:2.0.20230502-0058
/usr/local/lib/ruby/gems/3.2.0/gems/pups-1.1.1/lib/pups.rb
/usr/local/bin/pups --stdin
.....
Switched to a new branch 'stable'
I, [2023-06-18T16:43:24.458070 #1] INFO -- : Branch 'stable' set up to track remote branch 'stable' from 'origin'.
I, [2023-06-18T16:43:24.458386 #1] INFO -- : > cd /var/www/discourse && sudo -H -E -u discourse git config user.discourse-version stable
I, [2023-06-18T16:43:24.469320 #1] INFO -- :
I, [2023-06-18T16:43:24.469386 #1] INFO -- : > cd /var/www/discourse && mkdir -p tmp
I, [2023-06-18T16:43:24.472481 #1] INFO -- :
I, [2023-06-18T16:43:24.472660 #1] INFO -- : > cd /var/www/discourse && chown discourse:www-data tmp
I, [2023-06-18T16:43:24.476232 #1] INFO -- :
I, [2023-06-18T16:43:24.476303 #1] INFO -- : > cd /var/www/discourse && mkdir -p tmp/pids
I, [2023-06-18T16:43:24.479386 #1] INFO -- :
I, [2023-06-18T16:43:24.479449 #1] INFO -- : > cd /var/www/discourse && mkdir -p tmp/sockets
I, [2023-06-18T16:43:24.482943 #1] INFO -- :
I, [2023-06-18T16:43:24.483012 #1] INFO -- : > cd /var/www/discourse && touch tmp/.gitkeep
I, [2023-06-18T16:43:24.486152 #1] INFO -- :
I, [2023-06-18T16:43:24.486220 #1] INFO -- : > cd /var/www/discourse && mkdir -p /shared/log/rails
I, [2023-06-18T16:43:24.489788 #1] INFO -- :
I, [2023-06-18T16:43:24.489954 #1] INFO -- : > cd /var/www/discourse && bash -c "touch -a /shared/log/rails/{production,production_errors,unicorn.stdout,unicorn.stderr,sidekiq}.log"
I, [2023-06-18T16:43:24.495214 #1] INFO -- :
I, [2023-06-18T16:43:24.495285 #1] INFO -- : > cd /var/www/discourse && bash -c "ln -s /shared/log/rails/{production,production_errors,unicorn.stdout,unicorn.stderr,sidekiq}.log /var/www/discourse/log"
I, [2023-06-18T16:43:24.500211 #1] INFO -- :
I, [2023-06-18T16:43:24.500283 #1] INFO -- : > cd /var/www/discourse && bash -c "mkdir -p /shared/{uploads,backups}"
I, [2023-06-18T16:43:24.504652 #1] INFO -- :
I, [2023-06-18T16:43:24.504738 #1] INFO -- : > cd /var/www/discourse && bash -c "ln -s /shared/{uploads,backups} /var/www/discourse/public"
I, [2023-06-18T16:43:24.512836 #1] INFO -- :
I, [2023-06-18T16:43:24.512942 #1] INFO -- : > cd /var/www/discourse && bash -c "mkdir -p /shared/tmp/{backups,restores}"
I, [2023-06-18T16:43:24.518383 #1] INFO -- :
I, [2023-06-18T16:43:24.518453 #1] INFO -- : > cd /var/www/discourse && bash -c "ln -s /shared/tmp/{backups,restores} /var/www/discourse/tmp"
I, [2023-06-18T16:43:24.523090 #1] INFO -- :
I, [2023-06-18T16:43:24.523195 #1] INFO -- : > cd /var/www/discourse && chown -R discourse:www-data /shared/log/rails /shared/uploads /shared/backups /shared/tmp
chown: /shared/uploads/default/optimized/1X: Unknown error 523
chown: /shared/uploads/default/original/1X: Unknown error 523
I, [2023-06-18T16:43:41.385629 #1] INFO -- :
FAILED
--------------------
Pups::ExecError: cd /var/www/discourse && chown -R discourse:www-data /shared/log/rails /shared/uploads /shared/backups /shared/tmp failed with return #
Location of failure: /usr/local/lib/ruby/gems/3.2.0/gems/pups-1.1.1/lib/pups/exec_command.rb:117:in `spawn'
exec failed with the params {"cd"=>"$home", "hook"=>"code", "cmd"=>["sudo -H -E -u discourse git reset --hard", "sudo -H -E -u discourse git clean -f", "sudo -H -E -u discourse bash -c '\n set -o errexit\n if [$(git rev-parse --is-shallow-repository) == \"true\"]; then\n git remote set-branches --add origin main\n git remote set-branches origin $version\n git fetch --depth 1 origin $version\n else\n git fetch --tags --prune-tags --prune --force origin\n fi\n'", "sudo -H -E -u discourse bash -c '\n set -o errexit\n if [[$(git symbolic-ref --short HEAD) == $version]] ; then\n git pull\n else\n git -c advice.detachedHead=false checkout $version\n fi\n'", "sudo -H -E -u discourse git config user.discourse-version $version", "mkdir -p tmp", "chown discourse:www-data tmp", "mkdir -p tmp/pids", "mkdir -p tmp/sockets", "touch tmp/.gitkeep", "mkdir -p /shared/log/rails", "bash -c \"touch -a /shared/log/rails/{production,production_errors,unicorn.stdout,unicorn.stderr,sidekiq}.log\"", "bash -c \"ln -s /shared/log/rails/{production,production_errors,unicorn.stdout,unicorn.stderr,sidekiq}.log $home/log\"", "bash -c \"mkdir -p /shared/{uploads,backups}\"", "bash -c \"ln -s /shared/{uploads,backups} $home/public\"", "bash -c \"mkdir -p /shared/tmp/{backups,restores}\"", "bash -c \"ln -s /shared/tmp/{backups,restores} $home/tmp\"", "chown -R discourse:www-data /shared/log/rails /shared/uploads /shared/backups /shared/tmp", "[! -d public/plugins] || find public/plugins/ -maxdepth 1 -xtype l -delete"]}
bootstrap failed with exit code 1
**FAILED TO BOOTSTRAP** please scroll up and look for earlier error messages, there may be more than one.
./discourse-doctor may help diagnose the problem.
```
---
### Author:  [@Ed\_S](https://meta.discourse.org/u/Ed_S)
#### Post date: [June 20, 2023, 7:57am UTC](https://meta.discourse.org/t/problems-while-updating-from-3-0-3-to-3-0-4-error-523/268815/2 "2023-06-20T07:57:53Z")
> [@gmoirod](#):
>
> `Unknown error 523`
I can’t find anything useful about this error. What is your OS distribution and version? What kind of storage is in use for uploads?
I hope you already know that using the ‘stable’ track is an unusual tactic - almost everyone runs the ‘tests-passed’ track. See
[Why does Discourse always install “beta” versions by default?](https://meta.discourse.org/t/why-does-discourse-always-install-beta-versions-by-default/264400)
---
### Author:  [@RGJ](https://meta.discourse.org/u/RGJ)
#### Post date: [June 20, 2023, 8:00am UTC](https://meta.discourse.org/t/problems-while-updating-from-3-0-3-to-3-0-4-error-523/268815/3 "2023-06-20T08:00:56Z")
Are you using S3 and if so, is the name of your bucket configured correctly?
> [@Ed\_S](#):
>
> an unusual tactic
But it should not fail _more_, so this is irrelevant IMO?
---
### Author:  [@Ed\_S](https://meta.discourse.org/u/Ed_S)
#### Post date: [June 20, 2023, 11:34am UTC](https://meta.discourse.org/t/problems-while-updating-from-3-0-3-to-3-0-4-error-523/268815/4 "2023-06-20T11:34:06Z")
> [@RGJ](#):
>
> But it should not fail _more_
It might be seen to fail less, if very few installations use stable. Also, I wanted to sure @gmoirod was aware of the situation - guessing that some people who run stable are running it without knowing what it is.
---
### Author:  [@RGJ](https://meta.discourse.org/u/RGJ)
#### Post date: [June 20, 2023, 11:54am UTC](https://meta.discourse.org/t/problems-while-updating-from-3-0-3-to-3-0-4-error-523/268815/5 "2023-06-20T11:54:23Z")
I get that. But if his install is failing right now then my estimate is that jumping to 3.1.0beta5 will make it much worse. So let’s focus on the issue first.
---
### Author:  [@gmoirod](https://meta.discourse.org/u/gmoirod)
#### Post date: [June 20, 2023, 11:57am UTC](https://meta.discourse.org/t/problems-while-updating-from-3-0-3-to-3-0-4-error-523/268815/6 "2023-06-20T11:57:04Z")
> [@Ed\_S](#):
>
> I can’t find anything useful about this error. What is your OS distribution and version? What kind of storage is in use for uploads?
I run Discourse as docker containers on top of Debian 11 server.
My uploads are on a shared NFS mount. This has always been the case and I never had this issue before.
> [@Ed\_S](#):
>
> I hope you already know that using the ‘stable’ track is an unusual tactic - almost everyone runs the ‘tests-passed’ track
Yeah I saw several things on this… I have to go for it one day…
I am kind of a Debian guy you know. Keep “stable” for production.
---
### Author:  [@RGJ](https://meta.discourse.org/u/RGJ)
#### Post date: [June 20, 2023, 11:59am UTC](https://meta.discourse.org/t/problems-while-updating-from-3-0-3-to-3-0-4-error-523/268815/7 "2023-06-20T11:59:23Z")
> [@gmoirod](#):
>
> My uploads are on a shared NFS mount.
There you have it. And is that mount currently accessible from within the container?
---
### Author:  [@gmoirod](https://meta.discourse.org/u/gmoirod)
#### Post date: [June 20, 2023, 8:15pm UTC](https://meta.discourse.org/t/problems-while-updating-from-3-0-3-to-3-0-4-error-523/268815/8 "2023-06-20T20:15:17Z")
> [@RGJ](#):
>
> There you have it. And is that mount currently accessible from within the container?
My actual running Discourse 3.0.3 container :
```plaintext
{
"Type": "bind",
"Source": "/nfsdata/discourse-data-shared/uploads",
"Destination": "/shared/uploads",
"Mode": "",
"RW": true,
"Propagation": "rprivate"
},
```
Within the container, ownerships and rights seem good
```plaintext
$ sudo docker exec app sh -c "ls -al /shared/uploads /shared/uploads/default/optimized/1X /shared/uploads/default/original/1X"
/shared/uploads:
total 4
drwxr-xr-x 2 discourse www-data 0 Jun 20 20:07 .
drwxr-xr-x 10 root root 4096 Mar 8 16:29 ..
drwxr-xr-x 2 discourse www-data 0 Jun 8 2022 default
drwxr-xr-x 2 discourse www-data 0 Mar 8 17:34 tombstone
/shared/uploads/default/optimized/1X:
total 17094
drwxr-xr-x 2 discourse www-data 0 Mar 22 11:30 .
drwxr-xr-x 2 discourse www-data 0 Mar 8 16:18 ..
-rw-r--r-- 1 discourse www-data 54700 Mar 8 16:52 00964701d199ec0d6d3dd5269c842e1f0bb7e7a1_2_1035x456.png
-rw-r--r-- 1 discourse www-data 205 Mar 8 16:52 00964701d199ec0d6d3dd5269c842e1f0bb7e7a1_2_10x10.png
.....
/shared/uploads/default/original/1X:
total 17932
drwxr-xr-x 2 discourse www-data 0 Apr 23 11:42 .
drwxr-xr-x 2 discourse www-data 0 Jun 8 2022 ..
-rw-r--r-- 1 discourse www-data 35706 Nov 18 2022 00964701d199ec0d6d3dd5269c842e1f0bb7e7a1.png
-rwxr-xr-x 1 discourse www-data 17112 Jul 4 2022 00a82b03ffbcdf56e34f86adbec263e12573f49b.png
```
Moreover, I am able to upload new images in running Discourse 3.0.3
---
### Author:  [@gmoirod](https://meta.discourse.org/u/gmoirod)
#### Post date: [June 20, 2023, 8:23pm UTC](https://meta.discourse.org/t/problems-while-updating-from-3-0-3-to-3-0-4-error-523/268815/9 "2023-06-20T20:23:43Z")
Precision : I do not have SELinux/AppArmor activated
---
### Author:  [@gmoirod](https://meta.discourse.org/u/gmoirod)
#### Post date: [June 20, 2023, 8:30pm UTC](https://meta.discourse.org/t/problems-while-updating-from-3-0-3-to-3-0-4-error-523/268815/10 "2023-06-20T20:30:36Z")
Hoping this is not related 😭 [I Challenge Thee](https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=102728)
> Actually, this isn’t a problem with the repository on NFS. It’s a problem
> with NFS-mounted CLIENT dir.
>
> The problem turned out to be an NFS bug in the Linux kernel, so you can
> probably close this bug.
---
### Author:  [@RGJ](https://meta.discourse.org/u/RGJ)
#### Post date: [June 20, 2023, 8:45pm UTC](https://meta.discourse.org/t/problems-while-updating-from-3-0-3-to-3-0-4-error-523/268815/11 "2023-06-20T20:45:21Z")
That something is the top result in Google does not mean it’s the best result.
> Date: Thu, 28 Jun 2001 20:03:01 UTC
Are you able to `chown ` from within the container, i.e. run the failing command manually?
`sudo docker exec app sh -c "chown -R discourse:discourse /shared/uploads/default/optimized/1X"`
---
### Author:  [@gmoirod](https://meta.discourse.org/u/gmoirod)
#### Post date: [June 22, 2023, 8:13pm UTC](https://meta.discourse.org/t/problems-while-updating-from-3-0-3-to-3-0-4-error-523/268815/12 "2023-06-22T20:13:50Z")
> [@RGJ](#):
>
> Are you able to `chown ` from within the container, i.e. run the failing command manually?
I am afraid I can (I corrected the command as the one executed initially) …
```plaintext
$ docker exec -it app bash
app:/$ cd /var/www/discourse
app:/var/www/discourse$ chown -R discourse:www-data /shared/uploads
app:/var/www/discourse$ echo $?
0
```
Took a long time but no error.
Is there any difference in the docker image running in 3.0.3 and the one used to build image in 3.0.4 ?
---
### Author:  [@RGJ](https://meta.discourse.org/u/RGJ)
#### Post date: [June 22, 2023, 8:15pm UTC](https://meta.discourse.org/t/problems-while-updating-from-3-0-3-to-3-0-4-error-523/268815/13 "2023-06-22T20:15:55Z")
> [@gmoirod](#):
>
> Is there any difference in the docker image running in 3.0.3 and the one used to build image in 3.0.4 ?
Docker image versions are not tied to Discourse versions. Additionally, it depends on how you rebuilt before, so it’s hard to say.
---
### Author:  [@gmoirod](https://meta.discourse.org/u/gmoirod)
#### Post date: [June 22, 2023, 8:22pm UTC](https://meta.discourse.org/t/problems-while-updating-from-3-0-3-to-3-0-4-error-523/268815/14 "2023-06-22T20:22:50Z")
My actual 3.0.3 image gives me
```plaintext
# docker image inspect local_discourse/app | grep 'discourse/base'
"Image": "discourse/base:2.0.20230409-0052",
```
And the one in error used :
```plaintext
Status: Image is up to date for discourse/base:2.0.20230502-0058
```
I’m gonna check diff 🔍
---
### Author:  [@gmoirod](https://meta.discourse.org/u/gmoirod)
#### Post date: [June 22, 2023, 8:37pm UTC](https://meta.discourse.org/t/problems-while-updating-from-3-0-3-to-3-0-4-error-523/268815/15 "2023-06-22T20:37:11Z")
> [@gmoirod](#):
>
> I’m gonna check diff 🔍
Damned !
I can’t see anything related : [Comparing 3d317b7f58e8201912972afa3910b6c4b9ad8c75...main · discourse/discourse\_docker · GitHub](https://github.com/discourse/discourse_docker/compare/3d317b7f58e8201912972afa3910b6c4b9ad8c75...main)
---
### Author:  [@gmoirod](https://meta.discourse.org/u/gmoirod)
#### Post date: [June 22, 2023, 9:12pm UTC](https://meta.discourse.org/t/problems-while-updating-from-3-0-3-to-3-0-4-error-523/268815/16 "2023-06-22T21:12:56Z")
Okay there is definitely an issue with base image.
I forced the use of discourse/base:2.0.20230409-0052 in launcher and it worked like a charm.
```plaintext
# git diff launcher
diff --git a/launcher b/launcher
index 3e1a1c4..8a989b8 100755
--- a/launcher
+++ b/launcher
@@ -92,7 +92,7 @@ kernel_min_version='4.4.0'
config_file=containers/"$config".yml
cidbootstrap=cids/"$config"_bootstrap.cid
local_discourse=local_discourse
-image="discourse/base:2.0.20230502-0058"
+image="discourse/base:2.0.20230409-0052"
docker_path=`which docker.io 2> /dev/null || which docker`
git_path=`which git`
```
Anybody can see the change causing this ?
---
### Author:  [@gmoirod](https://meta.discourse.org/u/gmoirod)
#### Post date: [June 23, 2023, 2:35pm UTC](https://meta.discourse.org/t/problems-while-updating-from-3-0-3-to-3-0-4-error-523/268815/17 "2023-06-23T14:35:58Z")
Believe or not, I just rebuilded again with discourse/base:2.0.20230502-0058 and it passed… 🤷♂️
---
### Author:  [@Canapin](https://meta.discourse.org/u/Canapin)
#### Post date: [June 23, 2023, 3:11pm UTC](https://meta.discourse.org/t/problems-while-updating-from-3-0-3-to-3-0-4-error-523/268815/18 "2023-06-23T15:11:59Z")
> [@gmoirod](#):
>
> Believe or not
No trouble believing in computer shenanigans 🙃
---
### Author:  [@system](https://meta.discourse.org/u/system)
#### Post date: [December 6, 2023, 10:38am UTC](https://meta.discourse.org/t/problems-while-updating-from-3-0-3-to-3-0-4-error-523/268815/19 "2023-12-06T10:38:19Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.