error msg

[kwojcie]

Hi Brett,
appreciate your knowledge you share in many places...

I have a small problem, that I am sure I could figure out if I wasn't a blockhead when it comes to server setup... I get this message:

You don't have permission to access /traxis-images/css/ on this server.

even though everything is set right. I made sure that those directories are both read/write/execute enabled,
and all of that good stuff. I mean - traxis accesses images from the directory, why can't it access the css folder?

Thank you in advance for your time,

kjw

[Brett_Tabke]

Can you call a file from the browser? Something like:

[yourdomain...]

That should tell you if everything is configured correctly.

Many servers are setup NOT to allow http requests for images or html within cgi-bin space.

[kwojcie]

That's the thing,
I am getting images, no problem, out of an image directory that I created within the cgi-bin dir.
At the control panel, all of the images show up right.

And yet when I run it, appearently I cannot access
images/css - now, It could be that the css directory
that is accessed might not work, but I checked it out as best as I knew before I bothered you, and it seemed
that all of the normal attributes applied. I am baffled. I could send you the url, username and password, nd you could see for yourself...

I don't know if that would qulify as me helping you troubleshoot your program, or simply you helping me
(ok it would be the latter...) lol

[Brett_Tabke]

Point your image directory to [searchengineworld.com...]
and see what happens.

[kwojcie]

Ok,
that worked, although I guess you don't want the hits to your server...

However, a new problem cropped up.
I ran traxis - I got an error message saying that the traxis log file couldn't be loceted. This was the log file the path of which Traxis autodetected when I first ran setup.

So I went back and put in the path to my "regular" log file, and the script worked no problem, except that the reports showed zero hits - zilch.

At the bottom, there was this little interesting bit of info:

Oldest line found: 07/05/2000 - 5:35:13pm
Newest line found: 12/31/1969 - 4:00:00pm

?????

Could that be somehow related to the problem...?

[Val]

:) Some prehistoric server are you on ..

[EX_S]

Okay, I've got the same problem.

The log files aren't being writen anywhere (at least nowhere I can find them :) ). Has anyone found the cause of the problem?

There are no errors when any of the scripts are run; when I generate reports, they are empty, and get the same interesting bit of info:

Newest line found: 12/31/1969 - 4:00:00pm

My configuration settings are as follow:

traxis-global.cgi:
$data_path = "/home/jamesyu/public_html/cgi-local/traxis/data/";

traxis-counter.cgi:
$traxis_dir = "/home/jamesyu/public_html/cgi-local/traxis/";
$data_path = "/home/jamesyu/public_html/cgi-local/traxis/data/";

Has anyone found the cause/solution for this? Thanks in advance for the help.

James

[EX_S]

Oops! Don't worry about that! I viewed the source of my shtml page and found out the SSI call wasn't executing, so now it's off to fix that [an error occurred while processing this directive] error instead.

James

[bartek]

I get the same error. [an error occurred while processing this directive]. SSI is confirmed to work, all permissions are set as required. The /data/ dir has 755 permissions, although I can't seem to change the permissions on the files within it. Would the files also need 755 to work?
Also, just like kwojcie, I get: Oldest line found: 08/28/2000 - 09:44:53am Newest line found: 12/31/1969 - 7:00:00pm

[EX_S]

It could be any number of things. Here's what solved the problem for me. I changed the SSI call from:

<!--#include virtual="/home/jamesyu/public_html/cgi-local/traxis/traxis-counter.cgi"-->

to:

<!--#include virtual="/cgi-local/traxis/traxis-counter.cgi"-->

Probably my understanding of SSI is a bit lacking. I would have thought the full server path was correct, but apparently it wasn't. I also checked the pathways in both the global and counter modules, and uncommented the line in the global file.

The newest line 1969 is an indicator that there are no logs to work with.

James