Must be doing something wrong...

Hello-

I am trying to get a Windows-based 24x7 4.0 instance to talk to a Linux instance of the same software (both in trial mode). I run the agent on Linux as root using all the defaults (port 1096, etc.). On the Windows machine, I try to set up a remote agent for the Linux machine; I put in the IP address of the Linux machine, port 1096, and try a test connect. I put in "root" as the username and its password (I've also tried other users on the Linux machine) and it responds simply with "Connect to remote host "<IP>" failed. Nothing is put in any log; the Linux box shows nothing, the Windows box shows nothing.

I can telnet to the linux machine on port 1096 and it connects, so the agent is listening on the port (and when I shut the agent down, telnet is refused, which is correct..the agent is not listening on the port anymore) so I don't know why the master is unable to connect. I've tried ignoring the test connect problem and create a job that uses the remote machine, and it continues to fail with "Remote Job Failed Exit Code: -1".

I've following the instructions in the manual to the letter and nothing. Am I missing something or is there some other special thing I need to check that I'm not aware of?

Thanks,

Ron

Sounds like an user authentication issue.

If you use PAM authentication method please verify that PAM is properly configured on the Unix machine so that 24x7 can ask the operation system to authenticate the specified user.

If you use FTP authentication method please verify ftpd server is running.

PAM is not being used. I do have an FTP server running on the Linux machine, and I am able to connect from the windows machine and log in as me with my password. When I try to do the test connect, however, it still fails.

By the way, nowhere in the documentation does it suggest an FTP server is required to run 24x7 Scheduler. Where is this documented?

If you run the agent in a graphical mode, please click Tools/Options menu then Log tab. Enable Tracing option and try connecting again. If you run it in non GUI mode, edit preferences.xml manually and change traceEnabled parameter from false to true then restart the agent.

Please post the resulting debug.log file here. The file can be found in 24x7 installation directory.

Here is the contents of the file for when I try to test the connection:

2007-05-22 17:14:16,276 [main] DEBUG com.softtreetech.jscheduler.JSchedulerStarter - main(...) : start

2007-05-22 17:14:16,276 [main] DEBUG com.softtreetech.jscheduler.JSchedulerStarter - startup() : start

2007-05-22 17:14:16,276 [main] DEBUG com.softtreetech.jscheduler.JSchedulerStarter - startup() : creating business objects

2007-05-22 17:14:16,667 [main] DEBUG com.softtreetech.jscheduler.JSchedulerStarter - startup() : creating UI controller

2007-05-22 17:14:17,104 [main] DEBUG com.softtreetech.jscheduler.JSchedulerStarter - startup() : initializing business objects

2007-05-22 17:14:17,136 [main] DEBUG com.softtreetech.jscheduler.business.preferences.AbstractPrefDatabase - Creating backup for preferences file preferences.xml

2007-05-22 17:14:17,151 [main] DEBUG com.softtreetech.jscheduler.business.preferences.AbstractPrefDatabase - Preferences file has been copied to preferences.bak

2007-05-22 17:14:17,417 [main] DEBUG com.softtreetech.jscheduler.business.jobtemplates.JobTemplateSetImpl - loadDescription: path: Template/test_template.ini

2007-05-22 17:14:18,620 [main] DEBUG com.softtreetech.jscheduler.db.drivers.file.FileJobDbStorage - buildIndex(): totalRecordsNumber: 6

2007-05-22 17:14:18,620 [main] DEBUG com.softtreetech.jscheduler.db.drivers.file.FileJobDbStorage - buildIndex(): deletedRecordsNumber: 0

2007-05-22 17:14:18,776 [main] DEBUG com.softtreetech.jscheduler.JSchedulerStarter - startup() : end

2007-05-22 17:14:18,776 [main] DEBUG com.softtreetech.jscheduler.JSchedulerStarter - main(...) : end

2007-05-22 17:14:40,571 [AWT-EventQueue-0] DEBUG com.softtreetech.jscheduler.business.agent.remote.AgentServerImpl - testConnection

java.rmi.ConnectException: Connection refused to host: ; nested exception is:
java.net.ConnectException: Connection refused: connect

at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:601)

at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:198)

at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:184)

at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:110)

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(AbstractButton.java:1995)

at javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2318)

at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:387)

at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:242)

at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(BasicButtonListener.java:236)

at java.awt.Component.processMouseEvent(Component.java:6038)

at javax.swing.JComponent.processMouseEvent(JComponent.java:3260)

at java.awt.Component.processEvent(Component.java:5803)

at java.awt.Container.processEvent(Container.java:2058)

at java.awt.Component.dispatchEventImpl(Component.java:4410)

at java.awt.Container.dispatchEventImpl(Container.java:2116)

at java.awt.Component.dispatchEvent(Component.java:4240)

at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4322)

at java.awt.LightweightDispatcher.processMouseEvent(Container.java:3986)

at java.awt.LightweightDispatcher.dispatchEvent(Container.java:3916)

at java.awt.Container.dispatchEventImpl(Container.java:2102)

at java.awt.Window.dispatchEventImpl(Window.java:2429)

at java.awt.Component.dispatchEvent(Component.java:4240)

at java.awt.EventQueue.dispatchEvent(EventQueue.java:599)

at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:273)

at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:183)

at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:177)

at java.awt.Dialog$1.run(Dialog.java:1039)

at java.awt.Dialog$3.run(Dialog.java:1091)

at java.security.AccessController.doPrivileged(Native Method)

at java.awt.Dialog.show(Dialog.java:1089)

at com.softtreetech.jscheduler.ui.ooOO.K.show(Unknown Source)

at java.awt.Component.show(Component.java:1419)

at java.awt.Component.setVisible(Component.java:1372)

at java.awt.Window.setVisible(Window.java:801)

at java.awt.Dialog.setVisible(Dialog.java:979)

at com.softtreetech.jscheduler.ui.ooOO.K.öÔO000(Unknown Source)

at com.softtreetech.jscheduler.ui.new.OooO$12.o00000(Unknown Source)

at com.softtreetech.jscheduler.ui.new.String.actionPerformed(Unknown Source)

at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1995)

at javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2318)

at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:387)

at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:242)

at javax.swing.AbstractButton.doClick(AbstractButton.java:357)

at javax.swing.plaf.basic.BasicMenuItemUI.doClick(BasicMenuItemUI.java:1170)

at javax.swing.plaf.basic.BasicMenuItemUI$Handler.mouseReleased(BasicMenuItemUI.java:1211)

at java.awt.Component.processMouseEvent(Component.java:6038)

at javax.swing.JComponent.processMouseEvent(JComponent.java:3260)

at java.awt.Component.processEvent(Component.java:5803)

at java.awt.Container.processEvent(Container.java:2058)

at java.awt.Component.dispatchEventImpl(Component.java:4410)

at java.awt.Container.dispatchEventImpl(Container.java:2116)

at java.awt.Component.dispatchEvent(Component.java:4240)

at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4322)

at java.awt.LightweightDispatcher.processMouseEvent(Container.java:3986)

at java.awt.LightweightDispatcher.dispatchEvent(Container.java:3916)

at java.awt.Container.dispatchEventImpl(Container.java:2102)

at java.awt.Window.dispatchEventImpl(Window.java:2429)

at java.awt.Component.dispatchEvent(Component.java:4240)

at java.awt.EventQueue.dispatchEvent(EventQueue.java:599)

at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:273)

at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:183)

at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:173)

at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:168)

at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:160)

at java.awt.EventDispatchThread.run(EventDispatchThread.java:121)

Caused by: java.net.ConnectException: Connection refused: connect

at java.net.PlainSocketImpl.socketConnect(Native Method)

at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)

at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)

at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)

at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)

at java.net.Socket.connect(Socket.java:519)

at java.net.Socket.connect(Socket.java:469)

at java.net.Socket.<init>(Socket.java:366)

at java.net.Socket.<init>(Socket.java:179)

at sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(RMIDirectSocketFactory.java:22)

at sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(RMIMasterSocketFactory.java:128)

at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:595)

... 67 more

This is the file from the computer from where you attempt to make a connection. But what about the debug.log file from the agent computer? Does it register any connection attempts? Please post that file.

No debug file was created on the remote computer. I verified that tracing was enabled on the Linux machine, but no debug file was ever generated.

Does the user running the agent have permissions for the directory and can create / write files in that directory? Who owns the directory?

By the way, did you restart the agent after turning the debug option on?

Root is the user running the agent, so it does have access to read and write. I did restart the agent after turning on tracing, and got this:

2007-05-22 16:15:04,930 [main] DEBUG com.softtreetech.jscheduler.JSchedulerStarter - main(...) : start
2007-05-22 16:15:04,931 [main] DEBUG com.softtreetech.jscheduler.JSchedulerStarter - startup() : start
2007-05-22 16:15:04,931 [main] DEBUG com.softtreetech.jscheduler.JSchedulerStarter - startup() : creating business objects
2007-05-22 16:15:04,980 [main] DEBUG com.softtreetech.jscheduler.JSchedulerStarter - startup() : creating UI controller
2007-05-22 16:15:05,150 [main] DEBUG com.softtreetech.jscheduler.JSchedulerStarter - startup() : initializing business objects
2007-05-22 16:15:05,186 [main] DEBUG com.softtreetech.jscheduler.business.preferences.AbstractPrefDatabase - Creating backup for preferences file preferences.xml
2007-05-22 16:15:05,189 [main] DEBUG com.softtreetech.jscheduler.business.preferences.AbstractPrefDatabase - Preferences file has been copied to preferences.bak
2007-05-22 16:15:08,973 [main] DEBUG com.softtreetech.jscheduler.JSchedulerStarter - startup() : end
2007-05-22 16:15:08,973 [main] DEBUG com.softtreetech.jscheduler.JSchedulerStarter - main(...) : end

That is the log file in its entirety.

Ok that's better. The log indicates so far that the agent doesn't register any connection attempts. Please try telnet on port 1096 and check what you get in the debug.log on the agent. Please let us know.

Note, if something new appears, but you don't get similar things when connecting from the scheduler then the scheduler connection is either blocked by a firewall, anitvirus or something like that, or you don't specify the correct port number in the remote agent profile on the scheduler side. The specified port number must be the same in agent's settings and in agent profile on the scheduler side.

I can telnet to the server on port 1096, but nothing appears in the log. On the remote machine it does connect when the agent is running and does not connect when the agent is not running. That tells me the agent is listening, but as I said, nothing gets written to the log.

I tried on the local Linux machine where the agent is running as well and got the same result....nothing in the log (telnet localhost 1096).

Please run "netstat -a" and check which process is listening on port 1096

rolson@24x7Test:~$ netstat -a | grep 1096
tcp 0 0 localhost:53561 localhost:1096 ESTABLISHED
tcp6 0 0 *:1096 *:* LISTEN
tcp6 0 0 localhost:1096 localhost:53561 ESTABLISHED

Sorry, you lost me.

This looks like you have a local to local connection already established, yet you say you cannot connect to the agent. Does it mean that you can connect locally but cannot connect fro ma different computer?

That was the result from netstat; I filtered it to just show the lines that were specific to port 1096.

I am able to run a test job using the master on the Linux machine, so the application is working locally.

I cannot connect remotely to the agent using the master on the Windows machine. But as I said in another message I am able to telnet to the Linux machine from the Windows machine on port 1096.