- Community Home
- >
- Servers and Operating Systems
- >
- Server Clustering
- >
- Monitoring Daemon fails to load
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-29-2016 01:46 AM
09-29-2016 01:46 AM
Monitoring Daemon fails to load
Hi,
I installed CMU v 8.0 on one of my VMs for some plugin validation, all installed, GUI goes up, but I see that monitoring daemon fails to load.
Log:
[29-Sep-2016_11:24:32] [CMUstartup ] thread test [START]...
[29-Sep-2016_11:24:32] [CMUstartup ] thread test... [STOP]
[29-Sep-2016_11:24:32] [CMUTools ] about to run: -->/opt/cmu/tools/cmu_check_mtu -v &> /opt/cmu/tmp/CMU_TEMPO_FILE_861Sf2<-- cmu_system_helper
[29-Sep-2016_11:24:32] [CMUFileLockTools ] mypid is 353 CMUGetMonitoringDaemonLockFile
[29-Sep-2016_11:24:32] [MainMonitDaemon ] starting main monitoring daemonMain
[29-Sep-2016_11:24:32] [MainMonitDaemon ] (Using files:
ActionAndAlerts file: /opt/cmu/etc/ActionAndAlertsFile.txt
MetaAction file /opt/cmu/etc/MetaActionFile.txt) Main
[29-Sep-2016_11:24:32] [MainMonitDaemon ] (Using debug levels:
MainMonitoringDaemon: 1
SecondaryServerMonitoringDaemon: 1
SmallMonitoringDaemon: 1) Main
[29-Sep-2016_11:24:32] [CMUFileLockTools ] mypid is 380 CMUGetMonitoringDaemonLockFile
[29-Sep-2016_11:24:32] [CMUFileLockTools ] killing process 353 : CMUKillDaemon
[29-Sep-2016_11:24:32] [MonitReadClusterDb] [FATAL] Pointer to Ne_list first is NULL
[29-Sep-2016_11:24:32] [MainMonitDaemon ] Failed While writing /opt/cmu/etc/NodesList.txt
[29-Sep-2016_11:24:32] [MainMonitDaemon ] MonitoringDaemon stopped without cluster wide cleaning Main
Can you please assist?
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-02-2016 11:13 AM
10-02-2016 11:13 AM
Re: Monitoring Daemon fails to load
Hello,
Please send us the following information.
How many nodes are present in the cluster and how many network groups ? Each network group has how many nodes?
# service cmu status
# /opt/cmu/bin/cmu_show_network_groups
# /opt/cmu/bin/cmu_show_network_groups <network group name> [repeat this command for all the groups]
Increase the Monitoring debug level on the head node in /opt/cmu/etc/cmuserver.conf and restart the monitoring.
CMU_MAIN_MONITORING_DEBUG_LEVEL=4
CMU_SEC_MONITORING_DEBUG_LEVEL=4
CMU_SMD_MONITORING_DEBUG_LEVEL=4
Wait for couple of mintues and send the monitoring logs.