what to do if the server don't convert \r\n to \n?

[anqi]

Hi,

I now have a linux-based dedicated server. I am going to migrate my actinic store to the server. But the perl script can't run after uploading. After numerous times of uploading, deleting, refreshing, etc, etc, I found the reason may be:

The server doesn't convert \r\n to \n?

That means if I upload "helloworld.pl" from windows by ftp in ascii mode, it can't run (of course, i chmod 755 or 777). If i create helloworld.pl at server side directly, it can run.

I upload "helloworld.pl" to some other linux-based sites (share hosting), it can run. So I guess my dedicated server may set some parameters as default which prevent conversion of \r\n to \n, and finally prevent actinic's script from working.

Anyone had the same experience?

[NormanRouxel]

Actinic should manage this fine. It uploads the Perl scripts and makes sure that they're linux / unix safe.

Try running the Web / Network Setup / Test. This uploads some test scripts and executes them.

Your issue was probably with the editor you used to write your Hello World! script. I use Editpad and it has an option to use CR only, CR/LF or LF only.

[anqi]

I get 500 Internal Server Error when adding to cart or search, etc. the same symptom as uploaded "helloworld.pl"

[anqi]

error log: Premature end of script headers: ss000001.pl

[NormanRouxel]

What does Web / Network Setup / Test produce?

[anqi]

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.

[anqi]

HTTPPROXYMODE 0
HTTPPROXYADDRESS
HTTPPROXYPORT 80
HTTPPROXYUSER
HTTPPROXYPASSWORD
FTPPROXYMODE 0
FTPPROXYADDRESS
FTPPROXYPORT 21
FTPPROXYUSER
FTPPROXYPASSWORD
SCRIPTID 123
SCRIPTEXT .pl
SMTPHOST
WEBSITEURL http://www.mydomain.com/
IGNOREPASSIVEERRORS true
USERELATIVECGIURLS true
PATHTOPERL /usr/bin/perl
USEENHANCEFTP false
FTPCLIENTTIMEOUT 15000
FTPRETRYDELAY 3000
FTPSILENT false
FTPMAXRETRIES 3
FTPCONNECTTIMEOUT 25000
SMTPAUTHREQUIRED false
SMTPUSERNAME
SMTPPASSWORD
CATALOGURL http://www.mydomain.com/acatalog/
CGIBINURL http://www.mydomain.com/cgi-bin/
PATHFROMCGITOCATALOG ../acatalog/
CODEBASE ./
FTPHOST xxx.xxx.xxx.xxx
FTPUSERNAME myusername
FTPPASSWORD mypassword
PATHTOCGIBIN /public_html/cgi-bin/
USEPASSIVEFTP true
FTPPATHFROMCGITOCATALOG

[NormanRouxel]

These would be OK for a lot of hosts, but it of course depends on your specific server's Perl and cgi-bin setup.

If you post who your server ISP is, that may help others to answer.

[anqi]

Yes, this time is godaddy.

Although initialising actinic on a new space is always frustrating, I had successful experience with a windows server, and linux share hostings...

Does a specific linux version matter?

[anqi]

i was told if linux server was running cvs, it would affect conversion of \r\n when using ftp. i have to run dos2unix command on server after actinic updates the site in this case.

i know it's not actinic's fault because even helloworld.pl uploaded by other ftp software won't work until it is "dos2unix"ed. but if actinic could take care of such a hassle, it would be great.

[Bruce]

Anqi,

I will pass this to development and add a vote to the wishlist for you.

Kind regards,

[anqi]

I have been used to running an extra command unix2dos every time after Actinic finishes sending base files to the server for months.

However, today something happened - when Actinic was sending base files, there's timeout error and asking me Abort, Retry, or Ignore. I clicked Retry several times but it kept throwing timeout errors. Then I had to click Ignore. Actinic stopped responding for a while then gave out a message:

Turning to ASCII mode.

Something like that.

Because of timeout errors, I cancelled uploading and restarted uploading. This time everything completed successfully. I found I needn't run unix2dos to make perl scripts working again. Very strange, isn't it? I don't know I should be happy or sad. Be happy because I needn't worry about unix2dox from now on; be sad because Actinic behaviors more and more out of my control.

[CapCityCom]

I am using a virtual dedicated godaddy server as well. I am running into constant problems with just "testing". I wasnt getting anywhere with it until I entered in the settings you had. The only problem is Im getting a error message saying the following:

THE SERVER NAME OR ADDRESS COULD NOT BE RESOLVED.
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.


I entered exactly what you had except replaced the ftp settings and URLs with my owen address. You wouldnt happen to know what my problem might be? I contacted GODADDY and they arent helping my out one bit.

[Mike Hughes]

Double posting doesn't help anybody.

Mike

[anqi]

godaddy virtual server might be different.

please try to turn off firewall on your server first.