I check the log of Nebula Graph. It says
nebula-graphd.ERROR
Log file created at: 2022/12/3 21:57:44
Running on machine: ubuntu
Running duration (h:mm:ss): 0:00:00
Log line format: [IWEF]yyyymmdd hh:mm:ss.uuuuuu threadid file:line] msg
E20221120 21:57:44.568208 2865 QueryInstance.cpp:137] SyntaxError: syntax error near THERE_ARE_SOME_ERRORS' E20221120 21:57:44.568208 2864 QueryInstance.cpp:137] SyntaxError: syntax error near THERE_ARE_SOME_ERRORS’
E20221120 21:57:44.568349 2865 QueryInstance.cpp:137] SyntaxError: syntax error near THERE_ARE_SOME_ERRORS' E20221120 21:57:44.568373 2864 QueryInstance.cpp:137] SyntaxError: syntax error near THERE_ARE_SOME_ERRORS’
E20221120 21:57:44.568380 2865 QueryInstance.cpp:137] SyntaxError: syntax error near THERE_ARE_SOME_ERRORS' E20221120 21:57:44.568416 2865 QueryInstance.cpp:137] SyntaxError: syntax error near THERE_ARE_SOME_ERRORS’
I tried reboot, which doesn't work
It looks like the storaged is not added to the cluster successfully. Did you run the add hosts command? see here.
Could you please share what you have done?
It looks similar to https://discuss.nebula-graph.com.cn/t/topic/11277/ but not sure if you had done the same(put the ADD HOSTS of storage with a wrong port)
Related
Can anyone help me? I'm doing web scraping. I want to click on the button. Here is my xpath code:
/html/body/center/table/tbody/tr[2]/td/form/table[2]/tbody/tr[18]/td[3]/width='20%'/input[3]
I got an error as follow. Can anyone explain why and what is the solution?
SyntaxError: Failed to execute 'evaluate' on 'Document': Type conversion failed while evaluating the expression.
I'm new at making website. Even I only know Html Coding. I'm running a website using WordPress, but it is facing problem everyday at same time. Everyday at the same time site is showing Http 500 error.
So as I don't know any kind of coding, every day I have to delete WordPress from my site then again have to install it then I have to restore website using Updraftplus. But I want to fix this oroblem.
I have an option in my cPanel called "Errors". I find this error from there.
I copied what there was said:
1st error:
[Mon Dec 23 03:46:44.895719 2019] [lsapi:error] [pid 1014092:tid 47766993704704] [client 141.8.188.1:46957] [host gokumovie.com] Backend fatal error: PHP Fatal error: Uncaught Error: Call to undefined function esc_url() in /home/gokumovi/public_html/wp-includes/class-wp-fatal-error-handler.php:190\nStack trace:\n#0 /home/gokumovi/public_html/wp-includes/class-wp-fatal-error-handler.php(147): WP_Fatal_Error_Handler->display_default_error_template(Array, false)\n#1 /home/gokumovi/public_html/wp-includes/class-wp-fatal-error-handler.php(52): WP_Fatal_Error_Handler->display_error_template(Array, false)\n#2 [internal function]: WP_Fatal_Error_Handler->handle()\n#3 {main}\n thrown in /home/gokumovi/public_html/wp-includes/class-wp-fatal-error-handler.php on line 190\n
2nd error :
Backend fatal error: PHP Fatal error: Uncaught Error: Call to undefined function wp_kses_normalize_entities() in /home/gokumovi/public_html/wp-includes/formatting.php:4316\nStack trace:\n#0 /home/gokumovi/public_html/wp-includes/class-wp-fatal-error-handler.php(190): esc_url('https://wordpre...')\n#1 /home/gokumovi/public_html/wp-includes/class-wp-fatal-error-handler.php(147): WP_Fatal_Error_Handler->display_default_error_template(Array, false)\n#2 /home/gokumovi/public_html/wp-includes/class-wp-fatal-error-handler.php(52): WP_Fatal_Error_Handler->display_error_template(Array, false)\n#3 [internal function]: WP_Fatal_Error_Handler->handle()\n#4 {main}\n thrown in /home/gokumovi/public_html/wp-includes/formatting.php on line 4316\n
I have an almost fresh install of Symfony 3.2 and it appears not to be capturing and displaying PHP errors.
To test, I have omitted the final semicolon from a line in a working controller. When I try to access the route a blank screen is displayed (the app returns nothing). This is in the dev environment. The error is logged by Symfony, but it is not handled and displayed by the debug component. This is my first version 3 project - I have previously worked in version 2 where the nicely formatted error would be returned for such an error.
Any ideas how to fix this?
I am on PHP version 5.5.9.
The relevant lines in the Symfony log are:
php.CRITICAL: Fatal Parse Error: syntax error, unexpected 'return' (T_RETURN) {"exception":"[object] (Symfony\Component\Debug\Exception\FatalErrorException(code: 0): Parse Error: syntax error, unexpected 'return' (T_RETURN) at /var/www/html/tcfdev/src/AppBundle/Controller/HomeController.php:17)"} []
and
request.CRITICAL: Uncaught PHP Exception Symfony\Component\Debug\Exception\FatalErrorException: "Parse Error: syntax error, unexpected 'return' (T_RETURN)" at /var/www/html/tcfdev/src/AppBundle/Controller/HomeController.php line 17 {"exception":"[object] (Symfony\Component\Debug\Exception\FatalErrorException(code: 0): Parse Error: syntax error, unexpected 'return' (T_RETURN) at /var/www/html/tcfdev/src/AppBundle/Controller/HomeController.php:17)"} []
The apache2 log contains the following:
PHP Parse error: syntax error, unexpected 'return' (T_RETURN) in /var/www/html/tcfdev/src/AppBundle/Controller/HomeController.php on line 17
So it appears that debug is picking it up but failing to display it.
An almost fresh install? Did you get this from another project? Does your routing_dev.yml have the profiler and errors setup?
It should look something like this:
_wdt:
resource: "#WebProfilerBundle/Resources/config/routing/wdt.xml"
prefix: /_wdt
_profiler:
resource: "#WebProfilerBundle/Resources/config/routing/profiler.xml"
prefix: /_profiler
_errors:
resource: "#TwigBundle/Resources/config/routing/errors.xml"
prefix: /_error
_main:
resource: routing.yml
I am getting the following error message in Symfony:
Parse error: syntax error, unexpected '\' (T_NS_SEPARATOR), expecting identifier (T_STRING)
when I execute DoctrineMigrations for example this one line shows up?
how can I debug this?
this is the full trace:
PHP Fatal error: Uncaught Symfony\Component\Debug\Exception\FatalThrowableError: Parse error: syntax error, unexpected '\' (T_NS_SEPARATOR), expecting identifier (T_STRING) in /Library/WebServer/Documents/hrd_3/var/cache/dev/appDevDebugProjectContainer.php:7087
Stack trace:
#0 /Library/WebServer/Documents/hrd_3/vendor/symfony/symfony/src/Symfony/Component/HttpKernel/Kernel.php(117): Symfony\Component\HttpKernel\Kernel->initializeContainer()
#1 /Library/WebServer/Documents/hrd_3/vendor/symfony/symfony/src/Symfony/Bundle/FrameworkBundle/Console/Application.php(68): Symfony\Component\HttpKernel\Kernel->boot()
#2 /Library/WebServer/Documents/hrd_3/vendor/symfony/symfony/src/Symfony/Component/Console/Application.php(117): Symfony\Bundle\FrameworkBundle\Console\Application->doRun(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))
#3 /Library/WebServer/Documents/hrd_3/bin/console(29): Symfony\Component\Console\Application->run(Object(Symfony\Component\Console\Input\ArgvInput))
in /Library/WebServer/Documents/hrd_3/var/cache/dev/appDevDebugProjectContainer.php on line 7087
Fatal error: Uncaught Symfony\Component\Debug\Exception\FatalThrowableError: Parse error: syntax error, unexpected '\' (T_NS_SEPARATOR), expecting identifier (T_STRING) in /Library/WebServer/Documents/hrd_3/var/cache/dev/appDevDebugProjectContainer.php:7087
Stack trace:
#0 /Library/WebServer/Documents/hrd_3/vendor/symfony/symfony/src/Symfony/Component/HttpKernel/Kernel.php(117): Symfony\Component\HttpKernel\Kernel->initializeContainer()
#1 /Library/WebServer/Documents/hrd_3/vendor/symfony/symfony/src/Symfony/Bundle/FrameworkBundle/Console/Application.php(68): Symfony\Component\HttpKernel\Kernel->boot()
#2 /Library/WebServer/Documents/hrd_3/vendor/symfony/symfony/src/Symfony/Component/Console/Application.php(117): Symfony\Bundle\FrameworkBundle\Console\Application->doRun(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))
#3 /Library/WebServer/Documents/hrd_3/bin/console(29): Symfony\Component\Console\Application->run(Object(Symfony\Component\Console\Input\ArgvInput))
in /Library/WebServer/Documents/hrd_3/var/cache/dev/appDevDebugProjectContainer.php on line 7087
update:
in the debug container on 7087:
class VichUploaderBundleHandlerDownloadHandler_00000000110518fa000000015e248fd4966f7bb604f68fe14d5ab23e4a657cd2 extends \\Vich\UploaderBundle\Handler\DownloadHandler implements \\ProxyManager\Proxy\VirtualProxyInterface
{
if i disable this module, then another class will have this problem... like randomly.
I've found that the issue is caused by new zendframework v3.0.3 - see https://github.com/symfony/symfony/issues/9815
So for the quick fix at the moment just add
"zendframework/zend-code": "3.0.2"
into your composer file
Same bug is in symfony/framework-bundle version 2.8.13, file DependencyInjection/FrameworkExtension.php,
line 374:
$container->setParameter('router.cache_class_prefix', $container->getParameter('kernel.container_class'));
Version 2.8.12 is OK:
$container->setParameter('router.cache_class_prefix', $container->getParameter('kernel.name').ucfirst($container->getParameter('kernel.environment')));
Tested on PHP 5.6.26 ...
Fatal error: require_once(): Failed opening required '/home/webmaster/main/sites/all/modules/advanced_forum/includes/views/advanced_forum_handler_field_node_topic_iconinc' (include_path='.:/usr/share/php:/usr/share/pear') in /home/webmaster/main/includes/bootstrap.inc on line 3186
I update module after that have error.
First, check integrity of your module.
Second, if your module is okay use registry_rebuild. Place it on your sites/all/modules folder and call (registry_rebuild.php).
Example with your browser : http://yourdomain.local/sites/all/modules/registry_rebuild/registry_rebuild.php