Missing clearlogo.png (and other files)

[HawkXP71 112]

What triggers the creation of the clearlogo.png file? I have two servers (same media, one is essentially an offsite backup for my NAS, so I figured might as well run Emby on it as well)

The settings are exactly the same (the best I can tell) the only difference is the "actual" media location (/volume1 vs /volume2)

But on the backup server, there are tons of clearlogo.png that do not exist on the primary.  There are also a number on the primary that dont exist on the backup.

What triggers them? Refresh Metadata doesnt seem to kick this off even with replace existing images checked.

I also seem to be missing a bunch of XXX-thumb.jpg
 

Edited November 10, 2022 by HawkXP71

[GrimReaper 4753]

Library setting, Image Fetchers section, "Fetcher settings", select type of artwork do be downloaded.

Edited November 10, 2022 by GrimReaper

[HawkXP71 112]

6 minutes ago, GrimReaper said:

Library setting, Image Fetchers section, "Fetcher settings", select type of artwork do be downloaded.

Thanks!  Dont know if thats the issue, but once my current scan is done Ill kick an update again to see.

[HawkXP71 112]

I think I finally tracked down the issue...  The good news, the root cause has 100% NOTHING to do with emby, its 100% on my setup.

The bad news, I do think it exposes two issues in emby that should be looked at.

Its a permissions issue.  Essentially here is the problem, Im using DSM 7.x as both my AD as well my emby server.    The problem is this, when I aquire a new piece of media, and copy it over to my library directory, SOMETIMES (gots to love its) it uses my DOMAIN account and sometiems my emby user account. When it uses my domain account the permissions are of the form

drwxr-sr-x 1 TOWEL42\scott emby 44 Nov 13 23:38 ./Movies/Quigley Down Under (1990) [tmdbid=9588]

notice group and other permissions are missing the write permission flag

Then I just happened to notice this in the log (Ive been watching anytime I add any media to look for an error...
 

2022-11-14 02:01:18.425 Error ChapterImagesTask: Error creating thumbnails for /volume2/video/Movies/Quigley Down Under (1990) [tmdbid=9588]/Quigley Down Under.mkv

	*** Error Report ***
	Version: 4.7.9.0
	Command line: /volume2/@appstore/EmbyServer/system/EmbyServer.dll -programdata /var/packages/EmbyServer/var -ffdetect /var/packages/EmbyServer/target/bin/ffdetect -ffmpeg /var/packages/EmbyServer/target/bin/ffmpeg -ffprobe /var/packages/EmbyServer/target/bin/ffprobe -nolocalportconfig -ignore_vaapi_enabled_flag -pidfile /var/packages/EmbyServer/var/EmbyServer.pid -defaultdirectory /volume1/Public -updatepackage emby-server-synology7_{version}_x86_64.spk -noautorunwebapp
	Operating system: Linux version 4.4.180+ (root@build3) (gcc version 8.5.0 (GCC) ) #42962 SMP Tue Oct 18 15:05:01 CST 2022
	Framework: .NET 6.0.8
	OS/Process: x64/x64
	Runtime: volume2/@appstore/EmbyServer/system/System.Private.CoreLib.dll
	Processor count: 4
	Data path: /var/packages/EmbyServer/var
	Application path: /volume2/@appstore/EmbyServer/system
	System.UnauthorizedAccessException: System.UnauthorizedAccessException: Access to the path '/volume2/video/Movies/Quigley Down Under (1990) [tmdbid=9588]/Quigley Down Under-320-10.bif' is denied.
	 ---> System.IO.IOException: Permission denied

 

And when I looked at the directory, the bif file, and all thumbnail/images are missing.  Since as I would expect emby doesnt have write permissions to the directory.

Typically, I realize the permission issue, and fix it via a script that I have, which will look for directories and files with incorrect permissions (essentially any directory not in the emby group without write rwx permissions on the directory and rw permissions on the file)

Here is where I think there are  two  things Emby can fix.

• When any error occurs, not just have it in the log file, but on the dashboard with the data for the error being part of the "info" text
• For whatever reason, that directory that had the permission issue, either gets tagged as "bad dir" or something, because rescanning the library, or refreshing the media data for the movie doesnt create the BIF, nor does it download the images to the dir

The first issue is clearly an enhancement, but in general I think would provide a ton of insight for all sorts of errors. They are easily lost in the log, and if you dont know what you are looking for can be hard to track down by a non expert.

The second I do consider a bug.  The solution, has been to touch the directory and the media file.  that seems to trigger something so the images and bif will get created.

@GrimReaper @luke let me know if its not clear

TIA
~Scott

 

 

Quigley Down Under.nfo

[Luke 42085]

Quote

• When any error occurs, not just have it in the log file, but on the dashboard with the data for the error being part of the "info" text
• For whatever reason, that directory that had the permission issue, either gets tagged as "bad dir" or something, because rescanning the library, or refreshing the media data for the movie doesnt create the BIF, nor does it download the images to the dir

Hi, I don't think these are bugs. It can't create the files because the server is being denied permission.

 

[HawkXP71 112]

41 minutes ago, Luke said:

Hi, I don't think these are bugs. It can't create the files because the server is being denied permission.

 

The first one is absolute an enhancement, it would just be great if under notifications on the dashboard if it listed the errors that have occured.

The second one, is after I have fixed the permissions, the directory seems to be flagged internally to not try again.  How can that flag or whatever is causing the "dont work on this directory anymore" to be cleared out.

[Luke 42085]

3 minutes ago, HawkXP71 said:

The first one is absolute an enhancement, it would just be great if under notifications on the dashboard if it listed the errors that have occured.

The second one, is after I have fixed the permissions, the directory seems to be flagged internally to not try again.  How can that flag or whatever is causing the "dont work on this directory anymore" to be cleared out.

There is no such flag. Every save operation after that will still keep trying. Why do you think this is the case?

Quote

The first one is absolute an enhancement, it would just be great if under notifications on the dashboard if it listed the errors that have occured.

The problem, from my experience, is that users will interpret that as an Emby problem and come to us looking for answers. Even if they realize it's not an Emby problem, they'll still come to us if they don't know how to work with permissions. That means more time spend troubleshooting and less time developing.

Not that I'm completely against putting it there, but only if it's clear that it's something the end user needs to fix, and can get them started on how to do that.

[HawkXP71 112]

2 minutes ago, Luke said:

The problem, from my experience, is that users will interpret that as an Emby problem and come to us looking for answers. Even if they realize it's not an Emby problem, they'll still come to us if they don't know how to work with permissions. That means more time spend troubleshooting and less time developing.

Not that I'm completely against putting it there, but only if it's clear that it's something the end user needs to fix, and can get them started on how to do that.

Gotcha, suggestion, make it an "advanced" option that could be turned on, maybe in the logging area?  Have it turned off by default.  

Also, depending on the error message (since it looks like you are simply redisplaying the system exception thrown by the application I realize this is harder than it sounds) you could highlight the error differently if you know its a "setup issue", "permissions issue", "do this to fix it issue".

So that the tool becomes more self aware of how to heal itself , it doesnt do the healing of course  it just recommends what the user can do to fix it.  I realize that you have no idea if the person using it is a "I know where to download movies and can run chrome" type of user.  Or a guy with 40 years of unix experience, who has been a professional software developer for 30+ years...  So making it an advanced option for me, would be great.  But I totally get what you are saying.  To say the least, Ive been there done that with my products.

 

3 minutes ago, Luke said:

There is no such flag. Every save operation after that will still keep trying. Why do you think this is the case?

Only because of what I have seen.  Where I messed up and didnt set the perms correctly before I moved the file into the library area.

Then when I change the perms, nothing happens (maybe your inotifywait isnt  tracking attributes which makes perfect sense)

But even when I do a "refresh media" on the directory, I dont see it create the BIF, thumb images or NFO files.  it could be something else is in play, but that is why it seems to me there is some sort of flag
 

[HawkXP71 112]

In case anyone else has this issue (your network creating non emby writeable directories)  Here was my solution.

I call inotifywait command on bootup of my nas.  It only monitors the close_write and create events.  When activated, on the files close or created it runs chmod and/or chown on the files and directories that are out of spec.

Note, in order for things not to go recursive (since changing the attributes of a file triggers a close_write, I use a lock file to ignore events kicked off while running the chmod/chown