sexibytes / sexigraf

SexiGraf is a vSphere centric Graphite appliance with a Grafana frontend.
http://www.sexigraf.fr
MIT License
128 stars 21 forks source link

Can't connect to xxxxx.xxxxxx.xxx:443 (Name or service not known) #285

Closed ttmader closed 2 years ago

ttmader commented 2 years ago

Hello!

I have several vCenters connected but one of them is no longer visible and does not connect. I don't know if it's a firewall problem.

I have seen that Sexigraf does not resolve that vCenter by DNS and I have put it in the hosts file and checked connectivity via netcat to 443.

This is the error that appears in the log:

[2022/02/15 11:17:05] /root/getInventory.pl line249 - [INFO] Start processing vCenter xxxxx.xxxxxx.xxx [2022/02/15 11:17:05] /usr/local/lib/x86_64-linux-gnu/perl/5.22.1/XML/LibXML/Error.pm line183 - DIE :1: parser error : Start tag expected, '<' not found Can't connect to xxxxx.xxxxxx.xxx:443 (Name or service not known) ^ [2022/02/15 11:17:05] /usr/share/perl/5.22/Carp.pm line166 - DIE :1: parser error : Start tag expected, '<' not found Can't connect to xxxxx.xxxxxx.xxx:443 (Name or service not known) ^ [2022/02/15 11:17:05] /usr/share/perl/5.22/VMware/VICommon.pm line2380 - DIE SOAP request error - possibly a protocol issue: Can't connect to xxxxx.xxxxxx.xxx:443 (Name or service not known)

Name or service not known at /usr/local/share/perl/5.22.1/LWP/Protocol/http.pm line 50.

Can you help me?

Thank you.

ttmader commented 2 years ago

Hello again,

After modifying the /etc/hosts file and adding the vCenter that does not resolve through DNS and restarting Sexigraf, the entries disappear.

I think if I fix this, the problems will go away.

Thank you.

rschitz commented 2 years ago

I guess it's a dns issue then. the next release will take care of not responding vcenter ;)