Re: [cobalt-users] cgi-wrapper error

[Alfredo <alfredo@xxxxxxxxxxxxxxx>]

> Unfortunately this didnt help at all, cause after I removed the /, the
> counter spit out an error to the browser (an error occured processing this
> directive)


Well, at least we know that's not the problem. You have the script in 
your top site directory, right? Not in any sub-directory?

Well, since we started the exchange here, let's just go one round 
more before you go looking elsewhere.

What's crazy is that the scripts are working but still spitting out 
the error. Now, this is good because the script is working (LOL) but 
I understand that you want to figure out what that error is there 
(after all, there could be some precaution to take to make sure the 
scripts KEEP working).

I still think there may be other sub-routines that are failing 
somehow. For instance, when there's a "response page" for form-mail 
that doesn't come up, it mails the info but still shows an error. 
That's only one example, though. Form-mail does a lot of stuff: 
emails, returns a response page, sends a response, logs, etc. If one 
of those routines is failing, you'll get that error (although it will 
appear that the scripts works since it's emailing the info). With a 
counter, it could be some kind of logging function (don't know what 
script you're using).

Some more things to check before I give up:

1 -- Check to make sure your sendmail configs in the scripts are set to

/usr/lib/sendmail

Mind you, /usr/sbin/sendmail will also work because it's an alias but 
that may be causing a slight cough in the script.

2 -- Check the script configurations for "referrer" blocks 
(configurations that block certain domains or IP addresses from using 
them). Make sure you're complying with what the script calls for 
(sometimes they need BOTH domain name and IP address or domain name 
AND web site name).

3 -- Check permissons. For some scripts, when the permissions for the 
script are set to allow group execution, rather than 755, it will 
work but could show an error. I also use a script that I originally 
set to 755 and it worked but also returned errors in the log. Try 
switching those permissions from what you have and see if cgi-wrap 
still logs an error.

4 -- Full and relative paths and urls. If you're making calls to the 
script with a relative url in the form mail form itself (the html 
form), this MAY produce an error if the form is in,for instance, a 
user's web site (the ~username ones) or if it's in a directory that 
doesn't have world permissions.

Another possibility is the paths in the scripts themselves: if they 
are relative, try using full paths and urls.

If none of that helps, I'm out of gas. If you want to try these 
things and need more help from me, I'm happy to help off-list. Just 
email me.

Alfredo


--
People-Link/Institute for Mass Communications
www.people-link.org
Communications for a Better World...and for the People Who are Building One!
Members, Local 1180, Communications Workers of America, AFL-CIO