Re: [OPEN-ILS-GENERAL] Error in autogen.sh on Fedora

[Blake Henderson]

Bogna,

This is a set of commands that might help for stopping and starting 
everything:


sudo su -
/etc/init.d/apache2 graceful-stop
/etc/init.d/apache2-websockets stop
apache2ctl-websockets stop
su - opensrf
osrf_control --localhost --stop-all
oils_ctl.sh -a stop_sip
exit
ps -ef | grep OpenSRF | grep -v apache | grep -v grep | awk '{print $2}' 
| xargs kill -9
ps -ef | grep Clark | grep -v apache | grep -v grep | awk '{print $2}' | 
xargs kill -9
ps -ef | grep edi_webrick.rb | grep -v apache | grep -v grep | awk 
'{print $2}' | xargs kill -9
ps -ef | grep -i sip | grep -v apache | grep -v grep | awk '{print $2}' 
| xargs kill -9

rm /tmp/reporter-LOCK
su - opensrf
osrf_control --localhost --start-all
autogen.sh -u
exit
/etc/init.d/apache2 restart
/etc/init.d/apache2 start
/etc/init.d/apache2-websockets restart
apache2ctl-websockets start
su - opensrf
oils_ctl.sh -a start_sip
exit
echo '' > /var/log/syslog
echo '' > /openils/var/log/osrfsys.log
tail -f /var/log/apache2/*log /openils/var/log/*log /var/log/syslog

-Blake-
Conducting Magic
MOBIUS
573-234-4513
877-312-3517

On 9/1/2017 7:31 AM, Jason Stephenson wrote:

Hi, Bogna.

Did you start the OpenSRF services before running autogen.sh? That looks
like either you didn't start them or there were errors when you did.

The most likely culprit for the router not starting is one of the
ejabberd passwords being wrong in the configuration file.

Jason

Re: [OPEN-ILS-GENERAL] Error in autogen.sh on Fedora

[Jason Stephenson]

Hi, Bogna.

Did you start the OpenSRF services before running autogen.sh? That looks
like either you didn't start them or there were errors when you did.

The most likely culprit for the router not starting is one of the
ejabberd passwords being wrong in the configuration file.

Jason

On 09/01/2017 04:44 AM, Bogna Czyżewska wrote:
> Hi everyone,
> Funny thing: I changed the system to Ubuntu Xenial server version,
> installed the latest OpenSRF and Evergreen... and got almost the same
> message that I had on Fedora: Session Error:
> router@private.localhost/*open-ils.cstore* IS NOT CONNECTED TO THE
> NETWORK!!! (the changed part in bold).
> I could probably set up another thread for this since it's no longer a
> Fedora issue, but maybe someone of you guys can help with this error?
> Jason, maybe?
> 
> Best regards,
> Bogna
> 
> 2017-08-31 14:57 GMT+02:00 Jason Stephenson  >:
> 
> On 08/31/2017 08:41 AM, Bogna Czyżewska wrote:
> >
> > I'll try with OpenSRF 2.5 and Evergreen 2.12 and if I fail on that, I'll
> > stop bothering you and go back to koha :)
> 
> It's not a bother. Feel free to ask any questions you have. There are
> also other places to ask for help. The open-ils-dev list may be more
> appropriate for technical questions regarding installation:
> 
> http://libmail.georgialibraries.org/mailman/options/open-ils-dev
> 
> 
> You can also find many of us in the #evergreen channel on
> irc.freenode.net . The channel is most
> active during working hours on the
> US East Coast (currently UTC -5 hours).
> 
> Good luck!
> Jason
> 
> 

Re: [OPEN-ILS-GENERAL] Error in autogen.sh on Fedora

[Bogna Czyżewska]

Hi everyone,
Funny thing: I changed the system to Ubuntu Xenial server version,
installed the latest OpenSRF and Evergreen... and got almost the same
message that I had on Fedora: Session Error: router@private.localhost/
*open-ils.cstore* IS NOT CONNECTED TO THE NETWORK!!! (the changed part in
bold).
I could probably set up another thread for this since it's no longer a
Fedora issue, but maybe someone of you guys can help with this error?
Jason, maybe?

Best regards,
Bogna

2017-08-31 14:57 GMT+02:00 Jason Stephenson :

> On 08/31/2017 08:41 AM, Bogna Czyżewska wrote:
> >
> > I'll try with OpenSRF 2.5 and Evergreen 2.12 and if I fail on that, I'll
> > stop bothering you and go back to koha :)
>
> It's not a bother. Feel free to ask any questions you have. There are
> also other places to ask for help. The open-ils-dev list may be more
> appropriate for technical questions regarding installation:
>
> http://libmail.georgialibraries.org/mailman/options/open-ils-dev
>
> You can also find many of us in the #evergreen channel on
> irc.freenode.net. The channel is most active during working hours on the
> US East Coast (currently UTC -5 hours).
>
> Good luck!
> Jason
>

Re: [OPEN-ILS-GENERAL] Error in autogen.sh on Fedora

[Jason Stephenson]

On 08/31/2017 08:41 AM, Bogna Czyżewska wrote:
> 
> I'll try with OpenSRF 2.5 and Evergreen 2.12 and if I fail on that, I'll
> stop bothering you and go back to koha :)

It's not a bother. Feel free to ask any questions you have. There are
also other places to ask for help. The open-ils-dev list may be more
appropriate for technical questions regarding installation:

http://libmail.georgialibraries.org/mailman/options/open-ils-dev

You can also find many of us in the #evergreen channel on
irc.freenode.net. The channel is most active during working hours on the
US East Coast (currently UTC -5 hours).

Good luck!
Jason

Re: [OPEN-ILS-GENERAL] Error in autogen.sh on Fedora

[Bogna Czyżewska]

Hello Everyone,
Thank you all for your input.

I tried out Koha a few weeks ago and though installation was doable (I
won't say it was easy), I was disappointed in its search engine and
patron's user interface. That's why I decided to try Evergreen instead, it
looked more user-friendly.

I'll try with OpenSRF 2.5 and Evergreen 2.12 and if I fail on that, I'll
stop bothering you and go back to koha :)

Best regards,
Bogna

2017-08-31 14:16 GMT+02:00 Jason Stephenson :

> Hello, again, Bogna!
>
> I agree with Rogan Hamby's suggestion of trying Koha.
>
> It is big, too, but not quite as big as Evergreen and I hear it is
> easier to install. It may fit your needs better.
>
> You can find Koha here:
>
> https://koha-community.org/
>
> Also, I think Ben Shum is correct, you'll want to use the latest
> releases of OpenSRF and Evergreen for Ubuntu 16.04. We tend to lag a bit
> behind the Ubuntu release cycle.
>
> Good luck in your search!
> Jason
>
>

Re: [OPEN-ILS-GENERAL] Error in autogen.sh on Fedora

[Jason Stephenson]

Hello, again, Bogna!

I agree with Rogan Hamby's suggestion of trying Koha.

It is big, too, but not quite as big as Evergreen and I hear it is
easier to install. It may fit your needs better.

You can find Koha here:

https://koha-community.org/

Also, I think Ben Shum is correct, you'll want to use the latest
releases of OpenSRF and Evergreen for Ubuntu 16.04. We tend to lag a bit
behind the Ubuntu release cycle.

Good luck in your search!
Jason

Re: [OPEN-ILS-GENERAL] Error in autogen.sh on Fedora

[Ben Shum]

Hi Bogna,

Sounds like maybe you're using an older OpenSRF version like 2.4
series.  I think we only just introduced Ubuntu xenial support as of
the OpenSRF 2.5 series.  If you switch over to that version, then you
should find the ubuntu-xenial targets available to use.  Same for
Evergreen, I think Xenial support was only added for 2.12 series and
up.

Also yes, I've been testing on Ubuntu Server 16.04.3 LTS (the 64-bit
edition only, not 32-bit).

-- Ben

On Thu, Aug 31, 2017 at 6:02 AM, Bogna Czyżewska
 wrote:
> Hello again Jason,
> As you suggested, I replaced my Fedora with Ubuntu 16.04 server version, but
> I already encountered a problem - you stressed the importance of using auto
> tools, but there is no Xenial version of OpenSRF Makefile.install for
> prerequisites and running it as ubuntu-trusty fails immediately. Do you have
> any ideas how to overcome this? Is there a Ubuntu Xenial version of opensrf
> somewhere or do I have to just install on the run, as the errors appear?
>
> Best regards,
> Bogna
>
> 2017-08-31 10:03 GMT+02:00 Bogna Czyżewska :
>>
>> Hello Blake and Jason!
>> Blake,
>> Thank you for your reply. My goal is to install Evergreen on a server
>> available only within a company network. Truth is, Evergreen seems too big
>> for handling the +/- 100 books we have, but I wasn't able to find any
>> smaller solution that could manage collection browsing and basic
>> circulation.
>>
>> Jason,
>> Seems like I have to start from a scratch on a different system... A
>> difficult decision to make after spending few days of work and getting so
>> close to the working solution. Feels like a wrong bet in a gamble ;) I
>> understand you recommend Ubuntu 16.04 over Debian, since there are plans to
>> move to Ubuntu completely? In your first e-mail you wrote about server
>> edition - do you mean Ubuntu Server 16.04.3 LTS?
>>
>> Best regards,
>> Bogna
>>
>> 2017-08-30 16:44 GMT+02:00 Jason Stephenson :
>>>
>>>
>>> On 08/30/2017 10:30 AM, Bogna Czyżewska wrote:
>>> > Hello Jason,
>>> > Thanks for your advice. I actually started with Debian (latest, 9 I
>>> > think), and switched to Fedora because I encountered many errors during
>>> > installation and just got angry. That was my first encounter with
>>> > Debian
>>> > and I already knew some Fedora stuff, so I figured it'll be easier for
>>> > me to find the workarounds on it.
>>>
>>> We haven't worked out the issues with Debian 9, yet. I have installed
>>> successfully on Debian 8 and Ubunut 16.04. Ubuntu is used by many sites
>>> in production. I test extensively with both distros and plan to move our
>>> production environment from Debian to Ubuntu in October. So, I stand by
>>> my previous recommendation of Debian 8 or Ubuntu 16.04. :)
>>>
>>> >
>>> > The thing is, I don't think this problem is platform-specific, it seems
>>> > more like a misconfiguration to me. I tracked the issue down to a piece
>>> > of code in SettingsClient.pm, lines 67-68. I don't know perl, but
>>> > OpenSRF docs say that they're supposed to "return the complete set of
>>> > settings as a JSON document". Adding that to the log entries screaming
>>> > about problems with JSON parsing (at index 1), my guess is that I
>>> > messed
>>> > up some configuration file and now it's unreadable.
>>>
>>> No, I don't think you've messed up a configuration file.
>>>
>>> We used to support Fedora as an install target, but the person(s)
>>> maintaining it stopped updating it. We removed the Fedora dependency
>>> targets in the Makefile.install recently because Evergreen would no
>>> longer build/work on recent Fedora releases. I believe the issue you've
>>> encountered is one of those reasons.
>>>
>>> I don't recommend using Fedora in general. By their own admission, it is
>>> an "unstable" distribution and is not meant to be used in production
>>> environments. It is basically a test bed for RHEL.
>>>
>>> >
>>> > Problem is: what file can that be? Seems to be about
>>> > router@private.localhost, so maybe something with ejabberd, but
>>> > ejabberd
>>> > itself starts without problems and I can't find anything wrong within
>>> > it's config file (ejabberd.yml)...
>>>
>>> The problem is not with ejabberd. It's most likey in the osrf_json
>>> libraries. My hunch is that they're not linking correctly. This is
>>> possibly related to an issue we have on Debian 9:
>>>
>>> https://bugs.launchpad.net/evergreen/+bug/1708048/comments/2
>>>
>>> The solution there is for us to start using autotools as intended
>>> instead of trying to force it to do things it wasn't meant to do.
>>>
>>> HTH,
>>> Jason
>>>
>>>
>>> >
>>> > Best regards,
>>> > Bogna
>>> >
>>> > 2017-08-30 15:03 GMT+02:00 Jason Stephenson >> > >:
>>> >
>>> > Hello, Bogna!
>>> >
>>> > My recommendation is that you switch to Debian 8 Jessie or Ubuntu
>>> > 16.04
>>> > Server Edition for installing Evergreen. These are the Linux
>>> > distributions most commonly used by the community. You will like

Re: [OPEN-ILS-GENERAL] Error in autogen.sh on Fedora

[Rogan Hamby]

On Thu, Aug 31, 2017 at 4:03 AM, Bogna Czyżewska 
wrote:

> Hello Blake and Jason!
> Blake,
> Thank you for your reply. My goal is to install Evergreen on a server
> available only within a company network. Truth is, Evergreen seems too big
> for handling the +/- 100 books we have, but I wasn't able to find any
> smaller solution that could manage collection browsing and basic
> circulation.
>
>
I love Evergreen but when you say you only have about 100 books to manage I
have to agree with you about it being too big.  Evergreen has a lot of
virtues but it's definitely built for solutions that are quite a bit larger
than what you're describing and has some corresponding learning and
administrative curves.  For small libraries and collections you may want to
look at other solutions.  This is an Evergreen list so it's not the place
for anything in depth on other ILSes but I'll mention another open source
one, Koha.  If you have ~100 items and need full holdings and circ Koha
will certainly handle that and plenty more if you see the collection
growing.  It's widely used and has a strong community just as Evergreen
does.




> Jason,
> Seems like I have to start from a scratch on a different system... A
> difficult decision to make after spending few days of work and getting so
> close to the working solution. Feels like a wrong bet in a gamble ;) I
> understand you recommend Ubuntu 16.04 over Debian, since there are plans to
> move to Ubuntu completely? In your first e-mail you wrote about server
> edition - do you mean Ubuntu Server 16.04.3 LTS?
>
> Best regards,
> Bogna
>
> 2017-08-30 16:44 GMT+02:00 Jason Stephenson :
>
>>
>> On 08/30/2017 10:30 AM, Bogna Czyżewska wrote:
>> > Hello Jason,
>> > Thanks for your advice. I actually started with Debian (latest, 9 I
>> > think), and switched to Fedora because I encountered many errors during
>> > installation and just got angry. That was my first encounter with Debian
>> > and I already knew some Fedora stuff, so I figured it'll be easier for
>> > me to find the workarounds on it.
>>
>> We haven't worked out the issues with Debian 9, yet. I have installed
>> successfully on Debian 8 and Ubunut 16.04. Ubuntu is used by many sites
>> in production. I test extensively with both distros and plan to move our
>> production environment from Debian to Ubuntu in October. So, I stand by
>> my previous recommendation of Debian 8 or Ubuntu 16.04. :)
>>
>> >
>> > The thing is, I don't think this problem is platform-specific, it seems
>> > more like a misconfiguration to me. I tracked the issue down to a piece
>> > of code in SettingsClient.pm, lines 67-68. I don't know perl, but
>> > OpenSRF docs say that they're supposed to "return the complete set of
>> > settings as a JSON document". Adding that to the log entries screaming
>> > about problems with JSON parsing (at index 1), my guess is that I messed
>> > up some configuration file and now it's unreadable.
>>
>> No, I don't think you've messed up a configuration file.
>>
>> We used to support Fedora as an install target, but the person(s)
>> maintaining it stopped updating it. We removed the Fedora dependency
>> targets in the Makefile.install recently because Evergreen would no
>> longer build/work on recent Fedora releases. I believe the issue you've
>> encountered is one of those reasons.
>>
>> I don't recommend using Fedora in general. By their own admission, it is
>> an "unstable" distribution and is not meant to be used in production
>> environments. It is basically a test bed for RHEL.
>>
>> >
>> > Problem is: what file can that be? Seems to be about
>> > router@private.localhost, so maybe something with ejabberd, but
>> ejabberd
>> > itself starts without problems and I can't find anything wrong within
>> > it's config file (ejabberd.yml)...
>>
>> The problem is not with ejabberd. It's most likey in the osrf_json
>> libraries. My hunch is that they're not linking correctly. This is
>> possibly related to an issue we have on Debian 9:
>>
>> https://bugs.launchpad.net/evergreen/+bug/1708048/comments/2
>>
>> The solution there is for us to start using autotools as intended
>> instead of trying to force it to do things it wasn't meant to do.
>>
>> HTH,
>> Jason
>>
>>
>> >
>> > Best regards,
>> > Bogna
>> >
>> > 2017-08-30 15:03 GMT+02:00 Jason Stephenson > > >:
>> >
>> > Hello, Bogna!
>> >
>> > My recommendation is that you switch to Debian 8 Jessie or Ubuntu
>> 16.04
>> > Server Edition for installing Evergreen. These are the Linux
>> > distributions most commonly used by the community. You will likely
>> have
>> > more success and get more help with problems.
>> >
>> > Good luck,
>> > Jason
>> >
>> >
>>
>
>

Re: [OPEN-ILS-GENERAL] Error in autogen.sh on Fedora

[Bogna Czyżewska]

Hello again Jason,
As you suggested, I replaced my Fedora with Ubuntu 16.04 server version,
but I already encountered a problem - you stressed the importance of using
auto tools, but there is no Xenial version of OpenSRF Makefile.install for
prerequisites and running it as ubuntu-trusty fails immediately. Do you
have any ideas how to overcome this? Is there a Ubuntu Xenial version of
opensrf somewhere or do I have to just install on the run, as the errors
appear?

Best regards,
Bogna

2017-08-31 10:03 GMT+02:00 Bogna Czyżewska :

> Hello Blake and Jason!
> Blake,
> Thank you for your reply. My goal is to install Evergreen on a server
> available only within a company network. Truth is, Evergreen seems too big
> for handling the +/- 100 books we have, but I wasn't able to find any
> smaller solution that could manage collection browsing and basic
> circulation.
>
> Jason,
> Seems like I have to start from a scratch on a different system... A
> difficult decision to make after spending few days of work and getting so
> close to the working solution. Feels like a wrong bet in a gamble ;) I
> understand you recommend Ubuntu 16.04 over Debian, since there are plans to
> move to Ubuntu completely? In your first e-mail you wrote about server
> edition - do you mean Ubuntu Server 16.04.3 LTS?
>
> Best regards,
> Bogna
>
> 2017-08-30 16:44 GMT+02:00 Jason Stephenson :
>
>>
>> On 08/30/2017 10:30 AM, Bogna Czyżewska wrote:
>> > Hello Jason,
>> > Thanks for your advice. I actually started with Debian (latest, 9 I
>> > think), and switched to Fedora because I encountered many errors during
>> > installation and just got angry. That was my first encounter with Debian
>> > and I already knew some Fedora stuff, so I figured it'll be easier for
>> > me to find the workarounds on it.
>>
>> We haven't worked out the issues with Debian 9, yet. I have installed
>> successfully on Debian 8 and Ubunut 16.04. Ubuntu is used by many sites
>> in production. I test extensively with both distros and plan to move our
>> production environment from Debian to Ubuntu in October. So, I stand by
>> my previous recommendation of Debian 8 or Ubuntu 16.04. :)
>>
>> >
>> > The thing is, I don't think this problem is platform-specific, it seems
>> > more like a misconfiguration to me. I tracked the issue down to a piece
>> > of code in SettingsClient.pm, lines 67-68. I don't know perl, but
>> > OpenSRF docs say that they're supposed to "return the complete set of
>> > settings as a JSON document". Adding that to the log entries screaming
>> > about problems with JSON parsing (at index 1), my guess is that I messed
>> > up some configuration file and now it's unreadable.
>>
>> No, I don't think you've messed up a configuration file.
>>
>> We used to support Fedora as an install target, but the person(s)
>> maintaining it stopped updating it. We removed the Fedora dependency
>> targets in the Makefile.install recently because Evergreen would no
>> longer build/work on recent Fedora releases. I believe the issue you've
>> encountered is one of those reasons.
>>
>> I don't recommend using Fedora in general. By their own admission, it is
>> an "unstable" distribution and is not meant to be used in production
>> environments. It is basically a test bed for RHEL.
>>
>> >
>> > Problem is: what file can that be? Seems to be about
>> > router@private.localhost, so maybe something with ejabberd, but
>> ejabberd
>> > itself starts without problems and I can't find anything wrong within
>> > it's config file (ejabberd.yml)...
>>
>> The problem is not with ejabberd. It's most likey in the osrf_json
>> libraries. My hunch is that they're not linking correctly. This is
>> possibly related to an issue we have on Debian 9:
>>
>> https://bugs.launchpad.net/evergreen/+bug/1708048/comments/2
>>
>> The solution there is for us to start using autotools as intended
>> instead of trying to force it to do things it wasn't meant to do.
>>
>> HTH,
>> Jason
>>
>>
>> >
>> > Best regards,
>> > Bogna
>> >
>> > 2017-08-30 15:03 GMT+02:00 Jason Stephenson > > >:
>> >
>> > Hello, Bogna!
>> >
>> > My recommendation is that you switch to Debian 8 Jessie or Ubuntu
>> 16.04
>> > Server Edition for installing Evergreen. These are the Linux
>> > distributions most commonly used by the community. You will likely
>> have
>> > more success and get more help with problems.
>> >
>> > Good luck,
>> > Jason
>> >
>> >
>>
>
>

Re: [OPEN-ILS-GENERAL] Error in autogen.sh on Fedora

[Bogna Czyżewska]

Hello Blake and Jason!
Blake,
Thank you for your reply. My goal is to install Evergreen on a server
available only within a company network. Truth is, Evergreen seems too big
for handling the +/- 100 books we have, but I wasn't able to find any
smaller solution that could manage collection browsing and basic
circulation.

Jason,
Seems like I have to start from a scratch on a different system... A
difficult decision to make after spending few days of work and getting so
close to the working solution. Feels like a wrong bet in a gamble ;) I
understand you recommend Ubuntu 16.04 over Debian, since there are plans to
move to Ubuntu completely? In your first e-mail you wrote about server
edition - do you mean Ubuntu Server 16.04.3 LTS?

Best regards,
Bogna

2017-08-30 16:44 GMT+02:00 Jason Stephenson :

>
> On 08/30/2017 10:30 AM, Bogna Czyżewska wrote:
> > Hello Jason,
> > Thanks for your advice. I actually started with Debian (latest, 9 I
> > think), and switched to Fedora because I encountered many errors during
> > installation and just got angry. That was my first encounter with Debian
> > and I already knew some Fedora stuff, so I figured it'll be easier for
> > me to find the workarounds on it.
>
> We haven't worked out the issues with Debian 9, yet. I have installed
> successfully on Debian 8 and Ubunut 16.04. Ubuntu is used by many sites
> in production. I test extensively with both distros and plan to move our
> production environment from Debian to Ubuntu in October. So, I stand by
> my previous recommendation of Debian 8 or Ubuntu 16.04. :)
>
> >
> > The thing is, I don't think this problem is platform-specific, it seems
> > more like a misconfiguration to me. I tracked the issue down to a piece
> > of code in SettingsClient.pm, lines 67-68. I don't know perl, but
> > OpenSRF docs say that they're supposed to "return the complete set of
> > settings as a JSON document". Adding that to the log entries screaming
> > about problems with JSON parsing (at index 1), my guess is that I messed
> > up some configuration file and now it's unreadable.
>
> No, I don't think you've messed up a configuration file.
>
> We used to support Fedora as an install target, but the person(s)
> maintaining it stopped updating it. We removed the Fedora dependency
> targets in the Makefile.install recently because Evergreen would no
> longer build/work on recent Fedora releases. I believe the issue you've
> encountered is one of those reasons.
>
> I don't recommend using Fedora in general. By their own admission, it is
> an "unstable" distribution and is not meant to be used in production
> environments. It is basically a test bed for RHEL.
>
> >
> > Problem is: what file can that be? Seems to be about
> > router@private.localhost, so maybe something with ejabberd, but ejabberd
> > itself starts without problems and I can't find anything wrong within
> > it's config file (ejabberd.yml)...
>
> The problem is not with ejabberd. It's most likey in the osrf_json
> libraries. My hunch is that they're not linking correctly. This is
> possibly related to an issue we have on Debian 9:
>
> https://bugs.launchpad.net/evergreen/+bug/1708048/comments/2
>
> The solution there is for us to start using autotools as intended
> instead of trying to force it to do things it wasn't meant to do.
>
> HTH,
> Jason
>
>
> >
> > Best regards,
> > Bogna
> >
> > 2017-08-30 15:03 GMT+02:00 Jason Stephenson  > >:
> >
> > Hello, Bogna!
> >
> > My recommendation is that you switch to Debian 8 Jessie or Ubuntu
> 16.04
> > Server Edition for installing Evergreen. These are the Linux
> > distributions most commonly used by the community. You will likely
> have
> > more success and get more help with problems.
> >
> > Good luck,
> > Jason
> >
> >
>

Re: [OPEN-ILS-GENERAL] Error in autogen.sh on Fedora

[Jason Stephenson]

On 08/30/2017 10:30 AM, Bogna Czyżewska wrote:
> Hello Jason,
> Thanks for your advice. I actually started with Debian (latest, 9 I
> think), and switched to Fedora because I encountered many errors during
> installation and just got angry. That was my first encounter with Debian
> and I already knew some Fedora stuff, so I figured it'll be easier for
> me to find the workarounds on it.

We haven't worked out the issues with Debian 9, yet. I have installed
successfully on Debian 8 and Ubunut 16.04. Ubuntu is used by many sites
in production. I test extensively with both distros and plan to move our
production environment from Debian to Ubuntu in October. So, I stand by
my previous recommendation of Debian 8 or Ubuntu 16.04. :)

> 
> The thing is, I don't think this problem is platform-specific, it seems
> more like a misconfiguration to me. I tracked the issue down to a piece
> of code in SettingsClient.pm, lines 67-68. I don't know perl, but
> OpenSRF docs say that they're supposed to "return the complete set of
> settings as a JSON document". Adding that to the log entries screaming
> about problems with JSON parsing (at index 1), my guess is that I messed
> up some configuration file and now it's unreadable.

No, I don't think you've messed up a configuration file.

We used to support Fedora as an install target, but the person(s)
maintaining it stopped updating it. We removed the Fedora dependency
targets in the Makefile.install recently because Evergreen would no
longer build/work on recent Fedora releases. I believe the issue you've
encountered is one of those reasons.

I don't recommend using Fedora in general. By their own admission, it is
an "unstable" distribution and is not meant to be used in production
environments. It is basically a test bed for RHEL.

> 
> Problem is: what file can that be? Seems to be about
> router@private.localhost, so maybe something with ejabberd, but ejabberd
> itself starts without problems and I can't find anything wrong within
> it's config file (ejabberd.yml)...

The problem is not with ejabberd. It's most likey in the osrf_json
libraries. My hunch is that they're not linking correctly. This is
possibly related to an issue we have on Debian 9:

https://bugs.launchpad.net/evergreen/+bug/1708048/comments/2

The solution there is for us to start using autotools as intended
instead of trying to force it to do things it wasn't meant to do.

HTH,
Jason


> 
> Best regards,
> Bogna
> 
> 2017-08-30 15:03 GMT+02:00 Jason Stephenson  >:
> 
> Hello, Bogna!
> 
> My recommendation is that you switch to Debian 8 Jessie or Ubuntu 16.04
> Server Edition for installing Evergreen. These are the Linux
> distributions most commonly used by the community. You will likely have
> more success and get more help with problems.
> 
> Good luck,
> Jason
> 
> 

Re: [OPEN-ILS-GENERAL] Error in autogen.sh on Fedora

[Blake Henderson]

Bogna,

Installing Evergreen for the first time is difficult. If your goal is to 
get a local server up and running for evaluation and testing, you might 
be interested in the docker container:


https://hub.docker.com/r/mobiusoffice/evergreen-ils/

There are a couple of video's available to help as well:
first step:
https://vimeo.com/230985351

second step:
https://vimeo.com/231611654


-Blake-
Conducting Magic
MOBIUS

On 8/30/2017 9:30 AM, Bogna Czyżewska wrote:

Hello Jason,
Thanks for your advice. I actually started with Debian (latest, 9 I 
think), and switched to Fedora because I encountered many errors 
during installation and just got angry. That was my first encounter 
with Debian and I already knew some Fedora stuff, so I figured it'll 
be easier for me to find the workarounds on it.


The thing is, I don't think this problem is platform-specific, it 
seems more like a misconfiguration to me. I tracked the issue down to 
a piece of code in SettingsClient.pm, lines 67-68. I don't know perl, 
but OpenSRF docs say that they're supposed to "return the complete set 
of settings as a JSON document". Adding that to the log entries 
screaming about problems with JSON parsing (at index 1), my guess is 
that I messed up some configuration file and now it's unreadable.


Problem is: what file can that be? Seems to be about 
router@private.localhost, so maybe something with ejabberd, but 
ejabberd itself starts without problems and I can't find anything 
wrong within it's config file (ejabberd.yml)...


Best regards,
Bogna

2017-08-30 15:03 GMT+02:00 Jason Stephenson >:


Hello, Bogna!

My recommendation is that you switch to Debian 8 Jessie or Ubuntu
16.04
Server Edition for installing Evergreen. These are the Linux
distributions most commonly used by the community. You will likely
have
more success and get more help with problems.

Good luck,
Jason

Re: [OPEN-ILS-GENERAL] Error in autogen.sh on Fedora

[Bogna Czyżewska]

Hello Jason,
Thanks for your advice. I actually started with Debian (latest, 9 I think),
and switched to Fedora because I encountered many errors during
installation and just got angry. That was my first encounter with Debian
and I already knew some Fedora stuff, so I figured it'll be easier for me
to find the workarounds on it.

The thing is, I don't think this problem is platform-specific, it seems
more like a misconfiguration to me. I tracked the issue down to a piece of
code in SettingsClient.pm, lines 67-68. I don't know perl, but OpenSRF docs
say that they're supposed to "return the complete set of settings as a JSON
document". Adding that to the log entries screaming about problems with
JSON parsing (at index 1), my guess is that I messed up some configuration
file and now it's unreadable.

Problem is: what file can that be? Seems to be about
router@private.localhost, so maybe something with ejabberd, but ejabberd
itself starts without problems and I can't find anything wrong within it's
config file (ejabberd.yml)...

Best regards,
Bogna

2017-08-30 15:03 GMT+02:00 Jason Stephenson :

> Hello, Bogna!
>
> My recommendation is that you switch to Debian 8 Jessie or Ubuntu 16.04
> Server Edition for installing Evergreen. These are the Linux
> distributions most commonly used by the community. You will likely have
> more success and get more help with problems.
>
> Good luck,
> Jason
>

Re: [OPEN-ILS-GENERAL] Error in autogen.sh on Fedora

[Jason Stephenson]

Hello, Bogna!

My recommendation is that you switch to Debian 8 Jessie or Ubuntu 16.04
Server Edition for installing Evergreen. These are the Linux
distributions most commonly used by the community. You will likely have
more success and get more help with problems.

Good luck,
Jason