Common crawler / search debug settings

Common crawler / search debug settings

Useful Search Logging Switches

All switches can be found under com.stoneware.


WSTreeModeler
com.stoneware.service.Akka.search.WSTreeModeler
com.stoneware.service.Akka.search.WSTreeWorker
Set to "info" will show it actually trying to index the nodes.

----------------------

WSCrawlUserManager
This will show whenever search asks webStorage for a list of users that use webStorage.  They are then placed into the PWSUser table.  That is basically a schedule of users waiting to be crawled.  This is controlled by the GETDATA_PING_USER_INTERVAL in the properties file.  In this case, I have mine set to do this every 45 seconds.

DEBUG (01/29) 10:55:25 [com.stoneware.service.Akka.search.WSCrawlUserManager]: WSCrawlUserManager: GetData
DEBUG (01/29) 10:55:26 [com.stoneware.service.Akka.search.WSCrawlUserManager]: Number of users: 3
DEBUG (01/29) 10:56:10 [com.stoneware.service.Akka.search.WSCrawlUserManager]: WSCrawlUserManager: GetData
DEBUG (01/29) 10:56:11 [com.stoneware.service.Akka.search.WSCrawlUserManager]: Number of users: 3

----------------------

WSCrawlMountPointManager

When the crawler looks int the PWSUser table to get users to crawl, this debug will be triggered.  This shows that it asked for users, and it got the result back.  This happens based on the GETDATA_PING_MOUNT_POINT_INTERVAL setting in the properties file.  In this case, mine is set to do this every 30 seconds.

DEBUG (01/29) 11:05:32 [com.stoneware.service.Akka.search.WSCrawlMountPointManager]: GetData
DEBUG (01/29) 11:05:33 [com.stoneware.service.Akka.search.WSCrawlMountPointManager]: WSUserSet
DEBUG (01/29) 11:06:02 [com.stoneware.service.Akka.search.WSCrawlMountPointManager]: GetData
DEBUG (01/29) 11:06:02 [com.stoneware.service.Akka.search.WSCrawlMountPointManager]: WSUserSet

----------------------

IndexWorker
Gives a lot of data about what is happening in the system.... should users be crawled, what it is reading and writing from the database, etc.

In the example below, I have my search configured to only run once every 30 days for a given user.  They have already been crawled and it hasn't been 30 days yet.

Note how the debug shows what user it is checking.  It does an "isOKToCrawlUser" check.  It shows when the last crawl was, what time it is now, what the difference is in millis and minutes, and whether or not that meets the minimum duration (in my case it did not).

On a system that seems idle - this is a great switch to see what is going on.

DEBUG (01/29) 12:35:54 [com.stoneware.service.Akka.search.IndexWorker]: DataNucleusPersist ==> isOKToCrawlUser check: cn=relayuser,o=stoneware
INFO  (01/29) 12:35:54 [com.stoneware.service.Akka.search.IndexWorker]: DataNucleusPersist ==> ---- isOKToCrawl check ----
INFO  (01/29) 12:35:54 [com.stoneware.service.Akka.search.IndexWorker]: DataNucleusPersist ==> User: cn=relayuser,o=stoneware
INFO  (01/29) 12:35:54 [com.stoneware.service.Akka.search.IndexWorker]: DataNucleusPersist ==> Last Crawl: 1422551162997
INFO  (01/29) 12:35:54 [com.stoneware.service.Akka.search.IndexWorker]: DataNucleusPersist ==> Now: 1422556554926
INFO  (01/29) 12:35:54 [com.stoneware.service.Akka.search.IndexWorker]: DataNucleusPersist ==> Millis Diff: 5391929
INFO  (01/29) 12:35:54 [com.stoneware.service.Akka.search.IndexWorker]: DataNucleusPersist ==> Seconds Diff: 5391
INFO  (01/29) 12:35:54 [com.stoneware.service.Akka.search.IndexWorker]: DataNucleusPersist ==> DiffMins: 89.86548333333333
INFO  (01/29) 12:35:54 [com.stoneware.service.Akka.search.IndexWorker]: DataNucleusPersist ==> Elapsed Duration: 5391929 milliseconds
INFO  (01/29) 12:35:54 [com.stoneware.service.Akka.search.IndexWorker]: DataNucleusPersist ==> Min. Duration: 30 days
INFO  (01/29) 12:35:54 [com.stoneware.service.Akka.search.IndexWorker]: DataNucleusPersist ==> Not ok to crawl this user
DEBUG (01/29) 12:35:54 [com.stoneware.service.Akka.search.IndexWorker]: DataNucleusPersist ==> isOKToCrawlUser check: cn=user1,o=stoneware
INFO  (01/29) 12:35:54 [com.stoneware.service.Akka.search.IndexWorker]: DataNucleusPersist ==> ---- isOKToCrawl check ----
INFO  (01/29) 12:35:54 [com.stoneware.service.Akka.search.IndexWorker]: DataNucleusPersist ==> User: cn=user1,o=stoneware
INFO  (01/29) 12:35:54 [com.stoneware.service.Akka.search.IndexWorker]: DataNucleusPersist ==> Last Crawl: 1422551162997
INFO  (01/29) 12:35:54 [com.stoneware.service.Akka.search.IndexWorker]: DataNucleusPersist ==> Now: 1422556554940
INFO  (01/29) 12:35:54 [com.stoneware.service.Akka.search.IndexWorker]: DataNucleusPersist ==> Millis Diff: 5391943
INFO  (01/29) 12:35:54 [com.stoneware.service.Akka.search.IndexWorker]: DataNucleusPersist ==> Seconds Diff: 5391
INFO  (01/29) 12:35:54 [com.stoneware.service.Akka.search.IndexWorker]: DataNucleusPersist ==> DiffMins: 89.86571666666667
INFO  (01/29) 12:35:54 [com.stoneware.service.Akka.search.IndexWorker]: DataNucleusPersist ==> Elapsed Duration: 5391943 milliseconds
INFO  (01/29) 12:35:54 [com.stoneware.service.Akka.search.IndexWorker]: DataNucleusPersist ==> Min. Duration: 30 days
INFO  (01/29) 12:35:54 [com.stoneware.service.Akka.search.IndexWorker]: DataNucleusPersist ==> Not ok to crawl this user
DEBUG (01/29) 12:35:54 [com.stoneware.service.Akka.search.IndexWorker]: SearchWorker (indexWorker2) ==> Sending WSUserSet (count 0) to wsCrawlMountPointManager
DEBUG (01/29) 12:35:54 [com.stoneware.service.Akka.search.IndexWorker]: SearchWorker (indexWorker2) ==> All persistence work is done


    Can't find the KB

    Unable to find the KB to address your issue ?  

      • Recent Articles

      • Change Reset Password Button Text

        Change the text of the "Reset Password" button on the UW Login Page How to change the text of the Reset Password button on the Login Page. Login to webNetwork and open webAdmin on your Relay Central Server Expand Customization Center Expand Tenants ...

      • Remove Reset Password Button From Login Page

        Remove the Reset Password Button from the Login Page How to remove the Reset Password button from the Unified Workspace login page. Login to webNetwork and open webAdmin on your Relay Central Server Expand Customization Center Expand Tenants Expand ...

      • Lenovo Unified Workspace End-of-Life Questions and Answers

        As of January 31st 2024, Lenovo Unified Workspace (formerly Stoneware WebNetwork) is no longer supported. This means that we no longer provide licenses, downloads, updates, patches, or technical assistance for this product. If you have any questions ...

      • How do I determine my Unified Workspace license expiration date?

        The best method for determining the licensing information including the expiration date of your Unified Workspace license: Login to your 8090 management console on each server This may take remoting into each LUW server and relay, opening a browser, ...

      • Lenovo Unified Workspace 7.0.2.13 Released

        Highlights of Unified Workspace 7.0.2.13 Before you install: Please view the installation notes here. 7.0.2.13 requires a 7.0 license file. Below is a list of enhancements and fixes released in Unified Workspace 7.0.2.13 Fixed external storage ...

      • Related Articles

      • Explanation of the search.properties file.

        The search.properties file in the \stoneware\config folder configured / tunes the crawler / search features in webnetwork.  This file is only used on webNetwork servers not dedicated relays. # Disable crawler (true to completely disable all crawling ...

      • Common RDP Parameters

        The following are common RDP parameters for various RDP clients running through Unified Workspace. Windows ActiveX Client: AdvancedSettings2.PerformanceFlags will turn off certain features to improve performance. For instance, a value of: 1 - Disable ...

      • Debug relay startup problems.

        1) If you have your loaders clustered, make sure the cluster status is in sync by using the 8090 management console and checking the cluster status. 2) Use the 8090 console on the relay to turn on com.stoneware.client.stonewareclient debug.  When the ...

      • Disable Group Search for File Services

        Issue: In the past Unified Workspace (formerly webNetwork) required having to manually add some search indexes to prevent slowness issues in various parts of webNetwork, most notably (webStorage) File Services. When a user authenticates to Unified ...

      • Common Microsoft AD LDAP bind errors.

        LDAP error code 49 is the generic code for authentication error. https://helpdesk.lenovosoftware.com/portal/kb/articles/ldap-error-codes-22-8-2017 has the list of java ldap top level error codes. To fully understand the error you need the rest of the ...