Sponsored Content
Operating Systems Solaris Solaris 11 Express - cannot reboot remotely Post 302552504 by incredible on Sunday 4th of September 2011 02:47:45 AM
Old 09-04-2011
which h/w are you using? can you do a "soft-reset" of the system to power cycle and see if you can see the messages. IT SHOULD reset, probe and bring your OS back. If not, how did you got the OS up again?
 

8 More Discussions You Might Find Interesting

1. Solaris

Installing PHP on Solaris (Express) Error

Hi PHP 5 can't seem to find cc compiler even though it's there (note, i'm installing in a zone,& am root) Any Ideas ? $ pwd /tmp/php-5.2.6 $ ./configure loading cache ./config.cache checking for Cygwin environment... no checking for mingw32 environment... no checking for egrep... egrep... (4 Replies)
Discussion started by: stevie_velvet
4 Replies

2. Solaris

ipfilter solaris express

Hello, | am trying to setup ipfilter on solaris express snv_91 but I don't seem to have the following file available. /etc/ipf/pfil.ap Is this an older way of configuring the interface?, I have all the packages installed. Thanks, (1 Reply)
Discussion started by: Actuator
1 Replies

3. Solaris

Solaris Express or OpenIndiana

Simply question which should I use. correct me if I'm wrong but Solaris Express is taking the place of Opensolaris and is officially sanctioned by Oracle and OpenIndiana is what used to be OpenSolaris. If I opt for OpenIndiana is it going to follow the official Oracle Solaris releases or are... (3 Replies)
Discussion started by: michael78
3 Replies

4. Solaris

Solaris 11 Express NAT performance issues

Hi all, I decided to replace my linux router/firewall with Solaris 11 express. This is a pppoe connection directly to my server...no router boxes. I got everything setup, but the performance is terrible on the NAT....really slow. A web page that loads on the server instantly will take... (3 Replies)
Discussion started by: vectox
3 Replies

5. Solaris

OpenSolaris, Solaris, Solaris Express - differences

What are the differences between these systems? I have to use Oracle's product but I do not know who to choose (3 Replies)
Discussion started by: PtaQ
3 Replies

6. Solaris

In doubt to install Solaris 11 Express

Hi guys. I'm in doubt to install Solaris 11 Express or to install Solaris 10. I tried it a few months ago and that was totally disaster because Solaris 11 was slow as my granny :wall: My PC from my perspective has more than enough HW power to run Solaris 11. OS Name: ... (3 Replies)
Discussion started by: solaris_user
3 Replies

7. Solaris

Can't change root password in solaris express 11

How do I change root password in SolarisExpress 11? I used passwd while elevated to root and all it changes is the password of the user I am logged in, not te root password. (2 Replies)
Discussion started by: taltamir
2 Replies

8. Solaris

Solaris 11 Express - freezes on startup!

I seem to be having a very irritating problem with my Solaris 11 Express fileserver which I built for my small home business. The basic problem is that the system will hang or freeze about 20 seconds into booting up. Grub comes up fine, and I can select between pre-napp-it and current build. It... (13 Replies)
Discussion started by: Smokin Whale
13 Replies
powerman(1)							     powerman							       powerman(1)

NAME
powerman - power on/off nodes SYNOPSIS
pm [-options] -action [targets] [-action [targets] ...] DESCRIPTION
powerman provides power management in a data center or compute cluster environment. It performs operations such as power on, power off, and power cycle via remote power controller (RPC) devices. Target hostnames are mapped to plugs on RPC devices in powerman.conf(5). OPTIONS
-1, --on targets Power ON targets. -0, --off targets Power OFF targets. -c, --cycle targets Power cycle targets. -r, --reset targets Assert hardware reset for targets (if implemented by RPC). -f, --flash targets Turn beacon ON for targets (if implemented by RPC). -u, --unflash targets Turn beacon OFF for targets (if implemented by RPC). -l, --list List available targets. If possible, output will be compressed into a host range (see TARGET SPECIFICATION below). -q, --query-all Query plug status of all targets. Status is not cached; each time this option is used, powermand queries the appropriate RPC's. Targets connected to RPC's that could not be contacted (e.g. due to network failure) are reported as status "unknown". If possible, output will be compressed into host ranges. -Q, --query targets Query plug status of specific targets. -n, --soft-all Query soft power status of all targets (if implemented by RPC). In this context, a node in the OFF state could be ON at the plug but operating in standby power mode. -N, --soft targets Query soft power status of specific targets (if implemented by RPC). -b, --beacon-all Query beacon status of all targets (if implemented by RPC). -B, --beacon targets Query beacon status of specific targets (if implemented by RPC). -t, --temp-all Query node temperature of all targets (if implemented by RPC). Temperature information is not interpreted by powerman and is reported as received from the RPC on one line per target, prefixed by target name. -P, --temp targets Query node temperature of specific targets (if implemented by RPC). -h, --help Display option summary. -L, --license Show powerman license information. -h, --server-host host[:port] Connect to a powerman daemon on non-default host and optionally port. -V, --version Display the powerman version number and exit. -D, --device Displays RPC status information. If targets are specified, only RPC's matching the target list are displayed. -T, --telemetry Causes RPC telemetry information to be displayed as commands are processed. Useful for debugging device scripts. -x, --exprange Expand host ranges in query responses. -g, --genders If configured with the genders(3) package, this option tells powerman that targets are genders attributes that map to node names rather than the node names themselves. TARGET SPECIFICATION
powerman target hostnames may be specified as comma separated or space separated hostnames or host ranges. Host ranges are of the general form: prefix[n-m,l-k,...], where n < m and l < k, etc., This form should not be confused with regular expression character classes (also denoted by ``[]''). For example, foo[19] does not represent foo1 or foo9, but rather represents a degenerate range: foo19. This range syntax is meant only as a convenience on clusters with a prefixNN naming convention and specification of ranges should not be considered necessary -- the list foo1,foo9 could be specified as such, or by the range foo[1,9]. Some examples of powerman targets follows: Power on hosts bar,baz,foo01,foo02,...,foo05 powerman --on bar baz foo[01-05] Power on hosts bar,foo7,foo9,foo10 powerman --on bar,foo[7,9-10] Power on foo0,foo4,foo5 powerman --on foo[0,4-5] As a reminder to the reader, some shells will interpret brackets ([ and ]) for pattern matching. Depending on your shell, it may be neces- sary to enclose ranged lists within quotes. For example, in tcsh, the last example above should be executed as: powerman --on "foo[0,4-5]" FILES
/usr/bin/powerman /usr/bin/pm ORIGIN
PowerMan was originally developed by Andrew Uselton on LLNL's Linux clusters. This software is open source and distributed under the terms of the GNU GPL. SEE ALSO
powerman(1), powermand(8), httppower(8), plmpower(8), vpcd(8), powerman.conf(5), powerman.dev(5), powerman-devices(7). http://sourceforge.net/projects/powerman powerman-2.3.5 2009-02-09 powerman(1)
All times are GMT -4. The time now is 01:29 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy