* runaway gnatsds
2001-12-31 19:40 runaway gnatsds Jason Molenda
@ 2001-04-05 2:22 ` Jason Molenda
2001-12-31 19:40 ` Joseph S. Myers
2001-12-31 19:40 ` Christopher Faylor
2 siblings, 0 replies; 6+ messages in thread
From: Jason Molenda @ 2001-04-05 2:22 UTC (permalink / raw)
To: overseers
[jsm@sourceware automake]$ ps auxwww | grep gnatsd
gnatsid 21910 30.3 0.3 3072 2404 ? R Apr04 182:57 gnatsd gnatsd
gnatsid 22524 29.2 0.2 2912 2264 ? R Apr04 104:37 gnatsd gnatsd
jsm 3492 0.0 0.0 1152 440 pts/1 S 02:16 0:00 grep gnatsd
[jsm@sourceware automake]$ date
Thu Apr 5 02:16:21 PDT 2001
[jsm@sourceware automake]$
It seems unlikely that there is a valid reason for gnatsd to use
two or three hours of CPU time... I tried attaching to one of them
and got a BS stacktrace -
(gdb) attach 22524
Attaching to program `/usr/local/libexec/gnats/gnatsd', Pid 22524
Reading symbols from /lib/libc.so.6...done.
Reading symbols from /lib/ld-linux.so.2...done.
Reading symbols from /lib/libnss_dns.so.2...done.
Reading symbols from /lib/libresolv.so.2...done.
chunk_alloc (ar_ptr=0x400fd580, nb=8256) at malloc.c:2689
malloc.c:2689: No such file or directory.
(gdb) where
#0 chunk_alloc (ar_ptr=0x400fd580, nb=8256) at malloc.c:2689
#1 0x4006cb8a in __libc_malloc (bytes=8250) at malloc.c:2616
#2 0x80583c6 in regfree ()
#3 0x80561d1 in regfree ()
#4 0x805977a in regfree ()
#5 0x805958f in regfree ()
#6 0x804ae01 in strcpy ()
#7 0x804afcc in strcpy ()
#8 0x804aa27 in strcpy ()
#9 0x4002ccb3 in __libc_start_main (main=0x804a62c <strcpy+3040>, argc=2,
argv=0xbffffd84, init=0x804947c, fini=0x805eb7c <getopt_long_only+16860>,
rtld_fini=0x4000a350 <_dl_fini>, stack_end=0xbffffd7c)
at ../sysdeps/generic/libc-start.c:78
(gdb)
Whatever. I'll leave them running in case someone is doing something
unimaginably complicated that I don't know anything about.
Jason
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: runaway gnatsds
2001-12-31 19:40 ` Joseph S. Myers
@ 2001-04-05 3:08 ` Joseph S. Myers
0 siblings, 0 replies; 6+ messages in thread
From: Joseph S. Myers @ 2001-04-05 3:08 UTC (permalink / raw)
To: Jason Molenda; +Cc: overseers
On Thu, 5 Apr 2001, Jason Molenda wrote:
> It seems unlikely that there is a valid reason for gnatsd to use
> two or three hours of CPU time... I tried attaching to one of them
> and got a BS stacktrace -
Could these be related to the GNATS database corruption? Does gnatsd
handle corrupted PRs any better than GNATSweb (which seems to truncate
corrupted lines in the PRs after NUL characters, making me wonder whether
any of the corrupted PRs are getting further and less visibly corrupted by
people editing them)?
http://sources.redhat.com/ml/overseers/2001-q2/msg00013.html
http://gcc.gnu.org/ml/gcc/2001-04/msg00071.html
--
Joseph S. Myers
jsm28@cam.ac.uk
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: runaway gnatsds
2001-12-31 19:40 ` Christopher Faylor
@ 2001-04-05 7:55 ` Christopher Faylor
0 siblings, 0 replies; 6+ messages in thread
From: Christopher Faylor @ 2001-04-05 7:55 UTC (permalink / raw)
To: Jason Molenda; +Cc: overseers
On Thu, Apr 05, 2001 at 02:21:24AM -0700, Jason Molenda wrote:
>[jsm@sourceware automake]$ ps auxwww | grep gnatsd
>gnatsid 21910 30.3 0.3 3072 2404 ? R Apr04 182:57 gnatsd gnatsd
>gnatsid 22524 29.2 0.2 2912 2264 ? R Apr04 104:37 gnatsd gnatsd
>jsm 3492 0.0 0.0 1152 440 pts/1 S 02:16 0:00 grep gnatsd
>[jsm@sourceware automake]$ date
>Thu Apr 5 02:16:21 PDT 2001
>[jsm@sourceware automake]$
>
>It seems unlikely that there is a valid reason for gnatsd to use
>two or three hours of CPU time... I tried attaching to one of them
>and got a BS stacktrace -
I've seen this in the last couple of days. I've been killing the processes.
cgf
^ permalink raw reply [flat|nested] 6+ messages in thread
* runaway gnatsds
@ 2001-12-31 19:40 Jason Molenda
2001-04-05 2:22 ` Jason Molenda
` (2 more replies)
0 siblings, 3 replies; 6+ messages in thread
From: Jason Molenda @ 2001-12-31 19:40 UTC (permalink / raw)
To: overseers
[jsm@sourceware automake]$ ps auxwww | grep gnatsd
gnatsid 21910 30.3 0.3 3072 2404 ? R Apr04 182:57 gnatsd gnatsd
gnatsid 22524 29.2 0.2 2912 2264 ? R Apr04 104:37 gnatsd gnatsd
jsm 3492 0.0 0.0 1152 440 pts/1 S 02:16 0:00 grep gnatsd
[jsm@sourceware automake]$ date
Thu Apr 5 02:16:21 PDT 2001
[jsm@sourceware automake]$
It seems unlikely that there is a valid reason for gnatsd to use
two or three hours of CPU time... I tried attaching to one of them
and got a BS stacktrace -
(gdb) attach 22524
Attaching to program `/usr/local/libexec/gnats/gnatsd', Pid 22524
Reading symbols from /lib/libc.so.6...done.
Reading symbols from /lib/ld-linux.so.2...done.
Reading symbols from /lib/libnss_dns.so.2...done.
Reading symbols from /lib/libresolv.so.2...done.
chunk_alloc (ar_ptr=0x400fd580, nb=8256) at malloc.c:2689
malloc.c:2689: No such file or directory.
(gdb) where
#0 chunk_alloc (ar_ptr=0x400fd580, nb=8256) at malloc.c:2689
#1 0x4006cb8a in __libc_malloc (bytes=8250) at malloc.c:2616
#2 0x80583c6 in regfree ()
#3 0x80561d1 in regfree ()
#4 0x805977a in regfree ()
#5 0x805958f in regfree ()
#6 0x804ae01 in strcpy ()
#7 0x804afcc in strcpy ()
#8 0x804aa27 in strcpy ()
#9 0x4002ccb3 in __libc_start_main (main=0x804a62c <strcpy+3040>, argc=2,
argv=0xbffffd84, init=0x804947c, fini=0x805eb7c <getopt_long_only+16860>,
rtld_fini=0x4000a350 <_dl_fini>, stack_end=0xbffffd7c)
at ../sysdeps/generic/libc-start.c:78
(gdb)
Whatever. I'll leave them running in case someone is doing something
unimaginably complicated that I don't know anything about.
Jason
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: runaway gnatsds
2001-12-31 19:40 runaway gnatsds Jason Molenda
2001-04-05 2:22 ` Jason Molenda
2001-12-31 19:40 ` Joseph S. Myers
@ 2001-12-31 19:40 ` Christopher Faylor
2001-04-05 7:55 ` Christopher Faylor
2 siblings, 1 reply; 6+ messages in thread
From: Christopher Faylor @ 2001-12-31 19:40 UTC (permalink / raw)
To: Jason Molenda; +Cc: overseers
On Thu, Apr 05, 2001 at 02:21:24AM -0700, Jason Molenda wrote:
>[jsm@sourceware automake]$ ps auxwww | grep gnatsd
>gnatsid 21910 30.3 0.3 3072 2404 ? R Apr04 182:57 gnatsd gnatsd
>gnatsid 22524 29.2 0.2 2912 2264 ? R Apr04 104:37 gnatsd gnatsd
>jsm 3492 0.0 0.0 1152 440 pts/1 S 02:16 0:00 grep gnatsd
>[jsm@sourceware automake]$ date
>Thu Apr 5 02:16:21 PDT 2001
>[jsm@sourceware automake]$
>
>It seems unlikely that there is a valid reason for gnatsd to use
>two or three hours of CPU time... I tried attaching to one of them
>and got a BS stacktrace -
I've seen this in the last couple of days. I've been killing the processes.
cgf
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: runaway gnatsds
2001-12-31 19:40 runaway gnatsds Jason Molenda
2001-04-05 2:22 ` Jason Molenda
@ 2001-12-31 19:40 ` Joseph S. Myers
2001-04-05 3:08 ` Joseph S. Myers
2001-12-31 19:40 ` Christopher Faylor
2 siblings, 1 reply; 6+ messages in thread
From: Joseph S. Myers @ 2001-12-31 19:40 UTC (permalink / raw)
To: Jason Molenda; +Cc: overseers
On Thu, 5 Apr 2001, Jason Molenda wrote:
> It seems unlikely that there is a valid reason for gnatsd to use
> two or three hours of CPU time... I tried attaching to one of them
> and got a BS stacktrace -
Could these be related to the GNATS database corruption? Does gnatsd
handle corrupted PRs any better than GNATSweb (which seems to truncate
corrupted lines in the PRs after NUL characters, making me wonder whether
any of the corrupted PRs are getting further and less visibly corrupted by
people editing them)?
http://sources.redhat.com/ml/overseers/2001-q2/msg00013.html
http://gcc.gnu.org/ml/gcc/2001-04/msg00071.html
--
Joseph S. Myers
jsm28@cam.ac.uk
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2001-12-31 19:40 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2001-12-31 19:40 runaway gnatsds Jason Molenda
2001-04-05 2:22 ` Jason Molenda
2001-12-31 19:40 ` Joseph S. Myers
2001-04-05 3:08 ` Joseph S. Myers
2001-12-31 19:40 ` Christopher Faylor
2001-04-05 7:55 ` Christopher Faylor
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).