running job on remote agent

I have set up a script to run a perl job on a remote server. On the master i added the agent and tested the connection and it says test succeeded. When i use the gui to create a new job i point it to start in /home/batch/scripts and run command line /home/batch/scripts/file.pl and i have tried ,/file.pl and just file.pl . I made sure the user I running the program has permissions to execute the file and can run the program from the command line locally with the user I have set up for on the agent. I am getting FTP conversation failed 500 'SITE FILETYPE=jes 'not understood.

am i missing any documentation of error messages and explination as to cause of error? I couldnt find it in help.

What type/version of remote server are you using?

Im sorry if my descriptions are off. Its a Linux red hat box connecting to another Linux red hat box. I can get you the versions if you need them. The master is running Gui interface on one linxu box and the agent is running nogui on the other. I made sure the agent is running and it is. Do i have any configuration on the no gui to set up? Can you point me in the direction of some documentation on the nogui agent? commands, set up anything that would help?

The error message indicates an attempt to connect to a mainframe type agent. Do you have "Remote agent is running on Z/OS or OS/390" check box checked in the agent profile properties by any chance?

Is that a standalone Linux system or a hosted mainframe-based Linux subsystem?

ok that fixes that a little confusing that there is no radio button to select for linux but easy enough to remember after i have been told. Got it going program is working good but is there some documentation on errors that show up in the job log? and when i run agent.sh nogui on the linux box from shell i get the following. What i am i supposed to do next it takes the command line and doesnt respong after it tells me it started. doesnt repsong to anything i just ahve to close out of shell.

[jscheduler@www jscheduler]$ bash agent.sh nogui
This is a 30-day trial product. It may not be used for production purposes. (27 days left)
Copyright (c) 2006 SoftTree Technologies, Inc.
24x7 Scheduler started in agent mode.

Press Ctrl+C to abort

You didn't yet register the software. Stop the agent, start it in the GUI mode using ./master.sh and when prompted click the Register button and enter your license key into the opening. Close the scheduler, and restart the agent using ./agent.sh

There are exist other ways to enter the license key, but this is the simplest.

Well we dont have a gui interface on the linix boxes i will be running the agents on. We would like to run the agent nogui mode and I think is the last thing we need to test. If you could point me in the direction of how to register in nogui mode i would appreciate. I assumed the server team registered the software since it realized it has only 27 trial days left.

Two remaining options are:
1. Reinstall the agent and specify license key on the installer command line. As far as I remember the syntax is like
./setup.sh nogui [install path] [company name] [user name] [license key]

2. Temporarily install it on some other computer, for example, your Windows workstation, enter the license key as described in the previous post. After that copy the resulting "license" file to the agent computer to the 24x7 home directory. Uninstall the temporary copy to avoid license key conflicts.

Ok i just am hit one last speed bump. I am not sure what its looking for on the command line to run a job on a remote agent .I tested the connection but im sure you can see in the details it says the remote job started.
I keep getting

remote job started
Agent "testbox" connected
Remote job failed exit code -1

I have run the job from shell with the user i have set up and have tried the following commands. I am sure I have tried more but these are the last few i recorded. So you know when i SSH into the server i run perl -w test_emdeon_unzip.pl and the script runs.

/bin/sh -c "perl -w home/batch/scripts/test_emdeon_unzip.pl"
bash test_emdeon_unzip.pl
perl -w test_emdeon_unzip.pl
/bin/sh -c "test_emdeon_unzip.pl"
test_emdeon-unzip.pl

What do you get in the schedule.log file on the agent side?

5-Nov-2007 04:10:08 PM 2 null null 24x7 Scheduler 24x7 Remote Agent starting...

is that last thing logged and i have tried to run the job about a dozen times.

It looks like the user authentication fails. Normally. There would be a record like "User xxxxx connected from yyyyy. User authenticated successfully" or something like that. If you enable the tracing option in the preferences and restart the agent you can find more details in the debug.log file. Since you are running it as daemon process, no GUI, you can change this setting in the preferences.xml file directly. Find the text "traceEnabled" and in that line change the value "false" to "true" and then restart the agent.

I suspect that you left it to use the default FTP autnetication method and you either don't have ftpd running on the box or the user is not enabled for ftp and your FTP server fails the logon. If you don't want to use FTP as an authentication method, you can always switch to PAM.

Ftp is working i can use a terminal from the master to the agent box.
[jscheduler@cosbatch ~]$ ftp 192.168.208.163
Connected to 192.168.208.163.
220 ProFTPD 1.2.10 Server (IPAYX Test) [192.168.208.163]
500 AUTH not understood
500 AUTH not understood
KERBEROS_V4 rejected as an authentication type
Name (192.168.208.163:jscheduler): jscheduler
331 Password required for jscheduler.
Password:
230 User jscheduler logged in.
Remote system type is UNIX.
Using binary mode to transfer files.

I tried PAM as well and restarted the agent and master still nothing. And still nothing in the scheduler log other than showing me agent started again. Im lost

So what about the below messages
220 ProFTPD 1.2.10 Server (IPAYX Test) [192.168.208.163]
500 AUTH not understood
500 AUTH not understood
KERBEROS_V4 rejected as an authentication type

Anyway, your answer is in the agent's debug.log file. Please let us know what you get there when attempting to run a remote job.

exit code -1 good for anything. When we run the agent test we get something in the system messages when we actually run a job that is on the agent it never connects we dont even see an inbound connection from the server with the master on it.