Forum
Welcome, Guest
Username: Password: Remember me
This is the optional category header for the Suggestion Box.

TOPIC: Installed new NIC, now Slave in WFConnection State

Installed new NIC, now Slave in WFConnection State 8 months 6 days ago #1558

We were having consistent issues with the network connectivity in one of our hosts so we took it down and replaced the NIC, now the primary hypervisor says:
--------------------------------------------------------
| iSCSI-HA Status: Running 4418                        |
| Last Updated: Fri Feb 16 16:23:34 CST 2018           |
| HOST ROLE:              SLAVE                        |
| VIRTUAL IP:             10.10.10.3 is not local      |
| ISCSI TARGET:           Stopped [expected stopped]   |
| DRBD ROLE:              iscsi1=Secondary             |
| DRBD CONNECTION:        iscsi1 in WFConnection state |
--------------------------------------------------------
Control + C to exit


---------------
| DRBD Status |
---------------

-------------------------------------------------
| version: 8.4.5 (api:1/proto:86-101)                                         |
| srcversion: 2A6B2FA4F0703B49CA9C727                                         |
|  1: cs:WFConnection ro:Secondary/Unknown ds:UpToDate/DUnknown C r-----      |
|     ns:0 nr:0 dw:0 dr:0 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:f oos:5066752 |
--------------------------------------------------

We tried pinging 10.10.10.3 on this host and it responded.

I noticed Salvatore mentioned we should run this on the primary host to get them to resync:

drbdadm -- --overwrite-data-of-peer primary iscsi1

But I'm afraid to run that considering it's saying 10.10.10.3 isn't local.
The administrator has disabled public write access.

Installed new NIC, now Slave in WFConnection State 8 months 5 days ago #1559

It appears that your primary server has been demoted to the slave role and the floating ip is live on the other host

Chances are the other host had issues starting DRBD. Try shutting down services tnd then start again with the following commands:

service iscsi-ha-watchdog
service iscsi-ha stop
service drbd stop
systemctl forcedstop tgtd
service iscsi-ha-watchdog start

Also, your situation does not require a resync like the other post you referred to. In the other case, there was no data on a newly introduced host. Your situation is different in that your data is intact on both hosts and will be brought up to data as soon as drbd connects.
The administrator has disabled public write access.

Installed new NIC, now Slave in WFConnection State 8 months 3 days ago #1560

Thank you for your response, Salvatore! Unfortunately, that didn't do it. I ran the commands you posted on just the hypervisor that I'm talking about (one command failed, systemctl forcedstop tgtd didn't really match anything that I tabbed into).

It brought me back to this. Should I run it on both hypervisors? I should also mention that this hypervisor doesn't have any of the hosts running on it right now. They're all running on the other server.
--------------------------------
| iSCSI-HA Version IHA_2.1.5   |
| Sun Feb 18 16:57:55 CST 2018 |
--------------------------------
--------------------------------------------------------
| iSCSI-HA Status: Running 19221                       |
| Last Updated: Sun Feb 18 16:57:50 CST 2018           |
| HOST ROLE:              SLAVE                        |
| VIRTUAL IP:             10.10.10.3 is not local      |
| ISCSI TARGET:           Stopped [expected stopped]   |
| DRBD ROLE:              iscsi1=Secondary             |
| DRBD CONNECTION:        iscsi1 in WFConnection state |
--------------------------------------------------------
Control + C to exit


---------------
| DRBD Status |
---------------
-------------------------------------------------------------------------------
| version: 8.4.5 (api:1/proto:86-101)                                         |
| srcversion: 2A6B2FA4F0703B49CA9C727                                         |
|  1: cs:WFConnection ro:Secondary/Unknown ds:UpToDate/DUnknown C r-----      |
Last Edit: 8 months 3 days ago by Check Signal.
The administrator has disabled public write access.

Installed new NIC, now Slave in WFConnection State 8 months 2 days ago #1562

If the floating IP is pingable from both hosts, you can try running the following repair script. The script will prompt you to answer a few questions. Assuming that the current master has the most up to date data, select the master as being the survivor when prompted. Just in case you run it in the wrong direction, I would encourage you to export your vms first.

cd /etc/iscsi-ha/scripts
./drbd-sb-tool
The administrator has disabled public write access.
The following user(s) said Thank You: Jiri Ledvinka

Installed new NIC, now Slave in WFConnection State 7 months 2 weeks ago #1573

Brilliant! That did it. Now to still diagnose the real issue. Thank you so much for your help, Salvatore.
The administrator has disabled public write access.
Time to create page: 0.122 seconds