I've been noticing that my repo syncs haven't been completing an actual full sync. I had been syncing them through the web GUI, but tonight I tried it via the commandline to see if I could see what was happening. It usually dies after transferring 1013 packages.
And sure enough, doing so tonight yielded the following as soon as it went to transfer the 1014th package (I'm syncing the entire EPEL repo, so this has taken a little bit) python: ./rpmio_internal.h:502: c2f: Assertion `fd && fd->magic == 0x04463138' failed. ORA-24550: signal received: [si_signo=6] [si_errno=0] [si_code=-6] [si_int=4202816] [si_ptr=0x402140] [si_addr=0x4848] kpedbg_dmp_stack()+297<-kpeDbgCrash()+75Cannot open /usr/lib/oracle/11.2/client/lib/libclntsh.so.11.1 for reading: errno=24 <-075E6CC1Cannot open /usr/lib/oracle/11.2/client/lib/libclntsh.so.11.1 for reading: errno=24 <-07377F6F<-gsignal()+80<-abort()+257<-__assert_fail()+251Cannot open /usr/lib/librpmio-4.4.so for reading: errno=24 <-0064B377<-readLead()+84<-rpmReadPackageFile()+155Cannot open /usr/lib/python2.4/site-packages/rpm/_rpmmodule.so for reading: errno=24 <-002B6B60<-PyCFunction_Call()+285<-PyEval_EvalFrame()+18829<-PyEval_EvalFrame()+17663<-PyEval_EvalCodeEx()+2198<-PyEval_EvalFrame()+17398<-PyEval_EvalFrame()+17663<-PyEval_EvalFrame()+17663<-PyEval_EvalFrame()+17663<-PyEval_EvalCodeEx()+2198<-PyEval_EvalFrame()+17398<-PyEval_EvalFrame()+17663<-PyEval_EvalCodeEx()+2198<-PyEval_EvalFrame()+17398<-PyEval_EvalFrame()+17663 Aborted If I start the sync over after the crash, it'll pick up where it left off, so I'm guessing this is a resources issue. _______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list
