METAR Error

[allenxie]

Hi,
There's a METAR error in my server and I couldn't get real time weather data in my FSD....

Found in logs.txt

05-10-109 22:43:58 : Booting server
05-10-109 22:43:58 FSD: Reading certificates from 'cert.txt'
05-10-109 22:43:58 FSD: Booting port 6809 (client interface)
05-10-109 22:43:58 FSD: Booting port 3011 (server interface)
05-10-109 22:43:58 FSD: Booting port 3010 (system management interface)
05-10-109 22:43:58 FSD: No 'allowfrom' found, allowing everybody on the server port
05-10-109 22:43:58 FSD: We are up
05-10-109 22:44:23 FSD: ** METAR: Could not connect to ftp port on METAR host



My settings in FSD.conf:


################################################## #############################
# This group controls the weather system.
# The 'source' variable determines the source of the METAR data.
# For normal operation, set this to 'network'.
# There are 3 possible values here:
# 'file' : Read the METAR data from the file 'metar.txt'
# and allow weather requests from other servers.
# 'download' : Like 'file', but refresh metar.txt every hour by downloading
# the latest weather observations from metlab. The server has
# to be connected to the internet for this to work.
# 'network' : Relay weather requests to the closest METAR capable server.
#
# 'server','dir' and 'ftpmode' are only used when the METAR source is 'download'. These
# fields determine the host name and the directory from where metar data is
# read. FSD uses the FTP protocol to get the data. ftpmode can have the value 'active'
# 'passive' that are Active and Passive FTP protocol mode, default is 'passive'.
# If you use FSD on a computer having a private IP, only use passive mode.
[weather]
source=download
server=weather.noaa.gov
dir=data/observations/metar/cycles/
ftpmode=passive


I tried to change server line to this:
server=weather.noaa.gov:21

The error in the log.txt disappeared, but there is still no real time weather in FSINN....

Could you help me ?
Much appreciated！

[L. D. James]

Hi,
There's a METAR error in my server and I couldn't get real time weather data in my FSD....

...

[weather]
source=download
server=weather.noaa.gov
dir=data/observations/metar/cycles/
ftpmode=passive


I tried to change server line to this:
server=weather.noaa.gov:21

The error in the log.txt disappeared, but there is still no real time weather in FSINN....

What happens when you use the

server=tgftp.nws.noaa.gov

server?


-- L. James

--
L. D. James
ljames@apollo3.com
www.apollo3.com/~ljames

[allenxie]

Solved. Thanks!

[the whaler]

I am currently heaving the same problen, but with the website you mention.
I can find the site though (ftp) but i get the download warning.
This is frustrating at the moment.

config has had
[weather]
source=download
server=weather.noaa.gov
dir=data/observations/metar/cycles/
ftpmode=passive

[weather]
source=download
server=tgftp.nws.noaa.gov
dir=data/observations/metar/cycles/
ftpmode=passive

and
[weather]
source=download
server=ftp://tgftp.nws.noaa.gov
dir=data/observations/metar/cycles/
ftpmode=passive

but they all result in the same message.

** METAR ** could not lookup METAR host name tgftp.nws.noaa.gov

Where do I need to look?
Thanks in advance.
Lex

[the whaler]

Still no answer possible?
Could it be something in Linux, as the problem I have seems to be related there, but I am not sure.
Any help would be appreciated.
Thanks and best Regards.
Lex

Edit:
I used http://www.hcidata.info/host2ip.cgi to look into the ftp address. I got the following reply.

Details of ftp://tgftp.nws.noaa.gov/data/observations/metar/cycles/

Host Name : ftp://tgftp.nws.noaa.gov/data/observations/metar/cycles/IP Address : ftp://tgftp.nws.noaa.gov/data/observations/metar/cycles/ cannot be resolved to an IP AddressLocation : Unknown
So again this shows me that this is realated to Linux resolving internet addresses. I can remember there was something on the former mcdu forum with the release of fsd that there were issues with using the linux server to download metar files. I also remember there was a remark this was "no resolved". Yet as that forum is no longer accessible and there does'nt seem to be a backup I cannot look into this.
Anyone able to help me with this?
Any help would be appreciated.
Regards.
Lex

[the whaler]

Found a solution, so perhaps also workable for others.
Changed the ftp address in the corresponding IP number. From what the log said it had to be something with the dns naming and just replasing the ip number did the trick for me. So for those also struggling out there with fsd on linux here is my working config.

[weather]
source=download
#server=weather.noaa.gov #from origional but not correct anymore
#when using windows take the dns name
#server=tgftp.nws.noaa.gov
#when using linux take the corresponding IP
server=140.90.128.71
dir=data/observations/metar/cycles
ftpmode=passive

Regards.
Lex

[the whaler]

I might have cheered to early.
Yesterday I advertadly rebooted the whole linux server. And guess what. Now I get the same message but only with the IP adress. So appearantly somewhere along the line I did change something in Linux that at least the IP number would work with FSD. But this appearantly changed back at the reboot. So now its back to finding what it is.
Any Linux gooroo out there able to make sence?
If I find it again I will let you know.
any help is highly appreciated.
Thanks and best regards.
Lex

[the whaler]

No worries,
Found the problem
Appearantly somewhere along the line a few tabs or spaces came behind the ip number (probable when I copied the info in this thread).
So it was not recognised correctly. Now it works again.

it had
server=140.90.128.71 (spaces)
it should be
server=140.90.128.71(no spaces)

Lex

[L. D. James]

No worries,
Found the problem
Appearantly somewhere along the line a few tabs or spaces came behind the ip number (probable when I copied the info in this thread).
So it was not recognised correctly. Now it works again.

it had
server=140.90.128.71 (spaces)
it should be
server=140.90.128.71(no spaces)

Lex

Hi, Lex.

You should consider fixing your dns.

What do you have in your /etc/resolv.con file?

It should be something like:

# domain yourdomain.com
# search yourdomain.com
nameserver [the IP of the primary name server your ISP gave you]
nameserver [the IP of the secondary name server your ISP gave you]There are other parameters you can include, but this is a basic template that should get you operating.

-- L. James

--
L. D. James
ljames@apollo3.com
www.apollo3.com/~ljames (http://www.apollo3.com/%7Eljames)

[the whaler]

Thanks James.

Currently it has the following

nameserver 82.197.196.182
nameserver 82.197.196.183
nameserver 192.168.169.210

First two are the ones I found with my provider (http://www.tweakdsl.nl/?page=support/general/dns) as dns nameserver (resolving). They also have 2 for nameserver (regestration). Should I add those here as well?
I think this will be good anyway since I host some websites and it looks like I will then be able to add more. Need to investigate and off topic of course.

(last one is my freesco router, very nice floppy based linux router program (can work on i386 machines if you still have one), see freesco.net for info). This one also has the tweakdsl numbers by the way.

Thanks and best regards.
Lex

[the whaler]

Strange,found another site at this provider with different numbers, http://www.tweakdsl.nl/?page=business/support (http://www.tweakdsl.nl/?page=business/support) so I guess I need to contact them.

[the whaler]

Strange,found another site at this provider with different numbers, http://www.tweakdsl.nl/?page=business/support (http://www.tweakdsl.nl/?page=business/support) so I guess I need to contact them.


Anyway, adding all the IP numbers still did not do the trick. With the tgftp.nws.... I still get download error. With the IP number is works.

My knowledge is limited here unfortunatly. Will try to read more on Linux in the near future.
Regards.
Lex

[L. D. James]

Anyway, adding all the IP numbers still did not do the trick. With the tgftp.nws.... I still get download error. With the IP number is works.

My knowledge is limited here unfortunatly. Will try to read more on Linux in the near future.
Regards.
Lex

Try this and only this in your nameserver list:

nameserver 208.94.147.150
nameserver 208.94.147.151


-- L. James

--
L. D. James
ljames@apollo3.com
www.apollo3.com/~ljames

[the whaler]

Hi James.

No luck:confused:

IP works, dns name doesn't
Lex

[Hurkulez]

The problem is that ftp://tgftp.nws.noaa.gov/data/observ.../metar (ftp://tgftp.nws.noaa.gov/data/observations/metar/cycles/) site does not allow non username and non password log ins.

So I did the following:

1. Setup a local web server (abyss web server)
IE: Apache or Abyss Web Server

2: Install a dns updater if you do not have a static ip
IE: no-ip.org or dyndns

3. Put the FSD Server folder in the htdocs folder of Abyss Web Server folder
IE: c:\program files\abyss web server\htdocs\FSD_Server

4. In the FSD_Server Folder create a meters folder
IE: c:\program files\abyss web server\htdocs\FSD_Server\meters

5. Now install an FTP download software
IE: ws_ftp pro

6. Connect to above ftp link w/ ws_ftp pro
UN = anonymous
PW= your actual email address

7. Right pane - you should see cycles folder
a. Highlight it (Do not expand it)
b. Left pane - Point it to your ...\FSD_Server\meter folder

8. Click download
Now if the ftp download worked you should see meter cycles in the c:\program files\abyss web server\htdocs\FSD_Server\meters\cycles folder

9. In the connection log at bottom of WS_FTP
a. Right click it.
b. Add scheduled download
c Make hourly/60 mins download (cycles are updated hourly on the hour, on the FTP)

10. Edit fsd.conf file of FSD Server
IE:

[weather]
source=download
server=your dns goes here
dir=metar/cycles
ftpmode=passive

11. Launch FSD Server and you should have weather now.

NOTE: If behind a router you will have to port foward

[Rius]

I had the same problem. On my windows FSD server, I put the address tgftp.nws.noaa.gov and it worked really well, on my linux FSD server, I put the same address and had no weather.
I managed to solve the problem by putting the IP address (140.90.128.71) corresponding to tgftp.nws.noaa.gov dns, and everything works fine

[the whaler]

I hadnt followed the thread lately, but Hurkulez makes one small error I see. His explenation is for a windows server, not the linux one.

Why we need the ip adress in stead of the dns I don't really know, but it works and thats what counts.:)
Lex

[Hurkulez]

Sorry bought that :)