Bug 73717
Summary: | The following message is appearing "kernel: request_module[net-pf-10]: fork failed, errno 12" | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | william ewing <ewingw> |
Component: | kernel | Assignee: | Arjan van de Ven <arjanv> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Brian Brock <bbrock> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 7.1 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2004-09-30 15:39:55 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
william ewing
2002-09-09 11:44:55 UTC
what kernel version are you using ? Kernel Version is 2.4.9-34enterprise on a dual processor server with 4GB of RAM any chance you're using a program that creates a lot of threads ? I believe I am using a program that generates alot of threads ! There is one deamon which generates for each person that is logging in a new process. ie we have 1 ADVMAIL.SCKD process and it generates 1500 UAL.REMOTE (one for each person that logs into the E-Mail system) Is there a solution ? Is there any more INFO required ? ok to get it clear: you get 1500 processes. Do these processes each have threads? (I assume not, things would blow up before that ;) orry for my ignorance How do I get the information regarding threads that you want to know are you using HP OpenMail ? Yes I am using HP OPenMail Any Update on this call ? the only way we can go over 1200 openmail processes is with the current kernel in rawhide ;( there is unfortionatly a 1200 (or thereabouts) hard limit in the 2.4.18 and previous kernels for processes linked against -lpthreads, openmail does 1 per connection so there is a limit of 1200 openmail connections ;( Thanks but I had already worked that out and HP OpenMail have recompiled their UAL.REMOTE process without lpthreads. I have have had between 1500- 1600 E-Mail users on the system at any one time. At certain times, most likely peak times, I get the above error (request_module (net-pf-10) ) what does it mean and how can I overcome it ? (net-pf-10) is IPv6 (the next generation internet protocol with bigger addresses) While our kernels support ipv6 as a loadable module, I really doubt you want this in your setup. You can disable this message by putting alias net-pf-10 off in /etc/modules.conf Thanks, I have made the change to the modules.conf file but how to I invoke it ? Do I need to reboot ? it's supposed to be immediate if it's not then I'll check more I have rebooted the server but I am still getting the same error. Below is a copy of my modules.conf alias eth0 eepro100 alias eth1 eepro100 alias eth2 eepro100 alias scsi_hostadapter aic7xxx alias scsi_hostadapter2 cciss alias parport_lowlevel parport_pc alias usb-controller usb-ohci alias net-pf-10 off Is this ok ? Any other suggestions ? well modprobe ipv6 will work ;( (note of warning: if you do that and you have a firewall on the machine you also must set up ipv6 based firewall rules probably) Any other thoughts on stopping the request module failure ? Ok the fork failed is it trying to start a new process and failing because you have the maximum processes allowed running. That is logged and occurs before it can find out that ipv6 is off anyway. You could up the max processes with sysctl I guess I have ran sysctl -A and there are alot of entries . which one would I need to change ? and should I increase it by 10%, 50% , 100% .... Just checking again on now to use the sysctl to max the processes Please you please give me a hint on how to use sysctl to increase the number of Processes Thanks for the bug report. However, Red Hat no longer maintains this version of the product. Please upgrade to the latest version and open a new bug if the problem persists. The Fedora Legacy project (http://fedoralegacy.org/) maintains some older releases, and if you believe this bug is interesting to them, please report the problem in the bug tracker at: http://bugzilla.fedora.us/ |