2.2.4 logo_inline.svg

[CPCFenrir]

Good morning,

First of all thank you for maintaining this project!!!

I encountered this error message after installing the latest version:

Error - 500 Oooops, Something went wrong! You have experienced a technical error. We apologize.

Status: 'Internal Server Error' Message: Unable to open img/v2.2.4/svg/logo_inline.svg

best regards,

[TyrHeimdalEVE]

Hmmm, this should work if you updated correctly.

I don't see any issues related to the path here and https://github.com/goryn-clade/pathfinder/blob/v2.2.4/public/img/v2.2.4/svg/logo_inline.svg is most certainly available in the release.

Please re-open if you're still having issues.

[CPCFenrir]

Hi TyrHeimdalEve,

thank you for your quick reply !!

I made a backup of my db and started from 0. Same problem :/

best regards,

[TyrHeimdalEVE]

Checked the image:

bash-4.4# stat img/v2.2.4/svg/logo_inline.svg
  File: img/v2.2.4/svg/logo_inline.svg
  Size: 2885            Blocks: 8          IO Block: 4096   regular file
Device: 43h/67d Inode: 190859406   Links: 1
Access: (0644/-rw-r--r--)  Uid: (65534/  nobody)   Gid: (65534/  nobody)
Access: 2024-04-01 03:06:13.000000000
Modify: 2024-04-01 03:06:13.000000000
Change: 2024-04-03 06:47:29.000000000

The file is most certainly there. What exactly did you do to upgrade?

It sounds like you are somehow running the wrong image.

[CPCFenrir]

Hi Tyr,

First i try a general update, using the wiki.

1. Backup the database
2. Pull the latest version and rebuild my containers: docker-compose down git stash git pull --recurse-submodules git stash apply docker-compose up -d --build => Error 500 occurs Status: 'Internal Server Error' Message: Unable to open img/v2.2.4/svg/logo_inline.svg

therefore I stopped docker. do an rm of the files. and then I re-downloaded the complete file via:

git clone --recurse-submodules https://github.com/goryn-clade/pathfinder-containers.git

I did a complete installation, but I still have this problem opening the image :/

best regards,

[TyrHeimdalEVE]

Sorry for the late reply here, could you try rebuilding with the --no-cache option?

Also please post your docker-compose.yml file as well (remove anything sensitive, if applicable).

[CPCFenrir]

Hi Tyr,

Thanks for reply !!

i try : docker-compose up -d --no-cache docker-compose prune etc... same issue :/

I tried to start from a new installation but I think that's the problem... I use rm -r pathfinder-containers I think that’s not enough?

i use the docker container version of pathfinder

Regards,

[tomaswest]

docker pull ghcr.io/goryn-clade/pathfinder:latest docker pull ghcr.io/goryn-clade/pf-websocket:latest then restart your containers

[TyrHeimdalEVE]

Yes that is what I was suspecting was the root cause.

But the better way would be: docker compose up -d --pull always ... to ensure that no image is outdated.

[CPCFenrir]

docker pull ghcr.io/goryn-clade/pathfinder:latest docker pull ghcr.io/goryn-clade/pf-websocket:latest then restart your containers

Thanks you soo much tomaswest !!! It's work :1st_place_medal: