Hi,
I am trying to connect to a remote jobserver. The job server is connecting fine on the remote server. My problem is the job server is not responding on the local machine.When i hover over the icon for the job server in the designer It says
Job server is not responding – BODI - 1241021/1241023
The 3500,4000,4001 port is open from local to remote server.
Please suggest what can be the reason??
Is there any other port which is required?
I am using Oracle 10 g for local repository.
Just goto the Job Server Config and re-sync your repository. This happens sometimes when you configured your Job Server after the Local Repo setup or maybe you are trying to connect to a new JS.
If this would not work fine check if there are entries in the AL_MACHINE_INFO table in the Repository Metadata table.
It say’s “jobserver not responding” plus a servername:hostname:port. Is the hostname correct? Does a “ping hostname” command work from a dos box?
Often the hostname is just a short name, e.g. myunixhost but needs full qualification e.g. myunixhost.domain.com. AL_MACHINE_INFO (and for later a DSConfig parameter I keep forgetting the name for) is the way to go.
@wdaehn
Yes I have changed the hostname with proper IP of the server.
Even then the problem is same. (Able to connect from server machine but not able to connect from other systems).
I carried out the same installation over my LAN by making one system as server and others by client. It is working fine, i can connect to server(LAN machine), job server is working fine.
What i am thinking that there is some problem with ports. Could you please guide me whether any other port is required to establish the connection?
I checked my LAN setup port usage by netstat -nobv
It is showing that the local machine is connecting to LAN server by 3500 and also one more port which is dynamic and it is changing every time new connection is established.
While making connection to the ACTUAL server this port connection is not available, Only 3500 is available.
“JobServer not responsing” means the Designer pings the JobServer on port 3500 and does not get a response.
Did you try to ping the server from the designer using the hostname as shown in the designer?
When you connect to the JS on 3500 it tries to return a message to Designer using one of the ports specified in the range identified in server manager in peer-to-peer options. If these ports are not open you will not get any feedback to Designer. You need to make sure the specified range of ports is open and if you restrict the range then make sure that the same range is specified in Designer --> Options -->Environment in the Designer Communication Ports section.
If you get a notification error, your plan would be the fix. But we are not there yet, we can not even talk to the jobserver and tell it the port number to use.
@Wdaehn
Ping is not allowed to the server due to security reasons…So i am unable to ping even port 3500 is open.
I have checked it by telnet “serverip” 3500.
This is connecting.
@Wdaehn/Swiker
I am in the process of getting one port opened from server to client, as suggested by you for receiving reply from the server.
I will specify this particular port at sever and client both.
Once it will be done. I will get back with the output
Werner, I’ve just had to deal with this same issue and the network and firewall guys did some monitoring for me. When designer initiates the call on 3500 the return packet on some port other than that initiates a new session, this caused the exisitng firewall rule to be invalid in our instance. I’m no firewall expert but just allowing two way communication on the one port is not sufficient apparantly if it’s a new session.
Designer sends a packet to the JobServer on port 3500. As this is a TCP packet and not UDP, an acknowledge-packet has to be sent back. Usually with firewalls you check who initiates the communication and let the return packets pass automatically. TCP is a bidirectional stream.
If this packet does not return, Designer does not know if somebody received it or not and hence says “Jobserver not found”.
If that first step was successful a spanking new session will be created, this time with the jobserver being the initiator, the Designer the listener. That does happen because the initial packet sent before was a notification request: “Dear jobserver, I would like to receive all notifications about log changes from you. Therefore I am starting a listener thread at port xyz.”
But if the firewall does not allow the jobserver to initiate a TCP connection, the Designer will not see any action although both parties agreed, hence it shows a notification error.
So in short:
“notification error” means jobserver cannot initiate a TCP connection to Designer.
“jobserver not found” means Designer cannot initiate a TCP connection to jobserver.
As I understand it from our analysis that is exactly how it works. In our instance where no return packet was allowed I was expecting that one way communication Designer --> Job Server would allow a job to be run from Designer, albeit with no feedback. I guess two way communication needs to be established before the job launcher will start a job.
(BOB member since 2010-08-27)
(BOB member since 2008-07-17)
(BOB member since 2004-12-17)
(BOB member since 2010-08-27)
(BOB member since 2009-02-20)
(BOB member since 2004-12-17)