Unexpected errors regarding access

[raduman]

Hi,

After forcefully removing the docker proxy records I get the following batch of errors (obviously I have checked the access rights on the folders...
11534338 drwxr-xr-x 2 user user 4096 dec 20 10:43 yams
14549082 drwxr-xr-x 7 user user 4096 dec 15 11:55 media

The errors:

ERROR: for prowlarr Cannot start service prowlarr: error while creating mount source path '/opt/yams/config/prowlarr': mkdir /opt/yams: read-only file system
Starting readarr ... error
Starting gluetun ... error

ERROR: for bazarr Cannot start service bazarr: error while creating mount source path '/opt/yams/config/bazarr': mkdir /opt/yams: read-only file system

Starting lidarr ... error
Starting jellyfin ... error
ERROR: for lidarr Cannot start service lidarr: error while creating mount source path '/srv/media/downloads': mkdir /srv/media: read-only file system

ERROR: for jellyfin Cannot start service jellyfin: error while creating mount source path '/opt/yams/config/jellyfin': mkdir /opt/yams: read-only file system

ERROR: for gluetun Cannot start service gluetun: error while creating mount source path '/opt/yams/config/gluetun': mkdir /opt/yams: read-only file system

ERROR: for sonarr Cannot start service sonarr: error while creating mount source path '/srv/media/downloads': mkdir /srv/media: read-only file system

ERROR: for radarr Cannot start service radarr: error while creating mount source path '/opt/yams/config/radarr': mkdir /opt/yams: read-only file system

ERROR: for prowlarr Cannot start service prowlarr: error while creating mount source path '/opt/yams/config/prowlarr': mkdir /opt/yams: read-only file system

ERROR: for portainer Cannot start service portainer: error while creating mount source path '/opt/yams/config/portainer': mkdir /opt/yams: read-only file system

ERROR: for bazarr Cannot start service bazarr: error while creating mount source path '/opt/yams/config/bazarr': mkdir /opt/yams: read-only file system

ERROR: for readarr Cannot start service readarr: error while creating mount source path '/srv/media/books': mkdir /srv/media: read-only file system

ERROR: for lidarr Cannot start service lidarr: error while creating mount source path '/srv/media/downloads': mkdir /srv/media: read-only file system

ERROR: for jellyfin Cannot start service jellyfin: error while creating mount source path '/opt/yams/config/jellyfin': mkdir /opt/yams: read-only file system

ERROR: for gluetun Cannot start service gluetun: error while creating mount source path '/opt/yams/config/gluetun': mkdir /opt/yams: read-only file system
ERROR: Encountered errors while bringing up the project.

[rogs]

Hey @raduman!

I'm missing some information. Where are you trying to install YAMS? A SMB/NFS share? That doesn't look like a normal install location (eg: /opt/yams/)

[raduman]

Hey, thanks for your reply!

The folders are local. I have copy pasted just the permissions rows...

[rogs]

You still haven't said where are you installing it to.

According to the error, it appears the drive you are installing it to is read only. Can you write to those locations?

[raduman]

I want to install it locally. First time it went through, but it throwed errors because ports were in use. Since then I was not able to install it through again...

Yes, I can write to these locations under my own username...

df -h
Filesystem Size Used Avail Use% Mounted on
tmpfs 373M 2,1M 371M 1% /run
/dev/mapper/vgubuntu-root 230G 43G 176G 20% /
tmpfs 1,9G 0 1,9G 0% /dev/shm
tmpfs 5,0M 4,0K 5,0M 1% /run/lock
/dev/sda1 511M 30M 482M 6% /boot/efi
tmpfs 373M 80K 373M 1% /run/user/128
tmpfs 373M 68K 373M 1% /run/user/1000

[rogs]

Just to be clear, that is not what I'm asking for. Please, answer this questions:

• Where are you trying to install YAMS? Give me the full route
• Is it an external USB drive or a NFS/SMB share?
• Can you perform any operations on that location? (Create a file, read it, delete it)

I won't answer more questions if you don't answer any of mine. So far you haven't given me any info to go on.

And please, use code blocks if you can. Reading logs in a non monospaced block is really difficult

[raduman]

OK, sorry, but I believe there is a misunderstanding here

I am trying to install locally, on /opt/yams, where the installation was performed successfully in a first attempt where the error returned was about already used ports. So yes, the installer COULD write there before and I don't understand why it cannot write now.

There are NO external drives involved in this installations. None whatsoever. There is nothing mounted there.

I can write, rename, delete in that folder.

[rogs]

Ok, it is more clear now.

Delete the /opt/yams directory and try again.

Code: Select all

sudo rm -rf /opt/yams
sudo mkdir /opt/yams
sudo chown $USER:$USER /opt/yams

I just noticed something:

Code: Select all

11534338 drwxr-xr-x 2 user user 4096 dec 20 10:43 yams
14549082 drwxr-xr-x 7 user user 4096 dec 15 11:55 media

Is your user called "user" or did you change it for privacy?

[raduman]

the user is not user. I have changed it, indeed

thanks for your time and your help!

[raduman]

Nice going... file was copied successfully, then it says no such file or directory...

Copying docker-compose.example.yaml to /opt/yams/docker-compose.yaml...
docker-compose.example.yaml was copied successfuly!

Copying .env.example to /opt/yams/.env...
.env.example was copied successfuly!

Copying docker-compose.custom.yaml to /opt/yams/docker-compose.custom.yaml...
docker-compose.custom.yaml was copied successfuly!
Everything installed correctly!
Running the server...
This is going to take a while...
stat /opt/yams/docker-compose.yaml: no such file or directory

I think I will abandon this project, it takes too long to debug. Or I will reinstall the Ubuntu server when I will have more time...