INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Jobs

Secondary rebooted primary

Secondary rebooted primary

(OP)
Had a strange thing happen with my LDIR pair.  The secondary has been master for some time.  It 5:24 it notices that its mate (on the primary end of the failover cable) is not reachable and stops perceiving reals and virtuals as being up.  But there are no network problems at the time and in fact the mate is sending syslogging during the 40 minute problem period.  And other monitoring shows the web servers are all up and reachable.  But the oddest part and what I hoped someone would comment on - is the secondary winds up on its own rebooting the primary after 40 minutes or these CRIT messages. "Secondary: Hello communication resumed for all interfaces, reseting partner"  It turned out to be a great move because everything restored at that time and Primary became active.  But can anyone explain how one member of a pair can reboot the other???


Feb  6 05:24:12 111.55.77.70  Feb 6 07:19:43 LD-CRIT Secondary: Testing Interface 1
Feb  6 05:24:13 111.55.77.70  Feb 6 07:19:44 LD-CRIT Secondary: Mate's interface 1 failed
Feb  6 05:24:13 111.55.77.70  Feb 6 07:19:44 LD-CRIT Secondary: Testing on interface 1 Passed
Feb  6 05:24:13 111.55.77.70  Feb 6 07:19:44 LD-CRIT Secondary: Lost Failover communications with mate on interface 0
Feb  6 05:24:13 111.55.77.70  Feb 6 07:19:44 LD-CRIT Secondary: Testing Interface 0
Feb  6 05:24:13 111.55.77.70  Feb 6 07:20:11 LD-CRIT Real machine 'web25:7443:0:tcp': Failed (No answer).
Feb  6 05:24:26 111.55.77.70  Feb 6 07:20:23 LD-CRIT Secondary: Lost Failover communications with mate on interface 1
Feb  6 05:25:22 111.55.77.70  Feb 6 07:20:34 LD-CRIT Secondary: Testing on interface 1 Failed
Feb  6 05:25:22 111.55.77.70  Feb 6 07:20:34 LD-CRIT Secondary: Lost Failover communications with mate on interface 0
Feb  6 05:25:23 111.55.77.70  Feb 6 07:20:34 LD-CRIT Secondary: Testing Interface 0
Feb  6 05:26:09 111.55.77.70  Feb 6 07:22:00 LD-CRIT Secondary: Lost Failover communications with mate on interface 1
Feb  6 05:26:09 111.55.77.70  Feb 6 07:22:00 LD-CRIT Secondary: Testing Interface 1
Feb  6 05:26:18 111.55.77.70  Feb 6 07:22:11 LD-CRIT Secondary: Testing on interface 1 Failed
Feb  6 05:26:19 111.55.77.70  Feb 6 07:22:13 LD-CRIT Secondary: Mate's interface 0 failed
Feb  6 05:26:19 111.55.77.70  Feb 6 07:22:13 LD-CRIT Secondary: Testing on interface 0 Passed
.
.
Feb 6 06:00:24 111.55.77.70 Feb 6 07:56:39 LD-CRIT Secondary: Testing on interface 1 Failed
Feb 6 06:00:25 111.55.77.70 Feb 6 07:56:42 LD-CRIT Virtual machine 'service:443:0:tcp': Brought into service.
Feb 6 06:00:25 111.55.77.70 Feb 6 07:56:42 LD-CRIT Virtual machine 'service:443:0:tcp': Failed.
Feb 6 06:00:25 111.55.77.70 Feb 6 07:56:42 LD-CRIT Virtual machine 's1:443:0:tcp': Brought into service.
Feb 6 06:00:26 111.55.77.70 Feb 6 07:56:42 LD-CRIT Virtual machine 's1:443:0:tcp': Failed.
Feb 6 06:00:27 111.55.77.70 Feb 6 07:56:44 LD-CRIT Secondary: Lost Failover communications with mate on interface 2
Feb 6 06:00:27 111.55.77.70 Feb 6 07:56:44 LD-CRIT Secondary: Testing Interface 2
Feb 6 06:00:36 111.55.77.70 Feb 6 07:56:55 LD-CRIT Secondary: Testing on interface 2 Failed
Feb 6 06:00:36 111.55.77.70 Feb 6 07:56:55 LD-CRIT Secondary: Monitoring on interface 0 normal
Feb 6 06:00:36 111.55.77.70 Feb 6 07:56:55 LD-CRIT Secondary: Hello communication resumed for all interfaces, reseting partner
Feb 6 06:00:41 111.55.77.70 Feb 6 07:57:00 LD-CRIT Secondary: Switching to STNDBY.

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members!

Resources

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close