HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- file missing for diagmond
Operating System - HP-UX
1833726
Members
2576
Online
110063
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
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
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- 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
02-18-2002 04:44 AM
02-18-2002 04:44 AM
when doing a tusc on diagmond I get the following error:
( Attached to process 868 ("/usr/sbin/stm/uut/bin/sys/diagmond") [32-bit] )
[868] select(6, 0x7f7e1434, NULL, NULL, 0x7f7e1534) ...................................................................................... [sleeping]
[868] select(6, 0x7f7e1434, NULL, NULL, 0x7f7e1534) ...................................................................................... = 0
[868] stat("/var/stm/data/tools/monitor/MON_RESTART", 0x7f7e0430) ........................................................................ ERR#2 ENOENT
[868] stat("/var/stm/data/os_decode_xref", 0x7f7e10f8) ................................................................................... = 0
[868] access("/var/stm/data/monitor_paths", F_OK) ........................................................................................ = 0
[868] select(0, NULL, NULL, NULL, 0x7f7e110c) ............................................................................................ = 0
[868] getsockname(5, 0x7f7e1484, 0x7f7e1494) ............................................................................................. = 0
It's probably nothing, but I'm annoyed that the function of this file is documented nowhere...
Dirk
( Attached to process 868 ("/usr/sbin/stm/uut/bin/sys/diagmond") [32-bit] )
[868] select(6, 0x7f7e1434, NULL, NULL, 0x7f7e1534) ...................................................................................... [sleeping]
[868] select(6, 0x7f7e1434, NULL, NULL, 0x7f7e1534) ...................................................................................... = 0
[868] stat("/var/stm/data/tools/monitor/MON_RESTART", 0x7f7e0430) ........................................................................ ERR#2 ENOENT
[868] stat("/var/stm/data/os_decode_xref", 0x7f7e10f8) ................................................................................... = 0
[868] access("/var/stm/data/monitor_paths", F_OK) ........................................................................................ = 0
[868] select(0, NULL, NULL, NULL, 0x7f7e110c) ............................................................................................ = 0
[868] getsockname(5, 0x7f7e1484, 0x7f7e1494) ............................................................................................. = 0
It's probably nothing, but I'm annoyed that the function of this file is documented nowhere...
Dirk
Solved! Go to Solution.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-18-2002 05:16 AM
02-18-2002 05:16 AM
Solution
Hi,
Could the MON_RESTART file be a flag, which indicates to the diagmond process that it should restart and re-read it's configuration? In that case, the fact that the file's not there should not be a problem.
Anyway, are you actually experiencing problems with diagmond?
Regards,
Vincent
Could the MON_RESTART file be a flag, which indicates to the diagmond process that it should restart and re-read it's configuration? In that case, the fact that the file's not there should not be a problem.
Anyway, are you actually experiencing problems with diagmond?
Regards,
Vincent
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-18-2002 05:26 AM
02-18-2002 05:26 AM
Re: file missing for diagmond
No, diagmond runs fine. I was just wondering what the file does.
I touched the file while running tusc and it indeed causes diagmond to restart (but keeping the same PID).
Maybe it's an easier way to restart EMS than using monconfig...
Thanks for responding,
Dirk
I touched the file while running tusc and it indeed causes diagmond to restart (but keeping the same PID).
Maybe it's an easier way to restart EMS than using monconfig...
Thanks for responding,
Dirk
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP