- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- Re: Package Start fails w/ IP configured
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-20-2006 03:02 AM
тАО03-20-2006 03:02 AM
Package Start fails w/ IP configured
Cluster is running,
w/ Lock lun initialized
adding a package works
mounting FS works
adding an IP to the packages reboots the node.
package log says
WARNING: IP 10.10.5.5 is already configured on the subnet 10.10.5.0
cmrunpkg says:
cmcld[6818]: Aborting! select failed (file: rcomm/comm_ip.c, line: 443)
/var/log/messages says:
Mar 20 07:37:07 sgnode-2 CM-pkg1[6876]: cmmodnet -a -i 10.10.4.201 10.10.4.0
Mar 20 07:37:07 sgnode-2 cmcld[6663]: select for port 46356 failed with Interrupted system call
Mar 20 16:37:07 sgnode-2 kernel: NET: Registered protocol family 17
Mar 20 07:37:07 sgnode-2 cmcld[6663]: select for port 46100 failed with Interrupted system call
Mar 20 07:37:07 sgnode-2 cmcld[6663]: Aborting! select failed (file: lcomm/local_server.c, line: 1165)
Mar 20 07:37:07 sgnode-2 cmcld[6663]: 18, 95774e60, 1a2d
Mar 20 07:37:07 sgnode-2 cmcld[6663]: 14 (read)
Mar 20 07:37:07 sgnode-2 cmcld[6663]: 18 (read)
Mar 20 07:37:07 sgnode-2 cmcld[6663]: Aborting! select failed (file: rcomm/comm_ip.c, line: 443)
What's wrong here?
(of course I checked there is no duplicate IP, which would respond to ping)
Regards
Bernhard
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-20-2006 03:06 AM
тАО03-20-2006 03:06 AM
Re: Package Start fails w/ IP configured
WARNING: IP 10.10.5.5 is already configured on the subnet 10.10.5.0
should be
WARNING: IP 10.10.4.201 is already configured on the subnet 10.10.4.0
(I did a test with a package IP on the other heartbeat NIC and copied this line from that test, that is why it does not match above).
Regards,
Bernhard
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-20-2006 04:13 AM
тАО03-20-2006 04:13 AM
Re: Package Start fails w/ IP configured
works like a treat, however running "cmmodnet -i -a 10.10.4.201 10.10.4.0" gives exactly the same result as with the package start.
anybody listening out there?
Regards,
Bernhard
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-20-2006 05:49 AM
тАО03-20-2006 05:49 AM
Re: Package Start fails w/ IP configured
How new is the cluster? If network reconfiguration could have taken place since the cluster creation, it may be necessary to rebuild the cluster (incorrect LAN / NIC info in the binary maybe).
Also, what version of Serviceguard is installed, and version of linux?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-20-2006 07:32 PM
тАО03-20-2006 07:32 PM
Re: Package Start fails w/ IP configured
both nodes behave exactly the same way
they are BL20p running SLES9 SP2 Kernel 2.6.5-7.244-smp x86_64 ; MC/SG is 11.16.01
Is this an unsupported config? if yes, is it known *not* to work?
(I did the bonding of the network interfaces before the cluster setup, and I reverted to non-bonding NICs and re-created the cluster without NIC bonding, result is the same)
Regards,
Bernhard
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-20-2006 08:35 PM
тАО03-20-2006 08:35 PM
Re: Package Start fails w/ IP configured
I presume that you have checked to make sure that the ip 10.10.4.201 is not already configured prior to the cmmodnet? Maybe add an ifconfig statement to display the information immediately before the call to cmmodnet to check.
Hoever, even if there is some other problem, cmcld should not abort but should handle the situation gracefully.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-22-2006 08:11 PM
тАО03-22-2006 08:11 PM
Re: Package Start fails w/ IP configured
unfortunately this is only a test case, we resorted to installing 32-bit Linux on the blades which resolves the MC/SG issue.
however, it would be nice to know if the issue is resolved on x86_64 with sg 11.16.02 (which I cannot test)
Regards,
Bernhard