Sponsored Content
Full Discussion: Cluster form fail
Operating Systems Linux Red Hat Cluster form fail Post 302934281 by gema.utama on Thursday 5th of February 2015 09:55:37 PM
Old 02-05-2015
Cluster form fail

why does my cluster form but fail after a few minutes, or why do my multicast communications stop working after a short amount of time?
 

9 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Changing Unix form to Microsoft Word form to be able to email it to someone.

Please someone I need information on how to change a Unix form/document into a microsoft word document in order to be emailed to another company. Please help ASAP. Thankyou :confused: (8 Replies)
Discussion started by: Cheraunm
8 Replies

2. HP-UX

MC/SG Fail to join cluster node

Hi, Please advise me whereas I have two node cluster server configured with MC/SG. Application and DB are running on Node 1, while Node 2 is standby. All the volume group devices are part of cluster environment. There is only one package running at node 1. Node 2 is having the problem to... (1 Reply)
Discussion started by: rauphelhunter
1 Replies

3. High Performance Computing

Building a Solaris Cluster Express cluster in a VirtualBox on OpenSolaris

Provides a description of how to set up a Solaris Cluster Express cluster in a VirtualBox on OpenSolaris. More... (0 Replies)
Discussion started by: Linux Bot
0 Replies

4. Solaris

SC3.2 issue - cluster transport configuration not right - resulting fail

I am trying to set up a two host cluster. trouble is with the cluster transport configuration. i'm using e1000g2 and g3 for the cluster transport. global0 and global1 are my two nodes, and I am running the scinstall from global1. i think i should be expecting, is this: The following... (19 Replies)
Discussion started by: frustin
19 Replies

5. Solaris

Sun cluster and Veritas cluster question.

Yesterday my customer told me to expect a vcs upgrade to happen in the future. He also plans to stop using HDS and move to EMC. Am thinking how to migrate to sun cluster setup instead. My plan as follows leave the existing vcs intact as a fallback plan. Then install and build suncluster on... (5 Replies)
Discussion started by: sparcguy
5 Replies

6. UNIX for Advanced & Expert Users

Veritas Cluster automatic fail-back option on Solaris

Hi - Please help me to understand the Veritas Cluster fail-over capability. We configured oracle database file system on veritas cluster file system and it is automatically failing-over from node 1 to node 2. Does Veritas cluster softward have any option to fail-back from node 2 to node 1... (6 Replies)
Discussion started by: Mansoor8810
6 Replies

7. Solaris

Sun cluster 4.0 - zone cluster failover doubt

Hello experts - I am planning to install a Sun cluster 4.0 zone cluster fail-over. few basic doubts. (1) Where should i install the cluster s/w binaries ?. ( global zone or the container zone where i am planning to install the zone fail-over) (2) Or should i perform the installation on... (0 Replies)
Discussion started by: NVA
0 Replies

8. Shell Programming and Scripting

Transpose Data form Different form

HI Guys, I have data in File A.txt RL03 RL03_A_1 RL03_B_1 RL03_C_1 RL03 -119.8 -119.5 -119.5 RL07 RL07_A_1 RL07_B_1 RL07_C_1 RL07 -119.3 -119.5 -119.5 RL15 RL15_A_1 RL15_C_1 RL15 -120.5 -119.4 RL16... (2 Replies)
Discussion started by: asavaliya
2 Replies

9. Shell Programming and Scripting

Remove x lines form top and y lines form bottom using AWK?

How to remove x lines form top and y lines form bottom. This works, but like awk only cat file | head -n-y | awk 'NR>(x-1)' so remove last 3 lines and 5 firstcat file | head -n-3 | awk 'NR>4' (5 Replies)
Discussion started by: Jotne
5 Replies
condor_userlog(1)					      General Commands Manual						 condor_userlog(1)

Name
       condor_userlog Display - and summarize job statistics from job log files.

Synopsis
       condor_userlog [-help] [-total | -raw] [-debug] [-evict] [-j cluster | cluster.proc] [-all] [-hostname] logfile ...

Description
       condor_userlog  parses  the  information  in job log files and displays summaries for each workstation allocation and for each job. See the
       manual page for condor_submiton page for instructions for specifying that Condor write a log file for your jobs.

       If -totalis not specified, condor_userlogwill first display a record for each workstation allocation, which includes the following informa-
       tion:

       Job

	  The cluster/process id of the Condor job.

       Host

	  The  host  where  the job ran. By default, the host's IP address is displayed. If -hostnameis specified, the host name will be displayed
	  instead.

       Start Time

	  The time (month/day hour:minute) when the job began running on the host.

       Evict Time

	  The time (month/day hour:minute) when the job was evicted from the host.

       Wall Time

	  The time (days+hours:minutes) for which this workstation was allocated to the job.

       Good Time

	  The allocated time (days+hours:min) which contributed to the completion of this job. If the job exited during the allocation, then  this
	  value  will  equal  ``Wall Time.'' If the job performed a checkpoint, then the value equals the work saved in the checkpoint during this
	  allocation. If the job did not exit or perform a checkpoint during this allocation, the value will be 0+00:00. This value can be greater
	  than	0  and	less  than ``Wall Time'' if the application completed a periodic checkpoint during the allocation but failed to checkpoint
	  when evicted.

       CPU Usage

	  The CPU time (days+hours:min) which contributed to the completion of this job.

       condor_userlogwill then display summary statistics per host:

       Host/Job

	  The IP address or host name for the host.

       Wall Time

	  The workstation time (days+hours:minutes) allocated by this host to the jobs specified in the query. By default, all jobs in the log are
	  included in the query.

       Good Time

	  The time (days+hours:minutes) allocated on this host which contributed to the completion of the jobs specified in the query.

       CPU Usage

	  The CPU time (days+hours:minutes) obtained from this host which contributed to the completion of the jobs specified in the query.

       Avg Alloc

	  The average length of an allocation on this host (days+hours:minutes).

       Avg Lost

	  The average amount of work lost (days+hours:minutes) when a job was evicted from this host without successfully performing a checkpoint.

       Goodput

	  This percentage is computed as Good Time divided by Wall Time.

       Util.

	  This percentage is computed as CPU Usage divided by Good Time.

       condor_userlogwill then display summary statistics per job:

       Host/Job

	  The cluster/process id of the Condor job.

       Wall Time

	  The total workstation time (days+hours:minutes) allocated to this job.

       Good Time

	  The total time (days+hours:minutes) allocated to this job which contributed to the job's completion.

       CPU Usage

	  The total CPU time (days+hours:minutes) which contributed to this job's completion.

       Avg Alloc

	  The average length of a workstation allocation obtained by this job in minutes (days+hours:minutes).

       Avg Lost

	  The average amount of work lost (days+hours:minutes) when this job was evicted from a host without successfully performing a checkpoint.

       Goodput

	  This percentage is computed as Good Time divided by Wall Time.

       Util.

	  This percentage is computed as CPU Usage divided by Good Time.

       Finally, condor_userlogwill display a summary for all hosts and jobs.

Options
       -help

	  Get a brief description of the supported options

       -total

	  Only display job totals

       -raw

	  Display raw data only

       -debug

	  Debug mode

       -j

	  Select a specific cluster or cluster.proc

       -evict

	  Select only allocations which ended due to eviction

       -all

	  Select all clusters and all allocations

       -hostname

	  Display host name instead of IP address

General Remarks
       Since  the Condor job log file format does not contain a year field in the timestamp, all entries are assumed to occur in the current year.
       Allocations which begin in one year and end in the next will be silently ignored.

Exit Status
       condor_userlogwill exit with a status value of 0 (zero) upon success, and it will exit with the value 1 (one) upon failure.

Author
       Condor Team, University of Wisconsin-Madison

Copyright
       Copyright (C) 1990-2012 Condor Team, Computer Sciences Department, University of  Wisconsin-Madison,  Madison,  WI.  All  Rights  Reserved.
       Licensed under the Apache License, Version 2.0.

       See the Condor Version 7.8.2 Manualor http://www.condorproject.org/licensefor additional notices. condor-admin@cs.wisc.edu

								  September 2012						 condor_userlog(1)
All times are GMT -4. The time now is 04:11 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy