Skip to content
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

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

Closed
ttmader opened this issue Feb 15, 2022 · 2 comments
Closed

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

ttmader opened this issue Feb 15, 2022 · 2 comments

Comments

@ttmader
Copy link

ttmader commented Feb 15, 2022

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
Copy link
Author

ttmader commented Feb 15, 2022

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
Copy link
Member

rschitz commented Feb 16, 2022

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

@rschitz rschitz closed this as completed Feb 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants