#Update to v11 on RPi

1 messages ยท Page 1 of 1 (latest)

distant swan
#

Creating a thread so we don't spam the channel. =)

cobalt osprey
distant swan
#

When I check the status I get this:

image.png
distant swan
#

Also when I try to start Foundry directly, without starting the service I get the following error:

image.png
floral anchorBOT
#
V11 Database glibc Workaround

In upgrading to the new database engine for v11, some devices may experience an error related to an invalid version of glibc. This most notably affects ARM architecture devices, including some models of Raspberry Pi.

Rebuilding The Database Engine Using A Local `glibc`

1. Shut down your currently hosted Foundry VTT server instance.
2. In a terminal, access the folder or directory where your Foundry VTT executable is located.
3. Access the resources/app/ subdirectory.
4. run npm install classic-level --build-from-source
5. Relaunch your Foundry VTT server following your normal procedure.

distant swan
#

Thanks, but that gives me an error. ๐Ÿค”

image.png
surreal cipher
#

How is the SD card where foundry is stored mounted?

distant swan
surreal cipher
#

Okay..how is that mounted?

distant swan
#

I'm not all that proficient with linux. Could you tell me how I find out?

#

This is the content of fstab if that helps.


proc            /proc           proc    defaults          0       0
PARTUUID=dfe37cac-01  /boot           vfat    defaults          0       2
PARTUUID=dfe37cac-02  /               ext4    defaults,noatime  0       1
# a swapfile is not a swap partition, no line here
#   use  dphys-swapfile swap[on|off]  for that
UUID=7ad7a4cb-81dc-4925-b9e8-914f25b02afe /mnt/foundryvtt ext4 defaults,auto,users,rw,nofail 0 0
surreal cipher
#

ls -la /mnt/foundryvtt

distant swan
surreal cipher
distant swan
surreal cipher
#

Hmm, what are the perms on /mnt/foundryvtt/App/resources/app/?

distant swan
surreal cipher
#

Hmyea, not quite sure what permission issue it has though now

distant swan
surreal cipher
#

Could be a try at least ๐Ÿคท

#

I'm also not quite sure why store the Foundry app inside the userdata folder, but that shouldn't be the cause for this particular issue anyway, it's just..unconvential I guess

distant swan
#

In the end, if there would be need to install everything fresh and clean, I can do it the conventional way. But I'd need a lot of help for that. Setting this thing up initially was quite the ordeal for me. I am not able to do anything on linux on my own. :-S

cobalt osprey
#

That's why we have the guide I linked to at the start of this thread ๐Ÿ™‚

surreal cipher
distant swan
surreal cipher
#

What's the pi image you used?

distant swan
surreal cipher
#

Was it the 32bit image and what Pi model is it?

distant swan
#

I can't remember whether it was 32 of 64 bit, I'm sorry. But it's a raspberry pi 4.
Initially it was a 3 but when I updated to v10 I was running out of RAM and bought a 4 in which I put the SD card from the 3.

surreal cipher
#

If it's the 32 bit image you'll unfortunately have to reinstall the base os

#

But also..porting the SD card from a different model..isn't exactly a great idea..

distant swan
surreal cipher
#

ยฏ_(ใƒ„)_/ยฏ

distant swan
surreal cipher
distant swan
surreal cipher
#

Did you clear out the old installation first?

#

Delete old application folder, copy new application folder from SD card

#

Check if that works

distant swan
#

Because it was quicker than typing I moved it to the wastebasket with a mouse on the pi but yes.

surreal cipher
#

Then I don't know

distant swan
#

Might be a stupid question, but wouldn't it be possible to just change all references to the old foundry app location to the new one but keep using the old data folder and pretend foundry has always been where it is on the SD card? ๐Ÿ™ˆ

surreal cipher
#

Naturally

distant swan
#

Okay so, I guess I'll need to figure out what all referenced the old app path to the HDD. the systemctl service comes to mind of course. But what about nginx and the ssl cert? Do I need to change anything there?

surreal cipher
distant swan
surreal cipher
#

Yes

distant swan
#

Okay, I'll try that and see if that works.
Also: I didn't say it yet, but I'm incredibly grateful for your time and effort. Thank you so much. ๐Ÿ’™

surreal cipher
distant swan
surreal cipher
#

Going by the log you posted earlier

#

But yea, if it works thats fine too

distant swan
#

Great, so finally this is settled, Thank you so much. =)

distant swan
# surreal cipher But yea, if it works thats fine too

I'm afraid it's not all good yet. ๐Ÿค”
When I try to update modules and systems, I get a load of timed out errors.. And I've checked on my local installation of foundry, I can update the same packages there no problem. :-S

#

Some few packages update but the vast majority does not.

surreal cipher
#

Possible you're running into rate limiting

distant swan
surreal cipher
#

How many packages are installed in total?>

#

Roughly

distant swan
surreal cipher
#

5, 50, 500?

#

Yea

#

Update them individually, chances are you are being rate limited due to running to many checks at the same time by Github/Gitlab

#

Or your network is funky, or your install is fucked up because you transplanted SD cards between pi models, or who knows..

distant swan
#

Even individually, it's rare I get it updated. :-S

surreal cipher
#

What are the full errors you are getting? Check in the console

distant swan
#

Here are a couple:

image.png
surreal cipher
#

And is the listed URL openable from the pi itself?

distant swan
surreal cipher
#

curl -v <the url> for example

distant swan
surreal cipher
#

add -v as above

#

But generally there should be content in the reply

distant swan
surreal cipher
#

Oh right, Github

#

curl -vL <url>

distant swan
surreal cipher
#

Well, no idea then

#

That's the right manifest

#

Either you're still rate-limited through Foundry, didn't properly remove the old foundry installation and replaced it with a new one or something else entirely is still broken somewhere, considering the more than questionable history of this entire Pi installation

distant swan
surreal cipher
#

I mean, you are now not running of the HDD because you installed to the SD card

#

So..no idea what was there before and if you did delete and replace there

#

I would strongly suggest to reinstall the entire Pi at this point, especially since you transplanted the SD card from an older model

distant swan
#

BTW: Whenever I try to update a single package and do get a timed out error, it shows me that one twice:

image.png
distant swan
surreal cipher
#

If you truly feel that way, there's always hosting through the Foundry app or hosting providers you can turn to

distant swan
surreal cipher
#

That's fair enough. Those could also be options of course, especially caring for yourself is important in any case.

distant swan
brazen ember
#

If you had a pi 3 and are using the same image that was running on the 3 then you're using a 32bit

brazen ember
#

Just got caught up on the thread here

distant swan
brazen ember
#

I'd start with removing your v11 app folder completely, then downloading a new zip and extracting v11 again. You'll have to rebuild levels again though

distant swan
brazen ember
distant swan
brazen ember
#

Did you download a new copy when you did it before or did you use the existing zip?

#

Did you also check your node version yet? node -v

distant swan
distant swan
brazen ember
#

If that zip is no good and you've reinstall it 10 times using it, then you're just reinstalling the same problem over and over

distant swan
brazen ember
#

Generally the zip is fine, but if you downlaoded 11.313 and it's showing 11.308 clearly there was a problem

#

It also looks like your service is running node from /usr/bin/node can you quicky do /usr/bin/node -v just to make sure you don't have two node versions installed

distant swan
brazen ember
#

That happens sometimes when you update node via nvm. How did you update node?

distant swan
#

Here's the service:

image.png
#

And that screenshot I took yesterday:

image.png
#

That's how I updated node

brazen ember
#

You can update your service to ExecStart=/usr/local/bin/node ...

#

which will load the correct node

#

has the machine been rebooted since you updated?

distant swan
distant swan
brazen ember
#

Updating the path to the correct node version will have it load foundry with the correct node

#

Honestly from what I read of your thread here I would make a backup of your user data folder. Reinstall rasbian with the 64 bit version and then do a completely fresh v11 install and restore your backup

#

There is a fairly good chance just update your service to load the correct node will make things work though

distant swan
brazen ember
#

instead of ExecStart=node ... you do ExecStart=/usr/local/bin/node ...

distant swan
brazen ember
#

Then it loads the correct version of node. Alterniatively. Uninstall node via apt, and install it correctly via apt

distant swan
distant swan
brazen ember
#

To redepoy raspbian someone would need physical access to your pi. It's not something anyone is going to be able to do for you. Once you've got the current version of raspian things are as easy as following the gude we have

#

sudo apt remove nodejs npm

#

and sudo rm -rf /usr/local/bin/node*

#

That will completely remove node and npm

#

Probably run sudo apt-get purge nodejs for good measure after the other two

distant swan
brazen ember
#

Once it's removed do the following

sudo apt update
sudo apt upgrade -y

sudo apt install -y ca-certificates curl gnupg
sudo mkdir -p /etc/apt/keyrings
curl -fsSL https://deb.nodesource.com/gpgkey/nodesource-repo.gpg.key | sudo gpg --dearmor -o /etc/apt/keyrings/nodesource.gpg
echo "deb [signed-by=/etc/apt/keyrings/nodesource.gpg] https://deb.nodesource.com/node_18.x nodistro main" | sudo tee /etc/apt/sources.list.d/nodesource.list

sudo apt update
sudo apt install nodejs -y
distant swan
brazen ember
#

Your choice. Iโ€™d run it one at a time in your case

#

It is possible node 20 wont install on 32 bit raspbian actually

#

lets change it to 18

distant swan
distant swan
brazen ember
#

Cool looks like node20 went. Give node -v a go and see what it outputs

distant swan
distant swan
brazen ember
#

The commands I have you are directly out of the guide

#

Go ahead and reboot the pi

distant swan
brazen ember
# distant swan After reboot:

That's because you're running an outdated version of raspian. Going to need to remove node20 and install node18 which is what I was worried about

#

Do you need the commands to remove it again?

distant swan
brazen ember
distant swan
brazen ember
#

echo "deb [signed-by=/etc/apt/keyrings/nodesource.gpg] https://deb.nodesource.com/node_18.x nodistro main" | sudo tee /etc/apt/sources.list.d/nodesource.list

#

sudo apt update

#

sudo apt install nodejs -y

distant swan
#

Now, reboot and node -v? ^^

brazen ember
#

node -v should work without the reboot

distant swan
#

indeed

image.png
brazen ember
#

go ahead and reboot and it should start your foundry

distant swan
#

Would you look at that:

image.png
#

Still timed out errors though. XD

brazen ember
#

On the updates?

distant swan
#

yeah

brazen ember
#

Try doing one at a time

distant swan
#

I just did. Only tried a single system so far.

brazen ember
#

Try a different one?

distant swan
#

Same thing, slightly more context:

image.png
brazen ember
#

back in the terminal run which node

distant swan
brazen ember
#

if you press f12 in the foundry window and look at the console tab. Does it give anymore details around the red errors?

distant swan
brazen ember
#

No other red errors?

#

I would still go back and download a new zip and reinstall that way as we discussed before because of your issue with it report 308 previously

#

It may fix the download issue

distant swan
#

That is all I'm afraid. The warnings are to be expected.

image.png
brazen ember
#

I'm at a bit of a loss otherwise

#

I have to step away now as I need to get my kids ready for school

distant swan
distant swan
# brazen ember I'm at a bit of a loss otherwise

FYI: After updating Foundry there are still many timed out errors but certainly less than before. I could update aprox. 10-20% of the modules. The rest still timed out. But it's somewhat of an improvement. XD
But I'm afraid you're all right. I probably have to set the whole thing up again. - Perfectly understandable if you'd decline but if you'd like to help me through the guide in a few days, help me interpret the results, and guide me towards functionality, That'd be great. =)

surreal cipher
#

There'll likely be someone around to help you through the guide