09 Jun 2019
06:15 AM
- last edited on
14 Dec 2021
03:03 AM
by
MaciejNeumann
Dear All,
Followed the documented instructions to "Configure WebSphere Application Server via the Administrative console" even though getting the message "Deep monitoring of this process has not been set up. You're missing out on crucial process- and service-level monitoring insights".
Also included the below lines in the .profile file.
I am Looking forward to your as usual professional assistance.
Regards,
Babar
Has the process of the application server really been restarted?
Did you save the configuration after editing in WAS console?
Just investigate the agent logs and see if there is a log file for the restarted WAS process (should have the pid number in its name). Maybe there is some other problem with the injection.
The .profile is not necessary to modify for the WAS.
Hello @Julius L.
Configuration was saved and the process was restarted multiple times. We could not find anything in agent logs related to WAS restated process.
The .profile is not necessary to modify for the WAS.
The same server is hosting the Apache Web Server. Do we need to modify .profile for this process to be monitored?
Regards,
Babar
For Apache, it depends on how it is started. Normally I'd recommend to put it into the startup script or the environment script.
For the WAS - please doublecheck your configuration. Isn't there some other deep monitoring tool installed? If it is a WAS ND, try to restart also the nodeagent (although this should not be necessary).
Also check all the WAS logs for errors during application server startup. It may happen when permissions are wrong for the oneagent log directory, the injection fails and no logs are written in the oneagent log directory.
Hello @Julius L.
I asked the application team and they said we are following the same standards. No error is found in the WAS logs.
For the WAS processes, it looks like below with the message "This process isn't fully monitored".
Regards,
Babar
Hello @Mikhail A.
Below is the asked information.
Regards,
Babar
Check startServer.log for some warning or error (or maybe nativestderr.log)
You can also try to add a line LDR_PRELOAD=$DT_HOME/agent/lib/liboneagentproc.so
Hello @Mikhail A.
We included the 32-bit entry LDR_PRELOAD=$DT_HOME/agent/lib/liboneagentproc.so, even though the same situation.
No warning and error found in the startServer.log and nativestderr.log.
Regards,
Babar
Hello @Rahul V.
Unfortunately not yet. Even after reinstalling the agent with the root account.
Regards,
Babar