Date: Wed, 14 Jul 2004 10:24:54 -0700 (PDT) From: Doug White <dwhite@gumbysoft.com> To: Daniel Lang <dl@leo.org> Cc: current@freebsd.org Subject: Re: calcru: runtime went backwards Message-ID: <20040714102226.B7621@carver.gumbysoft.com> In-Reply-To: <20040714170519.GA4100@atrbg11.informatik.tu-muenchen.de> References: <20040714170519.GA4100@atrbg11.informatik.tu-muenchen.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 14 Jul 2004, Daniel Lang wrote: > since my most severe problems appear to be resolved, no more > panics so far (*knock on wood*), I would like to ask about > some other matters which are occurring on this host (see now > resolved and closed PR kern/68779 for machine details). > > 1. I get tons of messages like this on the console: > > calcru: runtime went backwards from 31915600 usec to 31915590 usec for pid 1265 (httpd) FreeBSD version or source update time would be nice. Do you have WITNESS and/or INVARIANTS enabled? > It always seems to be a httpd process. httpd is apache2 linked with > "libthr". It especially happens if I use the 'ps' and the 'top' > command. If this happens, the controlling terminal where the > command (e.g. ps) was issued, hangs for a while. Everything else > seems to be fine, though. > > I recall that there was a thread in -current about this matter, > but I couldn't find any solution right now... There aren't a lot of libthr uses... thought of trying libpthread? > 2. I also get lots of the following messages: > > [..] > Jul 14 18:02:08 atleo6 ftpd[81983]: getsockname (/usr/libexec/ftpd): Socket operation on non-socket > Jul 14 18:02:26 atleo6 ftpd[81992]: getsockname (/usr/libexec/ftpd): Socket operation on non-socket > Jul 14 18:03:56 atleo6 ftpd[82043]: getsockname (/usr/libexec/ftpd): Socket operation on non-socket > Jul 14 18:04:23 atleo6 ftpd[82055]: getsockname (/usr/libexec/ftpd): Socket operation on non-socket > [..] > > What could be wrong with ftpd here? I thought about ktracing ftpd, but > there are 200-300 concurrent ftpd processes active and the messages > appear very irregulary. If I could ktrace the parent ftpd and all > its childen, I'm afraid the trace-log would fill up all disk-space > before the problem even appears... Suggestions are appreciated > though. Is this the stock ftpd? -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040714102226.B7621>