Re: PKG 3.1.0 update - Segmentation fault: 11
On 27/07/2014 13:30, David Wolfskill wrote:
Errr...??!?
I haven't changed /usr/local/etc/pkg.conf at all.
The sample pkg.conf for 1.2.x
(https://github.com/freebsd/pkg/blob/release-1.2/pkg/pkg.conf.sample)
contained some ALIAS definitions, like so:
ALIAS : {
all-depends: query %dn-%dv,
annotations: info -A,
build-depends: info -qd,
download: fetch,
iinfo: info -i -g -x,
isearch: search -i -g -x,
leaf: query -e %a == 0 %n-%v,
leaf: query -e %a == 0 %n-%v, --
list: info -ql,
origin: info -qo,
provided-depends: info -qb,
raw: info -R,
required-depends: info -qr,
shared-depends: info -qB,
show: info -f -k,
size: info -sq,
}
It's that redefinition of 'leaf' that's causing the mayhem. Try
deleting the duplicated line. There will be an update going out ASAP to
cure the crashyness.
Cheers,
Matthew
--
Dr Matthew J Seaman MA, D.Phil.
PGP: http://www.infracaninophile.co.uk/pgpkey
JID: matt...@infracaninophile.co.uk
signature.asc
Description: OpenPGP digital signature
Re: PKG 3.1.0 update - Segmentation fault: 11
On 27/07/2014 14:22, Michelle Sullivan wrote: Unless the fault smashed the stack often you can find what the problem/cause was. If the stack is smashed you're screwed. gdb path to binary path to core Commands immediately useful: backtrace full (alias: bt full) frame number for which you want to examine if you get a line number/code, 'l' (el) will give the 5 lines eitherside If threaded select each thread before the frame to see what was happening in each thread. If I remember correctly - it's been several years since I last used gdb ;-) If you want to catch a smashed stack problem run the binary in gdb: gdb path to command Then: set args what ever is approrpiate run When it faults most of the time you'll get the stack just prior to the smashing - though I have had some really bad ones when even gdb cored out.. If the process forks out, you will need to use follow-fork.. Actually pkg(8) pretty much always forks itself -- run it with the '-d' flag to prevent that. However, this particular crash is something we've received plenty of reports about. I believe bapt has a fix just about ready, but he's AFK for a little while. If you'ld like to help with testing and stuff, might I suggest joining #pkgng on freenode IRC? Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey JID: matt...@infracaninophile.co.uk signature.asc Description: OpenPGP digital signature
Re: PKG 3.1.0 update - Segmentation fault: 11
On 2014-07-27 12:02, Jos Chrispijn wrote:
Hi Bapt,
I just found another issue with the port update failure:
pkg info
Child process pid=2126 terminated abnormally: Segmentation fault: 11
pkg2ng
Child process pid=2147 terminated abnormally: Segmentation fault: 11
Analysing shared libraries, this will take a while... Child process
pid=2150 terminated abnormally: Segmentation fault: 11
done
Can you tell me how to solve this?
Thanks,
Jos Chrispijn
Try do the following patch (going back to pkg-1.3.0).
In ports-mgmt/pkg do a `make reinstall'
It will take some time for the pkg team to find the issue and prepare a working
way for all users, so please stay tuned
Index: /usr/ports/ports-mgmt/pkg/Makefile
===
--- /usr/ports/ports-mgmt/pkg/Makefile (revision 363021)
+++ /usr/ports/ports-mgmt/pkg/Makefile (working copy)
@@ -1,7 +1,7 @@
# $FreeBSD$
PORTNAME= pkg
-DISTVERSION= 1.3.1
+DISTVERSION= 1.3.0
CATEGORIES=ports-mgmt
MASTER_SITES= \
http://files.etoilebsd.net/${PORTNAME}/ \
Index: /usr/ports/ports-mgmt/pkg/distinfo
===
--- /usr/ports/ports-mgmt/pkg/distinfo (revision 363021)
+++ /usr/ports/ports-mgmt/pkg/distinfo (working copy)
@@ -1,2 +1,2 @@
-SHA256 (pkg-1.3.1.tar.xz) =
5f1d620251774c54dc06468f7b5332186b20e1bdd52eed2cc5a02e7d2bde0fe0
-SIZE (pkg-1.3.1.tar.xz) = 1702492
+SHA256 (pkg-1.3.0.tar.xz) =
6d3001cdd605e6e3c15e686370cbeea999a5f19e72fd7f26e8af92ed2e2c2a01
+SIZE (pkg-1.3.0.tar.xz) = 1729104
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: PKG 3.1.0 update - Segmentation fault: 11
On Sun, Jul 27, 2014 at 12:02:50PM +0200, Jos Chrispijn wrote: html head meta http-equiv=content-type content=text/html; charset=ISO-8859-1 /head body smarttemplateinserted=true bgcolor=#FF text=#00 font face=VerdanaHfont face=Verdanai Bapt,br br font face=VerdanaI jfont face=Verdanaust found another issue with the port update failfont face=Verdanaure:/font/font/fontbr /fontbr gt; pkg infobr Child process pid=2126 terminated abnormally: Segmentation fault: 11br br font face=Verdanagt; pkg2ngbr Child process pid=2147 terminated abnormally: Segmentation fault: 11br Analysing shared libraries, this will take a while... Child process pid=2150 terminated abnormally: Segmentation fault: 11br donebr /fontbr font face=VerdanaCan you tell me how to solve this?br br Thanks,br font face=VerdanaJos Chrispijn/fontbr br /font/font /body /html This is a known one I'm very sorry about but tricky to fix, to solve it, open your /usr/local/etc/pkg.conf you might have a duplicated entrey in alias (probable leaf), remove the second one, that will solve your problem. regards, Bapt pgplxD1EAn7zt.pgp Description: PGP signature
Re: PKG 3.1.0 update - Segmentation fault: 11
2014-07-27 13:19 GMT+02:00 Baptiste Daroussin b...@freebsd.org: This is a known one I'm very sorry about but tricky to fix, to solve it, open your /usr/local/etc/pkg.conf you might have a duplicated entrey in alias (probable leaf), remove the second one, that will solve your problem. Thanks! ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: PKG 3.1.0 update - Segmentation fault: 11
Baptiste Daroussin: This is a known one I'm very sorry about but tricky to fix, to solve it, open your /usr/local/etc/pkg.conf you might have a duplicated entrey in alias (probable leaf), remove the second one, that will solve your problem. regards, Bapt thanks, will try and let you know once being successfully. BR, Jos Chrispijn ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: PKG 3.1.0 update - Segmentation fault: 11
On Sun, Jul 27, 2014 at 01:19:49PM +0200, Baptiste Daroussin wrote: ... This is a known one I'm very sorry about but tricky to fix, to solve it, open your /usr/local/etc/pkg.conf you might have a duplicated entrey in alias (probable leaf), remove the second one, that will solve your problem. Errr...??!? I haven't changed /usr/local/etc/pkg.conf at all. I have 3 systems I'm trying to update, and 2 more to update if I get those done successfully. I use portmaster to build update ports on all 5 systems. Each of the 3 has failed in the installation phase of updating to pkg-1.3.1. Each is running stable/9 @r269090. Two are i386; one is amd64. The i386 systems had been upgraded successfully to pkg-1.3.0; the amd64 system is only updated weekly, so it had been running pkg-1.2.7_4. Each of the 3 has failed with: ... === Installing for pkg-1.3.1 === Registering installation for pkg-1.3.1 Child process pid=11028 terminated abnormally: Segmentation fault: 11 *** [fake-pkg] Error code 245 Stop in /common/ports/ports-mgmt/pkg. *** [/common/ports/ports-mgmt/pkg/work/.install_done.pkg._usr_local] Error code 1 Stop in /common/ports/ports-mgmt/pkg. === A backup package for pkg-1.3.0 should be located in /usr/ports/packages/portmaster-backup === Installation of pkg-1.3.1 (ports-mgmt/pkg) failed === Aborting update === Update for ports-mgmt/pkg failed === Aborting update In each case, the md5 checksum for /usr/local/etc/pkg.conf is 4e302ae1f371e5134ffa717ff693d6f0. I have not done anything with it; I know of no reason I would want to change it. And so far, I haven't found a way to even get any of these systems back to a point where I have any confidence at all that the currently-installed ports and their dependencies are being tracked: on one system, I tried the Reversion to pkg-1.3.0 approach; that yields: You are about to convert your system to pkgng while you have ports/packages installed with the old pkg_install tools. You can choose to: - keep pkg_install as the package management system by adding this line to /etc/make.conf: WITHOUT_PKGNG=yes - switch to pkgng: ... [But I had already switched to pkgng months ago!] I still have /var/db/pkg/local.sqlite on each system. Is the information there slavagable? If so, how? Sorry; I'm a bit frustrated. I intentionally try to avoid weird configurations, and treat pkg pretty much as a black box to track what's where -- and for my purposes (at least) it's best if it Just Works. I appreciate the intent and effort behind the work to implement and improve pkg, and understand that there are assuredly huge challenges for those doing that work. But it never occurred to me that what I'm doing is so far outside the norm that I was at significant risk of experiencing a failure in what I had naively expected to be a routine upgrade. How can I get back to working environments on these 3 systems (and, ideally, proceed with updates to the 2 production systems without breaking their abaility to have updated ports)? Peace, david -- David H. Wolfskill da...@catwhisker.org Taliban: Evil cowards with guns afraid of truth from a 14-year old girl. See http://www.catwhisker.org/~david/publickey.gpg for my public key. pgpxGyaacEU_0.pgp Description: PGP signature
Re: PKG 3.1.0 update - Segmentation fault: 11
David Wolfskill wrote: On Sun, Jul 27, 2014 at 01:19:49PM +0200, Baptiste Daroussin wrote: ... This is a known one I'm very sorry about but tricky to fix, to solve it, open your /usr/local/etc/pkg.conf you might have a duplicated entrey in alias (probable leaf), remove the second one, that will solve your problem. Errr...??!? I haven't changed /usr/local/etc/pkg.conf at all. I have 3 systems I'm trying to update, and 2 more to update if I get those done successfully. I use portmaster to build update ports on all 5 systems. Each of the 3 has failed in the installation phase of updating to pkg-1.3.1. Each is running stable/9 @r269090. Two are i386; one is amd64. The i386 systems had been upgraded successfully to pkg-1.3.0; the amd64 system is only updated weekly, so it had been running pkg-1.2.7_4. Each of the 3 has failed with: ... === Installing for pkg-1.3.1 === Registering installation for pkg-1.3.1 Child process pid=11028 terminated abnormally: Segmentation fault: 11 *** [fake-pkg] Error code 245 Stop in /common/ports/ports-mgmt/pkg. *** [/common/ports/ports-mgmt/pkg/work/.install_done.pkg._usr_local] Error code 1 Stop in /common/ports/ports-mgmt/pkg. === A backup package for pkg-1.3.0 should be located in /usr/ports/packages/portmaster-backup === Installation of pkg-1.3.1 (ports-mgmt/pkg) failed === Aborting update === Update for ports-mgmt/pkg failed === Aborting update In each case, the md5 checksum for /usr/local/etc/pkg.conf is 4e302ae1f371e5134ffa717ff693d6f0. I have not done anything with it; I know of no reason I would want to change it. And so far, I haven't found a way to even get any of these systems back to a point where I have any confidence at all that the currently-installed ports and their dependencies are being tracked: on one system, I tried the Reversion to pkg-1.3.0 approach; that yields: By any chance is there a core file around releated to this, and if so was the binary that faulted unstripped? I'd be interested in seeing the backtrace... (I'm not using 1.3 or even NG on any of my production systems at the moment because I personally don't trust it yet (I have 57 complex systems and if they screw up I end up rebuilding the OS from scratch) so I'd be happy to take a look at any cores an unstripped binaries to see if I can work out why people see this occasionally... Sounds like you have 3 identical systems which 2 worked no problems the third faulted .. this is obviously not good and needs to be fixed, so will give another pair of eyes at the problem. Thanks, -- Michelle Sullivan http://www.mhix.org/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: PKG 3.1.0 update - Segmentation fault: 11
On Sun, Jul 27, 2014 at 02:38:39PM +0200, Michelle Sullivan wrote: ... By any chance is there a core file around releated to this, and if so was the binary that faulted unstripped? In each of the 3 cases, I find a /usr/ports/ports-mgmt/pkg/pkg-static.core file g1-252(9.3-S)[4] sudo file pkg-static.core Password: pkg-static.core: ELF 32-bit LSB core file Intel 80386, version 1 (FreeBSD), FreeBSD-style, from '-static' g1-252(9.3-S)[5] I'd be interested in seeing the backtrace... Well, given it was a segmentation fault, it's not clear to me that I'd be able to find much of value -- I'm way out of practice using gdb, and by the nature of a segmentation fault (or what caused it, anyway), something is pretty confused by the time the fault is discovered. (I'm not using 1.3 or even NG on any of my production systems at the moment because I personally don't trust it yet (I have 57 complex systems and if they screw up I end up rebuilding the OS from scratch) so I'd be happy to take a look at any cores an unstripped binaries to see if I can work out why people see this occasionally... Sounds like you have 3 identical systems which 2 worked no problems the third faulted .. this is obviously not good and needs to be fixed, so will give another pair of eyes at the problem. Err... no I have 5 system in total; 2 haven't failed because I haven't tried to update them yet: if they fail, I don't have access to email (or much of anything else); more critially, neither does my spouse -- and I value domestic tranquility. Of the 3 failures, 2 were on i386; one on amd64. They are all running stable/9 @r269090 (and the 2 that I haven't upgraded yet would normally be upgraded to that point before I start messing with ports on them). I'll be happy to provide any information about this that I can. Peace, david -- David H. Wolfskill da...@catwhisker.org Taliban: Evil cowards with guns afraid of truth from a 14-year old girl. See http://www.catwhisker.org/~david/publickey.gpg for my public key. pgphaddWvYA5I.pgp Description: PGP signature
Re: PKG 3.1.0 update - Segmentation fault: 11
David Wolfskill wrote: On Sun, Jul 27, 2014 at 02:38:39PM +0200, Michelle Sullivan wrote: ... By any chance is there a core file around releated to this, and if so was the binary that faulted unstripped? In each of the 3 cases, I find a /usr/ports/ports-mgmt/pkg/pkg-static.core file g1-252(9.3-S)[4] sudo file pkg-static.core Password: pkg-static.core: ELF 32-bit LSB core file Intel 80386, version 1 (FreeBSD), FreeBSD-style, from '-static' g1-252(9.3-S)[5] Doesn't appear stripped.. I'd be interested in seeing the backtrace... Well, given it was a segmentation fault, it's not clear to me that I'd be able to find much of value -- I'm way out of practice using gdb, and by the nature of a segmentation fault (or what caused it, anyway), something is pretty confused by the time the fault is discovered. Unless the fault smashed the stack often you can find what the problem/cause was. If the stack is smashed you're screwed. gdb path to binary path to core Commands immediately useful: backtrace full (alias: bt full) frame number for which you want to examine if you get a line number/code, 'l' (el) will give the 5 lines eitherside If threaded select each thread before the frame to see what was happening in each thread. If I remember correctly - it's been several years since I last used gdb ;-) If you want to catch a smashed stack problem run the binary in gdb: gdb path to command Then: set args what ever is approrpiate run When it faults most of the time you'll get the stack just prior to the smashing - though I have had some really bad ones when even gdb cored out.. If the process forks out, you will need to use follow-fork.. Regards, Michelle (I'm not using 1.3 or even NG on any of my production systems at the moment because I personally don't trust it yet (I have 57 complex systems and if they screw up I end up rebuilding the OS from scratch) so I'd be happy to take a look at any cores an unstripped binaries to see if I can work out why people see this occasionally... Sounds like you have 3 identical systems which 2 worked no problems the third faulted .. this is obviously not good and needs to be fixed, so will give another pair of eyes at the problem. Err... no I have 5 system in total; 2 haven't failed because I haven't tried to update them yet: if they fail, I don't have access to email (or much of anything else); more critially, neither does my spouse -- and I value domestic tranquility. Ahh - so all 3 failed, the other 2 have not been tried? Of the 3 failures, 2 were on i386; one on amd64. They are all running stable/9 @r269090 (and the 2 that I haven't upgraded yet would normally be upgraded to that point before I start messing with ports on them). I'll be happy to provide any information about this that I can. Regards, Michelle -- Michelle Sullivan http://www.mhix.org/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: PKG 3.1.0 update - Segmentation fault: 11
On Sun, Jul 27, 2014 at 03:22:08PM +0200, Michelle Sullivan wrote:
...
g1-252(9.3-S)[4] sudo file pkg-static.core
Password:
pkg-static.core: ELF 32-bit LSB core file Intel 80386, version 1 (FreeBSD),
FreeBSD-style, from '-static'
g1-252(9.3-S)[5]
Doesn't appear stripped..
I'd be interested in seeing the backtrace...
...
Unless the fault smashed the stack often you can find what the
problem/cause was. If the stack is smashed you're screwed.
gdb path to binary path to core
Well, you see, that's part of the problem: I'm not at all sure
where the executable in question actually is. (There is nothing
named pkg-static in my execution search path.) If I assume(!)
that it's in the port's staging area:
sudo gdb ./pkg-static ../../../../../pkg-static.core
...
Core was generated by `pkg-static'.
Program terminated with signal 11, Segmentation fault.
#0 0x080b6cdc in ?? ()
(gdb) bt
#0 0x080b6cdc in ?? ()
#1 0x28404360 in ?? ()
#2 0x28442220 in ?? ()
#3 0x in ?? ()
(gdb)
...
If you want to catch a smashed stack problem run the binary in gdb:
gdb path to command
Then:
set args what ever is approrpiate
Yes; well... that presumes a familiarity with the internal workings of
pkg which I don't have (and, in all honesty, don't want to have).
When it faults most of the time you'll get the stack just prior to the
smashing - though I have had some really bad ones when even gdb cored out..
Indeed: one gets into interesting issues of figuring out what is
actually reliable information (and what is merely debris).
...
Back on the original topic, I was able to get pkg-1.3.1 installed and
apparently functioning on one system (a headless build machine -- which
has the least number of ports inistalled).
What I ended up doing that seems to have worked(?) was:
* mv /var/db/pkg{,.save}
* mkdir /var/db/pkg
* cp -pr /var/db/pkg.save/local.sqlite /var/db/pkg
* portmaster -d ports-mgmt/pkg
This builds OK, then dies in installation a little peculiarly:
...
Compressing man pages (compress-man)
=== Installing for pkg-1.3.1
=== Checking if ports-mgmt/pkg already installed
=== An older version of ports-mgmt/pkg is already installed (apr-1.5.1.1.5.3_
...[list of every installed port on the machine]...)
You may wish to ``make deinstall'' and install this port again
by ``make reinstall'' to upgrade it properly.
If you really wish to overwrite the old port of ports-mgmt/pkg
without deleting it first, set the variable FORCE_PKG_REGISTER
in your environment or the make install command line.
*** [check-already-installed] Error code 1
* cd /usr/ports/ports-mgmt/pkg make reinstall
Which seems to have made constructive use of the port just built (vs.
building it all over yet again)a nd installed it.
I don't yet know how disruptive this has been to ... well anything
(e.g., the current status of installed ports; ability to update ports in
the future; ...).
Peace,
david
--
David H. Wolfskill da...@catwhisker.org
Taliban: Evil cowards with guns afraid of truth from a 14-year old girl.
See http://www.catwhisker.org/~david/publickey.gpg for my public key.
pgpFXy2iMjGzo.pgp
Description: PGP signature
Re: PKG 3.1.0 update - Segmentation fault: 11
On Sun, Jul 27, 2014 at 06:40:27AM -0700, David Wolfskill wrote: ... Back on the original topic, I was able to get pkg-1.3.1 installed and ... OK; I was able to simplify the process on my 2nd system: * Update /usr/local/etc/pkg.conf (to remove to eduplicate alias definition for leaf). * cd /usr/ports/ports-mgmt/pkg make reinstall Peace, david -- David H. Wolfskill da...@catwhisker.org Taliban: Evil cowards with guns afraid of truth from a 14-year old girl. See http://www.catwhisker.org/~david/publickey.gpg for my public key. pgpcrZ9gcDxQ4.pgp Description: PGP signature
Re: PKG 3.1.0 update - Segmentation fault: 11
On Sun, Jul 27, 2014 at 06:47:52AM -0700, David Wolfskill wrote: On Sun, Jul 27, 2014 at 06:40:27AM -0700, David Wolfskill wrote: ... Back on the original topic, I was able to get pkg-1.3.1 installed and ... OK; I was able to simplify the process on my 2nd system: * Update /usr/local/etc/pkg.conf (to remove to eduplicate alias definition for leaf). * cd /usr/ports/ports-mgmt/pkg make reinstall ... WARNING: Whatever I've done seems to have left me with a somewhat-broken version of pkg. pkg info pkg-1.3.1 (for example) spits out a list of installed packages, vs. providing details of pkg-1.3.1. I'm not at all clear on why this is, but I wanted to discourage folks from doing what I listed above without being aware that it doesn't seem to actually work completely. Peace, david -- David H. Wolfskill da...@catwhisker.org Taliban: Evil cowards with guns afraid of truth from a 14-year old girl. See http://www.catwhisker.org/~david/publickey.gpg for my public key. pgpSjXENQbbwT.pgp Description: PGP signature
Re: PKG 3.1.0 update - Segmentation fault: 11
Jos Chrispijn writes: Baptiste Daroussin: This is a known one I'm very sorry about but tricky to fix, to solve it, open your /usr/local/etc/pkg.conf you might have a duplicated entry in alias (probable leaf), remove the second one, that will solve your problem. regards, Bapt thanks, will try and let you know once being successfully. It worked for me. Respectfully, Robert Huff ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: PKG 3.1.0 update - Segmentation fault: 11
On Sun, Jul 27, 2014 at 07:06:17AM -0700, David Wolfskill wrote: On Sun, Jul 27, 2014 at 06:47:52AM -0700, David Wolfskill wrote: On Sun, Jul 27, 2014 at 06:40:27AM -0700, David Wolfskill wrote: ... Back on the original topic, I was able to get pkg-1.3.1 installed and ... OK; I was able to simplify the process on my 2nd system: * Update /usr/local/etc/pkg.conf (to remove to eduplicate alias definition for leaf). * cd /usr/ports/ports-mgmt/pkg make reinstall ... WARNING: Whatever I've done seems to have left me with a somewhat-broken version of pkg. pkg info pkg-1.3.1 (for example) spits out a list of installed packages, vs. providing details of pkg-1.3.1. I'm not at all clear on why this is, but I wanted to discourage folks from doing what I listed above without being aware that it doesn't seem to actually work completely. ... The above appears to have been caused by some rather unfortunate entries in /usr/local/etc/pkg.conf. I find that moving that file aside allows pkg info to work normally. Peace, david -- David H. Wolfskill da...@catwhisker.org Taliban: Evil cowards with guns afraid of truth from a 14-year old girl. See http://www.catwhisker.org/~david/publickey.gpg for my public key. pgpIllXGQXNOc.pgp Description: PGP signature
