Search the Community

Hello, Running emby-portable (Version 3.5.3.0) as a service on a WIN10 box with latest updates. On my monitoring software, I noticed that there was a certain pattern in CPU load: After analyzing this, it seems to be my emby server: And checking my emby logs on the problematic timeslots: 2018-09-23 02:24:05.683 Info TaskManager: IntervalTrigger fired for task: Convert media 2018-09-23 02:24:05.683 Info TaskManager: Queueing task SyncConvertScheduledTask 2018-09-23 02:24:05.683 Info TaskManager: Executing Convert media ... 2018-09-23 03:16:36.857 Info TaskManager: Convert media Completed after 52 minute(s) and 31 seconds ... 2018-09-23 05:24:08.625 Info TaskManager: IntervalTrigger fired for task: Convert media 2018-09-23 05:24:08.625 Info TaskManager: Queueing task SyncConvertScheduledTask 2018-09-23 05:24:08.625 Info TaskManager: Executing Convert media ... 2018-09-23 06:16:41.102 Info TaskManager: Convert media Completed after 52 minute(s) and 32 seconds ... 2018-09-23 08:24:08.636 Info TaskManager: IntervalTrigger fired for task: Convert media 2018-09-23 08:24:08.636 Info TaskManager: Queueing task SyncConvertScheduledTask 2018-09-23 08:24:08.636 Info TaskManager: Executing Convert media ... 2018-09-23 09:16:46.827 Info TaskManager: Convert media Completed after 52 minute(s) and 38 seconds On my dashoard https://xxx.xxx.xxx.xxx/web/index.html#!/scheduledtasks.html,I can see the job is running: Problem is: I am NOT adding any new media (defenitly no during the night :-) ) and nobody was watching anything. In fact, server should be stable an not doing anything for last days/weeks. So, what exactly is my server converting??? Is it needed? Any help is appreciated, so thanx for taking a closer look a this, Kind regards, Bart