Butler:. Is it doing anything?

I have scheduled tasks set to run from 11pm to 9am. How can I tell if they actually ran? I have no database backup after two weeks. Not sure if any of the other tasks are running. Is there any way to see what if anything happened between 11 and 9?

Make sure you didn’t tell Plex to backup the database to a location that is not accessible or is read-only.
Try emptying out the target folder input field again.
Settings - Server - Scheduled Tasks - ‘Show Advanced’ - “Backup directory”
to set it back top the default database folder.


Also verify that your database is not corrupted.

  1. activate debug logging (not ‘verbose’!)
  2. quit Plex Server
  3. wait 1 minute
  4. start Plex Server
  5. wait 5 minutes
  6. fetch log files and attach them here

Or inspect them yourself. Take a look at the Plex Media Server.log file and seek for messages about database corrupt or malformed.
If you find these, you may have to repair your database.
https://support.plex.tv/articles/201100678-repair-a-corrupt-database/

no corrupt or malformed entries in the logs. Created a new folder for backups and set it in the scheduled tasks settings. Ill check in 3 days. I have 2400 items with no indexes and that number didnt go down overnight so that part of the tasks didnt appear to run either. Wish there was a way to see what actually did run overnight. Log overnight had a butler started line but nothing much after that. Logs attached.Plex Media Server Logs_2019-08-18_10-18-23.zip (1.7 MB)

What kind of drive is F:? internal, external, pooled, network share?

Because it doesn’t appear to be reliable:
Aug 16, 2019 12:53:10.904 [5836] ERROR - Transcoder: Failed to delete session directory (boost::filesystem::remove: Access is denied: "F:\PlexData\Plex Media Server\Cache\Transcode\Sessions\plex-transcode-82d92091c5087f95-com-plexapp-android-2134-26fa9756-a85c-4130-93f8-790e00cc0cc5\chunk-00164")

F is an external USB drive

Update on this. Butler is butlering again. I found a registry entry pointing to an older Plex data location. I updated that entry and that seemed to fix the butler issue. Not sure exactly why that would fix it but that seemed to do the trick

1 Like

Interesting. Do you remember which registry branch this was in?

No the only reason I thought to do that was I saw some recently created files in the old location. Some Plex update service logs were written there 2 days ago but I changed data location to f drive over a month ago. Not sure what registry branch had the old path…

I think I know where. But I’m seriously confused, since this registry key should only affect the update helper service and not the Butler.

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.