| Summary: | Request timeout message is shown when one of the node is down | ||
|---|---|---|---|
| Product: | [Retired] GlusterSP | Reporter: | Sachidananda Urs <sac> |
| Component: | core | Assignee: | Harshavardhana <fharshav> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | unspecified | CC: | amarts, avati, cww, fharshav, pavan, platform, shireesh, webteam |
| Target Milestone: | 3.0.5 | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | Type: | --- | |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Balamurugan Arumugam
2010-01-12 08:17:43 UTC
When one of the node is down, none of the servers are shown in the list. `Request timedout' message is shown. This was happening when two nodes (out of 4) were not reachable. Also, I saw in /tmp/transport.log for a get-server-list command there were no responses (even from the same server). Later, I killed python, and everything started working fine. This happens when ejabberd crashes abnormally. Proposed handling of this case is to restart ejabberd if it crashes in a "non-stop" loop. Will be available in 3.0.3 release ejabberd is being removed since 3.0.5 release, all ejabberd related bugs are invalid. Issue with ejabberd - resolved in 3.1.x by removing the dependency on ejabberd |