Problems starting SunMC Agent 3.6 under Solaris 10

Hi folks,
I just did a test installation of the new SunMC 3.6 Server which worked fine. Afterwards, I did a fresh install of the 3.6 agent on a Sun Enterprise 420R running Solaris 10. I installed the agent in the global zone.
At the end of the setup, when the system asks me if I want to start the agent, which I affirmed. But this didn't work, system says just laconically "Could not start agent". Unfortunately, I can't even find the logs, since there is no log subdirectory under /var/opt/SUNWsymon. Have they moved this under Solaris 10?
Any ideas somebody how to dig into this?
Regards,
Peter

Hi Mike,
This sounds a lot like a post just a few days ago:
http://forum.sun.com/thread.jspa?threadID=27785&tstart=0Well, yes and no...I read this thread and I found some similarities but it's not the same problem. Besides, this was Solaris 8, I've 10 and my guess is that it has something to do with Sol10.
What do you see when you start the Agent with this command:
/opt/SUNWsymon/sbin/es-start -aiNo error...I end up in a prompt:
bash-3.00# /opt/SUNWsymon/sbin/es-start -ai
info Dec 05 17:48:19 agent Sun Management Center Version: 3.6, Build: 18, H491, (c) 2003 Sun Microsystems, Inc.
info Dec 05 17:48:19 agent registering import actions
info Dec 05 17:48:19 agent loading standard services
info Dec 05 17:48:19 agent standard services load complete
info Dec 05 17:48:19 agent agent host and port: cngaer:1161
info Dec 05 17:48:19 agent trap handler destination host and port: SunMC_server:162
info Dec 05 17:48:19 agent event trap destination host and port: SunMC_server:163
agent:>
I've really no idea what to enter at this prompt. A simple "help" doesn't give me anything but I got something from "ls"
agent:> ls
classes templates _config config services iso shadow contexts rules

Similar Messages

Problems starting Managed Server on WL6.0 Solaris

Hi,
I installed a WL6.0 on Solaris 8. Everythings works fine.
I careated a Domain and an additional Server wich is located at a
different machine. As is start this managed server on the other machine
it complains with the following error message:
<Aug 30, 2001 12:41:18 PM CEST> <Info> <Security> <Getting boot password
from user.>
Enter password to boot WebLogic server:weblogic
Starting WebLogic Server ....
Connecting to http://sol23:7001...
The WebLogic Server did not start up properly.
Exception raised:
weblogic.management.configuration.ConfigurationException: paros not
found
weblogic.management.configuration.ConfigurationException: paros not
found
at
weblogic.management.Admin.getBootstrapLocalServer(Admin.java:927)
at weblogic.management.Admin.initialize(Admin.java:287)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:317)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:169)
at weblogic.Server.main(Server.java:35)
Reason: Fatal initialization exception
In the access-Log of the Admin-Server the following line appears
my IP - - [30/Aug/2001:12:41:13 +0200] "GET
/wl_management_internal2/Bootstrap HTTP/1.0" 404 0
So my question: Where does this "wl_management_internal2" Application
come from?
Do I have to install some special things when I start an Admin-Server?
thanks
Falko Zurell . Webmaster
Pixelpark AG . http://www.pixelpark.com
Rotherstrasse 8 . 10245 Berlin . Germany
phone: + 49 30 5058 - 1963 . fax: -1600

Hi Falko,
This is not a problem. when you want to add a new managed server to the
admin server, you need to use weblogic console to create that server in the
admin server first, then start the managed server with that name to connect
to the admin server. That is like you have to let the admin server know
there is such a server, then let it join to the Admin server. you can do
that by using the admin console, from left panel, click on Servers -->
"Create a new server" and name it to be "paros", specify the port and IP.
and hit "create". then start the managed server.
Thanks
Yu
"Falko Zurell" <[email protected]> wrote in message
news:[email protected]...
Hi,
I installed a WL6.0 on Solaris 8. Everythings works fine.
I careated a Domain and an additional Server wich is located at a
different machine. As is start this managed server on the other machine
it complains with the following error message:
<Aug 30, 2001 12:41:18 PM CEST> <Info> <Security> <Getting boot password
from user.>
Enter password to boot WebLogic server:weblogic
Starting WebLogic Server ....
Connecting to http://sol23:7001...
The WebLogic Server did not start up properly.
Exception raised:
weblogic.management.configuration.ConfigurationException: paros not
found
weblogic.management.configuration.ConfigurationException: paros not
found
at
weblogic.management.Admin.getBootstrapLocalServer(Admin.java:927)
at weblogic.management.Admin.initialize(Admin.java:287)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:317)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:169)
at weblogic.Server.main(Server.java:35)
Reason: Fatal initialization exception
>
In the access-Log of the Admin-Server the following line appears
my IP - - [30/Aug/2001:12:41:13 +0200] "GET
/wl_management_internal2/Bootstrap HTTP/1.0" 404 0
So my question: Where does this "wl_management_internal2" Application
come from?
Do I have to install some special things when I start an Admin-Server?
thanks
Falko Zurell . Webmaster
Pixelpark AG . http://www.pixelpark.com
Rotherstrasse 8 . 10245 Berlin . Germany
phone: + 49 30 5058 - 1963 . fax: -1600

Problems starting node agent

I am trying to create a cluster of 2 Windows 2003 servers using enterprise edition 8.1 2005Q2 installations. I installed on one server and setup a domain and node agent, created a cluster and deployed my application. I tried to install a node agent only version on the other server, but it doesn't seem to exist, so I installed with domain administration server also. I deleted the node agent and recreated it pointing to the DAS on the other server. I got it to create, but I cannot start it. I get the message Password entered is invalid, even though I am entering the same password used to create it and the same password used as the master password. I've tried deleting and recreating the node agent and then I get the error failed to start and the log contains the error below. After that first time, I continue to get the password invalid message
[#|2006-11-29T16:34:06.281-0500|SEVERE|sun-appserver-ee8.1|javax.ee.enterprise.system.nodeagent|_ThreadID=10;|NAGT0014:Unexpected Node Agent exception.
java.lang.ExceptionInInitializerError
     at java.lang.Class.forName0(Native Method)
     at java.lang.Class.forName(Class.java:164)
     at com.sun.enterprise.pluggable.PluggableFeatureFactoryBaseImpl.invoke(PluggableFeatureFactoryBaseImpl.java:53)
     at $Proxy1.getSecuritySupport(Unknown Source)
     at com.sun.enterprise.security.SecurityUtil.getSecuritySupport(SecurityUtil.java:338)
     at com.sun.enterprise.ee.nodeagent.NodeAgent.initializeSecurity(NodeAgent.java:1125)
     at com.sun.enterprise.ee.nodeagent.NodeAgent.configureAgent(NodeAgent.java:1231)
     at com.sun.enterprise.ee.nodeagent.BaseNodeAgent.init(BaseNodeAgent.java:137)
     at com.sun.enterprise.ee.nodeagent.NodeAgent.synchronizeWithDASInternal(NodeAgent.java:545)
     at com.sun.enterprise.ee.nodeagent.NodeAgent.synchronizeWithDASInternal(NodeAgent.java:462)
     at com.sun.enterprise.ee.nodeagent.BaseNodeAgent.run(BaseNodeAgent.java:110)
     at com.sun.enterprise.ee.nodeagent.NodeAgentMain.startup(NodeAgentMain.java:149)
     at com.sun.enterprise.ee.nodeagent.NodeAgentMain.main(NodeAgentMain.java:190)
Caused by: java.lang.IllegalStateException: NSS password is invalid. Failed to authenticate to PKCS11 slot: internal
     at com.sun.enterprise.ee.security.EESecuritySupportImpl.<clinit>(EESecuritySupportImpl.java:148)
     ... 13 more
Message was edited by:
Envision
It turns out that the problem was related to the master password after all. Apparently the Windows Install doesn't set it, so it is left as adminadmin. Even after changing the master password, the node agent could not connect, because it needed the original password to connect first. If I changed the master password and re-created the node agent it works.

I am trying to create a cluster of 2 Windows 2003 servers using enterprise edition 8.1 2005Q2 installations. I installed on one server and setup a domain and node agent, created a cluster and deployed my application. I tried to install a node agent only version on the other server, but it doesn't seem to exist, so I installed with domain administration server also. I deleted the node agent and recreated it pointing to the DAS on the other server. I got it to create, but I cannot start it. I get the message Password entered is invalid, even though I am entering the same password used to create it and the same password used as the master password. I've tried deleting and recreating the node agent and then I get the error failed to start and the log contains the error below. After that first time, I continue to get the password invalid message
[#|2006-11-29T16:34:06.281-0500|SEVERE|sun-appserver-ee8.1|javax.ee.enterprise.system.nodeagent|_ThreadID=10;|NAGT0014:Unexpected Node Agent exception.
java.lang.ExceptionInInitializerError
     at java.lang.Class.forName0(Native Method)
     at java.lang.Class.forName(Class.java:164)
     at com.sun.enterprise.pluggable.PluggableFeatureFactoryBaseImpl.invoke(PluggableFeatureFactoryBaseImpl.java:53)
     at $Proxy1.getSecuritySupport(Unknown Source)
     at com.sun.enterprise.security.SecurityUtil.getSecuritySupport(SecurityUtil.java:338)
     at com.sun.enterprise.ee.nodeagent.NodeAgent.initializeSecurity(NodeAgent.java:1125)
     at com.sun.enterprise.ee.nodeagent.NodeAgent.configureAgent(NodeAgent.java:1231)
     at com.sun.enterprise.ee.nodeagent.BaseNodeAgent.init(BaseNodeAgent.java:137)
     at com.sun.enterprise.ee.nodeagent.NodeAgent.synchronizeWithDASInternal(NodeAgent.java:545)
     at com.sun.enterprise.ee.nodeagent.NodeAgent.synchronizeWithDASInternal(NodeAgent.java:462)
     at com.sun.enterprise.ee.nodeagent.BaseNodeAgent.run(BaseNodeAgent.java:110)
     at com.sun.enterprise.ee.nodeagent.NodeAgentMain.startup(NodeAgentMain.java:149)
     at com.sun.enterprise.ee.nodeagent.NodeAgentMain.main(NodeAgentMain.java:190)
Caused by: java.lang.IllegalStateException: NSS password is invalid. Failed to authenticate to PKCS11 slot: internal
     at com.sun.enterprise.ee.security.EESecuritySupportImpl.<clinit>(EESecuritySupportImpl.java:148)
     ... 13 more
Message was edited by:
Envision
It turns out that the problem was related to the master password after all. Apparently the Windows Install doesn't set it, so it is left as adminadmin. Even after changing the master password, the node agent could not connect, because it needed the original password to connect first. If I changed the master password and re-created the node agent it works.

How to start ftp under solaris 10

Hi,
if I try to enable ftp under Solaris 10, I get the message "unsatisfied dependencies":
root@u015ad2a:.../>svcadm -v enable -rst svc:/network/ftp:default
svc:/network/ftp:default temporarily enabled.
svc:/network/inetd:default temporarily enabled.
svc:/network/loopback temporarily enabled.
svc:/system/filesystem/local temporarily enabled.
svc:/milestone/single-user temporarily enabled.
svc:/system/identity:node temporarily enabled.
svc:/system/filesystem/minimal temporarily enabled.
svc:/system/filesystem/usr temporarily enabled.
svc:/system/filesystem/root temporarily enabled.
svc:/system/device/local temporarily enabled.
svc:/milestone/devices temporarily enabled.
svc:/system/manifest-import temporarily enabled.
svc:/milestone/sysconfig temporarily enabled.
svc:/milestone/name-services temporarily enabled.
svcadm: Instance "svc:/network/ftp:default" has unsatisfied dependencies.
root@u015ad2a:.../>svcs svc:/network/ftp:default
STATE STIME FMRI
uninitialized 9:40:09 svc:/network/ftp:default
How can I enable ftp?

This looks sort of like what happened to me just now. I tried svcs -x
and got:
# svcs -x
svc:/network/rpc/gss:default (Generic Security Service)
State: uninitialized since Mon Apr 18 13:01:12 2005
Reason: Restarter svc:/network/inetd:default has not initialized service state.
See: http://sun.com/msg/SMF-8000-4D
See: gssd(1M)
Impact: 10 dependent services are not running. (Use -v for list.)
svc:/network/service:default (layered network services)
State: offline since Mon Apr 18 13:01:29 2005
Reason: Start method is running.
See: http://sun.com/msg/SMF-8000-C4
See: ifconfig(1M)
See: /var/svc/log/network-service:default.log
Impact: 4 dependent services are not running. (Use -v for list.)
svc:/application/print/server:default (LP print server)
State: disabled since Mon Apr 18 13:01:12 2005
Reason: Disabled by an administrator.
See: http://sun.com/msg/SMF-8000-05
See: lpsched(1M)
Impact: 1 dependent service is not running. (Use -v for list.)
I tried all kinds of things to get gss to run, but I finally realized that
it was really ifconfig that was the problem. The system has two
network interfaces, and during installation I gave both of them
a name. However, hme1 was not really connected to anything.
All I did to get it to work was
# cd /etc
# mv hostname.hme1 no.hme1
After that, I rebooted, and everything came up OK. I don't know
if the original problem was the same, but this solved my problem.

Problem using agent-update.bin to roll out SunMC agents

Greetings,
I want to use agent-update.bin to roll out SUNMC agents to solaris 9 and 10 hosts. I use the es-agentupdate.sh tool to create the installation package and the seed file on the SunMC server in /var/opt/SUNWsymon/agentupdate.
I copy the binary /opt/SUNWsymon/base/bin/agent-update.bin to the root on a test server.
I run the following commands - each fails - unable to find the seed file. Can anyone suggest an -f argument which might work as I need the rollout to occur without user intervention to enter secrets.
./agent-update.bin -s oranc1 -r 8080 -p DPI_BasicAgent -f seed-file
or
./agent-update.bin -s oranc1 -r 8080 -p DPI_BasicAgent -f ./seed-file
or
./agent-update.bin -s oranc1 -r 8080 -p DPI_BasicAgent -f /var/opt/SUNWsymon/agentupdate/seed-file
Standard out from the last of these commands is as follows:
sbin_archive downloaded
SUNWessmu package installed
Running InstallClient : /tmp/agentupdate/DPI_BasicAgent/bin/sparc-sun-solaris/InstallClient -s oranc1 -p 8080 -u DPI_BasicAgent/upgrade-policy_sparc.xml -f /var/opt/SUNWsymon/agentupdate/seed-file
InstallClient started
upgrade policy downloaded
Argument file /var/opt/SUNWsymon/agentupdate/seed-file absent. Exiting...
Error: running InstallClient
Error: running InstallClient with error code 1
ERROR: information for "SUNWescom" was not found
ERROR: information for "SUNWescom" was not found
On the SUNMC server:
root@oranc1# pwd
/var/opt/SUNWsymon/agentupdate
root@oranc1# ls -l
total 6
drwxr-xr-x 4 root root 512 Feb 5 13:59 DPI_BasicAgent
-rw------- 1 root root 54 Nov 23 13:44 seed-file
drwxr-xr-x 4 root root 1024 Nov 23 12:46 SunMC36_Generic
I have also tried
-r-------- 1 root root 54 Nov 23 13:44 seed-file
Thanks in advance for your help
Tony

Greetings Mike,
I copied the seed-file from my SUNMC server to the host being updated and put it in the same directory as agent-update.bin. Ran the following:
./agent-update.bin -s oranc1 -r 8080 -p DPI_BasicAgent -s ./seed-file
The result is:
Error: getting sbin_archive
Web server is listening on port 8080 and accessible through a browser. Agent package directory name and seedfile name are OK.
any additonal help appreciated.
Regards
Tony

Problems starting WLS 6.1 on solaris...

I have installed WLS in the sun solaris machine and have problems starting up a mydomain
test server. I am getting:
weblogic.management.configuration.ConfigurationException: - with nested exception:
[weblogic.security.internal.FileUtilsException: couldn't create temporary file for
SerializedSystemIni.dat, .new, /config/mydomain - with nested exception:
[java.io.IOException: No such file or directory]]
I am suspecting the problem might be that we have installed it as root and then change
the rights to weblogic. Any pointers are greatly appreciated.
Thanks.

I'm guess you changed owner of config/mydomain to weblogic? To
confirm - try touching/create a test file in config/mydomain,
i.e. touch mytest.perm;ls -l mytest.perm;rm mytest.perm
You could start weblogic with truss:
truss -t open -o /tmp/truss.out -f "your start command"
Then examine /tmp/truss.out
"Dariusz" <[email protected]> wrote in message news:<3d08b130$[email protected]>...
I have installed WLS in the sun solaris machine and have problems starting up a mydomain
test server. I am getting:
weblogic.management.configuration.ConfigurationException: - with nested exception:
[weblogic.security.internal.FileUtilsException: couldn't create temporary file for
SerializedSystemIni.dat, .new, /config/mydomain - with nested exception:
[java.io.IOException: No such file or directory]]
I am suspecting the problem might be that we have installed it as root and then change
the rights to weblogic. Any pointers are greatly appreciated.
Thanks.

Problem starting the oem agent

the agent ran when i configured it with the installation gui. now i need to restart itmanually. This is not on the grid control server.
databasE: 10.1.0.3
oem: 10.2.0.5
solaris
I am in my $AGENT_HOME/bin
oracle(eradev) 24> emctl start agent
EM Configuration issue. /opt/oracle/product/10.1.0.3/myserver.com_mydev not found.
The directory show is the oracle home of the database that is currently set to the ORACLE_SID.
I tried using the emca, but that seems to configure for stand alone OEM. I need to start an agent to communicate with my Grid Control OMS.
Edited by: Guess2 on Sep 10, 2009 7:26 AM

Try this:
$ cd $AGENT_HOME/bin
$ ./emctl start agent:p

NIC install problem under Solaris 10

I have an old 3Com NIC card (ISA) under Solaris 10. 3C509B Etherlink III card and prtconf -pv command shows correct PNP80f7 device id, all correct
resources, IRQ, I/O address .... But fail to work. Is it sun does not support elx driver or something I misconfigured?
My installation as follows:
elx "PNP80F7" entry to /etc/driver_aliases
PNP80F7|TCM5094.... elx net isa elx.bef "3Com"
entry to /boot/solaris/devicedb/master
#devlinks
#touch reconfigure ; reboot

I use these cards for my x86 installations as well. The one thing that I've had to do is force the speed and duplex using the 3Com driver diskettes before installing the operating system. For whatever reason, Solaris 10 finds the card but will not initialize it properly whenever I the card is programmed to auto-negotiate. Forcing the card to half-duplex on the card itself works almost all of the time for me.
Get the driver diskettes from 3Com's site, boot from a bootable floppy, run 3c9x5cfg (if I recall correctly), and change the duplex and speed to whatever is appropriate. I've had the best luck with half-duplex. (If you need a boot diskette, you can get them from http://www.bootdisk.com.)

Compile occi under solaris using g++/gcc problem

Hi Expert:
I got some link error when i tried to compile a demo occi code under solaris using g++. Please share experience.
Thanks.

Namespaces are not supported in -compat=4 mode. The only effect of -features=namespace is to recognize "namespace" as a keyword, and disallow it as an identifier. You don't actually get namespace semantics.
The pupose of -compat=4 is to allow code written for C++ 4.x to compile and run until the code can be updated to conform to the C++ Standard. If you want to use features from the C++ standard, like namespaces, you must use Sun C++ in the default standard mode.
If you remove -compat=4, the code compiles and links. If you need to use -compat=4 mode, remove uses of namespace, and fix the code to remove name conflicts.
BTW, we recommend against using -features=bool in -compat=4 mode. It can cause odd behavior when part of the code expects boolean expressions to have type int and part of the code expects bool to be a different type.
It appears you are using C++ 5.0, a product that has been obsolete for several years and which is no longer supported. You should consider updating to Sun Studio 11 (C++ 5.8), at no cost.
http://developers.sun.com/sunstudio/

Unable to Start OracleAgent for Cache connect on Solaris 9

Please see below for configuration details. TimesTen 6.1 installed on Solaris 9 with access control enabled. DSN is defined in sys.odb.ini file under install_dir/info directory.
unable to start cache agent either with ttAdmin or with ttIsql. Error messages is as below. Please help!!
DSN defined in sys.odbc.ini
[ATS_tt60demo1]
Driver=/u03/TimesTen/tt60demo1/lib/libtten.so
DataStore=/u03/TimesTen/tt60demo1/info/DemoDataStore/ATSdemo1data
ExclAccess=0
Logging=1
#LogPurge=1
PermSize=16
ThreadSafe=1
Isolation=1
WaitForConnect=0
Authenticate=0
#LockLevel=0
UID=scott
OracleID=atsdev
OraclePWD=tiger
PassThrough=0
environment Variables
SSH_TTY=/dev/pts/3
PATH=/u03/TimesTen/tt60demo1/bin:/u03/TimesTen/tt60demo1/demo:/u03/TimesTen/tt60demo1/demo/ttclasses:/u03/TimesTen/tt60demo1/demo/xlaPersistent:/u03/TimesTen/tt60demo1/demo/tutorial/java:/u03/TimesTen/tt60demo1/3rdparty/ant/bin:.:/usr/bin:/usr/ucb:/usr/local/bin:/tools/bin:/tools/pvcs:/export/home/timesten/bin:/usr/xpg4/bin:/bin:/usr/sbin:/etc:/sbin:/u03/app/product/10.2.0/Db_1/bin
ORACLE_BASE=/u03/app/product
EDITOR=vi
HISTFILE=/export/home/timesten/.hist4229
CLASSPATH=/u03/TimesTen/tt60demo1/lib/classes14.jar:/u03/TimesTen/tt60demo1/lib/timestenjmsxla.jar:/u03/TimesTen/tt60demo1/3rdparty/jms1.1/lib/jms.jar:/u03/TimesTen/tt60demo1/demo:/u03/TimesTen/tt60demo1/demo/tutorial/java:/u03/TimesTen/tt60demo1/demo/tutorial/java/dist/lib/TimesTenJavaDemos.jar
LOGNAME=timesten
HOSTNAME=ncnc-sun5
PVCS_BINDIR=/tools/pvcs
ORACLE_SID=atsdev
PS1=${LOGNAME}@${HOSTNAME}:$PWD>
PS2=>>
USER=timesten
XMINCLUDE=/usr/dt/include
SHELL=/bin/ksh
HOME=/export/home/timesten
XFILESEARCHPATH=/usr/openwin/lib/%T/%N/%S:/usr/openwin/lib/%T/%N/%S
XMLIB=/usr/dt/lib
ANT_HOME=/u03/TimesTen/tt60demo1/3rdparty/ant
SSH_CLIENT=138.1.113.119 1178 22
LD_LIBRARY_PATH=/u03/TimesTen/tt60demo1/lib:/usr/openwin/lib:/usr/dt/lib:/usr/lib:/lib:/tools/lib:/u03/app/product/10.2.0/Db_1/lib:/u03/app/product/10.2.0/Db_1/network/lib
TERM=xterm
ORACLE_HOME=/u03/app/product/10.2.0/Db_1
THREADS_FLAG=native
PWD=/u03/TimesTen/tt60demo1/info
TZ=US/Eastern
ENV=/export/home/timesten/.kshrc
timesten@ncnc-sun5:/u03/TimesTen/tt60demo1/info> ttisql ATS_tt60demo1
Copyright (c) 1996-2005, Oracle. All rights reserved.
Type ? or "help" for help, type "exit" to quit ttIsql.
All commands must end with a semicolon character.
connect "DSN=ATS_tt60demo1";
Enter password for 'scott':
Connection successful: DSN=ATS_tt60demo1;UID=scott;DataStore=/u03/TimesTen/tt60demo1/info/DemoDataStore/ATSdemo1data;WaitForConnect=0;DRIVER=/u03/TimesTen/tt60demo1/lib/libtten.so;OracleId=atsdev;Authenticate=0;PermSize=16;
(Default setting AutoCommit=1)
Command> call ttCacheUidPwdSet('scott','tiger');
Command> call ttCacheStart();
10024: Could not start Oracle Agent for the requested data store.. Could not initialize OCI function pointers. Error: none
The command failed.
Command>exit
Disconnecting..
Done.

Solved the problem myself. Had to stop and restart cache agent using the timesten software installation account and not as root.
Documentation is not clear as to what happens when you install timesten using a "non root" account. Per documentation, we have to run setuproot script to create startup / stop scripts under init directory. With a non-root installation these scripts are created and on reboot agent process inherits the root account privs. This is a problem. For a non-root install the agent process should inherit the privs of the account that performed the installation and not root's.
May be a documentation correction is needed here.

Problem with the Agent

Following a problem I had with saving to a shared location on windows nt using RMAN. (see note 145843.1 in metalink, also see bottom of this text)
When I got to the stage of assigning the service to the domain administrator the agent failed. Can anyone shed any light on the situation on to why it is doing whats its doing.
Thanks to all
Note 145843.1
Doc ID: Note:145843.1 Type: BULLETIN
Last Revision Date: 21-OCT-2005 Status: PUBLISHED
PURPOSE
Following are step-by-step instructions for configuring RMAN to write
to mapped (shared/networked) drive(s) on Windows NT, 2000 or 2003.
SCOPE & APPLICATION
RMAN users who are familiar with basic RMAN functionality
as well as database configuration on the Windows Platform.
WRITING FILES TO A MAPPED DRIVE WITH RMAN
The problem of backing up to a mapped network drive using the SYSTEM account
is a security issue. By default, Oracle requires the SYSTEM user to have
privileges to write to the drives. Microsoft considers granting SYSTEM owned
service access to a shared drive a security issue.
However, there is a workaround that allows Oracle to access a shared drive.
The Oracle services are originally configured to log on using the SYSTEM
account. The SYSTEM account should not be granted access to the shared drive,
therefore the Oracle services for the TARGET DB need to be reconfigured to
logon using an Administrator account (preferably a Domain Administrator).
THE STEPS NEEDED TO RESOLVE THIS ISSUE
1. On the machine where you wish to write the files to, create a shared drive
granting the user 'Administrator' FULL Control.
Note: For reference below, this Administrator will use the password 'test',
this will be referred to as the "Destination" machine.
2. On the machine with the TARGET DB, verify the Administrator user has the
same password of the user that shared the drive on the destination machine.
In the example here, the password would be 'test'.
3. Map a network drive on the TARGET machine to the shared drive on the
destination machine. When mapping this drive, use the Administrator
user with the password 'test'.
4. On the TARGET machine, BOTH the OracleTNSListener Service and the
OracleService<SID> services must be configured to start using the
Administrator/test account.
(As discussed above, Oracle uses the Local System account by default.)
a. Go to the Control Panel and then open up the Services panel.
b. Double click on the appropriate service
(TNSListener or OracleService<SID>).
c. Change the "Log on as" user from the "Local System Account" to
ShowDoc https://metalink.oracle.com/metalink/plsql/f?p=130:14:176254058330...
2 of 3 12/06/2008 08:48
"This Account".
d. Specify the service to log on as the Administrator user.
c. Click on "OK".
5. Shutdown the TARGET database and stop and start the services on the Target
machine. Restart the TARGET database.
6. You should now be able to use RMAN from the Catalog machine to copy the
datafiles. In the RMAN script, specify the drive letter that you mapped
in step 3.
Special Windows 2003 Update :
As Windows 2003 has a changed access behavior compared to Windows 2000,
the solution is a little restrict :
Don't use local drive letters for mapping network shares.
Workaround is to use UNC locations directly, e.g. backup to \\B\share
Since this is in fact an absolute location this is always the same for any
node in the network.
So whether accessed from node A or node B, \\B\share is always the shared
location on B.
FINAL NOTES
It is recommended to use the Domain Administrator account to ensure that
passwords are the same across the various machines. If there is no domain,
use the local Administrator account and ensure that the passwords are the same
for this account across all of the machines.
If your backups are to be automated using the AT command, it is best to start
up the SCHEDULE service under the same Administrator account that the
OracleService<SID> and the OracleTNSListener services use.
In the event that you HAVE to use a user account for the Oracle Services,
rather then using the SYSTEM account, you can create a batch file that
reconnects the shared drives at system startup. The batch file runs
automatically as a service when the server starts and would establish the
connection to the shared drives, regardless of which user logs into the
system. This process of creating the batch file is outlined in the Microsoft's
Knowledgebase article Q243486 - "How to Run a Batch File Before Logging on
to Your Computer." The batch file is not supported by Oracle and is only
mentioned here as an alternative way to reconnect the shared drives.
COMMON MISTAKES
If the OracleService<SID> and OracleTNSListener services are not configured
to use the same account as the shared drive, you can expect the following
errors:
RMAN-10035: exception raised in RPC: ORA-19504: failed to create file
"<file name>"
ORA-27040: skgfrcre: create error, unable to create file
OSD-04002: unable to open file
O/S-Error: (OS 5) Access is denied.
ORA-19600: input file is datafile 1(<path and file name of Datafile 1>)
ORA-19601: output file is datafile-copy 0(<path and file name of file
to be created>)
RMAN-10031: ORA-19624 occurred during call to
DBMS_BACKUP_RESTORE.COPYDATAFILE
If the mapped drive is created on the CATALOG machine and NOT on the TARGET
machine, you can expect the following errors.
RMAN-10035: exception raised in RPC: ORA-19504: failed to create file
"<file name>"
ORA-27040: skgfrcre: create error, unable to create file
OSD-04002: unable to open file
O/S-Error: (OS 3) The system cannot find the path specified.
ORA-19600: input file is datafile 1 (<path and file name of Datafile 1>)
ORA-19601: output file is datafile-copy 0 (<path and file name of file to
be created>)
RMAN-10031: ORA-19624 occurred during call to
DBMS_BACKUP_RESTORE.COPYDATAFILE

If there's more information required, Please do not hesitate to send a post. I check this post Daily.

Cannot stop and start CCMS agent

Hi experts,
I'm new to SAP and here we have problem on sapccmsr agent not running. Previously the sapccmsr was running fine until one day it is not. When i tried to start the application, it says that theres another CCMS agent running with the profile:
bcuser> code/libs/sapccmsr -DCCMS pf=saploc/oscol.pfl
INFO: CCMS agent sapccmsr working directory is /sbdc/sapbc47/Server/packages/SAPMonitoring/saploc/PRFCLOG/sapccmsr
INFO: CCMS agent sapccmsr config file is /sbdc/sapbc47/Server/packages/SAPMonitoring/saploc/PRFCLOG/sapccmsr/csmconf
INFO: Central Monitoring System is [M04]. (found in config file)
INFO: Checking shared memory status of sapccmsr
Another CCMS Agent is already running with this profile.
EXITING with code 0
bcuser> ps -ef | grep sapccmsr | grep -v grep
bcuser>
And when i tried to stop the sapccmsr manually, it failed:
bcuser> code/libs/sapccmsr -stop pf=saploc/oscol.pfl
INFO: CCMS agent sapccmsr working directory is /sbdc/sapbc47/Server/packages/SAPMonitoring/saploc/PRFCLOG/sapccmsr
INFO: CCMS agent sapccmsr config file is /sbdc/sapbc47/Server/packages/SAPMonitoring/saploc/PRFCLOG/sapccmsr/csmconf
INFO: Setting Stop Flag for sapccmsr
INFO: Waiting for background process to stop...
INFO: Background process has not stopped after 10 seconds.
INFO: Process might be busy..
INFO: Please try again.
EXITING with code -1
bcuser>
Yeah i think it is because there is no sapccmsr processes running!
My question is; how to force the sapccmsr to start? I already delete the sapccmsr.pid but no success.
The last resort would be to restart the box but unfortunately, thats not the feasible option... for the time being...
Please help....
Thanks in advance

try to execute execute ./sapccmsr pf=/usr/sapSID/SYS/profile/PROFILE -j2ee -initshm
filter on
INFO: Attached to Shared Memory Key 73 (size 60000000), no pool used
so you see the size of the shared memory is 60000000
then execute on solaris
ipcs -ma |grep 60000000
this will result in keys with size 60000000
m 108039 0x4761 rw-r--- eppadm sapsys eppadm sapsys 1 60000000 4955 20441 11:40:28 11:40:28 8:30:38
m 5744 0x3d9d rw-r--- yppadm sapsys yppadm sapsys 1 60000000 29224 29224 15:22:23 15:22:24 15:22:23
m 30323 0x3f91 rw-r--- yppadm sapsys yppadm sapsys 1 60000000 29480 29480 15:22:33 15:22:35 15:22:33
m 150522485 0x46fd rw-r--- eppadm sapsys eppadm sapsys 4 60000000 21181 5909 12:05:31 12:05:31 17:03:39
in this case there are 4 with size 60000000 our instance EPP both ccms agents had a problem so we cleaned those 2 entries
ipcrm -m 108039 -m 150522485
afterwards the agents were able to start

Swedish chars �� not working under Solaris

Hi All,
I created the following little code and it is not working under Solaris 7, JDK1.4.1_01. (also tested some other but does not work)
public class HelloSweden
public static void main(String [] args)
String newName="��";
String charsetName = "iso-8859-2";
byte [] s = {(byte)229, (byte)228, (byte)246};
try
newName = new String(s, 0, s.length, charsetName);
catch ( java.io.UnsupportedEncodingException e )
System.err.println(e.getMessage());
e.printStackTrace();
System.out.println("new name is: "+newName);
for(int i=0; i<newName.getBytes().length; i++)
System.out.println(i+"."+":"+newName.getBytes());
The problem is that on Solaris 7 the output is:
new name is: ???
0.:63
1.:63
2.:63
Whereas on Linux it works fine:
new name is: ��
0.:-27
1.:-28
2.:-10
I also tried the "javac -encoding iso8859-1" option but no use.
Could anybody help?
Thnx,
GF

I also tried the "javac -encoding iso8859-1" option
but no use.
Was the output exactly the same or were the numbers correct, at least?
You may need to compile with:
javac -encoding ISO-8859-1 ClassName.java
and then run with:
java -Dfile.encoding=ISO-8859-1 ClassName
You can set the character encoding explicitely like that. The character encoding depends on locale settings; if you set LC_ALL to a Swedish locale ("sv_SE"?) javac and java should start using the correct encodings automatically.

Does SunMC agent need SNMP packages

I'm configuring JASS (Security Toolkit) to run on newly jumpstarted machines and wanted to run the finish script: disable-snmp, but wasn't sure if SunMC needed to have these packages installed in order to run. I currently am at 3.0 but will be upgrading to 3.5. I have not run JASS on our current SunMC agents yet, but they do have these installed? How can I find out what packages SunMC needs?
SUNWsacom
SUNWmibii
SUNWsasnm
SUNWsasnx

I'm configuring JASS (Security Toolkit) to run on
newly jumpstarted machines and wanted to run the
finish script: disable-snmp, but wasn't sure if SunMC
needed to have these packages installed in order to
run. I currently am at 3.0 but will be upgrading to
3.5. I have not run JASS on our current SunMC agents
yet, but they do have these installed? How can I find
out what packages SunMC needs?SunMC 3.0 and 3.5 do not need any existing Solaris SNMP packages. SunMC comes with its own SNMP Agents (ps -ef | grep esd | grep agent). In fact most people disable the SNMP daemon that comes with current versions of Solaris ("snmpdx" process) and disable its start script (/etc/rc3.d/S76snmpdx) .. so that SunMC can take over the default SNMP port (161).
Are you removing packages for security reasons? Is your environment critical enough you cannot simply disable unused services (like snmpdx)?
Regards,
Aronek
Standard disclaimer: I am an employee of Halcyon (www.HalcyonInc.com)

Problem starting logical host on eGate 5.1.0

I'm having problem starting logical host for eGate 5.1.0 on Linux platform, and I cant see where is the problem lies. Is there anybody here that can give me some hint or guide?
Below is the error message from the log.
[#|2006-08-22T17:57:28.506+0800|WARNING|IS5.1|javax.enterprise.resource.jms|_ThreadID=11; ThreadName=STCMS process monitoring;|STCMS process ended unexpectedly with exit code 1; initiating application server restart|#]
[#|2006-08-22T17:57:28.567+0800|INFO|IS5.1|javax.enterprise.system.core|_ThreadID=11; ThreadName=STCMS process monitoring;|sending restart notification to server...server|#]
[#|2006-08-22T17:57:28.721+0800|WARNING|IS5.1|javax.enterprise.system.tools.admin|_ThreadID=12; ThreadName=RMI TCP Connection(1)-127.0.0.1;|core.tmp_folder_deletion_failed|#]
[#|2006-08-22T17:57:28.722+0800|INFO|IS5.1|javax.enterprise.resource.jms|_ThreadID=12; ThreadName=RMI TCP Connection(1)-127.0.0.1;|stcms.alert_shutting_down|#]
[#|2006-08-22T17:57:28.722+0800|INFO|IS5.1|javax.enterprise.resource.jms|_ThreadID=12; ThreadName=RMI TCP Connection(1)-127.0.0.1;|stcms.broker_shutting_down|#]
[#|2006-08-22T17:57:31.020+0800|INFO|IS5.1|javax.enterprise.system.container.web|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;|Creating virtual server server|#]
[#|2006-08-22T17:57:31.039+0800|INFO|IS5.1|javax.enterprise.system.core|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;|IS AVK Instrumentation disabled|#]
[#|2006-08-22T17:57:31.045+0800|INFO|IS5.1|javax.enterprise.system.core.security|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;|SEC1143: Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper.|#]
[#|2006-08-22T17:57:31.117+0800|INFO|IS5.1|javax.enterprise.system.core|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;|[STC JTS Extension] The last agent commit optimization is enabled.|#]
[#|2006-08-22T17:57:32.315+0800|INFO|IS5.1|com.stc.corba.any.UtilDelegate|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;|[STC CORBA Extension]EE/SE Corba Util delegate loaded|#]
[#|2006-08-22T17:57:33.730+0800|INFO|IS5.1|com.stc.corba.any.UtilDelegate|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;|[STC CORBA Extension]Enabling SE Corba support|#]
[#|2006-08-22T17:57:34.007+0800|SEVERE|IS5.1|javax.enterprise.system.core|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;|CORE5082: Exception running j2ee services: [java.lang.RuntimeException: java.lang.ExceptionInInitializerError]|#]
[#|2006-08-22T17:57:34.008+0800|SEVERE|IS5.1|javax.enterprise.system.core|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;stacktrace-id=0;|CORE5091: Error executing J2EE server ...
java.lang.RuntimeException: java.lang.ExceptionInInitializerError
     at com.sun.enterprise.server.J2EEServer.run(J2EEServer.java:351)
     at com.sun.enterprise.server.J2EEServer.main(J2EEServer.java:754)
     at com.sun.enterprise.server.ApplicationServer.onInitialization(ApplicationServer.java:233)
     at com.sun.enterprise.server.PEMain.run(PEMain.java:222)
     at com.sun.enterprise.server.PEMain.main(PEMain.java:186)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
Caused by: java.lang.RuntimeException: java.lang.ExceptionInInitializerError
     at com.sun.enterprise.server.ServerContextImpl.getMonitoringRegistry(ServerContextImpl.java:374)
     at com.sun.enterprise.iiop.ORBMonitoring.<init>(ORBMonitoring.java:48)
     at com.sun.enterprise.server.J2EEServer.run(J2EEServer.java:236)
     ... 9 more
Caused by: java.lang.ExceptionInInitializerError
     at java.lang.Class.forName0(Native Method)
     at java.lang.Class.forName(Class.java:164)
     at com.sun.enterprise.server.ServerContextImpl.getMonitoringRegistry(ServerContextImpl.java:368)
     ... 11 more
Caused by: java.lang.NullPointerException: No MBeanServer was returned by the MBeanServerFactory
     at com.sun.enterprise.admin.monitor.registry.spi.MonitoringRegistrationHelper.getMBeanServer(MonitoringRegistrationHelper.java:83)
     at com.sun.enterprise.admin.monitor.registry.spi.MonitoringRegistrationHelper.<init>(MonitoringRegistrationHelper.java:60)
     at com.sun.enterprise.admin.monitor.registry.spi.MonitoringRegistrationHelper.<clinit>(MonitoringRegistrationHelper.java:55)
     ... 14 more
|#]
[#|2006-08-22T17:57:34.012+0800|SEVERE|IS5.1|javax.enterprise.system.core|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;|CORE5092: J2EE server reported following error: [java.lang.ExceptionInInitializerError] |#]
[#|2006-08-22T17:57:34.012+0800|SEVERE|IS5.1|javax.enterprise.system.core|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;|CORE5093: Error executing J2EE server |#]
[#|2006-08-22T17:57:34.013+0800|SEVERE|IS5.1|javax.enterprise.system.core|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;stacktrace-id=1;|CORE5071: An error occured during initialization
com.sun.appserv.server.ServerLifecycleException: com.sun.appserv.server.ServerLifecycleException: java.lang.ExceptionInInitializerError
     at com.sun.enterprise.server.ApplicationServer.onInitialization(ApplicationServer.java:235)
     at com.sun.enterprise.server.PEMain.run(PEMain.java:222)
     at com.sun.enterprise.server.PEMain.main(PEMain.java:186)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
Caused by: com.sun.appserv.server.ServerLifecycleException: java.lang.ExceptionInInitializerError
     at com.sun.enterprise.server.J2EEServer.main(J2EEServer.java:763)
     at com.sun.enterprise.server.ApplicationServer.onInitialization(ApplicationServer.java:233)
     ... 7 more
Caused by: java.lang.RuntimeException: java.lang.ExceptionInInitializerError
     at com.sun.enterprise.server.J2EEServer.run(J2EEServer.java:351)
     at com.sun.enterprise.server.J2EEServer.main(J2EEServer.java:754)
     ... 8 more
Caused by: java.lang.RuntimeException: java.lang.ExceptionInInitializerError
     at com.sun.enterprise.server.ServerContextImpl.getMonitoringRegistry(ServerContextImpl.java:374)
     at com.sun.enterprise.iiop.ORBMonitoring.<init>(ORBMonitoring.java:48)
     at com.sun.enterprise.server.J2EEServer.run(J2EEServer.java:236)
     ... 9 more
Caused by: java.lang.ExceptionInInitializerError
     at java.lang.Class.forName0(Native Method)
     at java.lang.Class.forName(Class.java:164)
     at com.sun.enterprise.server.ServerContextImpl.getMonitoringRegistry(ServerContextImpl.java:368)
     ... 11 more
Caused by: java.lang.NullPointerException: No MBeanServer was returned by the MBeanServerFactory
     at com.sun.enterprise.admin.monitor.registry.spi.MonitoringRegistrationHelper.getMBeanServer(MonitoringRegistrationHelper.java:83)
     at com.sun.enterprise.admin.monitor.registry.spi.MonitoringRegistrationHelper.<init>(MonitoringRegistrationHelper.java:60)
     at com.sun.enterprise.admin.monitor.registry.spi.MonitoringRegistrationHelper.<clinit>(MonitoringRegistrationHelper.java:55)
     ... 14 more
|#]
[#|2006-08-22T17:57:34.023+0800|SEVERE|IS5.1|javax.enterprise.system.core|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;|Server Startup failed. Exiting...|#]
[#|2006-08-22T17:57:34.023+0800|INFO|IS5.1|javax.enterprise.system.core|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;|Server shutdown in progress...|#]
[#|2006-08-22T17:57:34.024+0800|INFO|IS5.1|javax.enterprise.system.container.web|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;|WEB0303: Stopping Tomcat.|#]
[#|2006-08-22T17:57:34.025+0800|WARNING|IS5.1|javax.enterprise.system.core|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;stacktrace-id=2;|CORE5061: Exception :
com.sun.appserv.server.ServerLifecycleException: WEB0106: An error occurred while stopping the web container
     at com.sun.enterprise.web.PEWebContainer.stopInstance(PEWebContainer.java:536)
     at com.sun.enterprise.web.PEWebContainerLifecycle.onShutdown(PEWebContainerLifecycle.java:65)
     at com.sun.enterprise.server.ApplicationServer.onShutdown(ApplicationServer.java:400)
     at com.sun.enterprise.server.PEMain.run(PEMain.java:255)
     at com.sun.enterprise.server.PEMain.main(PEMain.java:186)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
Caused by: LifecycleException: WEB0103: This web container has not yet been started
     at com.sun.enterprise.web.WebContainer.stop(WebContainer.java:529)
     at com.sun.enterprise.web.PEWebContainer.stopInstance(PEWebContainer.java:528)
     ... 9 more
|#]
Hopefully somebody can help me as I'm stuck with it for few days already. Thank you.

This is what I got when I try to start the server from the directory logicalhost/is/domains/domain1/bin/
./startservAug 23, 2006 7:23:55 PM com.stc.is.util.pinger.HttpOKPinger <init>
INFO: Setting URL to http://localhost:18000
Aug 23, 2006 7:23:55 PM com.stc.is.util.pinger.HttpOKPinger isAlive
INFO: Opening connection to http://localhost:18000
Aug 23, 2006 7:23:55 PM com.stc.is.util.pinger.HttpOKPinger isAlive
INFO: Connection to http://localhost:18000 opened successfully.
Aug 23, 2006 7:23:55 PM com.stc.is.util.pinger.HttpOKPinger isAlive
SEVERE: Connection refused
java.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
at java.net.Socket.connect(Socket.java:507)
at java.net.Socket.connect(Socket.java:457)
at sun.net.NetworkClient.doConnect(NetworkClient.java:157)
at sun.net.www.http.HttpClient.openServer(HttpClient.java:365)
at sun.net.www.http.HttpClient.openServer(HttpClient.java:477)
at sun.net.www.http.HttpClient.<init>(HttpClient.java:214)
at sun.net.www.http.HttpClient.New(HttpClient.java:287)
at sun.net.www.http.HttpClient.New(HttpClient.java:299)
at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:792)
at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:744)
at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:669)
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:913)
at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:367)
at com.stc.is.util.pinger.HttpOKPinger.isAlive(Unknown Source)
at com.stc.is.util.Ping.main(Unknown Source)
Aug 23, 2006 7:23:55 PM com.stc.is.util.Ping main
INFO: IS is not alive.
Startup failed.
any clue what is it about?

Problems starting SunMC Agent 3.6 under Solaris 10

Similar Messages

Maybe you are looking for