Recently i installed a new motherboard and CPU with more cores than my old one.

 

At first when trying to update the cpu pinning it didn't work when pinning all the cores to certain containers, but it did work when only pinning cores 1-8.

 

Now it doesn't work at all and whenever i hit apply the change doesn't apply and i get this error in the syslog:

Quote

Jun  3 18:42:05 Tower root: error: /webGui/include/UpdateOne.php: missing csrf_token

 

I'm not sure what UpdateOne is.

 

i've checked all my plugins for updates, ive rebooted the server a couple of times, i've restarted the docker service, i've booted into safe mode, Nothing seems to help.

 

I am able to change the pinning if i go per container but i really want to avoid that if i can.

Try again after booting in safe mode.

Already tried that, didn't help.

Then I would suggest recreating the flash drive, backup the current one first and then redo it and just restore the bare minimum, like the key, super.dat and the pools folder for the assignments, also copy the docker user templates folder, if all works you can then reconfigure the server or try restoring a few config files at a time from the backup to see if you can find the culprit.

I was hoping i could avoid that 🫠

 

oh well.

I would also try a different browser, maybe you have a browser extension that is preventing the csrf token from being added to the page.

11 minutes ago, ljm42 said:

I would also try a different browser, maybe you have a browser extension that is preventing the csrf token from being added to the page.

tried firefox, chrome, and edge.
same issue

 

any idea what UpdateOne.php is a reference to?

The CPU Pinning page first submits to UpdateOne.php then to UpdateTwo.php. All post submissions require a CSRF token and fail if it is missing.  

 

CSRF tokens have been working for years so I was thinking perhaps your browser was not letting JavaScript run to add the CSRF token.

 

One thing to try... go to Tools -> PHP Settings and enable "All Categories". Press "View Log" and keep the popup window open while trying the operation again. Is anything added to the log?

Either way, please upload your diagnostics (from Tools -> Diagnostics) 

[05-Jun-2024 00:50:08 UTC] PHP Warning:  PHP Request Startup: Input variables exceeded 1000. To increase the limit change max_input_vars in php.ini. in Unknown on line 0

trying to update 63 containers with 32 cores would seem to be the issue here?

 

guessing i need to change the max_input_vars in php.ini wherever that may be stored

Edited June 5, 20242 yr by MammothJerk

Oooh that's exciting  

 

Tools -> PHP Settings -> PHP Info confirms that max_input_vars is at 1000

 

Edit /etc/php.ini and add a new line at the end:

max_input_vars = 1500

 

And then reload PHP:

/etc/rc.d/rc.php-fpm reload

 

Refresh Tools -> PHP Settings -> PHP Info to confirm max_input_vars has a new value, then try submitting the form. If PHP log still complains, try a higher number.

 

FYI, the changes to php.ini will be lost the next time you reboot

 

I had to use 2500 and the reload command was different

/etc/rc.d/rc.nginx reload 
/etc/rc.d/rc.php-fpm reload

found from a different thread

 

Now it works though.

 

Any reason why the limit is so "low"?

 

I doubt that i'm the first to run into this issue with only 32 cores and 63 containers.

 

Perhaps a better error message should be put forth...

 

Anyways, thanks for the help!

Glad to hear it! That was an interesting one to track down  

 

Oh you are right, I fixed the rc.php-fpm command in my response. In my testing, reloading nginx was not necessary but it doesn't hurt.

 

We need to do some evaluation of this page, see if there is a way to get it to send fewer vars.