I am trying to deploy a job through the TAC, and I am receiving an error "Connection to server failed" for just one of my jobs. The other jobs are running file. When I check the jobserver logs, it shows: Caused by: java.io.FileNotFoundException: /opt/Talend-5.4.1/jobserver/agent/./TalendJobServersFiles/repository/XXXX_MainXXXXX_20141124_165609_freso/MainXXXXX/MainXXXXX_run.sh (No such file or directory) at java.io.FileOutputStream.open(Native Method) at java.io.FileOutputStream.<init>(Unknown Source) at java.io.FileOutputStream.<init>(Unknown Source) at java.io.FileWriter.<init>(Unknown Source) The problem appears to be, job in the job server is an old jobs, and I can delete or get rid of it. I tried shutting everything down and restarting the jobserver, but the error still persists. How do I get rid of this old job, which appears to be stuck in the job server? Thanks!
It is a bit strange. Perhaps the job needs a lot more jars unlike the others.
Could it be someone has started the jobserver accidentally with the wrong user?
Check if the file exists and if the files does have the correct rights.
One way to fix that is to delete the problem task from the job server repository and delete also the task in the TAC and re-create the task.
This way I have managed to solve such problems. In my tests in the new release 5.4.2 I have never experienced these problems anymore.
OK it must be something with the file name. You XXXX-t something out or it is the real name? I would suggest you file a support ticket because you have a support subscription.
Hi Guys, While trying to Run the jobs via the TAC, im getting the error Connection to the server failed. This issue got resolved after restarting the JOB server and TAC server. I would like to know the reason for the failure and why the restart worked..??
Hi Guys, While trying to Run the jobs via the TAC, im getting the error Connection to the server failed. This issue got resolved after restarting the JOB server and TAC server. I would like to know the reason for the failure and why the restart worked..??
You get an error because of a connection failed to the job server? In this case - especially if you run under Windows: We had the same problem and reason was, someone stupid has updated the Kasperski Virusscanner and the most recent version established on port 8888 its own server port. After a reboot the job server and Kasperski was fighting for the port.
This is also because of the tac server space issue .
check if your talend installation directory is 100% and clean up the old logs or unwanted files in my scenario it was due to 100% of tac installation directory
