Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Qlik Open Lakehouse is Now Generally Available! Discover the key highlights and partner resources here.
cancel
Showing results for 
Search instead for 
Did you mean: 
Anonymous
Not applicable

Fail to connect to CommandLine / Connection to generator failed.

This problem manifests in two different locations.
If you open the settings->configuration you will see an error under the commandline section, it will read "Fail to connect to CommandLine"
If you didnt happen to check this screen, and you tried to generate a task, the generation may fail with the error "Connection to generator failed (CommandLine).
Ok,  this problem has recurred for me.  Wanted to share past experience as these steps are not working this time.
First off, you need to know where your talend install directory is. In my case it is in /opt/talend.  You will see references to the command_line directory.   This works, but it may be of interest to know that the "command_line" directory is in reality just a link to the actual install directory, in my case /opt/talend/Talend-Tools-Studio-r118616-V5.5.1
So, if you run into this problem the following suggestions seem to resolve the problem most of the time:
1: "Delete the commandline workspace directory":   This instruction may lead you to make an awkward mistake.   Since you just changed into the "command_line" directory, you might assume the directory "workspace" is your target.  It is not!  You want to delete the "commandline-workspace" directory. You should do a recursive delete "rm -r commandline-workspace". The commandline-workspace will rebuild, the workspace will not.
2: "Copy your license file to the command_line directory."  Again, the directory you are copying into is simply a link to the actual directory.  This can be confusing if you are trying to "find" the license file.  Not sure if it is relevant, but I had a problem copying files for Talend from my Windows PC.  installing and using "dos2unix" on the files will correct any naughty line endings.
I usually just reboot the system after making changes.
In the past, these two steps always worked for me,  but this time they are not.   Any other suggestions?

Labels (2)
1 Reply
Anonymous
Not applicable
Author

Hi,
Have you tried to  stop commandline service and restart it to see if it works?
Best regards
Sabrina