Known Issues for Virtual Appliance Version 99.0.0
The following are the known issues included in this release.
Issue Number | Issue Description | Workaround |
|---|---|---|
220850 | After upgrading the appliance, the process of logging into the appliance can take more than 15 minutes. | There is no workaround. |
155957, 174165 | Uploading log files from AWS S3 to Netskope tenant fails when S3 is connected through proxy in secure mode. | When accessing AWS S3 through proxy in secure mode, the OPLP appliance suppresses the proxy information. To connect to S3 through proxy, you must turn off secure mode. |
113634 | If timezone is configured on the OPLP appliance and timezone is also specified in the parser, then the date and time for the logs uploaded through the OPLP appliance is incorrect in Skope IT. | There is no workaround. |
211845 | When an IPv6 interface is configured, updating the setting (ip, netmask) will cause the CLI to continuously restart. | If the interface setting needs to be changed, follow the workaround below:
|
Currently, discovery / OPLP can accept log files, system logs, and custom parsers files in UTF-8 encoding only.
If these files are encoded using other encodings, we may fail to parse them properly. This will manifest as UnicodeDecodeError in our logs.
The best practice is to set UTF-8 as the default encoding in all pipelines feeding into OPLP. UTF-8 can handle any character set, so this will not result in any information loss.
For the log files that are already encoded without using UTF-8, convert these files to UTF-8 before uploading them to OPLP.
The following is an example using a file that is encoded in UTF-16.
Unzip if log files are zipped. In this example, the unzipped text file is logsample.log.
Check current encoding used: file logsample.log > outputs “Little-endian UTF-16 Unicode text,”
Convert it to UTF-8 as iconv -c -f utf-16 -t utf-8 logsample.log > logsample_utf8.log
Send logsample_utf8.log to OPLP either as a text file or zipped file.