- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Secure OS Software for Linux
- >
- syntax errors in osspi_alarmdef file
Secure OS Software for Linux
1753742
Members
5094
Online
108799
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
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
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
08-13-2008 10:33 AM
08-13-2008 10:33 AM
syntax errors in osspi_alarmdef file
Hi,
I just ran discovery on my first Linux managed node from an HP-UX OVOU 8.29 management server.
After discovery, I distributes osspi templates to the node, including the OSSPI-alarmdef_write, but I get syntax errors. The process did not create the osspi_alarmdef file, but instead created the osspi_alarmdef.chk file, which was expected.
Here are the contents of osspi_alarmdef.chk
Parsing file: "//var/opt/OV/tmp/osspi/osspi_alarm1.25610"
1 :alias FS0 = "/boot"
2 :
3 :alarm FS0:FS_SPACE_UTIL > 80 for 5 minutes
4 : type = "/boot"
5 : service = "OSSPI:fs@@<$MSG_NODE_ID>"
6 : start
7 : if FS0:FS_SPACE_UTIL > 95 then
8 : Critical alert "Filesystem /boot usage over 95%"
9 : else if FS0:FS_SPACE_UTIL > 90 then
10 : Major alert "Filesystem /boot usage over 90%"
11 : else if FS0:FS_SPACE_UTIL > 85 then
12 : Minor alert "Filesystem /boot usage over 85%"
13 : else if FS0:FS_SPACE_UTIL > 80 then
14 : Warning alert "Filesystem /boot usage over 80%"
15 : repeat every 5 minutes
16 : if FS0:FS_SPACE_UTIL > 95 then
17 : Critical alert "Filesystem /boot usage over 95%"
18 : else if FS0:FS_SPACE_UTIL > 90 then
19 : Major alert "Filesystem /boot usage over 90%"
20 : else if FS0:FS_SPACE_UTIL > 85 then
21 : Minor alert "Filesystem /boot usage over 85%"
22 : else if FS0:FS_SPACE_UTIL > 80 then
23 : Warning alert "Filesystem /boot usage over 80%"
24 : end
25 : reset alert "End of /boot filesystem overusage"
26 :
27 :alias FS1 = "/staff1"
28 :
29 :alarm FS1:FS_SPACE_UTIL > 80 for 5 minutes
30 : type = "/staff1"
31 : service = "OSSPI:fs@@<$MSG_NODE_ID>"
32 : start
33 : if FS1:FS_SPACE_UTIL > 95 then
34 : Critical alert "Filesystem /staff1 usage over 95%"
35 : else if FS1:FS_SPACE_UTIL > 90 then
36 : Major alert "Filesystem /staff1 usage over 90%"
37 : else if FS1:FS_SPACE_UTIL > 85 then
38 : Minor alert "Filesystem /staff1 usage over 85%"
39 : else if FS1:FS_SPACE_UTIL > 80 then
40 : Warning alert "Filesystem /staff1 usage over 80%"
41 : repeat every 5 minutes
42 : if FS1:FS_SPACE_UTIL > 95 then
43 : Critical alert "Filesystem /staff1 usage over 95%"
44 : else if FS1:FS_SPACE_UTIL > 90 then
45 : Major alert "Filesystem /staff1 usage over 90%"
46 : else if FS1:FS_SPACE_UTIL > 85 then
47 : Minor alert "Filesystem /staff1 usage over 85%"
48 : else if FS1:FS_SPACE_UTIL > 80 then
49 : Warning alert "Filesystem /staff1 usage over 80%"
50 : end
51 : reset alert "End of /staff1 filesystem overusage"
52 :
53 :alias FS2 = "/staff2"
54 :
55 :alarm FS2:FS_SPACE_UTIL > 80 for 5 minutes
56 : type = "/staff2"
57 : service = "OSSPI:fs@@<$MSG_NODE_ID>"
58 : start
59 : if FS2:FS_SPACE_UTIL > 95 then
60 : Critical alert "Filesystem /staff2 usage over 95%"
61 : else if FS2:FS_SPACE_UTIL > 90 then
62 : Major alert "Filesystem /staff2 usage over 90%"
63 : else if FS2:FS_SPACE_UTIL > 85 then
64 : Minor alert "Filesystem /staff2 usage over 85%"
65 : else if FS2:FS_SPACE_UTIL > 80 then
66 : Warning alert "Filesystem /staff2 usage over 80%"
67 : repeat every 5 minutes
68 : if FS2:FS_SPACE_UTIL > 95 then
69 : Critical alert "Filesystem /staff2 usage over 95%"
70 : else if FS2:FS_SPACE_UTIL > 90 then
71 : Major alert "Filesystem /staff2 usage over 90%"
72 : else if FS2:FS_SPACE_UTIL > 85 then
73 : Minor alert "Filesystem /staff2 usage over 85%"
74 : else if FS2:FS_SPACE_UTIL > 80 then
75 : Warning alert "Filesystem /staff2 usage over 80%"
76 : end
77 : reset alert "End of /staff2 filesystem overusage"
78 :
79 :alias FS3 = "/sys"
80 :
81 :alarm FS3:FS_SPACE_UTIL > 80 for 5 minutes
("//var/opt/OV/tmp/osspi/osspi_alarm1.25610", near line - 81)
Note:
CHECKDEF is dependent on the coda process to define metrics.
Make sure coda is running before executing CHECKDEF.
Unable to complete command: errno 25 (Inappropriate ioctl for device).
Child process: exit status 1
Error 64. Can not continue.
Program ended due to error.
I also turned on tracing and I am including the trace file from the managed node.
Thanks for all the help.
Tobby
I just ran discovery on my first Linux managed node from an HP-UX OVOU 8.29 management server.
After discovery, I distributes osspi templates to the node, including the OSSPI-alarmdef_write, but I get syntax errors. The process did not create the osspi_alarmdef file, but instead created the osspi_alarmdef.chk file, which was expected.
Here are the contents of osspi_alarmdef.chk
Parsing file: "//var/opt/OV/tmp/osspi/osspi_alarm1.25610"
1 :alias FS0 = "/boot"
2 :
3 :alarm FS0:FS_SPACE_UTIL > 80 for 5 minutes
4 : type = "/boot"
5 : service = "OSSPI:fs@@<$MSG_NODE_ID>"
6 : start
7 : if FS0:FS_SPACE_UTIL > 95 then
8 : Critical alert "Filesystem /boot usage over 95%"
9 : else if FS0:FS_SPACE_UTIL > 90 then
10 : Major alert "Filesystem /boot usage over 90%"
11 : else if FS0:FS_SPACE_UTIL > 85 then
12 : Minor alert "Filesystem /boot usage over 85%"
13 : else if FS0:FS_SPACE_UTIL > 80 then
14 : Warning alert "Filesystem /boot usage over 80%"
15 : repeat every 5 minutes
16 : if FS0:FS_SPACE_UTIL > 95 then
17 : Critical alert "Filesystem /boot usage over 95%"
18 : else if FS0:FS_SPACE_UTIL > 90 then
19 : Major alert "Filesystem /boot usage over 90%"
20 : else if FS0:FS_SPACE_UTIL > 85 then
21 : Minor alert "Filesystem /boot usage over 85%"
22 : else if FS0:FS_SPACE_UTIL > 80 then
23 : Warning alert "Filesystem /boot usage over 80%"
24 : end
25 : reset alert "End of /boot filesystem overusage"
26 :
27 :alias FS1 = "/staff1"
28 :
29 :alarm FS1:FS_SPACE_UTIL > 80 for 5 minutes
30 : type = "/staff1"
31 : service = "OSSPI:fs@@<$MSG_NODE_ID>"
32 : start
33 : if FS1:FS_SPACE_UTIL > 95 then
34 : Critical alert "Filesystem /staff1 usage over 95%"
35 : else if FS1:FS_SPACE_UTIL > 90 then
36 : Major alert "Filesystem /staff1 usage over 90%"
37 : else if FS1:FS_SPACE_UTIL > 85 then
38 : Minor alert "Filesystem /staff1 usage over 85%"
39 : else if FS1:FS_SPACE_UTIL > 80 then
40 : Warning alert "Filesystem /staff1 usage over 80%"
41 : repeat every 5 minutes
42 : if FS1:FS_SPACE_UTIL > 95 then
43 : Critical alert "Filesystem /staff1 usage over 95%"
44 : else if FS1:FS_SPACE_UTIL > 90 then
45 : Major alert "Filesystem /staff1 usage over 90%"
46 : else if FS1:FS_SPACE_UTIL > 85 then
47 : Minor alert "Filesystem /staff1 usage over 85%"
48 : else if FS1:FS_SPACE_UTIL > 80 then
49 : Warning alert "Filesystem /staff1 usage over 80%"
50 : end
51 : reset alert "End of /staff1 filesystem overusage"
52 :
53 :alias FS2 = "/staff2"
54 :
55 :alarm FS2:FS_SPACE_UTIL > 80 for 5 minutes
56 : type = "/staff2"
57 : service = "OSSPI:fs@@<$MSG_NODE_ID>"
58 : start
59 : if FS2:FS_SPACE_UTIL > 95 then
60 : Critical alert "Filesystem /staff2 usage over 95%"
61 : else if FS2:FS_SPACE_UTIL > 90 then
62 : Major alert "Filesystem /staff2 usage over 90%"
63 : else if FS2:FS_SPACE_UTIL > 85 then
64 : Minor alert "Filesystem /staff2 usage over 85%"
65 : else if FS2:FS_SPACE_UTIL > 80 then
66 : Warning alert "Filesystem /staff2 usage over 80%"
67 : repeat every 5 minutes
68 : if FS2:FS_SPACE_UTIL > 95 then
69 : Critical alert "Filesystem /staff2 usage over 95%"
70 : else if FS2:FS_SPACE_UTIL > 90 then
71 : Major alert "Filesystem /staff2 usage over 90%"
72 : else if FS2:FS_SPACE_UTIL > 85 then
73 : Minor alert "Filesystem /staff2 usage over 85%"
74 : else if FS2:FS_SPACE_UTIL > 80 then
75 : Warning alert "Filesystem /staff2 usage over 80%"
76 : end
77 : reset alert "End of /staff2 filesystem overusage"
78 :
79 :alias FS3 = "/sys"
80 :
81 :alarm FS3:FS_SPACE_UTIL > 80 for 5 minutes
("//var/opt/OV/tmp/osspi/osspi_alarm1.25610", near line - 81)
Note:
CHECKDEF is dependent on the coda process to define metrics.
Make sure coda is running before executing CHECKDEF.
Unable to complete command: errno 25 (Inappropriate ioctl for device).
Child process: exit status 1
Error 64. Can not continue.
Program ended due to error.
I also turned on tracing and I am including the trace file from the managed node.
Thanks for all the help.
Tobby
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.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP