Unable to communicate to Job Server: Socket is Closed

system · April 10, 2013, 12:51pm

Hi,

I am trying to execute a job from the Console, but get the following exception when the job is executed-
“Exception thrown when trying to communicate with Job Server:XXXXXXv007:3500. Socket is closed”. I do not have an option to execute the job from Designer due to firewall issues. I was able to telnet to the job server port using command prompt from the Client.

Please let me know if this is related to network configuration between Console and Job Server? and any steps to resolve this?

Ankit J (BOB member since 2013-03-14)

system · April 10, 2013, 6:03pm

Is the Job Server and the Web Server (for the Management Console) on the same O/S (same machine)?

Sounds like a firewall issue to me. Or the Job Server isn’t running?

eganjp (BOB member since 2007-09-12)

system · April 11, 2013, 2:52am

Yes, both the Job Server and Web Server are on the same machine (same OS)

The Job Server is running and enabled (at least thats what the status on the CMC says)

Ankit J (BOB member since 2013-03-14)

system · April 11, 2013, 4:01pm

Is that the correct port number? Sometimes the port number defined for the job server (using Server Manager) and the port number recorded in the repository table (al_machine_info) are not in agreement.

Otherwise, I’m out of ideas.

eganjp (BOB member since 2007-09-12)

system · April 11, 2013, 6:17pm

you can’t see the status of DS Job Server in CMC, for DS Job Server check if you have started the Data Services Service (Windows service) also check for the existence of al_jobserver process in the task manager

check the DS Job server log fine in %LINK_DIR%\log<JobServerName>\server_eventlog_.txt file for any errors

manoj_d (BOB member since 2009-01-02)

system · April 24, 2013, 3:46pm

Do you have an anti virus in place? Some times it restricts the communication.

Arun

Arun.K (BOB member since 2011-10-18)

system · April 24, 2013, 6:38pm

So far we have confirmed the following items but the issue is not yet fixed-

There is no anti-virus installed
Job Server is running
Confirmed that tnsnames.ora and listener.ora files have all the required components
No firewall exists between Web Server and Job Server (they both are in the same server)
No difference in OS (since they both are on the same server)

Any other options that we can check??

Ankit J (BOB member since 2013-03-14)

system · April 24, 2013, 6:42pm

For the repository in which the ETL job resides please post the output of table AL_MACHINE_INFO. You may mask the actual machine name when you post the results to the forum.

The values in that table must match the current configuration of the job server (machine name/ip address, port numbers, etc).

eganjp (BOB member since 2007-09-12)

system · April 25, 2013, 5:25pm

eganjp,
Here is the output from AL_MACHINE_INFO
SEQNUM || SERVER_NAME || MACHINE_NAME || PORT
44 || Administrator || XXXl08v007 || 8080
36 || Administrator || XXXl08v007.XXX.com || 8080
1 || RepoManager || ||
2 || JobServer_1 || XXXl08v007 || 3500

Couple of my observations-

XXXl08v007, XXXl08v007.XXX.com are the different host names to same IP address. To log into CMS and DS Console, we use XXXl08v007XX7 that is a third host name to the same IP address
Why is the RepoManager values blank for machine name and port?

Please advice…

Ankit J (BOB member since 2013-03-14)

system · April 25, 2013, 5:32pm

XXXl08v007 is the name that the Management Console web server/app server is going to use to try to talk to the job server. The port number is also used. If either of these are wrong then the Management Console can’t start the job and you get an error. If the Management Console and the job server are on the same machine you could change the MACHINE_NAME value to LocalHost I belive. I would only do this to troubleshoot. I don’t normally leave it that way.

If you have other repositories on the same job server that are working then compare the values in AL_MACHINE_INFO and make adjustments as needed.

It’s possible that the information in AL_MACHINE_INFO is completely correct. But it’s where I would start.

eganjp (BOB member since 2007-09-12)

system · April 25, 2013, 7:05pm

We just resolved this error!

The port configuration of the servers for the repository were set to auto assign that was not supported by the environment.

We directly entered the port number for each service and were able to execute the job.

Thanks everyone for your help! Appreciate your responses!

Ankit J (BOB member since 2013-03-14)

system · July 2, 2014, 5:24am

็Hi,Ankit J

I had this same problem And have tried many ways to solve it.

How to configuration port number

Help explain please?

khaicanyon (BOB member since 2014-07-02)