Bug 56581
| Summary: | Broken Pipe errors. | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | Neil Darlow <neil> |
| Component: | fam | Assignee: | Alexander Larsson <alexl> |
| Status: | CLOSED RAWHIDE | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | low | ||
| Version: | 7.2 | CC: | alexl, hetz |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i386 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2001-11-29 00:04:31 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
Neil Darlow
2001-11-21 12:52:03 UTC
This would seem to indicate some fam client shutting down uncleanly. What apps do you typically run? The process id attached to the Broken pipe errors associates with: xinetd[pid]: warning: can't get client address: Transport endpoint is not connected I've seen that before. I've never really understood why it appears though. I will have to research it in detail some day. It seems harmless though. I think there might be a degree of urgency here. Consider: Nov 20 13:41:36 ideal fam[10420]: fd 9 write error: Broken pipe Nov 20 13:41:36 ideal last message repeated 609 times I'd say that 609 loggings within a one second period is a lot of syslog traffic. That's got to hurt system performance. Ok. I researched the "can't get client address: Transport endpoint is not connected" message, and it is harmless. It is more or less a bug in xinetd, where it calls getpeername() on the wrong socket (the listening socket instead of the client socket). This message will be printed by xinetd each time it starts fam. That is not the reason for your other message though. It seems some app connects to fam, and then dies. Do you have any idea what app this is? I get this message when starting up KDE, so it's probably some KDE app exiting without calling FAMClose() (or equivalently, not destroying the KDirWatch object). I think it's mostly harmless. It seems to only happen on startup. I'm reassigning this to kde-libs, which is clearly wrong, but there is no general "kde" component, and i don't know which app to blame. I'm hoping bero might look closer into this. I'm running KDE also. The fam errors don't appear to be related to other syslog messages consistently. On several occasions, too often to be considered coincidence, I do see this: Nov 26 12:52:03 ideal xinetd[8904]: warning: can't get client address: Transport endpoint is not connected Nov 26 12:52:17 ideal modprobe: modprobe: Can't locate module sound-slot-1 Nov 26 12:52:17 ideal modprobe: modprobe: Can't locate module sound-service-1-0 Nov 26 12:52:17 ideal modprobe: modprobe: Can't locate module sound-slot-1 Nov 26 12:52:18 ideal modprobe: modprobe: Can't locate module sound-service-1-0 I have a Soundblaster 16 Value card. ISA Plug and Play which I configured ok with sndconfig. The faulty application could be related to ArTs or somesuch. There's precious little else to go on though. Even examining the timestamps of the /tmp/.famXXXX files doesn't tie-up with syslog entries to any degree. That's 14 seconds from something connection to fam to something trying to open the sound device. Probably not the same app. I looked more into this, and is seems to actually be a fam problem. The app cancels all the monitored objects, and then closes the connection, only all the messages are queued up in the unix-domain socket, so the client closed the connection before the server starts handling the cancel messages. And for some reason fam tries to write to the client when handling the message, leading to it getting broken pipe errors and printing warnings. This is not an actual problem, but should be fixed. It's not highly priorotized though. 2 things: 1. It's not KDE specific as I've shawn to you both (alexl and bero) 2. Why it's not highly prioritize? it severly kills the performance if I get 770 error messages... Hetz is just reinforcing my performance-hit comment. Remember, it's populating /tmp with .famXXXX files as well as clogging syslog. I'd say this is also a quality issue. It reflects badly if not fixed. I will fix it. I just won't drop other important things and scramble to get this fixed. Anyway, if someone thinks this is extremely important to get fixed today, I'm accepting patches. Ok. This is fixed in 2.6.6-1, which will be availible in rawhide whenever the buildsystem syncs to rawhide. I'll send the patch upstream. Umm, that will be a bit of a problem since RH 8.0 won't be backward compatible with RH 7.2 (gcc, glibc, etc...) Could you put somewhere an SRPM and I'll rebuild it on 7.2? I'll be happy to provide the RPM's back ;) Hetz I've build 7.2 packages too. I will push them tomorrow. i386 rpms + SRPMS availible at: http://people.redhat.com/alexl/RPMS/ |