Troubleshooting document describes known problems and solutions encountered during installation of the enterprise-components
on Windows
operating system.
Note:
Please use our google group or open a ticket in case you encounter any installation/startup problem which is not covered in this document.
enterprise-components
support for Windows operating systems is experimental at this point and there are some functionalities that are
known not to work. These include:
- eodMng/hdbSync component (
hdb
synchronization) is currently not working on Windows (core functionality is originally based onrsync
). - hk component (
housekeeping
) - the compress functionality requires the zip application to be installed and available onPATH
. When the pattern specified in the pattern column of the housekeeping table does not match any files, theforfiles
command used to find files on Windows returns an error. In such case the error message from the command is redirected to a file with extension.finderr
in thelog
directory for thehk
component. Also, a message is logged on theWARN
level. This does not affect the functionality of the component. - Monitor component - checking of disk usage and free disk space is currently not working on Windows (this
functionality is originally based on
du
anddf
). The rest of themonitor's
functionality is working on Windows. - The reconnect feature of the handle library may cause a process to be not responsive (busy and not accepting connections) when there are more than two processes to which the process is trying to reconnect.
- On Linux the Standard Library (
qsl/sl.q
) creates links to the initialization and current logs for a component. Such links are not created on Windows to avoid problems with insufficient privileges. - The
.os.sleep
function has 1000ms (1s) resolution on Windows. If the sleep parameter is not a multiple of 1000, it is rounded up to the nearest multiple of 1000.