Bug 469899
Summary: | reported ccsd updates not effective | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | Steve Reichard <sreichar> |
Component: | cman | Assignee: | Christine Caulfield <ccaulfie> |
Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Cluster QE <mspqa-list> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 5.2 | CC: | cluster-maint, edamato |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2009-02-16 14:05:58 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
Steve Reichard
2008-11-04 16:59:22 UTC
Some more coeval syslogs would be helpful, ideally not quite as expurgated as those. Also, it would be helpful if the times were synchronised on the systems. It's hard to make sense of those logs because so much is missing. It might fill up bugzilla but whole logs from before and after an incident (from all systems) are much more useful than carefully grepped logs from a whole day. Also if the node was fenced very soon after the ccsd update it might just be that the new cluster.conf was not flushed to disk I have been struggling with a situation which is fencing nodes under various unexpected circumstance, so your point about not being flushed would seem to be the issue. Just re-read the man page and see that it states that the update is for the working version, not stated as an update to the on-disk file. For tidiness I'll close this. Feel free to reopen it if it happens again and we can get some more information. |