-
Notifications
You must be signed in to change notification settings - Fork 1
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
Issue with checks for CLARIN-LT #9
Comments
We tried to connect to the Host from the Server but Ping/dig/head/etc get any valid. Most time it can't establish a connection. It looks like an DNS Issue, to solve it we must change the Name-Server of the monitoring-VM. |
We have tried to change the NameServer, but on reboot it was overwritten. |
There used to be DNS (and/or firewall) problems with this host, after discussing it with Andrius, I thought it was solved. I setup a statuscake probe, and for most areas the access seems to be working well now since a couple of weeks, but in the logs I still notice problems with access from Warsaw (Poland). Including @uandrius to this issue so that he can comment |
We received a user report as well that (some?) handles are not resolving: http://hdl.handle.net/20.500.11821/11 and emails to the clarin.vdu.lt domain are not arriving (Your message couldn't be delivered. The Domain Name System (DNS) reported that the recipient's domain does not exist.) |
The CLARIN-LT checks give an error that I cannot trace myself: the OAI endpoint seems to work correctly and the SSL certificate is valid.
OAI-PMH CRITICAL: HTTPSConnectionPool(host='clarin.vdu.lt', port=443): Max retries exceeded with url: /oai/request?verb=Identify (Caused by NewConnectionError('<urllib3.connection.VerifiedHTTPSConnection object at 0x14fccff72978>: Failed to establish a new connection: [Errno -2] Name or service not known',))
See https://monitoring.clarin.eu/monitoring/host/show?host=CLARIN-LT and https://monitoring.clarin.eu/monitoring/service/show?host=CLARIN-LT&service=ssl_cert%20clarin.vdu.lt
The text was updated successfully, but these errors were encountered: