I'm a new guy doing some quntum calculation with gaussian on my rocks clusters. Recently, my cluster upgraded to rocks 5.3, but something strange happened. Everything goes correct except a serious problem. when I summit my gaussian job with script to sge queue, the job does run, but with the following error message:
However, the command "g03 gaussian.gjf" runs both on front node and all the computing nodes.
Actually, I reinstalled my cluster, but the problem still there.
Anyone could give some suggestions? Thanks!
PS: Before this upgration, everything goes correct.
Last edited by vbe; 02-03-2010 at 05:15 AM..
Reason: rm bad tags, added code tags
Hi All
Does anyone know what is meant by PRINTER STATUS CONNECT concerning print queues?
At work we run a Perle/Connectix JetStream 8500 (RJ45 Model) to connect our dot matrix printers and often we get the Connect Status.
Nobody I speak to knows what the status means. When the printer... (0 Replies)
Hi,
I´m having a lot of problems when working with message queues, both on HP-UX Systems and Sun Solaris. When we fill a queue with a messages, the system hangs and locks everything that relies on the use of IPC resources. Anyone knows how to eliminate this problem?
Thanks,
Haroldo Teixeira (2 Replies)
Hwey I manage a Unix box where I ama having multiple printer problems. the only way to get printers to print again is by rebooting. I stop and start services with no luck. Any one have any ideas? It can go weeks with being OK but then any given printer can go and cause the entire print queue to... (6 Replies)
Hi,
We have a problem with remote printers installed on our server.
Consistently, the printer status is ready but the impressions of the queue are waiting therefore blocked. To unblock the situation, we must launch stopsrc qdaemon-s-s and startsrc qdaemon to reactivate the queue.
Thank you... (2 Replies)
I am using AIX 5.
Just swapped over an HP printer.
The old printer was on a JetDirect box. The new printer connects directly to the network. Using the same IP address to print to, so the only alteration I made was to edit the etc/qconfig file to alter the port setting from 9103 to 9100. I can... (2 Replies)
Hey all
Im looking to reduce the number of cpus available on a certain node in our cluster available for jobs using SGE.
i.e. we have one node that has 24 cpus available for jobs on SGE, i would like to reduce that to 16. Thanks (1 Reply)
Hi,
I'm trying to edit my working bash script to an SGE script in order to submit it as a job to the cluster.
Currently I have:
#!/bin/bash
# Perform fastqc on files in a specified directory.
for ((j=1; j <=17; j++))
do
directory=/data4/una/batch"$j"/
... (0 Replies)
Hello,
I'm working on a SGE cluster and trying to echo the variables passed to the qsub command.
My script is as follows
#!/bin/bash
#$ -V
#$ -cwd
#$ -pe make 10
if ; then
echo "Variable is not set"
else
echo "Variable says: $StatedUserName"
fi
and I run the... (1 Reply)
Discussion started by: nans
1 Replies
LEARN ABOUT OPENSOLARIS
scversions
scversions(1M) System Administration Commands scversions(1M)NAME
scversions - Sun Cluster version management
SYNOPSIS
scversions [-c]
DESCRIPTION
Note -
Beginning with the Sun Cluster 3.2 release, Sun Cluster software includes an object-oriented command set. Although Sun Cluster software
still supports the original command set, Sun Cluster procedural documentation uses only the object-oriented command set. For more infor-
mation about the object-oriented command set, see the Intro(1CL) man page.
The scversions command commits the cluster to a new level of functionality after a rolling-upgrade to new Sun Cluster software. With no
arguments, the scversions command prints a message indicating whether a commitment is needed.
OPERANDS
The following operands are supported:
-c Commit the set of nodes that are currently active members of the cluster to the highest possible level of functionality.
When you upgrade a node (either through upgrade to a new release of the product or by application of a patch) and boot it back
into the cluster, some of the internal protocols on that node might have to run at lower versions in order to cooperate cor-
rectly with other nodes in the cluster. When the cluster is in this state, some administrative actions might be disabled and
some new functionality introduced in the upgrade might be unavailable.
When you run this command once from any node after all nodes are upgraded, the cluster switches to the highest versions of
internal protocols possible. Assuming that all nodes have the same Sun Cluster software installed at that time, all new func-
tionality becomes available and any administrative restrictions are removed.
If a node that has not been upgraded is an active member of the cluster at the time you run the -c option to scversions, the
command has no effect because the cluster is already running at the highest possible level of functionality.
If a node has not been upgraded and is not an active member of the cluster when you run the -c option to scversions (for exam-
ple, if that node is down for maintenance), the internal protocols of the cluster are upgraded to the highest possible ver-
sions. You might have to upgrade the node that was not an active member of the cluster to enable it to rejoin the cluster.
EXIT STATUS
0 Success
non-zero Failure
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWsczu |
+-----------------------------+-----------------------------+
|Interface Stability |Evolving |
+-----------------------------+-----------------------------+
SEE ALSO scinstall(1M)Sun Cluster 3.2 17 Aug 2007 scversions(1M)