Yes, when executing the nohup java -jar adlite-viewer.jar & process the website is unreachable from a browser. But, when I execute the process and leave the window open the site if reachable. The process just hangs but when I leave the session open and run it from the command line the site comes right up?
Also, when I do get the process running in the background or it seems to be and try again to login to the site I receive the following error inside of the agent log
[AppDynamics Pool - Global] 16 Sep 2010 10:19:18,944 INFO com.singularity.CONFIG.ConfigurationChannel - Sending registration request with: Host Name [intccjb1] Install Dir [Server Node_/usr/local/ccjb1/jboss-4.0.5.GA/bin], Version [Server Agent Lite v2.1.2.0 GA Build Date 2010-06-21 12:27] [AppDynamics Pool - Global] 16 Sep 2010 10:20:18,959 ERROR com.singularity.CONFIG.ConfigurationChannel - Fatal transport error: Read timed out [AppDynamics Pool - Global] 16 Sep 2010 10:20:18,959 WARN com.singularity.CONFIG.ConfigurationChannel - Could not connect to the controller/invalid response from controller, cannot get initialization information
I am not killing the process nor is someone else. That isnt the problem period this isnt a user issue but an application issue. The process is running in nohup and the site is unreachable. Please read all of the information in my previous posts.
Hi all, I confirm that doing 'nohup java -jar adlite-viewer.jar &" doesnt work as : - the viewer is not reachable through the browser - stopping my ssh session kills the viewer process
I am not able to recreate this issue on my end but the logs that you have posted says "Could not connect to the controller/invalid response from controller, cannot get initialization information"
This means viewer is not able to connect to the agent. Can you please try nohup java -jar adlite-viewer.jar -Dappdynamics.viewer.host {your ip addr} -Dappdynamics.viewer.port {port} & to start the viewer.
Please ensure that you do following sequence. 1) Start the App Server that you want to monitor 2) nohup java -jar adlite-viewer.jar -Dappdynamics.viewer.host {your ip addr} -Dappdynamics.viewer.port {port} & execute this command by adding your ip address and viewer port 8990 3) try accessing the viewer from your browser by navigating to http://{ipaddress}:{port}
Please let me know if above mentioned steps are useful.
If you get the same exception then please send me the logs so that we can do further troubleshooting at our end.
Completed this task and the process still comes back with an error. VCROZET confirmed that this is recreatable on your end per his response in the conversation below and above.
# vcrozetvcrozet September 20 Permalink
Hi all, I confirm that doing 'nohup java -jar adlite-viewer.jar &" doesnt work as : - the viewer is not reachable through the browser - stopping my ssh session kills the viewer process
Here is the error I am still receiving.
intccjb1] Install Dir [Server Node_/usr/local/ccjb1/jboss-4.0.5.GA/bin], Version [Server Agent Lite v2.1.2.0 GA Build Date 2010-06-21 12:27] [AppDynamics Pool - Global] 21 Sep 2010 14:37:47,231 INFO com.singularity.ControllerTimeSkewHandler - Controller Time Skew Handler Run Aborted - Skew Check is Disabled [AppDynamics Pool - Global] 21 Sep 2010 14:37:47,379 ERROR com.singularity.CONFIG.ConfigurationChannel - Fatal transport error: Read timed out [AppDynamics Pool - Global] 21 Sep 2010 14:37:47,380 WARN com.singularity.CONFIG.ConfigurationChannel - Could not connect to the controller/invalid response from controller, cannot get initialization information
The no hup option might not work on all the platforms, we tried on Fedora and it does work. In any case using no hup is not the permanent solution we are going to implement a more stable solution that will work in all the environments in our next update of adlite which will be out sometime in November. Our standard version allows you to run the viewer in the background, do you want to sign up for a trial in the interim?
Has the new version been released which supports background?
Solaris used to be able to run in background using nohup with the previous version, but not the version: AppDynamics Lite Viewer 2.0 GA Build Date 2011-10-11 20:40:31
In new version there are no changes around starting Liteviewer is background lite viewer 2.0 should also start in background when you do nohup java -jar adlite-viewer.jar & .
and it worked on the previous version, but now we get
$ exit You have running jobs
when we try to exit the shell, and although it's still running, the viewer seems to stop talking to the agent or at least gives the error:
No transactions have been discovered! This is most likely due to the lack of a connected agent, failure to run load through your JVM, or an incorrect transaction detection configuration
So when You exit from shell . do you see the adlite-viewer process is running or not ? Running liteviewer in a background is related environment so Hatim's comment is right but this has nothing to do with Lite Viewer implementation .
Comments
You can start the adlite-viewer in back ground by executing following command from your adlite viewer installation directory .
nohup java -jar adlite-viewer.jar &
Please let us know if you are still facing any issues while running adlite-viewer in back ground.
Regards,
Arpit Patel
[AppDynamics Pool - Global] 16 Sep 2010 10:19:18,944 INFO com.singularity.CONFIG.ConfigurationChannel - Sending registration request with: Host Name [intccjb1] Install Dir [Server Node_/usr/local/ccjb1/jboss-4.0.5.GA/bin], Version [Server Agent Lite v2.1.2.0 GA Build Date 2010-06-21 12:27]
[AppDynamics Pool - Global] 16 Sep 2010 10:20:18,959 ERROR com.singularity.CONFIG.ConfigurationChannel - Fatal transport error: Read timed out
[AppDynamics Pool - Global] 16 Sep 2010 10:20:18,959 WARN com.singularity.CONFIG.ConfigurationChannel - Could not connect to the controller/invalid response from controller, cannot get initialization information
When you do nohup java -jar adlite-viewer.jar & this it will run Lite viewer as a background process and will run .
if some one kills all java processes or if you explicitly kill the viewer process the site will not be reachable.
Can you please provide me some more information regarding the environment that your using?
Regards,
Arpit Patel
I confirm that doing 'nohup java -jar adlite-viewer.jar &" doesnt work as :
- the viewer is not reachable through the browser
- stopping my ssh session kills the viewer process
what are the next steps to resolving this issue?
I will also need the hardware details . (The server on which you are running the liteviewer).
Regards,
Arpit Patel
if you are able to recreate the issue on your end then it isn't an environmental issue but possibly a bug of sometime. I need an effort on this one.
I am not able to recreate this issue on my end but the logs that you have posted says "Could not connect to the controller/invalid response from controller, cannot get initialization information"
This means viewer is not able to connect to the agent. Can you please try nohup java -jar adlite-viewer.jar -Dappdynamics.viewer.host {your ip addr} -Dappdynamics.viewer.port {port} & to start the viewer.
Please ensure that you do following sequence.
1) Start the App Server that you want to monitor
2) nohup java -jar adlite-viewer.jar -Dappdynamics.viewer.host {your ip addr} -Dappdynamics.viewer.port {port} & execute this command by adding your ip address and viewer port 8990
3) try accessing the viewer from your browser by navigating to http://{ipaddress}:{port}
Please let me know if above mentioned steps are useful.
If you get the same exception then please send me the logs so that we can do further troubleshooting at our end.
#
vcrozetvcrozet September 20 Permalink
Hi all,
I confirm that doing 'nohup java -jar adlite-viewer.jar &" doesnt work as :
- the viewer is not reachable through the browser
- stopping my ssh session kills the viewer process
Here is the error I am still receiving.
intccjb1] Install Dir [Server Node_/usr/local/ccjb1/jboss-4.0.5.GA/bin], Version [Server Agent Lite v2.1.2.0 GA Build Date 2010-06-21 12:27]
[AppDynamics Pool - Global] 21 Sep 2010 14:37:47,231 INFO com.singularity.ControllerTimeSkewHandler - Controller Time Skew Handler Run Aborted - Skew Check is Disabled
[AppDynamics Pool - Global] 21 Sep 2010 14:37:47,379 ERROR com.singularity.CONFIG.ConfigurationChannel - Fatal transport error: Read timed out
[AppDynamics Pool - Global] 21 Sep 2010 14:37:47,380 WARN com.singularity.CONFIG.ConfigurationChannel - Could not connect to the controller/invalid response from controller, cannot get initialization information
The no hup option might not work on all the platforms, we tried on Fedora and it does work. In any case using no hup is not the permanent solution we are going to implement a more stable solution that will work in all the environments in our next update of adlite which will be out sometime in November. Our standard version allows you to run the viewer in the background, do you want to sign up for a trial in the interim?
- Hatim
Solaris used to be able to run in background using nohup with the previous version, but not the version: AppDynamics Lite Viewer 2.0 GA Build Date 2011-10-11 20:40:31
In new version there are no changes around starting Liteviewer is background lite viewer 2.0 should also start in background when you do nohup java -jar adlite-viewer.jar & .
Regards,
Arpit Patel
I know that we used:
nohup $JAVA_HOME/bin/java -jar adlite-viewer.jar &1 &
and it worked on the previous version, but now we get
$ exit
You have running jobs
when we try to exit the shell, and although it's still running, the viewer seems to stop talking to the agent or at least gives the error:
No transactions have been discovered! This is most likely due to the lack of a connected agent, failure to run load through your JVM, or an incorrect transaction detection configuration
Regards,
Arpit Patel