Defining Mysterious Script Errors

There are a few ways. They do not _always_ offer more info, but many times they do. As such they are worth the time to try and should be done before emailing technical support.

• View your script error logs located in your /logs_cgi/ directory. (Once you've fixed the error, you may also want to delete those logs to save on disk space. The server will recreate the log file for you if/when needed.)
  
  
• Use the CGI Script Debugger available in your CNC under Troubleshooting or, if you prefer, you can use telnet to perform the troubleshooting for you by following the instructions below:
  
  Telnet into your account.
  Type: cd /big/dom/xdomain/cgi-bin/ {Enter} (or the path to the directory where your script is) (where xdomain=xyourdomain)
  
  ls {Enter} (Will show you a list of everything in that directory)
  
  perl -cw scriptname.pl {Enter}
  (where scriptname.pl is the name of the script you wish to check)
  
  This is a fantastic little script that will let you know if the syntax of your script is ok. If it is not, it will usually point out exactly where the syntax is flawed and suggest a fix for it.

• Permissions for scripts in the cgi-bin must be set to 755 to work on the FutureQuest^® servers. See How do I change file permissions? (chmod)
  
  
• All scripts must be uploaded in ASCII mode - See Uploading In ASCII
  
  
• Check to make sure the script does not contain any embedded carriage returns
  
  
• Make sure your CGI script does not exceed 30 seconds of runtime if run via Apache
  
  
• Make sure your script does not consume more than 32 MB of RAM per instance if run via Apache
  
  

Back to Top