Stopped working , might be an acl or similar issues but cannot anything wrong (error: mv: cannot create regular file ...)

[SundudeDK]

Hi cannot pinpoint what is wrong, it has worked fine but stopped a few months ago and have not yet found the reason,

Anyone with some tips or knowledge of what is wrong

error message in docker

db-backup | 2025-05-25.16:13:12 [NOTICE] ** [01-10.5.4.251__all] Dumping MySQL/MariaDB database: 'USER_DB_NAME' and compressing with 'gzip'
db-backup | 2025-05-25.16:13:12 [INFO] ** [01-10.5.4.251__all] DB Backup of 'mariadb_USER_DB_NAME_10.5.4.251_20250525-161312.sql.gz' completed successfully
db-backup | 2025-05-25.16:13:12 [NOTICE] ** [01-10.5.4.251__all] Generating SHA1 sum for 'mariadb_USER_DB_NAME_10.5.4.251_20250525-161312.sql.gz'
db-backup | 2025-05-25.16:13:13 [NOTICE] ** [01-10.5.4.251__all] Backup of 'mariadb_USER_DB_NAME_10.5.4.251_20250525-161312.sql.gz' created with the size of 536 bytes
db-backup | mv: cannot create regular file '/backup/mariadb_USER_DB_NAME_10.5.4.251_20250525-161312.sql.gz.sha1': No such file or directory
db-backup | mv: cannot create regular file '/backup/mariadb_USER_DB_NAME_10.5.4.251_20250525-161312.sql.gz': No such file or directory
db-backup | ln: failed to create symbolic link '/backup/latest-mariadb_USER_DB_NAME_10.5.4.251': No such file or directory
db-backup | 2025-05-25.16:13:13 [ERROR] ** [01-10.5.4.251__all] Moving of backup 'mariadb_USER_DB_NAME_10.5.4.251_20250525-161312.sql.gz' reported errors

volume in docker mounted to a backup share /srv/filemerge/pool1/dockers/dbbackup:/backup
db-backup user created with id of 10000
db-backup group created with id of 10000

Outseems right
id db-backup
uid=10000(db-backup) gid=10000(db-backup) groups=10000(db-backup),1001(docker-rw)
access controls are set on the folder

running exec to the running container i can see the mount point and i can create a file or folder and it is accessible directly after makeing them in the docker image.
docker exec -it xxx1234 mkdir /backup/test
docker exec -it xxxx1234 touch /backup/test2

anyone with any fix/explanation??

Best Regards
jan

[SundudeDK]

Might have been solved, seems to be working right now.
Not sure but the mv: cannot create regular file disappeared or it might be due to the cleanup cycle?

Anyway again investigating a bit further i found out that the job changed some of the folder permissions to something that i did not work (dirs 700 and 600 for files). So my reasoning is these permissions was not allowing for changing the linked symbolic file .

pic.1 Correct working folder permission

pic2. incorrrect folder permissiong after running the backup job

pic3 correct working file permission

pic4 incorrect file permission

Looking thorgh the documentation i added the below to the docker compose file

I would suggest that these two paramerets are added the docker compose example ad optional parameters, would have save me some time as it used to work, and then (after an update?) it stopped to work.

In any case it would now always work the first time if the folder and file permission are high enough. Then when the backup job runs for the first time it will reset the folder and link file and any new backup job files will get possible incorrect permissions and the next backup might fail. Making it a bit hard to notice and fix.
/jan

[SundudeDK]

Might have been solved, seems to be working right now.
Not sure but the mv: cannot create regular file disappeared or it might be due to the cleanup cycle?

Anyway again investigating a bit further i found out that the job changed some of the folder permissions to something that i did not work (dirs 700 and 600 for files). So my reasoning is these permissions was not allowing for changing the linked symbolic file .

pic.1 Correct working folder permission

pic2. incorrrect folder permissiong after running the backup job

pic3 correct working file permission

pic4 incorrect file permission

Looking thorgh the documentation i added the below to the docker compose file

I would suggest that these two paramerets are added the docker compose example ad optional parameters, would have save me some time as it used to work, and then (after an update?) it stopped to work.

In any case it would now always work the first time if the folder and file permission are high enough. Then when the backup job runs for the first time it will reset the folder and link file and any new backup job files will get possible incorrect permissions and the next backup might fail. Making it a bit hard to notice and fix.
/jan