You are viewing a plain text version of this content. The canonical link for it is here.
Posted to lokahi-dev@incubator.apache.org by ST...@symcor.com on 2008/03/05 22:36:18 UTC
Agent talk
I'm trying to get Lokahi working, but I seem to have a problem with the
agent. Whatever I do in the GUI (configtest, deploy, start, stop, etc.) it
doesn't appear to do anything.
Using Oracle (updated build.properties and lokahi.properties to use
Oracle), only a single Apache configured in a single hosting pool, all on
the same machine. The agent logs show nothing, I tried logging all
connections made to the agent port and found that there were none, so it
looks like the GUI isn't talking to the agent.
Any ideas what I should look for?
Thanks,
-Severn
RE: Agent talk
Posted by ST...@symcor.com.
Hmm, I applied the patch and it's still showing the velocity message when
it gets initialized (i.e. hit "deploy").
The names do match up. I tried shutting down tomcat, deleting the row in
the db and it got recreated exactly the same when I started it back up.
I've tracked it down furthur... it looks like in AdminBean, Oracle is
returning "???" for attr[0] and either ??? or null for attr[2] (so it's
never matching)... hrm...
-Severn
"Feist, Jeffrey" <je...@merck.com>
03/06/2008 02:08 PM
Please respond to
lokahi-dev@incubator.apache.org
To
lokahi-dev@incubator.apache.org
cc
Subject
RE: Agent talk
There is a patch for that velocity message on the Jira page. (See my
post on 29/Feb/08 07:56 AM)
You are right about the primary JVM. The jobs will only send when there
is a primary JVM. In your build.properties file, does your "Initial
Instance Name" match up to the instance that the hardware is on?
If you delete that whole row in the TMC_Admin table, it should
automatically repopulate. Try that and see if it puts the test1 JVM into
the primary spot.
-----Original Message-----
From: STsui@symcor.com [mailto:STsui@symcor.com]
Sent: Thursday, March 06, 2008 12:10 PM
To: lokahi-dev@incubator.apache.org
Subject: RE: Agent talk
The jobs stay in the "New" state.
The only exception I see is:
[03/06/2008 09:33:32.348] [INFO ] [SimpleLog4JLogSystem.java:137]
[org.apache.velocity.runtime.log.SimpleLog4JLogSystem::logVelocityMessag
e]
Velocimacro : error using VM library template VM_global_library.vm :
org.apache.velocity.exception.ResourceNotFoundException: Unable to find
resource 'VM_global_library.vm'
which looks non-critical... I don't see sendRequest anywhere in the
logs.
It looks like it adds it to the job pool but doesn't connect out.
I can get a page when I go to http://host:5665/mod_soap
--
I think it might have something to do with this:
[03/06/2008 12:07:49.324] [DEBUG] [CheckJvmThread.java:346]
[org.apache.lokahi.core.controller.CheckJvmThread::isPrimary]
myTomcatWorker=test1:8008
[03/06/2008 12:07:49.325] [DEBUG] [CheckJvmThread.java:347]
[org.apache.lokahi.core.controller.CheckJvmThread::isPrimary]
primaryTomcatWorker=
[03/06/2008 12:07:49.325] [DEBUG] [CheckJvmThread.java:348]
[org.apache.lokahi.core.controller.CheckJvmThread::isPrimary]
backupTomcatWorker=
[03/06/2008 12:07:49.326] [DEBUG] [CheckJvmThread.java:349]
[org.apache.lokahi.core.controller.CheckJvmThread::isPrimary]
alternateTomcatWorkers=
[03/06/2008 12:07:49.367] [DEBUG] [CheckJvmThread.java:403]
[org.apache.lokahi.core.controller.CheckJvmThread::isPrimary]
runThread=true
[03/06/2008 12:07:49.368] [DEBUG] [CheckJvmThread.java:404]
[org.apache.lokahi.core.controller.CheckJvmThread::isPrimary] Returning
false
The TMC_ADMIN table has ALTERNATE_JVM=test1:8008, INSTANCE_ID=1, and
everything else NULL
-Severn
"Feist, Jeffrey" <je...@merck.com>
03/06/2008 08:41 AM
Please respond to
lokahi-dev@incubator.apache.org
To
lokahi-dev@incubator.apache.org
cc
Subject
RE: Agent talk
Do the jobs stay in the "New" state or do they make it to "Running"?
If you view the lokahi_log4j.log, do a search for the hardware name that
you are sending the job to. You should see something like
"org.apache.lokahi.core.api.job.Job::sendRequest] Sending job" and then
something like "SENDING JOB!!!!!!". Do you get any exceptions or
connection refused messages?
You should also see the agent's URL in the logs. It will appear as
params[0]=http://<servername>:5665/mod_soap. Are you able to hit this
URL in a browser?
Finally, I always do a search in the logs for "Exception" to see if
there is an issue somewhere.
Good luck!
-Jeff
-----Original Message-----
From: STsui@symcor.com [mailto:STsui@symcor.com]
Sent: Wednesday, March 05, 2008 5:36 PM
To: lokahi-dev@incubator.apache.org
Subject: Agent talk
I'm trying to get Lokahi working, but I seem to have a problem with the
agent. Whatever I do in the GUI (configtest, deploy, start, stop, etc.)
it
doesn't appear to do anything.
Using Oracle (updated build.properties and lokahi.properties to use
Oracle), only a single Apache configured in a single hosting pool, all
on
the same machine. The agent logs show nothing, I tried logging all
connections made to the agent port and found that there were none, so it
looks like the GUI isn't talking to the agent.
Any ideas what I should look for?
Thanks,
-Severn
------------------------------------------------------------------------
------
Notice: This e-mail message, together with any attachments, contains
information of Merck & Co., Inc. (One Merck Drive, Whitehouse Station,
New Jersey, USA 08889), and/or its affiliates (which may be known
outside the United States as Merck Frosst, Merck Sharp & Dohme or MSD
and in Japan, as Banyu - direct contact information for affiliates is
available at http://www.merck.com/contact/contacts.html) that may be
confidential, proprietary copyrighted and/or legally privileged. It is
intended solely for the use of the individual or entity named on this
message. If you are not the intended recipient, and have received this
message in error, please notify us immediately by reply e-mail and then
delete it from your system.
------------------------------------------------------------------------
------
------------------------------------------------------------------------------
Notice: This e-mail message, together with any attachments, contains
information of Merck & Co., Inc. (One Merck Drive, Whitehouse Station,
New Jersey, USA 08889), and/or its affiliates (which may be known
outside the United States as Merck Frosst, Merck Sharp & Dohme or MSD
and in Japan, as Banyu - direct contact information for affiliates is
available at http://www.merck.com/contact/contacts.html) that may be
confidential, proprietary copyrighted and/or legally privileged. It is
intended solely for the use of the individual or entity named on this
message. If you are not the intended recipient, and have received this
message in error, please notify us immediately by reply e-mail and then
delete it from your system.
------------------------------------------------------------------------------
RE: Agent talk
Posted by "Feist, Jeffrey" <je...@merck.com>.
There is a patch for that velocity message on the Jira page. (See my
post on 29/Feb/08 07:56 AM)
You are right about the primary JVM. The jobs will only send when there
is a primary JVM. In your build.properties file, does your "Initial
Instance Name" match up to the instance that the hardware is on?
If you delete that whole row in the TMC_Admin table, it should
automatically repopulate. Try that and see if it puts the test1 JVM into
the primary spot.
-----Original Message-----
From: STsui@symcor.com [mailto:STsui@symcor.com]
Sent: Thursday, March 06, 2008 12:10 PM
To: lokahi-dev@incubator.apache.org
Subject: RE: Agent talk
The jobs stay in the "New" state.
The only exception I see is:
[03/06/2008 09:33:32.348] [INFO ] [SimpleLog4JLogSystem.java:137]
[org.apache.velocity.runtime.log.SimpleLog4JLogSystem::logVelocityMessag
e]
Velocimacro : error using VM library template VM_global_library.vm :
org.apache.velocity.exception.ResourceNotFoundException: Unable to find
resource 'VM_global_library.vm'
which looks non-critical... I don't see sendRequest anywhere in the
logs.
It looks like it adds it to the job pool but doesn't connect out.
I can get a page when I go to http://host:5665/mod_soap
--
I think it might have something to do with this:
[03/06/2008 12:07:49.324] [DEBUG] [CheckJvmThread.java:346]
[org.apache.lokahi.core.controller.CheckJvmThread::isPrimary]
myTomcatWorker=test1:8008
[03/06/2008 12:07:49.325] [DEBUG] [CheckJvmThread.java:347]
[org.apache.lokahi.core.controller.CheckJvmThread::isPrimary]
primaryTomcatWorker=
[03/06/2008 12:07:49.325] [DEBUG] [CheckJvmThread.java:348]
[org.apache.lokahi.core.controller.CheckJvmThread::isPrimary]
backupTomcatWorker=
[03/06/2008 12:07:49.326] [DEBUG] [CheckJvmThread.java:349]
[org.apache.lokahi.core.controller.CheckJvmThread::isPrimary]
alternateTomcatWorkers=
[03/06/2008 12:07:49.367] [DEBUG] [CheckJvmThread.java:403]
[org.apache.lokahi.core.controller.CheckJvmThread::isPrimary]
runThread=true
[03/06/2008 12:07:49.368] [DEBUG] [CheckJvmThread.java:404]
[org.apache.lokahi.core.controller.CheckJvmThread::isPrimary] Returning
false
The TMC_ADMIN table has ALTERNATE_JVM=test1:8008, INSTANCE_ID=1, and
everything else NULL
-Severn
"Feist, Jeffrey" <je...@merck.com>
03/06/2008 08:41 AM
Please respond to
lokahi-dev@incubator.apache.org
To
lokahi-dev@incubator.apache.org
cc
Subject
RE: Agent talk
Do the jobs stay in the "New" state or do they make it to "Running"?
If you view the lokahi_log4j.log, do a search for the hardware name that
you are sending the job to. You should see something like
"org.apache.lokahi.core.api.job.Job::sendRequest] Sending job" and then
something like "SENDING JOB!!!!!!". Do you get any exceptions or
connection refused messages?
You should also see the agent's URL in the logs. It will appear as
params[0]=http://<servername>:5665/mod_soap. Are you able to hit this
URL in a browser?
Finally, I always do a search in the logs for "Exception" to see if
there is an issue somewhere.
Good luck!
-Jeff
-----Original Message-----
From: STsui@symcor.com [mailto:STsui@symcor.com]
Sent: Wednesday, March 05, 2008 5:36 PM
To: lokahi-dev@incubator.apache.org
Subject: Agent talk
I'm trying to get Lokahi working, but I seem to have a problem with the
agent. Whatever I do in the GUI (configtest, deploy, start, stop, etc.)
it
doesn't appear to do anything.
Using Oracle (updated build.properties and lokahi.properties to use
Oracle), only a single Apache configured in a single hosting pool, all
on
the same machine. The agent logs show nothing, I tried logging all
connections made to the agent port and found that there were none, so it
looks like the GUI isn't talking to the agent.
Any ideas what I should look for?
Thanks,
-Severn
------------------------------------------------------------------------
------
Notice: This e-mail message, together with any attachments, contains
information of Merck & Co., Inc. (One Merck Drive, Whitehouse Station,
New Jersey, USA 08889), and/or its affiliates (which may be known
outside the United States as Merck Frosst, Merck Sharp & Dohme or MSD
and in Japan, as Banyu - direct contact information for affiliates is
available at http://www.merck.com/contact/contacts.html) that may be
confidential, proprietary copyrighted and/or legally privileged. It is
intended solely for the use of the individual or entity named on this
message. If you are not the intended recipient, and have received this
message in error, please notify us immediately by reply e-mail and then
delete it from your system.
------------------------------------------------------------------------
------
------------------------------------------------------------------------------
Notice: This e-mail message, together with any attachments, contains
information of Merck & Co., Inc. (One Merck Drive, Whitehouse Station,
New Jersey, USA 08889), and/or its affiliates (which may be known
outside the United States as Merck Frosst, Merck Sharp & Dohme or MSD
and in Japan, as Banyu - direct contact information for affiliates is
available at http://www.merck.com/contact/contacts.html) that may be
confidential, proprietary copyrighted and/or legally privileged. It is
intended solely for the use of the individual or entity named on this
message. If you are not the intended recipient, and have received this
message in error, please notify us immediately by reply e-mail and then
delete it from your system.
------------------------------------------------------------------------------
RE: Agent talk
Posted by ST...@symcor.com.
The jobs stay in the "New" state.
The only exception I see is:
[03/06/2008 09:33:32.348] [INFO ] [SimpleLog4JLogSystem.java:137]
[org.apache.velocity.runtime.log.SimpleLog4JLogSystem::logVelocityMessage]
Velocimacro : error using VM library template VM_global_library.vm :
org.apache.velocity.exception.ResourceNotFoundException: Unable to find
resource 'VM_global_library.vm'
which looks non-critical... I don't see sendRequest anywhere in the logs.
It looks like it adds it to the job pool but doesn't connect out.
I can get a page when I go to http://host:5665/mod_soap
--
I think it might have something to do with this:
[03/06/2008 12:07:49.324] [DEBUG] [CheckJvmThread.java:346]
[org.apache.lokahi.core.controller.CheckJvmThread::isPrimary]
myTomcatWorker=test1:8008
[03/06/2008 12:07:49.325] [DEBUG] [CheckJvmThread.java:347]
[org.apache.lokahi.core.controller.CheckJvmThread::isPrimary]
primaryTomcatWorker=
[03/06/2008 12:07:49.325] [DEBUG] [CheckJvmThread.java:348]
[org.apache.lokahi.core.controller.CheckJvmThread::isPrimary]
backupTomcatWorker=
[03/06/2008 12:07:49.326] [DEBUG] [CheckJvmThread.java:349]
[org.apache.lokahi.core.controller.CheckJvmThread::isPrimary]
alternateTomcatWorkers=
[03/06/2008 12:07:49.367] [DEBUG] [CheckJvmThread.java:403]
[org.apache.lokahi.core.controller.CheckJvmThread::isPrimary]
runThread=true
[03/06/2008 12:07:49.368] [DEBUG] [CheckJvmThread.java:404]
[org.apache.lokahi.core.controller.CheckJvmThread::isPrimary] Returning
false
The TMC_ADMIN table has ALTERNATE_JVM=test1:8008, INSTANCE_ID=1, and
everything else NULL
-Severn
"Feist, Jeffrey" <je...@merck.com>
03/06/2008 08:41 AM
Please respond to
lokahi-dev@incubator.apache.org
To
lokahi-dev@incubator.apache.org
cc
Subject
RE: Agent talk
Do the jobs stay in the "New" state or do they make it to "Running"?
If you view the lokahi_log4j.log, do a search for the hardware name that
you are sending the job to. You should see something like
"org.apache.lokahi.core.api.job.Job::sendRequest] Sending job" and then
something like "SENDING JOB!!!!!!". Do you get any exceptions or
connection refused messages?
You should also see the agent's URL in the logs. It will appear as
params[0]=http://<servername>:5665/mod_soap. Are you able to hit this
URL in a browser?
Finally, I always do a search in the logs for "Exception" to see if
there is an issue somewhere.
Good luck!
-Jeff
-----Original Message-----
From: STsui@symcor.com [mailto:STsui@symcor.com]
Sent: Wednesday, March 05, 2008 5:36 PM
To: lokahi-dev@incubator.apache.org
Subject: Agent talk
I'm trying to get Lokahi working, but I seem to have a problem with the
agent. Whatever I do in the GUI (configtest, deploy, start, stop, etc.)
it
doesn't appear to do anything.
Using Oracle (updated build.properties and lokahi.properties to use
Oracle), only a single Apache configured in a single hosting pool, all
on
the same machine. The agent logs show nothing, I tried logging all
connections made to the agent port and found that there were none, so it
looks like the GUI isn't talking to the agent.
Any ideas what I should look for?
Thanks,
-Severn
------------------------------------------------------------------------------
Notice: This e-mail message, together with any attachments, contains
information of Merck & Co., Inc. (One Merck Drive, Whitehouse Station,
New Jersey, USA 08889), and/or its affiliates (which may be known
outside the United States as Merck Frosst, Merck Sharp & Dohme or MSD
and in Japan, as Banyu - direct contact information for affiliates is
available at http://www.merck.com/contact/contacts.html) that may be
confidential, proprietary copyrighted and/or legally privileged. It is
intended solely for the use of the individual or entity named on this
message. If you are not the intended recipient, and have received this
message in error, please notify us immediately by reply e-mail and then
delete it from your system.
------------------------------------------------------------------------------
RE: Agent talk
Posted by "Feist, Jeffrey" <je...@merck.com>.
Do the jobs stay in the "New" state or do they make it to "Running"?
If you view the lokahi_log4j.log, do a search for the hardware name that
you are sending the job to. You should see something like
"org.apache.lokahi.core.api.job.Job::sendRequest] Sending job" and then
something like "SENDING JOB!!!!!!". Do you get any exceptions or
connection refused messages?
You should also see the agent's URL in the logs. It will appear as
params[0]=http://<servername>:5665/mod_soap. Are you able to hit this
URL in a browser?
Finally, I always do a search in the logs for "Exception" to see if
there is an issue somewhere.
Good luck!
-Jeff
-----Original Message-----
From: STsui@symcor.com [mailto:STsui@symcor.com]
Sent: Wednesday, March 05, 2008 5:36 PM
To: lokahi-dev@incubator.apache.org
Subject: Agent talk
I'm trying to get Lokahi working, but I seem to have a problem with the
agent. Whatever I do in the GUI (configtest, deploy, start, stop, etc.)
it
doesn't appear to do anything.
Using Oracle (updated build.properties and lokahi.properties to use
Oracle), only a single Apache configured in a single hosting pool, all
on
the same machine. The agent logs show nothing, I tried logging all
connections made to the agent port and found that there were none, so it
looks like the GUI isn't talking to the agent.
Any ideas what I should look for?
Thanks,
-Severn
------------------------------------------------------------------------------
Notice: This e-mail message, together with any attachments, contains
information of Merck & Co., Inc. (One Merck Drive, Whitehouse Station,
New Jersey, USA 08889), and/or its affiliates (which may be known
outside the United States as Merck Frosst, Merck Sharp & Dohme or MSD
and in Japan, as Banyu - direct contact information for affiliates is
available at http://www.merck.com/contact/contacts.html) that may be
confidential, proprietary copyrighted and/or legally privileged. It is
intended solely for the use of the individual or entity named on this
message. If you are not the intended recipient, and have received this
message in error, please notify us immediately by reply e-mail and then
delete it from your system.
------------------------------------------------------------------------------