Filerun auto logout silently while scrolling through photos
Open a folder with 500-600 photos.
Set view mode to photos.
Scroll through the nice thumbnail overview and notice at some point the thumbnails stop loading and a notification on the bottom is shown " you are no longer logged in". This happens constantly now, making it impossible to make my way through folders with lots of photos. I haven't even reached the bottom of page 1 of a folder yet.
I did not change my configuration, did not do a reinstall (using docker). I don't know why I never had this issue before.
I was waiting for the new update before using Filerun this much but now I can't wait. This issue combined with the webdav issues are really blocking me in going through my personal photos.
Activity log shows nothing interesting but SQL error log does:
The permission denied error makes no sense, because the user in my docker compose is also full owner of all data of all user folders, including hidden filerun folders like .filerun.trash and .filerun.thumbnails.
Customer support service by UserEcho
The MySQL database might be corrupt. I would recommend running "REPAIR TABLE df_users_sessions" on the MySQL database. Let me know if you need more details on how to do that with a Docker-based FileRun install.
Thanks soo much for your quick reply!
I am not sure why I still get permission denied, using the username and password in my docker-compose for the filerun-db service:
The relevant section in my compose:
I see a "filerundb" and a "filerun/db". Perhaps a path is wrong somewhere.
I would also check for available disk space.
I found this in the logfile:
So indeed, this needs to be repaired!
filerundb = name of the SQL database
filerun/db = the path of the mapped volume ($DOCKERDIR/filerun/db:/var/lib/mysql)
I also see the files in the expected location:
So all is fine. I do not understand why it says permission denied. The files are owned by the same user that runs docker commands, same user configured for filerun service etc.
78% free space on the drive (59GB used of 512GB).
/filerun/db/mysql has octal permission 700
files inside it have octal permission 660.
I will just change everything to 755 see what happens.
But I cannot even SHOW TABLES; I always get permission denied. Makes no sense, because I can login fine using the user/pw in my Docker Compose:
I don't understand why I keep getting permission denied.
The output was again permission denied at and then OK for a lot of files.
If I deliberately entered wrong password, the error message was different.
I rebooted the docker service of filerun-db and while service was running, log only showed errors and "aborts" . I have daily/weekly/monthly backups going back 6 months but decided its easier to simply delete $DOCKERDIR/filerun/ contents, starting fresh. Instead of restoring and hoping I found one version without any corruption. I believe this corruption existed a while. Only now exposed itself.
Will start fresh and hopefully all works well.
Starting fresh, with containers and non-persistent volumes removed via Portainer, contents of $DOCKERDIR/filerun/ emptied, then running docker-compose up -d, Filerun is stuck on "Setting up database" for over 12min.
The log shows:
When I refresh the page, the install wizard just starts over. After the first screen > empty white screen > database setup screen > Setting up database... (forever).
I guess I always had a database for the past few years so I never had this issue before..
I had changed my subdomain for filerun in my Compose file from FILES.mydomain.cloud to DRIVE.mydomain.cloud.
Switching it back to FILES subdomain solved it. A little strange, because registering my existing license happens later..
I will take this opportunity to also generate higher quality thumbnails and previews. In the past I always had PNG Quant enabled, but I believe that focuses on smallest filesize, not quality? Better quality with pngquant disabled (since this is default, even though the library is included in the docker image)?
Same quality with PNG Quant, just lower size.
Again thanks for the quick replies, really appreciated. I did a comparison:
copied a folder of photos to another user, so both users have their own copy of this folder of photos.
Then I kept pngquant disabled (= default), and used command line to generate thumbs for the first user. Enabled pngquant and ran the command for the second user.
The difference is really big, quite noticeable. Quality with pngquant disabled is much, much better. The same as on my phone for example: high quality thumbs.
With pngquant disabled its like looking at an older bitmap, or a photo saved with less colors or something.
Perhaps this has to do with pngquant quality settings, I understand it is possible to configure a quality range.
At least the default setting (disabled) is definitely the best for now.
My bad, I checked now, the program is ran with "--quality=65-80".