XF 2.2 xenForo doesn't track statistics anymore

Hotfix

Active member
Yesterday I woke up with a long list of errors:

Screenshot_2021-02-15 Server error log Varasija - Admin control panel.png


I thought it was weird, because everything seemed to be running fine – until I checked the forum statistics:

Screenshot_2021-02-15 Varasija - Admin control panel.png


No, the forum didn't die in the last 24 hours.

The stats from the last day are obviously wrong and perhaps linked to the long list of errors I've got.

Has anyone had to deal with a similar situation and what did you do to resolve it?
 
What’s the stack trace and request state of the errors?

Sorry. I'm still quite new to xenForo, and not sure what you're looking for, so I'll copypaste everything here:

Stack trace​


3098 | }
3099 | max-width: 95%;
3100 |
3101| border: 1px solid mix(rgb(230, 214, 236), , 65%);
3102 | .m-dropShadow(0, 3px, 5px, 0, .3);
3103 |
3104 | li
------------

#0 src/XF/CssRenderer.php(416): XF\CssRenderException::createFromLessException(Object(Less_Exception_Chunk), 'public:core.les...', '// Note that th...')
#1 src/XF/CssRenderer.php(350): XF\CssRenderer->renderToCss('public:core.les...', '// Note that th...')
#2 src/XF/CssRenderer.php(258): XF\CssRenderer->renderTemplate('public:core.les...', NULL)
#3 src/XF/CssRenderer.php(116): XF\CssRenderer->renderTemplates(Array, Array, Array)
#4 src/XF/CssWriter.php(53): XF\CssRenderer->render(Array)
#5 css.php(30): XF\CssWriter->run(Array, 2, 4, 'bd90a5dd06aadea...')
#6 {main}

-------------

Previous Less_Exception_Chunk: ParseError: Unexpected input in anonymous-file-0.less on line 3101, column 8
3099| max-width: 95%;
3100|
3101| border: 1px solid mix(rgb(230, 214, 236), , 65%);
3102| .m-dropShadow(0, 3px, 5px, 0, .3);
3103|
3104| li - src/vendor/oyejorge/less.php/lib/Less/Parser.php:677
#0 src/vendor/oyejorge/less.php/lib/Less/Parser.php(621): Less_Parser->GetRules(NULL)
#1 src/vendor/oyejorge/less.php/lib/Less/Parser.php(449): Less_Parser->_parse()
#2 src/XF/CssRenderer.php(412): Less_Parser->parse('// Note that th...')
#3 src/XF/CssRenderer.php(350): XF\CssRenderer->renderToCss('public:core.les...', '// Note that th...')
#4 src/XF/CssRenderer.php(258): XF\CssRenderer->renderTemplate('public:core.les...', NULL)
#5 src/XF/CssRenderer.php(116): XF\CssRenderer->renderTemplates(Array, Array, Array)
#6 src/XF/CssWriter.php(53): XF\CssRenderer->render(Array)
#7 css.php(30): XF\CssWriter->run(Array, 2, 4, 'bd90a5dd06aadea...')
#8 {main}


Request state

array(4) {
["url"] => string(158) "/css.php?css=public%3Anormalize.css%2Cpublic%3Afa.css%2Cpublic%3Acore.less%2Cpublic%3Aapp.less&s=2&l=4&d=1613258123&k=bd90a5dd06aadea78e7798ab93be5e743f328637"
["referrer"] => string(21) "https://mywebsite.com/"
["_GET"] => array(5) {
["css"] => string(67) "public:normalize.css,public:fa.css,public:core.less,public:app.less"
["s"] => string(1) "2"
["l"] => string(1) "4"
["d"] => string(10) "1613258123"
["k"] => string(40) "bd90a5dd06aadea78e7798ab93be5e743f328637"
}
["_POST"] => array(0) {
}
}


Request state

array(4) {
["url"] => string(158) "/css.php?css=public%3Anormalize.css%2Cpublic%3Afa.css%2Cpublic%3Acore.less%2Cpublic%3Aapp.less&s=2&l=4&d=1613258123&k=bd90a5dd06aadea78e7798ab93be5e743f328637"
["referrer"] => string(21) "https://mywebsite.com/"
["_GET"] => array(5) {
["css"] => string(67) "public:normalize.css,public:fa.css,public:core.less,public:app.less"
["s"] => string(1) "2"
["l"] => string(1) "4"
["d"] => string(10) "1613258123"
["k"] => string(40) "bd90a5dd06aadea78e7798ab93be5e743f328637"
}
["_POST"] => array(0) {
}
}
 
Last edited:
The problem with the stats fixed itself. I still have no idea what's the cause of the errors and how it affects the forum. No one has reported having any problems.
 
Just spitballing here but is it possible that some scenario happened like this:
  • Overly aggressive indexing bots or a link to your site on some social platform caused high load on your server
  • Due to the high load, some cron job that's for statistics updates didn't run as expected
  • The stats were messed up because of that
  • Later when things were normal the job ran OK and fixed the issue
?
 
Top Bottom