Author |
Message |
dzafer
Joined: 11 Aug 2008 Posts: 5 Country: Belgium |
|
Scheduler/RA server error code 57 - bad packet received |
|
Hi there,
I am testing the scheduler/RA agent solution
Installed products:
 |
 |
Trial - 24x7 scheduler version:3.4.32 on windows w2k3
Trial - 24x7 RA Server (Java) Version N/A. Build 14 (08.01.2004) on Solaris10 |
Requirements:
 |
 |
I need to run a shell script remotely on the Solaris server |
Test
 |
 |
////////////////////////////////////////////////////////////
// 24x7 Scheduler 3.4.32
// Job Template: 24x7 UNIX RAS (Run program on UNIX host)
// Generated on 7-August-2008 13:01
////////////////////////////////////////////////////////////
RAConnect( "172.31.105.52", 1096, "oracle", "xxx" )
Dim( process_id, number )
RARun( "ls", process_id )
RADisconnect |
Error received :
 |
 |
Job Started
Agent test contacted
Fail to execute remote job Unknown error occur : Error code 57 |
In the Agent server log:
 |
 |
INFO: start
11-aug-2008 11:02:46 com.softtree.raserver.Session run
SEVERE: Bad packet received: magic: 0x6000 command: 66 reply: 76 arg0: 0xa2 arg1: 0x0 arg2: 0x0 length: 675145
11-aug-2008 11:02:46 com.softtree.raserver.Session run
SEVERE: java.lang.RuntimeException: Bad packet received!
11-aug-2008 11:02:46 com.softtree.raserver.Session run
INFO: end |
Whatever is the command to be executed remotely, I receive always the same error.
Any help will be appreciated.
Thanks
|
|
Mon Aug 11, 2008 5:26 am |
|
 |
SysOp
Site Admin
Joined: 26 Nov 2006 Posts: 7949
|
|
|
|
Are you using the required JRE or JDK 1.4 or some other version?
|
|
Mon Aug 11, 2008 9:47 am |
|
 |
SysOp
Site Admin
Joined: 26 Nov 2006 Posts: 7949
|
|
|
|
Just out of curiosity, why aren't you using the Multi-platform version of 24x7 and thus avoiding a need to deal with the remote agents on Solaris?
|
|
Mon Aug 11, 2008 9:49 am |
|
 |
dzafer
Joined: 11 Aug 2008 Posts: 5 Country: Belgium |
|
|
|
It's Java version "1.5.0_14" (JRE)
Do you mean that no RA agent is required using the Multi-Platform of the 24x7Scheduler?
I will give a try. Thank you.
|
|
Mon Aug 11, 2008 10:31 am |
|
 |
SysOp
Site Admin
Joined: 26 Nov 2006 Posts: 7949
|
|
|
|
Major Java versions are not forward or backward compatible, The Universal version 0f 24x7 RA requires use of JRE 1.4.
Yes, the 24x7 Multi-platform Edition can run directly on the Solaris. You can run it both in scheduler and agent modes; and to scripting is needed for the scheduler/agent communications, in case of remote jobs.
Please note that you still need JRE 1.4 to run the Multiplatform Edition on Solaris.
|
|
Mon Aug 11, 2008 10:38 am |
|
 |
dzafer
Joined: 11 Aug 2008 Posts: 5 Country: Belgium |
|
|
|
Ok,
There was a confusion about the global configuration:
Now I have
- 24x7 Scheduler Multi-platform is installed with the jre 1.4 on windows (main scheduler)
- 24x7 RA on solaris10 64 bits (remote agent)
- Later other RA will be installed on different platforms (windows, linux ...)
No I receive this error
 |
 |
ftp conversation failed:500 'SITE FILETYPE = JES': command not understood |
I found on the forum a similar issue but I don't know how to solve it regarding the host file
Here is my hosts file
 |
 |
#
# Internet host table
#
::1 localhost
127.0.0.1 localhost
172.31.4.63 orasrv-1 loghost |
Thank you
|
|
Tue Aug 12, 2008 4:10 am |
|
 |
SysOp
Site Admin
Joined: 26 Nov 2006 Posts: 7949
|
|
|
|
Sounds like a lot of confusion there…
If you got 24x7 Scheduler Multi-platform (MP), you do not need 24x7 RA for Solaris or any other system. MP doesn't use them. MP is both a scheduler and an agent. If you use master.sh/master.bat to launch it, it will start in scheduler mode. If you use agent.sh/agent.bat to launch it, it will start in agent mode. As simple as that. Please uninstall 24x7 RA and Windows version of 24x7, to eliminate any further confusion
ftp conversation failed:500 'SITE FILETYPE = JES': command not understood That's because you are telling the MP that it is talking to an agent running on a mainframe system such as z/OS or OS/390 system. I doubt you are actually wanting that.
All you need is install the SAME piece of software on both Solaris and Windows machines. In case you would like to run it as an agent on Solaris, use ./agent.sh to start it. In case if you want to run it as a scheduler on Windows, use master.bat. If you want to do the opposite, use master.sh and agent.bat respectively. Hope this helps.
If we can be of any further assistance, or you are not sure how to configure or run this stuff, please don't hesitate to ask.
|
|
Tue Aug 12, 2008 9:33 am |
|
 |
dzafer
Joined: 11 Aug 2008 Posts: 5 Country: Belgium |
|
|
|
Hi,
Thank you, now it's clear (Maybe you need to add this kind of procedure/information somewhere on your website?)
On Solaris, I have started ./agent.sh nogui
When the job is started I receive now :
 |
 |
Remote Job Started
Agent "xxxx" contacted.
Remote job failed : exit code -1
|
Is there a way to have more info about the error?
Thank you
|
|
Tue Aug 12, 2008 11:26 am |
|
 |
SysOp
Site Admin
Joined: 26 Nov 2006 Posts: 7949
|
|
|
|
Hi, it is actually in the manual and the manual is available both on-line and preinstalled with the software :)
In regard to the error.
 |
 |
Remote job failed : exit code -1 |
What do you get for this job in the scheduler.log file on the agent side? Are there any additional details?
|
|
Tue Aug 12, 2008 11:43 am |
|
 |
dzafer
Joined: 11 Aug 2008 Posts: 5 Country: Belgium |
|
|
|
Hi there,
Please, I really need your assistance! No way to go away from the exit code -1
Here is the line in the scheduler.job
 |
 |
13-aug-2008 11:05:14 AM 3 null 6 dzafer Job completed with exit code -1. This exit code does not satisfy job exit code condition. Job failed. |
Here is the script
 |
 |
RAConnect ("172.31.105.52", 1096, "oracle10", "xxx")
Dim( process_id, number)
Dim( output, string)
RARunAndWait("mv /oracle10/test.txt /oracle10/data", 0, process_id, output);
RADisconnect
|
|
|
Wed Aug 13, 2008 5:25 am |
|
 |
SysOp
Site Admin
Joined: 26 Nov 2006 Posts: 7949
|
|
|
|
Hi, the script you are trying to execute is not good because of the following:
1. JAL script which is not supported in the Multi-platform version
2. Scripting is not required for the scheduler agent connectivity and running remote jobs.
In brief, you should configure a new remote agent profile in the scheduler. File / New / Remote agent menu. In the Job properties, on the "Security" step, select the name of the agent which you want to run the job. That's all.
Please read "Remote Agents and Remote Job" topic and related topics in the installed help file. This should help you to understand the concept, learn how to configure agent profiles and setup remote jobs.
Hope this helps.
|
|
Wed Aug 13, 2008 10:14 am |
|
 |
|