[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Segmentation faults with aptitude and apt-get on some packages




On 11/16/2016 4:30 PM, James Clarke wrote:
>> On 16 Nov 2016, at 22:26, rod <r.schnell@mythos.freeddns.org> wrote:
>>> On 11/16/2016 2:12 PM, rod wrote:
>>>> On 11/16/2016 1:32 PM, James Clarke wrote:
>>>> Hi Rod,
>>>>> On 16 Nov 2016, at 17:13, rod <r.schnell@mythos.freeddns.org> wrote:
>>>>>
>>>>> I followed the guide you wrote (after dumping debian for solaris to
>>>>> reset the sc> password). It works well as written, covering all the
>>>>> issues that came up.
>>>>>
>>>>> The current problem I'm having is this:
>>>>>
>>>>> root@mw-monitor:/home/rod# aptitude
>>>>> Ouch!  Got SIGSEGV, dying..
>>>>> Segmentation fault
>>>>>
>>>>> or
>>>>>
>>>>> root@mw-monitor:/home/rod# apt-get install gunzip
>>>>> Reading package lists... Done
>>>>> Building dependency tree
>>>>> Reading state information... Done
>>>>> ESegmentation fault
>>>>>
>>>>> with this on the console:
>>>>>
>>>>> [ 1656.976655] apt-get[545]: segfault at fff0000200794008 ip
>>>>> fff0000100015994 (rpc fff0000100015970) sp 000007feffa705b1 error 30001
>>>>> in ld-2.24.so[fff0000100000000+22000]
>>>>>
>>>>> Any ideas?
>>>>
>>>> We’ve had to rebuild ~1700 packages built in the last couple of weeks,
>>>> since they were built with a broken binutils. My guess is that aptitude
>>>> was broken by this (it’s one of the packages built during that time
>>>> period).  I am however surprised that apt-get is segfaulting; that was
>>>> built well before any of this mess. If I run that command I get this:
>>>>
>>>> # apt-get install gunzip
>>>> Reading package lists... Done
>>>> Building dependency tree       
>>>> Reading state information... Done
>>>> E: Unable to locate package gunzip
>>>>
>>>> That’s with the latest version (1.3.1). FYI, there is no gunzip package;
>>>> it’s included in gzip.
>>>>
>>>> If you want to get a working system set up now, I suggest you reinstall
>>>> with your mirror configured to a snapshot taken before 2nd November using
>>>> http://snapshot.debian.org/archive/debian-ports/, as it’s going to be a
>>>> few days before everything has finished building. Unfortunately we weren’t
>>>> aware of the problem and how widespread it was when you were installing.
>>>>
>>>> Regards,
>>>> James
>>>
>>> Thanks James.  I did look at the buildd page and saw large number
>>> working on being rebuilt and thought it might be something like this.
>>>
>>> I will change the mirror and reload simple for quickness.
>>>
>>> I figured it was better to mention it...
>>>
>>> Rod
>>
>> OK so new question...
>> Once I've done the reinstall from the archive should I do apt-get update
>> && apt-get upgrade followed by apt-get dist-upgrade?  Will it grab from
>> the newly built packages? Will it bork the newly installed system?
> 
> You can, but it won’t do anything, since the installer should have put the
> snapshot mirror in your /etc/apt/sources.list, so as far as it’s concerned
> everything is up to date. Once everything has been rebuilt, you can put the
> original mirror configuration back in /etc/apt/sources.list and do an upgrade.
> 
> Regards,
> James
> 
Thanks


Reply to: