[OPEN-ILS-GENERAL] PostgreSQL/Perl config script
So..., I'm getting close to getting my first install up and running, but am stuck at setting up the database. When running the following script (as listed in the official documentation for 2.5.1)...I get the error listed a little furher down. Here is the script... perl Open-ILS/src/support-scripts/eg_db_config --update-config \ > --service all --create-database --create-schema --create-offline \ > --user evergreen --password evergreen --hostname localhost –port \ > --database 1 --admin-user egadmin --admin-pass egadmin Note: I have used a variety of things for "database" (name) and have also done this with and without a port number (port 5222) I have uninstalled all versions of PostgreSQL on my machine and am now runninge 9.1. Here is the error message I receive. Any help would be greatly appreciated. Matthias ...I get the following error === Backed up original configuration file to '/openils/conf/opensrf.xml.2013.12.5.22.19.16' psql: received invalid response to SSL negotiation: < Argument "" isn't numeric in numeric ge (>=) at Open-ILS/src/support-scripts/eg_db_config line 153. psql: received invalid response to SSL negotiation: < * Could not determine the version of PostgreSQL you have installed. Our best * * guess was: * * * which didn't make any sense. For assistance, please email * * open-ils-general@list.georgialibraries.org or join #Evergreen on the * * freenode IRC network. * install_driver(Pg) failed: Can't locate DBD/Pg.pm in @INC (@INC contains: /etc/perl /usr/local/lib/perl/5.10.1 /usr/local/share/perl/5.10.1 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.10 /usr/share/perl/5.10 /usr/local/lib/site_perl .) at (eval 9) line 3. Perhaps the DBD::Pg perl module hasn't been fully installed, or perhaps the capitalisation of 'Pg' isn't right. Available drivers: AnyData, DBM, ExampleP, File, Gofer, Proxy, SQLite, Sponge. at Open-ILS/src/support-scripts/eg_db_config line 220
Re: [OPEN-ILS-GENERAL] opensrf - cannot authenticate user
My apologies but I realized that the instructions were correct, but I was doing it wrong! :( I have figure out my issues with the install, and am stuck at the PostgreSQL install right now, on which I'll post shortly. However, these were the instructions I was using. http://evergreen-ils.org/dokuwiki/doku.php?id=server:2.0:install Thanks, Martin On Tue, Dec 3, 2013 at 2:23 PM, Yamil Suarez wrote: > Mart, > > Can you reply with the exact URL of the installation instructions you used > from the wiki? I want to add a note to the top of that page with a warning > that these instructions should not be used anymore. > > Thanks, > Yamil > > > > On Dec 3, 2013, at 2:17 PM, mart steinholz wrote: > > > Daniel, > > > > Thanks so much! I used server install instructions off the wiki, and not > from the main documentation. I'll re-install from the "docs" site. > > > > Thanks! > > > > Martin > > > > >
[OPEN-ILS-GENERAL] Link to login to catalog then redirect to another site
Hello, I'm needing to create a way to validate a patron's library account, then send them to a page on our site. Can anyone help me with this? The ideal would be a widget I can put on a page without a redirect, but a link that sends them to our catalog logon then back to another page on our site would work. Thanks in advance! George -- George Rodgers-Clark, Tech La Conner Regional Library P O Box 370 614 Morris Street La Conner, WA 98257 360-466-3352 grodgers-cl...@lclib.lib.wa.us
Re: [OPEN-ILS-GENERAL] IMPORTANT: Postgres bug affecting Streaming Replication
UPDATE HAT TRICK: Chris Sharp was the first to notice and mention the release of the Postgres updates mentioned below. Thanks, Chris! Here's where you can download the update: http://www.postgresql.org/about/news/1492/ Happy upgrading, folks! On Sat, Nov 23, 2013 at 4:46 PM, Mike Rylander wrote: > UPDATE THE SECOND: > > The Postgres team is planning to wrap releases to fix this issue on > Dec 2, for release on Dec 5. The PGDG apt repos should have the > package at that time, and I expect the debian and ubuntu repositories > to follow shortly thereafter. Please mark your calendars, if you're > affected by this bug, and plan downtime to upgrade your servers ASAP > after the release. For the announcement to the pgsql-hackers list > see: http://markmail.org/thread/qnye6rk37ug52zox > > --miker > > > On Thu, Nov 21, 2013 at 3:55 PM, Mike Rylander wrote: >> UPDATE >> >> I need clarify and correct the information below: this is not >> restricted streaming-replication based hot-standby replicas, it is for >> all hot_standby-enabled replicas (regardless of the mechanism used to >> ship the WAL data) when there is a recovery.conf in place. This is >> per: http://markmail.org/message/p6bcdo5h2ll4kk3k >> >> >> On Thu, Nov 21, 2013 at 1:35 PM, Mike Rylander wrote: >>> THE BAD NEWS: >>> >>> If your site uses Postgres' streaming replication to create a >>> read-only hot-standby, such as for reporting or to support search >>> capacity needs, this message is for you. >>> >>> On Nov, 18, a bug was reported to the Postgres hackers list that can >>> cause extreme corruption of hot-standby secondary servers. Known >>> affected versions include 9.2.5 and 9.3.1. It is likely that this >>> goes as far back as 9.1. >>> >>> The nature of the bug is such that it is somewhat hard to provoke. >>> However, it can occur at any standby startup if the secondary is in >>> hot-standby mode, and not only during the initial secondary creation. >>> In other words, every restart of a hot-standby secondary instance of >>> Postgres is another chance to run afoul of this bug. It is most >>> likely to occur under high write load or situations where there is >>> significant lag during standby startup. >>> >>> Symptoms include: missing data; apparently-duplicated data; mismatch >>> between index and heap data; "impossible" constraint violations >>> (unique and fkey). >>> >>> The underlying cause of these symptoms is a loss of proper transaction >>> visibility information on the hot-standby secondary. >>> >>> THE GOOD NEWS: >>> >>> There is an apparent fix being tested now by several large Postgres >>> entities. It is expected that a point release for all affected >>> versions will be made available ASAP. Additionally, if you have >>> already been bitten by the corruption bug, there is a straight-forward >>> procedure for recover, which I am sure will be detailed in the release >>> notes for the upcoming point releases. >>> >>> You can read the full thread from the pgsql-hackers mailing list here: >>> http://markmail.org/message/p54pqkykjtwvog3h >>> >>> -- >>> Mike Rylander >>> | Director of Research and Development >>> | Equinox Software, Inc. / Your Library's Guide to Open Source >>> | phone: 1-877-OPEN-ILS (673-6457) >>> | email: mi...@esilibrary.com >>> | web: http://www.esilibrary.com >> >> >> >> -- >> Mike Rylander >> | Director of Research and Development >> | Equinox Software, Inc. / Your Library's Guide to Open Source >> | phone: 1-877-OPEN-ILS (673-6457) >> | email: mi...@esilibrary.com >> | web: http://www.esilibrary.com > > > > -- > Mike Rylander > | Director of Research and Development > | Equinox Software, Inc. / Your Library's Guide to Open Source > | phone: 1-877-OPEN-ILS (673-6457) > | email: mi...@esilibrary.com > | web: http://www.esilibrary.com -- Mike Rylander | Director of Research and Development | Equinox Software, Inc. / Your Library's Guide to Open Source | phone: 1-877-OPEN-ILS (673-6457) | email: mi...@esilibrary.com | web: http://www.esilibrary.com
Re: [OPEN-ILS-GENERAL] Display of canceled line items in acquisitions
It sounds reasonable to me. Mary Mary Llewellyn Database Manager Bibliomation, Inc. 24 Wooster Ave. Waterbury, CT 06708 mllew...@biblio.org -Original Message- From: open-ils-general-boun...@list.georgialibraries.org [mailto:open-ils-general-boun...@list.georgialibraries.org] On Behalf Of Holly Brennan Sent: Wednesday, December 04, 2013 7:54 PM To: Evergreen Discussion Group Subject: Re: [OPEN-ILS-GENERAL] Display of canceled line items in acquisitions No opposition from our cataloging team. -Holly -Original Message- From: open-ils-general-boun...@list.georgialibraries.org [mailto:open-ils-general-boun...@list.georgialibraries.org] On Behalf Of Kathy Lussier Sent: Tuesday, December 03, 2013 5:31 AM To: Evergreen General Discussion List Subject: [OPEN-ILS-GENERAL] Display of canceled line items in acquisitions Hi all, Based on feedback from the acquisitions staff here in Massachusetts, MassLNC is considering a small development project that would change the way canceled line items display on a PO. I wanted to get some feedback from the Evergreen acquisitions community in case people like the way it currently displays. The concern from our acquisitions staff is that line items display as canceled even in cases where the order isn't truly canceled. This scenario most often occurs in cases where a title is backordered. You identify something as being backordered by marking it as canceled and then identifying the cancel reason as backorder quantity. The status of the line item then displays as canceled, even though the library fully expects to receive the title at some future date. Acquisitions staff find this label misleading and confusing, and, at times, it has led to some extra time in their workflow as they ascertain whether the line item is truly canceled and needs to be re-ordered through a different vendor. In 2.5, there have been some improvements in the PO display, with the cancel reason displaying to the right of the title (see attached image) and a different background color used for truly canceled line items and those that are just delayed. These changes should address the problem with added time in the workflow. However, the canceled status still displays, and we believe it continues to be a misleading label for the status of the line item. We would like to suggest that, in cases where the line item is canceled, that the cancel reason display in the status column of the PO instead of displaying the status as canceled. For example, in the attached image, "backorder quantity" would display in the status column for the first line item and "not accepted" would display for the second line item. In the case where line items are not canceled, we would like to continue to see the line item status display there. Would there be any objections to pursuing this approach? Are there reasons I'm not thinking of where it would be beneficial to display the status as canceled for line items that are delayed? Thanks! Kathy -- Kathy Lussier Project Coordinator Massachusetts Library Network Cooperative (508) 343-0128 kluss...@masslnc.org Twitter: http://www.twitter.com/kmlussier
