Shutdown nGeniusONE Server: Difference between revisions

From wiki.comcert.com
Jump to navigation Jump to search
No edit summary
No edit summary
 
Line 10: Line 10:
=== Linux ===
=== Linux ===


Login to nGeniusONE Server's CLI as root
Login to nGeniusONE Server's CLI as root or Administrator


Change to /opt/NetScout/rtm/bin
Change to /opt/NetScout/rtm/bin:
<pre># cd /opt/NetScout/rtm/bin</pre>
<pre># cd /opt/NetScout/rtm/bin</pre>


Stop all services
Stop all services:
<pre># ./stop</pre>
<pre># ./stop</pre>


Verify that all services have stopped
Verify that all services are stopped:
<pre># ./PS</pre>
<pre># ./PS</pre>


Shoud output:
It is normal that the process&nbsp;Xvfb is still running.&nbsp; It&nbsp;is not necessary to kill that process.


To start without rebooting:
To start without rebooting:
Line 27: Line 27:


It could take up to 15' before the WebUI is accessible again.
It could take up to 15' before the WebUI is accessible again.
<span style="background-color:#FFFF00;">Do not stop the server again before the startup process is finished and the WebUI is reachable.</span>


&nbsp;
&nbsp;

Latest revision as of 10:50, 5 January 2021

Introduction

To reduce the risk of data loss it is recommeded to stop all services before restarting the server.

 

Solution

Linux

Login to nGeniusONE Server's CLI as root or Administrator

Change to /opt/NetScout/rtm/bin:

# cd /opt/NetScout/rtm/bin

Stop all services:

# ./stop

Verify that all services are stopped:

# ./PS

It is normal that the process Xvfb is still running.  It is not necessary to kill that process.

To start without rebooting:

# ./start

It could take up to 15' before the WebUI is accessible again.

Do not stop the server again before the startup process is finished and the WebUI is reachable.

 

Windows

RDP to the nGeniusONE server's desktop

Login with Local Administrator priviledges

Run PowerShell as Administrator

Move to Netscout\rtm\bin

Execute .\stopserv.bat to stop all running services

To start without rebooting, run .\start.bat

It could take up to 15' before the WebUI is accessible again.