Bug 762541 (GLUSTER-809) - changing the IP address in bonding leads to unresponding ejabberd
Summary: changing the IP address in bonding leads to unresponding ejabberd
Keywords:
Status: CLOSED WONTFIX
Alias: GLUSTER-809
Product: GlusterSP
Classification: Retired
Component: core
Version: unspecified
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Balamurugan Arumugam
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-04-08 09:19 UTC by Raghavendra Bhat
Modified: 2010-11-29 10:39 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:


Attachments (Terms of Use)

Description Raghavendra Bhat 2010-04-08 07:09:33 UTC
Just changing the IP address of the bonding will create problem. It says the system is rebooting in 15 seconds, but the system does not reboot. Have to login using ssh and doing manually reboot there will make things proper.

Comment 1 Raghavendra Bhat 2010-04-08 09:19:42 UTC
There were two network interfaces eth0 and eth1. I bonded them together with IP address of the bond as the one present int the general tab. Then I removed eth0 from the bond gave it separate IP address different from the general section. It worked well. Then again included it in bond0 and gave bind0 a different IP address. But after rebooting it doesnot take the password. It says invalid password for the right password also, hence not able to login. But can login through ssh.


Note You need to log in before you can comment on or make changes to this bug.