EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  <20052006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  <20052006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Re: can't connect to ArchiveDataServer
From: Devin Bougie <[email protected]>
To: [email protected]
Cc: Kay-Uwe Kasemir <[email protected]>, Paul Sichta <[email protected]>
Date: Wed, 7 Dec 2005 12:16:44 -0500
Many thanks to Kay and Paul for pointing us in the right direction. We were actually missing the "ScriptAlias" directive. I believe the httpd setup as outlined in the Channel Archiver manual should contain the line:
ScriptAlias /archive/cgi "/var/www/html/archive/cgi"


Thanks again,
Devin

On Dec 6, 2005, at 12:46 PM, Kay-Uwe Kasemir wrote:
On Dec 6, 2005, at 12:24 , Devin Bougie wrote:

Hi All,

We have built the 11/07/2005 snapshot of the Channel Archiver with EPICS R3.14.7 . Everything seems to be working until we try to connect to the ArchiveDataServer.

Using the java Archive Viewer, the following error appears on the console when trying to connect to ArchiveDataServer.cgi :
Fatal error parsing XML: org.xml.sax.SAXParseException: expected Element


and the java Archive Viewer gui displays the following error:
java.lang.IllegalArgumentException: Couldn't execute the archiver.info request
java.io.IOException: org.xml.sax.SAXParseException: expected Element


ArchiveDataClient.pl gives a somewhat different error:
[dab66@ees101 dab66]% ArchiveDataClient.pl -u $URL -a
Archives:
not well-formed (invalid token) at line 1, column 0, byte 0 at / usr/lib/perl5/vendor_perl/5.8.0/i386-linux-thread-multi/XML/ Parser.pm line 185

The very likely cause: Your web server is not properly configured to recognize CGI scripts. So the URL used to run the ArchiveDataServer.cgi does not execute ArchiveDataServer.cgi and hence return some form of XML. Instead, you get a dump of the executable file.

Try this to verify:

telnet my_web_server_host 80
GET /archive/cgi/ArchiveDataServer.cgi HTTP/1.0<RETURN>
<RETURN>

If you get an error message wrapped into ugly XML,
you're fine.
If you get garbage that looks like a binary dump
of the ArchiveDataServer.cgi program,
look for anything with 'cgi' or 'CGI' or 'Cgi' in your web server
config file. Per default, newer Apache versions have cgi
disabled (commented-out) and you have to re-enable it.

-Kay



Navigate by Date:
Prev: Re: can't connect to ArchiveDataServer Kay-Uwe Kasemir
Next: ca_host_name function in CA Liyu, Andrei
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  <20052006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: Re: can't connect to ArchiveDataServer Kay-Uwe Kasemir
Next: ca_host_name function in CA Liyu, Andrei
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  <20052006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 02 Sep 2010 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·