# Scanner constantly running - High CPU - 1.31 & beyond

**URL:** <https://forums.plex.tv/t/scanner-constantly-running-high-cpu-1-31-beyond/851382>\
**Category:** Plex Media Server\
**Tags:** server-linux\
**Created:** [August 24, 2023, 12:14am UTC](https://forums.plex.tv/t/scanner-constantly-running-high-cpu-1-31-beyond/851382 "2023-08-24T00:14:51Z")\
**Posts on this page:** 14\
**Page:** 1

<div class="post-metadata">

**Author:** ![ChuckIbey](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/chuckibey/32/179454_2.png) [@ChuckIbey](https://forums.plex.tv/u/ChuckIbey)\
**Post date:** [August 24, 2023, 12:14am UTC](https://forums.plex.tv/t/scanner-constantly-running-high-cpu-1-31-beyond/851382/1 "2023-08-24T00:14:51Z")

</div>

Server Version#: currently 1.32.5.7349  
Player Version#: n/a  
Server Hardware: Linux on Intel NUC, Ubuntu 18.04.6 LTS

Plex Media Server has worked great for probably a decade. On all new updates from 1.31 and beyond, the scanner constantly runs and PMS uses between 30% and 55% CPU constantly at idle. Scanner keeps going, stopping, and running again. It’s also triggering a “remote access is down” notification and then 15 seconds later a “remote access is back up” notification. Always.

I can downgrade to 1.30.1.6562 and it all goes back to normal. Everything works wonderfully. Anything beyond that, and my problem comes back.

On working versions, PMS CPU usage is at 0.5% idle.

Is it an issue with my OS being a little older? Ubuntu 18?

Let me know what information I can provide… logs, screenshots, more details. Whatever is needed.

\<If providing [server logs](https://support.plex.tv/articles/200250417-plex-media-server-log-files/) please do NOT turn on verbose logging, only [debug logging](https://support.plex.tv/articles/201643703-reporting-issues-with-plex-media-server/#toc-1) should be enabled\>

---

<div class="post-metadata">

**Author:** ![ChuckPa](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/chuckpa/32/79710_2.png) [@ChuckPa](https://forums.plex.tv/u/ChuckPa)\
**Post date:** [August 24, 2023, 12:38am UTC](https://forums.plex.tv/t/scanner-constantly-running-high-cpu-1-31-beyond/851382/2 "2023-08-24T00:38:18Z")

</div>

Yep, it’s 18.04.

All the updates since 1.31 have continued their normal trek to keep up with standard distros.

Ubuntu 18.04 is EOL.

While there weren’t any issues at first, they will catch up to you.

At present, OpenSSL v3.0.0 is beyond what 18.04 can do because it’s not getting any updates to support it.

[![](https://res.cloudinary.com/canonical/image/fetch/f_auto,q_auto,fl_sanitize,c_fill,w_720/https://lh3.googleusercontent.com/O88ANiY5eBHfYRRlyAj0_wgH-bkvG7-MTYgjI3NJ1z_36bH-F09iAmC6NaT6Wtq20nKWBIMnnuYTpFZK1ShZB1u4jiRX_-gZlVTsSrIhSDaMOpxE9j4UnvS4ixUgddzZeDZn0VC-YPrkml1qO_Taf152Dk_zK-jkVSquABxGgeO-Lkh2eNOU6PdJuo_9og) ](https://res.cloudinary.com/canonical/image/fetch/f_auto,q_auto,fl_sanitize,c_fill,w_720/https://lh3.googleusercontent.com/O88ANiY5eBHfYRRlyAj0_wgH-bkvG7-MTYgjI3NJ1z_36bH-F09iAmC6NaT6Wtq20nKWBIMnnuYTpFZK1ShZB1u4jiRX_-gZlVTsSrIhSDaMOpxE9j4UnvS4ixUgddzZeDZn0VC-YPrkml1qO_Taf152Dk_zK-jkVSquABxGgeO-Lkh2eNOU6PdJuo_9og)

---

<div class="post-metadata">

**Author:** ![ChuckIbey](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/chuckibey/32/179454_2.png) [@ChuckIbey](https://forums.plex.tv/u/ChuckIbey)\
**Post date:** [August 24, 2023, 12:41am UTC](https://forums.plex.tv/t/scanner-constantly-running-high-cpu-1-31-beyond/851382/3 "2023-08-24T00:41:13Z")

</div>

Appreciate the quick response. Time to upgrade Ubuntu and see what breaks.

---

<div class="post-metadata">

**Author:** ![ChuckPa](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/chuckpa/32/79710_2.png) [@ChuckPa](https://forums.plex.tv/u/ChuckPa)\
**Post date:** [August 24, 2023, 12:59am UTC](https://forums.plex.tv/t/scanner-constantly-running-high-cpu-1-31-beyond/851382/4 "2023-08-24T00:59:50Z")

</div>

Ubuntu “dies like clockwork”.

Take the version - Add 5 years – Better upgrade before then.

---

<div class="post-metadata">

**Author:** ![ChuckIbey](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/chuckibey/32/179454_2.png) [@ChuckIbey](https://forums.plex.tv/u/ChuckIbey)\
**Post date:** [August 24, 2023, 2:32am UTC](https://forums.plex.tv/t/scanner-constantly-running-high-cpu-1-31-beyond/851382/5 "2023-08-24T02:32:14Z")

</div>

Brought the OS up to Ubuntu 22.04.3 LTS and I’m still seeing the issue. High CPU usage at idle and frequent scanning. Restarted the server and the computer, same result.

In the PMS dashboard, it reports using 25-40% CPU, but looking at something like netdata or glances, it shows much higher. 75-110% usage. On 1.30 it was basically zero on idle and no scans unless needed.

Ideas? I’ll have to downgrade again otherwise. At least it forced me to upgrade Ubuntu lol.

More info: Noticed the green lock icon next to my server is flashing… primarily stays off, but the green lock flashes on and off. Same with remote access icon. Flashing occasionally.

---

<div class="post-metadata">

**Author:** ![ChuckPa](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/chuckpa/32/79710_2.png) [@ChuckPa](https://forums.plex.tv/u/ChuckPa)\
**Post date:** [August 24, 2023, 3:53am UTC](https://forums.plex.tv/t/scanner-constantly-running-high-cpu-1-31-beyond/851382/6 "2023-08-24T03:53:12Z")

</div>

Let me see the logs…

Please make sure they capture the cpu activity you’re seeing.

If the “Green Lock” by your server is turning green…

1. It’s secure (encrypted) for a moment…  
2… Then it loses connection and resets

The remote access is flipping out due to DHCP server/IP changes or forwarding.

If your IP address is being reset (even to the same address) it’ll make the green lock go nuts because the connection breaks for a few milliseconds … enough to close the socket (TCP/IP rules)

---

<div class="post-metadata">

**Author:** ![dbirch](https://avatars.discourse-cdn.com/v4/letter/d/f19dbf/32.png) [@dbirch](https://forums.plex.tv/u/dbirch)\
**Post date:** [August 24, 2023, 4:11am UTC](https://forums.plex.tv/t/scanner-constantly-running-high-cpu-1-31-beyond/851382/7 "2023-08-24T04:11:53Z")

</div>

Do you have a bash script/cron running that modifies permissions?

---

<div class="post-metadata">

**Author:** ![ChuckIbey](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/chuckibey/32/179454_2.png) [@ChuckIbey](https://forums.plex.tv/u/ChuckIbey)\
**Post date:** [August 24, 2023, 4:12am UTC](https://forums.plex.tv/t/scanner-constantly-running-high-cpu-1-31-beyond/851382/8 "2023-08-24T04:12:44Z")

</div>

Sending via private message, unless there’s no issue posting here. Wasn’t sure how much private info is included in the logs.

I don’t recall seeing the green lock or remote access status misbehaving on the prior version (1.30.1.6562 ), it’s only on upgrade. Server has a static IP address assigned.

---

<div class="post-metadata">

**Author:** ![ChuckIbey](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/chuckibey/32/179454_2.png) [@ChuckIbey](https://forums.plex.tv/u/ChuckIbey)\
**Post date:** [August 24, 2023, 4:13am UTC](https://forums.plex.tv/t/scanner-constantly-running-high-cpu-1-31-beyond/851382/9 "2023-08-24T04:13:36Z")

</div>

I do actually… I found my permissions weren’t always being correctly assigned as material was moved into my server’s folders so made a script to fix permissions every few minutes. It wasn’t causing any issues on 1.30.1.6562 .

---

<div class="post-metadata">

**Author:** ![ChuckPa](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/chuckpa/32/79710_2.png) [@ChuckPa](https://forums.plex.tv/u/ChuckPa)\
**Post date:** [August 24, 2023, 4:19am UTC](https://forums.plex.tv/t/scanner-constantly-running-high-cpu-1-31-beyond/851382/11 "2023-08-24T04:19:38Z")

</div>

> [@ChuckIbey](#):
>
> I do actually… I found my permissions weren’t always being correctly assigned as material was moved into my server’s folders so made a script to fix permissions every few minutes. It wasn’t causing any issues on 1.30.1.6562 .

DOOH!!!

That script is causing the problem.

PMS 1.31.x and above is sensitive to permission changes as well.

You need to change your scripting to be:

> [@Linux Tips](https://forums.plex.tv/t/linux-tips/276247/26):
>
> Selectively changing directory and file permissions. PMS 1.31.1 and above monitor your media for file permission changes in addition to media content changes. This was provided so PMS knows when your media acquisition processes (DVR/other tasks) complete and the media is now ready for PMS to use. Unfortunately, a number of our users have a “sledgehammer” hammer approach where they just change all permissions for all media. PMS is now sensitive to ALL permission changes (even for media al…

---

<div class="post-metadata">

**Author:** ![ChuckIbey](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/chuckibey/32/179454_2.png) [@ChuckIbey](https://forums.plex.tv/u/ChuckIbey)\
**Post date:** [August 24, 2023, 4:21am UTC](https://forums.plex.tv/t/scanner-constantly-running-high-cpu-1-31-beyond/851382/12 "2023-08-24T04:21:57Z")

</div>

Alright, disabling and checking.

Of note regarding the “green lock”. It flashes and is mainly OFF when I’m connected to the server via IP:PORT, but when connecting via plex.tv, it is always on and a secured connection.

---

<div class="post-metadata">

**Author:** ![ChuckPa](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/chuckpa/32/79710_2.png) [@ChuckPa](https://forums.plex.tv/u/ChuckPa)\
**Post date:** [August 24, 2023, 4:24am UTC](https://forums.plex.tv/t/scanner-constantly-running-high-cpu-1-31-beyond/851382/13 "2023-08-24T04:24:04Z")

</div>

> [@ChuckIbey](#):
>
> via IP:PORT,

IP:port == http.  
URL = https ✅

IP:port does not have a certificate for encryption.  
A URL / FQDN can have a certificate

---

<div class="post-metadata">

**Author:** ![ChuckIbey](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/chuckibey/32/179454_2.png) [@ChuckIbey](https://forums.plex.tv/u/ChuckIbey)\
**Post date:** [August 24, 2023, 4:28am UTC](https://forums.plex.tv/t/scanner-constantly-running-high-cpu-1-31-beyond/851382/14 "2023-08-24T04:28:14Z")

</div>

I think that’s fixed it. Everything seems back to normal. I’ll implement the changes in permissions scripting that you linked.

Appreciate the assistance 🙂

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/plex/original/3X/2/a/2acb9765406f63293d357b4ec509ec39aa28f2ad.png) [@system](https://forums.plex.tv/u/system)\
**Post date:** [November 22, 2023, 4:28am UTC](https://forums.plex.tv/t/scanner-constantly-running-high-cpu-1-31-beyond/851382/15 "2023-11-22T04:28:16Z")

</div>

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