Bug 24232 - problems with ypserv + rmmod
Summary: problems with ypserv + rmmod
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: ypserv
Version: 7.0
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Florian La Roche
QA Contact: Aaron Brown
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-01-17 19:15 UTC by Gerald Teschl
Modified: 2007-04-18 16:30 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2001-03-23 13:46:17 UTC
Embargoed:


Attachments (Terms of Use)

Description Gerald Teschl 2001-01-17 19:15:13 UTC
I don't quite understand this, but here is the problem:
Server and all clients run rh7.0 + all updates.

From time to time ypserve starts spanning children until it reaches its
limit.
The load will go up to 30 and the sever will not react for about a minute.
After that everything is fine again.

Inspecting the log shows that this happens always after rmmod is executed
by
cron:

Jan 16 11:30:01 keen CROND[26630]: (root) CMD (   /sbin/rmmod -as)
Jan 16 11:31:01 keen ypserv[626]: WARNING(ypproc_all_2_svc): too many
running children

A "ps" shows:

  626 ?        D      2:04 ypserv
  642 ?        S      0:00 [ypbind]
  646 ?        S      0:03 [ypbind]
  647 ?        S      0:00 [ypbind]
  651 ?        S      0:02 [ypbind]
<snip>
28643 ?        D      0:00 ypserv
.
.
.
28678 ?        D      0:00 ypserv

It does not happen every time rrmod is executed. In addition, it is not
related
to server activity, since it will also happen in the night when nobody uses
the
system. I have removed the kmod entry form cron.d and it hasn't occured
since.

Comment 1 Florian La Roche 2001-02-13 13:51:52 UTC
I don't see how this "rmmod" can directly be a problem for ypserv. Are you
running in
some limit for the number of processes on this machine?

If you still have logfiles pointing at the real problem we run into here, please
reopen
a new bug-report with more information. It might be that ypserv should have
further
checks for error returns, but I need more information on what exactly is going
wrong.

Thaks for this report.


Comment 2 Gerald Teschl 2001-03-23 13:46:07 UTC
Resolved by the 2.2.17-14 kernel.


Note You need to log in before you can comment on or make changes to this bug.