Closed (outdated)
Project:
U.S. National Weather Service
Version:
6.x-1.1
Component:
Code
Priority:
Major
Category:
Bug report
Assigned:
Reporter:
Created:
28 Oct 2011 at 15:26 UTC
Updated:
29 Apr 2026 at 03:53 UTC
Jump to comment: Most recent
Comments
Comment #1
dwaine commentedSounds like you've covered the basics. Next step is to see if the .wsdl document is being loaded nicely. First test is to make sure that the www.weather.gov server is serving that document by the pasting URL into a browser. If the document is available, then the next step is to verify the server that hosts your Drupal code base is allowed to access that document. If you have command line access and the box is Unix based you can use the wget command line tool to complete that test. If you are still having trouble post the results of these two tests in hopes the results give us a better clue to the problem.
Thanks
Dwaine
Comment #2
Saoirse1916 commentedThanks for the response -- I did check the URL and it loads fine for me. I have also been working with the host on the problem and they've verified that SOAP is installed properly and have attempted a SOAP connection using a different URL which works fine. When we use http://www.weather.gov/forecasts/xml/DWMLgen/wsdl/ndfdXML.wsdl it throws the above error. The host attempted to connect to that URL with Lynx from the server itself without problem.
Comment #3
Saoirse1916 commentedI've been working with my webhost (ANHosting) and this is the final response that I received:
We apologize for the very long delay in our response. There have been varying levels of technicians looking into this problem for you and as far as can be determined we don't believe this to be an issue on our side at all. We have tried testing everything that could of been thought possible to stop this from working and nothing seems to have helped correct the issue. We have tested another soap script in the same folder and it worked just fine and without issue. So soap is indeed enabled and working on that part of your site. We have tried editing out and in lines into the php.ini file, both server wide and your custom one in the php.ini and nothing worked so we can rule out a php setting. We have created a phpinfo page and it confirms soap being installed and working just fine. We have also checked your drupal admins settings including where the temp folder is set to and nothing there should be affecting this. We have even tried completely installing a new version of the drupal module and it still fails with the same error.
I apologize but we are not able to find anything on our end through server configuration that would stop this from working. Most likely something is wrong inside of the module or with the file that the SOAP script is connecting to and grabbing data from. It is a very odd looking URL by any means. Please ask the administrator/developer of this module to investigate and confirm that this is working for them, because even writing my own custom SOAP scripts to connect to http://www.weather.gov/forecasts/xml/DWMLgen/wsdl/ndfdXML.wsdl and they will not work at all.
Please let us know if you have any questions. Thank you.
Comment #4
David4514 commentedI do not know if this is related. Two days ago this was working and today it is not. I am using 7.x-1.3 instead. The error message shown is:
Is it possible that something just changed that makes opening this stream no longer work? This is now failing both on the ISP where a test site is located and on a local server at my home where as little as two days ago they were both working. I did not try yesterday.
[Edit: 11-19-2011 6:00pm EST - This may be a NWS website issue. It is just taking 4 to 5 minutes to access their web page. Before I invest any more time, I think I will give it a day to see if the problem resolves itself]
[Edit 11-22-2011 5:15pm EST - All seems well now. The problem that I was experiencing was a nws site issue.]
Comment #5
Saoirse1916 commentedI've come up with a workaround which uses the NOAA RSS feed saved as a .txt file, called with cURL rather than SOAP. I've wrapped it into a module and I wonder if it would be worthwhile to combine with this module since it's effectively a duplication of features, just with a different approach. Might be useful in cases like mine when SOAP doesn't work for one reason or another.
Comment #6
tomdavidson commentedI think the issue is that the module was not following the 301 redirect to the new url. I offer a patch that updates the url and makes it configurable at #1925268: outdated data source , #3.
Comment #7
aaronrus commentedClosing as outdated — the branch this issue was reported against is no longer supported. The module is now maintained on the 2.x-dev branch.
Thank you for your report!