Announcement

Collapse
No announcement yet.

premature end of script errors

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    premature end of script errors

    We recently had to rebuild our Linux server and since that time on reloading our sites from a back up we now continually get a "merge file error" at the end of any upload and CGI-Scripts are unable to be executed properly.

    We use a dedicated server through Pipex and I the actinic test script and our formail.pl script work so Pipex are satisfied with the perl / cgi set up and say it has to be actinic. I have been through every post on here related to this issue. I have refreshed, changed to cgi, changed id from 1 to 2, deleted all files and refreshed, tried passive, tried without passive and basically came to the conclusion that i picked a bad day to give up glue sniffing.

    If anybody can help me I would be grateful. I have attached a jpg of our settings.
    Attached Files

    #2
    Is this still the same or have you been able to get the upload working? Are you tryig to upload or refresh the site. I would suggest trying a refresh. Do this after you have tested the Network Settings and have got them to pass succesfully. If the test on the settings creates errors then please post the error messages too.

    Kind regards,
    Bruce King
    SellerDeck

    Comment


      #3
      premature end of script errors

      Still the same errors Bruce and I have tried refreshing and uploading the site.

      If I copy my old .pl & .pm files over the CGI scripts works even though on testing it still says CGI errors...this is ater succesfully confirming network settings that are shown below.

      If I try and purge & refresh get a mail merge error. If I change a paramter and uplaod the relevant scripts then no longer execute and again I have to coopy them over from a backup on the server.

      Not sure if this is relevant but I also am getting a lot of errors on the server as shown below:

      [Wed Sep 13 12:48:15 2006] [notice] caught SIGTERM, shutting down
      [Wed Sep 13 12:48:16 2006] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
      [Wed Sep 13 12:48:17 2006] [notice] Digest: generating secret for digest authentication ...
      [Wed Sep 13 12:48:17 2006] [notice] Digest: done
      [Wed Sep 13 12:48:17 2006] [notice] mod_python: Creating 4 session mutexes based on 256 max processes and 0 max threads.



      Network settings:

      HTTPPROXYMODE 0
      HTTPPROXYADDRESS
      HTTPPROXYPORT 80
      HTTPPROXYUSER
      HTTPPROXYPASSWORD
      FTPPROXYMODE 0
      FTPPROXYADDRESS
      FTPPROXYPORT 21
      FTPPROXYUSER
      FTPPROXYPASSWORD
      SCRIPTID 1
      SCRIPTEXT .pl
      SMTPHOST mail.activ8uk.com
      WEBSITEURL http://dropeasy.co.uk/
      IGNOREPASSIVEERRORS true
      USERELATIVECGIURLS false
      PATHTOPERL /usr/bin/perl
      USEENHANCEFTP true
      FTPCLIENTTIMEOUT 5000
      FTPRETRYDELAY 3000
      FTPSILENT false
      FTPMAXRETRIES 3
      FTPCONNECTTIMEOUT 15000
      SMTPAUTHREQUIRED false
      SMTPUSERNAME
      SMTPPASSWORD
      CATALOGURL http://dropeasy.co.uk/acatalog/
      CGIBINURL http://dropeasy.co.uk/cgi-bin/
      PATHFROMCGITOCATALOG ../acatalog/
      CODEBASE ./
      FTPHOST dropeasy.co.uk
      FTPUSERNAME dropeasy
      FTPPASSWORD *********
      PATHTOCGIBIN /home/dropeasy/cgi-bin/
      USEPASSIVEFTP true
      FTPPATHFROMCGITOCATALOG /home/dropeasy/acatalog/

      Comment


        #4
        You did not say what happens when you use the test button in Advanced | Network Settings - do you get an error? Or does it pass?

        One thing I noticed on the site - although without a test login ID and password it was not possible to check very far, was this code
        Code:
        <TITLE> DROPEASY If you have an account, please login below or click <a href="http://www.dropeasy.co.uk/register.html">here</a> to register .</TITLE>
        <META HTTP-EQUIV="refresh" CONTENT="7; URL=http://dropeasy.co.uk/acatalog/LATEST_ITEMS.html">
        <BASE HREF="http://dropeasy.co.uk/acatalog/"><META NAME="ACTINICTITLE" CONTENT="If you have an account, please login below or click <a href="http://www.dropeasy.co.uk/register.html">here</a> to register .">
        The embedded double quotes is impossible to parse correctly, so on some pages you end up with the text "here</a> to register ." showing above the beginning of the body of the page.

        It's a waste of time having the same thing in the title - this appears in the frame surround of the window and is not clickable. The link really needs to go somewhere in the body of the html page.
        Bill
        www.egyptianwonders.co.uk
        Text directoryWorldwide Actinic(TM) shops
        BC Ness Solutions Support services, custom software
        Registered Microsoft™ Partner (ISV)
        VoIP UK: 0131 208 0605
        Located: Alexandria, EGYPT

        Comment


          #5
          Error messgae on network |advanced test is:

          Actinic received a server error from the web server. The CGI scripts are not executing properly on the server. Run Web | Configure Web Site Details... to review your web site configuration.

          followed by:

          The test script failed to execute on the web server. The error could be caused by several things. Check the path to the Perl shell, the CGI script extension, the path to CGI-BIN, and the CGI-BIN URL. This error could also occur if your web site is out of disk space or your web server is not configured to accept POSTs to CGI scripts.

          This is despite the ts00....pl file being executed correctly using the wizard.

          Thanks for the heads up on the html error ;O)

          Started to look at SUEXEC as the potential issue but the warning signs about this are making me a tad nervous.

          Comment


            #6
            premature end of script errors

            To give you an update after playing around with various test scripts the hosting company support have managed to get the server working.

            Same old problem as posted here on numerous occasions regarding ASCII upload in the httpd file. They "claim" they only had to restart the vsftpd but this has been restarted on numerous occasions.

            All i know is that it is now working and my wife will like me a little more now.

            if you are getting an error message like this:

            bash: ./ss000001.pl: /usr/bin/perl^M: bad interpreter: No such file or directory

            It is due to the ftp upload being binary....

            Comment


              #7
              Got the "premature end of header" error message. test.cgi went fine, so I had to assume that the server is ok. After messing around with it for a longer period of time I just changed the following in the ca012345.pl file :

              Commented the following line :

              use strict;

              to

              #use strict;

              uploaded, and everything worked fine again. To be honest I dont know a lot about Perl and I have not a clue what I have been doing, but it seems to do the trick.
              ##########

              rolo2912
              Not so advanced web solutions

              Comment

              Working...
              X