Sporadic account auth failure / timeout

Discuss your pilot or production implementation with other Zimbra admins or our engineers.
User avatar
JDunphy
Outstanding Member
Outstanding Member
Posts: 610
Joined: Fri Sep 12, 2014 11:18 pm
Location: Victoria, BC
ZCS/ZD Version: 8.8.15_P22 RHEL8 Network Edition
Contact:

Re: Sporadic account auth failure / timeout

Postby JDunphy » Fri May 28, 2021 2:03 pm

You might verify if memcached is crashed or other by issuing a command to it... Example:

Code: Select all

% telnet 127.0.0.1 11211
Trying 127.0.0.1...
Connected to 127.0.0.1.
Escape character is '^]'.
stats items
STAT items:3:number 3
STAT items:3:number_hot 0
STAT items:3:number_warm 1
STAT items:3:number_cold 2
STAT items:3:age_hot 0
STAT items:3:age_warm 3
STAT items:3:age 1459
STAT items:3:mem_requested 398
STAT items:3:evicted 0
STAT items:3:evicted_nonzero 0
STAT items:3:evicted_time 0
STAT items:3:outofmemory 0
STAT items:3:tailrepairs 0
STAT items:3:reclaimed 16
STAT items:3:expired_unfetched 0
STAT items:3:evicted_unfetched 0
STAT items:3:evicted_active 0
STAT items:3:crawler_reclaimed 0
STAT items:3:crawler_items_checked 140
STAT items:3:lrutail_reflocked 18872
STAT items:3:moves_to_cold 9603
STAT items:3:moves_to_warm 9574
STAT items:3:moves_within_lru 261
STAT items:3:direct_reclaims 0
STAT items:3:hits_to_hot 0
STAT items:3:hits_to_warm 473
STAT items:3:hits_to_cold 9758
STAT items:3:hits_to_temp 0
END
quit
Connection closed by foreign host.

Ref: https://itecsoftware.com/testing-memcac ... t-commands

This link explains the purpose of how memcached is used within zimbra. Find the section on Architecture and Flow for memcached.
Ref: https://wiki.zimbra.com/wiki/Zimbra_Proxy_Guide

Jim


tjessy
Posts: 7
Joined: Tue May 25, 2021 2:14 pm

Re: Sporadic account auth failure / timeout

Postby tjessy » Tue Jun 01, 2021 9:16 pm

JDunphy wrote:You might verify if memcached is crashed or other by issuing a command to it... Example:
Ref: https://itecsoftware.com/testing-memcac ... t-commands

This link explains the purpose of how memcached is used within zimbra. Find the section on Architecture and Flow for memcached.
Ref: https://wiki.zimbra.com/wiki/Zimbra_Proxy_Guide

Jim


Thanks for the tip, memcached is looking fine - I can list all the cached connections - and the failing ones cache record seems kind of
identical to the others which are working...

Right now, only the every hour restart seems to work...

Code: Select all

root@mail:~# telnet 127.0.0.1 11211
Trying 127.0.0.1...
Connected to 127.0.0.1.
Escape character is '^]'.
stats cachedump 2 100
ITEM route:proto=imapssl;user=hr@domain.xxx [18 b; 1622570441 s]
END
stats cachedump 3 100
ITEM route:proto=httpssl;id=f1690dc0-70d8-417c-908e-5e34cd6514fb [18 b; 1622582223 s]
ITEM route:proto=pop3ssl;user=muldor@domain.xxx [18 b; 1622584035 s]
ITEM route:proto=imapssl;user=totdit@domain.xxx [18 b; 1622585449 s]
ITEM route:proto=imapssl;user=koszedor@domain.xxx [18 b; 1622585433 s]
ITEM route:proto=imapssl;user=sao@domain.xxx [18 b; 1622582640 s]
ITEM route:proto=imapssl;user=hegyietta@domain.xxx [18 b; 1622582640 s]
ITEM route:proto=pop3ssl;user=kuczko@domain.xxx [18 b; 1622582032 s]
ITEM route:proto=imapssl;user=polgrnelia@domain.xxx [18 b; 1622585289 s]
ITEM route:proto=imapssl;user=kabarenc@domain.xxx [18 b; 1622581652 s]
ITEM route:proto=imapssl;user=marsztina@domain.xxx [18 b; 1622582376 s]
ITEM route:proto=imapssl;user=zolusz@domain.xxx [18 b; 1622585033 s]
ITEM route:proto=imapssl;user=eroronika@domain.xxx [18 b; 1622585033 s]
ITEM route:proto=imapssl;user=ugyveto@domain.xxx [18 b; 1622584974 s]
ITEM route:proto=imapssl;user=hidveofia@domain.xxx [18 b; 1622581350 s]
ITEM route:proto=imapssl;user=monusente@domain.xxx [18 b; 1622584063 s]
ITEM route:proto=imapssl;user=gusztgela@domain.xxx [18 b; 1622583858 s]
ITEM route:proto=imapssl;user=banlargely@domain.xxx [18 b; 1622583784 s]
ITEM route:proto=imapssl;user=szilales.aniko@domain.xxx [18 b; 1622582603 s]
ITEM route:proto=httpssl;id=c2c89d94-d63d-40ea-b219-e2f9bbbec603 [18 b; 1622582132 s]
ITEM route:proto=httpssl;id=6b1d296c-c045-46e8-9227-30f4c05b291b [18 b; 1622583912 s]
ITEM route:proto=imapssl;user=szabzsa@domain.xxx [18 b; 1622583759 s]
ITEM route:proto=httpssl;user=baraente@domain.xxx [18 b; 1622583021 s]
ITEM route:proto=httpssl;user=mihalorgy@domain.xxx [18 b; 1622582976 s]
ITEM route:proto=httpssl;id=ffccf339-3e99-490e-b9db-361380d67611 [18 b; 1622582974 s]
tjessy
Posts: 7
Joined: Tue May 25, 2021 2:14 pm

Re: Sporadic account auth failure / timeout

Postby tjessy » Thu Jun 10, 2021 11:07 am

I decided to switch off memcached as this seems to be the only working workaround on a long run.
I'm not too familiar with it, I see items 2 & 3, both have some accounts inside when doing a cachedump - but nothing outstanding for those accounts
which do not work. The only common thing is that all start working immediately after memcached restarts / shuts off... odd enough. :/

Return to “Administrators”

Who is online

Users browsing this forum: Baidu [Spider] and 23 guests