msg files being locked when opening smat

[Rob Parnell]

I am on 5.3 on Aix 5.3

When I close the thread and open the smat for that thread It reads fine but when I close the smat and open the thread it gives me a bad file numberand will not write to the file.  I have tried to open an old file while I have smat open to see if it will release the lock but it doesn’t seem to work

Anybody else have this issue.  When I was on 3.7.1 all I had to do was close the thread and open smat then close smat and open the thread and never had an issue

Topic

[Anonymous]

Apply latest patch to 5.3P (rev3 now). Apply this line to all of your client.ini files (server and all clients) in the [general] section:

netmon_auto_load_logs=false

This looks like the well known bug in Cloverleaf that causes locks on SMAT files to persist through hciss and other parts of Cloverleaf.

[Beth Palmateer]

Will this also work on 5.2.1?  We had the exact same thing happen except we went from 3.7.1 to 5.2.1, on AIX 5.1.  Our workaround has just been to stop the thread and copy the current .idx and .msg files to a temp filename, then start the thread.  We can then access the records through smat without the lock issue, and it has been simple enough to do that I never persued a fix.

[Author]

Replies