SSI doesn’t seem to be working in Plesk. How can I determine what the problem is?
# Make sure that SSI is enabled for the domain within the Plesk interface. This can be enabled/disabled within the domain’s physical hosting screen.
# Make sure that the file has the proper extension (by default):
# Make sure that the file has the proper ownership. The owner should be domain_ftp_user and the group should be psacln.
# The apache configuration file httpd.conf should contains the lines:
AddType text/html .shtml
AddOutputFilter INCLUDES .shtml
Look in the domain’s Apache error_log file at /var/www/vhosts/serverbuddies.com/statistic/logs/ for more information.
Reference: http://parallels.com/
Understanding the dig command
dig will let you perform any valid DNS query, the most common of which are A (the IP address), TXT (text annotations), MX (mail exchanges), and NS nameservers.
The command dig is a tool for querying DNS nameservers for information about host addresses, mail exchanges, nameservers, and related information.
This tool can be used from any Linux (Unix) or Macintosh OS X operating system. The most typical use of dig is to simply query a single host.
$ dig serverbuddies.com
; <> DiG 9.5.1-P3 <> serverbuddies.com
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 39970
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 13, ADDITIONAL: 0
;; QUESTION SECTION:
;serverbuddies.com. IN A
;; ANSWER SECTION:
serverbuddies.com. 14043 IN A 67.228.43.85
A quick way to just get the answer only is to run the following command:
dig serverbuddies.com +short
Use the following command to get a list of all the mailservers for mt-example.com:
dig serverbuddies.com MX +noall +answer
Use the following command to get a list of authoritative DNS servers for mt-example.com:
dig serverbuddies.com NS +noall +answer
How to determine system log settings for a Linux server?
Usually the /var/log/messages file is used for the regular system messages.
It is possible to find which place is used by a Linux system for logging from the /etc/syslog.conf or /etc/rsyslog.conf configuration files:
or
How to check if Perl script engine is enabled and working for a domain?
To check this we can use a simple script like this:
#!/usr/bin/perl
print “content-type:text/html\n\n”;
print “<html>\n”;
print “<head />\n”;
print “<body>\n”;
print “Hello World!\n”;
print “</body>\n”;
print “</html>\n”;
#
Save the content into a text file and save in the domain web-accessible folder (like $HTTPD_VHOSTS_D/domain.tld/httpdocs) on the server with .pl extension (test.pl for example). Then try to open the file via browser by the http://domain.tld/test.pl URL. The domain name should be resolved for this to work.
The test looks successful if a page shows the “Hello World!” string.
If an error or full script listing is visible, it means that Perl script engine is not configured for the domain properly.
Debugging on part(s) of the bash script
Using the set Bash built-in you can run in normal mode those portions of the script of which you are sure they are without fault, and display debugging information only for troublesome zones. Say we are not sure what the w command will do in the example commented-script1.sh, then we could enclose it in the script like this.
set -x # activate debugging from here
w
set +x # stop debugging from here
You can switch debugging mode on and off as many times as you want within the same script.
