Linux 64 bit

Can we get support for 64 bit Linux? Contrcted or via phone. I have been told it should run on 64 bit linux but we cannot get it to. If we check the z/os or os 390 the test connection function respond but it cannot run a script because you get the JES filetype error. If we uncheck the z/os box it never authenticates the user at all (test connection function fails)We have spent days trying to get it to run on 64 bit platform Linux.

Simple enough to figure out why the test connection was working with z/os selected, it doesnt check port 1096 or use the java application to authenticate it just uses ftp port 21 doesnt even care if agent is running. We think its how the program is written that is having the problem with 64 bit Linux. Since it uses 1096 port to test connection and the agent is listening on 1096. We wonder if maybe the agent doesnt know how to handle the FTP daemon on 64 bit linux to allow it to authenticate. The Agent starts and runs fine on the 64 bit but, the master cannot communicate with it. We think have ruled out just about every possible scenario on our end that could be casuing the problems. We even went as far as to write a program that would use Java to listen on port 1096 so we could make sure the Master was getting to where it needed to be. We would really like to work woth someone to get 64 bit Linux to work as we see this as our future and I am sure many other clients will as well.
thanks-Will

In order to help you need to know several things. Please answer a the following questions:

1. Please describe what kind of job you want to run - this will help me to figure out what kind of agent you need to install on z/OS, if any. It can use strait FTP extensions available on z/OS to run jobs remotely or it can use an agent. I will help you with that when I know what you got there.
2. Do you have/run 24x7 on z/OS using 64-bit JDK/JRE v1.4 or some other version?
3. Do you run it in Linux subsystem or z/OS? If Linux, which flavor?

We are not running z/OS we have Red Hat 4 in 64 bit. I just mentioned that it connected when we selected z/OS but thats because z/OS just uses port 21 and FTP to test the connection. It never uses port 1096 or Java to authenticate the user like the linux version does.
1. We are running a command line that launches a PHP script
2.We are running it on Red Hat 4 but there is no 64 bit distribution of the Java you state to use in the manual. We are using the 32 bit distro.
3. Linux Red Hat 4 64 bit, we have it running on Red Hat 4 32 bit and it works fine its just the way Java and the program are working on the 64 bit platform that gives us issues.

Like i mentioned below it appears to be the way the program calls Java on the 64 bit version. We wrote a small program that listens on port 1096 and then sent a test connection from the master. It was received on 1096. When we start the agent up and send a test connection it dies. The agent doesnt record anything in the messages or FTP log on the system and the log files for the scheduler program has nothing in them. We are guessing the scheduler program doesnt know how to handle the ftp daemon on the 64 bit platform so it cannot authenticate. We have treid to use just PAM authentication as well and still nothing.

Thanks for the info. I think I now get it.

1. You cannot use PAM authentication method because of the 32-bit / 64-bit mismatch, but you should be able to use FTP based authentication. FTP authentication simple attempts to pen a local FTP connection using the specified user and password. It doesn't really matter if the FTP server and client have same code base or not.

2. I believe 64-bit Java is available for Red-hat for quite a while. I think Sun provides a version for Intel Itanium system and IBM offers a version for x86.

Anyway, as long as you can run it using 32-bit Java variant, you should be ok.

3. The most likely reason for the agent dying when receiving a connection, is use of wrong Java version. I don't mean 32-bit or 64-bit version. I mean release number. Please note that 1.5 and 1.6 are not backward compatible. 24x7 code has been compiled using 1.4 and it rarely works with more recent JREs

PS. We are working on porting 24x7 to JDK 1.6. I don't have an exact date when it will be available, likely in 2 to 3 months.

1. Well what you say about using using FTP is what we thought as well but i dont think thats the way its reacting for us. I think it still connectes to the java agent on port 1096 and the the agent application calls the FTP daemon to authenticate. If you turn the agent off and try ftp as method and test connection it doesnt work on 64 bit on 32 bit.

2. I will look into that maybe it will remedy our issue. The 32 bit version using the 64 bit libraries runs the agent just doesnt let agent and master communicate. I know we should be ok using 32 bit but we have done some very extensive testing and it will not work.

3. We definitely are using the 1.4 vesrion of Java and not the packaged version that comes with Red HAt the actual downlaod from Sun.

Its very good to hear that its is going to be ported to 1.6 since i have read that sun will not support 1.4 in about 6 months. I will try to find a 64bit distro like you mentioned in answer two and post results.

1. That's what I mean. The agent is responsible for the authentication and it is the agent that uses local FTP daemon or server to authenticate users with the system.
Do you get anything interesting in syslog when this authentication fails?
If there is not match data to analyze and not much log entries to see what is going on, please try using tcpdump to capture all traffic on FTP port 21 for the agent computer. In the captured traffic log you should be able to see where it doesn't click.

2. "32 bit version using the 64 bit libraries" What did you mean by that?

3. 1.6 is not available on all systems, while 1.4 is available virtually everywhere.

1.The logs are empty and we did try a TCP capture and see the agent answer on 1096 but nothing after that no messages. errors or response of any type. Unfortunitely Java is handleing the request at the application layer and just fails. The TCPdump shows the packet getting to the agent. Java app never initiates FTP daemon and if it does it isnt recording it anywhwere we can find.

2. I just mean we installed the 32 bit 1.4 Java on a 64 bit Linux box. Since the system is 64 bit the 32 bit install has to use the 64 bit. It starts we can even use the gui it just drop the request when we try to communicate with it.

3. I understand just we are in a pickle because we are not in the virtually everywhere you speak of. If i could get 1.4 to work on 64 bit an updated version wouldnt concern me.

Which JDK/JRE distribution are you using?

Do you have tracing enabled in the agent? I mean, is the trace enabled flag set to true in the preferences.xml file If not, please set it and restart the agent. After running a test session, please email the resulting debug.log file to our support email account.

sorry if any confusion on the emails the first email from me has the debug log from the master running in nogui mode on the 64 bit box. the second email please ignore it was from a computer trying to connect to the 64 bit box but didnt have the firewall opened for ports needed. the thirds email is the debug log for the remote computer trying to connect to the master on the 64 bit box. And to answer you question yes trace is turned on and we are using j2sdk1.4.2_15

Could you please update me on the debug.log? What are you getting there? Can you post relevant fragment of the log with entries related to the connection (around time of connection attempt)? Please note that normally there will be nothing added to the log related to the connection until user has been authenticated, unless some exceptions occur and the user cannot be authenticated for whatever reason. So I am looking for exceptions and stack trace records in the log to figure out where and why this process breaks.

PS. I want to stress again that the issue is not 32-bit to 64-bit communication. It is something on the agent side that makes it not to authenticate the user.

2008-03-03 09:55:19,406 [AWT-EventQueue-0] DEBUG com.softtreetech.jscheduler.business.agent.remote.AgentServerImpl - testConnection
java.rmi.NoSuchObjectException: no such object in table
at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(Unknown Source)
at sun.rmi.transport.StreamRemoteCall.executeCall(Unknown Source)
at sun.rmi.server.UnicastRef.invoke(Unknown Source)
at com.softtreetech.jscheduler.business.agent.remote.RemoteAgentImpl_Stub.checkLicense(Unknown Source)
at com.softtreetech.jscheduler.business.agent.remote.AgentServerImpl.testConnection(Unknown Source)
at com.softtreetech.jscheduler.ui.ooOO.K$4.actionPerformed(Unknown Source)
at javax.swing.AbstractButton.fireActionPerformed(Unknown Source)
at javax.swing.AbstractButton$Handler.actionPerformed(Unknown Source)
at javax.swing.DefaultButtonModel.fireActionPerformed(Unknown Source)
at javax.swing.DefaultButtonModel.setPressed(Unknown Source)
at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(Unknown Source)
at java.awt.Component.processMouseEvent(Unknown Source)
at javax.swing.JComponent.processMouseEvent(Unknown Source)
at java.awt.Component.processEvent(Unknown Source)
at java.awt.Container.processEvent(Unknown Source)
at java.awt.Component.dispatchEventImpl(Unknown Source)
at java.awt.Container.dispatchEventImpl(Unknown Source)
at java.awt.Component.dispatchEvent(Unknown Source)
at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source)
at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source)
at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source)
at java.awt.Container.dispatchEventImpl(Unknown Source)
at java.awt.Window.dispatchEventImpl(Unknown Source)
at java.awt.Component.dispatchEvent(Unknown Source)
at java.awt.EventQueue.dispatchEvent(Unknown Source)
at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
at java.awt.Dialog$1.run(Unknown Source)
at java.awt.Dialog$3.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at java.awt.Dialog.show(Unknown Source)
at com.softtreetech.jscheduler.ui.ooOO.K.show(Unknown Source)
at java.awt.Component.show(Unknown Source)
at java.awt.Component.setVisible(Unknown Source)
at java.awt.Window.setVisible(Unknown Source)
at java.awt.Dialog.setVisible(Unknown Source)
at com.softtreetech.jscheduler.ui.ooOO.K.while.for(Unknown Source)
at com.softtreetech.jscheduler.ui.OoOO.H$12.super(Unknown Source)
at com.softtreetech.jscheduler.ui.OoOO.O0OO.actionPerformed(Unknown Source)
at com.softtreetech.jscheduler.ui.OOoOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO$4.mousePressed(Unknown Source)
at java.awt.AWTEventMulticaster.mousePressed(Unknown Source)
at java.awt.Component.processMouseEvent(Unknown Source)
at javax.swing.JComponent.processMouseEvent(Unknown Source)
at java.awt.Component.processEvent(Unknown Source)
at java.awt.Container.processEvent(Unknown Source)
at java.awt.Component.dispatchEventImpl(Unknown Source)
at java.awt.Container.dispatchEventImpl(Unknown Source)
at java.awt.Component.dispatchEvent(Unknown Source)
at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source)
at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source)
at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source)
at java.awt.Container.dispatchEventImpl(Unknown Source)
at java.awt.Window.dispatchEventImpl(Unknown Source)
at java.awt.Component.dispatchEvent(Unknown Source)
at java.awt.EventQueue.dispatchEvent(Unknown Source)
at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.run(Unknown Source)

2008-03-03 09:24:29,750 [main] DEBUG com.softtreetech.jscheduler.JSchedulerStarter - main(...) : start
2008-03-03 09:24:29,751 [main] DEBUG com.softtreetech.jscheduler.JSchedulerStarter - startup() : start
2008-03-03 09:24:29,754 [main] DEBUG com.softtreetech.jscheduler.JSchedulerStarter - startup() : creating business objects
2008-03-03 09:24:30,106 [main] DEBUG com.softtreetech.jscheduler.JSchedulerStarter - startup() : creating UI controller
2008-03-03 09:24:30,244 [main] DEBUG com.softtreetech.jscheduler.JSchedulerStarter - startup() : initializing business objects
2008-03-03 09:24:30,249 [main] DEBUG com.softtreetech.jscheduler.business.preferences.AbstractPrefDatabase - Creating backup for preferences file preferences.xml
2008-03-03 09:24:30,250 [main] DEBUG com.softtreetech.jscheduler.business.preferences.AbstractPrefDatabase - Preferences file has been copied to preferences.bak
2008-03-03 09:24:30,450 [main] DEBUG com.softtreetech.jscheduler.business.jobtemplates.JobTemplateSetImpl - loadDescription: path: Template/test_template.ini
2008-03-03 09:24:30,492 [main] DEBUG com.softtreetech.jscheduler.JSchedulerStarter - startup() : loading job db
2008-03-03 09:24:30,536 [main] DEBUG com.softtreetech.jscheduler.db.drivers.file.FileJobDbStorage - buildIndex(): totalRecordsNumber: 5
2008-03-03 09:24:30,537 [main] DEBUG com.softtreetech.jscheduler.db.drivers.file.FileJobDbStorage - buildIndex(): deletedRecordsNumber: 0
2008-03-03 09:24:30,567 [main] DEBUG com.softtreetech.jscheduler.db.drivers.file.FileJobDbStorage - save() : start
2008-03-03 09:24:30,568 [main] DEBUG com.softtreetech.jscheduler.db.drivers.file.FileJobDbStorage - isRequirePurge(): totalRecordsNumber: 5
2008-03-03 09:24:30,568 [main] DEBUG com.softtreetech.jscheduler.db.drivers.file.FileJobDbStorage - isRequirePurge(): deletedRecordsNumber: 0
2008-03-03 09:24:30,568 [main] DEBUG com.softtreetech.jscheduler.db.drivers.file.FileJobDbStorage - isRequirePurge(): result: false
2008-03-03 09:24:30,568 [main] DEBUG com.softtreetech.jscheduler.db.drivers.file.FileJobDbStorage - save() : total modifications : 5
2008-03-03 09:24:30,574 [main] DEBUG com.softtreetech.jscheduler.db.drivers.file.FileJobDbStorage - save() : end
2008-03-03 09:24:30,576 [main] DEBUG com.softtreetech.jscheduler.db.drivers.file.FileJobDbStorage - buildIndex(): totalRecordsNumber: 5
2008-03-03 09:24:30,576 [main] DEBUG com.softtreetech.jscheduler.db.drivers.file.FileJobDbStorage - buildIndex(): deletedRecordsNumber: 0
2008-03-03 09:24:30,604 [main] DEBUG com.softtreetech.jscheduler.JSchedulerStarter - startup() : ready to run jobs
2008-03-03 09:26:02,501 [Thread-9] DEBUG com.softtreetech.jscheduler.business.remotecontrol.SocketConnection - requestId 1
2008-03-03 09:26:02,507 [Thread-4] DEBUG com.softtreetech.jscheduler.business.remotecontrol.RemoteOperationsImpl - Connect called jscheduler _JAVA_ *****
2008-03-03 09:26:02,571 [Thread-9] DEBUG com.softtreetech.jscheduler.business.remotecontrol.SocketConnection - requestId 3
2008-03-03 09:26:02,653 [Thread-9] DEBUG com.softtreetech.jscheduler.business.remotecontrol.SocketConnection - requestId 6
2008-03-03 09:26:02,653 [Thread-9] DEBUG com.softtreetech.jscheduler.business.remotecontrol.SocketConnection - Method name opensession
2008-03-03 09:26:02,653 [Thread-9] DEBUG com.softtreetech.jscheduler.business.remotecontrol.SocketConnection - methodSignature LSSSS
2008-03-03 09:26:02,653 [Thread-9] DEBUG com.softtreetech.jscheduler.business.remotecontrol.SocketConnection - arguments 4
2008-03-03 09:26:02,654 [Thread-9] DEBUG com.softtreetech.jscheduler.business.remotecontrol.SocketConnection - method params [24x7 Java API, jscheduler, LinuxRocks42, *****]
2008-03-03 09:26:02,654 [Thread-5] DEBUG com.softtreetech.jscheduler.business.remotecontrol.RemoteOperationsImpl - Open session called 24x7 Java API jscheduler
2008-03-03 09:26:02,654 [Thread-5] DEBUG com.softtreetech.jscheduler.business.runner.security.SecurityService - hasRemoteControlAccess: /home/jscheduler/24x7_Scheduler/rcontrol.pl
2008-03-03 09:26:02,693 [Thread-5] DEBUG com.softtreetech.jscheduler.business.runner.security.SecurityService - authNativeUser: jscheduler login ok

keep in mind the authentication you see is me using the command line (cons.sh) to connect to the master running with distributed server mode and remote control enabled. So i am testing local not over network.

Last edited by wmweaver2 on Mon Mar 03, 2008 12:37 pm; edited 2 times in total

we completely respect your take thats its not a 64 bit to 32 bit issue. I am just letting you know that it works just fine on any 32 bit linux platform we have running and wont authenticate on any of the 3 64 bit Linux servers. They are all on the same network and it seemed very odd to our network and development teams so i thought I should bring it to softtree supports attention.

It could be just a license issue. How did you install the software? Did you copy all files from a different system? Are you sure that the agent is using a unique license key?