[OPEN-ILS-DEV] restoring evergreen to an empty state

[Nella Lall]

Dan,

Thanks for this pointer, this file seemed to be the problem, once I 
edited it with the proper ejabber domain/username/password and a proper 
logfile location, I was able to do the autogen.sh properly and 
successfully.  Now I can get the older version staff client working 
against the server (it was able to re-register my workstation name which 
was the first problem I brought to the list).  Thanks so much to 
everyone for all your help!

Nella

Dan Wells wrote:
> Hello Nella,
>
> I don't think it is time to throw in the towel yet.  What are the contents of your .srfsh.xml file?  You may want to re-copy the example file ( cp /openils/conf/srfsh.xml.example ~/.srfsh.xml ) and then edit it to match your ejabber domain/username/password and add a proper logfile location. The logfile can be in any directory where your user has write permission.
>
> I might also try at this point just doing a stop_all, running "ps -aef | grep opensrf" a few times to verify that everything has stopped (and killing anything that might not stop in a timely manner), then do a start_all, then run the autogen.sh again.
>
> Hope this helps,
> DW
>
>
>   
>>>> Nella Lall <ndlall at ucalgary.ca> 3/14/2008 3:40 PM >>>
>>>>         
> Jason,
>
> Sorry, I was unable to get back to you immediately.
>
> Well, I don't even get to the srfsh# prompt.  My error messages are instant:
>
> evergreen-admin at eg-server:~$ pwd
> /home/evergreen-admin
> evergreen-admin at eg-server:~$ ls -lt .srfsh.xml
> -rw-r--r-- 1 evergreen-admin evergreen-admin 379 2007-11-14 12:03 .srfsh.xml
>
>
> evergreen-admin at eg-server:~$ sudo /openils/bin/srfsh
> Unable to fopen log file /path/to/log/srfsh.log for writing; logging to 
> standard error
> srfsh 2008-03-14 11:27:22 [INFO:9528:osrf_system.c:267:] Bootstrapping 
> system with domain 127.0.0.1, port 5222, and unixpath (none)
> Unable to fopen log file /path/to/log/srfsh.log for writing; logging to 
> standard error
> srfsh 2008-03-14 11:27:22 [WARN:9528:transport_session.c:386:] Received 
> <stream:error> message from Jabber server
> Unable to fopen log file /path/to/log/srfsh.log for writing; logging to 
> standard error
> srfsh 2008-03-14 11:27:22 [DEBG:9528:socket_bundle.c:367:] removing socket 3
> Unable to bootstrap client for requests
> Unable to fopen log file /path/to/log/srfsh.log for writing; logging to 
> standard error
> srfsh 2008-03-14 11:27:22 [ERR :9528:srfsh.c:21:] Unable to bootstrap 
> client for requests
>
>
> And the ps -aef command gives:
>
> evergreen-admin at eg-server:~$ ps -aef | grep opensrf.settings
> opensrf   6047  6045  0 Mar11 ?        00:00:02 OpenSRF master 
> [opensrf.settings]
> opensrf   6053  6045  0 Mar11 ?        00:00:00 OpenSRF listener 
> [opensrf.settings]
> opensrf   6135  6047  0 Mar11 ?        00:00:00 OpenSRF drone 
> [opensrf.settings]
> opensrf   6150  6047  0 Mar11 ?        00:00:00 OpenSRF drone 
> [opensrf.settings]
> opensrf   6153  6047  0 Mar11 ?        00:00:00 OpenSRF drone 
> [opensrf.settings]
> opensrf   6215  6047  0 Mar11 ?        00:00:00 OpenSRF drone 
> [opensrf.settings]
> opensrf   9543  6047  0 11:29 ?        00:00:00 OpenSRF drone 
> [opensrf.settings]
> 1000      9545  9415  0 11:29 pts/1    00:00:00 grep opensrf.settings
> opensrf  19898 19896  0 Mar12 ?        00:00:00 OpenSRF listener 
> [opensrf.settings]
> opensrf  20004  6047  0 Mar12 ?        00:00:00 OpenSRF drone 
> [opensrf.settings]
> evergreen-admin at eg-server:~$
>
>
> New insights with this information?  Is it time to give up and do a full 
> re-install of evergreen???
>
> Nella
>
> Jason Etheridge wrote:
>   
>>>  So, I think things are bit happier but the Connection to Settings
>>>  failed??  What does this new message mean?
>>>     
>>>       
>> For some reason, the fieldmapper.pl script called by autogen.sh was
>> not able to get a response from the opensrf.settings server that
>> should be running after you have started services.
>>
>> Let's see if we can reproduce that error from a different angle.
>> Assuming you have configured the .srfsh.xml file, run
>> /openils/bin/srfsh  (you will have to do this as the user associated
>> with the home directory where you placed .srfsh.xml)
>>
>> You should get a prompt that looks like this:  srfsh#
>>
>> Enter the following command and press enter: request opensrf.settings
>> opensrf.settings.host_config.get "localhost"
>>
>> But instead of localhost, use the fully qualified domain name for your
>> installation.
>>
>> If srfsh can connect to the settings service with that command, it
>> should give a lot of indented data marked up with curly brackets,
>> colons, and quotation marks.  On my system, the first thing I see is
>> Received Data: { "z3950"
>>
>> If it can't connect, it should say something simpler, like Unable to
>> communicate with service opensrf.settings
>>
>> If you would, paste us the first ten lines or so of the output from
>> that (or all of it if it's small).
>>
>> This will tell us where to look next for figuring out what's going on.
>>
>> Another thing to do is try: ps -aef | grep opensrf.settings
>>
>> You should see OpenSRF processes listed.  Go ahead and paste these as well.
>>
>> Thanks!
>>
>>   
>>     
>
>
>