10 More Discussions You Might Find Interesting
1. Solaris
Hi,
I am getting service busy alarms on my machines which are using MongoDB every now and then. When the service busy alarm appears, I get the following errors on my mongo router logs.
Tue Apr 7 08:01:08.445 dbclient_rs nodes.ok = true hxcslc-b05:27014
Tue Apr 7 08:01:08.445 dbclient_rs... (0 Replies)
Discussion started by: sni_engineer
0 Replies
2. Solaris
Hi,
I am facing following alarms in var/adm/messages after an interval of 10 mins. I dont know what the impact is and how can i fix it. Can anyone help please?
Dec 4 07:50:03 hxcsvc-a01 ftpd: open_module: stat(/usr/lib/security/pam_unix_session.so.1) failed: No such file or directory
Dec ... (4 Replies)
Discussion started by: sni_engineer
4 Replies
3. Solaris
Hi folks,
I encountered this alarms on a solaris server:
04/21/12 23:17:55 MNP-PGW-A_bge3 mnp 231748 Power Supply Unit 0 is faulty
04/21/12 23:17:55 MNP-PGW-A_bge3 mnp 231748 Power Supply Unit 1 is faulty
04/21/12 23:18:26 MNP-PGW-A_bge3 mnp 231822 Power Supply Unit 0 is faulty:CLEAR... (0 Replies)
Discussion started by: kimurayuki
0 Replies
4. Solaris
Hi I am trying to configure the Hardware alarms on HP server.
I have refer to "HP ProLiant Health Monitor User Guide" and installed
HPQacucli-3.5.0-solaris10-i386
HPQhealth-4.4.0-solaris10-i386
HPQhma-5.7.0-solaris10-i386
HPQilo-1.4.5-solaris10-i386
HPQsmh-5.5.0-solaris10-i386
... (2 Replies)
Discussion started by: anand87
2 Replies
5. UNIX for Dummies Questions & Answers
All the autosys jobs are on server-1 and server-1 has been crashed due to some reason, Now I have to run 5 autosys jobs on server-2 (failover server) which are on server 1.
How to do with Autosys command (which command needs to fired on JIL) (0 Replies)
Discussion started by: tp2115
0 Replies
6. Solaris
Hello,
I have been receiving following alarms in /var/adm/messages
dtcp: WARNING DB (db_tcp.c,363) db_alloc_connid: lp && lp->serverlist error for service 20
It seems like this message is related to LP print service. Since I am not using any print service, is there any way to switch it... (2 Replies)
Discussion started by: aalishan
2 Replies
7. Infrastructure Monitoring
Hi all,
I have a Sun Solaris 9 box which acts as a firewall. Sometimes if multiple actions which cause snmp traps occur very close together, a single snmp trap that is sent containing the text for multiple alarms. I would like to prevent that and have a trap sent for each action which would... (0 Replies)
Discussion started by: g0ld2k
0 Replies
8. UNIX for Advanced & Expert Users
My project uses Autosys.
I am new to this product and I don't know where to start from.
Q1. Please provide me the link where I can get Autosys documentation
Q2. Please refer a good book on Autosys. (Beginner/Intermediate Level) (0 Replies)
Discussion started by: gram77
0 Replies
9. Shell Programming and Scripting
Hi
I have been trying to set up alarms on my Solaris box (Sun OS 5.8)
The objective is to present the user an audible alarm every hour or so.
I have so far done this:
#!/bin/sh
val=1
while
do
printf "\a"
val=`expr $val + 1`
done
I have put this in my crontab to run hourly.... (2 Replies)
Discussion started by: run_time_error
2 Replies
10. Solaris
Is there a imbedded command (Solaris v8 ksh) that will send an administrative alert/alarm. Or is it just triggering a mail message via shell script? If no, is there a good open-source code someone knows about?
Thanks so much in advance for any replies.
...Gozer13 (3 Replies)
Discussion started by: gozer13
3 Replies
disksup(3erl) Erlang Module Definition disksup(3erl)
NAME
disksup - A Disk Supervisor Process
DESCRIPTION
disksup is a process which supervises the available disk space in the system. It is part of the OS_Mon application, see os_mon(7) . Avail-
able for Unix and Windows.
Periodically checks the disks. For each disk or partition which uses more than a certain amount of the available space, the alarm
{{disk_almost_full, MountedOn}, []} is set.
On Unix :
All (locally) mounted disks are checked, including the swap disk if it is present.
On WIN32 :
All logical drives of type "FIXED_DISK" are checked.
Alarms are reported to the SASL alarm handler, see alarm_handler(3erl) . To set an alarm, alarm_handler:set_alarm(Alarm) is called where
Alarm is the alarm specified above.
The alarms are cleared automatically when the alarm cause is no longer valid.
CONFIGURATION
The following configuration parameters can be used to change the default values for time interval and threshold:
disk_space_check_interval = int()>0 :
The time interval, in minutes, for the periodic disk space check. The default is 30 minutes.
disk_almost_full_threshold = float() :
The threshold, as percentage of total disk space, for how much disk can be utilized before the disk_almost_full alarm is set. The
default is 0.80 (80%).
See config(5) for information about how to change the value of configuration parameters.
EXPORTS
get_disk_data() -> [DiskData]
Types DiskData = {Id, KByte, Capacity}
Id = string()
KByte = int()
Capacity = int()
Returns the result of the latest disk check. Id is a string that identifies the disk or partition. KByte is the total size of the
disk or partition in kbytes. Capacity is the percentage of disk space used.
The function is asynchronous in the sense that it does not invoke a disk check, but returns the latest available value.
Returns [{"none",0,0}] if disksup is not available.
get_check_interval() -> MS
Types MS = int()
Returns the time interval, in milliseconds, for the periodic disk space check.
set_check_interval(Minutes) -> ok
Types Minutes = int()>=1
Changes the time interval, given in minutes, for the periodic disk space check.
The change will take effect after the next disk space check and is non-persist. That is, in case of a process restart, this value is
forgotten and the default value will be used. See Configuration above.
get_almost_full_threshold() -> Percent
Types Percent = int()
Returns the threshold, in percent, for disk space utilization.
set_almost_full_threshold(Float) -> ok
Types Float = float(), 0=<Float=<1
Changes the threshold, given as a float, for disk space utilization.
The change will take effect during the next disk space check and is non-persist. That is, in case of a process restart, this value
is forgotten and the default value will be used. See Configuration above.
SEE ALSO
alarm_handler(3erl) , os_mon(3erl)
Ericsson AB os_mon 2.2.5 disksup(3erl)