[Umlaut-general] installation problems continued...

[Jonathan Rochkind]

Something odd is indeed going on. I can't quite figure out from the 
'evidence'.

Is your SFX open to the world? I can try installing an Umlaut locally 
and pointing it at your SFX and seeing if it works. If it does, that 
would rule out some incompatiblity between your SFX and Umlaut, and 
suggest that somehow your Umlaut is not installed properly. 

If you have any way to give me shell access to your machine, I'm happy 
to help troubleshoot it.

I am on vacation for the first half of next week, but I do want to help 
you with this stuff.

I am aware that the Umlaut installation process is not as simple or as 
trouble-free as it ought to be, and would like to attend to that at some 
point, Rails3 should help.

Jonathan

Seaman, Graham wrote:
> Going through the log I found the initial problem was:
>
> FATAL: NameError (uninitialized constant JSON::SAFE_STATE_PROTOTYPE):
>
> This was because I had a recent JSON gem installed (1.4.3); I
> uninstalled it, and installed 1.1.3. Unfortunately the symptoms are
> still the same although the error message about JSON isn't there any
> more.
>
> I've copied the log from a session to
> http://navtis.pastebin.com/q5vHtJmC
> I'll send the corresponding 3 screenshots off list.
>
> Graham 
>
> -----Original Message-----
> From: umlaut-general-bounces at rubyforge.org
> [mailto:umlaut-general-bounces at rubyforge.org] On Behalf Of Jonathan
> Rochkind
> Sent: 30 June 2010 16:17
> To: umlaut-general at rubyforge.org
> Subject: Re: [Umlaut-general] installation problems continued...
>
> Hmm, this is weird. I don't entirely understand it, not really enough 
> info in your report for me to have an idea I'm afraid. Any way you could
>
> give me login to your machine, and I can try to figure it out for you?
>
> Otherwise, can you start up Umlaut, trigger the error, and then send me 
> the entire Umlaut log file?
>
> Sorry it's not working as well as it should, apparently.
>
> I have no idea what's up with that "String.pm" thing.  That's a perl 
> file, there's no Perl in Umlaut, not sure where that's coming from. Oh 
> wait, that's you looking at SFX error logs.  That's probably not 
> neccesary. Oh wait, maybe it is, I see from your description that maybe 
> it is Umlaut somehow not dealing with SFX properly. Or not. I'm not sure
>
> I completely understand even what you're reporting I'm afraid. You could
>
> also send me a screen-cast of what you're doing to encounter the error, 
> maybe?  Just brainstorming for ways to send me more info without giving 
> me access to your server.
>
> What version of SFX are you running?
>
> Jonathan
>
> Seaman, Graham wrote:
>   
>> Hi,
>>
>> After a 3 month delay I finally got back to installing Umlaut. I'm
>>     
> running on Centos, and have restarted my install with the version of
> umlaut from trunk. The initial setup/database load seems to have gone
> ok, and I can start umlaut up (but am having to use ./script/server
> -p8080 as port 3000 is firewalled).
>   
>> I've got institution.yml set up to use SFX only. The inital umlaut
>>     
> page appears, and I can successfully carry out a search on a journal
> title; the results look fine.  But if I click on any of the journal
> titles or the corresponding sfx links in the results page, I get an
> exception thrown. My rails debugging skills are nil, and I'm a bit
> drowned in all the diagnostic/logging info that comes back, with the
> result that I'm not sure if I now have a code problem, a connection
> problem, or a configuration problem. As far as I can tell the context
> object values in the link seem sensible, and if I strip off the
> parameters (ie. everything following http://localhost:8080/resolv?) in
> the link, and feed them direct to sfx I get back the full xml
> ctx_obj_set. Tailing the SFX apache error log tells me that String.pm is
> complaining about an uninitialized value in a string comparison but
> nothing else - and these warnings come up on a lot of working searches
> anyway.
>   
>> The error reported on the umlaut web page seems to be an error in the
>>     
> error reporting, rather than the underlying problem: I'm getting
> NoMethodError in Resolve#index from 'resolve/_service_errors.rhtml at
> line 12,  where the problem seems to be that
> dispatch.service.service_types_generated is a nil object.
>   
>>
>> Any suggestions as to what to look at next?
>>
>>
>>
>> Thanks
>>
>>
>>
>> Graham
>>
>>
>>
>>
>>
>>
>>
>>
>>   
>>     
>
> _______________________________________________
> Umlaut-general mailing list
> Umlaut-general at rubyforge.org
> http://rubyforge.org/mailman/listinfo/umlaut-general
> _______________________________________________
> Umlaut-general mailing list
> Umlaut-general at rubyforge.org
> http://rubyforge.org/mailman/listinfo/umlaut-general
>