- Coveo On-Premises Crawling Module
Updating the Coveo On-Premises Crawling Module 0.2
Since version 0.3, released on March 30, 2018, the Coveo On-Premises Crawling Module update process is automatic. This allows you to benefit from the latest features and bug fixes, and prevents the Crawling Module from becoming incompatible with the most recent Coveo Cloud update. Therefore, to stay up to date, the Crawling Module periodically polls the Coveo Cloud platform for a new version of its components. If an update is available, it will be downloaded and installed within 24 hours, at the scheduled update time. The default schedule is 11:00 PM (see Editing your On-Premises Crawling Module Configuration).
Disconnecting your server from the Internet or shutting it down will result in the Crawling Module not polling Coveo Cloud for updates. Upon the next successful call for an update, if a component is two or more versions behind, the workers will stop until the Crawling Module is up to date again.
If automatic updates fail or if you cannot wait for the next scheduled update, you can update Maestro and the workers manually (see Updates). You can also contact the Coveo Support team for assistance.
If you installed the Crawling Module for the first time on March 30, 2018 or later, you do not need to trigger the update process manually, unless it fails (see Deployment Overview and Updates). However, customers currently using the Crawling Module 0.2 must follow the instructions below to update to version 0.3.
Disable antivirus protection for the
C:\ProgramData directory while you update the Crawling Module.
- Kill your workers (see Killing the Workers and Removing the Database).
- Download the latest version of the Coveo On-Premises Crawling Module on the server on which you originally installed version 0.2.
- In the unzipped CrawlingModules folder you saved on your machine, open the scripts folder.
- Click the File tab, and then, in the menu, click Open Windows PowerShell as an administrator.
- In the Administrator: Windows PowerShell command prompt, run the two following commands to validate that all Docker containers have effectively been removed:
docker swarm leave --force
docker rm -f crawlers_db
- In the Administrator: Windows PowerShell window, type
.\deleteCrawlingModulesService.bat, and then press Enter. This deletes the
Coveo.CrawlingModulesWindows service. In the confirmation dialog, click Yes.
- Ensure that the
Coveo.CrawlingModulesservice has been removed from the Windows Services:
- In the task bar, click the Windows icon, and then, in the start menu, click Services.
- In the Services window, browse the Services (local) list, looking for
Coveo.CrawlingModules. If it is not in the list, it has effectively been removed.
Delete the Maestro directory you created when installing the crawling module package (see Installing Maestro).
If you get an
Access Deniederror stating that a file is already in use, reboot your machine, and then retry deleting the directory.
Do not delete
C:\ProgramData\Coveo, as this folder contains your Crawling Module configuration and logs.
Reinstall Maestro (see Installing Maestro).
Your Crawling Module configuration and indexed content should remain unaffected by the update.
It should not be necessary to authenticate to the Coveo Cloud platform again (see Linking Maestro to the Coveo Cloud V2 Platform).
Update your workers (see Updating the Workers).
- Restart your workers (see Starting the Workers and Database).