Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

HELP - CPU pinning not saving my selection

Featured Replies

I'm running 6.7.2 and noticed that Plex and a few other dockers are running really slow. I previously ran into Spaceinvanderone's awesome youtube series on optimizing my server and pinned certain CPU cores/threads to Plex and several other dockers. Fast forward a few months and now the server starts to act up, i check the CPU pinning area in Settings and notice that nothing is selected. I re-allocated the CPU pairings as per spaceinvaderone's suggestions and hit Apply then Done. All looks ok, but then when i reopen the CPU pinning feature to check my selections, everything has been deselected. 

 

Diagnostics attached.  

 

Thoughts on what's going on? Thanks a lot in advance!

2019-07-14 21-04-26-1.zip

Do you also have any cpu pinning entered in manually in the extra parameters of the template?

  • Author

No. I don’t honestly know how to do that. 

Post an applicable xml file from /config/plugins/dockerMan/templates-user on the flash drive that you're having problems with.

  • Author

ok ... FINALLY got the file to post. (i've been out traveling on business)... see the attached.

 

 

my-PlexMediaServer.xml

  • Author

the more i think about this, the more i feel that the issue might have to do with my flash drive.... i had to replace my flash drive due to it becoming corrupted (which itself was a random event). i replaced the flash drive, got a new GUID issued and was back up and running.... i think that's around the same time i began having these issues.

 

any ideas on how to check into all this?

 

thanks again!

Are there another xml in the folder named identically, but having a (1) at the end?

Sent from my NSA monitored device

  • Author

thanks for your reply... no, nothing in that directory has a (1) at its end. see the screenshot. 

IMG_0001.PNG

9 hours ago, lordmarqui said:

the more i think about this, the more i feel that the issue might have to do with my flash drive.... i had to replace my flash drive due to it becoming corrupted (which itself was a random event). i replaced the flash drive, got a new GUID issued and was back up and running.... i think that's around the same time i began having these issues.

 

any ideas on how to check into all this?

 

thanks again!

That was my first idea, but nothing was in the logs about any flash problems.  Still possible though.

  • Author

any suggestions from here? 

 

if there is a chance the flash drive is the issue, could you kindly direct me on how to rebuild it without losing all my server data?

any suggestions from here? 
 
if there is a chance the flash drive is the issue, could you kindly direct me on how to rebuild it without losing all my server data?
You will NEVER lose your data. All you have to do is save the contents of /config on the flash and it's like nothing ever happened after transferring over the registration.

Even if the flash completely drops dead and you don't have a backup, you will never lose the files on the hard drives

Sent from my phone as I'm probably having a beer and enjoying a fire

  • Author

thanks squid... i went ahead and recreated my flash drive, copied over my old config folder and had to reassign all my drives for the array... problem is the issue still remains. even with this new flash drive, the CPU pinning will not stay even after i apply the changes.

 

any other thoughts?

Show me screenshots of what you're doing and seeing in order

Sent from my phone as I'm probably having a beer and enjoying a fire

  • Author

here's my process:Settings > CPU Pinning >

 

Screen Shot 2019-07-22 at 7.13.01 PM.png

 

CPU Pinning Docker: Plex (I then select all the cores/threads I want)

Click Apply, then Done.

 

Screen Shot 2019-07-22 at 7.13.18 PM.png

 

Screen Shot 2019-07-22 at 7.13.48 PM.png

 

Reload CPU Pinning, settings aren't saved.

Screen Shot 2019-07-22 at 7.14.15 PM.png

FYI: VM pinning does work correctly.

 

(I have NOT messed with the CPU Isolation tick boxes yet.)

 

Thanks again for your time

Edited by lordmarqui

  • Community Expert

The second last screenshot shows you have set up the cpu pinning selections but have not yet hit the Apply button to commit them.   Are you sure you are not omitting that step?

  • Author

i'm definitely hitting the Apply button after selecting them. Then I hit Done. Then it exits me out of the CPU pinning window and takes me back to the settings  window. then i click back into CPU pinning and it's as if i never changed any of the selections 

  • Community Expert
39 minutes ago, lordmarqui said:

i'm definitely hitting the Apply button after selecting them. Then I hit Done. Then it exits me out of the CPU pinning window and takes me back to the settings  window. then i click back into CPU pinning and it's as if i never changed any of the selections 

Fair enough - just thought it was worth checking in case you were having a blindspot for a simple error.  I do no use that feature so I have no other ideas for what might be causing your problems.

Ok, I see lots of CSRF token errors on your logs which indicates a browser left open to Unraid after a reboot.  Let's try this:

 

1)  Close out of all browser sessions connected to the Unraid webGui.

2)  Restart your server.

3)  Attempt to adjust the CPU pinning again.

4)  Verify it didn't take.

5)  Collect diagnostics and repost them here.

 

I want to see the logs right after you attempt to change the pinning and it fails.  Want to see what it says.

 

Also can you confirm what type of browser you're using and try using a different one just to make sure this isn't a weird browser issue.

  • Author

thanks for the reply! see the attached... (i'm also attaching the syslog in case that helps at all.)

 

i'm using chrome on a mac... i tried cpu allocation in safari without success... i then rebooted and followed the procedure you indicated.

 

thanks again

 

 

tower-diagnostics-20190723-2242.zip tower-syslog-20190723-2242.zip

Edited by lordmarqui
added more info

  • Author

Were those logs helpful at all?

4 minutes ago, lordmarqui said:

Were those logs helpful at all?

Just as useful as the previous ones (ie: not at all)

 

But, since you're running an Mac, can you post the output of this.  I have a thought (and yes I know that is a rare thing ;) )

 

ls -ail /boot/config/plugins/dockerMan/templates-user

 

  • Author

See the attached 

4695E845-4B4F-4DF1-B7C7-6279EC00D451.jpeg

  • Author

Squid, you still still thinking it might be a docket folder issue? seems to me that they’re all accounted for?

 

do you think this had anything to do with me copying my /config folder over from a flash backup? 

I was hoping there were some hidden files in there created by the Mac.  Have you tried pinning the CPUs from when you edit the App?  Switch to advanced view

  • Author

that worked! ... i am able to pin dockers to specific CPUs using the advanced view of each container but still not via the CPU Pinning feature in Settings...  Not sure why but i don't care at this point!

 

thanks a lot for your help in all this!

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.