ERROR weewx.reportengine: ftpgenerator: (0): caught exception '<class 'socket.gaierror'>': [Errno -3]

[Artvd]

Hello 

I am experiencing a problem with ftp upload. It even remaind after reinstalling Weewx and hope someone can help me to resolve this. This is the log:

Mar 11 21:25:51 raspberrypi weewx[8796] INFO weewx.reportengine: Copied 97 files to /var/www/html/weewx

Mar 11 21:25:51 raspberrypi weewx[8796] ERROR weewx.reportengine: ftpgenerator: (0): caught exception '<class 'socket.gaierror'>': [Errno -3] Tijdelijk probleem in naamsherleiding

Mar 11 21:25:51 raspberrypi weewx[8796] ERROR weewx.reportengine:         ****  Traceback (most recent call last):

Mar 11 21:25:51 raspberrypi weewx[8796] ERROR weewx.reportengine:         ****    File "/usr/share/weewx/weewx/reportengine.py", line 331, in run

Mar 11 21:25:51 raspberrypi weewx[8796] ERROR weewx.reportengine:         ****      n = ftp_data.run()

Mar 11 21:25:51 raspberrypi weewx[8796] ERROR weewx.reportengine:         ****    File "/usr/share/weewx/weeutil/ftpupload.py", line 127, in run

Mar 11 21:25:51 raspberrypi weewx[8796] ERROR weewx.reportengine:         ****      ftp_server.connect(self.server, self.port)

Mar 11 21:25:51 raspberrypi weewx[8796] ERROR weewx.reportengine:         ****    File "/usr/lib/python3.7/ftplib.py", line 152, in connect

Mar 11 21:25:51 raspberrypi weewx[8796] ERROR weewx.reportengine:         ****      source_address=self.source_address)

Mar 11 21:25:51 raspberrypi weewx[8796] ERROR weewx.reportengine:         ****    File "/usr/lib/python3.7/socket.py", line 707, in create_connection

Mar 11 21:25:51 raspberrypi weewx[8796] ERROR weewx.reportengine:         ****      for res in getaddrinfo(host, port, 0, SOCK_STREAM):

Mar 11 21:25:51 raspberrypi weewx[8796] ERROR weewx.reportengine:         ****    File "/usr/lib/python3.7/socket.py", line 748, in getaddrinfo

Mar 11 21:25:51 raspberrypi weewx[8796] ERROR weewx.reportengine:         ****      for res in _socket.getaddrinfo(host, port, family, type, proto, flags):

Mar 11 21:25:51 raspberrypi weewx[8796] ERROR weewx.reportengine:         ****  socket.gaierror: [Errno -3] Tijdelijk probleem in naamsherleiding

[Karen K]

That looks like a resolver problem that does not relate to WeeWX.

What happens if you enter ping www.ibm.com on the console?

[Artvd]

Thanks for your reaction. I do not have a console so i do not knkow how to do that otherwise 

Op donderdag 11 maart 2021 om 22:18:45 UTC+1 schreef kk44...@gmail.com:

[Karen K]

Where do you enter commands to start/stop WeeWX or edit config files? There you can enter that ping command.

[Artvd]

This is what i get

$ ping ibm.com

PING ibm.com (23.213.242.74) 56(84) bytes of data.

64 bytes from a23-213-242-74.deploy.static.akamaitechnologies.com (23.213.242.74): icmp_seq=1 ttl=59 time=9.90 ms

64 bytes from a23-213-242-74.deploy.static.akamaitechnologies.com (23.213.242.74): icmp_seq=2 ttl=59 time=10.1 ms

64 bytes from a23-213-242-74.deploy.static.akamaitechnologies.com (23.213.242.74): icmp_seq=3 ttl=59 time=9.45 ms

64 bytes from a23-213-242-74.deploy.static.akamaitechnologies.com (23.213.242.74): icmp_seq=4 ttl=59 time=9.63 ms

64 bytes from a23-213-242-74.deploy.static.akamaitechnologies.com (23.213.242.74): icmp_seq=5 ttl=59 time=9.61 ms

Op donderdag 11 maart 2021 om 22:29:38 UTC+1 schreef kk44...@gmail.com:

[Karen K]

Ok, that is good. I am not used to dutch language, and I wondered what the error message "Tijdelijk probleem in naamsherleiding" means, and I thought, may be, the computer does not find any sites in the internet. But it does. So that is not the problem.

But still, the error log let me think that WeeWX cannot cannot convert names to IP addresses.

What if you put an IP address instead of the name in the config?

[Artvd]

It  means  " Temporary problem in name redirection" .
I have taken up contact with my hosting company. There is perhaps a problem on their side. but i gueas i will have to wait till tomorrow.

Op donderdag 11 maart 2021 om 23:22:58 UTC+1 schreef kk44...@gmail.com:

[Artvd]

It is resolved. It was a problem at my web hosting provider. Thanks for your assistence.

Op donderdag 11 maart 2021 om 23:40:56 UTC+1 schreef Artvd:

[Karen K]

That's what I guessed. Therefore I asked you that ping thing, although it does not reveal the real problem.