"Could not start Agent" with SunMC 3.6.1 on Red Hat Enterprise release 4

Hi everyone,
I'm trying to install the Linux agent from the SunMC 3.6.1 installation dvd on a RedHat system (kernel 2.6). The installation seems to go fine, but while seting up the agent I recieve the following eror:
/opt/SUNWsymon/base/sbin/xget: error while loading shared libraries: libxcfg.so.1.0: cannot open shared object file: No such file or directory
/opt/SUNWsymon/base/sbin/xput: error while loading shared libraries: libxcfg.so.1.0: cannot open shared object file: No such file or directory
Naturally, in the end you get the message "Could not start Agent"...
Has anybody experienced this with a RedHat system or any other Linux system?
Best Regards,
Emerald

Hi!
I am trying to install SunMC 4.0 agent in a Red Hat Enterprise Linux AS release 4 (whith a SunMC server installed in a Solaris 10 platform).
I had installed the agent in the Red Hat, but the agent did not start.
I got this messages from the agent.log ( the same messages that Emerald)
[00000000 0046 ]info May 14 10:19:25 agent Channel already exists: syslog......................
[00000001 0048 ]info May 14 10:19:25 agent using ip mode for URL addressing....................
[00000002 003b ]info May 14 10:19:25 agent enabling timed jobs.................................
[00000003 004d ]info May 14 10:19:25 agent subagent registry successfully loaded...............
[00000004 005a ]info May 14 10:19:25 agent loading trap actions: subagent-manager-trap-action..
[00000005 0040 ]info May 14 10:19:25 agent startLegacySubagents: <>............................
[00000006 003e ]info May 14 10:19:25 agent activating MIB objects..............................
[00000007 0047 ]info May 14 10:19:25 agent *** shutting down subagents ***.....................
[00000008 005d ]error May 14 10:19:25 agent stopemd: action command script em-daemon.sh not found.
[00000009 007b ]error May 14 10:19:25 agent invalid dictionary entry: internal outBoundTrap in b
ase-agent.x(221) at token '???'............................................................................
[0000000a 0042 ]error May 14 10:19:25 agent *** aborting execution ***..........................
[0000000b 0046 ]info May 14 10:20:29 agent Channel already exists: syslog......................
[0000000c 0048 ]info May 14 10:20:29 agent using ip mode for URL addressing....................
[0000000d 003b ]info May 14 10:20:29 agent enabling timed jobs.................................
[0000000e 004d ]info May 14 10:20:29 agent subagent registry successfully loaded...............
[0000000f 005a ]info May 14 10:20:29 agent loading trap actions: subagent-manager-trap-action..
[00000010 0040 ]info May 14 10:20:29 agent startLegacySubagents: <>............................
[00000011 003e ]info May 14 10:20:29 agent activating MIB objects..............................
[00000012 0047 ]info May 14 10:20:29 agent *** shutting down subagents ***.....................
[00000013 005d ]error May 14 10:20:29 agent stopemd: action command script em-daemon.sh not found
Had anyone resolve this isue?? or had any ideas to resolve it??
Thanks in advance.
maza

Similar Messages

Could not start agent

Hi, I've managed to install SMC3.6 agent on a Solaris 8 platform but I was unable to start my agent. I get "Could not start agent" whenever i invoked the ./es-start -a command.
I've removed SMC3.6 agent and installed with 3.5 and it works. But I still prefer to use 3.6.
Do I require any patches for SMC3.6 agents?

I've tried "sh -x" like you asked me to and I get:
# sh -x
# ./es-start -aOops, I meant "sh -x es-start -a". "sh -x" should
show you every line of the startup shell script as
it's being run. But it looks like you found the
problem anyways...
couldn't load file "pkgsymon.so": ld.so.1: esd:
fatal: relocation error: file
/opt/SUNWsymon/base/lib/sparc-sun-solaris2.8/
liblaccess.so.1.0: symbol free_proflist:referenced
symbol not found
invalid command name "unordered_slice" while
executing "unordered_slice internal value"
invoked from within "source toe-basic.toe"
invoked from within "source base-$file.tcl"I'm no expert with Solaris libraries, but it looks
like the files "pkgsymon.so" or "liblaccess.so.1.0"
can't be found. You said that you had other Solaris 8
systems that run 3.6 fine: can you see where they
have those files:
find /opt/SUNWsymon -name pkgsymon.so
find /opt/SUNWsymon -name liblaccess.so.1.0
...then if they are in the right place (or exist at
all) on the problem box? And does it have a
/opt/SUNWsymon/base/lib/sparc-sun-solaris2.8
directory?
Maybe SunMC detected the wrong version of Solaris on
install or something, and either didn't install the
proper libraries, or put them in sparc-sun-solaris2.7
or sparc-sun-solaris2.9?
Does you root user have different environment
variables set (i.e. LD_LIBRARY_PATH) on the problem
box than on the ones that work?
At this point i'm just guessing: 3.6 is so new I
haven't had a lot of debugging time with it. Worst
case you can call Sun support and yell at them...
(just kidding, please don't do that :) )
Regards,
[email protected]
Hi Mike,
Found the 2 files in the /opt/SUNsymon. Checked and confirmed /opt/SUNWsymon/base/lib/sparc-sun-solaris2.8 is there. Will try touse sunchecktool to see if i need any patch fer that fella.
Anyway, about yelling at the Sun guys. That's a good one! :)
Thanks!

Could not start Agent on a Solaris 5.10u2 x86 machine

Hi,
I installed SunMC 3.6.1 on a Solaris 5.10u2 x86 machine. Only Agent
and Concole are installed.
There's no error during installation and setup, but the agent could not be started.
# /opt/SUNWsymon/sbin/es-start -a
Could not start Agent.
After running svcs -x, I could see:
# svcs -x
svc:/application/management/sunmcagent:default has no "restarter" property group; ignoring.
svc:/application/management/sunmcplatform:default has no "restarter" property group; ignoring.
svc:/application/print/server:default (LP print server)
State: disabled since Mon Aug 21 10:41:38 2006
Reason: Disabled by an administrator.
See: http://sun.com/msg/SMF-8000-05
See: lpsched(1M)
Impact: 2 dependent services are not running. (Use -v for list.)
# svcs -v
offline - Aug_21 - svc:/application/print/ipp-listener:default
offline - Aug_21 - svc:/application/print/rfc1179:default
- - - svc:/application/management/sunmcagent:default
How to solve this problem? Any help is appreciated.
Hal

Hi Hal, :)
# /opt/SUNWsymon/sbin/es-start -a
Could not start Agent.I've seen this before too. "svcadm enable/disable sunmcagent" didn't fix things. But for some reason if I started the agent interactively (es-start -ai) it worked... and I let the Agent load a few modules and verified it worked in the Console. Then once I quit out of interactive mode (thereby stopping the Agent) svcadm enable/disable and es-start/stop worked correctly again.
I had that happen to me 2-3 times now, and every time mucking about in interactive mode a bit fixed it. It must reset something in svcs.
Regards,
[email protected]
http://www.HalcyonInc.com

Could not start program with Version 8.0.25010

After I updated version 8.0.25010 I could not start the program and screen shows a warning " NtlmWebAuthException:2"

Hi Kevin,
Thank you for posting in Windows Server Forum.
If possible please try to reinstall and then check the result. Apart from that, have you make any changes related to connection setting on server side? Have you provided RD Gateway address or you are connecting directly?
The remote PC might only allow PCs to connect that have Network Level Authentication set up. For more info, see
What types of Remote Desktop connections should I allow?
For more information refer below article.
Remote Desktop Client on iOS: FAQ
http://technet.microsoft.com/en-us/library/dn473015.aspx
Hope it helps!
Thanks.
Dharmesh Solanki

Could not start SDM with NW2004 SP16.

I installed the trial version of NW2004 SP16 full Java version downloaded from SDN here. But the SDM service could not sttart when I start the J2EE engine.
Who can help?
Thanks in advance.

Hi Poseidon,
see,
http://help.sap.com/saphelp_nw04/helpdata/en/76/fb72ec091f4bf8a2d8ba321bb7e8d9/frameset.htm
Regards
Juan

[SOLVED] Could not start x with nouveau

Hi, i just switched from the nvidia driver to nouveau, but could not get X to start. I am getting an "KMS not enabled" error in /var/log/Xorg.0.log. My GPU is Nvidia G105M. I have used the nouveau driver in the past, but there was no kms back then. I have done everything according the nouveau page in arch's wiki.
Any ideas how to start x?
Thanks
Last edited by raxbg (2014-05-25 18:40:10)

You could try loading the KMS early in the boot process, as described in the wiki: "Early KMS Start"
However, I do not use nvidia/nouveau so this is just a wild guess

Could not start Oracle Agent Service

I have Oracle 8.17 Enterprise Edition installed on Windows 2000
Advanced Server. After the server boots and tries to start
Oracle services, it fails to start the Oracle Agent Service and
gives the following error:
"Could not start the OracleORA817Agent Service on Local
Computer. Error 3221356551:"
Because of this, none of the other Oracle Service start either.
If you have any suggestions, please let me know.
Thanks.
-ian

Hi,
In w2k advance server, I have two database (db1 and db2), they
have its own listener (list01 and list02). I can sqlplus to two
databases.
After i combined the two listeners to one listener (named
listenerA) in registry, the following error occured when i
sqlplus:
TNS: listener cannot resolve the SERVICE_NAME
In registry, I deleted services for listener01 and 02
in "service in w2k". And add listenerA to service and start it.
I found that db1 abd db2 are not started (no new event showing
database started or altered in alert_log) even w2k show "service
started". When I user database configuation to "reconfigure
database" (just click next and finish), i can sqlplus to the db1
and db2.
So, i think it's not the problem of listenerA, may be the
database is not start or partly start. But I don't know whether
I have delete wrongly in registry or anything wrong. Can anyone
help me ?
I have stopped the oracle agent in w2k service, is it related to
problem ?
Moreover, when i created a new db3 with listenerB, it works
normally even restart the db3 service.
Thanks for your kind attention

Could not start the Oracle Agent service on local computer

I have Oracle Enterprise 9.2.0.1 on Windows 2000 server,
When I'm starting the Agent service I get this message:
"Could not start the OracleOra9201Agent service on local computer.
The service didn't return an error.This could be an internal Windows error or an internal service error. If the problem persists, contact your system administrator."
Could you please help me to fix this problem? What I should do??

Are you using DHCP or using static IP address?
Also search forum , you ight get lots of thread addressing same issue.

My iphone can't back up to pc,because a session could not started with iphone.how fix the itunes

my iphone can't back up to pc,because a session could not started with iphone.how fix the itunes or iphone,this problem is after update ios7.0.4 and update itunes.pls teach me fix my pc,my pc is windows vista....

i have this problem too >> but i try other iphone ios7.0.3 i ok and work
but my ios7.0.4 cant back up and keep pop out session could not started with iphone !
really hope someone can help it ..
thank a lot !

Problem with deploying : SDM could not start the J2EE cluster on the host .

Hello, All
I have following problem with deploying the aplication I get this messenger:
16/09/2008 07:59:44 PM /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] ERROR:
[001]Deployment aborted
Settings
SDM host : 192.168.0.14
SDM port : 50018
URL to deploy : file:/C:/DOCUME1/PENITU1/LOCALS~1/Temp/temp47114ZChangeRequestDatabase.ear
Result
=> deployment aborted : file:/C:/DOCUME1/PENITU1/LOCALS~1/Temp/temp47114ZChangeRequestDatabase.ear
Aborted: development component 'ZChangeRequestDatabase'/'local'/'LOKAL'/'0.2008.05.03.04.24.17'/'0':
SDM could not start the J2EE cluster on the host Jupiter! The online deployment is terminated. There is no cluster control instance running on host Jupiter which is described in SecureStorage . The instances, returned by MessageServer [MS host: Jupiter; MS port: 3901], are :|Name:JM_T1221612526745_0_penitus15 |Host:PENITUS15 |State:5|HostAddress:192.168.0.205||Name:JM_T1221612357814_0_Jupiter |Host:pfs |State:5|HostAddress:192.168.0.14||Name:JC_Jupiter_JTP_00 |Host:pfs |State:5|HostAddress:192.168.0.14|Please check if there is an appropriate running cluster instances.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).STARTUP_CLUSTER)
Deployment exception : The deployment of at least one item aborted
I dont'n know How do I solver this error?
- I reviewed the virtual memory and I increase the virtual memory
- I restarted the server and the system
- I reviwed the parameter in the config tool --> cluster --> security storage it is OK
Any suggestion for solver this problem
Thanks
Regards
DS

I found this messenger in Additional log information., Please si
17/09/2008 03:04:51 PM /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] INFO:
[004]Additional log information about the deployment
<!LOGHEADER[START]/>
<!HELP[Manual modification of the header may cause parsing problem!]/>
<!LOGGINGVERSION[1.5.3.7185 - 630]/>
<!NAME[C:\usr\sap\JTP\JC00\SDM\program\log\sdmcl20080917200328.log]/>
<!PATTERN[sdmcl20080917200328.log]/>
<!FORMATTER[com.sap.tc.logging.TraceFormatter(%24d %s: %m)]/>
<!ENCODING[Cp1252]/>
<!LOGHEADER[END]/>
Sep 17, 2008 1:04:40 PM Info: -
Starting deployment -
Sep 17, 2008 1:04:40 PM Info: Error handling strategy: OnErrorStop
Sep 17, 2008 1:04:40 PM Info: Prerequisite error handling strategy: OnPrerequisiteErrorStop
Sep 17, 2008 1:04:40 PM Info: Update strategy: UpdateAllVersions
Sep 17, 2008 1:04:40 PM Info: Starting deployment prerequisites:
Sep 17, 2008 1:04:40 PM Info: Loading selected archives...
Sep 17, 2008 1:04:40 PM Info: Loading archive 'C:\usr\sap\JTP\JC00\SDM\program\temp\temp62604ZIssueDatabase.ear'
Sep 17, 2008 1:04:41 PM Info: Selected archives successfully loaded.
Sep 17, 2008 1:04:41 PM Info: Actions per selected component:
Sep 17, 2008 1:04:41 PM Info: Initial deployment: Selected development component 'ZIssueDatabase'/'local'/'LOKAL'/'0.2008.04.17.10.53.03'/'0' will be deployed.
Sep 17, 2008 1:04:41 PM Info: Ending deployment prerequisites. All items are correct.
Sep 17, 2008 1:04:43 PM Error: Unable to compare host[Jupiter] and host[PENITUS15] Throwable: java.net.UnknownHostException Throwable message: PENITUS15: PENITUS15
Sep 17, 2008 1:04:45 PM Error: Unable to compare host[Jupiter] and host[pfs] Throwable: java.net.UnknownHostException Throwable message: pfs: pfs
Sep 17, 2008 1:04:45 PM Error: Unable to compare host[Jupiter] and host[pfs] Throwable: java.net.UnknownHostException Throwable message: pfs
Sep 17, 2008 1:04:45 PM Info: Saved current Engine state.
Sep 17, 2008 1:04:45 PM Info: Starting: Initial deployment: Selected development component 'ZIssueDatabase'/'local'/'LOKAL'/'0.2008.04.17.10.53.03'/'0' will be deployed.
Sep 17, 2008 1:04:45 PM Info: SDA to be deployed: C:\usr\sap\JTP\JC00\SDM\root\origin\local\ZIssueDatabase\LOKAL\0\0.2008.04.17.10.53.03\temp62604ZIssueDatabase.ear
Sep 17, 2008 1:04:45 PM Info: Software type of SDA: J2EE
Sep 17, 2008 1:04:45 PM Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
Sep 17, 2008 1:04:45 PM Error: Unable to compare host[Jupiter] and host[PENITUS15] Throwable: java.net.UnknownHostException Throwable message: PENITUS15
Sep 17, 2008 1:04:45 PM Error: Unable to compare host[Jupiter] and host[pfs] Throwable: java.net.UnknownHostException Throwable message: pfs
Sep 17, 2008 1:04:45 PM Error: Unable to compare host[Jupiter] and host[pfs] Throwable: java.net.UnknownHostException Throwable message: pfs
Sep 17, 2008 1:04:45 PM Info: Starting cluster instance processes.
Sep 17, 2008 1:04:45 PM Error: Unable to compare host[Jupiter] and host[PENITUS15] Throwable: java.net.UnknownHostException Throwable message: PENITUS15
Sep 17, 2008 1:04:45 PM Error: Unable to compare host[Jupiter] and host[pfs] Throwable: java.net.UnknownHostException Throwable message: pfs
Sep 17, 2008 1:04:45 PM Error: Unable to compare host[Jupiter] and host[pfs] Throwable: java.net.UnknownHostException Throwable message: pfs
Sep 17, 2008 1:04:45 PM Error: An error occured while starting a cluster instance.
Sep 17, 2008 1:04:45 PM Error: There is no clutser control instance running on host Jupiter which is described in SecureStorage .
The instances, returned by MessageServer [MS host: Jupiter; MS port: 3901], are :
Name:JM_T1221672404781_2_penitus15
Host:PENITUS15
State:5
HostAddress:192.168.0.215
Name:JM_T1221679486171_0_Jupiter
Host:pfs
State:5
HostAddress:192.168.0.14
Name:JC_Jupiter_JTP_00
Host:pfs
State:5
HostAddress:192.168.0.14
Please check if there is an appropriate running cluster instances.
Sep 17, 2008 1:04:45 PM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Sep 17, 2008 1:04:45 PM Error: Aborted: development component 'ZIssueDatabase'/'local'/'LOKAL'/'0.2008.04.17.10.53.03'/'0':
SDM could not start the J2EE cluster on the host Jupiter! The online deployment is terminated.
There is no clutser control instance running on host Jupiter which is described in SecureStorage .
The instances, returned by MessageServer [MS host: Jupiter; MS port: 3901], are :
Name:JM_T1221672404781_2_penitus15
Host:PENITUS15
State:5
HostAddress:192.168.0.215
Name:JM_T1221679486171_0_Jupiter
Host:pfs
State:5
HostAddress:192.168.0.14
Name:JC_Jupiter_JTP_00
Host:pfs
State:5
HostAddress:192.168.0.14
Please check if there is an appropriate running cluster instances.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).STARTUP_CLUSTER)
Sep 17, 2008 1:04:45 PM Info: Starting to save the repository
Sep 17, 2008 1:04:46 PM Info: Finished saving the repository
Sep 17, 2008 1:04:47 PM Info: J2EE Engine is in same state (online/offline) as it has been before this deployment process.
Sep 17, 2008 1:04:47 PM Error: -
At least one of the Deployments failed -
Any help will be well received about this problema
Thk
Regards
DS

Could not start cache agent for the requested data store

Hi,
This is my first attempt in TimesTen. I am running TimesTen on the same Linux host (RHES 5.2) that running Oracle 11g R2. The version of TimesTen is:
TimesTen Release 11.2.1.4.0
Trying to create a simple cache.
The DSN entry for ttdemo1 in .odbc.ini is as follows:
+[ttdemo1]+
Driver=/home/oracle/TimesTen/timesten/lib/libtten.so
DataStore=/work/oracle/TimesTen_store/ttdemo1
PermSize=128
TempSize=128
UID=hr
OracleId=MYDB
DatabaseCharacterSet=WE8MSWIN1252
ConnectionCharacterSet=WE8MSWIN1252
Using ttisql I connect
Command> connect "dsn=ttdemo1;pwd=oracle;oraclepwd=oracle";
Connection successful: DSN=ttdemo1;UID=hr;DataStore=/work/oracle/TimesTen_store/ttdemo1;DatabaseCharacterSet=WE8MSWIN1252;ConnectionCharacterSet=WE8MSWIN1252;DRIVER=/home/oracle/TimesTen/timesten/lib/libtten.so;OracleId=MYDB;PermSize=128;TempSize=128;TypeMode=0;OracleNetServiceName=MYDB;
(Default setting AutoCommit=1)
Command> call ttcacheuidpwdset('ttsys','oracle');
Command> call ttcachestart;
*10024: Could not start cache agent for the requested data store. Could not initialize Oracle Environment Handle.*
The command failed.
The following is shown in the tterrors.log:
15:41:21.82 Err : ORA: 9143: ora-9143--1252549744-xxagent03356: Datastore: TTDEMO1 OCIEnvCreate failed. Return code -1
15:41:21.82 Err : : 7140: oraagent says it has failed to start: Could not initialize Oracle Environment Handle.
15:41:22.36 Err : : 7140: TT14004: TimesTen daemon creation failed: Could not spawn oraagent for '/work/oracle/TimesTen_store/ttdemo1': Could not initialize Oracle Environment Handl
What are the reasons that the daemon cannot spawn another agent? FYI the environment variables are set as:
ORA_NLS33=/u01/app/oracle/product/11.2.0/db_1/ocommon/nls/admin/data
ANT_HOME=/home/oracle/TimesTen/ttdemo1/3rdparty/ant
CLASSPATH=/home/oracle/TimesTen/ttdemo1/lib/ttjdbc5.jar:/home/oracle/TimesTen/ttdemo1/lib/orai18n.jar:/home/oracle/TimesTen/ttdemo1/lib/timestenjmsxla.jar:/home/oracle/TimesTen/ttdemo1/3rdparty/jms1.1/lib/jms.jar:.
oracle@rhes5:/home/oracle/TimesTen/ttdemo1/info% echo $LD_LIBRARY_PATH
/home/oracle/TimesTen/ttdemo1/lib:/home/oracle/TimesTen/ttdemo1/ttoracle_home/instantclient_11_1:/u01/app/oracle/product/11.2.0/db_1/lib:/u01/app/oracle/product/11.2.0/db_1/network/lib:/lib:/usr/lib:/usr/ucblib:/usr/local/lib
Cheers

Sure thanks.
Here you go:
Daemon environment:
_=/bin/csh
DISABLE_HUGETLBFS=1
SYSTEM=TEST
INIT_FILE=/u01/app/oracle/product/10.1.0/db_1/dbs/init+ASM.ora
GEN_APPSDIR=/home/oracle/dba/bin
LD_LIBRARY_PATH=/home/oracle/TimesTen/11.2.1.4.0/TimesTen/ttimdb1/ttoracle_home/instantclient_11_1:/home/oracle/TimesTen/11.2.1.4.0/TimesTen/ttimdb1/lib:/home/oracle/TimesTen/11.2.1.4.0/TimesTen/ttimdb1/ttoracle_home/instantclient_11_1:/u01/app/oracle/product/11.2.0/db_1/lib:/u01/app/oracle/product/11.2.0/db_1/network/lib:/lib:/usr/lib:/usr/ucblib:/usr/local/lib
HOME=/home/oracle
SPFILE_DIR=/u01/app/oracle/backup/+ASM/initfile_dir
TNS_ADMIN=/u01/app/oracle/product/11.2.0/db_1/network/admin
INITFILE_DIR=/u01/app/oracle/backup/+ASM/initfile_dir
HTMLDIR=/home/oracle/+ASM/dba/html
HOSTNAME=rhes5
TEMP=/oradata1/tmp
PWD=/home/oracle/TimesTen/11.2.1.4.0/TimesTen/ttimdb1/bin
HISTSIZE=1000
PATH=/home/oracle/TimesTen/11.2.1.4.0/TimesTen/ttimdb1/bin:/home/oracle/TimesTen/11.2.1.4.0/TimesTen/ttimdb1/quickstart/sample_code/oci:/home/oracle/TimesTen/11.2.1.4.0/TimesTen/ttimdb1/quickstart/sample_code/odbc:/home/oracle/TimesTen/11.2.1.4.0/TimesTen/ttimdb1/quickstart/sample_code/odbc/xla:/home/oracle/TimesTen/11.2.1.4.0/TimesTen/ttimdb1/quickstart/sample_code/jdbc:/home/oracle/TimesTen/11.2.1.4.0/TimesTen/ttimdb1/quickstart/sample_code/odbc_drivermgr:/home/oracle/TimesTen/11.2.1.4.0/TimesTen/ttimdb1/quickstart/sample_code/proc:/home/oracle/TimesTen/11.2.1.4.0/TimesTen/ttimdb1/quickstart/sample_code/ttclasses:/home/oracle/TimesTen/11.2.1.4.0/TimesTen/ttimdb1/quickstart/sample_code/ttclasses/xla:/home/oracle/TimesTen/11.2.1.4.0/TimesTen/ttimdb1/ttoracle_home/instantclient_11_1:/home/oracle/TimesTen/11.2.1.4.0/TimesTen/ttimdb1/ttoracle_home/instantclient_11_1/sdk:/home/oracle/TimesTen/11.2.1.4.0/TimesTen/ttimdb1/3rdparty/ant/bin:/usr/kerberos/bin:/bin:/usr/bin:/usr/local/bin:/sbin:/usr/bin/X11:/usr/X11R6/bin:/usr/platform/SUNW,Ultra-2/sbin:/u01/app/oracle/product/11.2.0/db_1:/u01/app/oracle/product/11.2.0/db_1/bin:.
GEN_ADMINDIR=/home/oracle/dba/admin
CONTROLFILE_DIR=/u01/app/oracle/backup/+ASM/controlfile_dir
ETCDIR=/home/oracle/+ASM/dba/etc
GEN_ENVDIR=/home/oracle/dba/env
DATAFILE_DIR=/u01/app/oracle/backup/+ASM/datafile_dir
BACKUPDIR=/u01/app/oracle/backup/+ASM
RESTORE_ARCFILES=/u01/app/oracle/backup/+ASM/restorefile_dir/restore_arcfiles.txt
TMPDIR=/oradata1/tmp
CVS_RSH=ssh
ARCLOG_DIR=/u01/app/oracle/backup/+ASM/arclog_dir
REDOLOG_DIR=/u01/app/oracle/backup/+ASM/redolog_dir
INPUTRC=/etc/inputrc
LOGDIR=/home/oracle/+ASM/dba/log
DATAFILE_LIST=/u01/app/oracle/backup/+ASM/datafile_dir/datafile.list
LS_COLORS=no=00:fi=00:di=00;34:ln=00;36:pi=40;33:so=00;35:bd=40;33;01:cd=40;33;01:or=01;05;37;41:mi=01;05;37;41:ex=00;32:*.cmd=00;32:*.exe=00;32:*.com=00;32:*.btm=00;32:*.bat=00;32:*.sh=00;32:*.csh=00;32:*.tar=00;31:*.tgz=00;31:*.arj=00;31:*.taz=00;31:*.lzh=00;31:*.zip=00;31:*.z=00;31:*.Z=00;31:*.gz=00;31:*.bz2=00;31:*.bz=00;31:*.tz=00;31:*.rpm=00;31:*.cpio=00;31:*.jpg=00;35:*.gif=00;35:*.bmp=00;35:*.xbm=00;35:*.xpm=00;35:*.png=00;35:*.tif=00;35:
PS1=rhes5:($ORACLE_SID)$
G_BROKEN_FILENAMES=1
SHELL=/bin/ksh
PASSFILE=/home/oracle/dba/env/.ora_accounts
LOGNAME=oracle
ORA_NLS10=/u01/app/oracle/product/11.2.0/db_1/nls/data
ORACLE_SID=mydb
APPSDIR=/home/oracle/+ASM/dba/bin
ORACLE_OWNER=oracle
RESTOREFILE_DIR=/u01/app/oracle/backup/+ASM/restorefile_dir
SQLPATH=/home/oracle/dba/bin
TRANDUMPDIR=/tran
RESTORE_SPFILE=/u01/app/oracle/backup/+ASM/restorefile_dir/restore_spfile.txt
RESTORE_DATAFILES=/u01/app/oracle/backup/+ASM/restorefile_dir/restore_datafiles.txt
ENV=/home/oracle/.kshrc
SSH_ASKPASS=/usr/libexec/openssh/gnome-ssh-askpass
SSH_CONNECTION=50.140.197.215 62742 50.140.197.216 22
LESSOPEN=|/usr/bin/lesspipe.sh %s
TERM=xterm
GEN_ETCDIR=/home/oracle/dba/etc
SP_FILE=/u01/app/oracle/product/10.1.0/db_1/dbs/spfile+ASM.ora
ORACLE_BASE=/u01/app/oracle
ASTFEATURES=UNIVERSE - ucb
ADMINDIR=/home/oracle/+ASM/dba/admin
SSH_CLIENT=50.140.197.215 62742 22
TZ=GB
SUPPORT=oracle@linux
ARCHIVE_LOG_LIST=/u01/app/oracle/backup/+ASM/arclog_dir/archive_log.list
USER=oracle
RESTORE_TEMPFILES=/u01/app/oracle/backup/+ASM/restorefile_dir/restore_tempfiles.txt
MAIL=/var/spool/mail/oracle
EXCLUDE=/home/oracle/+ASM/dba/bin/exclude.lst
GEN_LOGDIR=/home/oracle/dba/log
SSH_TTY=/dev/pts/2
RESTORE_INITFILE=/u01/app/oracle/backup/+ASM/restorefile_dir/restore_initfile.txt
HOSTTYPE=i386-linux
VENDOR=intel
OSTYPE=linux
MACHTYPE=i386
SHLVL=1
GROUP=dba
HOST=rhes5
REMOTEHOST=vista
EDITOR=vi
ORA_NLS33=/u01/app/oracle/product/11.2.0/db_1/ocommon/nls/admin/data
ODBCINI=/home/oracle/.odbc.ini
TT=/home/oracle/TimesTen/11.2.1.4.0/TimesTen/ttimdb1/
SHLIB_PATH=/u01/app/oracle/product/11.2.0/db_1/lib:/home/oracle/TimesTen/11.2.1.4.0/TimesTen/ttimdb1//lib
ANT_HOME=/home/oracle/TimesTen/11.2.1.4.0/TimesTen/ttimdb1/3rdparty/ant
CLASSPATH=/home/oracle/TimesTen/11.2.1.4.0/TimesTen/ttimdb1/lib/ttjdbc5.jar:/home/oracle/TimesTen/11.2.1.4.0/TimesTen/ttimdb1/lib/orai18n.jar:/home/oracle/TimesTen/11.2.1.4.0/TimesTen/ttimdb1/lib/timestenjmsxla.jar:/home/oracle/TimesTen/11.2.1.4.0/TimesTen/ttimdb1/3rdparty/jms1.1/lib/jms.jar:.
TT_AWT_PLSQL=0
NLS_LANG=AMERICAN_AMERICA
NLS_COMP=ANSI
NLS_SORT=BINARY
NLS_LENGTH_SEMANTICS=BYTE
NLS_NCHAR_CONV_EXCP=FALSE
NLS_CALENDAR=GREGORIAN
NLS_TIME_FORMAT=hh24:mi:ss
NLS_DATE_FORMAT=syyyy-mm-dd hh24:mi:ss
NLS_TIMESTAMP_FORMAT=syyyy-mm-dd hh24:mi:ss.ff9
ORACLE_HOME=
DaemonCWD = /home/oracle/TimesTen/11.2.1.4.0/TimesTen/ttimdb1/info
DaemonLog = /home/oracle/TimesTen/11.2.1.4.0/TimesTen/ttimdb1/info/tterrors.log
DaemonOptionsFile = /home/oracle/TimesTen/11.2.1.4.0/TimesTen/ttimdb1/info/ttendaemon.options
Platform = Linux/x86/32bit
SupportLog = /home/oracle/TimesTen/11.2.1.4.0/TimesTen/ttimdb1/info/ttmesg.log
Uptime = 136177 seconds
Backcompat = no
Group = 'dba'
Daemon pid 8111 port 53384 instance ttimdb1
End of report

Could not start the hyperion workspace-web application Error 1067

Hi,
I have installed hyperion from scratch in a distributed environment...everything was working fine.......i.e. shared services, workspace, essbase, sql server, and hfm. I was able to logon and navigate different options in the hyperion products...but essbase stopped working when I re-started all four servers ....?
(1) When I restarted all four servers and stopped and restarted all hyperion services as per giving sequence then everything works fine but essbase EAS console and workspace web console...i was getting error message " could not connect to administration server" whenever i try to connect EAS console to essbase then I went to services there I saw workspace agent and workspace web application service is down.
(2) as soon as I started those both services then my shared services automatically stopped but I was able to logon in Essbase console and workspace console but my shared services are down...
(3) as soon as I start shared service they started but my workspace agent and workspace web application automatically stopped...and when I try to start again workspace web application then I get this error "[ Could not start the hyperion workspace-web application services on local computer. Error 1067: the process terminated unexpectedly]"
I have been searching online and googling but have a hard luck to get some best solution for this...can some one help me or guide me to walk through with this issue...
Thank you very much in advance ...
Regards,
Safi

I solved this issue...It was with Hyperion Services those were stop responding some how.....but I stopped each service and restarted then those started working again...
Regards,
Safi

Could not find agent library in absolute path

Hi,
I have a JVMTI agent which works on windows that I am trying to port to linux.
I have compiled to code on Ubuntu 10.04 using Eclipse and have created shared library .so file.
When I try to run an application with the agentpath argument, I get the error: "Could not find agent library in absolute path"
When trying to run the mtrace sample from the java JDK, it works fine.
My Java version is:
java version "1.6.0_20"
Java(TM) SE Runtime Environment (build 1.6.0_20-b02)
Java HotSpot(TM) Client VM (build 16.3-b01, mixed mode, sharing)
I also tried running nm | grep Agent_OnLoad and got the following:
00029220 T Agent_OnLoad
00036230 b ZGVZ12AgentOnLoadE4data
00030720 r ZZ12AgentOnLoadE19__PRETTY_FUNCTION__
00036240 b ZZ12AgentOnLoadE4data
My agent references several libraries such as boost asio and log4cxx could it be related somehow to these?
I think it might be some sort of compilation issue because on windows it works fine.
Thanks

I managed to solve my problem.
It turned out that the error was caused by missing referenced libraries that were not linked in to my so file.
Once I added all of the required libraries, the agent started working.

Error : Could not start the SSO service. Please check the configuration

Hi,
I am getting the above error when enabling the"Agent-Based Windows Single Sign-On with Active Directory (Kerberos0".
I already twice did the KTpass.Timing is perfect bet CAS and AD.Please look into this CAS LOG file and advice me the next step to solve this issue.
Thanks
swami

Until you perform the configuration on the AD server, the following message will appear:
Error: Could not start the SSO service. Please check the configuration.
So configure the AD server so that the error message will not appear again.

Error: Could not start Service[keystone]: Execution of '/sbin/service openstack-keystone start' returned 1: Starting keystone: [FAILED]

I'm using Oracle Linux 6u6. While I'm installing openstack ( 2 node set up) using packstack, I'm getting this error:
Applying 10.245.33.37_cinder.pp
10.245.33.37_keystone.pp:                         [ ERROR ]
Applying Puppet manifests                         [ ERROR ]
ERROR : Error appeared during Puppet run: 10.245.33.37_keystone.pp
Error: Could not start Service[keystone]: Execution of '/sbin/service openstack-keystone start' returned 1: Starting keystone: [FAILED]
You will find full trace in log /var/tmp/packstack/20150327-100335-ltC8Ic/manifests/10.245.33.37_keystone.pp.log
Please check log file /var/tmp/packstack/20150327-100335-ltC8Ic/openstack-setup.log for more information
Additional information:
* A new answerfile was created in: /root/packstack-answers-20150327-100336.txt
* Time synchronization installation was skipped. Please note that unsynchronized time on server instances might be problem for some OpenStack components.
* Did not create a cinder volume group, one already existed
* File /root/keystonerc_admin has been created on OpenStack client host 10.245.33.37. To use the command line tools you need to source the file.
* To access the OpenStack Dashboard browse to http://10.245.33.37/dashboard .
Please, find your login credentials stored in the keystonerc_admin in your home directory.
Packages:
[root@slcai461 ~]# rpm -qa|grep keystone
python-keystoneclient-0.9.0-5.el6.noarch
python-keystone-2014.1.3-2.el6.noarch
openstack-keystone-2014.1.3-2.el6.noarch
[root@slcai461 ~]# rpm -qa|grep packstack
openstack-packstack-puppet-2014.1.1-0.12.dev1068.0.4.el6.noarch
openstack-packstack-2014.1.1-0.12.dev1068.0.4.el6.noarch
Log :
[root@slcai461 ~]# cat /var/tmp/packstack/20150327-100335-ltC8Ic/manifests/10.245.33.37_keystone.pp.log
Warning: Config file /etc/puppet/hiera.yaml not found, using Hiera defaults
Warning: Scope(Class[Keystone]): The sql_connection parameter is deprecated, use database_connection instead.
Warning: Scope(Class[Keystone]): token_format parameter is deprecated. Use token_provider instead.
Warning: Scope(Class[Keystone::Endpoint]): The public_address parameter is deprecated, use public_url instead.
Warning: Scope(Class[Keystone::Endpoint]): The internal_address parameter is deprecated, use internal_url instead.
Warning: Scope(Class[Keystone::Endpoint]): The admin_address parameter is deprecated, use admin_url instead.
Warning: Scope(Class[Nova::Keystone::Auth]): The cinder parameter is deprecated and has no effect.
Notice: Compiled catalog for slcai461.us.oracle.com in environment production in 1.60 seconds
Warning: The package type's allow_virtual parameter will be changing its default value from false to true in a future release. If you do not want to allow virtual packages, please explicitly set allow_virtual to false.
   (at /usr/lib/ruby/site_ruby/1.8/puppet/type.rb:816:in `set_default')
Notice: /Stage[main]/Keystone/Keystone_config[DEFAULT/admin_token]/value: value changed '[old secret redacted]' to '[new secret redacted]'
Notice: /Stage[main]/Keystone/Keystone_config[database/connection]/value: value changed '[old secret redacted]' to '[new secret redacted]'
Notice: /Stage[main]/Keystone::Db::Sync/Exec[keystone-manage db_sync]: Triggered 'refresh' from 3 events
Notice: /Stage[main]/Keystone/Exec[keystone-manage pki_setup]: Triggered 'refresh' from 2 events
Error: Could not start Service[keystone]: Execution of '/sbin/service openstack-keystone start' returned 1: Starting keystone: [FAILED]
Wrapped exception:
Execution of '/sbin/service openstack-keystone start' returned 1: Starting keystone: [FAILED]
Error: /Stage[main]/Keystone::Service/Service[keystone]/ensure: change from stopped to running failed: Could not start Service[keystone]: Execution of '/sbin/service openstack-keystone start' returned 1: Starting keystone: [FAILED]
Notice: /Stage[main]/Keystone::Service/Service[keystone]: Triggered 'refresh' from 5 events
Notice: /Stage[main]/Neutron::Keystone::Auth/Keystone_service[neutron]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Neutron::Keystone::Auth/Keystone_service[neutron]: Skipping because of failed dependencies
Notice: /Stage[main]/Keystone::Roles::Admin/Keystone_tenant[admin]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Keystone::Roles::Admin/Keystone_tenant[admin]: Skipping because of failed dependencies
Notice: /Stage[main]/Nova::Keystone::Auth/Keystone_service[nova_ec2]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Nova::Keystone::Auth/Keystone_service[nova_ec2]: Skipping because of failed dependencies
Notice: /Stage[main]/Cinder::Keystone::Auth/Keystone_service[cinderv2]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Cinder::Keystone::Auth/Keystone_service[cinderv2]: Skipping because of failed dependencies
Notice: /Stage[main]/Nova::Keystone::Auth/Keystone_service[novav3]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Nova::Keystone::Auth/Keystone_service[novav3]: Skipping because of failed dependencies
Notice: /Stage[main]/Keystone::Roles::Admin/Keystone_tenant[services]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Keystone::Roles::Admin/Keystone_tenant[services]: Skipping because of failed dependencies
Notice: /Stage[main]/Neutron::Keystone::Auth/Keystone_user[neutron]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Neutron::Keystone::Auth/Keystone_user[neutron]: Skipping because of failed dependencies
Notice: /Stage[main]/Nova::Keystone::Auth/Keystone_user[nova]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Nova::Keystone::Auth/Keystone_user[nova]: Skipping because of failed dependencies
Notice: /Stage[main]/Glance::Keystone::Auth/Keystone_user[glance]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Glance::Keystone::Auth/Keystone_user[glance]: Skipping because of failed dependencies
Notice: /Stage[main]/Keystone::Roles::Admin/Keystone_role[admin]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Keystone::Roles::Admin/Keystone_role[admin]: Skipping because of failed dependencies
Notice: /Stage[main]/Glance::Keystone::Auth/Keystone_user_role[glance@services]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Glance::Keystone::Auth/Keystone_user_role[glance@services]: Skipping because of failed dependencies
Notice: /Stage[main]/Keystone::Endpoint/Keystone_service[keystone]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Keystone::Endpoint/Keystone_service[keystone]: Skipping because of failed dependencies
Error: Could not prefetch keystone_endpoint provider 'keystone': Execution of '/usr/bin/keystone --os-endpoint http://127.0.0.1:35357/v2.0/ endpoint-list' returned 1: An unexpected error prevented the server from fulfilling your request. (HTTP 500)
Notice: /Stage[main]/Keystone::Endpoint/Keystone_endpoint[RegionOne/keystone]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Keystone::Endpoint/Keystone_endpoint[RegionOne/keystone]: Skipping because of failed dependencies
Notice: /Stage[main]/Main/Keystone_service[cinder_v2]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Main/Keystone_service[cinder_v2]: Skipping because of failed dependencies
Notice: /Stage[main]/Main/Keystone_endpoint[RegionOne/cinder_v2]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Main/Keystone_endpoint[RegionOne/cinder_v2]: Skipping because of failed dependencies
Notice: /Stage[main]/Nova::Keystone::Auth/Keystone_endpoint[RegionOne/novav3]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Nova::Keystone::Auth/Keystone_endpoint[RegionOne/novav3]: Skipping because of failed dependencies
Notice: /Stage[main]/Cinder::Keystone::Auth/Keystone_service[cinder]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Cinder::Keystone::Auth/Keystone_service[cinder]: Skipping because of failed dependencies
Notice: /Stage[main]/Cinder::Keystone::Auth/Keystone_endpoint[RegionOne/cinder]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Cinder::Keystone::Auth/Keystone_endpoint[RegionOne/cinder]: Skipping because of failed dependencies
Notice: /Stage[main]/Glance::Keystone::Auth/Keystone_service[glance]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Glance::Keystone::Auth/Keystone_service[glance]: Skipping because of failed dependencies
Notice: /Stage[main]/Glance::Keystone::Auth/Keystone_endpoint[RegionOne/glance]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Glance::Keystone::Auth/Keystone_endpoint[RegionOne/glance]: Skipping because of failed dependencies
Notice: /Stage[main]/Nova::Keystone::Auth/Keystone_user_role[nova@services]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Nova::Keystone::Auth/Keystone_user_role[nova@services]: Skipping because of failed dependencies
Notice: /Stage[main]/Keystone::Roles::Admin/Keystone_user[admin]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Keystone::Roles::Admin/Keystone_user[admin]: Skipping because of failed dependencies
Notice: /Stage[main]/Keystone::Roles::Admin/Keystone_user_role[admin@admin]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Keystone::Roles::Admin/Keystone_user_role[admin@admin]: Skipping because of failed dependencies
Notice: /Stage[main]/Cinder::Keystone::Auth/Keystone_user[cinder]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Cinder::Keystone::Auth/Keystone_user[cinder]: Skipping because of failed dependencies
Notice: /Stage[main]/Nova::Keystone::Auth/Keystone_endpoint[RegionOne/nova_ec2]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Nova::Keystone::Auth/Keystone_endpoint[RegionOne/nova_ec2]: Skipping because of failed dependencies
Notice: /Stage[main]/Cinder::Keystone::Auth/Keystone_endpoint[RegionOne/cinderv2]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Cinder::Keystone::Auth/Keystone_endpoint[RegionOne/cinderv2]: Skipping because of failed dependencies
Notice: /Stage[main]/Nova::Keystone::Auth/Keystone_service[nova]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Nova::Keystone::Auth/Keystone_service[nova]: Skipping because of failed dependencies
Notice: /Stage[main]/Nova::Keystone::Auth/Keystone_endpoint[RegionOne/nova]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Nova::Keystone::Auth/Keystone_endpoint[RegionOne/nova]: Skipping because of failed dependencies
Notice: /Stage[main]/Neutron::Keystone::Auth/Keystone_user_role[neutron@services]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Neutron::Keystone::Auth/Keystone_user_role[neutron@services]: Skipping because of failed dependencies
Notice: /Stage[main]/Neutron::Keystone::Auth/Keystone_endpoint[RegionOne/neutron]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Neutron::Keystone::Auth/Keystone_endpoint[RegionOne/neutron]: Skipping because of failed dependencies
Notice: /Stage[main]/Cinder::Keystone::Auth/Keystone_user_role[cinder@services]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Cinder::Keystone::Auth/Keystone_user_role[cinder@services]: Skipping because of failed dependencies
Notice: Finished catalog run in 3.10 seconds
Please let me know how to fix this.

This problem connected with proxy-setings.
As the first steps you should try:
       1. export system env variable:
http_proxy=http://www-proxy.ru.oracle.com:80
https_proxy=https://www-proxy.ru.oracle.com:80
no_proxy=127.0.0.1,localhost
and you can also export
    export OS_TENANT_NAME=admin
    export OS_USERNAME=admin
    export OS_PASSWORD=root
    export OS_AUTH_URL=http://<conntroller_IP>:5000/v2.0/
2. and than restart mysqld, if it is running, stop iptables and repeat installation process from beginning with the currently generated answer file
if we are exporting variable OS_PASSWORD, its value should be the same as value for CONFIG_KEYSTONE_ADMIN_PW in the currently generated answer file.
This OS_PASSWORD will be written by packstack in the /root/keystonerc_admin file and will be used as admin's password for login to Openstack dashboard.

"Could not start Agent" with SunMC 3.6.1 on Red Hat Enterprise release 4

Similar Messages

Maybe you are looking for