{"id":1425,"date":"2015-01-20T06:04:30","date_gmt":"2015-01-20T06:04:30","guid":{"rendered":"http:\/\/pariswells.com\/blog\/?p=1425"},"modified":"2015-06-15T22:58:29","modified_gmt":"2015-06-15T22:58:29","slug":"worksiteimanage-connectercrawler-not-running","status":"publish","type":"post","link":"https:\/\/pariswells.com\/blog\/fixes\/worksiteimanage-connectercrawler-not-running","title":{"rendered":"Worksite\/Imanage Connecter\/Crawler not running"},"content":{"rendered":"\r\n

\"worksite\"After an Indexer Server Veeam restore, the Worksite Connector\/Crawler started but no log file updated, which meant it was in a stale state.<\/p>\r\n

Stop the Worksite Connector Service<\/p>\r\n

Go to the directory : Worksite Connector\\actions\\fetch<\/p>\r\n

Delete fetch.queue file<\/p>\r\n

Start the service back up<\/p>\r\n

Check to make sure the log file location in Worksite Connector\\logs\\worksiteCrawler.log is updating<\/p>\r\n

You might want to check the ingestion service log is also updating or you might need to clear the ingest.queue<\/p>\r\n

If below does not work this might need to be done<\/strong><\/p>\r\n

    \r\n\t
  1. Stop all services.<\/li>\r\n\t
  2. Ran _cleanup scripts from E:\\Indexer\\WorkSite Connector\\ & \u00a0E:\\Indexer\\WorkSite Ingestion Server\\<\/li>\r\n\t
  3. Changed the time in this file E:\\Indexer\\WorkSite Connector\\connector_DBNAME_datastore.db back to \u201cm\/d\/yy\u201d the date when the indexer stopped working. Please note this time is in \u201cepoch\u201d so you will need a timestamp converter.<\/li>\r\n\t
  4. Started services.<\/li>\r\n<\/ol>\r\n

    To stop and start the services, there are 2 methods:<\/strong><\/p>\r\n

      \r\n\t
    1. Run the script in \u201cIndexerInstallDrive<\/em>\\Indexer\\_stop_services\u201d, \u201cIndexerInstallDrive<\/em>\\Indexer\\_start_services\u201d<\/li>\r\n\t
    2. Log into the Autonomy Control Center \u201chttp:\/\/IndexerServerName<\/em>:8080\/controlCenter<\/a>\u201d. Default username and password \u2013 admin\/admin. Once logged in you can stop and start all services in the GUI.<\/li>\r\n<\/ol>\r\n

      \u00a0\"worksiteindexer\"<\/a><\/p>\r\n

      \u00a0 Essentially when indexing, data flows in the following order:<\/strong><\/p>\r\n

        \r\n\t
      1. The WorkSite Connector service to crawl WorkSite databases servers.<\/li>\r\n\t
      2. The WorkSite Ingestion service, which converts all files to the IDX format.<\/li>\r\n\t
      3. The WorkSite Content service, which indexes all of the content and serves search requests.<\/li>\r\n<\/ol>\r\n

        \u00a0 When troubleshooting indexer issues, the logs are key to identifying issues. I recommend you use \u2018BareTail\u2019 as this allows you to view the many logs as well as the changes to them, each component has at least 5 types of logs.<\/p>\r\n

        \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Connector: componentinstalldisk<\/em>:\\Indexer\\WorkSite Connector\\logs<\/p>\r\n

        \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Ingestion: componentinstalldisk<\/em>:\\Indexer\\WorkSite Ingestion Server\\logs<\/p>\r\n

        \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Content: componentinstalldisk<\/em>:\\Indexer\\WorkSite Content\\logs<\/p>\r\n

         <\/p>\r\n

        Here is a nice write up from Autonomy from when the client wants a better understanding about timing with the indexer:<\/p>\r\n

        1. Customer drags a document into WorkSite (~1-2 seconds, very minimal)<\/p>\r\n

        2. WorkSite Crawler crawls searching for new\/updated documents during interval of time between each crawl. (takes a 1 minute rest between crawls)<\/p>\r\n

        3. Document is moved through Ingestion (~1-2 seconds, very minimal)<\/p>\r\n

        4. Document is moved through Active DIH (~1-2 seconds, very minimal)<\/p>\r\n

        5. Document is moved to Active Content, where every 15 seconds Active Content writes the data to disk making it available for search.<\/p>\r\n

        So the time for a new document to be indexed is a lot based on where the Connector and Active Content is on it\u2019s interval. Potentially you could see a 1 minute 30 second delay, or potentially only a 30 second delay before searchable.<\/p>\r\n","protected":false},"excerpt":{"rendered":"

        After an Indexer Server Veeam restore, the Worksite Connector\/Crawler started but no log file updated, which meant it was in a stale state. Stop the Worksite Connector […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[14],"tags":[1034,878,879,622,912,881,623,877,882,880],"class_list":["post-1425","post","type-post","status-publish","format-standard","hentry","category-fixes","tag-active-dih","tag-crawler","tag-fetch-queue","tag-imanage","tag-indexer","tag-ingest-queue","tag-worksite","tag-worksite-connecter","tag-worksite-ingestion-service","tag-worksitecrawler-log"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t