Multiple RPM package updates fail with SIGSEGV in PYTHON.EXE

[darcio]

I attempted to update several RPM packages, they are:

1) rpm
2) python
3) klusrmgr

All of these appear to fail due to a SIGSEGV in PYTHON.EXE, subsequently I am currently stuck on all the RPM package updates.

Here is a sample of a matching error from the anpm.log :

* START *
[ 29 Apr 2017 12:00:44 ]
Executing: @python G:\UTIL\ANPM\scripts\yum_update.py klusrmgr
Running Transaction Check

Killed by SIGSEGV
pid=0x0068 ppid=0x0067 tid=0x0001 slot=0x00af pri=0x0200 mc=0x0001 ps=0x0010
G:\USR\BIN\PYTHON.EXE
DB48 0:000117ad
cs:eip=005b:132517ad
ss:esp=0053:0012f180 ebp=0012f1e8

ds=0053 es=0053 fs=150b gs=0000 efl=00210246

eax=21050000 ebx=20e10220 ecx=0012f1b8 edx=00000000 edi=0012f1c0 esi=20e10140
Process has been dumped
Return code: 0
* STOP *

[darcio]

ANPM LOG showing multiple PYTHON.EXE errors

[darcio]

In addition to the above, here is the RPM update specific error entry, since it differs somewhat from the other PYTHON.EXE related ones (I'm not sure if this is a separate issue or not???):

* START *
[ 29 Apr 2017 12:01:30 ]
Executing: @python G:\UTIL\ANPM\scripts\yum_update.py rpm
Running Transaction Check
Error: [u'ERROR with transaction check vs depsolve:', 'rpm = 4.13.0-10.oc00 is needed by rpm-python-4.13.0-10.oc00.i686',
'rpm.dll is needed by rpm-python-4.13.0-10.oc00.i686',
'rpmbuild.dll is needed by rpm-python-4.13.0-10.oc00.i686', 'rpmio.dll is needed by rpm-python-4.13.0-10.oc00.i686',
u'Please report this error at http://trac.netlabs.org/rpm/']
YumRPMCheckError()
Return code: 0
* STOP *

[Silvan Scherrer]

what does yum list db4* say? and please don't post ANPM logs here, as we see a lot more details when posting yum logs. But according to ANPM logs, you had some not complete updates like db4.

[darcio]

Here is what I get back:

[G:\]yum list db4*
arcanoae-exp | 1.9 kB 00:00
arcanoae-rel | 1.9 kB 00:00
netlabs-exp | 2.9 kB 00:00
netlabs-rel | 2.9 kB 00:00
netlabs-rel/primary_ | 1.3 MB 00:30 =-] 63 kB/s | 1.2 MB 00:00 ETA
Installed Packages
db4.i686 4.8.30-8.oc00 installed

db4-utils.i686 4.8.30-8.oc00 installed

Available Packages
db4.i386 4.8.30-6.oc00 netlabs-rel

db4-cxx.i386 4.8.30-6.oc00 netlabs-rel

db4-cxx.i686 4.8.30-8.oc00 netlabs-exp

db4-debuginfo.i686 4.8.30-8.oc00 netlabs-exp

db4-devel.i386 4.8.30-6.oc00 netlabs-rel

db4-devel.i686 4.8.30-8.oc00 netlabs-exp

db4-devel-static.i386 4.8.30-6.oc00 netlabs-rel

db4-devel-static.i686 4.8.30-8.oc00 netlabs-exp

db4-utils.i386 4.8.30-6.oc00 netlabs-rel

[Silvan Scherrer]

and what does yum list python* say?
did you retry to update any package after a fresh reboot?

[darcio]

Results of 'yum list python*':

Installed Packages
python.i686 2.7.6-14.oc00 installed
python-libs.i686 2.7.6-14.oc00 installed
python-pycurl.i686 7.19.5.1-2.oc00 installed
Available Packages
python.i386 2.7.6-12.oc00 netlabs-rel
python.i686 2.7.6-17.oc00 netlabs-exp
python-debug.i386 2.7.6-12.oc00 netlabs-rel
python-debug.i686 2.7.6-12.oc00 netlabs-rel
python-debuginfo.i686 2.7.6-17.oc00 netlabs-exp
python-devel.i386 2.7.6-12.oc00 netlabs-rel
python-devel.i686 2.7.6-17.oc00 netlabs-exp
python-libs.i386 2.7.6-12.oc00 netlabs-rel
python-libs.i686 2.7.6-17.oc00 netlabs-exp
python-libxml2.i686 2.9.4-2.oc00 netlabs-rel
python-lxml.i386 3.5.0-1.oc00 netlabs-rel
python-lxml.i686 3.5.0-1.oc00 netlabs-rel
python-lxml-docs.noarch 3.5.0-1.oc00 netlabs-rel
python-magic.i386 5.04-7.oc00 netlabs-rel
python-magic.i686 5.04-7.oc00 netlabs-rel
python-magic.noarch 5.30-2.oc00 netlabs-rel
python-packaging-doc.noarch 16.8-2.oc00 netlabs-exp
python-pycurl.i386 7.19.5.1-1.oc00 netlabs-rel
python-rpm-macros.noarch 1-1.oc00 netlabs-rel
python-srpm-macros.noarch 1-1.oc00 netlabs-rel
python-test.i386 2.7.6-12.oc00 netlabs-rel
python-test.i686 2.7.6-17.oc00 netlabs-exp
python-tools.i386 2.7.6-12.oc00 netlabs-rel
python-tools.i686 2.7.6-17.oc00 netlabs-exp
python2-appdirs.noarch 1.4.3-1.oc00 netlabs-exp
python2-lxml.i686 3.6.4-2.oc00 netlabs-rel
python2-packaging.noarch 16.8-2.oc00 netlabs-exp
python2-pyparsing.noarch 2.1.10-2.oc00 netlabs-exp
python2-rpm.i686 4.13.0-15 netlabs-rel
python2-rpm-macros.noarch 1-1.oc00 netlabs-rel
python2-setuptools.noarch 34.4.1-1.oc00 netlabs-exp
python2-six.noarch 1.10.0-1.oc00 netlabs-rel
python3-rpm-macros.noarch 1-1.oc00 netlabs-rel

After reboot no difference, still the same failure point.

[Silvan Scherrer]

ok probably it's clear what you did. You updated db4 and didn't update python. You should update python to latest as well and the issue might be gone.

[darcio]

Well, my problem is that attempting to update python causes the very same PYTHON.EXE SIGSEGV exception. Belive me, it was one of the very first things I tried guessing that maybe python changed and I needed to update.

Literally, I just tried it, and it produced the following error:

[ 2 May 2017 21:34:58 ]
Executing: @python G:\UTIL\ANPM\scripts\yum_update.py python
Running Transaction Check

Killed by SIGSEGV
pid=0x00a7 ppid=0x00a6 tid=0x0001 slot=0x00dd pri=0x0200 mc=0x0001 ps=0x0010
G:\USR\BIN\PYTHON.EXE
DB48 0:000117ad
cs:eip=005b:164f17ad ss:esp=0053:0012f180 ebp=0012f1e8

ds=0053 es=0053 fs=150b gs=0000 efl=00210246

eax=22030000 ebx=20f491e0 ecx=0012f1b8 edx=00000000 edi=0012f1c0 esi=20eed1a0
Process has been dumped
Return code: 0

[Silvan Scherrer]

you can always use the zip version and update the exe and dll manually. At least that's what I would try. zip are at ​http://rpm.netlabs.org/release/00/zip/

[darcio]

Ok, I will give that a try...but won't this approach leave the RPM/YUM database in an in-consistent state???

It would seem to me that all other packages requiring this release as a pre-requisite will continue to complain...no?

[darcio]

...further on, the currently installed RPM package of python is the latest official release, the only other available upgrade is a exp one at Netlabs...so which one are you suggesting I install?

Is it the ZIP of the current release, or the ZIP of the exp release?

[Silvan Scherrer]

I gave you the wrong link above. Sure you need to try latest python from exp repo as well. As you also installed latest db4 from exp repo.

When the zip update worked, then I suggest to do a yum update python as well. As then the database is consistent again.

[darcio]

Replying to diver:

I gave you the wrong link above. Sure you need to try latest python from exp repo as well. As you also installed latest db4 from exp repo.

When the zip update worked, then I suggest to do a yum update python as well. As then the database is consistent again.

So what link should I use? I have the following RPM package location => ​http://rpm.netlabs.org/release/00/pentium4/i686/

However even though I can pull the EXE & DLL out of the RPM package I'm not sure what to do with the remainder of the contents? Do I "force" them into the \usr\xxx locations?

[Silvan Scherrer]

you need the files from exp repo, not rel repo. exp repo is at ​http://rpm.netlabs.org/experimental/00/zip/
Just use the dll and exe. And try a yum upgrade python afterwards.

[darcio]

Yup, that's precisely what I did. Replaced the EXEs only (all three of them, I assume other than the main one the others are some sort of re-directs???).

Anyways, good news...this appears to have worked. I was able to get the full Python exp release upgraded as well as a couple of the other packages. So this issue seems to have been addressed.

So the root cause, just to make sure understand this and avoid this mistake in the future, was that I upgraded DB4 to exp release and presumably it needed the PYTHON exp release to be installed first?

[Silvan Scherrer]

I'm glad it works again.
And yes this is what you did. You updated one package from Exp repo (DB4 in your case) but not the one requiring the other package (python in your case). Python has a requirement of DB4 4.8.30-8 rpm. So if you had updated python only the issue would not have bitten you.

As all works again, I close this ticket.

[darcio]

OK, let's close the ticket.

Regarding the root cause; DB4 upgrade prior to upgrading PYTHON...not sure how that could be the case given that ANPM (which is the only way I install stuff) will automatically pre-install all the pre-requisites...???

Anyways, my stuff is working now, thank you for your assistance!