<div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sat, Dec 10, 2022 at 6:39 PM Dave Withheld <<a href="mailto:davewithheld@hotmail.com">davewithheld@hotmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div class="msg-1607565249975156440">
<div dir="ltr">
<div>
<div dir="ltr">On Thu, Dec 8, 2022 at 8:03 AM Dave Withheld <<a href="mailto:davewithheld@hotmail.com" target="_blank">davewithheld@hotmail.com</a>> wrote:
<div>
<blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div>
<div dir="ltr">
<div><span style="font-family:Calibri,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0);background-color:rgb(255,255,255)">In our production factory, we run a 2-node cluster on CentOS 8 with pacemaker, a virtual IP, and drbd for shared storage
with samba (among other services) running as a resource on the active node. Everything works great except when we fail over. All resources are moved to the other node and start just fine, but Windows hosts that have connections to the samba shares all have
to be rebooted before they can reconnect. Clients that were not connected can connect. We have samba configured for only SMB1 protocol and all Windows clients are configured to allow it.<br>
</span></div>
<div><span style="font-family:Calibri,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0);background-color:rgb(255,255,255)"><br>
</span></div>
</div>
</div>
</blockquote>
<div>>>Did you test if it is samba/smb-client related or windows IP-stack related - like ping the samba-host from the windows machines?</div>
<div>>>Is the virtual IP using the physical MAC address of the interface - like windows missing the gratuitous ARP?</div>
<div style="font-family:Calibri,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0);background-color:rgb(255,255,255)">
<br>
</div>
<div style="font-family:Calibri,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0);background-color:rgb(255,255,255)">
Not just ping, but several other services (custom daemons, http, Mariadb, etc) all connect seamlessly. It's only the samba connections that don't (obviously ping works, too).</div>
<div style="font-family:Calibri,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0);background-color:rgb(255,255,255)">
<br>
</div>
<div style="font-family:Calibri,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0);background-color:rgb(255,255,255)">
As for the MAC address, it is the same: ip a shows two IPs for the interface but only one link/ether.</div>
<div style="font-family:Calibri,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0);background-color:rgb(255,255,255)">
<br>
</div>
<div style="font-family:Calibri,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0);background-color:rgb(255,255,255)">
This server (2-node cluster) is replacing an old system I built in 2008, which used heartbeat (no pacemaker or corosync) and had a much older version of samba. It had no problem failing over: mapped drives on the Windows clients worked just as well after
a failover as they did before and UNCs worked seamlessly, as well. In fact, the few times it failed over, no one even knew it until we saw a message in our emails sent by the servers when the resources moved.</div>
<div style="font-family:Calibri,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0);background-color:rgb(255,255,255)">
<br>
</div>
<div style="font-family:Calibri,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0);background-color:rgb(255,255,255)">
On the old system, ifconfig showed an eth0 interface, as well as an eth0:0 interface on the active node which the virtual IP. The docs called the virtual IP an "alias". On the new server, ifconfig does not show the virtual IP at all and I have to use "ip
a" to see the two addresses on one interface. I tried using the command "ifconfig eno1:0 XXX.XXX.XXX.XXX up" to manually add an IP in a similar manner to the old server and the address I added did show up in ifconfig. The point is, the virtual address is
being added differently and I suspect the Windows clients treat it differently.</div>
<div style="font-family:Calibri,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0);background-color:rgb(255,255,255)">
<br>
</div>
<div style="font-family:Calibri,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0);background-color:rgb(255,255,255)">
I will be looking closely at the resource agents and see how they compare. If any of this rings a bell, I would love to hear more from anyong with experience. Thanks!<br></div></div></div></div></div></div></blockquote><div><br></div><div>Sry didn't say I had a clue for you. Just thought this info was missing ;-)</div><div>My personal experience with samba is both minimal and dated.</div><div>What you could do - if nobody has a clue - would be capturing the traffic -</div><div>both cases if the old setup is still available.</div><div><br></div><div>Klaus </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div class="msg-1607565249975156440"><div dir="ltr"><div><div dir="ltr"><div><div style="font-family:Calibri,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0);background-color:rgb(255,255,255)">
</div>
<div><br>
</div>
<div>>>Klaus</div>
<blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div>
<div dir="ltr">
<div><span style="font-family:Calibri,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0);background-color:rgb(255,255,255)"></span></div>
<div><span style="font-family:Calibri,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0);background-color:rgb(255,255,255)">Maybe this is a question for the samba folks, but thought I'd try here first since it's only a problem when the other
node takes over the samba resource. Anyone seen this problem and solved it?<br>
</span></div>
</div>
_______________________________________________<br>
Manage your subscription:<br>
<a href="https://lists.clusterlabs.org/mailman/listinfo/users" target="_blank">https://lists.clusterlabs.org/mailman/listinfo/users</a><br>
<br>
ClusterLabs home: <a href="https://www.clusterlabs.org/" target="_blank">
https://www.clusterlabs.org/</a><br>
</div>
</blockquote>
</div>
</div>
</div>
</div>
_______________________________________________<br>
Manage your subscription:<br>
<a href="https://lists.clusterlabs.org/mailman/listinfo/users" rel="noreferrer" target="_blank">https://lists.clusterlabs.org/mailman/listinfo/users</a><br>
<br>
ClusterLabs home: <a href="https://www.clusterlabs.org/" rel="noreferrer" target="_blank">https://www.clusterlabs.org/</a><br>
</div></blockquote></div></div>