Announcement

**NormanRouxel** · 19-May-2004, 06:24 PM

I built a new system today (Apache 1.3 flavour - I've not used Apache 2) and followed the AUG and it's all working without problems.

The header line in the .pm files is irrelevant I think. These files are included in other files so that line isn't used.

Have you got a cgi-bin off of the htdocs directory? That's where the AUG recommends it. You also need these lines modified in httpd.conf

Code:

    ScriptAlias /cgi-bin/ "C:/Apache/htdocs/cgi-bin/"

    #
    # "C:/Apache/cgi-bin" should be changed to whatever your ScriptAliased
    # CGI directory exists, if you have that configured.
    #
    <Directory "C:/Apache/htdocs/cgi-bin">
        AllowOverride None
        Options None
        Order allow,deny
        Allow from all
    </Directory>

Norman

**0-zone** · 20-May-2004, 12:10 PM

Hi Norman..

File positions are:

Apache 2

[apache config]
DocumentRoot "C:/Usr/Simon/Work/Apache_Local_pages"

scriptAlias /cgi-bin/ "C:/Usr/Simon/Work/Apache_Local_pages/cgi-bin/"

<Directory "C:/Usr/Simon/Work/Apache_Local_pages/cgi-bin">
AllowOverride None
Options None
Order allow,deny
Allow from all
</Directory>

I do a lot of PHP & mySQL work and I find the apache 2 very stable, (have been running a standalone apache server [of varous flavours] for a couple of years now)

I can see your point about the .pm files ("require" overriding the headers as an include)

and whilst the cgi-bin is a sibling of the acatalog folder rather than
at the parent level, to my mind this should have little impact.. unless- god forbid - paths are hard coded in Actinic (say bye-bye to generic encapsulation)

I will try altering the structure to add the htdocs folder layer..and report back ; However I think I know the answer to that one already

What gets me, is the fact that a 500 error is usualy the perl path,
yet when you check [test] the network settings in Actinic the two Actinic temp test .pl files work fine and no error issues forth...
Presumably meaning the perl is working fine.

This is why I wonder if the current version of ActivePerl is incompatable with the Actinic code.

I can find litttle or no mention on the web of the
"Perl Command Line Interpreter has encountered a problem and needs to close"
in relationship to anything, which suggests to me (by inferance) that this is a fairly rare occurance (normaly if you post up an error message you will get a mirriad of hits)

I do not think it is a missing Perl module (MD5 perhaps) - because
Actinic appears to draw the relevant code from other files (md000001.pl etc) and it would be a fairly fundimental ommission from the AUG if the instalation of such a module where ommited.

Also the AUG appears to show a different warFTP release from
the one that others have got to work succesfully (1.65)

I am concerned about the CHMOD issue ;- but reason that if Actinic has not even reached the stage where it attempts to set the folder and file permissions, it is for the moment irrelvant:-
I base this on the assumption that it should work since the warFTP login it is using has full permisions to admin all files and folders, and I am using the settings you and others have specified.
[warFTP folder settings: (1.65)
Sysadmin
[User ] C:\Usr\Simon\Work\Apache_Local_pages\cgi-bin : Delete Execute List Read Write
RH[User ] C:\Usr\Simon\Work\Apache_Local_pages : Delete List Read Write Maps to rootdir + Applies for subdirs.]

I would like to try the (exact) same setup as you have - or at least confirm that we are both using the same version of ActivePerl and warFTP with exactly the same settings...

The other concern that I have is that this is a perl/ XP os issue
(see threading concerns on the instalation of the mod_perl for Apache)
and the warning from Jarle Aase that warFTP "is not supported" under XP....

My guess on this whole lot is that either :
I am doing something incredibly stupid (in which case I will look very red faced as a professional programmer) because I cant see the wood for the trees
or
the standalone instructions needs to be re-addressed in relationship to new software releases and or system requirements

in fact after tinkering for a while I have made maters worse (deleting the acatalog and cgi-bin then recreating them in dreamweaver makes the file permissions totaly unsetable in XP)

I originaly did the setup by doing a straight FTP of the cgi-bin and the acatalog folder from the clients site and then trying to do an update from within Actinic....

and now Actinc falls over on the network test......"actinic cant set permisions for acatalog"

I may have to blow it all away and start again to get the network test to work again including working with warFTP 1.8 (Current) to see if I can get back to where I was before....

I can feel myself slowly sinking into the mire here :-)

Any advice is much appreciated

Simon

**cdicken** · 21-May-2004, 03:32 PM

Just to confirm, I have set up an XP machine with the standalone server and it has worked fine. I also always use the latest Perl and Apache versions as they become available just to make sure of avoiding issues like yours.

Could you confirm where you are aiming to put the 'acatalog' directory please?

You say your cgi-bin is within:

C:\Usr\Simon\Work\Apache_Local_pages\cgi-bin

This means Actinic should be trying to put the 'acatalog' folder within:

C:\Usr\Simon\Work\Apache_Local_pages\acatalog

It also means that Apache_Local_pages should be the folder you get when you go to http://localhost/ (i.e. your document root). Could you confirm this please? Is 'Apache_Local_pages' in your system the equivalent of the default Apache 'htdocs' folder?

Also, where is your Apache 'httpd.conf' file stored?

I have a lot of questions (rather than answers) because your Apache working directory is different than the one in the AUG. It may be that we can never get it working and you may have to think about reinstalling Apache to C:\Apache2 and then having a document root of C:\Apache2\htdocs.

**0-zone** · 21-May-2004, 06:33 PM

Originally posted by cdicken
Just to confirm, I have set up an XP machine with the standalone server and it has worked fine. I also always use the latest Perl and Apache versions as they become available just to make sure of avoiding issues like yours.

Could you confirm where you are aiming to put the 'acatalog' directory please?

You say your cgi-bin is within:

C:\Usr\Simon\Work\Apache_Local_pages\cgi-bin

correct

This means Actinic should be trying to put the 'acatalog' folder within:

C:\Usr\Simon\Work\Apache_Local_pages\acatalog

correct

It also means that Apache_Local_pages should be the folder you get when you go to http://localhost/ (i.e. your document root). Could you confirm this please? Is 'Apache_Local_pages' in your system the equivalent of the default Apache 'htdocs' folder?

correct

Also, where is your Apache 'httpd.conf' file stored?

C:\Program Files\Apache Group\Apache2\conf\

I have a lot of questions (rather than answers) because your Apache working directory is different than the one in the AUG. It may be that we can never get it working and you may have to think about reinstalling Apache to C:\Apache2 and then having a document root of C:\Apache2\htdocs.

realy just to carify (+ not egg sucking :-)):
C:\Usr\Simon\Work\Apache_Local_pages\
is the Apache root where documents are served from (in 'httpd.conf)
C:\Usr\Simon\Work\Apache_Local_pages\cgi-bin
(in httpd.conf)
C:\Usr\Simon\Work\Apache_Local_pages\acatalog
is the Actinic catalog position.
Access from:
http://localhost/

there "should" be no technical diference from the default Apache 'htdocs' folder since Apache only references anything
below root... (once in the httpd.conf)

I may have to do a reinstall to the default (all it is is a copy and paste of all the files below C:\Usr\Simon\Work\Apache_Local_pages)

But I fail to see how (or why) this could affect Actinic (since all my other PHP and CGI and mySQL stuff works fine...) unless there are hard coded paths in Actinic.... we have 2 sites deployed - one sits under htdocs another under httpdocs :- so i would have thought the folder above cgi-bin and acatalog was transparent to actinc.....

thanks for lending an ear Chris :-)

**cdicken** · 24-May-2004, 10:18 AM

unless there are hard coded paths in Actinic....

No - Actinic works fine on any number of server setups. The problem is probably some conflict between all the different things on your PC which, unfortunately, we are unable to provide support for.

Do you have a 'clean' machine that you could try a default install on - just to show it does work?

**0-zone** · 24-May-2004, 01:24 PM

Originally posted by cdicken
No - Actinic works fine on any number of server setups. The problem is probably some conflict between all the different things on your PC which, unfortunately, we are unable to provide support for.

Do you have a 'clean' machine that you could try a default install on - just to show it does work?

Chris;
The Pc was bought three weeks ago; and ony has what I need to
work with on an every day basis

Apache
php
perl
Actinic
Macromedia (Flash,Dreamweaver)
Photoshop
Office

I will be trying an install from apache default....

Announcement

Standalone still not working

Standalone still not working

Comment

Comment

Comment

Comment

Comment

Comment