Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 3 replies
  • Subscribers 27 subscribers
  • Views 3574 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

check_timeout_cta_collector: found timeout collector on STAS

giomoda

Hey guys.

So, I'm in a bit of a pickle here. I've just deployed a XG on a customer for a POC and enabled STAS. Everything worked fine for a few days, but now every morning I get absolutely no authentication from STAS to the XG box. Searching the logs I found that, when this happens, access_server.log shows "check_timeout_cta_collector: found timeout collector" repeatedly.

This customer have a, for lack of better word, curious behavior: they shutdown all of their servers off-hours, including DCs running STAS, so I'm pretty sure that this, ahem, "curious behavior" has something to do with it. The only way to get things working again is restarting authentication services at the XG AND restarting STAS service at the collector. 

So, does anyone know if STAS has a builtin timeout or something where it discards the server completely after the server is offline for some time? That's what it looks like to me.

Regards,

Giovani



This thread was automatically locked due to age.
Parents
  • 0

    Hi,

    Did you already talked to your Sophos pre sales rep about this? 

    As far as i know, there can be an issue with STAS, if you restart the Windows Server. So basically does the issue happens all the time after reboot or "sometimes"? 

  • 0 in reply to LuCar Toni

    Hey Man,

    No, I thought of asking here first.

    Well, it's been happening every single day since Friday, so at leas it's consistent. And note it's not a reboot per se. It's a full shutdown followed by several hours of being in that state. They shutdown the servers at about 8 PM and only start them again at around 6 AM next day. I've tested this in my lab and a simple shutdown does not seem to trigger the issue. I'll leve my lab DCs offline tonight and see if I can reproduce the issue. If so I think I'll need to raise a support ticket.

    Thanks for your input.

    Regards,

    Giovani

Reply
  • 0 in reply to LuCar Toni

    Hey Man,

    No, I thought of asking here first.

    Well, it's been happening every single day since Friday, so at leas it's consistent. And note it's not a reboot per se. It's a full shutdown followed by several hours of being in that state. They shutdown the servers at about 8 PM and only start them again at around 6 AM next day. I've tested this in my lab and a simple shutdown does not seem to trigger the issue. I'll leve my lab DCs offline tonight and see if I can reproduce the issue. If so I think I'll need to raise a support ticket.

    Thanks for your input.

    Regards,

    Giovani

Children
  • +1 in reply to giomoda

    Well, as it turns out, STAS seems to have an issue with the server being offline for long periods of time. Since this customer have two DCs, I changed the configuration a bit and the problem has not occurred again. Initially I had setup the PDC as the collector and the other DC with agent only. Last Thursday I changed both DCs to collectors, reporting to each other, and added the second DC to XG's collector group. Now when the servers go online XG is able to switch to the second collector and get things going again.

    MESSAGE Jul 30 07:09:01 [4143548928]: check_timeout_cta_collector: found timeout collector
    MESSAGE Jul 30 07:09:01 [4143548928]: start_cta_requester: TLVDATA:'X.X.X.X:6677', LEN:'17'
    MESSAGE Jul 30 07:09:01 [4143548928]: (add_worker): CTA REQUESTER
    MESSAGE Jul 30 07:09:01 [4143548928]: fill_cta_garner_data: X.X.X.X

    Hope this helps someone if they ever encounter such issue.

    Regards,

    Giovani