The cause is a missing wrapper.dll file, which is required during a pre-check test of the Collector during upgrade. This is a known issue regarding upgrading a Windows collector from versions 19.60-x to the latest released version. "This Collector does not seem to have tanuki wrapper integration enabled." Answer When attempting to upgrade a Windows Collector from the UI, the upgrade fails and the following error is reported in the tool tip of the failed Collector: Windows - This Collector does not seem to have tanuki wrapper integration enabled Įrror messages on Windows: "This Collector does not seem to have tanuki wrapper integration enabled." Question The Collector will start back where it left off in the logs when the previous Collector was stopped. This should safely update the Collector and keep all your existing configurations and Sources. (It will have automatically started.)Ĭopy the previously backed up /config and /cache directories and put them into the new Collector installation directory, overwriting the existing /config and /cache directories. Deleted this from the UI as the last step in this process. The new install will create a new collector in the UI with an appended epoch time. Run the new 64-bit Collector install to reinstall the Collector. Run the Collector uninstall to completely remove the existing 32bit Collector. Make a backup copy of the current C:\Program Files (x86)\cache directory and place this in a safe temporary location. Make a backup copy of the current C:\Program Files (x86)\config directory and place this in a safe temporary location. To manually upgrade the Collector from 32-bit to 64-bit Any further upgrades of the Collectors through the UI will continue to update using the same 64-bit version. This is a one-time manual update to existing Collectors. This issue can be resolved on 64-bit versions of Windows by upgrading to the 64-bit version of the Collector. In some instances, this could prevent the log file from properly rotating. The Sumo Logic Collector will hold a log file open for read while log messages are actively being written to the file, and may not close the file for up to a couple minutes after the log has stopped being written to. Collector locking log files on Windows servers Restart the computer after changing this setting for the new value to be applied. The value name is MTU and the data value should be set to 1500. Run the following command to determine the current MTU value: If your client runs in a Linux operating system, you can review and set the MTU value by using the ip command. Setting the default MTU on a Linux Operating System Path MTU Discovery is responsible for ensuring that packets of the correct size are sent to each end point by first checking whether the end point can handle jumbo frames, and then resending the packet in smaller chunks until it's successfully sent. Packets will be dropped in cases where ICMP Unreachable messages are disabled on the receiving end since Path MTU Discovery relies on these messages to determine the correct packet size. This is referred to as using jumbo frames and can cause packet loss since not all devices on the internet support large packet sizes. the age old default of 1500 bytes. In newer AWS EC2 VPC's, the MTU is set to 9001 by default. For example, MTU being set to 9001 bytes vs. Rule out dropped packets due to jumbo frames being unsupported by your network end points.
0 Comments
Leave a Reply. |