hosting at positive internet

[adrians]

Hi,

I'm trying to get v6 connecting to my webspace at positive internet (standard linux, apache, php, mysql setup).

While testing I can get it to put files into the cgi-bin but when it tries to execute them it gives me an 'Internal Server Error'.

The secure server error log says "[Wed Dec 11 15:03:24 2002] [error] [client 195.157.130.161] Premature end of script headers: /home/gsb/secure_html/cgi-bin/sts000001.pl"

What should I be checking here? I'm pretty sure most of my network settings are ok, but not sure what to check now.

Any help greatly appreciated.

Thanks,

Adrian
men&motors tv channel
http://www.menandmotors.co.uk

[cdicken]

I will run this past the support team here and see if they can come up with anything.

[Ben]

I've recommended that Adrian change one of the network settings. The error should be resolved this afternoon when he refreshes the site.

Ben Popplestone
Actinic Software

[NeilM]

I'm having similar problems.

Reading the http error log, the perl scripts have to execute permissions set, is there a way that catalog can do this when it uploads the files?

:confused:

[cdicken]

Neil

What type of server are you uploading to? NT or Unix? This will dramatically affect how much control Actinic has over the perl permissions on the web site.

[NeilM]

Chris,

Linux.

Thanks

Neil

[cdicken]

Quoting from the Advanced User Guide, these are the permissions required by Actinic on a Unix server.

------------------------------

If the customer is running in normal mode, the minimum permissions required are:

'cgi-bin' directory
- 755
'acatalog' directory
- The FTP user ID must have full permissions (7)
- The effective user ID of the CGI scripts must have read/write permission
- The effective user ID of the Web server must have read permissions. Depending on the set up, the permissions could be 700, 760, 764, 746, or 706. 700 and 760 are probably the most common.

If you encounter problems with permissions when trying to upload your store for the first time, try setting the permissions on the effective user ID of the web server to '777'. Once your store is uploaded, progressively tighten up the permissions on the web server to one of the settings recommended above, or until your store no longer functions.

-------------------------

How useful you find that will depend on how familiar you are with Unix servers. However, your web host should be able to use this information to make sure your web space is configured correctly.

[NeilM]

Chris

In your answer "The effective user ID of the CGI scripts must have read/write permission" this is the problem the perl script is not executable, and therefore apache will not execute it. Do I have to use a cgi wrapper that means it does not have to be execuatable?

Thanks

Neil
:confused:

[cdicken]

When I want to get some scripts working, I log on to the site with CuteFTP (I am using Cute FTP 4.0) and go to the 'cgi-bin'. I then do a right click on all my .pl files in my 'cgi-bin' and select CHMOD. Then in the 'Manual' field enter '755'. Then on the *.pm files I do the same but do '644'.

[NeilM]

Chris

So do I, but, isn't catalog supposed to do this for me?, I don't want my Business customers to have to do this.

Can't catalog do this, then?

Neil

[cdicken]

Most of the time, yes. But every server is different and sometimes the server does not allow Actinic to do it.

[NeilM]

Chris

So how can I tell why this has not done it, is there an upload log or something?

Thanks

Neil

[cdicken]

There is not an upload log as such, but a settings test will give you some idea about what is happening.

When you click the 'Test' message in 'Advanced | Network Setup', what message do you get?

[zmagyar]

This message in the error log used to be indicate that the path to perl is not correct. Can you double check that please?

Zoltan
Actinic

[adrians]

Hi everyone,

Chris' tips on chmod'ing the .pl's after upload has worked for me.

Positive Internet (for me at least) have a policy as a web host that is 777 is not allowed, but there is a way around it. 755 did the trick.

Thanks for your help,

Adrian

[NeilM]

All

I have sorted out my problem, the FTP server proFTP does not allow chmod by default. Once I set it...bingo

Thanks

Neil