Discussions
Categories
Choose a Product
THRUST SERVICES
CORE APPS
CE PRODUCTS
...
Quick Links
POPULAR
HELPFUL TIPS
Groups
My Links
FOR SIGNED IN MEMBERS:
Back to website
Home
TeamSite
TeamSite, LiveSite and OpenDeploy
Performance Issues with Linux TeamSite732
Migrateduser
Hello,
we're having perplexing performance issues with Linux TeamSite732, for which we also use Samba (currently installed on the TS server) and mounts of TeamSite to remote servers - I specifically mention these because they may be key. We're wondering if anyone else has had these problems, because we are not seeing a definitive cause yet.
The 'performance issues' manifest themselves in 3 ways (please bear with me on this):
1. TeamSite UI slows to a halt and people can't do anything or even login
Doing an iwstat -c at these times shows a large buildup of processes and the iwstat 'load' often gets over 10%, and I have seen 'top' load at 19. It eventually comes down and people can work again. I don't believe the number of user processes on the UI themselves are the issue though.
2. TeamSite not unmounting properly
When stopping TeamSite the /iwmnt/default store wasn't getting unmounted properly (the other 3 usually do).
In iwserver.log we see:
umount: /iwmnt/default: device is busy.
iwmount: Failed to umount ...
What we then see is that default isn't shown with a df -k, but its directory is there and if we do an ls -l we see:
ls: cannot access /iwmnt/default: Input/output error
d????????? ? ? ? ? ? default
We think that one was due to Samba, so we have a workaround (until we move Samba to another server) whereby we have created a 'mirror' iwmnt_smb/default mount for Samba to access. This seems to be working better (I need to try and restart TS a couple of times with this new regime to fully confirm).
3. Each night at 9:15 and/or 10:15 the servers on which TeamSite is remotely mounted report the mounts down (cannot statvfs for Sol servers, I/O error for Linux ones). If I look on TeamSite itself at those times it has slowed to a crawl - running functions like iwstat or df -k take a long time to return. There are no users in TS then, so they can't be blamed.
I have the Unix and Network teams investigating but they don't see anything, and moving backups and other network processes to different times didn't change anything.
Our setup is unique, but I am wondering if there is anyone else out there who may have any clues for us, as we are scratching our collective heads here. I have given 3 types of issue but I am sure there must be a common cause, and then a fix hopefully.
Cheers
HF
Find more posts tagged with
Comments
There are no comments yet