200 X-Frame-Options: SAMEORIGIN Content-Security-Policy: frame-ancestors 'self'; X-UA-Compatible: IE=Edge X-XSS-Protection: 1; mode=block X-Content-Type-Options: nosniff X-Telligent-Evolution: 12.x Pragma: no-cache Connection: close Accept-Ranges: bytes Cache-Control: no-store, no-cache, max-age=0 Date: Fri, 29 Nov 2024 22:50:31 GMT ETag: "0x8DD02F56CCD7D1F" Set-Cookie: .te.csrf=7pOi6RWiFzWIgBJa0t9xB9luEd523z3LGBa8VDg_dZ8; path=/; secure; SameSite=Lax Set-Cookie: .te.auth=55l6OeqrQp2eI1J2lfXpXBQAdPG2%2fy832RhCtXGPp4qf6s3ICXz1Dy2uu%2bmJORGs0tEjKtb1a3wPdlpBAMNF6XJ9qMdf9vWvsXGtZ8bHojXmcOskY4%2fjiZR3jArYlL8A2JbRjlnFywzqWW%2fykez%2ftMldAxFUTydoRGQjaaYhzrOQzuS8fxhH9OoSpS4tjV2KqUPoRUEr45LmPI64XloYlUsD4patLIjmwLGVdrpB2i0VJvluCWoQqluqC1iB0r%2foKX4WypwNsFa1FocyzsXozA%3d%3d; path=/; secure; HttpOnly; SameSite=Lax Set-Cookie: e14Guest=1; expires=Fri, 31-Dec-9999 23:59:59 GMT; path=/; secure; HttpOnly Set-Cookie: e14Country=NL; expires=Fri, 31-Dec-9999 23:59:59 GMT; path=/; secure; HttpOnly Set-Cookie: e14Language=en; expires=Fri, 31-Dec-9999 23:59:59 GMT; path=/; secure; HttpOnly Set-Cookie: e14TimeZone=Etc/UTC; expires=Fri, 31-Dec-9999 23:59:59 GMT; path=/; secure; HttpOnly Server-Timing: cdn-cache; desc=MISS Server-Timing: edge; dur=12 Server-Timing: origin; dur=29 Server-Timing: ak_p; desc="1732920631502_3090373303_141050754_4116_8448_9_9_-";dur=1 Strict-Transport-Security: max-age=86400 ; includeSubDomains ; preload #set ($UserId = $core_v2_user.Accessing.Id) #set ($Roles = $core_v2_utility.MakeList('Moderators', 'Almost Admins', 'Administrators')) #set ($IsAdminLike = $e14_utils.IsUserInRoleOrAdmin($UserId, $Roles)) #if($IsAdminLike == 'False') #end
Actions
Forum Thread Details
  • State Suggested Answer
  • Locked Locked
  • Replies 15 replies
  • Answers 1 answer
  • Subscribers 17 subscribers
  • Views 1424 views
  • Users 0 members are here
Related
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

Element14 summary pages not including recent blogs?

JWx

Hello!

It seems that summary pages are not catching up with recent blog articles - there are at least three new blogs in this challenge which I cannot see in project's summary page nor Element14 main page... Anyone else noticed this or is it some isolated problem?

Parents
  • 0

    Yes, it looks like the indexer is not running. Normally would iron these things out, but since he's on leave (as far as I know), I had tagged and in a Top Member's posting to indicate that it was broken as of 19th May at 1900 (UTC+11) as I too had posted a blog that didn't get updated in any of the indexes (including the one under my Profile). It sometimes recovers on its own, but this time, I think it's just stuck in its "fallen-over" state until someone gives it a prod.

    - Gough

  • 0 in reply to Gough Lui

    I'm surprised the indexer has been stuck for so long. It really hampers discoverability of postings.

    Perhaps might be able to let us know when it's coming back given the others I've tagged haven't chimed in yet ...

    - Gough

  • 0 in reply to Gough Lui

    You had a good observation, all 4 tabs appear to be frozen since May 18. 

  • 0 in reply to robogary

    Looks like we're back up and running again ...

    - Gough

  • 0 in reply to Gough Lui

    Although this was some time ago, I received a recent update on this issue - as I had raised it with the development team as a ticket to ask:

    "Why does this keep happening?" and "Why doesn't it automatically kickstart itself?"

    They both tie together, for a while the servers were having repeated issues, nearly daily, so the notifications that the servers were having issues, were turned off.

    They've long since been turned back on, but they will not be setup in such a way that they will auto-restart the server or services, this is so that a member of the team can come along, investigate the problem and escalate it to Verint for repair, ultimately.

    Since May, the server admin/dev team now get notifications when these services/servers stop so that they can be restarted, but it is still done manually. They watch Feedback and Support for reports on it from members to know if the 'server watchers' have also missed something.

    There's still an open support case with Verint about issues with some missing or duplicate services that are causing problems.

Reply
  • 0 in reply to Gough Lui

    Although this was some time ago, I received a recent update on this issue - as I had raised it with the development team as a ticket to ask:

    "Why does this keep happening?" and "Why doesn't it automatically kickstart itself?"

    They both tie together, for a while the servers were having repeated issues, nearly daily, so the notifications that the servers were having issues, were turned off.

    They've long since been turned back on, but they will not be setup in such a way that they will auto-restart the server or services, this is so that a member of the team can come along, investigate the problem and escalate it to Verint for repair, ultimately.

    Since May, the server admin/dev team now get notifications when these services/servers stop so that they can be restarted, but it is still done manually. They watch Feedback and Support for reports on it from members to know if the 'server watchers' have also missed something.

    There's still an open support case with Verint about issues with some missing or duplicate services that are causing problems.

Children
No Data