https://worldofeuc.com logo
Join Slack
Powered by
This message was deleted.
# citrix-netscaler
s
This message was deleted.
e
Looks fine here. They upgraded yesterday. Maybe it is related to that. Reboot the agents 🙂 https://docs.netscaler.com/en-us/citrix-application-delivery-management-service/release-notes/whats-new
h
have the same with one customer, trying to look at it, thanks for the heads up
k
Thanks @Eirik Vesterhus / Intility AS... I'm rebooting one to see if helps.
I think it threw the error right after the boot...
All of our agents are 14.1-8.35... why don't they mention the version in the release notes <o>
h
yeah see the same
but only one customer at this time
reboot didn't help
k
We'll open a ticket of this
this started yesterday and based on the release notes a new agent was published yesterday
likely these are connected
@Henry Heres, agents runnin 14.1-8.35 version or only the problematic one?
h
yes
checking another customer if they have the same agent build, believe they do but there I don't see this
other customers same build and no issue
k
we have a local user account configured on the ADCs that the agent uses for comms
superuser
my biggest worry, is that this is connected to the July CVE and the environments have been exposed and now someone has done something. I already verified in one environment that I'm able to log in to the NetScalers with the account, so it hasn't been deleted nor password reset
h
same here
k
we have 13 agents, not sure if all of them have the issue, but majority has
h
the environment was checked/validated with the CVE at the time and ADM got configured afterwards, don't think this has anything to do with the CVE
👍 1
k
ofc the support wants to call
🙂 1
h
also going to log a case, just removed the instance and re-added, everything works fine but after some time same error
k
we're seeing this in 5/13 of our agents... there was an updated version of the agent pushed today (14.1-8.37), but that didn't solve the issue
✅ 2
j
Any updates from citrix engineering?
k
They requested to reboot the agent... I rebooted all affected, but it didn't help
I was already planning to re-enter the password in the NetScaler profile in ADM, but still waiting for their input
first got a request to do ha failover, but now they requested agent and adc support bundles and are escalating the case as many customers are seeing the same
e
Found out anything, @Kari Ruissalo (WyW)? Did you also see license server as disconnected but instance not in grace?
k
nope, just sent them a reminder of it, but they're still looking in to it
I'm not licensing any of the VPXs currently via ADM service
I'm still seeing those login issues though
Was asked to remove one ADC from ADM and then bring it back... didn't help.
👍 1
🫣 1
h
Did the same on day one and just before my vacation, instantly issue reappeared. No feedback from support @Kari Ruissalo (WyW) ? This is my last week on holiday next week I’m also logging a case, this is beyond laughable and bad that this can happen after adm service upgrade from Citrix side.
k
Ticket is in escalation, but no updates
h
Can you provide the case number? I can try and escalate it via the CTP side
@Kari Ruissalo (WyW) can you share the case number? I have someone who can follow-up on this.
any new updates @Kari Ruissalo (WyW)? I'm still waiting response on the other side as well.
k
nothing
h
Sigh… I’m going to log a case as well this is crazy
k
got a response today "we've upgraded the service, do you still have the issue" -> we still have the issue
h
also opened up a case and referring to yours
👍 1
got reply that it got escalated and if's the same problem
latest update it is a known issue and no ETA around a solution yet.
k
They asked me a screenshot of the event in ADM and info about the profile etc..
🥲 1
h
Latest update on my support case is resolution expected to be delivered in Q1-2024
k
I just gathered them some logs last Wednesday, but haven't heard anything after that
@Henry Heres ETA for fix on 1st week of December by support
h
oh!
I'll reply to my case 🙂 that's sooner than Q1 2024
k
it's taking surprisingly long.. considering the issue's been there for quite some time
h
sigh... yes that's painfully correct
got the same feedback as you, so fingers crossed.
👍 1
k
o tempora, o mores; agent version 14.1-16.33 rolled yesterday finally fixed the issue!
✅ 1
h
going to check!
same here! last message was yesterday 🙂
👍 1
k
it took three months to fix that
would really like to understand what was the cause, but I bet we never get to know!
h
Same here, going to chase it for sure
Did you get any feedback? I got some 🙂 can DM if you want.
k
Did not
Sure, you can DM 👍
7 Views
Open in Slack
PreviousNext
Powered by