I've had a couple of problems with the RA server for Solaris.

I tried downloading the native version but although the file
command recognises that it is executable, and the permissions are
correctly set, I still get:

devdb02_oracle @ /u01/app/oracle/product/24x7 # ./ra_server
ksh: ./ra_server: cannot execute

I then tried the java version. I used the server.sh script to start
the RA server. I created a new remote agent using the GUI, and tried
to test the connection. This hung, and the following
message was logged by the RA server:

SEVERE: Bad packet received: magic: 0x6000 command: 66 reply: 76 arg0: 0x8f arg1: 0x0 arg2: 0x0 length: 6751
45

I'm running the Java version of the Master Scheduler also on Solaris.

For native code version try first chmod 755 ./ra_server to make an executable
then run it like
./ra_server -p 1096 -f ra_server.log -s

and see what you get in the log file

For both native code and Java version, don't try to connect from the GUI.

Anyway, I think you are confused by the number of available options. From your previous post I assume you are trying to run 24x7 Scheduler Java Edition. This scheduler does not need remote agents. It can run itself as an agent. Just install and run it on remote computer as "./agent.sh nogui" then you can define a profile and connect to it from the master scheduler. Again options you have tried before aren't needed for the Java Scheduler.

: I've had a couple of problems with the RA server for Solaris.

: I tried downloading the native version but although the file
: command recognises that it is executable, and the permissions are
: correctly set, I still get: devdb02_oracle @ /u01/app/oracle/product/24x7 #
: ./ra_server
: ksh: ./ra_server: cannot execute

: I then tried the java version. I used the server.sh script to start
: the RA server. I created a new remote agent using the GUI, and tried
: to test the connection. This hung, and the following
: message was logged by the RA server: SEVERE: Bad packet received: magic:
: 0x6000 command: 66 reply: 76 arg0: 0x8f arg1: 0x0 arg2: 0x0 length: 6751
: 45

: I'm running the Java version of the Master Scheduler also on Solaris.

Thanks for that. Just to clarify: If I am using the Java
Scheduler, and I want to execute jobs on one or more
remote servers, I install the Java Scheduler on each of
those remote servers, and then use the agent.sh script on
those servers to start an agent?

: For native code version try first chmod 755 ./ra_server to make an executable
: then run it like
: ./ra_server -p 1096 -f ra_server.log -s

: and see what you get in the log file

: For both native code and Java version, don't try to connect from the GUI.

: Anyway, I think you are confused by the number of available options. From
: your previous post I assume you are trying to run 24x7 Scheduler Java
: Edition. This scheduler does not need remote agents. It can run itself as
: an agent. Just install and run it on remote computer as "./agent.sh
: nogui" then you can define a profile and connect to it from the
: master scheduler. Again options you have tried before aren't needed for
: the Java Scheduler.

PS

I have installed the Java Scheduler on a second
Solaris server, and run the agent.sh script. I can
start the agent GUI OK, and network options are
configured so that the agent is using port 1096.

I tried adding the agent profile to the Master Scheduler
but again it hangs when I try to test the connection.
The following error is displayed on the console from
which I launched the Master:

IOException while running socketReader: java.io.EOFException
java.io.EOFException

at java.io.DataInputStream.readInt(DataInputStream.java:448)

at com.sybase.dpb.AsyncSocketReader.run(AsyncSocketReader.java:41)

: Thanks for that. Just to clarify: If I am using the Java
: Scheduler, and I want to execute jobs on one or more
: remote servers, I install the Java Scheduler on each of
: those remote servers, and then use the agent.sh script on
: those servers to start an agent?

Correct.

: Thanks for that. Just to clarify: If I am using the Java
: Scheduler, and I want to execute jobs on one or more
: remote servers, I install the Java Scheduler on each of
: those remote servers, and then use the agent.sh script on
: those servers to start an agent?

My guess is that port 1096 is in use. Try a different number, for example, 10099. You will need to use that number in both places - agent settins (see Tools/Options; Network Properties) and Master (see Agent Profile properties)

By the way, somebody had this issue before.
Please take a look at http://www.softtreetech.com/cgi_bin/config.cgi?read=6645
and also at http://www.softtreetech.com/cgi_bin/config.cgi?read=6651

I think it was resolved by updating Java JRE or JDK to a more recent version and picking different ports for the master/agent communications

: PS

: I have installed the Java Scheduler on a second
: Solaris server, and run the agent.sh script. I can
: start the agent GUI OK, and network options are
: configured so that the agent is using port 1096.

: I tried adding the agent profile to the Master Scheduler
: but again it hangs when I try to test the connection.
: The following error is displayed on the console from
: which I launched the Master: IOException while running socketReader:
: java.io.EOFException
: java.io.EOFException

: at java.io.DataInputStream.readInt(DataInputStream.java:448)

: at com.sybase.dpb.AsyncSocketReader.run(AsyncSocketReader.java:41)

I tried using 10099. I used netstat before just to check that the
port was not in use.

Both the scheduler and agent servers are using the sma eJRE version:

devdb02 # java -version
java version "1.4.2_04"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_04-b05)
Java HotSpot(TM) Client VM (build 1.4.2_04-b05, mixed mode)

devdb01 # java -version
java version "1.4.2_04"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_04-b05)
Java HotSpot(TM) Client VM (build 1.4.2_04-b05, mixed mode)

I still get the same problem. I have even tried starting the master
and agent on the same server - no luck.

: My guess is that port 1096 is in use. Try a different number, for example,
: 10099. You will need to use that number in both places - agent settins
: (see Tools/Options; Network Properties) and Master (see Agent Profile
: properties)

: By the way, somebody had this issue before.
: Please take a look at
: http://www.softtreetech.com/cgi_bin/config.cgi?read=6645
: and also at http://www.softtreetech.com/cgi_bin/config.cgi?read=6651

: I think it was resolved by updating Java JRE or JDK to a more recent version
: and picking different ports for the master/agent communications

I will forward this info to support and get back to you as soon as I hear anything back.

: I tried using 10099. I used netstat before just to check that the
: port was not in use.

: Both the scheduler and agent servers are using the sma eJRE version: devdb02
: # java -version
: java version "1.4.2_04"
: Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_04-b05)
: Java HotSpot(TM) Client VM (build 1.4.2_04-b05, mixed mode)

: devdb01 # java -version
: java version "1.4.2_04"
: Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_04-b05)
: Java HotSpot(TM) Client VM (build 1.4.2_04-b05, mixed mode)

: I still get the same problem. I have even tried starting the master
: and agent on the same server - no luck.

You must be checking "remote agent is 24x7 Scheduler v3.x" option in the agent profile, which is the casue of the problem. Don't check that option and you will be fine.

FYI: This option is for connecting to 24x7 Scheduler v3 for Windows which is a "sibling" Non-Java version of the 24x7 Scheduler. This option casues 24x7 to use a different connection method and protocol which leads to the communication error.

: I will forward this info to support and get back to you as soon as I hear
: anything back.

Many Thanks for that - working fine now.

: You must be checking "remote agent is 24x7 Scheduler v3.x" option
: in the agent profile, which is the casue of the problem. Don't check that
: option and you will be fine.

: FYI: This option is for connecting to 24x7 Scheduler v3 for Windows which is
: a "sibling" Non-Java version of the 24x7 Scheduler. This option
: casues 24x7 to use a different connection method and protocol which leads
: to the communication error.