I've spent a LOT of time on this with BMC support and I wanted to know if anyone else had similar problems and how they fixed it.
Essentially we can not get FTS to remain stable. It will always eventually crash and need to be restarted, which essentially means restarting ARS since its' a plugin. We have Suse linux servers in the server group that are VM's. The mount points where the application is installed is pretty fast NAS (SAN? one of the two) and the index files live here as well. BMC has told us - by way of Lucene, which is the underlying product - that the actual mechanism that writes to SAN/NAS drives is not good for the types of file operations which FTS does in order to do it's work. Essentially we always end up with some form of file lock or read error. In short, you have to have an actual physical drive hooked up the box to make this work. That's NOT happening in our environment. Essentially there's a problem - BMC is saying they support VM's, but FTS can use virtual disks - and it's not really BMC's fault so much as the fault of the underlying engine. Anyone else run into this? Heck, we are getting FTS errors at times when it's been turned OFF for weeks. William Rentfrow [email protected] Office: 715-204-3061 Cell: 715-398-5056 _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
