Bug 77660
| Summary: | rstatd croaks upon receiving rup call | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 2.1 | Reporter: | Norm Murray <nmurray> |
| Component: | rusers | Assignee: | Phil Knirsch <pknirsch> |
| Status: | CLOSED ERRATA | QA Contact: | Ben Levenson <benl> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 2.1 | CC: | nmurray, rvokal, tao |
| 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: | 2003-02-24 21:17:02 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
Norm Murray
2002-11-11 16:41:28 UTC
Updates from Issue Tracker 10262......... MY REQUEST TO CUSTOMER (FORD) ON 2002/11/27: The responsible Engineer is looking at the problem and would like to know which AS 2.1 kernel and rusers-server you are using? ------ Please type "rpm -qa | grep kernel" (without the quotes) and post the output here. It should be something like "kernel-2.4.9-e.2". Please type "rpm -qa | grep rusers-server" and post the output here. ----- Also, please type "rpm -V kernel" (again without quotes) and post the output here. It should look something like ".M...... /dev/shm" ---- Thanks ------------------------------------------------------ CUSTOMER'S RESPONSE ON 2002/12/03: Customer response rpm -qa | grep kernel reveals: kernel-2.4.9-e.9 (the updated kernel) kernel-headers-2.4.9-e.9 kernel-utils-2.4.6 rusers-server is rusers-server-0.17-12 rpm -V kernel reveals only: .M...... /dev/shm Chris Runge provided us with a "temporary" fix, in an unsupported rpm. He should be able to point you at what was done to fix it. I have verified that the same failure occurs even on a server which has been upgraded with all updates. A rup call from a remote box still kills rstatd. ----------------------------------- REQUEST THAT ENGINEERING PROVIDE AN UPDATE TO THE CUSTOMER PLEASE. I WILL APPEND IT TO ISSUE TRACKER SO CUSTOMER CAN VIEW IT. THANKS. Packages done, errata generated (http://porkchop.redhat.com/errata/erratainfo.cgi?advisory=2002:278) Waiting for QA now. Read ya, Phil Status update: The Director of AS Errata say that our rough estimate is the end of the month (January 2003). We are testing our first quarterly errata bundle which will have that errata in it. I hope to be all caught up with errata at that time. An errata has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on the solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2002-278.html Customer reporting bug still exists... Customer is running most current rusers and rusers-server errata, as well as all other updates. When rup is used, the rstatd daemon crashes with no visible crash output...just disappears. Please cancel REOPEN from Summer Sexton on 2003-02-24 14:42 As I prepared additional documentation to assist in debugging I discovered I had window to wrong server. The server with ALL updates installed does, in fact, now work. Sorry for any inconvenience this caused (so many desktops, so many windows, so little mind :) Now need to open/update request for rstatd bug fix on 7.2 & 7.3 |