Views
 |
Debugging Tips |
|
General Debugging Tips including 3.5-Apollo Specific |
|
I have always advocated go in hack Uniform Server around and break it. This little chap is the result of a session where I could not resolve the reason why I broke it. I decided to animate his eyes and antenna serves as a reminder not to go in heavy handed. |
This page contains a few tips that will assist you in debugging on Uniform Server.
What’s my IP?
There are many on line services that will provide your IP address for example click this link: Whats My IP you cant miss it, top right big and bold.
On the above page try the “More Info About You” link.
Checking your server is externally accessible
You have popped your servers on-line and wondering if they are accessible from the Internet. Google translate is ideal for this, in order to translate a page it needs access to your servers (Exactly what we need and fully automated.).
- Go to Google Translate page: Google Translate
- Select Text and Web top menu bar (Automatically selected for you)
- Bottom of page you will find a text field Translate a web page enter a valid address for your page:
- It accepts IP addresses for example http://89.007.251.102/test/index.html
- Or domain names for example: http://fred.com/test/index.html
- Select any language from the drop down list.
- Click Translate
- If the page is accessible it is translated.
- If its not accessible a blank page is displayed.
Quick and effective that’s what I like.
Apache not starting - httpd.conf syntax check 1
If you have made changes to Apache configuration file httpd.conf and find Apache no longer runs the chances are you made a typo? Apache will not run if there is a syntax error in the configuration file however the virtual drive (default W) may have been created if so you can use the following to check for syntax errors:
Open a command prompt (run > type cmd > click Ok)
|
This will run Apache and check the configuration syntax.
|
Any syntax errors will be reported.
Apache not starting - httpd.conf syntax check 2
If Apache fails to start its more than likely the virtual drive will not be created. The following batch file will create a virtual drive and test the syntax. This batch file may be run with or without the servers running.
Save the following to a file named uc_apache_syntax.bat place the file in folder Uniform Server double click to run.
:Batch file to check Apache configuration syntax :Creates a virtual drive if it does not already exist :Optionally removes the virtual drive created :Place in folder ”Uniform Server” with other bat files :File: uc_apache_syntax.bat :Author: Mike Gleaves :Version: 1.0 :Date: 25-1-2008 @echo off :== Set drive to W change this as required set Disk=W :== create virtual disk and map folder udrive to it subst %Disk%: "udrive" :== Clear screen hides error if already created cls :== select drive, change to folder, run apache command, %Disk%: cd usr\local\apache2\bin apache.exe -t :== User option to remove virtual drive echo. echo. SET remove_disk=N SET /P remove_disk=Remove virtual drive %Disk% type Y or y press enter = IF %remove_disk%==N goto :NOTREMOVED IF %remove_disk%==Y goto :REMOVE IF %remove_disk%==y goto :REMOVE :NOTREMOVED echo. echo "Disk has not been removed" goto :END :REMOVE echo. echo "Disk removed" subst %Disk%: /d :END echo. pause
File details and notes:
|
Notes:
If the servers are not running a virtual disk drive is created the default is “W” if you are using a different disk change the line: set Disk=W accordingly.
Note: Command -t must be run from the virtual drive and not from where Uniform Server was extracted otherwise the following error is generated:
Hence these lines are required in the batch file they change the working disk and directory:
|
Apache - Log files
Apache logs all its transactions to the following file access.log and errors to error.log these are located in folder:
*\Uniform Server\udrive\usr\local\apache2\logs
when debugging Apache problems make this your first port of call .
Mod Rewrite - Log file
Logs all Mod Rewrite transactions to a file using “RewriteLog” and “RewriteLogLevel” directives. These instructions cannot be placed in an htaccess file they must be placed in Apache’s main configuration file httpd.conf preferably in a Vhost.
|
|
Note: Only enable these lines while testing do not use on a live server because logging will quickly eat your disk space. Comment out the lines (by placing # at the start of the line) or delete after testing, you may also wish to delete the log file (rewrite.txt).
| | Ric |
