#FILEWATCHER ON SAMBA SHARE HOW TO#
#FILEWATCHER ON SAMBA SHARE FULL#
#FILEWATCHER ON SAMBA SHARE TV#

Please let me know if you have any tips on how to get my Movies library to properly scan files into Emby.

I don't think there is any permissions issue- both 'Movies' and 'TV' directories on my Pi have full permissions enabled. This resolved my playback issue! But, for some reason, the 'Movies' library will not scan in any files no matter what I do. So I tried that- and set the optional network path in Emby to the SMB address. After searching the forums, I found a suggestion that I should try mounting the shares to actual directories on my Pi, and then add those folders as the library paths in Emby. It scanned all my files in correctly, but I was having issues with playback for some reason. On my first setup attempt with Emby, I added the libraries with direct network paths to the SMB share. Here's the other strange thing- at one point, I had both libraries scanning in correctly. I've tried deleting my Emby libraries & re-adding them, rebooting my Pi server, clicked 'Scan Library Files' everywhere I can find it. I've tried to comb through it to look for any clues about why my Movies library isn't being scanned properly, but I'm not finding anything obvious.

The strange thing is that the TV library is scanning in just fine, but for some reason, the Movies library either is not scanning or is saying 0 items found.Īttached is a log file. Then in Emby, I have two libraries- one for TV, one for Movies. The Pi mounts the SMB respective Movies and TV shares to /home/pi/readyshare/movies and /home/pi/readyshare/tv. Files are being shared on my network with SMB from an external drive attached to my router. I have two folders on the pi, 'Movies', and 'TV'. Example if the file comes at 100 hrs, then the script thinks that the file came before the SLA time and doesn't send any alert (100-2359 is negative).I'm running an Emby server on my Raspberry Pi, and I seem to be having trouble with scanning my library. Obviously, I also cannot calculate the right SLA miss time if it comes later than that. If you look at the last line in my example - the timings end at 2359 and I can't calculate if the file arrived after 2359 (as that's the highest time in a day and this minus any value won't produce a negative value). Example if the first file comes at 930, then (930-900) is 30 minutes late. It calculates the 'SLA' missed time using current time-end time (3rd column). If the file arrives late, the script sends an email saying that the SLA was missed for that file. If it is negative, then it checks if the file came after and missed it's SLA or not. To check if a file arrived after it's defined time, I've set another condition which checks the endtime - current time value. When the end time (column 3) is less than ten minutes and the file hasn't arrived, then an email is sent to the team that the file is missing. The script runs every ten minutes in the background 24/7 and compares the current timings with the second and third column, if the current time falls in between these timings, checks if the file is there or not. Something like this: First one is the file, second and third are timings between which the file usually comes, fourth is the team responsible for the file and 5th is their email.

The script reads a file which contains list of input files (full path to the file), delimited with | and other information. So I have successfully developed a filewatcher script that's running fine.

#FILEWATCHER ON SAMBA SHARE FULL#

#FILEWATCHER ON SAMBA SHARE TV#

Filewatcher on samba share