topic Re: Server monitor - log4j:WARN No appenders could be found for logger in AppD Archive

Server monitor - log4j:WARN No appenders could be found for logger

CommunityUser — Fri, 10 Jul 2015 15:45:05 GMT

I'm trying to set up server monitoring on aws amazon linux following the steps from appdynamics. I get this error message and then the agent hangs. The only instructions provided are to run the agent. Am I missing a set here?

$ sudo java -jar app-dynamics/machineagent.jar

Using Java Version [1.7.0_79] for Agent

Using Agent Version [Machine Agent v4.1.0.1 GA Build Date 2015-06-24 13:28:57]
log4j:WARN No appenders could be found for logger (com.appdynamics.voltron.FrameworkBootstrap).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.
[Machine Agent] Resolved install dir location :/home/ec2-user/app-dynamics
Machine Agent Install Directory :/home/ec2-user/app-dynamics
Machine Agent Temp Directory :/home/ec2-user/app-dynamics/tmp
Tasks Root Directory :/home/ec2-user/app-dynamics/controlchannel
Logger Configuration :/home/ec2-user/app-dynamics/conf/logging/log4j.xml
Redirecting all logging statements to the configured logger
[Machine Agent] Resolved install dir location :/home/ec2-user/app-dynamics

Re: Server monitor - log4j:WARN No appenders could be found for logger

Arun_Dasetty — Mon, 13 Jul 2015 14:11:37 GMT

Hi Dane,

Given that you have not modified /home/ec2-user/app-dynamics/conf/logging/log4j.xml and your machine agent regsitered fine at contorller UI (as per controller-info.xml at /home/ec2-user/app-dynamics/conf/ path and listed no errors in machienaget.log at logs folder) we could confirm that you can ignore warn messages at console, let us know if that clarifies.

Re: Server monitor - log4j:WARN No appenders could be found for logger

CommunityUser — Tue, 14 Jul 2015 14:49:42 GMT

Hi Akumar,

I have run into the same issue where the warning messages appear and the installation process hangs. How were you able to ignore warn messages at console? Did they actually not appear on the console? Also, I found in my machineagent.log the following error:

ERROR RegistrationChannel - Fatal transport error while connecting to URL [/controller/instance/UNKNOWN_MACHINE_ID/systemagentregistration]: org.apache.http.conn.ConnectTimeoutException: Connect to paid138.saas.appdynamics.com:80 [paid138.saas.appdynamics.com/69.27.44.200] failed: Read timed out.

I believe that error is simply due to the fact that the installation process is hanging. Do you have any ideas of how I could solve that?

Thanks,

James

Re: Server monitor - log4j:WARN No appenders could be found for logger

Arun_Dasetty — Wed, 15 Jul 2015 13:55:36 GMT

Hi James,

Lets focus on the main error, it looks machine agent could not connect to the saas contorller, can you check connectivity and let us know if any proxy exists between?

shell> telnet <saas-host-name> 443

shell> telnet <saas-host-name> 80

Re: Server monitor - log4j:WARN No appenders could be found for logger

CommunityUser — Wed, 15 Jul 2015 14:13:57 GMT

Hi Akumar,

I was able to connect to both ports from the aws ec2 instance I am using.

Re: Server monitor - log4j:WARN No appenders could be found for logger

Arun_Dasetty — Thu, 16 Jul 2015 14:19:10 GMT

Hi James,

Please send the following to reduce further iterations if issue still persists,

- account name in saas you are trying to associate agent so that we will login from our end using portal

- telnet output and machine agent logs from physical instance where agent is installed.

<machineagent_dir>/logs folder archive

Re: Server monitor - log4j:WARN No appenders could be found for logger

CommunityUser — Thu, 16 Jul 2015 17:21:47 GMT

Account Name: Ellucian382

telnet output:

$ telnet ellucian382.saas.appdynamics.com 80

Trying 69.27.44.200...

Connected to ellucian382.saas.appdynamics.com.

Escape character is '^]'.

$ telnet ellucian382.saas.appdynamics.com 443

Trying 69.27.44.200...

Connected to ellucian382.saas.appdynamics.com.

Escape character is '^]'.

Attached below are the machine agent logs.

Re: Server monitor - log4j:WARN No appenders could be found for logger

Arun_Dasetty — Fri, 17 Jul 2015 14:43:18 GMT

Hi James,

Please restart machine agent with application-name , tier-name and node-name details provided in C:\Users\jfamulare\Desktop\test-appdynamics\conf\controller-info.xml file and restart as below:

shell> java -Dappdynamics.agent.uniqueHostId=USD1500294_new -jar machineagent.jar

[main] 08 Jul 2015 13:59:16,305 INFO SystemAgent - Full Agent Registration Info Resolver using application name [null]
[main] 08 Jul 2015 13:59:16,305 INFO SystemAgent - Full Agent Registration Info Resolver using tier name [null]
[main] 08 Jul 2015 13:59:16,305 INFO SystemAgent - Full Agent Registration Info Resolver using node name [null]

We expect that should fix the issue. Keep us posted how it goes.

Re: Server monitor - log4j:WARN No appenders could be found for logger

CommunityUser — Mon, 20 Jul 2015 12:32:22 GMT

Hi Akumar,

I'm not exactly sure what values to put for application name, tier name and node name. I tried your command once with them having no values and again with their values as follows:

<application-name>null</application-name>
<tier-name>null</tier-name>
<node-name>null</node-name>

but had no success. What do you mean by restarting the machine agent?

James

Re: Server monitor - log4j:WARN No appenders could be found for logger

CommunityUser — Mon, 20 Jul 2015 12:38:27 GMT

Here's my latest machine-agent.log.

Re: Server monitor - log4j:WARN No appenders could be found for logger

Arun_Dasetty — Mon, 20 Jul 2015 13:16:45 GMT

Hi James,

Try below and see how it goes:

a) stop the java pid 18764 which is current machine agent java process

b) start machine agent as below:

cmd> cd C:\Users\jfamulare\Desktop\test-appdynamics

cmd> java -Dappdynamics.agent.applicationName=MyApp1 -Dappdynamics.agent.tierName=mytier1 -Dappdynamics.agent.nodeName=mynodeUSD1500294 -Dappdynamics.agent.uniqueHostId=USD1500294_new -jar machineagent.jar

We mean to provide some string value in contorller-info.xml at path C:\Users\jfamulare\Desktop\test-appdynamics\conf for application-name, tier-name and node-name args once

- We understood that you can access URL http://Ellucian382.saas.appdynamics.com:80/ in browser from windows instance 198.6.12.113 , let us know if any disconnect, we agree that the telnet command succeeded but would like check in browser once

Re: Server monitor - log4j:WARN No appenders could be found for logger

CommunityUser — Mon, 20 Jul 2015 13:32:51 GMT

Hi Akumar,

Thanks for the quick response! I followed the steps below, but the install still hung with the thats output to the console being:

[Machine Agent] Resolved install dir location :C:\Users\jfamulare\Desktop\test-a ppdynamics.

I was able to access the URL you provided and am attaching an image of that from my browser as well as the most recent error log. Let me know if you see any errors there.

James

Re: Server monitor - log4j:WARN No appenders could be found for logger

CommunityUser — Wed, 22 Jul 2015 14:20:51 GMT

Hello we had the same issue...

I get the following error appellant "[Agent-Scheduler-2] July 22, 2015 10: 57: 04.708 RegistrationChannel ERROR - Fatal transport error while connecting to URL [/ controller / instance / UNKNOWN_MACHINE_ID / systemagentregistration]: org.apache.http.conn.ConnectTimeoutException: Connect to 10.100.9.44:8090 [/10.100.9.44] failed: Connect timed out "

This appears when this agent running machine, one license available still have more to agent machine, the hosts regardless of the name of the corresponding revised machine, the machines are by ping but I can not resolve this error.

Re: Server monitor - log4j:WARN No appenders could be found for logger

Arun_Dasetty — Thu, 23 Jul 2015 15:22:43 GMT

Hi Jonathan and James,

I could say we see similar errors in other customer environments, and they have proxy in place at the end of conclusion as i could access one of your saas ui fine in UI, can you please get in touch with your network team and confirm there is proxy in place?

If proxy in place you would need to add -Dappdynamics.agent.proxyHost and proxyPort as part jvm args before -jar machiangent.jar arg, also attach C:\Users\jfamulare\Desktop\test-appdynamics\conf\contorller-info.xml <machinagent_dir>/conf/contorller-info.xml file .

Also confirm if any AppServerAgent from same or other machine could connect fine to your controller UI, if answer is yes, that confirms there is some firewal/proxy affecting connection as i still see

[Agent-Scheduler-1] 20 Jul 2015 09:20:42,283 ERROR RegistrationChannel - Fatal transport error while connecting to URL [/controller/instance/UNKNOWN_MACHINE_ID/systemagentregistration]: org.apache.http.conn.ConnectTimeoutException: Connect to paid138.saas.appdynamics.com:80 [paid138.saas.appdynamics.com/69.27.44.200] failed: Read timed out