Arnold Janssen
2007-08-09 14:36:24 UTC
Hi all,
The problem I'm going to describe might sound a bit vague. That's because it is just that! ;-) I'm also not sure if the agents-forum is the right one. If you feel it isn't, please say so.
We've got a two-node Netware 6.5 cluster and one of the cluster resources is our primary Groupwise 6.5 domain (containing one Postoffice). We also got a second domain for the GWIA and Webaccess on a different (BorderManager, non-clustered) server. The problem is with the cluster resource. When Groupwise is running on the first server (FS01) the utilization sometimes goes up to 85-95%. It can stay there the whole day (like today) but Groupwise itself doesn't seem to be affected by it much. The client responds normal and the POA logger screen doesn't show anything shocking. When switched to verbose logging, there do seem to be a lot of physical connects and disconnects, but from the information I could gather from the Novell site, this is normal.
This DOES seem to be a Groupwise issue though, because when I migrate the GW resource to the other node (FS02) the problem goes to that server. When I check the busiest threads, GWTCP-DISPATCHER is on top most of the time, but it doesn't seem to be that busy. We have got a few services that use the GWIA (on the BM-server) as a SMTP-server. These services sometimes generate quite a bit of mail, but that wouldn't affect the Postoffice, would it? And if it would...we would be able to see it being busy in the logging, wouldn't we?
I'm guessing this could be one of the following:
- A client issue on a PC where the GW-client somehow hogs TCP-connections to the server.
- A client issue where a GW-client gets stuck in some kind of weird rule (is there an easy way to troubleshoot that?).
- An issue with the Quickfinder index on the server (although I don't think that's it).
- Anything else... ;-)
You're thoughts on this are more than welcome!
Thanks,
Arnold...
The problem I'm going to describe might sound a bit vague. That's because it is just that! ;-) I'm also not sure if the agents-forum is the right one. If you feel it isn't, please say so.
We've got a two-node Netware 6.5 cluster and one of the cluster resources is our primary Groupwise 6.5 domain (containing one Postoffice). We also got a second domain for the GWIA and Webaccess on a different (BorderManager, non-clustered) server. The problem is with the cluster resource. When Groupwise is running on the first server (FS01) the utilization sometimes goes up to 85-95%. It can stay there the whole day (like today) but Groupwise itself doesn't seem to be affected by it much. The client responds normal and the POA logger screen doesn't show anything shocking. When switched to verbose logging, there do seem to be a lot of physical connects and disconnects, but from the information I could gather from the Novell site, this is normal.
This DOES seem to be a Groupwise issue though, because when I migrate the GW resource to the other node (FS02) the problem goes to that server. When I check the busiest threads, GWTCP-DISPATCHER is on top most of the time, but it doesn't seem to be that busy. We have got a few services that use the GWIA (on the BM-server) as a SMTP-server. These services sometimes generate quite a bit of mail, but that wouldn't affect the Postoffice, would it? And if it would...we would be able to see it being busy in the logging, wouldn't we?
I'm guessing this could be one of the following:
- A client issue on a PC where the GW-client somehow hogs TCP-connections to the server.
- A client issue where a GW-client gets stuck in some kind of weird rule (is there an easy way to troubleshoot that?).
- An issue with the Quickfinder index on the server (although I don't think that's it).
- Anything else... ;-)
You're thoughts on this are more than welcome!
Thanks,
Arnold...