Ok, I've found all of the libraries that ArchiveDataServer.cgi calls, but I'm having an issue with one of them.  As mentioned before, I've had to transfer the channel archiver to a new machine.  The difficulty is that the new machine is 64 bit linux while the old one is 32 bit.  The archiver won't compile on 64 bit, so it was compiled on 32 bit linux and transfered.  For the most part, it is working, save for ArchiveDataServer.cgi

I've transferred the libraries that are needed by ArchiveDataServer.cgi, but I'm getting an error with one of them.  Any help with getting past this would be most welcome.

The error:
[Mon Nov 19 09:36:24 2012] [error] [client 127.0.0.1] /var/www/html/archive/cgi/ArchiveDataServer.cgi: symbol lookup error: /usr/local/lib/libxmlrpc_cgi.so.3: undefined symbol: xmlrpc_registry_new
[Mon Nov 19 09:36:24 2012] [error] [client 127.0.0.1] Premature end of script headers: ArchiveDataServer.cgi

Thanks very much!
James Ross

On Thu, Nov 15, 2012 at 10:21 AM, James F Ross <[email protected]> wrote:

Hello everyone
Ok, I found out what the problem was.  ArchiveDataServer.cgi is failing to find some library files that it needs.  This is probably because this is a new computer and things aren't completely set up the way they were on the old machine running the archiver.  I'm in the process of tracking down the libraries it is complaining about and making links to them in /usr/lib and /usr/local/lib which seems to be working.

Thanks for all the help!  I'll ask if I have further questions
James

On Tue, Nov 13, 2012 at 10:52 AM, Kasemir, Kay <[email protected]> wrote:

Hi James:

>my current issue seems to be that the archive data server is not working.

Correct, that's what this means:
>"java.lang.IllegalArgumentException: Couldn't execute the archiver.info<http://archiver.info> request java.io.IOException: Unexpected Response from Server:  Internal Server Error"

The old archive manual,  https://ics-web.sns.ornl.gov/kasemir/archiver/manual.pdf, has sections about the setup and testing of the ArchiveDataServer.cgi (4.3.1, 4.3.3, ..).
You can try to connect to the ArchiveDataServer.cgi via "telnet" to see if the web server is executing it at all.
If it's running, it will also update a file /tmp/archserver.log (something like that, don't remember the exact name in /tmp) with the recent requests. If the archiver.info request already fails, that should indicate that the ArchiveDataServer.cgi is really not invoked at all. Your web server might return the binary bits of the ArchiveDataServer.cgi file instead of executing it.

-Kay