Re: channel archiver on 64 bit? Re: archive data server

[Ralph Lange <Ralph.Lange@gmx.de>]

James,

The Debian packages by Michael Davidsaver are available for 32 and 64
bit Intel architectures.
Naturally, the source packages, that these binary packages are compiled
from, do compile on 32 and 64 bit.
Both are available from the BNL repository at
http://epics.nsls2.bnl.gov/debian/

~Ralph


On 19.11.2012 16:43, John William Sinclair wrote:
> James,
>
> I built the archiver for a 64bit cpu and had to make quite a few changes.
>
> For XML support, I have only updated the Xerces code so if you are
> using something else you may have other issues.
>
> I have attached an archive of all files (only in the message sent
> specifically to James).
>
> Best,
> John Sinclair
>
> On 11/19/2012 10:33 AM, James F Ross wrote:
>> I haven't been working on any updates...  I'm just trying to get all
>> aspects of the channel archiver to run, which it is doing for the
>> most part.  It is just the data server that I'm having trouble with.
>>
>> For the moment, I'm just trying to find out why there is an undefined
>> symbol in the library libxmlrcp_cgi.so.3 when I try to run
>> ArchiveDataServer.cgi.  The complete error message is:
>>
>> [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!
>> James
>>
>> On Mon, Nov 19, 2012 at 10:29 AM, Kasemir, Kay <kasemirk@ornl.gov
>> <mailto:kasemirk@ornl.gov>> wrote:
>>
>>     Hello:
>>
>>     > The archiver won't compile on 64 bit…
>>     I believe there are sites who updated the sources to compile on 64
>>     bit.
>>     In 2010, the channel archiver sources have been moved from an SNS
>>     repository to source forge so that other sites can easily
>>     contribute such updates.
>>     If you have been working on 64 bit updates and need write access
>>     to the SF repo, please let me know.
>>     Or if  you prefer to publish your updates by other means, please
>>     contact Andrew so he can list that on the EPICS extensions web site.
>>
>>     Thanks,
>>     Kay
>>
>>     From: James F Ross <james.falconer.ross@gmail.com
>>    
>> <mailto:james.falconer.ross@gmail.com><mailto:james.falconer.ross@gmail.com
>>     <mailto:james.falconer.ross@gmail.com>>>
>>     Date: Monday, November 19, 2012 09:56
>>     To: Kasemir Kay <kasemirk@ornl.gov
>>     <mailto:kasemirk@ornl.gov><mailto:kasemirk@ornl.gov
>>     <mailto:kasemirk@ornl.gov>>>
>>     Cc: "tech-talk@aps.anl.gov
>>     <mailto:tech-talk@aps.anl.gov><mailto:tech-talk@aps.anl.gov
>>     <mailto:tech-talk@aps.anl.gov>>" <tech-talk@aps.anl.gov
>>     <mailto:tech-talk@aps.anl.gov><mailto:tech-talk@aps.anl.gov
>>     <mailto:tech-talk@aps.anl.gov>>>
>>     Subject: Re: archive data server
>>
>>     I should add that the ldd command indicates that I have the right
>>     library file from the old computer.
>>     James
>>
>>     On Mon, Nov 19, 2012 at 9:44 AM, James F Ross
>>     <james.falconer.ross@gmail.com
>>    
>> <mailto:james.falconer.ross@gmail.com><mailto:james.falconer.ross@gmail.com
>>     <mailto:james.falconer.ross@gmail.com>>> wrote:
>>     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
>>     <james.falconer.ross@gmail.com
>>    
>> <mailto:james.falconer.ross@gmail.com><mailto:james.falconer.ross@gmail.com
>>     <mailto:james.falconer.ross@gmail.com>>> 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 <kasemirk@ornl.gov
>>     <mailto:kasemirk@ornl.gov><mailto:kasemirk@ornl.gov
>>     <mailto:kasemirk@ornl.gov>>> 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><http://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
>>     <http://archiver.info><http://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
>>
>>
>>
>>
>