Archive for the tag 'Troubleshooting'

Whenever possible place any executable scripts inside the cgi-bin directory.

When uploading scripts via FTP make sure to always use ASCII mode. If you are doing a server to server FTP transfer use BINARY mode.

The first line in all PERL scripts must contain the path to PERL which is: #!/usr/bin/perl

Directories and scripts should both executable. Usually the permission level 755 is the best. All files and directories where CGI will be executed must NOT be world or group writeable and must be at least user executable.

Data files that scripts will read/write must NOT be group or world writeable.

Make sure that you DO NOT modify the permissions of the cgi-bin itself. This will cause all scripts to fail. If the permissions have be altered, chmod the cgi-bin back to 755.

Check the code. Frequently there may be a line not closed with “;” or a routine that is not closed.

Make sure that all modules and ‘include files’ required by the scripts are located on the server and are in the proper locations.

Check that your CGI/Perl script is outputting the necessary HTTP headers. To do that in Perl, just below the “shebang” line (#!/usr/bin/perl), type the following line.


#!/usr/bin/perl
print "Content-type: text/html\n\n"


Add a “-w” to the first line of your script. (Example: # !/usr/bin/perl

Most FTP programs allow you to change the permissions of files on the server. You may also use the command shell (SSH) and use the command directly. Example: chmod 755 myscript.cgi

Troubleshooting Ensim Upgrade or Installer Issues

Problem : The host name of the server is incorrect.

Refer the log file /var/log/ensim/installer..-.log to review the list of successful and unsuccessful events recorded during the upgrade.

Check the file /etc/sysconfig/network. The host name must be a fully qualified domain name. See the following example.

Correct: myhost.mydomain.com

The file /etc/hosts should contain the host name and IP address of your server. If it does not, use an editor to modify the file.

—/etc/hosts begin file–
127.0.0.1 localhost.localdomain localhost
1.2.3.4 myhost.mydomain.com myhost
—/etc/hosts end file–

Troubleshooting Issues with ensim installer

Issues that you may encounter during the installation. You may refer to the log file /var/log/ensim/installer..-.log for details.

Example:

During installation, the following message is displayed:

check_hostname

This means The host file is incorrect.

The file /etc/hosts should contain the host name and IP address of your server (see the following example). If it does not, use an editor to modify the file.

Example

—/etc/hosts begin file—
127.0.0.1
localhost.localdolocalhost
1.2.3.4 myhost.mydomain.com
myhost

—/etc/hosts end file—

where 1.2.3.4 is the IP address of myhost.mydomain.com

Also check the file /etc/sysconfig/network. The host name must be a fully qualified domain name.

See the following example.

Incorrect: myhost
Correct: myhost.mydomain.com
SBDavid

Troubleshooting BIND

Troubleshooting BIND

There are a number of tools that are available to assist with testing and troubleshooting problems with your BIND configuration. The simplest tool on most systems is the host command, which simply performs an address lookup or a reverse address lookup. More complete information can be gathered using dig.

The simplest usage of host is to lookup an address, or a name.

$ host serverbuddies.com
serverbuddies.com has address 67.228.43.85
serverbuddies.com mail is handled by 0 mail.serverbuddies.com.

Ask for the name servers that are authoritative for a domain by using the -t ns command line option..

$ host -t ns google.com
google.com name server ns2.google.com.
google.com name server ns3.google.com.
google.com name server ns4.google.com.
google.com name server ns1.google.com.

The MX record can be retrieved by using the -t mx option.

$ host -t mx yahoo.com

Just like host, it is possible to query your default system resolver, or you can query a name server specified on the command line. For example, I could query my local name server about the nostarch.com domain.

$ dig @192.168.1.1 serverbuddies.com

More at http://doxfer.com/