Jump to content
  • [6.12.10] can't update CPU Pinning


    Autchirion
    • Closed

    As soon as I change the CPU pinning for at least one container and hit "apply" it will only show "Please wait..." with a spinning wheel in the UI which will never end.

    I tried it with Containers on and containers off and I checked the log for error messages while doing so. No error message commes up, it just seems like it's doing nothing.

    • Like 2



    User Feedback

    Recommended Comments

    gloworm

    Posted

    I am also having the same issue running 6.12.10.

    D3ver0x

    Posted (edited)

    Same issue for me, 6.12.10. It only happens for docker CPU pinning. VM CPU pinning works fine. Checking network request I found a request to /webGui/include/UpdateOne.php with 500 Internal Server Error

    Edited by D3ver0x
    SimonF

    Posted

    1 hour ago, D3ver0x said:

    Same issue for me, 6.12.10. It only happens for docker CPU pinning. VM CPU pinning works fine. Checking network request I found a request to /webGui/include/UpdateOne.php with 500 Internal Server Error

    Any errors in the phplog, can be viewed from tools->php settings

     

    image.png

    View log.

    D3ver0x

    Posted (edited)

    6 hours ago, SimonF said:

    Any errors in the phplog, can be viewed from tools->php settings

     

    image.png

    View log.

    Here is the error:

     

    Stack trace:
    #0 {main}
      thrown in /usr/local/emhttp/plugins/dynamix/include/UpdateOne.php on line 71
    [23-May-2024 22:19:31 America/Los_Angeles] PHP Warning:  Undefined array key "styles.css.map" in /usr/local/emhttp/plugins/dynamix/template.php on line 74
    [23-May-2024 22:19:31 America/Los_Angeles] PHP Warning:  Trying to access array offset on value of type null in /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php on line 195
    [23-May-2024 22:19:31 America/Los_Angeles] PHP Warning:  Trying to access array offset on value of type null in /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php(657) : eval()'d code on line 15
    [23-May-2024 22:19:42 America/Los_Angeles] PHP Warning:  Attempt to read property "CPUset" on bool in /usr/local/emhttp/plugins/dynamix/include/UpdateOne.php on line 66
    [23-May-2024 22:19:42 America/Los_Angeles] PHP Fatal error:  Uncaught Error: Call to a member function addChild() on bool in /usr/local/emhttp/plugins/dynamix/include/UpdateOne.php:71

     

    Edited by D3ver0x
    SimonF

    Posted

    Which plugins do you have installed?

    Autchirion

    Posted

    These are mine:

    CA Auto Update Applications
    CA Mover Tuning
    Community Applications
    Compose.Manager
    Custom Tab
    Dynamix System Statistics
    Fix Common Problems
    FolderView
    Intel GPU TOP
    NerdTools
    Open Files
    Unassigned Devices
    Unassigned Devices Plus
    Unassigned Devices Preclear
    unbalanced

    D3ver0x

    Posted

    On 5/24/2024 at 6:10 AM, SimonF said:

    Which plugins do you have installed?

    image.png.3c3fa704a80940be82ff2b6ea51af8c4.png

     

     

    Anyway, I was able to update it by editing each of the container manually in docker screen

    SimonF

    Posted

    On 5/28/2024 at 3:12 AM, D3ver0x said:

    image.png.3c3fa704a80940be82ff2b6ea51af8c4.png

     

     

    Anyway, I was able to update it by editing each of the container manually in docker screen

    Can you provide a screen image of the docker section before you do apply?

    wuudogg

    Posted (edited)

    Piling on. Same problem. Spin loop when changing from the CPU Pinning Section for docker.  INo issues changing VMs.  I'm also uncertain if the CPU Pinning GUI screen is correct or if the docker CPU pinning details are correct per docker instance.  They do not seem to be in sync either.  Would almost like to wipe out CPU Pinning and start over.   Wondering if the "FolderView" Plugin may be the culprit here.   May be a timing coincidence but don't recall the issue before FolderView.  Hate to remove it, love it, but will to test. 

    Edited by wuudogg
    JorgeB

    Posted

    Just now, wuudogg said:

    Wondering if the "FolderView" Plugin may be the culprit here.

    Try booting in safe mode and see if it works.

    wuudogg

    Posted

    54 minutes ago, JorgeB said:

    Try booting in safe mode and see if it works.

    Will try that now. Thanks for the idea.

    Autchirion

    Posted

     

    16 hours ago, JorgeB said:

    Try booting in safe mode and see if it works.

     

    5 hours ago, Arbadacarba said:

     

     

     

    both of them together fixed it for me.

    wuudogg

    Posted

    2 hours ago, Autchirion said:

     

     

     

    both of them together fixed it for me.

    Safe Mode alone did not work. Removed the FolderView Plugin. Still spins and doesn't save from the gui.    I added a cloudflare container manually years ago, but the CPU Pinning always worked.  Have since removed it.  Been lazy, going to prune a bunch of old irrelevant containers and see if anything else is lurking hosing me up.

     

    wuudogg

    Posted

    That was it. Thank you @Autchirion Not in safe mode, though expect it would also work in safe mode, I removed 2 old containers that were made via cli that I was hoarding for sentimental value I guess. Clobbered them and any changes now save again from the CPU Pinning Gui. Thanks all.  

    JorgeB

    Posted

    Changed Status to Closed

    Changed Priority to Other

    UsedOak

    Posted

    @JorgeB I just wanted to add for the sake of issue tracking that I too experienced this issue regarding the inability to change Docker CPU Pinning allocations when a CLI installed container is present. In my particular case it was a Cloudflared container and I am running 7.0.0-beta1. Upon removing the CLI created container it saved correctly so this issue is still present in the beta of the 7 series release.

    AlanC

    Posted

    Still present in 7.0.2 beta too

    snowe

    Posted

    Still an issue. I cannot go around deleting all the extra containers I've made, as they run a significant amount of things. There needs to be an actual solution for this.

    Autchirion

    Posted

    1 hour ago, snowe said:

    Still an issue. I cannot go around deleting all the extra containers I've made, as they run a significant amount of things. There needs to be an actual solution for this.

    FYI, you can look in the Apps Tab. There is a section „previous apps“, you can remove all of them so that it’s clean. After that stop the docker service remove the docker image, create a new one and start the service.

    After that, just go to previous apps, select all and install them. This reduces the effort and the downtime a lot.

    don’t do this if you’ve got more than 100 containers, this is the 24h limit you can pull from dockerhub.

     

     I’ve got like 20 containers and I had a downtime of 30 minutes, for a home setup this is acceptable in most cases.

     

    But the issue comes back, I have it again.

    snowe

    Posted

    6 minutes ago, Autchirion said:

    FYI, you can look in the Apps Tab. There is a section „previous apps“, you can remove all of them so that it’s clean. After that stop the docker service remove the docker image, create a new one and start the service.

    After that, just go to previous apps, select all and install them. This reduces the effort and the downtime a lot.

    don’t do this if you’ve got more than 100 containers, this is the 24h limit you can pull from dockerhub.

     

     I’ve got like 20 containers and I had a downtime of 30 minutes, for a home setup this is acceptable in most cases.

     

    But the issue comes back, I have it again.

     

    I haven't actually started any apps in the CLI, I've only run stuff through docker compose. Removing the images seems to mean completely deleting the compose files, because I've stopped all containers and the problem still persists. In any case, I just went through manually and updated all the CPU pinning. It did take an hour, but I didn't have to pay too close attention. This is still a ridiculous bug to have.

    • Upvote 1


    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
    Add a comment...

    ×   Pasted as rich text.   Restore formatting

      Only 75 emoji are allowed.

    ×   Your link has been automatically embedded.   Display as a link instead

    ×   Your previous content has been restored.   Clear editor

    ×   You cannot paste images directly. Upload or insert images from URL.


  • Status Definitions

     

    Open = Under consideration.

     

    Solved = The issue has been resolved.

     

    Solved version = The issue has been resolved in the indicated release version.

     

    Closed = Feedback or opinion better posted on our forum for discussion. Also for reports we cannot reproduce or need more information. In this case just add a comment and we will review it again.

     

    Retest = Please retest in latest release.


    Priority Definitions

     

    Minor = Something not working correctly.

     

    Urgent = Server crash, data loss, or other showstopper.

     

    Annoyance = Doesn't affect functionality but should be fixed.

     

    Other = Announcement or other non-issue.

×
×
  • Create New...