Hi

 

 

I got a call trace error alert this morning by Fix Common Problems.  Diags posted - what should I do to fix please?

 

 

Thanks

 

DZMM

First thing you need to do is fix this:

 

Feb 18 02:12:20 Highlander root: error: plugins/advanced.buttons/AdvancedButtons.php: wrong csrf_token

 

as your syslog is full of it (17,760 instances, in fact). I understand it's caused by having a stale browser window open on the web GUI. It's happening typically three times a second, every second.

 

It looks as though it filled up your log because there's no sign of the call trace you mentioned.

 

 

 

On 2/18/2017 at 3:08 PM, John_M said:

First thing you need to do is fix this:

 

 

 

as your syslog is full of it (17,760 instances, in fact). I understand it's caused by having a stale browser window open on the web GUI. It's happening typically three times a second, every second.

 

It looks as though it filled up your log because there's no sign of the call trace you mentioned.

 

 

 

thanks - how do I fix?  I think this is related to the problem I'm having where I can't open the Sabnzbd webgui in a normal browser window and I have to open an incognito window.

The error has just popped up again - hopefully there's more detail in these logs

highlander-diagnostics-20170221-0938.zip

The wrong_csrf token error is explained in the release thread - it's caused by the old token being returned by a stale browser window following a reboot of unRAID. A new token is generated as the system starts and it doesn't match the old one. The solution is to close or refresh browser windows.

This time there were fewer - hundreds instead of thousands and the details of your call trace were still present in the syslog. It was caused by IRQ 16 being ignored and then disabled. I've seen this before and the severity depends on what hardware is affected. If it affects a NIC or a SAS controller it will severely affect performance. I haven't been able to find out what uses IRQ 16 in your system (and I can't ask you to run lsirq because unRAID doesn't have it built in - maybe the Nerd Pack has it) so it's probably not that important. If you don't notice any problems it can probably be ignored. Look out for a newer BIOS - yours is already fairly recent - or a newer kernel (unRAID 6.3.3, when it's released).

Thanks - the only problem I have is the weird Sabnzbd webgui issue, and the main webgui being slow to show the login page sometimes. 

Will monitor as suggested