Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

pgloader breaks some time after installation #103

Closed
richardlew opened this issue Aug 7, 2014 · 6 comments
Closed

pgloader breaks some time after installation #103

richardlew opened this issue Aug 7, 2014 · 6 comments

Comments

@richardlew
Copy link

Hi,

After installing pgloader 3.0.99 I can get it to work as expected. However after some time it stops working, normally the next day when I come back to it. I can"t see anything that triggers this.

When it is broken, it behaves as though I"m just running sbcl and any mention of pgloader is gone. It gives this error and then goes into the debgger. Doing a backtrace shows a segfault.

# pgloader
This is SBCL 1.1.14, an implementation of ANSI Common Lisp.
More information about SBCL is available at <http://www.sbcl.org/>.

SBCL is free software, provided as is, with absolutely no warranty.
It is mostly in the public domain; some portions are provided under
BSD-style licenses.  See the CREDITS and COPYING files in the
distribution for more information.
fatal error encountered in SBCL pid 19390(tid 140737354045184):
premature end of core file

Welcome to LDB, a low-level debugger for the Lisp runtime environment.
ldb> backtrace
Backtrace:
Segmentation fault (core dumped)

I can just reinstall and then it will start working again but it will just break again.
@dimitri
Copy link
Owner

dimitri commented Aug 7, 2014

Can you please try with a recent pgloader, I know I fixed the Makefile that produces the binary in between 3.0.99 and now... You can either recompile from sources or try a more recent version as I randomly update them at http://pgloader.io/files/.

@dimitri
Copy link
Owner

dimitri commented Aug 7, 2014

I know that strip(1) will actually break the binary file if used against it. Could it be that you have a nightly cron job going mad and stripping all the files in /usr/bin?

@menardorama
Copy link

HI
I"ve the same issue, on Centos 6 it"s the prelink (or prefetcher) in cause.

For now just set PRELINKING=no the in /etc/sysconfig/prelink, it"s a daily job in /etc/cron.daily

Dimitri, have any idea to fix this issue on your side ? Keeping prefetch can be necessary on some system

@dimitri
Copy link
Owner

dimitri commented Aug 18, 2014

I found some worthy notes at https://lists.fedoraproject.org/pipermail/devel/2011-December/160415.html and implemented the patch here, closing this ticket. Please try to build the RPM on your end (you need to change *release* from nil to t in src/params.lisp before doing make rpm) and try it, and feel free to re-open the issue if it"s not enough.

Another way to try it is with doing the following yourself, but the the new file will not be part of the pgloader package:

echo "-b /usr/bin/pgloader" > /etc/prelink.conf.d/pgloader.conf

@menardorama
Copy link

Hi

Thanks for your feedback, in my opinion you should implement that at least for the systems that use prelink (such as CentOS 6) that"s not a big deal and we wouldn"t have to build our own rpms.

@dimitri
Copy link
Owner

dimitri commented Aug 18, 2014

It"s implemented already, will be included in the next set of RPMs. Sorry if I"ve been unclear in my message before, you only need to build your own RPM in the interim before the next release, 3.1.0, which is due very soon now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@dimitri @menardorama @richardlew