Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Duplicate
-
3.1.4
-
None
-
None
Description
Virtual IP Address Configuration, config file vaddrs.config is known to be broken:
missing vip_config, which is designed to be a dedicated binary to config Virtual IPs
[May 8 16:18:13.908] Manager {0x7f3c9e4247e0} NOTE: [VMap::Vmap] Added cluster interface 'em1' real ip: '115.238.23.57' to known interfaces
[May 8 16:18:13.908] Manager {0x7f3c9e4247e0} NOTE: [VMap::Vmap] Added interface 'lo' real ip: '127.0.0.1' to known interfaces
[May 8 16:18:13.908] Manager {0x7f3c9e4247e0} NOTE: [VMap::VMap] Already added interface 'em1'. Not adding for real IP '115.238.23.57'
[May 8 16:18:13.908] Manager {0x7f3c9e4247e0} NOTE: [VMap::lt_readAListFile] Adding virtual address '192.168.0.199' interface: 'lo' sub-interface-id '0'
[May 8 16:18:13.908] Manager {0x7f3c9e4247e0} NOTE: [VMap::lt_readAListFile] Interface 'lo' marked as having potential virtual ips
[May 8 16:18:13.908] Manager {0x7f3c9e4247e0} NOTE: [VMap::lt_readAListFile] Adding virtual address '192.168.0.99' interface: 'lo' sub-interface-id '1'
[May 8 16:18:13.908] Manager {0x7f3c9e4247e0} NOTE: [VMap::downAddr] Bringing down addr: '192.168.0.199'
[May 8 16:18:13.908] Manager {0x7f3c9e4247e0} NOTE: [VMap::downAddr] Bringing down addr: '192.168.0.99'
confusing:
1, I think in most case we do need Virtual IP, do we need to management in TS manager?
2, do we need to write a dedicate vip_config file? maybe we need to script it?
3, we need more cleanup in the codes, IE: remove the windows mess 
Attachments
Issue Links
- duplicates
-
-
- Closed
-
- is related to
-
-
- Closed
-