Hi all. I have been cracking my head to OpenSRF these past few days trying to bring the Perl debugger to debug OpenSRF's Evergreen services, like open-ils.serial. with success...
Thanks to the help of community members and divine justification, I have been writing a tutorial about my experiences so others could aim their debuggers at Evergreen. You can read and comment here: https://docs.google.com/document/d/1CGMPWG2Pb5_mhnnEzXywfkQTnp8OeCdMivjd9Pap_ow/edit?usp=sharing Currently it has been marginally tested, but it works for me as well as a perl -d can. I hope you find something to nag about. Sincerely yours, Olli-Antti Kivilahti Open Library 2014 Joensuu Regional Library This message is powered by Ubuntu On 06/13/2013 07:00 PM, [email protected] wrote: > Send Open-ils-dev mailing list submissions to > [email protected] > > To subscribe or unsubscribe via the World Wide Web, visit > http://libmail.georgialibraries.org/mailman/listinfo/open-ils-dev > or, via email, send a message with subject or body 'help' to > [email protected] > > You can reach the person managing the list at > [email protected] > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Open-ils-dev digest..." > > > Today's Topics: > > 1. Re: Any ideas why I sometimes get a "segmentation fault" with > pg_restore? (Yamil Suarez) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 12 Jun 2013 14:04:52 -0400 > From: Yamil Suarez <[email protected]> > Subject: Re: [OPEN-ILS-DEV] Any ideas why I sometimes get a > "segmentation fault" with pg_restore? > To: Development Evergreen list > <[email protected]> > Message-ID: > <canakoqb5ey6-k5fvmg0q5-lqufc9xscr2e4trwy-6xe3onn...@mail.gmail.com> > Content-Type: text/plain; charset=ISO-8859-1 > > On Mon, Jun 10, 2013 at 6:19 PM, Yamil Suarez <[email protected]> wrote: >> Hello, >> >> To maintaining test VMs with production data I usually use a combination of >> pg_dump[1] on the production server. I then I use "dropdb evergreen" and >> then pg_restore[2] on the test VMs. On occasion I get an error message of >> "segmentation fault" when I try to run pg_restore[2] on the test VM, but >> usually I don't have any issues. Before I got this error today, I did a >> pg_dump of the concerto data that was already on the VMs postgres, and as a >> test I successfully used pg_restore to reload the concerto data with out any >> problems. Except for some warning I usually get when I successfully run >> pg_restore[3]. Finally, I checked >> /var/log/postgresql/postgresql-9.1-main.log and only saw entries for the >> warnings I just mentioned from when I restored up the concerto data as a >> test. >> >> I was wondering if someone had an idea of why this is happening to me this >> morning? >> >> Thanks in advance, >> Yamil >> >> >> [1] pg_dump -Fc evergreen > prod_data.sql >> >> >> [2] pg_restore -U postgres -C -j 4 --dbname=template1 prod_data.sql >> >> >> [3] >> WARNING: => is deprecated as an operator name >> This name may be disallowed altogether in future versions of PostgreSQL. > > For the list record, I figured out that I was getting the error > because when I used a certain GUI FTP tool and then saved the file on > an OS X machine, the pg_dump file was being changed in some way. I > confirmed this by checking the MD5 of the file. When I copied the file > in a different way, pg_restore did not give me an error anymore. > > Yamil > > > End of Open-ils-dev Digest, Vol 87, Issue 8 > *******************************************
