User Tools

Site Tools


databaseandnetworkmanagement:kumu_networks

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
databaseandnetworkmanagement:kumu_networks [2022/01/24 20:51] slawrencedatabaseandnetworkmanagement:kumu_networks [2022/01/25 17:48] (current) slawrence
Line 5: Line 5:
 **There is an AWS instance that is running our production trial environment. **There is an AWS instance that is running our production trial environment.
 ** **
-//  * kumuapps1.err+ 
 +  * kumuapps1.err
   * kumuapps2.err   * kumuapps2.err
   * kumuesk1.err   * kumuesk1.err
Line 11: Line 12:
   * kumulbdbrmq.err   * kumulbdbrmq.err
   * kumuoat1.err   * kumuoat1.err
-  * kumuoat2.err//+  * kumuoat2.err
  
 **Currently, the system is only running the MDC agent on kumuoat1.err.  kumuoat2.err functionality has been shut down (more on that later). **Currently, the system is only running the MDC agent on kumuoat1.err.  kumuoat2.err functionality has been shut down (more on that later).
Line 44: Line 45:
 NOTE:  As per usual, you can generally see if the MDC Agent is running simply by tailing the log file with something like:** NOTE:  As per usual, you can generally see if the MDC Agent is running simply by tailing the log file with something like:**
  
-**//sudo tail -f /home/rdfagent/rdfagent/logs/agent/spring.log +//sudo tail -f /home/rdfagent/rdfagent/logs/agent/spring.log 
-**//+//
  
 +NOTE:  There is a script on kumuoat1.err -> /home/scotty/start_commands.sh
 +This script can fully reboot the MDC with the VPN and all running. Please run as "sudo ./start_commands.sh".
databaseandnetworkmanagement/kumu_networks.1643057469.txt.gz · Last modified: 2022/01/24 20:51 by slawrence