Mailing List Archive: Processes not ending

Processes not ending

Sep 21, 2004, 10:19 AM

Post #1 of 5 (1582 views)

Any of you that were in #gentoo-amd64 last night you know the fiasco I had to go through installing the new glibc in portage, otherwise here is a list of the problems I was having and am having.

It somehow deleted the symlink from /lib to /lib64
PAM got corrupted some how, which I beleve had to do with the above

After fixing the symlink, Klugeflang (sp?) suggested I re-bootstrap, which I did, and then emerge -e world. Well this has caused several SEVERE problems.

No processes will end. They run, and when they are supposed to end, the don't. They just become defunct, and refuse to die, even with kill, and killall.

For some reason the defunt processes make both of my CPUs go to 100% usage, and I've had load raitings in the 10-15 range, which is insane. I tried to reboot, but X refuses to start now saying its lacking a keyboard (wtf?), and if I log in at a console window after one command (ls, ps, emerge, etc) it sticks. The only way I'm able to see whats going on is to get to an unused console and use top. The only way I've been able to kill a running process is to kill it with signal 1 (login).

PLEASE HELP! I'm really screwed here!

Antonio Farinetti, Loyal gentoo user since 2000.

Re: Processes not ending [ In reply to ]

xcourse97 at charter

Sep 21, 2004, 5:07 PM

Post #2 of 5 (1526 views)

Permalink

Sorry to hear about the problems you've been having! Is this a new
system you're building up? or have you already had it running OK and
this is just a new install? What is your hardware configuration?

On Tue, 2004-09-21 at 12:19, Antonio Farinetti wrote:
> Any of you that were in #gentoo-amd64 last night you know the fiasco I
> had to go through installing the new glibc in portage, otherwise here
> is a list of the problems I was having and am having.
> * It somehow deleted the symlink from /lib to /lib64
> * PAM got corrupted some how, which I beleve had to do with the
> above
>
>
> After fixing the symlink, Klugeflang (sp?) suggested I re-bootstrap,
> which I did, and then emerge -e world. Well this has caused several
> SEVERE problems.
>
> No processes will end. They run, and when they are supposed to end,
> the don't. They just become defunct, and refuse to die, even with
> kill, and killall.
>
> For some reason the defunt processes make both of my CPUs go to 100%
> usage, and I've had load raitings in the 10-15 range, which is insane.
> I tried to reboot, but X refuses to start now saying its lacking a
> keyboard (wtf?), and if I log in at a console window after one command
> (ls, ps, emerge, etc) it sticks. The only way I'm able to see whats
> going on is to get to an unused console and use top. The only way I've
> been able to kill a running process is to kill it with signal 1
> (login).
>
> PLEASE HELP! I'm really screwed here!
>
> Antonio Farinetti, Loyal gentoo user since 2000.
>

--
gentoo-amd64@gentoo.org mailing list

Re: Processes not ending [ In reply to ]

antonio_farinetti at yahoo

Sep 21, 2004, 7:19 PM

Post #3 of 5 (1524 views)

Permalink

It was a current system, that got updated to the 0918
release of glibc, upon the advice of people in
#gentoo-amd64, I have reformatted because nothing they
could suggest helped. I believe LV chalked this up to
a glibc thing.

Oh well.

emerge -u life -p

Tony
--- William Tetrault <xcourse97@charter.net> wrote:

> Sorry to hear about the problems you've been having!
> Is this a new
> system you're building up? or have you already had
> it running OK and
> this is just a new install? What is your hardware
> configuration?
>
> On Tue, 2004-09-21 at 12:19, Antonio Farinetti
> wrote:
> > Any of you that were in #gentoo-amd64 last night
> you know the fiasco I
> > had to go through installing the new glibc in
> portage, otherwise here
> > is a list of the problems I was having and am
> having.
> > * It somehow deleted the symlink from /lib
> to /lib64
> > * PAM got corrupted some how, which I beleve
> had to do with the
> > above
> >
> >
> > After fixing the symlink, Klugeflang (sp?)
> suggested I re-bootstrap,
> > which I did, and then emerge -e world. Well this
> has caused several
> > SEVERE problems.
> >
> > No processes will end. They run, and when they are
> supposed to end,
> > the don't. They just become defunct, and refuse to
> die, even with
> > kill, and killall.
> >
> > For some reason the defunt processes make both of
> my CPUs go to 100%
> > usage, and I've had load raitings in the 10-15
> range, which is insane.
> > I tried to reboot, but X refuses to start now
> saying its lacking a
> > keyboard (wtf?), and if I log in at a console
> window after one command
> > (ls, ps, emerge, etc) it sticks. The only way I'm
> able to see whats
> > going on is to get to an unused console and use
> top. The only way I've
> > been able to kill a running process is to kill it
> with signal 1
> > (login).
> >
> > PLEASE HELP! I'm really screwed here!
> >
> > Antonio Farinetti, Loyal gentoo user since 2000.
> >
>
>
> --
> gentoo-amd64@gentoo.org mailing list
>
>

=====
Antonio Farinetti
Lamar University Physics and Computer Science Department
Home: (409) 838 - 4641
Cell: (281) 814 - 0684

--
gentoo-amd64@gentoo.org mailing list

Re: Processes not ending [ In reply to ]

jhuebel at gentoo

Sep 21, 2004, 8:32 PM

Post #4 of 5 (1533 views)

Permalink

On Tuesday 21 September 2004 9:19 pm, Antonio Farinetti wrote:
> It was a current system, that got updated to the 0918
> release of glibc, upon the advice of people in
> #gentoo-amd64, I have reformatted because nothing they
> could suggest helped. I believe LV chalked this up to
> a glibc thing.
>
> Oh well.
>
> emerge -u life -p

It's just one of the dangers of running the "testing" packages. You take the
chance that your system could become unstable. :-/

Sorry to hear about the problems you had. But thanks for finding the issues
for us so the next person's experience is better! ;-)

--
Jason Huebel
Gentoo/amd64 Strategic Lead
Gentoo Developer Relations/Recruiter

GPG Public Key:
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x9BA9E230

"Do not weep; do not wax indignant. Understand."
Baruch Spinoza (1632 - 1677)

Re: Processes not ending [ In reply to ]

antonio_farinetti at yahoo

Sep 22, 2004, 6:58 AM

Post #5 of 5 (1531 views)

Permalink

Just FYI I used your stage 3 tarball for 2004.3 and everything is working great, I believe it should be emerging X by now.

But one little issue I noticed

/etc/make.profile points to /usr/portage/profiles/amd64-gcc34-2004.1 (or whatever)

LV mentioned it should point to /usr/portage/profiles/generic-linux/ something or other...

But otherwise building the new gcc/glibc 20040818, etc worked GREAT, goood job jason!

Jason Huebel <jhuebel@gentoo.org> wrote:
On Tuesday 21 September 2004 9:19 pm, Antonio Farinetti wrote:
> It was a current system, that got updated to the 0918
> release of glibc, upon the advice of people in
> #gentoo-amd64, I have reformatted because nothing they
> could suggest helped. I believe LV chalked this up to
> a glibc thing.
>
> Oh well.
>
> emerge -u life -p

It's just one of the dangers of running the "testing" packages. You take the
chance that your system could become unstable. :-/

Sorry to hear about the problems you had. But thanks for finding the issues
for us so the next person's experience is better! ;-)

--
Jason Huebel
Gentoo/amd64 Strategic Lead
Gentoo Developer Relations/Recruiter

GPG Public Key:
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x9BA9E230

"Do not weep; do not wax indignant. Understand."
Baruch Spinoza (1632 - 1677)

> ATTACHMENT part 2 application/pgp-signature

Antonio Farinetti
Lamar University Physics and Computer Science Department
Home: (409) 838 - 4641
Cell: (281) 814 - 0684