Sponsored Content
Operating Systems Solaris Best way to monitor health of Solaris zones ? Post 302923962 by pradeep84in on Wednesday 5th of November 2014 01:41:10 PM
Old 11-05-2014
Can you elaborate what do you mean by monitor of solaris health zone ?

If it's only a health check of solaris servers then you can have a script which will monitor the cpu usage, load, monitor IO, memory utilization and check of syslog files for any error and send the mail if any error found or any of the resource reached to its threshold limit and generate a mail to DL/mail id as per requirement and support time.

You can schedule the script after a particular interval with the help of scheduler(Autosys, Tivoli, Control-M, etc.) as per the criticality of the server in the environment.

If case of server down or not pinging job schedule on scheduler for monitoring will get fail and failure alarm/notification will get generated.
 

8 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Solaris Zones

okay people i need some help: i was able to configure zones on my solaris 10 server, the problem is I can't ssh into the zones!!! I can zlogin -C zone2 successfully for both zones. Am I missing something? I can ping the zones, but can't ssh. From the zones, I can ping my global server. (7 Replies)
Discussion started by: Sarccastik Dude
7 Replies

2. Solaris

Regarding Solaris Zones

Hello All, I have a list of Local Zones in my list. I want to find out their Global Zone names exactly....I know the command "arp ..."But I dont know how to filter it correctly and find it out. Thanks in advance, Jacky (9 Replies)
Discussion started by: jegaraman
9 Replies

3. Solaris

Solaris zones

Hi, I created a zone with separate /usr for the zone. when I do ping to newly created zone it showing alive, I am able to login through zone console zlogin -C -E <zone name> I created a test account on zone which is already existing under global zone and try to ssh, it is working fine but... (1 Reply)
Discussion started by: alberto
1 Replies

4. Solaris

Monitor server's health

Dear all, There wasn't any monitoring on our server except on the filesystem. Therefore, I was wondering anything i should do on a daily basis to check on the server's status, health, hardware, or any other thing as a disaster prevention? Also, what command i should use to do that? ... (2 Replies)
Discussion started by: beginningDBA
2 Replies

5. Shell Programming and Scripting

Script to monitor Machine Health (Project Doctortux) Input needed.

I have written little script to check the CPU performance of the machine. Request you to contribute your comments on the same. Feel free to add your own scriptlet to make it better. I have decided to call it as doctortux I have decided to run the script in two mode 1)Interactive.(Not... (4 Replies)
Discussion started by: pinga123
4 Replies

6. Shell Programming and Scripting

System Health - Cpu, Load, IO Monitor

hello there, can someone please tell me the commands that makes sense, from a production point of view, to be used to make sure CPU, LOAD or IO usages on a Linux or Solaris server isn't too high? I'm aware of vmstat, iostat, sar. But i seriously need real world advice as to what fields in... (1 Reply)
Discussion started by: SkySmart
1 Replies

7. Solaris

Solaris zones

Hi guys and gals, Does anyone know how to import solaris zones from the xml files that sit in /etc/zones? I want the zones from one machine to another, all I have is the XML files for the zones, so I can't export them first. Thanks in advance Martin (1 Reply)
Discussion started by: callmebob
1 Replies

8. Solaris

Migration of Solaris 10 on physical host to Solaris Zones

Hi All Kindly let me know how can I move Solaris 10 OS running update 10 on physical machine to another machine solaris zone running Solaris 10 update 11 (2 Replies)
Discussion started by: amity
2 Replies
pbs_sched(8B)								PBS							     pbs_sched(8B)

NAME
pbs_sched_cc - pbs C scheduler SYNOPSIS
pbs_sched [-a alarm] [-d home] [-L logfile] [-p file] [-S port] [-R port] [-c file] DESCRIPTION
The pbs_sched program runs in conjunction with the PBS server. It queries the server about the state of PBS and communicates with pbs_resmon to get information about the status of running jobs, memory available etc. It then makes decisions as to what jobs to run. pbs_sched must be executed with root permission. OPTIONS
-a alarm This specifies the time in seconds to wait for a schedule run to finish. If a script takes too long to finish, an alarm signal is sent, and the scheduler is restarted. If a core file does not exist in the current directory, abort() is called and a core file is generated. The default for alarm is 180 seconds. -d home This specifies the PBS home directory, PBS_HOME. The current working directory of the scheduler is PBS_HOME/sched_priv. If this option is not given, PBS_HOME defaults to $PBS_SERVER_HOME as defined during the PBS build procedure. -L logfile Specifies an absolute path name of the file to use as the log file. If not specified, the scheduler will open a file named for the current date in the PBS_HOME/sched_logs directory (see the -d option). -p file This specifies the "print" file. Any output from the C code which is written to standard out or standard error will be written to this file. If this option is not given, the file used will be PBS_HOME/sched_priv/sched_out . See the -d option. -S port This specifies the port to use. If this option is not given, the default port for the PBS scheduler is used. -R port This specifies the resource monitor port to use. If this option is not given, the default port for the PBS mom is used. NOTE: this option only makes the mom port available to the scheduler writer. It doesn't force them to use it. -c file Specify a configuration file, see description below. If this is a relative file name it will be relative to PBS_HOME/sched_priv, see the -d option. If the -c option is not supplied, pbs_sched will not attempt to open a configura- tion file. The options that specify file names may be absolute or relative. If they are relative, their root directory will be PBS_HOME/sched_priv. USAGE
This version of the scheduler requires knowledge of the C language and the PBS API. Source code is provided for a main program for the scheduler. The site must supply the heart of the program. When invoked, the main program performs general initialization and housekeeping chores. Then a locally supplied function, schedinit() is called to perform site specific initialization. In the main loop, a locally supplied function, schedule() is called to make the scheduling decisions and perform any required actions. Information about jobs and queues is obtained from the Server through the standard PBS API as found in libifl.a. Information about the execution host(s) is obtained from the Resource Monitor. Routines to communicate with the Resource Monitor are found in libnet.a. If the processing takes more than the allotted time, the scheduler will restart itself. The default amount of time is three minutes. This can be changed with the -a option. On receipt of a SIGHUP signal, the scheduler will close and reopen its log file and reread its configuration file (if any). CONFIGURATION FILE
A configuration file may be specified with the -c option. This file may be used to specify the hosts (servers) which are allowed to con- nect to pbs_sched. The hosts are specified in the configuration file in a manor identical to that used in pbs_mom. clienthost One or more servers, one per line, may be specified: $clienthost hostname +.IP restricted Allows connections from non-priviledged ports on the named hosts. Typically only used with Mac OSX: $restricted hostname Two host names are always allowed to connection to pbs_sched, "localhost" and the name returned to pbs_sched by the system call gethostname(). These names need not be specified in the configuration file. The configuration file must be "secure". It must be owned by a user id and group id less than 10 and not be world writable. FILES
$PBS_SERVER_HOME/sched_priv the default directory for configuration files, typically (/usr/spool/pbs)/sched_priv. Signal Handling A C based scheduler will handle the following signals: SIGHUP The server will close and reopen its log file and reread the config file if one exists. SIGALRM If the site supplied scheduling module exceeds the time limit, the Alarm will cause the scheduler to attempt to core dump and restart itself. SIGINT and SIGTERM Will result in an orderly shutdown of the scheduler. All other signals have the default action installed. EXIT STATUS
Upon normal termination, an exit status of zero is returned. SEE ALSO
pbs_sched_tcl(8B), pbs_server(8B), and pbs_mom(8B). PBS Internal Design Specification Local pbs_sched(8B)
All times are GMT -4. The time now is 06:09 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy