1

I have written a bash script that periodically checks a directory for newly added .ear files and copies them to the respective JBoss server's deploy directory.Before copying, it checks if JBoss is running, and stops it if it is.After copying the file,it removes the older .ear files if any,and starts JBoss.
I am trying to have this script executed via a web page. i.e provide a link to the users, clicking on which, the entire process gets executed.So far I am not able to get the desired result, though manually executing it works.
I'm getting the following error in http logs:

warn] [client 127.0.0.1] Timeout waiting for output from CGI script /var/www/cgi-bin/auto.sh, referer: http://localhost/

Would appreciate if someone could shed some light on how to go about it.

1
  • isn't this what jboss' autodeploy does? :)
    – rytis
    Feb 8, 2010 at 15:06

2 Answers 2

2
  1. The CGI script will run with the userid of the webserver, which might not be the userid of the person who was testing it. Have you considered that?

  2. The CGI script needs to print a header and some output like "Success, thanks for using auto.sh".

 echo "Content-type: text/plain"
 echo 
 echo "Success, thanks for using auto.sh"

If its too clunky trying to do CGI from the shell, wrap it in a little bit of perl or python which have libraries to deal with CGI.

An alternative approach would be to leave a token in a file or database column that tells it to run, and then have it either activate from cron or have it constantly run and look for the token.

Also, depending on how the web server is set up, your CGI only gets so long to run before it times out...

3
  • +1 Started to type the same thing as token/cron but then noticed you already said it :-) Feb 8, 2010 at 14:57
  • 1
    A proper content-type would be text/plain, not just text Feb 8, 2010 at 20:51
  • Thanks. I edited the answer to reflect your contribution.
    – Paul
    Feb 8, 2010 at 23:13
0

Thanks a ton, ~drpaulbrewer and others.It was certainly a permission issue.Have managed to get it working by giving the necessary permissions to apache in sudoers file.Was also getting a '[error] [client 127.0.0.1] standard in must be a tty, referer: http://localhost/' error in the logs, which I got rid of by excluding apache from the 'Defaults requiretty' section in the sudoers file.

Though I had initially thought of running the script as a cronjob, it was not implemented, since we are running this on a test environment, and have multiple instances of JBoss running simultaneously.We thought it would be better to let the users trigger the script manually, hence this approach.

Thanks again. Nagaraj

You must log in to answer this question.