If you followed the Five easy steps to installation and are having troubles THis page
may be able to help you solve your problem.
Trouble Shooting Server Errors
If you get a 500 Error (Internal Server Error), then one of the
following is likely the problem:
- The path to Perl is wrong. you may consult your ISP's documentation, contact your
system administrator or try /usr/bin/perl, /usr/local/bin/perl, /usr/bin/perl5 or
- You did not transfer the script in ASCII mode. Do this and transfer the file
- You did not set the permissions on the file to executable as describe in step 2.
- The file path you provided in step 3 (namely the path for $hw_cgi_dir_url)
may be incorrect. Double check tomake sure this path is correct.
If you get a 404 Error (File Not Found), then the URL that you entered
does not correspond to the location where you put the hw2test.cgi script in step 2.
You should double check the URL even the spleen and capitalization of the URL.
If you get a 403 Error (Forbidden), then you most likely forgot to
change the permissions to 0755(executable) or you did not put the script in a directory
with the appropriate CGI permissions.
If you see the source code of the script and not an information page,
then either the extension that you gave the script is incorrect (if you tried
".cgi" try ".pl" instead), or you did not put the script in a
directory with appropriate CGI permissions.
Trouble Shooting Other Errors
So you didn't get a common server type error, so now whats the problem?
Cannot Connect to the IWIN and/or NWS servers error
- The National Weather service or IWIN server is down. This happens sometimes but is not
often. You can double check the HAMweather site to see if the main HAMweather demo
is working. If it is then this most likely is not the problem.
- If you are getting this error only and you are using the sockets http_mode (the default)
to connect to the Weather servers you may try using the LWP mode. Simply goto
the web based admin, click the system settings link and you can select the select the
LWP::Simple or LWP advanced mode for HTTP mode. Alternatively, you can open up the
hwconfig.txt file and set the $http_mode variable to 1 thus it would look like: NOTE: This mode
requires that you have the LWP Modules installed.
Fetching page error : -hwERR Can't connect socket:Unknown error or
-hwERR Can't connect socket:Address family not supported by protocol family
- These error are most likely caused if your servers setup will not allow the sockets
http_mode (the default) to connect to the weather servers. In this case you will
need to use the LWP http_mode. This requires that you have the LWP modules install
on you server. (You can test for them using the Pre-Install Setup Program) If the LWP
modules are installed then goto the web based admin, click the system settings link and
you can select the select the LWP::Simple or LWP advanced mode for HTTP mode.
Alternatively, you can open up the hwconfig.txt file and set the $http_mode variable to 1
thus it would look like: NOTE: This mode requires that you have the LWP Modules installed.
Document Contains no Data (Netscape Users) or a Blank Screen (Internet
This error happens when the HAMweather script outputs the appropriate headers and
nothing else. The normal reasons for failure are:
- When Using HAMweather Pro the GD.pm module is not installed. When
creating/updating the dynamic maps HAMweather uses the GD.pm module to create them.
If this modules is not on the server the script will fail before it can output naything
but the headers, thus causing this error. Test that you have the GD.pm module
installed on your server using the pre-install test script (hw2test.cgi) included in the
HAMweather package. NOTE: If you have
installed the GD.pm locally to your web site and not server wide then you will need to add
the 'use lib' command near the top of the hamweather.cgi file to let hamweather know where
the GD.pm module was installed. the 'use lib' line should look similiar to:
use lib '/path/to/the/local/GDpm_directory',
- When using HW Pro and GD.pm is installed then you may have HW configured to use the
GD.pm incorrectly. If you are using GD.pm 1.19 or older you need to make sure HW is
using GD.pm in GIF mode and if you are using GD.pm 1.20+ then you need to make sure
HW is using GD.pm in PNG mode. You can check/set this setting by going to the web
based admin, click on System settings and select the correct GD.pm version number next to
the GD.pm Version setting. Alternatively you can open up the hwconfig.txt file and
set the $gd_version variable to 0 for GD.pm 1.19 or older or set it to 1 for gd.pm 1.20
and newer. If you do not know what version of GD.pm you have installed you can use
the pre-install test script provided in the distribution to find out.
- Permissions and/or filepaths couldbe incorrect. Double check these.
Note: As of Version
2.0 Beta 2.03 HAMweather uses version checkig that should help in stopping a lot of the
Document Contains no Data (Netscape Users) or a Blank Screen (Internet Explorer Users)
error for if the GD.pm is not installed or the permissions to the needed library files or
incorrect an error will be displayed.
Error loading files XXXXXX
- This error is caused when HAMweather tries loading a library file that does not exist.
It is usually followed by a more detailed error message that will provide more insight
into the failure.
- This error can occur if HAMweather tries to load a library file that is older than the
one required. If this is so you will see an erro discripting labeling what file the
error was with witht he current files version number and the needed version number.
Make sure you have the latest versions of the HAMweather files.
HAMweather Debug Mode
HAMweather contains a debug mode that will give you information about your server,
parameters passed to HAMweather and other pertinent HAMweather information. To use
this mode simply browse to the hamweather.cgi filr and pass the debug=1 parameter.
The URL would look similiar to the following URLs:
When you access the debug mode of HAMweather you will see the perl environmental
variables, the passed parameters, versions of HAMweather and all loaded hamweather library
files and other pertinent information. If for some reason you do not see this
information then the Debug ability may have been turned off. You can turn debug mode
capability on by going tothe web based admin, clicking the system settings link, and then
selected the "On with 'debug=1' paramter" or "Always On" options next
to the 'Debug mode" setting. Alternatively, in the hwconfig.txt file there is a
variable named $allow_debug. This variable should be set to 0 to turn on debug
ability or 1 to turn off. Changing that line the hwconfig.txt file to the following
would turn debug ability on:
$allow_debug = 0;
This debug information maybe useful in solving your HAMweather problems. When you
are done debugging if youwant to turn the debug ability off simply change the $allow_debug
value to '1' in the hwconfig.txt file.
The Support Center
If all else fells try out the HAMweather support Center at http://www.hamweather.com/support/ Near the
botomof this page you will be able to goto the Support Forums or you can goi directly to
them at http://www.hamweather.com/cgi-bin/support/hamboards.cgi
NOTE: Once at the support center you can
view past threads for up to 365 days. SImple click the options link and select how
many days worth of past threads to view.
Hmmm.. I need some trouble shooting help.