
UNSOLVED
Avamar shutdown taking a "long" time
Working on an issue and part of the resolution is to reboot the Avamar node.
Did all the pre-requisite checking of processes etc., and issued the "dpnctl stop" command - 20 minutes later, the GSAN is still in the process of shutting down.
I see the following messages in the gsan.log, and they seem to be repeating:
2018/02/01-15:50:13.53083 {0.0} [manage:2158] samconn::sendmessage retry stripe still accessible excess waiting retry=0 force=0 stripeid=0.0-1 TERMINATEDISPATCHER=192 TO stripeid=0.0-1 targetstripeid=0.0-1 origin=[0.0,158.107.40.35:26000] seq=300219186634 flags=X:N:2229 kind=0 pri=28
2018/02/01-15:50:13.55125 {0.0} [srvm-219193096#srv:1946] samconn::sendmessage retry stripe still accessible excess waiting retry=0 force=0 stripeid=0.0-1 EXIT_DPN=66 TO stripeid=0.0-1 targetstripeid=0.0-1 origin=[0.0,158.107.40.35:26000] seq=300219186631 flags=X:N:2017 kind=0 pri=28
2018/02/01-15:50:19.50959 {0.0} [connbeat:188] servmain::checkconntimeout calling shutdown lastreqtime=3087892784907307 maxconninactive=3600 0x7f3690458230 clientaddr=158.107.40.35:51472 ismaint=1 type=avmaint access=uname=root uid=0 priv=enabled,create,read,backup,access,move,delete,maint,manage,fullmanage,noticketrequired,superuser,ignoreacls,readdir,mclogin,opt1,opt2 avail=modes=00pu
2018/02/01-15:50:19.50963 {0.0} [connbeat:188] servmain::shutdown already killed 158.107.40.35:51472
Not sure exactly what they mean, other than it's something that is delaying the shutdown.
Wondering if anyone could shed any light on this?
All feedback/comments appreciated - thanks.
Cal C.
Responses (0)
Solutions (0)
