-
-
Notifications
You must be signed in to change notification settings - Fork 404
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When Resource XML file inproperly formatted, graph creation can fail with errors #4865
Comments
What data query were you using? Can you upload the Resources XML file here for us to review. |
I'm using data query that I found on the forum. This is data query for iDirect : |
The XML files have some illegal characters in them. Notice in the attached image the following Get rid of those illegal characters and I think the problem will be solved. I will put in a patch to mask the error, but my guess is that we should be handling this better. In any event, it's a Resource XML file issue. Occurs in all of them. |
This fix provides additional clarity on the errors being encountered in this bug.
Test the update before you fix the XML files. |
Thank you very much. I'm sorry that I didn't notice that before .. |
Hello,
I run my cacti server on Centos 7.
Recently I tried to create a new graph and I got errors after that in my logs :
--
2022/07/18 10:25:38 - ERROR PHP WARNING: Illegal string offset 'direction' in file: /var/www/html/cacti/graphs_new.php on line: 826
2022/07/18 10:25:38 - CMDPHP PHP ERROR WARNING Backtrace: (/graphs_new.php[68]:graphs(), /graphs_new.php[670]:CactiErrorHandler())
2022/07/18 10:25:38 - ERROR PHP WARNING: Illegal string offset 'direction' in file: /var/www/html/cacti/graphs_new.php on line: 670
I compare the file graphs_new.php that I've to other ones and it looks like everything is normal.
Just cause I'm curious I ran 'systemctl status cactid' on my server and I got the error :
"Failed to start Cacti Daemon Main Poller Service"
I guess there is a link between this 2 problems.
Cacti version : 1.2.21.
The text was updated successfully, but these errors were encountered: