Bug 90000
| Summary: | xinet crashes without any reason | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | Kristian Sørensen <ks> |
| Component: | xinetd | Assignee: | Jay Fenlason <fenlason> |
| Status: | CLOSED ERRATA | QA Contact: | Brock Organ <borgan> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 9 | CC: | jfeeney, linux_4ever |
| 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: | 2003-08-07 15:13:28 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
Kristian Sørensen
2003-04-30 23:33:14 UTC
My guess is that portmapper isn't running on your machine. As root, try: ps -ef | grep port See if portmapper is running. If it is running, could you post the xinetd config for sgi_fam & pop3s. If portmapper is not running, I would disable the sgi_fam service. Nautilis is the only program that actually wants sgi_fam. Most servers never run X so it can be disabled in most cases. Portmapper is not running and X is required, so this is not an option. I did not quite understand what you meant by this: "If it is (portmapper running) running, could you post the xinetd config for sgi_fam & pop3s." What is this - and how is it done. Would it help for me to start portmapper? >Portmapper is not running and X is required
This is your problem. Start portmap like so: /etc/rc.d/init.d/portmap start
Then you can re-test xinetd.
To make it automatically start on boot: /sbin/chkconfig --level 5 portmap on
sgi_fam is trying to register with the portmapper daemon and it wasn't running.
Xinetd was simply reporting sgi_fam not being able to do so. I don't know if
this solves the ultimate problem of xinetd crashing, but it should get rid of
the sgi_fam message.
If you still have a problem, what does crashing mean? Has xinetd exited? How
long does it take before it crashes? The pop3 configuration would be in either
/etc/xinetd.conf or /etc/xinetd.d/(program or service name). Look for something
with port = pop3 or port = 110.
The problem is very sporatic. I have not experienced it in the past 5 days or so. >If you still have a problem, what does crashing mean? This means that xinetd stops suddenly without any warning messages in any log files ect. >Has xinetd exited? yes. >How long does it take before it crashes? The computer is actually also my workstation, and I have installed Postfix as MTA for testing purposes. The computer is only running in the daytime, as I am the onlyone who send mail to my own mailserver. The reason I discovered that Xinetd stops is that I use Xinetd to spawn pop3s-threads for my e-mail program. The times Xinetd has stoped, my computer have been running for 4-6 hours - but the MTA has not in any way been hard loaded! I don't know how we are to get closer on this problem. If I observe new stuff regarding this, I will post it for you. Can you try the errata candidate xinetd that's currently going through QA here? I put a copy in http://people.redhat.com/fenlason/.xinetd/xinetd-2.3.11-1.9.0.i386.rpm It has a fair number of bugfixes over the 2.3.10 version that was shipped with Red Hat Linux 9. Closing this since the submitter hasn't responded and the errata went out. |