This message was deleted.
# citrix-vad
s
This message was deleted.
r
Does it happen when lhc is off?
Interesting, what version?
m
i just turned it off now, looks like it stopped
it seems to be the same one over and over becoming elected
7.15 u5
r
I assume it's going back and forth between the 2 DDC?
This is dumb resolution, but are you or can you cycle all the services on one DDC?
m
yeah, it didn’t stop it
I rebooted all of them
only thing that stopped it was turning off lhc
it’s done it 50 times today
sometimes 12 times an hour
and then it’ll go for a couple hours without doing it
r
That's definitely going to calls brokering issues. Man I'm kinda clueless now
m
it has been, our storefront tickets are huge this morning
I need to do an upgrade at some point anyway, was hoping this thing cold hold it together until I was ready to fail over to a new site
r
Nothing in the event veiwer about losing connection to the main SQL DBA?
Do you see Event ID:1197?
m
no
there’s tons of messages saying it successfully connected to the database
r
Ok.
m
none about a disconnect
r
What about event ID 3502-3503?
m
no recent ones
one from over a month ago
3503
r
Well damn. That's strange
m
ja
r
Oh u see 3503 now?
m
no idea what the LHC is doing
no, only 1 whole 3503 in the logs from 7/7
r
Oh ok. Rebuild LHC local DB?
m
I’m just going to leave it off, we’re almost all pooled random anyway
doesn’t really buy us anything on 7.15
r
Ahh ok man.
m
we used to do more apps which is probably why it was on in the first place
r
Yea
s
Noticed the same in my Citrix Cloud env, Broker Election process happens during normal mode of operation unlike LHC in IMA and this happens every 2 minutes. Checked with Citrix product team and this is normal behavior. Once an outage kicks in, all the VDAs re-register with the elected member and HA Service on elected member responds to XML communication. Election is done by alphabetical order.
m
it shouldn’t be normal to kill the xml service every 30 seconds, storefront relies on that for brokering
s
What is the event ID on StoreFront server? 4003 or 0?
m
neither, seeing a bit of this though “An authentication request was made before establishing a web session. This typically occurs when sticky load-balancing between client and StoreFront is misconfigured.”