Restrictions
Describes the specification limitations of WHEEL.
If the remote task is terminated by a signal
If a process running on a remote host terminates due to a signal, it is considered to have terminated normally because the WHEEL specification does not allow the remote signal number to be supplemented.
About Task Types The terms used to describe the various tasks have the following meanings:
| Term | Meaning |
|---|---|
| Local task | Represents a task to run on localhost. |
| Remote task | Indicates the task to be executed on the remote host. Do not use a batch system. |
| Remote Job Task | Represents a task that runs on a remote host using a batch system. |
Handling Running Scripts When Stopping a Project
If the Stop Project button stops the project, the script set to WHEEL is stopped, but any child processes called from the script are not stopped.
Handling Large Files
WHEEL uses git to manage data handled by projects. Therefore, placing large files in the project directory can cause various problems due to poor performance of repository operations. To avoid this problem, configure git LFS to manage files larger than a certain size uploaded from the WHEEL graph view. Be aware that if you add files to your project’s git repository by means other than WHEEL, you may not be able to work with them properly depending on their size.
Changing the connector name with the input/output connector connected
If you rename an input connector while multiple output connectors are connected to one input connector, multiple renaming operations are performed at the same time, and the components may not be consistent. Before editing the input/output connector, disconnect it.
Operating in a Windows Environment
If the WHEEL operating environment is WindowsOS, an error may be displayed when you execute delete of the project. The deleted project is deleted from the project list, but the actual data is not deleted. Delete manually.
About holding and unknown conditions
If a project contains a task that submits a job, the state of the project may be in the holding or unknown state. The holding state is transitioned when the WHEEL process has terminated before confirming that the job has been submitted and terminated. In this state, the execution of the project is paused, but only the job that was submitted before the process ended is acknowledged. The status changes to unknown when all jobs have finished.
The unknown state means that the state of the project cannot be determined. If you are transitioning from the holding state described above, check the state of the individual components to make sure that all tasks have been completed. If there are tasks that have not finished, rerunning the project will rerun only those components that are not running and failed.
In addition, if the status check processing after a job is submitted fails (e.g. When the batch system cannot be connected due to a temporary failure, etc.), the status is unknown. In this case, log in to the job destination server directly to check whether the task in unknown status has finished normally, and then copy any necessary files.
About Importing Existing Projects
When WHEEL reads an existing project that is not in the project list, it commits all changes to the git repository. Therefore, if the imported project or components in the project are not “not-started,” you will not be able to clean the project again. Therefore, check the state of the project and components before loading.
If you get the “Control socket creation failed” error while connecting via ssh
If you share ${HOME}/.ssh between the host and WHEEL container in the docker environment, sometimes you get this error. In this case, you may avoid this error by adding the following environment variable via the docker run argument
-e SSH_CONTROL_PERSIST_DIR=/tmp
This error occurs if the directory which is used to store the socket file for ssh multiplex connection
is shared between the docker container and the host OS.
With this option, the socket file will go to the SSH_CONTROL_PERSIST_DIR directory, so that you can avoid this error
If you get “remote host identification of XXX is different from the one on line YYY of ~/.ssh/known_hosts” error while connecting via ssh
This error means the server sent a different host key than the last time you accessed it. Someone could be eavesdropping on you right now, but it may cause that the host key has just been changed in ordinal operations.
For example: - Server OS is updated and the host key is initialized - The server is behind a load balancer and you access the server with the same hostname but connect to a different server - The server is a container or virtual machine, so sometimes re-initialize OS and ssh server - You access to server via port-forwarding and you make the tunnel to another server on the same port as the last server connected to
If you are certain that these changes have been made on the server with the intent to, because of an announcement from the server administrator or you are the administrator yourself, you can remove the previous entry by following the command. Please try to connect the server from WHEEL after executing the command.
ssh-keygen -R 'XXX'
Or, you can delete the previous entry at line number YYYY on ~/.ssh/known_hosts by using a text editor or something