5.5.2 behavor

Hi,
i still have one prod box with 5.5.2 on w2k that i inherited. from time to time it goes slow to the point that it is not usable and the iwserver process runs on 50% for infinite amount of time...
it takes me to restart teamsite service to get back on shapve. but it takes 10 to 15 mins to restart the service since iwserver has to think for a while before it starts loosing it s 1 GB of memory to die.

i noticed few things in the logs, but nothing significant to me: i run iwstat and iwstat -c the number look ok to me, but there might something in there that i dont know about
this is what i got from runing iwstat:
[HTML]

\iw-home\bin>iwstat
Store Status
default Running
archive Running
workflow Running
ID Thread User Duration Store Operation
0x91baae 0xc50 cs2\muser 0.031 - GetServerStatus
0x91baad 0x1024 - 1.469 default CFILE_LOOKUP_svc com (64,4000003c) 3b6819/3b6816
0x91baa4 0x4f0 euser 1.500 default IterateModFSE 0x000010084600187f4000003c
0x91baa2 0x1104 euser 1.500 default IterateModFSE 0x000010084600187f4000003c
0x91ba4e 0xfa8 cs2\auzer 8.203 default IterateBFSE 0x0000100846001959400002e4
Minutes Thruput Avg op Load
1 49 0.0662 3.24
15 78 0.0502 3.91
60 313 0.0003 0.09
480 155 0.0001 0.01
1014 156 0.0012 0.18

\iw-home\bin>iwstat -c
Store Status
default Running
archive Running
workflow Running
ID Thread User Duration Store Operation
0x91bb87 0x1024 - 0.032 default CFILE_LOOKUP_svc general (64,4001fe04) 4256f6/3b6816
0x91bb86 0x1168 cs2\muser 0.032 - GetServerStatus
0x91bb84 0x1104 euser 0.063 default GetPath
0x91bb82 0xfa8 cs2\auzer 0.688 default IterateBFSE 0x0000100846001959400002e4
0x91bb81 0xc50 euser 1.954 default FindCorrespondingFSEByID
0x91bb50 0x4f0 euser 3.438 default IterateModFSE 0x000010084600187f4000003c
Cache Active Dirty To Purge Available
default 224823 0 0
archive 7 0 0
workflow 2 0 0
Total 224832 0 0 25168
Minutes Thruput Avg op Load
1 49 0.0662 3.24
15 78 0.0502 3.91
60 313 0.0003 0.09
480 155 0.0001 0.01
1014 156 0.0012 0.18

\iw-home\bin> [/HTML]

i also attached event /iw_trace/ error /ssl_engine _logs for today since those are the only logs that had modification date of today.

we are movin this box to 6.5 soon and i cant wait for that, but till then i d love to find what might be causing iwserver to hang on 50% for infinite amount of time.

i did run ts_diagnotstics tool on the same box couple months back and it didnt show in problems and the support thought the same... they only helpd us with this since we r upgradin, otherwise they wouldnt look at 5.5.2 issues.

thank you for taking time to look at this.

Find more posts tagged with

Comments

CRB

Andy (nipper) i saw this thread, and it might have something to do with my issue here.. i know the users of this box use view last modified alot...
http://devnet.interwoven.com/forums_vb/showthread.php?t=11227&forumid=11&highlight=IterateModFSE

looking at my thread and the info do you think it resembles what you dicusses in the thread of 2005?

also i noticed this on the trace_log:
Trying to delete non-existent vnode 0x8261e228

TS has printing that msg for 6 hours now, even after restarting TS service, it is still doing it.. how can get rid of this non-existent vnode? or to prevent it from happening?

nipper

I suspect this would be an iwfsck issue. Run it (without having it repair) first.

CRB

will it make a difference if i use iwfsck that came with 5.5.2 right now, or should i use the latest like the one with 6.7.1... i read somewhere where IWOV recommand using the lastest iwfsk but i am not sure if it is the case for 5.5.2.

[font=Verdana][size=2][color=#000000]also to avoid freezing the 5.5.2 if possible, can i just copy the iw-store to different box where i have 6.5 and config the 6.5 to use that store and run iwfsck on it?

[/color][/size][/font]

and in case of iwfsk took too long and i decided to cancel it, is it going to have any impact of the current store?

finally, the cmd would be iwfck -d ? no need for anything else for now?

nipper

that is a start, in 6.7 the detailed command is iwfsck -d -p -r

I do not know if the 6.7 iwfsck will work with 5.5.

As long as you do not try to fix any errors, you are OK. iwfsck is interruptible but very slow.

HTH

me