Jump to content

Forum is down


Go to solution Solved by wegorz23,

Recommended Posts

Posted

Hi,

We have problem with our IPS forum today. It is down, even after reebot of machine.

Support tool show this:

Could contain: Text

We have many error logs now, and some uncaught exception.

the errors in logs:

Sun, 15 Jan 2023 10:59:30 +0000
TypeError: Unsupported operand types: string - int (0)
#0 /home/audiostereo/public_html/applications/cms/sources/Blocks/Block.php(217): IPS\Theme\content_blocks_350()
#1 /home/audiostereo/public_html/system/Theme/Theme.php(4628) : eval()'d code(18): IPS\cms\Blocks\_Block::display()
#2 /home/audiostereo/public_html/applications/cms/sources/Blocks/Block.php(217): IPS\Theme\content_blocks_351()
#3 /home/audiostereo/public_html/applications/cms/widgets/Blocks.php(143): IPS\cms\Blocks\_Block::display()
#4 /home/audiostereo/public_html/system/Widget/Widget.php(826): IPS\cms\widgets\_Blocks->render()
#5 /home/audiostereo/public_html/system/Widget/Widget.php(858): IPS\_Widget->_render()
#6 /home/audiostereo/public_html/system/Theme/Theme.php(885) : eval()'d code(19215): IPS\_Widget->__toString()
#7 /home/audiostereo/public_html/system/Theme/SandboxedTemplate.php(61): IPS\Theme\class_core_front_global->widgetContainer()
#8 /home/audiostereo/public_html/system/Theme/Theme.php(885) : eval()'d code(7104): IPS\Theme\_SandboxedTemplate->__call()
#9 /home/audiostereo/public_html/system/Theme/SandboxedTemplate.php(61): IPS\Theme\class_core_front_global->globalTemplate()
#10 /home/audiostereo/public_html/system/Output/Output.php(745): IPS\Theme\_SandboxedTemplate->__call()
#11 /home/audiostereo/public_html/init.php(927) : eval()'d code(26): IPS\_Output->error()
#12 /home/audiostereo/public_html/init.php(1070): IPS\cms_hook_Output->error()

 

And the same after disable all plugins and apps and clearing cache. 

Posted

Data storage and cache warning are checked periodically so will not immediately disappear. You can dismiss those notifications and see if they re-appear.

Please let us know if you have any other issues.

Posted (edited)

Now its ok but it was second time in two weeks that forum down and cannot access any thing.

The log file was like 500 gb and whole machine was down. 

This one today was clearly and simple to match whats the problem is (block 350 or 351) but second time its like nothing.

The process list was full and cpu still stay on 100% CPU.

It was like that: (not this one when our forum was down) 

#0 /home/audiostereo/public_html/system/Theme/Theme.php(340): IPS\_Member::loggedIn()
#1 /home/audiostereo/public_html/system/Dispatcher/Standard.php(63): IPS\_Theme::i()
#2 /home/audiostereo/public_html/system/Dispatcher/Front.php(759): IPS\Dispatcher\_Standard::baseCss()
#3 /home/audiostereo/public_html/init.php(927) : eval()'d code(110): IPS\Dispatcher\_Front::baseCss()
#4 /home/audiostereo/public_html/init.php(927) : eval()'d code(49): IPS\Dispatcher\postnotes_hook_postNotes_cssAndJsFiles::baseCss()
#5 /home/audiostereo/public_html/system/Dispatcher/Front.php(76): IPS\Dispatcher\bimchatbox_hook_includeJSandCSS::baseCss()
#6 /home/audiostereo/public_html/init.php(927) : eval()'d code(36): IPS\Dispatcher\_Front->init()
#7 /home/audiostereo/public_html/index.php(13): IPS\_Dispatcher::i()
#8 {main}
#0 /home/audiostereo/public_html/init.php(1029): IPS\_Log::log()
#1 [internal function]: IPS\IPS::exceptionHandler()
#2 {main}

 

ParseError: syntax error, unexpected token "=>" (0)
#0 /home/audiostereo/public_html/init.php(1606): IPS\IPS::init()
#1 /home/audiostereo/public_html/index.php(12): require_once('...')
#2 {main}

 

Edited by wegorz23
Posted

In the log there are many third party traces so you would want to troubleshoot that first. Clearing any cache/template cache on the file system may help when you encounter it. 

  • Solution
Posted
On 1/16/2023 at 11:27 AM, Marc Stridgen said:

The first question there would be what are those blocks? Are those perhaps 3rd party blocks that are running?

Its simple html blocks but connecting to DB and getting data from that. By ips { \IPS\Db->select } 

Its like after migrating to php8.0 thats happened and its clearly that problem. 

The problem is that try { } catch { } not getting that. 😞 

We can close that topic.

 

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...