error 500 running abyss, but apache's fine...?!

[strinxx]

Hi everybody!
I know, there are lots of topics regarding error 500, I spent a few days already, crawling this forum... but I seem to be the only one with this thing:
I perfectly set up the php settings within Abyss - several times, tried out whatever might have helped (but didn't...).

My setup is a Debian-system (Kanotix), installed everything as far as I was able to (this is brandnew stuff here, but I really like it!)... Abyss is running fine, except the php-script. error 500, "broken pipe"

I tried Xampp with php-support, everything is ok. PHP no problem.
(my w2k-server works perfectly with Abyss and this webfilbrowser script, by the way)

I would sooo love to stay with Abyss, such a great piece of software!
Any ideas?
(php-5.1.1 installed)

Thank you so much in advance for your help!
Mike

[TRUSTAbyss]

Do you mind telling us what script is giving you this broken pipe?

[strinxx]

Thank you for this fast reply!
The php-script is called "wegbfilebrowser", by webfilebrowser.org.
I downloaded it from sourceforge.

Mike

[aprelium]

strinxx,

Your problem seems to be related to your PHP interpreter declaration and not to the script itself (which works fine on any PHP enabled web server including Abyss Web Server). How have you declared PHP support in Abyss Web Server? What is the executable you are using as your PHP interpreter?

Can you create a simple phpinfo.php file which contains:

[strinxx]

well...,

if I browse http://127.0.0.1/phpinfo.php, than it says "can't connect to server..",
if I get to http://127.0.0.1:8000/phpinfo.php I get "error 500".

I declared the interpreter as follows:
/opt/lampp/bin/php-5.1.1
script paths /*.php

If I typ in a shell "/opt/lampp/bin/php-5.1.1 /home/.../htdocs//index.php
it seems to work fine, script is running, no problems shown...

Does this help?

[admin]

strinxx,

We thought you were using the Windows version.

Can you please clear the executable (x) bit of your scripts by executing the command in htdocs/:

[strinxx]

Yes, unfortunately!
Same matter!

[strinxx]

Hey Guys!

After fooling around for several hours, I just set the interprete-type to "standard"
...and it worked! Any ideas what that's supposed to mean?
Thanxx anyway!
Mike

[aprelium]

strinxx,

Glad to know that the problem is solved now.

When PHP was first developed, it was using a wrong method to communicate with web servers. This method was not conforming to the CGI standard.
Because it became so popular, people were used to this problem and new versions of PHP were still by default configured to follow this wrong method (although the odd behavior was fixed).
That's why we have added "PHP Style" in the Interpreter Type. It's simply to tell Abyss Web Server to communicate with PHP using this "wrong" method.
But some versions are built and configured to use the standard method (and are fully conforming to CGI). That's the case of your PHP. In such a case, setting the Interpreter Type to Standard is required.
_________________
Support Team
Aprelium - http://www.aprelium.com