Page 1 of 1

Unix installation error

Posted: Tue Jul 11, 2006 6:09 pm
by jorgeverav0
Hello,

Trying to install webinator in my linux - red hat server and I get this error:
--------------------------------------------------------
CGI extension [ENTER for none]: .cgi
Checking dir with a web fetch...failed, will try again
Trying again with file...*** Failed ***
The URL http://mydomain.com/cgi-bin/texis.cgi/i ... html?-dump
could not be fetched.
Possibly the CGI URL prefix (http://mydomain.com/cgi-bin)
or the CGI extension (.cgi) is wrong.
The web server response was: HTTP/1.1 500 Internal Server Error
--------------------------------------------------------

Checking the server error log this appear:

Symbolic link not allowed: /home/httpd/vhosts/mydomain.com/cgi-bin/texis.cgi
Premature end of script headers: texis.cgi

Thanks in advance for your help.

Unix installation error

Posted: Tue Jul 11, 2006 9:30 pm
by John
At that point the rest of the install should be OK, so you can copy the texis executable from the installdir/bin directory to /home/httpd/vhosts/mydomain.com/cgi-bin/texis.cgi and it should work there. You should be able to test by going to the URL http://mydomain.com/cgi-bin/texis.cgi/

Unix installation error

Posted: Wed Jul 12, 2006 11:13 am
by jorgeverav0
Thanks Jhon,
I copied the file texis from installation dir: /usr/local/morph3/bin/texis to the cgi-bin dir: /home/httpd/vhosts/mydomain.com/cgi-bin/

but one thing, I didn't find a texis.cgi, so I try with and without the cgi extension in the cgi-bin dir, and nothing. Still getting: 500 Internal Server Error and in the server error log the same: Premature end of script headers: texis.cgi

any ideas????

Unix installation error

Posted: Wed Jul 12, 2006 11:44 am
by John
The .cgi may or may not be needed, depending on your webserver configuration.

If there anything in the vortex.log or monitor.log in the INSTALLDIR/texis directory? It sounds as if at least the executable is being found now.

Unix installation error

Posted: Wed Jul 12, 2006 1:10 pm
by jorgeverav0
No, nothing in log files.

Unix installation error

Posted: Wed Jul 12, 2006 2:05 pm
by Kai
Make sure that installdir/texis/vortex.log and monitor.log are read/writable by all, so that any errors can be logged. Then try it with texis.cgi again. If that fails, try running ./texis -version from the command line in installdir/bin to verify that it runs (run this as the CGI user, not root).

Unix installation error

Posted: Wed Jul 12, 2006 7:25 pm
by jorgeverav0
Thanks. I have gived permissions log files and now I see this in monitor.log

======================================================
200 2006-07-12 17:53:45 (18143) Texis Monitor version 05.01.1151518054 starting
100 2006-07-12 17:53:45 (18143) Warning: real user is root; changed to effective user
200 2006-07-12 17:53:45 (18143) Generating default Webinator license
200 2006-07-12 17:53:45 (18143) License Violation (License Server Contact)
200 2006-07-12 17:53:45 (18143) Contacting license server
200 2006-07-12 17:53:46 (18143) Successful reply from license server
200 2006-07-12 17:53:46 (18147) Database Monitor on /usr/local/morph3/texis/testdb/ starting
200 2006-07-12 17:54:20 (18143) Texis Monitor received signal 15 (SIGTERM); will exit
200 2006-07-12 17:54:20 (18143) Texis Monitor exiting
200 2006-07-12 17:54:21 (18147) Database Monitor on /usr/local/morph3/texis/testdb/ exiting
======================================================

I run ./texis -version and is working.

Now before installation I put a texis.cgi file in the cgi-bin directory and the installation detected and renamed, but still not working. The installation didn't put the new texis.cgi

Following Jhon advice I copied texis executable from the installdir/bin directory to the cgi-bin directory and still nothing...

Unix installation error

Posted: Mon Jul 17, 2006 12:28 pm
by mark
Please clarify "nothing".

What happens when you try to access the texis.cgi you copied in? Did you make sure to preserve permissions and ownership on it?

If you do the install again what errors do you get?

Is there anything new in the vortex.log or monitor.log or webserver error log?