10-21-2009
Solved
Thanks for the 'simple' advise. Swap was indeed the problem, we upped it to twice the RAM size and I can now run 3 JBoss instances on the same Solaris 10 server.
Thanks jlliagre
9 More Discussions You Might Find Interesting
1. Solaris
Hi All ,
I try to install some packages in my global zone...
On the execution of the installion of the script it quits by saying the error
"Non global zone check failed"
Kindly help me in this regard
Thanks in advance,
jeganr (7 Replies)
Discussion started by: jegaraman
7 Replies
2. Solaris
Hi
i have created a solaris zone but have not yet connected any network cables for this new zone,
can i set the zone up without running the command 'add net' and not adding an ip or physical interface?
i tried to add dummy internet settings and get this
zonecfg:coddr> add net... (4 Replies)
Discussion started by: newbiesolaris10
4 Replies
3. Solaris
I have an old Sun SparcStation 5 that is running Sun OS 5.7, I'm not sure which commands would allow me to obtain the DNS zone transfer settings?
1.) I'm needing to know if the zone transfers are enabled.
2.) If it is enabled, does it transfer to specific servers
3.) If so, how do I go about... (1 Reply)
Discussion started by: Fhistleb
1 Replies
4. Solaris
I am using a solaris zone in Sun blade-T6320 which has a java version "1.5.0_18" i want to update it to 1.6.0.16 or higher , how can i do that , does i need to add the new java package to the global server or just instal it in the zone itself.
do i need to remove the older version or and install... (1 Reply)
Discussion started by: Sojourner
1 Replies
5. Solaris
Hi,
A quick question: Can Solaris 10 local zones be moved to a Solaris 11 global zone and work well?
Thank you in advance! (5 Replies)
Discussion started by: aixlover
5 Replies
6. UNIX for Advanced & Expert Users
Dear all,
recently, I migrated a solaris zone from one host to another. The zone was inside of a zpool. The zpool cotains two volumes.
I did the following:
host1:
$ zlogin zone1 shutdown -y -g0 -i0 #Zone status changes from running to installed
$ zpool export zone1
host2:
$ zpool... (2 Replies)
Discussion started by: custos
2 Replies
7. Solaris
Hi Gurus
I am not able to find the patching procedure for solaris 10 ( sol10 u11) to latest patchset with sun cluster having failover zones so that same I should follow.
Take an instance, there are sol1 and sol2 nodes and having two failover zones like sozone1-rg and sozone2-rg and currently... (1 Reply)
Discussion started by: nick101
1 Replies
8. Solaris
I am planning to do solaris 11 global zone patching having solaris 10 branded zone. I have a doubts on step 8 specially
Can someone clear my step 8 doubts or if anything wrong between step 1 to step 9 please correct that also as I have pretty good idea about Step 10 mean patching in solaris 10... (2 Replies)
Discussion started by: amity
2 Replies
9. Solaris
Hi, hoping someone can help, its been a while since I used Solaris.
After creating a NGZ (non global zone), the NGZ can access the GZ (Global Zone) and the GZ can access the NGZ (using ssh, zlogin)
However, the NGZ cannot access any other netwqork devices, it can't even see the default router
... (2 Replies)
Discussion started by: GazinLincoln
2 Replies
LEARN ABOUT SUNOS
list-instances
asadmin-list-instances(1AS) User Commands asadmin-list-instances(1AS)
NAME
asadmin-list-instances, list-instances - lists all the instances in the server
SYNOPSIS
list-instances [--user admin_user] [--password admin_password] [--host localhost] [--port 4848] [--domain domain_name] [--local=false]
[--passwordfile filename] [--secure|-s]
Use the list-instances to list all the instance in the server. The list-instances command can be run both locally and remotely. To list
remote instances, the named administration server must be running on the hostname and port number specified. The user authenticates using
the password identified for the administration server.
OPTIONS
--user administrative user associated for the instanace.
--password administrative password corresponding to the administrative user.
--host host name of the machine hosting the administrative instance.
--port port number associated with the administrative host.
--domain name of the domain.
--local determines if the command should delegate the request to administrative instance or run locally.
--passwordfile file containing passwords appropriate for the command (e.g., administrative instance).
--secure if true, uses SSL/TLS to communicate with the administrative instance.
Example 1: Using list-instances in local mode
asadmin> list-instances --domain1 --local
admin-server running
server1 running
Where: the server1 and admin-server instances for the domain1 domain is listed.
Example 2: Using list-instances in remote mode
asadmin> list-instances --user admin --passwordfile passwords.txt --host localhost --port 4848
server1 [mayank:80] running
Where: the server1 instance associated with the specified user, passwords, host, and port number specified is listed for the remote
machine.
EXIT STATUS
0 command executed successfully
1 error in executing the command
INTERFACE EQUIVALENT
Server Instance page
asadmin-show-instance-status(1AS)
J2EE 1.4 SDK March 2004 asadmin-list-instances(1AS)