EP starting failed after switching UM datasource to LDAP
I would like to use Windows 2003 AD as user storage of EP. For this purpose, I completed the necessary configuration steps according to online help but still not able to connect EP to LDAP.
Test button show me that parameters entered in the LDAP configuration tab is correct. But once I change the UM datasource to dataSourceConfiguration_ADS_readonly_db.xml and restart the J2EE server. The application server won't start up successfully. It indicated problems with a yellow flag on the server node. Clicking the processes will display that some processes is running. Trace file outlines problem as below:
Jul 15, 2006 11:22:50... com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_62] Fatal: No connection to the ldap server, recheck configuration or availability of directory server
Jul 15, 2006 11:22:50... com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_62] Fatal: Server not available,recheck configuration or availability of directory server
Jul 15, 2006 11:22:50... com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_62] Fatal: Initialisation of a connection pool failed for UACC please check the configuration or availability of the directory server
Jul 15, 2006 11:22:50... com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_62] Fatal: Please recheck the LDAP configuration Initialisation of connection pool failed for UACC
poolname shaw2k99:389_UACC
java.naming.provider.url= ldap://shaw2k99:389/CN%3DUsers%2CDC%3Ddimension%2CDC%3Dcom%2CDC%3Dcn
java.naming.factory.initial= com.sun.jndi.ldap.LdapCtxFactory
java.naming.ldap.version= 3
connection_pool_name= shaw2k99:389_UACC
java.naming.security.authentication= simple
[EXCEPTION: no connection to the ldap server:[LDAP: error code 1 - 00000000: LdapErr: DSID-0C090627, comment: In order to perform this operation a successful bind must be completed on the connection., data 0, vece ]]
Jul 15, 2006 11:22:50... com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_62] Fatal: DataSource CORP_LDAP:Initialisation of connection manager failed because: Initialisation of connection pool failed for UACC
poolname shaw2k99:389_UACC
java.naming.provider.url= ldap://shaw2k99:389/CN%3DUsers%2CDC%3Ddimension%2CDC%3Dcom%2CDC%3Dcn
java.naming.factory.initial= com.sun.jndi.ldap.LdapCtxFactory
java.naming.ldap.version= 3
connection_pool_name= shaw2k99:389_UACC
java.naming.security.authentication= simple
[EXCEPTION: no connection to the ldap server:[LDAP: error code 1 - 00000000: LdapErr: DSID-0C090627, comment: In order to perform this operation a successful bind must be completed on the connection., data 0, vece ]]
Jul 15, 2006 11:22:50... com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_62] Fatal: Initialization of UME persistence adapter "CORP_LDAP" failed.
service com.sap.security.core.ume.service ================= ERROR =================
Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
com.sap.engine.frame.ServiceException: Initialisation of connection pool failed for UACC
Does anyone have clue on this? Thanks!
My EP version: EP 7.0 SP4
AD version: 2003
Hello,
I dont think, that the problem is directly related with the usage of SSL. We dont use SSL and we have the same problem mentioned in the first post of this topic in our portal. We are using EP7 SP8.
The connection tests in the config-tool and in the UME-configuration of the EP indicates us, that the connection to the LDAP-Server is working correct. But when we are restarting the portal, then the following exception appears and the server stops to start:
com.sap.security.core.persistence.datasource.PersistenceException: Initialisation of connection pool failed for UACC
poolname <ip-address>:389_UACC
java.naming.provider.url= ldap:// <ip-address>:389/
java.naming.factory.initial= com.sun.jndi.ldap.LdapCtxFactory
java.naming.ldap.version= 3
com.sun.jndi.ldap.connect.timeout= 25000
connection_pool_name= <ip-address>:389_UACC
java.naming.security.authentication= simple
[EXCEPTION: No connection to the ldap server: [LDAP: error code 1 - 00000000: LdapErr: DSID-0C090627, comment: In order to perform this operation a successful bind must be completed on the connection., data 0, vece]]
at com.sap.security.core.persistence.datasource.imp.LDAPConnectionManager.initConnectionPools(LDAPConnectionManager.java:777)
at com.sap.security.core.persistence.datasource.imp.LDAPConnectionManager.initialize(LDAPConnectionManager.java:83)
at com.sap.security.core.persistence.datasource.imp.LDAPPersistence.init(LDAPPersistence.java:453)
Has anyone a hint how to solve our problem?
Regards,
Udo
Similar Messages
-
J2EE Start Failed after upgrade
Hello Guys !
I Have this problem since upgra SP22.
#1.5 #005056AA79B8001C00000010000013CC000494B587D8095A#1289407295922#/System/Server##com.sap.engine.core.service630.container.ServiceRunner#######SAPEngine_System_Thread[impl:5]_55##0#0#Error#1#com.sap.engine.core.service630.container.ServiceRunner#Plain###Service com.sap.security.core.ume.service error. Nested exception is: com.sap.engine.frame.ServiceException: Start of UME service failed. Check help topic "Start of UME Service Failed". Technical details: Initialisation of connection pool failed for UACC
poolname norfloxacino.ems.com.br:389_UACC
[EXCEPTION: no connection to any server possible]
at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:398)
at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:83)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:156)
Caused by: com.sap.security.core.persistence.datasource.PersistenceException: Initialisation of connection pool failed for UACC
poolname norfloxacino.ems.com.br:389_UACC
[EXCEPTION: no connection to any server possible]
at com.sap.security.core.persistence.datasource.imp.LDAPPersistence.init(LDAPPersistence.java:423)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:440)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:164)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:117)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:63)
at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:221)
at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:287)
... 6 more
#1.5 #005056AA79B8001C00000012000013CC000494B587D80CC6#1289407295922#/System/Server##com.sap.engine.core.service630.container.ServiceRunner#######SAPEngine_System_Thread[impl:5]_55##0#0#Error#1#/System/Server#Plain###Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.#
#1.5 #005056AA79B8001C00000014000013CC000494B587D80E8E#1289407295922#/System/Server/Critical##com.sap.engine.core.Framework#######SAPEngine_System_Thread[impl:5]_55##0#0#Fatal#1#com.sap.engine.core.Framework#Plain###Critical shutdown was invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.#
Does anyone have any idea about the error above?
Thank you for your help!Hello
Did the system really work well before the upgrade?
and during/after the upgarde, did you changed any setting, especially regarding J2EE UME/ LDAP ?
Could you please help to check the following defaulttrace for more information:
../j2ee/cluster/server0/log/defaultTrace.*.trc
As per the error message you pasted here, the connection from your UME to the LDAP failed, so the core service of com.sap.engine.core.security.ume cannot startup.
Hence the first check point should be the connectioin to your LDAP, please open the configtool and go to the "UEM LDAP Data" setting there carefully, then you can perform a
"Test Connection" there.
If the connection always fails, you can also download a LDAP browser from "http://www.ldapbrowser.com/download.htm", then
test whether you are able to connect to the LDAP, if it also fails, I would like to suggest you check with your LDAP vendor to verify whether there is any problem at the LDAP server side.
Thanks
Thunder -
"opmn start failed" after starting infrastrucure as root
Infrastructure installed and functioning properly until one day I tried to make a startup script to start the infrastructure automaticly every time I restart the computer. After that I cannot start any opmn process.
After turning the opmn log level to 6, I get this output:
oracle@infra:~> opmnctl startall
opmnctl: starting opmn and all managed processes...
Loading Module libopmnohs callback functions
Module libopmnohs: loaded callback function opmnModInitialize
Module libopmnohs: unable to load callback function opmnModSetNumProcs
Module libopmnohs: unable to load callback function opmnModParse
Module libopmnohs: unable to load callback function opmnModHelp
Module libopmnohs: unable to load callback function opmnModDepend
Module libopmnohs: loaded callback function opmnModStart
Module libopmnohs: unable to load callback function opmnModReady
Module libopmnohs: loaded callback function opmnModNotify
Module libopmnohs: loaded callback function opmnModRestart
Module libopmnohs: loaded callback function opmnModStop
Module libopmnohs: loaded callback function opmnModPing
Module libopmnohs: loaded callback function opmnModProcRestore
Module libopmnohs: loaded callback function opmnModProcComp
Module libopmnohs: unable to load callback function opmnModReqComp
Module libopmnohs: unable to load callback function opmnModInfo
Module libopmnohs: unable to load callback function opmnModCron
Module libopmnohs: loaded callback function opmnModTerminate
and the same errors for every other component
opmnctl: opmn start failed
The startup script I wrote:
#!/bin/bash
. /etc/rc.status
rc_reset
su oracle
ORACLE_HOME=/opt/oracle/OraInfra
export PATH=$PATH:$ORACLE_HOME/bin:$ORACLE_HOME/dcm/bin:$ORACLE_HOME/webcache/bin:$ORACLE_HOME/opmn/bin
export ORACLE_SID=iasdb
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$ORACLE_HOME/lib
export DISPLAY=10.1.1.201:0.0
export INFRA=infra.zvs.com.mk
case "$1" in
start)
echo
echo Starting Listener
echo -----------------
$ORACLE_HOME/bin/lsnrctl start
echo
$ORACLE_HOME/dbstart
echo echo Starting all opmnctl controlled processes
echo -----------------------------------------
$ORACLE_HOME/opmn/bin/opmnctl startall
echo
echo Checking status of app server instances
echo --------------------------------------Â
echo Getting status for $INFRA
$ORACLE_HOME/dcm/bin/dcmctl getState -v -i $INFRA
echo Starting the EM website
echo -----------------------
#$ORACLE_HOME/bin/emctl start oms
$ORACLE_HOME/bin/emctl start em
stop)
echo Stopping the EM website
$ORACLE_HOME/bin/emctl stop em
echo Completed
echo Starting all opmnctl controlled processes
$ORACLE_HOME/opmn/bin/opmnctl stopall
$ORACLE_HOME/dbstop
esac
rc_exit
Please help, BorutI didn't started any component as root, but I can't finish installing AS 10.1.4.0.1 on Solaris 10 (x86). Tried many times, reinstalling everything, including the OS.
When I change the log level from 4 to 9, I can see the exact same error messages as you do.
But the only failing component to me is HTTP_Server.
No logs under $OH/opmn/log or $OH/Apache/Apache/logs.
OID and OC4J_SECURITY components are just fine.
Any help or suggestion would be appreciated.
Thanks in advance. -
[SOLVED] Cannot start mysqld after switching to MariaDB
Hey guys,
I just switched to MariaDB as recommended.
After installing MariaDB and running
systemctl start mysqld
, I get this error message:
Job for mysqld.service failed.
journal:
systemd[1]: Starting MariaDB database server...
mysqld[9358]: 130326 0:27:17 InnoDB: The InnoDB memory heap is disabled
mysqld[9358]: 130326 0:27:17 InnoDB: Mutexes and rw_locks use GCC atomic builtins
mysqld[9358]: 130326 0:27:17 InnoDB: Compressed tables use zlib 1.2.7
mysqld[9358]: 130326 0:27:17 InnoDB: Initializing buffer pool, size = 128.0M
mysqld[9358]: 130326 0:27:17 InnoDB: Completed initialization of buffer pool
mysqld[9358]: 130326 0:27:17 InnoDB: highest supported file format is Barracuda.
mysqld[9358]: 130326 0:27:17 InnoDB: Waiting for the background threads to start
mysqld[9358]: 130326 0:27:18 Percona XtraDB (http://www.percona.com) 5.5.30-MariaDB-30.1 started; log sequence number 46580545
mysqld[9358]: 130326 0:27:18 [ERROR] mysqld: Got error 'Size of control file is smaller than expected' when trying to use aria control file '/var/lib/mysql/aria_log_control'
mysqld[9358]: 130326 0:27:18 [ERROR] Plugin 'Aria' init function returned error.
mysqld[9358]: 130326 0:27:18 [ERROR] Plugin 'Aria' registration as a STORAGE ENGINE failed.
mysqld[9358]: 130326 0:27:18 [ERROR] Aria engine is not enabled or did not start. The Aria engine must be enabled to continue as mysqld was configured with --with-aria-tmp-tables
mysqld[9358]: 130326 0:27:18 [ERROR] Aborting
mysqld[9358]: 130326 0:27:18 InnoDB: Starting shutdown...
mysqld[9358]: 130326 0:27:19 InnoDB: Shutdown completed; log sequence number 46580545
mysqld[9358]: 130326 0:27:19 [Note] /usr/bin/mysqld: Shutdown complete
systemd[1]: mysqld.service: main process exited, code=exited, status=1/FAILURE
Last edited by lonaowna (2013-03-26 01:23:20)Hi ! I come here because I have a trouble since the last update of Mysqld :
I cannot start the daemon with
sudo systemctl start mysqld
I have these problems when i look in journalctl -xn :
mars 26 00:22:14 server mysqld[11593]: InnoDB: Error: log file ./ib_logfile0 is of different size 0 3174400 bytes
mars 26 00:22:14 server mysqld[11593]: InnoDB: than specified in the .cnf file 0 5242880 bytes!
mars 26 00:22:14 server mysqld[11593]: 130326 0:22:14 [ERROR] Plugin 'InnoDB' init function returned error.
mars 26 00:22:14 server mysqld[11593]: 130326 0:22:14 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
mars 26 00:22:14 server mysqld[11593]: 130326 0:22:14 [ERROR] Unknown/unsupported storage engine: InnoDB
mars 26 00:22:14 server mysqld[11593]: 130326 0:22:14 [ERROR] Aborting
mars 26 00:22:14 server mysqld[11593]: 130326 0:22:14 [Note] /usr/bin/mysqld: Shutdown complete
mars 26 00:22:14 server systemd[1]: mysqld.service: main process exited, code=exited, status=1/FAILURE
When I try with mysqld, I have
130326 0:23:21 [Warning] Can't create test file /var/lib/mysql/server.lower-test
130326 0:23:21 [Warning] Can't create test file /var/lib/mysql/server.lower-test
mysqld: Can't change dir to '/var/lib/mysql/' (Errcode: 13)
130326 0:23:21 [ERROR] Aborting
130326 0:23:21 [Note] mysqld: Shutdown complete
And when I look in /var/lib/mysql/server.err I have these lines
130207 23:32:56 mysqld_safe mysqld from pid file /var/lib/mysql/server.pid ended
130322 00:25:27 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
130322 0:25:27 InnoDB: The InnoDB memory heap is disabled
130322 0:25:27 InnoDB: Mutexes and rw_locks use GCC atomic builtins
130322 0:25:27 InnoDB: Compressed tables use zlib 1.2.7
130322 0:25:27 InnoDB: Initializing buffer pool, size = 128.0M
130322 0:25:27 InnoDB: Completed initialization of buffer pool
130322 0:25:27 InnoDB: highest supported file format is Barracuda.
InnoDB: Error: tried to read 65536 bytes at offset 0 3173376.
InnoDB: Was only able to read 1024.
InnoDB: Fatal error: cannot read from file. OS error number 17.
130322 0:25:30 InnoDB: Assertion failure in thread 139785666135872 in file os0file.c line 2538
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
23:25:30 UTC - mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.
key_buffer_size=16777216
read_buffer_size=262144
max_used_connections=0
max_threads=151
thread_count=0
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 134074 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 0 thread_stack 0x40000
/usr/bin/mysqld(my_print_stacktrace+0x29)[0x78ae99]
/usr/bin/mysqld(handle_fatal_signal+0x471)[0x67ad71]
/usr/lib/libpthread.so.0(+0xf1e0)[0x7f226299a1e0]
/usr/lib/libc.so.6(gsignal+0x35)[0x7f22615612c5]
/usr/lib/libc.so.6(abort+0x148)[0x7f2261562748]
/usr/bin/mysqld[0x8f2ac0]
/usr/bin/mysqld[0x8af1a0]
/usr/bin/mysqld[0x8e187c]
/usr/bin/mysqld[0x8e75ef]
/usr/bin/mysqld[0x834204]
/usr/bin/mysqld[0x7fe61f]
/usr/bin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x41)[0x67ccf1]
/usr/bin/mysqld[0x59ad94]
/usr/bin/mysqld(_Z11plugin_initPiPPci+0xa42)[0x59f342]
/usr/bin/mysqld[0x524328]
/usr/bin/mysqld(_Z11mysqld_mainiPPc+0x447)[0x529187]
/usr/lib/libc.so.6(__libc_start_main+0xf5)[0x7f226154da15]
/usr/bin/mysqld[0x51ff89]
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
130322 00:25:30 mysqld_safe mysqld from pid file /var/lib/mysql/server.pid ended
130326 00:24:58 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
130326 0:24:58 InnoDB: The InnoDB memory heap is disabled
130326 0:24:58 InnoDB: Mutexes and rw_locks use GCC atomic builtins
130326 0:24:58 InnoDB: Compressed tables use zlib 1.2.7
130326 0:24:58 InnoDB: Initializing buffer pool, size = 128.0M
130326 0:24:58 InnoDB: Completed initialization of buffer pool
InnoDB: Error: log file ./ib_logfile0 is of different size 0 3174400 bytes
InnoDB: than specified in the .cnf file 0 5242880 bytes!
130326 0:24:58 [ERROR] Plugin 'InnoDB' init function returned error.
130326 0:24:58 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
130326 0:24:58 [ERROR] Unknown/unsupported storage engine: InnoDB
130326 0:24:58 [ERROR] Aborting
130326 0:24:58 [Note] /usr/bin/mysqld: Shutdown complete
130326 00:24:58 mysqld_safe mysqld from pid file /var/lib/mysql/server.pid ended
130326 00:25:33 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql/
130326 0:25:33 InnoDB: The InnoDB memory heap is disabled
130326 0:25:33 InnoDB: Mutexes and rw_locks use GCC atomic builtins
130326 0:25:33 InnoDB: Compressed tables use zlib 1.2.7
130326 0:25:33 InnoDB: Initializing buffer pool, size = 128.0M
130326 0:25:33 InnoDB: Completed initialization of buffer pool
InnoDB: Error: log file ./ib_logfile0 is of different size 0 3174400 bytes
InnoDB: than specified in the .cnf file 0 5242880 bytes!
130326 0:25:33 [ERROR] Plugin 'InnoDB' init function returned error.
130326 0:25:33 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
130326 0:25:33 [ERROR] Unknown/unsupported storage engine: InnoDB
130326 0:25:33 [ERROR] Aborting
130326 0:25:33 [Note] /usr/bin/mysqld: Shutdown complete
130326 00:25:33 mysqld_safe mysqld from pid file /var/lib/mysql//server.pid ended
When I try mysqld_safe, here is what I get
130326 00:24:58 mysqld_safe Logging to '/var/lib/mysql/server.err'.
130326 00:24:58 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
130326 00:24:58 mysqld_safe mysqld from pid file /var/lib/mysql/server.pid ended
Resolution
===== It's a good thing to make a post :
It allows me to order my ideas and I find the solution here http://serverfault.com/questions/104014 … erent-size
I juste deleted the files /var/lib/mysqld/ib_logfile0 and /var/lib/mysql/ib_logfile1
First, I had a problem about the file who is in the future (WTF ?:p) But after, it worked !
Thanks Anyway !
Last edited by shox (2013-03-25 23:51:43) -
Update failed after switching to nightly channel according to the MDN (Flame)
Good Evening Firefox OS Pro's :)
I just got my new Flame, flashed the base image (http://cds.w5v8t3u9.hwcdn.net/Flame_2.0_v180_1.zip) and the rest (http://ftp.mozilla.org/pub/mozilla.org/b2g/nightly/latest-mozilla-b2g32_v2_0-flame-kk/) according to the MDN (https://developer.mozilla.org/en-US/Firefox_OS/Developer_phone_guide/Flame#Updating_your_Flame's_software).
The phone boots and everything is working fine. However after executing the steps under the headline "Switch to nightly update channel" I got an update notification, but the update failed to install with the error message: "there was an error while downloading the updates".
Edit: The error message appeared during the "Uncompressing...". After it failed the notification is there again.
So... I noticed that the update channel was nightly-b2g32 before I changed it with the script to nightly. What is the difference between these two? Is nightly the wrong channel for 2.0?
Thanks in advance :Dnightly-b2g32 is 2.1 I think.
[https://developer.mozilla.org/en-US/Firefox_OS/Developer_phone_guide/Flame MDN Flame] -
LMS 4.0 Archive Poller starts failing after some working cycles
Hi,
We have a LMS 4.0 running in our network with arround 650 nodes.
We are having problems with the Archive Poller.
The first few days it worked fine, but then it started to fail for some devices and on the next day it failed to poll all devices. I have restarted the daemon manager after the failure and it came back working fine for another few days. Since then the Change Poller works for a few days, then it degrades polling to a complete failure, a restart of the daemon manager get it working only for a few days.
Here is some output of a failed node:
*** Device Details for zagora4-sw ***
Protocol ==> Unknown / Not Applicable
Selected Protocols with order ==> Telnet,SSH
Execution Result:
Unable to get results of job execution for device. Retry the job after increasing the job result wait time using the option:Admin > Collection Settings > Config > Config Job Timeout Settings
It seems that the poller is not even trying to poll nodes...?
Do you think the DB might got corrupted, as I restarted the machine without shutting down the processes some weeks ago...
Any hints or ideas would be appreciated !Hi @ all
I have the same Problem as Ruslan. Do ansbody have a idea to solve this problem ? Afer some succesfull runs ob the ArchivePoll it stop with the mentioned error...
*** Device Details for nunw-n30-05-005 ***
Protocol ==> Unknown / Not Applicable
Selected Protocols with order ==> Telnet,SSH,HTTPS
Execution Result:
Unable to get results of job execution for device. Retry the job after increasing the job result wait time using the option:Admin > Collection Settings > Config > Config Job Timeout Settings
I´d tried to increase the "wait time" but notthing happens ...
HELP Please ...
Thanks
Regard Mario -
J2EE start fails after changing the instance-number
Hi,
we installed a SCS with instance number 41. After a few weeks it was necessary to change it to 44. We changed all property-files and the profiles.
The SCS started fine, but the J2EE-Server failed starting.
In dev_server0 is still a line with the former port 3241:
[Thr 182906379008] *** WARNING => INFO: Unknown property [instance.en.port=3241] [jstartxx_mt. 841]
I thought I changed everything from 41 to 44. Does someone have an idea, which I forgot? Thank you for help.
Here you can see the whole dev_server0:
trc file: "/usr/sap/SM1/DVEBMGS40/work/dev_server0", trc level: 1, release: "700"
node name : ID401326950
pid : 29093
system name : SM1
system nr. : 40
started at : Tue May 22 14:51:09 2007
arguments :
arg[00] : /usr/sap/SM1/DVEBMGS40/exe/jlaunch
arg[01] : pf=/usr/sap/SM1/SYS/profile/SM1_DVEBMGS40_sm1-ci
arg[02] : -DSAPINFO=SM1_40_server
arg[03] : pf=/usr/sap/SM1/SYS/profile/SM1_DVEBMGS40_sm1-ci
arg[04] : -DSAPSTART=1
arg[05] : -DCONNECT_PORT=60030
arg[06] : -DSAPSYSTEM=40
arg[07] : -DSAPSYSTEMNAME=SM1
arg[08] : -DSAPMYNAME=sm1-ci_SM1_40
arg[09] : -DSAPPROFILE=/usr/sap/SM1/SYS/profile/SM1_DVEBMGS40_sm1-ci
arg[10] : -DFRFC_FALLBACK=ON
arg[11] : -DFRFC_FALLBACK_HOST=localhost
[Thr 182906379008] Tue May 22 14:51:09 2007
[Thr 182906379008] *** WARNING => INFO: Unknown property [instance.box.number=SM1DVEBMGS40sm1-ci] [jstartxx_mt. 841]
[Thr 182906379008] *** WARNING => INFO: Unknown property [instance.en.host=sm1-scs] [jstartxx_mt. 841]
[Thr 182906379008] *** WARNING => INFO: Unknown property [instance.en.port=3241] [jstartxx_mt. 841]
[Thr 182906379008] *** WARNING => INFO: Unknown property [instance.system.id=40] [jstartxx_mt. 841]
JStartupReadInstanceProperties: read instance properties [/usr/sap/SM1/DVEBMGS40/j2ee/cluster/instance.properties]
-> ms host : sm1-scs
-> ms port : 3944
-> OS libs : /usr/sap/SM1/DVEBMGS40/j2ee/os_libs
-> Admin URL :
-> run mode : NORMAL
-> run action : NONE
-> enabled : yes
Used property files
-> files [00] : /usr/sap/SM1/DVEBMGS40/j2ee/cluster/instance.properties
Instance properties
-> ms host : sm1-scs
-> ms port : 3944
-> os libs : /usr/sap/SM1/DVEBMGS40/j2ee/os_libs
-> admin URL :
-> run mode : NORMAL
-> run action : NONE
-> enabled : yes
Bootstrap nodes
-> [00] bootstrap : /usr/sap/SM1/DVEBMGS40/j2ee/cluster/instance.properties
-> [01] bootstrap_ID40132690 : /usr/sap/SM1/DVEBMGS40/j2ee/cluster/instance.properties
-> [02] bootstrap_ID40132695 : /usr/sap/SM1/DVEBMGS40/j2ee/cluster/instance.properties
Worker nodes
-> [00] ID401326900 : /usr/sap/SM1/DVEBMGS40/j2ee/cluster/instance.properties
-> [01] ID401326950 : /usr/sap/SM1/DVEBMGS40/j2ee/cluster/instance.properties
[Thr 182906379008] JLaunchRequestQueueInit: create named pipe for ipc
[Thr 182906379008] JLaunchRequestQueueInit: create pipe listener thread
[Thr 1074792800] JLaunchRequestFunc: Thread 1074792800 started as listener thread for np messages.
[Thr 1076894048] WaitSyncSemThread: Thread 1076894048 started as semaphore monitor thread.
[Thr 182906379008] SigISetDefaultAction : default handling for signal 17
[Thr 182906379008] NiInit3: NI already initialized; param 'maxHandles' ignored (1;202)
[Thr 182906379008] CPIC (version=700.2006.09.13)
[Thr 182906379008] *** WARNING => Maximum Java heap size specified twice (through maxHeapSize and in javaParameters) - using -Xmx2048M [jstartxx_mt. 2604]
[Thr 182906379008] [Node: server0] java home is set by profile parameter
Java Home: /usr/lib/java
[Thr 182906379008] JStartupICheckFrameworkPackage: can't find framework package /usr/sap/SM1/DVEBMGS40/exe/jvmx.jar
JStartupIReadSection: read node properties [ID401326950]
-> node name : server0
-> node type : server
-> node execute : yes
-> jlaunch parameters :
-> java path : /usr/lib/java
-> java parameters : -Djava.security.policy=./java.policy -Djava.security.egd=file:/dev/urandom -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy -Djco.jarm=1 -verbose:gc -Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.services.ts.jts.ots.PortableInterceptor.JTSInitializer -Xmn400M -Xgcpolicy:gencon -Xtrace -Xsoftrefthreshold0
-> java vm version : J2RE 1.4.2 IBM J9 2.2 Linux amd64-64 j9xa64142-20060428 (JIT enabled)
-> java vm vendor : IBM J9SE VM (IBM Corporation)
-> java vm type : <default>
-> java vm cpu : amd64
-> heap size : 2048M
-> init heap size : 2048M
-> root path : /usr/sap/SM1/DVEBMGS40/j2ee/cluster/server0
-> class path : ./bin/boot/boot.jar:./bin/boot/jaas.jar:./bin/system/bytecode.jar:.
-> OS libs path : /usr/sap/SM1/DVEBMGS40/j2ee/os_libs
-> main class : com.sap.engine.boot.Start
-> framework class : com.sap.bc.proj.jstartup.JStartupFramework
-> registr. class : com.sap.bc.proj.jstartup.JStartupNatives
-> framework path : /usr/sap/SM1/DVEBMGS40/exe/jstartup.jar:/usr/sap/SM1/DVEBMGS40/exe/jvmx.jar
-> shutdown class : com.sap.engine.boot.Start
-> parameters :
-> debuggable : no
-> debug mode : no
-> debug port : 54021
-> shutdown timeout : 120000
[Thr 182906379008] JLaunchISetDebugMode: set debug mode [no]
[Thr 1077946720] JLaunchIStartFunc: Thread 1077946720 started as Java VM thread.
JHVM_LoadJavaVM: VM Arguments of node [server0]
-> stack : 1048576 Bytes
-> arg[ 0]: exit
-> arg[ 1]: abort
-> arg[ 2]: vfprintf
-> arg[ 3]: -Djava.security.policy=./java.policy
-> arg[ 4]: -Djava.security.egd=file:/dev/urandom
-> arg[ 5]: -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy
-> arg[ 6]: -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy
-> arg[ 7]: -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
-> arg[ 8]: -Djco.jarm=1
-> arg[ 9]: -verbose:gc
-> arg[ 10]: -Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.services.ts.jts.ots.PortableInterceptor.JTSInitializer
-> arg[ 11]: -Xmn400M
-> arg[ 12]: -Xgcpolicy:gencon
-> arg[ 13]: -Xtrace
-> arg[ 14]: -Xsoftrefthreshold0
-> arg[ 15]: -Dsys.global.dir=/usr/sap/SM1/SYS/global
-> arg[ 16]: -Dapplication.home=/usr/sap/SM1/DVEBMGS40/exe
-> arg[ 17]: -Djava.class.path=/usr/sap/SM1/DVEBMGS40/exe/jstartup.jar:/usr/sap/SM1/DVEBMGS40/exe/jvmx.jar:./bin/boot/boot.jar:./bin/boot/jaas.jar:./bin/system/bytecode.jar:.
-> arg[ 18]: -Djava.library.path=/opt/IBMJava2-amd64-142/jre/bin:/opt/IBMJava2-amd64-142/jre/bin:/opt/IBMJava2-amd64-142/jre/bin:/opt/IBMJava2-amd64-142/jre/bin/j9vm:/opt/IBMJava2-amd64-142/jre/bin:/usr/sap/SM1/DVEBMGS40/exe:/usr/sap/SM1/DVEBMGS40/exe:/usr/sap/SM1/DVEBMGS40/exe:/tmp/sapinst_exe.7551.1151567769:/usr/sap/SM1/SYS/exe/run:/sapdb/programs/lib:/usr/lib:/usr/sap/SM1/DVEBMGS40/j2ee/os_libs:/usr/sap/SM1/DVEBMGS40/exe:/usr/sap/SM1/DVEBMGS40/exe:/usr/sap/SM1/DVEBMGS40/exe:/usr/sap/SM1/SYS/exe/run:/sapdb/programs/lib
-> arg[ 19]: -Dmemory.manager=2048M
-> arg[ 20]: -Xmx2048M
-> arg[ 21]: -Xms2048M
-> arg[ 22]: -DLoadBalanceRestricted=no
-> arg[ 23]: -Djstartup.mode=JCONTROL
-> arg[ 24]: -Djstartup.ownProcessId=29093
-> arg[ 25]: -Djstartup.ownHardwareId=X1817543257
-> arg[ 26]: -Djstartup.whoami=server
-> arg[ 27]: -Djstartup.debuggable=no
-> arg[ 28]: -DSAPINFO=SM1_40_server
-> arg[ 29]: -DSAPSTART=1
-> arg[ 30]: -DCONNECT_PORT=60030
-> arg[ 31]: -DSAPSYSTEM=40
-> arg[ 32]: -DSAPSYSTEMNAME=SM1
-> arg[ 33]: -DSAPMYNAME=sm1-ci_SM1_40
-> arg[ 34]: -DSAPPROFILE=/usr/sap/SM1/SYS/profile/SM1_DVEBMGS40_sm1-ci
-> arg[ 35]: -DFRFC_FALLBACK=ON
-> arg[ 36]: -DFRFC_FALLBACK_HOST=localhost
-> arg[ 37]: -DSAPSTARTUP=1
-> arg[ 38]: -DSAPSYSTEM=40
-> arg[ 39]: -DSAPSYSTEMNAME=SM1
-> arg[ 40]: -DSAPMYNAME=sm1-ci_SM1_40
-> arg[ 41]: -DSAPDBHOST=sm1-db
-> arg[ 42]: -Dj2ee.dbhost=sm1-db
[Thr 1077946720] JHVM_LoadJavaVM: Java VM created OK.
JHVM_BuildArgumentList: main method arguments of node [server0]
[Thr 1082288480] Tue May 22 14:51:13 2007
[Thr 1082288480] JHVM_RegisterNatives: registering methods in com.sap.bc.krn.perf.PerfTimes
[Thr 1082288480] JHVM_RegisterNatives: registering methods in com.sap.bc.proj.jstartup.JStartupFramework
[Thr 1082288480] JLaunchISetClusterId: set cluster id 401326950
[Thr 1094003040] Tue May 22 14:54:13 2007
[Thr 1094003040] JLaunchIExitJava: exit hook is called (rc = -337)
[Thr 1094003040] **********************************************************************
ERROR => The Java VM terminated with a non-zero exit code.
Please see SAP Note 943602 , section 'J2EE Engine exit codes'
for additional information and trouble shooting.
[Thr 1094003040] SigISetIgnoreAction : SIG_IGN for signal 17
[Thr 1094003040] JLaunchCloseProgram: good bye (exitcode = -337)
trc file: "/usr/sap/SM1/DVEBMGS40/work/dev_server0", trc level: 1, release: "700"
node name : ID401326950
pid : 30385
system name : SM1
system nr. : 40
started at : Tue May 22 14:54:15 2007
arguments :
arg[00] : /usr/sap/SM1/DVEBMGS40/exe/jlaunch
arg[01] : pf=/usr/sap/SM1/SYS/profile/SM1_DVEBMGS40_sm1-ci
arg[02] : -DSAPINFO=SM1_40_server
arg[03] : pf=/usr/sap/SM1/SYS/profile/SM1_DVEBMGS40_sm1-ci
arg[04] : -DSAPSTART=1
arg[05] : -DCONNECT_PORT=60030
arg[06] : -DSAPSYSTEM=40
arg[07] : -DSAPSYSTEMNAME=SM1
arg[08] : -DSAPMYNAME=sm1-ci_SM1_40
arg[09] : -DSAPPROFILE=/usr/sap/SM1/SYS/profile/SM1_DVEBMGS40_sm1-ci
arg[10] : -DFRFC_FALLBACK=ON
arg[11] : -DFRFC_FALLBACK_HOST=localhost
[Thr 182906379008] Tue May 22 14:54:15 2007
[Thr 182906379008] *** WARNING => INFO: Unknown property [instance.box.number=SM1DVEBMGS40sm1-ci] [jstartxx_mt. 841]
[Thr 182906379008] *** WARNING => INFO: Unknown property [instance.en.host=sm1-scs] [jstartxx_mt. 841]
[Thr 182906379008] *** WARNING => INFO: Unknown property [instance.en.port=3241] [jstartxx_mt. 841]
[Thr 182906379008] *** WARNING => INFO: Unknown property [instance.system.id=40] [jstartxx_mt. 841]
JStartupReadInstanceProperties: read instance properties [/usr/sap/SM1/DVEBMGS40/j2ee/cluster/instance.properties]
-> ms host : sm1-scs
-> ms port : 3944
-> OS libs : /usr/sap/SM1/DVEBMGS40/j2ee/os_libs
-> Admin URL :
-> run mode : NORMAL
-> run action : NONE
-> enabled : yes
Used property files
-> files [00] : /usr/sap/SM1/DVEBMGS40/j2ee/cluster/instance.properties
Instance properties
-> ms host : sm1-scs
-> ms port : 3944
-> os libs : /usr/sap/SM1/DVEBMGS40/j2ee/os_libs
-> admin URL :
-> run mode : NORMAL
-> run action : NONE
-> enabled : yes
Bootstrap nodes
-> [00] bootstrap : /usr/sap/SM1/DVEBMGS40/j2ee/cluster/instance.properties
-> [01] bootstrap_ID40132690 : /usr/sap/SM1/DVEBMGS40/j2ee/cluster/instance.properties
-> [02] bootstrap_ID40132695 : /usr/sap/SM1/DVEBMGS40/j2ee/cluster/instance.properties
Worker nodes
-> [00] ID401326900 : /usr/sap/SM1/DVEBMGS40/j2ee/cluster/instance.properties
-> [01] ID401326950 : /usr/sap/SM1/DVEBMGS40/j2ee/cluster/instance.properties
[Thr 182906379008] JLaunchRequestQueueInit: create named pipe for ipc
[Thr 182906379008] JLaunchRequestQueueInit: create pipe listener thread
[Thr 1074792800] JLaunchRequestFunc: Thread 1074792800 started as listener thread for np messages.
[Thr 1076894048] WaitSyncSemThread: Thread 1076894048 started as semaphore monitor thread.
[Thr 182906379008] SigISetDefaultAction : default handling for signal 17
[Thr 182906379008] Tue May 22 14:54:16 2007
[Thr 182906379008] NiInit3: NI already initialized; param 'maxHandles' ignored (1;202)
[Thr 182906379008] CPIC (version=700.2006.09.13)
[Thr 182906379008] *** WARNING => Maximum Java heap size specified twice (through maxHeapSize and in javaParameters) - using -Xmx2048M [jstartxx_mt. 2604]
[Thr 182906379008] [Node: server0] java home is set by profile parameter
Java Home: /usr/lib/java
[Thr 182906379008] JStartupICheckFrameworkPackage: can't find framework package /usr/sap/SM1/DVEBMGS40/exe/jvmx.jar
JStartupIReadSection: read node properties [ID401326950]
-> node name : server0
-> node type : server
-> node execute : yes
-> jlaunch parameters :
-> java path : /usr/lib/java
-> java parameters : -Djava.security.policy=./java.policy -Djava.security.egd=file:/dev/urandom -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy -Djco.jarm=1 -verbose:gc -Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.services.ts.jts.ots.PortableInterceptor.JTSInitializer -Xmn400M -Xgcpolicy:gencon -Xtrace -Xsoftrefthreshold0
-> java vm version : J2RE 1.4.2 IBM J9 2.2 Linux amd64-64 j9xa64142-20060428 (JIT enabled)
-> java vm vendor : IBM J9SE VM (IBM Corporation)
-> java vm type : <default>
-> java vm cpu : amd64
-> heap size : 2048M
-> init heap size : 2048M
-> root path : /usr/sap/SM1/DVEBMGS40/j2ee/cluster/server0
-> class path : ./bin/boot/boot.jar:./bin/boot/jaas.jar:./bin/system/bytecode.jar:.
-> OS libs path : /usr/sap/SM1/DVEBMGS40/j2ee/os_libs
-> main class : com.sap.engine.boot.Start
-> framework class : com.sap.bc.proj.jstartup.JStartupFramework
-> registr. class : com.sap.bc.proj.jstartup.JStartupNatives
-> framework path : /usr/sap/SM1/DVEBMGS40/exe/jstartup.jar:/usr/sap/SM1/DVEBMGS40/exe/jvmx.jar
-> shutdown class : com.sap.engine.boot.Start
-> parameters :
-> debuggable : no
-> debug mode : no
-> debug port : 54021
-> shutdown timeout : 120000
[Thr 182906379008] JLaunchISetDebugMode: set debug mode [no]
[Thr 1077946720] JLaunchIStartFunc: Thread 1077946720 started as Java VM thread.
JHVM_LoadJavaVM: VM Arguments of node [server0]
-> stack : 1048576 Bytes
-> arg[ 0]: exit
-> arg[ 1]: abort
-> arg[ 2]: vfprintf
-> arg[ 3]: -Djava.security.policy=./java.policy
-> arg[ 4]: -Djava.security.egd=file:/dev/urandom
-> arg[ 5]: -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy
-> arg[ 6]: -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy
-> arg[ 7]: -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
-> arg[ 8]: -Djco.jarm=1
-> arg[ 9]: -verbose:gc
-> arg[ 10]: -Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.services.ts.jts.ots.PortableInterceptor.JTSInitializer
-> arg[ 11]: -Xmn400M
-> arg[ 12]: -Xgcpolicy:gencon
-> arg[ 13]: -Xtrace
-> arg[ 14]: -Xsoftrefthreshold0
-> arg[ 15]: -Dsys.global.dir=/usr/sap/SM1/SYS/global
-> arg[ 16]: -Dapplication.home=/usr/sap/SM1/DVEBMGS40/exe
-> arg[ 17]: -Djava.class.path=/usr/sap/SM1/DVEBMGS40/exe/jstartup.jar:/usr/sap/SM1/DVEBMGS40/exe/jvmx.jar:./bin/boot/boot.jar:./bin/boot/jaas.jar:./bin/system/bytecode.jar:.
-> arg[ 18]: -Djava.library.path=/opt/IBMJava2-amd64-142/jre/bin:/opt/IBMJava2-amd64-142/jre/bin:/opt/IBMJava2-amd64-142/jre/bin:/opt/IBMJava2-amd64-142/jre/bin/j9vm:/opt/IBMJava2-amd64-142/jre/bin:/usr/sap/SM1/DVEBMGS40/exe:/usr/sap/SM1/DVEBMGS40/exe:/usr/sap/SM1/DVEBMGS40/exe:/tmp/sapinst_exe.7551.1151567769:/usr/sap/SM1/SYS/exe/run:/sapdb/programs/lib:/usr/lib:/usr/sap/SM1/DVEBMGS40/j2ee/os_libs:/usr/sap/SM1/DVEBMGS40/exe:/usr/sap/SM1/DVEBMGS40/exe:/usr/sap/SM1/DVEBMGS40/exe:/usr/sap/SM1/SYS/exe/run:/sapdb/programs/lib
-> arg[ 19]: -Dmemory.manager=2048M
-> arg[ 20]: -Xmx2048M
-> arg[ 21]: -Xms2048M
-> arg[ 22]: -DLoadBalanceRestricted=no
-> arg[ 23]: -Djstartup.mode=JCONTROL
-> arg[ 24]: -Djstartup.ownProcessId=30385
-> arg[ 25]: -Djstartup.ownHardwareId=X1817543257
-> arg[ 26]: -Djstartup.whoami=server
-> arg[ 27]: -Djstartup.debuggable=no
-> arg[ 28]: -DSAPINFO=SM1_40_server
-> arg[ 29]: -DSAPSTART=1
-> arg[ 30]: -DCONNECT_PORT=60030
-> arg[ 31]: -DSAPSYSTEM=40
-> arg[ 32]: -DSAPSYSTEMNAME=SM1
-> arg[ 33]: -DSAPMYNAME=sm1-ci_SM1_40
-> arg[ 34]: -DSAPPROFILE=/usr/sap/SM1/SYS/profile/SM1_DVEBMGS40_sm1-ci
-> arg[ 35]: -DFRFC_FALLBACK=ON
-> arg[ 36]: -DFRFC_FALLBACK_HOST=localhost
-> arg[ 37]: -DSAPSTARTUP=1
-> arg[ 38]: -DSAPSYSTEM=40
-> arg[ 39]: -DSAPSYSTEMNAME=SM1
-> arg[ 40]: -DSAPMYNAME=sm1-ci_SM1_40
-> arg[ 41]: -DSAPDBHOST=sm1-db
-> arg[ 42]: -Dj2ee.dbhost=sm1-db
[Thr 1077946720] JHVM_LoadJavaVM: Java VM created OK.
JHVM_BuildArgumentList: main method arguments of node [server0]
[Thr 1082288480] Tue May 22 14:54:18 2007
[Thr 1082288480] JHVM_RegisterNatives: registering methods in com.sap.bc.krn.perf.PerfTimes
[Thr 1082288480] JHVM_RegisterNatives: registering methods in com.sap.bc.proj.jstartup.JStartupFramework
[Thr 1082288480] JLaunchISetClusterId: set cluster id 401326950
[Thr 1077946720] Tue May 22 15:09:19 2007
[Thr 1077946720] JLaunchIExitJava: exit hook is called (rc = 0)
[Thr 1077946720] SigISetIgnoreAction : SIG_IGN for signal 17
[Thr 1077946720] JLaunchCloseProgram: good bye (exitcode = 0)
trc file: "/usr/sap/SM1/DVEBMGS40/work/dev_server0", trc level: 1, release: "700"
node name : ID401326950
pid : 31835
system name : SM1
system nr. : 40
started at : Tue May 22 15:09:21 2007
arguments :
arg[00] : /usr/sap/SM1/DVEBMGS40/exe/jlaunch
arg[01] : pf=/usr/sap/SM1/SYS/profile/SM1_DVEBMGS40_sm1-ci
arg[02] : -DSAPINFO=SM1_40_server
arg[03] : pf=/usr/sap/SM1/SYS/profile/SM1_DVEBMGS40_sm1-ci
arg[04] : -DSAPSTART=1
arg[05] : -DCONNECT_PORT=60030
arg[06] : -DSAPSYSTEM=40
arg[07] : -DSAPSYSTEMNAME=SM1
arg[08] : -DSAPMYNAME=sm1-ci_SM1_40
arg[09] : -DSAPPROFILE=/usr/sap/SM1/SYS/profile/SM1_DVEBMGS40_sm1-ci
arg[10] : -DFRFC_FALLBACK=ON
arg[11] : -DFRFC_FALLBACK_HOST=localhost
[Thr 182906379008] Tue May 22 15:09:21 2007
[Thr 182906379008] *** WARNING => INFO: Unknown property [instance.box.number=SM1DVEBMGS40sm1-ci] [jstartxx_mt. 841]
[Thr 182906379008] *** WARNING => INFO: Unknown property [instance.en.host=sm1-scs] [jstartxx_mt. 841]
[Thr 182906379008] *** WARNING => INFO: Unknown property [instance.en.port=3241] [jstartxx_mt. 841]
[Thr 182906379008] *** WARNING => INFO: Unknown property [instance.system.id=40] [jstartxx_mt. 841]
JStartupReadInstanceProperties: read instance properties [/usr/sap/SM1/DVEBMGS40/j2ee/cluster/instance.properties]
-> ms host : sm1-scs
-> ms port : 3944
-> OS libs : /usr/sap/SM1/DVEBMGS40/j2ee/os_libs
-> Admin URL :
-> run mode : NORMAL
-> run action : NONE
-> enabled : yes
Used property files
-> files [00] : /usr/sap/SM1/DVEBMGS40/j2ee/cluster/instance.properties
Instance properties
-> ms host : sm1-scs
-> ms port : 3944
-> os libs : /usr/sap/SM1/DVEBMGS40/j2ee/os_libs
-> admin URL :
-> run mode : NORMAL
-> run action : NONE
-> enabled : yes
Bootstrap nodes
-> [00] bootstrap : /usr/sap/SM1/DVEBMGS40/j2ee/cluster/instance.properties
-> [01] bootstrap_ID40132690 : /usr/sap/SM1/DVEBMGS40/j2ee/cluster/instance.properties
-> [02] bootstrap_ID40132695 : /usr/sap/SM1/DVEBMGS40/j2ee/cluster/instance.properties
Worker nodes
-> [00] ID401326900 : /usr/sap/SM1/DVEBMGS40/j2ee/cluster/instance.properties
-> [01] ID401326950 : /usr/sap/SM1/DVEBMGS40/j2ee/cluster/instance.properties
[Thr 182906379008] JLaunchRequestQueueInit: create named pipe for ipc
[Thr 182906379008] JLaunchRequestQueueInit: create pipe listener thread
[Thr 1074792800] JLaunchRequestFunc: Thread 1074792800 started as listener thread for np messages.
[Thr 1076894048] WaitSyncSemThread: Thread 1076894048 started as semaphore monitor thread.
[Thr 182906379008] SigISetDefaultAction : default handling for signal 17
[Thr 182906379008] NiInit3: NI already initialized; param 'maxHandles' ignored (1;202)
[Thr 182906379008] CPIC (version=700.2006.09.13)
[Thr 182906379008] *** WARNING => Maximum Java heap size specified twice (through maxHeapSize and in javaParameters) - using -Xmx2048M [jstartxx_mt. 2604]
[Thr 182906379008] [Node: server0] java home is set by profile parameter
Java Home: /usr/lib/java
[Thr 182906379008] JStartupICheckFrameworkPackage: can't find framework package /usr/sap/SM1/DVEBMGS40/exe/jvmx.jar
JStartupIReadSection: read node properties [ID401326950]
-> node name : server0
-> node type : server
-> node execute : yes
-> jlaunch parameters :
-> java path : /usr/lib/java
-> java parameters : -Djava.security.policy=./java.policy -Djava.security.egd=file:/dev/urandom -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy -Djco.jarm=1 -verbose:gc -Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.services.ts.jts.ots.PortableInterceptor.JTSInitializer -Xmn400M -Xgcpolicy:gencon -Xtrace -Xsoftrefthreshold0
-> java vm version : J2RE 1.4.2 IBM J9 2.2 Linux amd64-64 j9xa64142-20060428 (JIT enabled)
-> java vm vendor : IBM J9SE VM (IBM Corporation)
-> java vm type : <default>
-> java vm cpu : amd64
-> heap size : 2048M
-> init heap size : 2048M
-> root path : /usr/sap/SM1/DVEBMGS40/j2ee/cluster/server0
-> class path : ./bin/boot/boot.jar:./bin/boot/jaas.jar:./bin/system/bytecode.jar:.
-> OS libs path : /usr/sap/SM1/DVEBMGS40/j2ee/os_libs
-> main class : com.sap.engine.boot.Start
-> framework class : com.sap.bc.proj.jstartup.JStartupFramework
-> registr. class : com.sap.bc.proj.jstartup.JStartupNatives
-> framework path : /usr/sap/SM1/DVEBMGS40/exe/jstartup.jar:/usr/sap/SM1/DVEBMGS40/exe/jvmx.jar
-> shutdown class : com.sap.engine.boot.Start
-> parameters :
-> debuggable : no
-> debug mode : no
-> debug port : 54021
-> shutdown timeout : 120000
[Thr 182906379008] JLaunchISetDebugMode: set debug mode [no]
[Thr 1077946720] JLaunchIStartFunc: Thread 1077946720 started as Java VM thread.
JHVM_LoadJavaVM: VM Arguments of node [server0]
-> stack : 1048576 Bytes
-> arg[ 0]: exit
-> arg[ 1]: abort
-> arg[ 2]: vfprintf
-> arg[ 3]: -Djava.security.policy=./java.policy
-> arg[ 4]: -Djava.security.egd=file:/dev/urandom
-> arg[ 5]: -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy
-> arg[ 6]: -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy
-> arg[ 7]: -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
-> arg[ 8]: -Djco.jarm=1
-> arg[ 9]: -verbose:gc
-> arg[ 10]: -Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.services.ts.jts.ots.PortableInterceptor.JTSInitializer
-> arg[ 11]: -Xmn400M
-> arg[ 12]: -Xgcpolicy:gencon
-> arg[ 13]: -Xtrace
-> arg[ 14]: -Xsoftrefthreshold0
-> arg[ 15]: -Dsys.global.dir=/usr/sap/SM1/SYS/global
-> arg[ 16]: -Dapplication.home=/usr/sap/SM1/DVEBMGS40/exe
-> arg[ 17]: -Djava.class.path=/usr/sap/SM1/DVEBMGS40/exe/jstartup.jar:/usr/sap/SM1/DVEBMGS40/exe/jvmx.jar:./bin/boot/boot.jar:./bin/boot/jaas.jar:./bin/system/bytecode.jar:.
-> arg[ 18]: -Djava.library.path=/opt/IBMJava2-amd64-142/jre/bin:/opt/IBMJava2-amd64-142/jre/bin:/opt/IBMJava2-amd64-142/jre/bin:/opt/IBMJava2-amd64-142/jre/bin/j9vm:/opt/IBMJava2-amd64-142/jre/bin:/usr/sap/SM1/DVEBMGS40/exe:/usr/sap/SM1/DVEBMGS40/exe:/usr/sap/SM1/DVEBMGS40/exe:/tmp/sapinst_exe.7551.1151567769:/usr/sap/SM1/SYS/exe/run:/sapdb/programs/lib:/usr/lib:/usr/sap/SM1/DVEBMGS40/j2ee/os_libs:/usr/sap/SM1/DVEBMGS40/exe:/usr/sap/SM1/DVEBMGS40/exe:/usr/sap/SM1/DVEBMGS40/exe:/usr/sap/SM1/SYS/exe/run:/sapdb/programs/lib
-> arg[ 19]: -Dmemory.manager=2048M
-> arg[ 20]: -Xmx2048M
-> arg[ 21]: -Xms2048M
-> arg[ 22]: -DLoadBalanceRestricted=no
-> arg[ 23]: -Djstartup.mode=JCONTROL
-> arg[ 24]: -Djstartup.ownProcessId=31835
-> arg[ 25]: -Djstartup.ownHardwareId=X1817543257
-> arg[ 26]: -Djstartup.whoami=server
-> arg[ 27]: -Djstartup.debuggable=no
-> arg[ 28]: -DSAPINFO=SM1_40_server
-> arg[ 29]: -DSAPSTART=1
-> arg[ 30]: -DCONNECT_PORT=60030
-> arg[ 31]: -DSAPSYSTEM=40
-> arg[ 32]: -DSAPSYSTEMNAME=SM1
-> arg[ 33]: -DSAPMYNAME=sm1-ci_SM1_40
-> arg[ 34]: -DSAPPROFILE=/usr/sap/SM1/SYS/profile/SM1_DVEBMGS40_sm1-ci
-> arg[ 35]: -DFRFC_FALLBACK=ON
-> arg[ 36]: -DFRFC_FALLBACK_HOST=localhost
-> arg[ 37]: -DSAPSTARTUP=1
-> arg[ 38]: -DSAPSYSTEM=40
-> arg[ 39]: -DSAPSYSTEMNAME=SM1
-> arg[ 40]: -DSAPMYNAME=sm1-ci_SM1_40
-> arg[ 41]: -DSAPDBHOST=sm1-db
-> arg[ 42]: -Dj2ee.dbhost=sm1-db
[Thr 1077946720] Tue May 22 15:09:22 2007
[Thr 1077946720] JHVM_LoadJavaVM: Java VM created OK.
JHVM_BuildArgumentList: main method arguments of node [server0]
[Thr 1082288480] Tue May 22 15:09:24 2007
[Thr 1082288480] JHVM_RegisterNatives: registering methods in com.sap.bc.krn.perf.PerfTimes
[Thr 1082288480] JHVM_RegisterNatives: registering methods in com.sap.bc.proj.jstartup.JStartupFramework
[Thr 1082288480] JLaunchISetClusterId: set cluster id 401326950
[Thr 1077946720] Tue May 22 15:24:25 2007
[Thr 1077946720] JLaunchIExitJava: exit hook is called (rc = 0)
[Thr 1077946720] SigISetIgnoreAction : SIG_IGN for signal 17
[Thr 1077946720] JLaunchCloseProgram: good bye (exitcode = 0)
trc file: "/usr/sap/SM1/DVEBMGS40/work/dev_server0", trc level: 1, release: "700"
node name : ID401326950
pid : 32545
system name : SM1
system nr. : 40
started at : Tue May 22 15:24:27 2007
arguments :
arg[00] : /usr/sap/SM1/DVEBMGS40/exe/jlaunch
arg[01] : pf=/usr/sap/SM1/SYS/profile/SM1_DVEBMGS40_sm1-ci
arg[02] : -DSAPINFO=SM1_40_server
arg[03] : pf=/usr/sap/SM1/SYS/profile/SM1_DVEBMGS40_sm1-ci
arg[04] : -DSAPSTART=1
arg[05] : -DCONNECT_PORT=60030
arg[06] : -DSAPSYSTEM=40
arg[07] : -DSAPSYSTEMNAME=SM1
arg[08] : -DSAPMYNAME=sm1-ci_SM1_40
arg[09] : -DSAPPROFILE=/usr/sap/SM1/SYS/profile/SM1_DVEBMGS40_sm1-ci
arg[10] : -DFRFC_FALLBACK=ON
arg[11] : -DFRFC_FALLBACK_HOST=localhost
[Thr 182906379008] Tue May 22 15:24:27 2007
[Thr 182906379008] *** WARNING => INFO: Unknown property [instance.box.number=SM1DVEBMGS40sm1-ci] [jstartxx_mt. 841]
[Thr 182906379008] *** WARNING => INFO: Unknown property [instance.en.host=sm1-scs] [jstartxx_mt. 841]
[Thr 182906379008] *** WARNING => INFO: Unknown property [instance.en.port=3241] [jstartxx_mt. 841]
[Thr 182906379008] *** WARNING => INFO: Unknown property [instance.system.id=40] [jstartxx_mt. 841]
JStartupReadInstanceProperties: read instance properties [/usr/sap/SM1/DVEBMGS40/j2ee/cluster/instance.properties]
-> ms host : sm1-scs
-> ms port : 3944
-> OS libs : /usr/sap/SM1/DVEBMGS40/j2ee/os_libs
-> Admin URL :
-> run mode : NORMAL
-> run action : NONE
-> enabled : yes
Used property files
-> files [00] : /usr/sap/SM1/DVEBMGS40/j2ee/cluster/instance.properties
Instance properties
-> ms host : sm1-scs
-> ms port : 3944
-> os libs : /usr/sap/SM1/DVEBMGS40/j2ee/os_libs
-> admin URL :
-> run mode : NORMAL
-> run action : NONE
-> enabled : yes
Bootstrap nodes
-> [00] bootstrap : /usr/sap/SM1/DVEBMGS40/j2ee/cluster/instance.properties
-> [01] bootstrap_ID40132690 : /usr/sap/SM1/DVEBMGS40/j2ee/cluster/instance.properties
-> [02] bootstrap_ID40132695 : /usr/sap/SM1/DVEBMGS40/j2ee/cluster/instance.properties
Worker nodes
-> [00] ID401326900 : /usr/sap/SM1/DVEBMGS40/j2ee/cluster/instance.properties
-> [01] ID401326950 : /usr/sap/SM1/DVEBMGS40/j2ee/cluster/instance.properties
[Thr 182906379008] JLaunchRequestQueueInit: create named pipe for ipc
[Thr 182906379008] JLaunchRequestQueueInit: create pipe listener thread
[Thr 1074792800] JLaunchRequestFunc: Thread 1074792800 started as listener thread for np messages.
[Thr 1076894048] WaitSyncSemThread: Thread 1076894048 started as semaphore monitor thread.
[Thr 182906379008] SigISetDefaultAction : default handling for signal 17
[Thr 182906379008] NiInit3: NI already initialized; param 'maxHandles' ignored (1;202)
[Thr 182906379008] CPIC (version=700.2006.09.13)
[Thr 182906379008] *** WARNING => Maximum Java heap size specified twice (through maxHeapSize and in javaParameters) - using -Xmx2048M [jstartxx_mt. 2604]
[Thr 182906379008] [Node: server0] java home is set by profile parameter
Java Home: /usr/lib/java
[Thr 182906379008] JStartupICheckFrameworkPackage: can't find framework package /usr/sap/SM1/DVEBMGS40/exe/jvmx.jar
JStartupIReadSection: read node properties [ID401326950]
-> node name : server0
-> node type : server
-> node execute : yes
-> jlaunch parameters :
-> java path : /usr/lib/java
-> java parameters : -Djava.security.policy=./java.policy -Djava.security.egd=file:/dev/urandom -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy -Djco.jarm=1 -verbose:gc -Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.services.ts.jts.ots.PortableInterceptor.JTSInitializer -Xmn400M -Xgcpolicy:gencon -Xtrace -Xsoftrefthreshold0
-> java vm version : J2RE 1.4.2 IBM J9 2.2 Linux amd64-64 j9xa64142-20060428 (JIT enabled)
-> java vm vendor : IBM J9SE VM (IBM Corporation)
-> java vm type : <default>
-> java vm cpu : amd64
-> heap size : 2048M
-> init heap size : 2048M
-> root path : /usr/sap/SM1/DVEBMGS40/j2ee/cluster/server0
-> class path : ./bin/boot/boot.jar:./bin/boot/jaas.jar:./bin/system/bytecode.jar:.
-> OS libs path : /usr/sap/SM1/DVEBMGS40/j2ee/os_libs
-> main class : com.sap.engine.boot.Start
-> framework class : com.sap.bc.proj.jstartup.JStartupFramework
-> registr. class : com.sap.bc.proj.jstartup.JStartupNatives
-> framework path : /usr/sap/SM1/DVEBMGS40/exe/jstartup.jar:/usr/sap/SM1/DVEBMGS40/exe/jvmx.jar
-> shutdown class : com.sap.engine.boot.Start
-> parameters :
-> debuggable : no
-> debug mode : no
-> debug port : 54021
-> shutdown timeout : 120000
[Thr 182906379008] JLaunchISetDebugMode: set debug mode [no]
[Thr 1077946720] JLaunchIStartFunc: Thread 1077946720 started as Java VM thread.
JHVM_LoadJavaVM: VM Arguments of node [server0]
-> stack : 1048576 Bytes
-> arg[ 0]: exit
-> arg[ 1]: abort
-> arg[ 2]: vfprintf
-> arg[ 3]: -Djava.security.policy=./java.policy
-> arg[ 4]: -Djava.security.egd=file:/dev/urandom
-> arg[ 5]: -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy
-> arg[ 6]: -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy
-> arg[ 7]: -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
-> arg[ 8]: -Djco.jarm=1
-> arg[ 9]: -verbose:gc
-> arg[ 10]: -Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.services.ts.jts.ots.PortableInterceptor.JTSInitializer
-> arg[ 11]: -Xmn400M
-> arg[ 12]: -Xgcpolicy:gencon
-> arg[ 13]: -Xtrace
-> arg[ 14]: -Xsoftrefthreshold0
-> arg[ 15]: -Dsys.global.dir=/usr/sap/SM1/SYS/global
-> arg[ 16]: -Dapplication.home=/usr/sap/SM1/DVEBMGS40/exe
-> arg[ 17]: -Djava.class.path=/usr/sap/SM1/DVEBMGS40/exe/jstartup.jar:/usr/sap/SM1/DVEBMGS40/exe/jvmx.jar:./bin/boot/boot.jar:./bin/boot/jaas.jar:./bin/system/bytecode.jar:.
-> arg[ 18]: -Djava.library.path=/opt/IBMJava2-amd64-142/jre/bin:/opt/IBMJava2-amd64-142/jre/bin:/opt/IBMJava2-amd64-142/jre/bin:/opt/IBMJava2-amd64-142/jre/bin/j9vm:/opt/IBMJava2-amd64-142/jre/bin:/usr/sap/SM1/DVEBMGS40/exe:/usr/sap/SM1/DVEBMGS40/exe:/usr/sap/SM1/DVEBMGS40/exe:/tmp/sapinst_exe.7551.1151567769:/usr/sap/SM1/SYS/exe/run:/sapdb/programs/lib:/usr/lib:/usr/sap/SM1/DVEBMGS40/j2ee/os_libs:/usr/sap/SM1/DVEBMGS40/exe:/usr/sap/SM1/DVEBMGS40/exe:/usr/sap/SM1/DVEBMGS40/exe:/usr/sap/SM1/SYS/exe/run:/sapdb/programs/lib
-> arg[ 19]: -Dmemory.manager=2048M
-> arg[ 20]: -Xmx2048M
-> arg[ 21]: -Xms2048M
-> arg[ 22]: -DLoadBalanceRestricted=no
-> arg[ 23]: -Djstartup.mode=JCONTROL
-> arg[ 24]: -Djstartup.ownProcessId=32545
-> arg[ 25]: -Djstartup.ownHardwareId=X1817543257
-> arg[ 26]: -Djstartup.whoami=server
-> arg[ 27]: -Djstartup.debuggable=no
-> arg[ 28]: -DSAPINFO=SM1_40_server
-> arg[ 29]: -DSAPSTART=1
-> arg[ 30]: -DCONNECT_PORT=60030
-> arg[ 31]: -DSAPSYSTEM=40
-> arg[ 32]: -DSAPSYSTEMNAME=SM1
-> arg[ 33]: -DSAPMYNAME=sm1-ci_SM1_40
-> arg[ 34]: -DSAPPROFILE=/usr/sap/SM1/SYS/profile/SM1_DVEBMGS40_sm1-ci
-> arg[ 35]: -DFRFC_FALLBACK=ON
-> arg[ 36]: -DFRFC_FALLBACK_HOST=localhost
-> arg[ 37]: -DSAPSTARTUP=1
-> arg[ 38]: -DSAPSYSTEM=40
-> arg[ 39]: -DSAPSYSTEMNAME=SM1
-> arg[ 40]: -DSAPMYNAME=sm1-ci_SM1_40
-> arg[ 41]: -DSAPDBHOST=sm1-db
-> arg[ 42]: -Dj2ee.dbhost=sm1-db
[Thr 1077946720] Tue May 22 15:24:28 2007
[Thr 1077946720] JHVM_LoadJavaVM: Java VM created OK.
JHVM_BuildArgumentList: main method arguments of node [server0]
[Thr 1082288480] Tue May 22 15:24:30 2007
[Thr 1082288480] JHVM_RegisterNatives: registering methods in com.sap.bc.krn.perf.PerfTimes
[Thr 1082288480] JHVM_RegisterNatives: registering methods in com.sap.bc.proj.jstartup.JStartupFramework
[Thr 1082288480] JLaunchISetClusterId: set cluster id 401326950
[Thr 1077946720] Tue May 22 15:39:31 2007
[Thr 1077946720] JLaunchIExitJava: exit hook is called (rc = 0)
[Thr 1077946720] SigISetIgnoreAction : SIG_IGN for signal 17
[Thr 1077946720] JLaunchCloseProgram: good bye (exitcode = 0)Werner,
First check the instance.properties file to see if it has picked up the change. You may need to change it there.
Also, these need to be changed in your default profile:
j2ee/scs/host = <host>
j2ee/scs/system = 44
j2ee/ms/port = 3944
Also, you have max heap specified twice, make sure this is only specified once by taking it out of the body of the java parameters. It can cause other problems being in there twice.
[Thr 182906379008] *** WARNING => Maximum Java heap size specified twice (through maxHeapSize and in javaParameters) - using -Xmx2048M [jstartxx_mt. 2604]
-jwise -
Sap service fails after switching to the second node in HA system.
Hello all,
We have installed the HA mscs cluster installation for ECC6.0(my SAP erp 2005) system.The ASCS+SCS isntance and the DB instance are the failover resources.
When the ASCS+SCS(sap cluster group) fail over to the next node the service sap_<sid>_00 (ascs) and sap_<sid>_01(scs) fails to start automatically and we have to manually start the instance from the services console by giving the sapservice<sid> password to start the services.
when we try to start the service without giving the password then the system gives a message unable to start due to logon failure and after giving the password it shows that the user has been been granted to logon as a service user.
Pl help resolve this issue.
thx
satyajitA change to the zpool_import() management of the zpool.cache file, as delivered by Solaris 10 kernel patches 137137-09 (for SPARC) or 137138-09 (for x86), might cause systems that have their shared ZFS (zfs(1M)) storage pools under the control of HAStoragePlus to be simultaneously imported on multiple cluster nodes. Importing a ZFS storage pool on multiple cluster nodes will result in pool corruption, which might cause data integrity issues or cause a cluster node to panic.
To avoid this problem, install Solaris 10 patch 139579-02 (for SPARC) or 139580-02 (for x86) immediately after you install 137137-09 or 137138-09 but before you reboot the cluster nodes.
Alternatively, only on the Solaris 10 5/08 OS, remove the affected patch before any ZFS pools are simultaneously imported to multiple cluster nodes. You cannot remove patch 137137-09 or 137138-09 from the Solaris 10 10/08 OS, because these patches are preinstalled on that release. -
Perl applications failing after switch from 5.16 to 5.18
I recently updated my system and it seems perl recieved an update too as it is now at 5.18. However, after the system update I could not start rxvt-unicode anymore (it segfaulted). After some research and reinstalling I found that perl is responsible for that: Going back to 5.16 fixed it.
To keep a long story short: A lot of my perl modules could not handle the new perl version. I am not a 100% sure if these would all be aur packages but I suppose not, as I also had an issue with ImageMagick (its' perl module). Finally I somehow hacked together a few commands that reinstalled most of my perl modules. However, this does not string strike me as a pretty solution (as I just searched for packages containing "perl" and reinstalled them.
For example, ImageMagick needed this as a seperate install. Now, I am wondering whether there is way to do something about this problem. I can't imagine I am the only one having a problem with this perl update, so maybe there is someone who could help me straighten this up.
Thanks in advance,
javexMany things broke with perl 5.18, I think you should report bugs upstream.
Marc Lehmann (the guy behind urxvt) was pretty unhappy about perl 5.18 http://lists.schmorp.de/pipermail/rxvt- … 01795.html -
User Profiles Synch Service starting failes after "ILM Configuration: Starting services"
Hello guys.
I tried to configure user profiles synchronization and it could not be started without any problems as expected :)
This time I got the following error in logs:
02.05.2013 10:54:03.34 OWSTIMER.EXE (0x17DC)
0x183C SharePoint Portal Server
User Profiles 9q1k
Medium ILM Configuration: Starting services.
0160471f-15fc-4d97-8227-05b86f4d0fc7
02.05.2013 10:54:33.52 OWSTIMER.EXE (0x17DC)
0x183C SharePoint Portal Server
User Profiles 9q15
High UserProfileApplication.SynchronizeMIIS: Failed to configure ILM, will attempt during next rerun. Exception: System.FormatException: Index (zero based) must be greater than or equal to zero and less than the size
of the argument list. at System.Text.StringBuilder.AppendFormat(IFormatProvider provider, String format, Object[] args) at System.String.Format(IFormatProvider provider, String format, Object[] args) at Microsoft.Office.Server.Administration.ProfileSynchronizationServiceInstance.IsStarted(ServiceController
controller) at Microsoft.Office.Server.Administration.ProfileSynchronizationServiceInstance.WaitUntilStarted() at Microsoft.Office.Server.Administration.UserProfileApplication.SetupSynchronizationService(ProfileSynchronizationServiceInstance
profileSyncInstance). 0160471f-15fc-4d97-8227-05b86f4d0fc7
02.05.2013 10:54:33.52 OWSTIMER.EXE (0x17DC)
0x183C SharePoint Portal Server
User Profiles 9i1u
Medium UserProfileApplication.SynchronizeMIIS: End setup for 'UserProfilesService'.
0160471f-15fc-4d97-8227-05b86f4d0fc7
So, what I have and what I've done:.
1) I have a test 2-servers farm installation (Database server + WFE/Application server); SQL Server 2008 R2 SP2, SHP 2010 SP1 + October 2012 CU; There are no any service applications except default ones(Security Token Service and Application Discovery
and Load Balancer Service Application) as well as there are no any services started except default :)
2) I created a site collection and manage path for MySites, created a new UPA and its proxy.
That's all. Now, if I try starting User Profiles Synchronization Service, it stucks on "starting" for about 10 mins and I see the error above in ULS. Hope you can somehow help me.
By the way, I don't want a both sides synchronization this time, I just need to check some stuff with People Search. Will "Read" rights for Managed Account in AD be enough to export profiles from AD? (I mean if I select my farm account as a synchronization
account, will it work?)
Thank's in advance!
Anton.
UPDATED
The problem probably was due to the lack of internet access. As Raymond
Diack said:
"the farm account needs internet access to do a CRL check to these sites:
crl.microsoft.com
ctldl.windowsupdate.com
ctldl.windowsupdate.nsatc.net
www.update.microsoft.com.nsatc.net "Sure, here is the stack near the error without any filters:
11:13:11.88 OWSTIMER.EXE (0x0AA8) 0x0EA8 SharePoint Portal Server User Profiles 9q1j Medium ILM Configuration: Opening firewall ports. 589d9196-6647-4432-9ab0-a389871310b7
11:13:12.13 OWSTIMER.EXE (0x0AA8) 0x0EA8 SharePoint Portal Server User Profiles 9q1k Medium ILM Configuration: Starting services. 589d9196-6647-4432-9ab0-a389871310b7
11:13:12.36 w3wp.exe (0x1364) 0x0CA0 SharePoint Foundation Topology e5mc Medium WcfSendRequest: RemoteAddress: 'http://hq-tcc-app-02:32843/900539dde24c4bc9a0db06a9f9fe6ebf/MetadataWebService.svc' Channel: 'Microsoft.SharePoint.Taxonomy.IMetadataWebServiceApplication' Action: 'http://schemas.microsoft.com/sharepoint/taxonomy/soap/IDataAccessReadOnly/GetChanges' MessageId: 'urn:uuid:80a1f95b-37a3-45f1-89a6-f33de57b678a'
11:13:12.36 w3wp.exe (0x0788) 0x0D2C SharePoint Foundation Topology e5mb Medium WcfReceiveRequest: LocalAddress: 'http://hq-tcc-app-02.corp.fsk-ees.local:32843/900539dde24c4bc9a0db06a9f9fe6ebf/MetadataWebService.svc' Channel: 'System.ServiceModel.Channels.ServiceChannel' Action: 'http://schemas.microsoft.com/sharepoint/taxonomy/soap/IDataAccessReadOnly/GetChanges' MessageId: 'urn:uuid:80a1f95b-37a3-45f1-89a6-f33de57b678a' 75b52d1d-0e9e-45a6-8122-c578bc8aeaf7
11:13:12.36 w3wp.exe (0x0788) 0x0D2C SharePoint Foundation Monitoring nasq Medium Entering monitored scope (ExecuteWcfServerOperation) 75b52d1d-0e9e-45a6-8122-c578bc8aeaf7
11:13:12.36 w3wp.exe (0x0788) 0x0D2C SharePoint Server Taxonomy fuc5 Medium MetadataWebServiceApplication.GetChanges called on 'Служба управляемых метаданных' starting. 75b52d1d-0e9e-45a6-8122-c578bc8aeaf7
11:13:12.36 w3wp.exe (0x0788) 0x0D2C SharePoint Server Taxonomy fuc6 Medium MetadataWebServiceApplication.GetChanges called on 'Служба управляемых метаданных' completed. 75b52d1d-0e9e-45a6-8122-c578bc8aeaf7
11:13:12.38 w3wp.exe (0x0788) 0x0D2C SharePoint Foundation Monitoring b4ly Medium Leaving Monitored Scope (ExecuteWcfServerOperation). Время выполнения=4,01622273221876 75b52d1d-0e9e-45a6-8122-c578bc8aeaf7
11:13:12.75 OWSTIMER.EXE (0x0AA8) 0x16F0 SharePoint Foundation Monitoring nasq Medium Entering monitored scope (Timer Job job-timer-locks) ea70e10e-4455-47ea-a3fd-e7cb0f0a9ce4
11:13:12.75 OWSTIMER.EXE (0x0AA8) 0x16F0 SharePoint Foundation Monitoring b4ly Medium Leaving Monitored Scope (Timer Job job-timer-locks). Время выполнения=4,16512433842849 ea70e10e-4455-47ea-a3fd-e7cb0f0a9ce4
11:13:22.52 w3wp.exe (0x1364) 0x0CA0 SharePoint Foundation Topology e5mc Medium WcfSendRequest: RemoteAddress: 'http://hq-tcc-app-02:32843/900539dde24c4bc9a0db06a9f9fe6ebf/MetadataWebService.svc' Channel: 'Microsoft.SharePoint.Taxonomy.IMetadataWebServiceApplication' Action: 'http://schemas.microsoft.com/sharepoint/taxonomy/soap/IDataAccessReadOnly/GetChanges' MessageId: 'urn:uuid:5b799d56-3784-48ff-beaf-6fb6bfeade78'
11:13:22.52 w3wp.exe (0x0788) 0x1544 SharePoint Foundation Topology e5mb Medium WcfReceiveRequest: LocalAddress: 'http://hq-tcc-app-02.corp.fsk-ees.local:32843/900539dde24c4bc9a0db06a9f9fe6ebf/MetadataWebService.svc' Channel: 'System.ServiceModel.Channels.ServiceChannel' Action: 'http://schemas.microsoft.com/sharepoint/taxonomy/soap/IDataAccessReadOnly/GetChanges' MessageId: 'urn:uuid:5b799d56-3784-48ff-beaf-6fb6bfeade78' 941bbfb5-84aa-411e-b310-74830120b860
11:13:22.52 w3wp.exe (0x0788) 0x1544 SharePoint Foundation Monitoring nasq Medium Entering monitored scope (ExecuteWcfServerOperation) 941bbfb5-84aa-411e-b310-74830120b860
11:13:22.52 w3wp.exe (0x0788) 0x1544 SharePoint Server Taxonomy fuc5 Medium MetadataWebServiceApplication.GetChanges called on 'Служба управляемых метаданных' starting. 941bbfb5-84aa-411e-b310-74830120b860
11:13:22.52 w3wp.exe (0x0788) 0x1544 SharePoint Server Taxonomy fuc6 Medium MetadataWebServiceApplication.GetChanges called on 'Служба управляемых метаданных' completed. 941bbfb5-84aa-411e-b310-74830120b860
11:13:22.52 w3wp.exe (0x0788) 0x1544 SharePoint Foundation Monitoring b4ly Medium Leaving Monitored Scope (ExecuteWcfServerOperation). Время выполнения=2,92432418086656 941bbfb5-84aa-411e-b310-74830120b860
11:13:26.78 OWSTIMER.EXE (0x0AA8) 0x0894 SharePoint Foundation Monitoring nasq Medium Entering monitored scope (Timer Job SchedulingUnpublish) 6044b3fe-8ca7-4f76-81b0-ea55e6795d5b
11:13:26.78 OWSTIMER.EXE (0x0AA8) 0x0894 SharePoint Foundation Monitoring b4ly Medium Leaving Monitored Scope (Timer Job SchedulingUnpublish). Время выполнения=2,56094000773841 6044b3fe-8ca7-4f76-81b0-ea55e6795d5b
11:13:32.66 w3wp.exe (0x1364) 0x0CA0 SharePoint Foundation Topology e5mc Medium WcfSendRequest: RemoteAddress: 'http://hq-tcc-app-02:32843/900539dde24c4bc9a0db06a9f9fe6ebf/MetadataWebService.svc' Channel: 'Microsoft.SharePoint.Taxonomy.IMetadataWebServiceApplication' Action: 'http://schemas.microsoft.com/sharepoint/taxonomy/soap/IDataAccessReadOnly/GetChanges' MessageId: 'urn:uuid:f5648c05-71d7-443c-b12d-946eb36bcb3f'
11:13:32.66 w3wp.exe (0x0788) 0x1544 SharePoint Foundation Topology e5mb Medium WcfReceiveRequest: LocalAddress: 'http://hq-tcc-app-02.corp.fsk-ees.local:32843/900539dde24c4bc9a0db06a9f9fe6ebf/MetadataWebService.svc' Channel: 'System.ServiceModel.Channels.ServiceChannel' Action: 'http://schemas.microsoft.com/sharepoint/taxonomy/soap/IDataAccessReadOnly/GetChanges' MessageId: 'urn:uuid:f5648c05-71d7-443c-b12d-946eb36bcb3f' 1af7e327-bb71-49f8-a598-2e85ae5ce2a6
11:13:32.66 w3wp.exe (0x0788) 0x1544 SharePoint Foundation Monitoring nasq Medium Entering monitored scope (ExecuteWcfServerOperation) 1af7e327-bb71-49f8-a598-2e85ae5ce2a6
11:13:32.66 w3wp.exe (0x0788) 0x1544 SharePoint Server Taxonomy fuc5 Medium MetadataWebServiceApplication.GetChanges called on 'Служба управляемых метаданных' starting. 1af7e327-bb71-49f8-a598-2e85ae5ce2a6
11:13:32.71 w3wp.exe (0x0788) 0x1544 SharePoint Server Taxonomy fuc6 Medium MetadataWebServiceApplication.GetChanges called on 'Служба управляемых метаданных' completed. 1af7e327-bb71-49f8-a598-2e85ae5ce2a6
11:13:32.72 w3wp.exe (0x0788) 0x1544 SharePoint Foundation Monitoring b4ly Medium Leaving Monitored Scope (ExecuteWcfServerOperation). Время выполнения=65,7127512016192 1af7e327-bb71-49f8-a598-2e85ae5ce2a6
11:13:39.79 OWSTIMER.EXE (0x0AA8) 0x0500 SharePoint Foundation Monitoring nasq Medium Entering monitored scope (Timer Job SchedulingApproval) 69e34469-a502-4257-80f4-d8fb990f2bf7
11:13:39.80 OWSTIMER.EXE (0x0AA8) 0x0500 SharePoint Foundation Monitoring b4ly Medium Leaving Monitored Scope (Timer Job SchedulingApproval). Время выполнения=11,6191443325898 69e34469-a502-4257-80f4-d8fb990f2bf7
11:13:40.33 w3wp.exe (0x1364) 0x0E98 SharePoint Portal Server Runtime 8gp7 Medium Topology cache updated. (AppDomain: /LM/W3SVC/961767364/ROOT-1-130050376913614507)
11:13:42.88 w3wp.exe (0x1364) 0x0CA0 SharePoint Foundation Topology e5mc Medium WcfSendRequest: RemoteAddress: 'http://hq-tcc-app-02:32843/900539dde24c4bc9a0db06a9f9fe6ebf/MetadataWebService.svc' Channel: 'Microsoft.SharePoint.Taxonomy.IMetadataWebServiceApplication' Action: 'http://schemas.microsoft.com/sharepoint/taxonomy/soap/IDataAccessReadOnly/GetChanges' MessageId: 'urn:uuid:23bdd02e-0716-4697-b55d-55862694ebe1'
11:13:42.89 w3wp.exe (0x0788) 0x0D2C SharePoint Foundation Topology e5mb Medium WcfReceiveRequest: LocalAddress: 'http://hq-tcc-app-02.corp.fsk-ees.local:32843/900539dde24c4bc9a0db06a9f9fe6ebf/MetadataWebService.svc' Channel: 'System.ServiceModel.Channels.ServiceChannel' Action: 'http://schemas.microsoft.com/sharepoint/taxonomy/soap/IDataAccessReadOnly/GetChanges' MessageId: 'urn:uuid:23bdd02e-0716-4697-b55d-55862694ebe1' c7b0b8bc-dad4-4863-98e0-92838dafa933
11:13:42.89 w3wp.exe (0x0788) 0x0D2C SharePoint Foundation Monitoring nasq Medium Entering monitored scope (ExecuteWcfServerOperation) c7b0b8bc-dad4-4863-98e0-92838dafa933
11:13:42.89 w3wp.exe (0x0788) 0x0D2C SharePoint Server Taxonomy fuc5 Medium MetadataWebServiceApplication.GetChanges called on 'Служба управляемых метаданных' starting. c7b0b8bc-dad4-4863-98e0-92838dafa933
11:13:42.89 w3wp.exe (0x0788) 0x0D2C SharePoint Server Taxonomy fuc6 Medium MetadataWebServiceApplication.GetChanges called on 'Служба управляемых метаданных' completed. c7b0b8bc-dad4-4863-98e0-92838dafa933
11:13:42.89 w3wp.exe (0x0788) 0x0D2C SharePoint Foundation Monitoring b4ly Medium Leaving Monitored Scope (ExecuteWcfServerOperation). Время выполнения=2,88158131829604 c7b0b8bc-dad4-4863-98e0-92838dafa933
11:13:42.89 OWSTIMER.EXE (0x0AA8) 0x0EA8 SharePoint Portal Server User Profiles 9q15 High UserProfileApplication.SynchronizeMIIS: Failed to configure ILM, will attempt during next rerun. Exception: System.FormatException: Index (zero based) must be greater than or equal to zero and less than the size of the argument list. at System.Text.StringBuilder.AppendFormat(IFormatProvider provider, String format, Object[] args) at System.String.Format(IFormatProvider provider, String format, Object[] args) at Microsoft.Office.Server.Administration.ProfileSynchronizationServiceInstance.IsStarted(ServiceController controller) at Microsoft.Office.Server.Administration.ProfileSynchronizationServiceInstance.WaitUntilStarted() at Microsoft.Office.Server.Administration.UserProfileApplication.SetupSynchronizationService(ProfileSynchronizationServiceInstance profileSyncInstance). 589d9196-6647-4432-9ab0-a389871310b7
11:13:42.89 OWSTIMER.EXE (0x0AA8) 0x0EA8 SharePoint Portal Server User Profiles 9i1u Medium UserProfileApplication.SynchronizeMIIS: End setup for 'UPS'. 589d9196-6647-4432-9ab0-a389871310b7
11:13:42.89 OWSTIMER.EXE (0x0AA8) 0x0EA8 SharePoint Foundation Topology 8xqz Medium Updating SPPersistedObject ProfileSynchronizationSetupJob Name=ProfileSynchronizationSetupJob. Version: 15232 Ensure: False, HashCode: 11248478, Id: c8e4ed56-ab72-4b99-8532-d282d3f26896, Stack: at Microsoft.SharePoint.Administration.SPPersistedObject.BaseUpdate() at Microsoft.SharePoint.Administration.SPJobDefinition.Update() at Microsoft.Office.Server.Administration.ProfileSynchronizationSetupJob.Execute(SPJobState state) at Microsoft.SharePoint.Administration.SPTimerJobInvokeInternal.Invoke(SPJobDefinition jd, Guid targetInstanceId, Boolean isTimerService, Int32& result) at Microsoft.SharePoint.Administration.SPTimerJobInvoke.Invoke(TimerJobExecuteData& data, Int32& result) 589d9196-6647-4432-9ab0-a389871310b7
11:13:42.92 OWSTIMER.EXE (0x0AA8) 0x0EA8 SharePoint Foundation Monitoring b4ly High Leaving Monitored Scope (Timer Job ProfileSynchronizationSetupJob). Время выполнения=161321,353202712 589d9196-6647-4432-9ab0-a389871310b7
11:13:42.96 OWSTIMER.EXE (0x0AA8) 0x0EA8 SharePoint Foundation Topology 8dyx High Deleting the SPPersistedObject, ProfileSynchronizationSetupJob Name=ProfileSynchronizationSetupJob. 589d9196-6647-4432-9ab0-a389871310b7 -
Display flickering after switching laptop on, display flickering after switching laptop on
after switching on my laptop the screen starts flickering.
after switching on my laptop the screen starts flickering.
-
RPC Remote calls fail after loading sibling.
Hi All,
Main loads an app compiled in 3.2. Cannot recompile legacy SWF with version of Main.
Main and Client are on the same domain. Debugging on localhost.
Sibling has RemoteObject code but never makes RemoteObject calls.
Main apps remote calls start failing after sibling is loaded.
TypeError: Error #1034: Type Coercion failed: cannot convert
mx.messaging.messages::AcknowledgeMessage@c7ab831 to mx.messaging.messages.IMessage.
<mx:SWFLoader id="swfLoader"
loadForCompatibility="true"
trustContent="false"
width="100%" height="100%"
source="ClientGuiApp3-2.swf?fredOn=false"
complete="swfComplete();"
creationComplete="initNestedAppProps();"/>
What I have done to try to fix it.
trustContent = "False" to put it in its own security domain.
I thought loadForCompatability good enough to make them use their own class definitions?
Document I found says RPC special case for multiversion Sandbox or Bootstrap.
http://help.adobe.com/en_US/Flex/4.0/html/WS2db454920e96a9e51e63e3d11c0bf69084-7f0c.html
loadForCompatibiity means sandboxing or new security domain for the sibling?
Thanks in advance,
Kevin1. Remove the WinrmIIS Extension from "Programs and Features"
2. Reboot the server
3. Execute the cmd "winrm quickconfig". This adds an exception for the remote management in the Windows firewall.
4. Install "Winrm IIS extension
5. Try open Exchange Management Console
Let me know what happens :)
Thanks for your guide;
"WinRM IIS Extension" is not installed.and firewall is off.
When I open up the Exchange Management Console ,after these message :
<Initializing ...
Setting up Remote Powershell session to: ServerName.MyDomain.net ...>
I'm seeing these errors:
<The following error occurred when setting up Remote Powershell session to 'ServerName.MyDomain.net':
Closing remote server shell instance failed with the following error message : The WinRM client cannot complete the operation within the time specified. Check if the machine name is valid and is reachable over the network and firewall exception for Windows Remote Management service is enabled. For more information, see the about Remote Troubleshooting Help topic. >
also When I open up the Exchange Management Shell,After several hours the below message remain:
<VERBOSE:Connecting to ServerName.MyDomain.net > -
When I try and start iTunes after trying to intall the 11.4 update on my Windows 7 laptop, it says to reinstall iTunes and "Windows Error Code 193" I tried ave the same failed response. Can someone help?
Hi inharmony35,
If you are having issues with iTunes after an attempted update, you may want to try the steps in the following articles:
Apple Support: Removing and reinstalling iTunes and other software components for Windows Vista, Windows 7, or Windows 8
http://support.apple.com/kb/HT1923
Apple Support: Issues installing iTunes or QuickTime for Windows
http://support.apple.com/kb/HT1926
Regards,
- Brenden -
HT201210 why it IPAD still black out and fail to switch on again after restore?
Help!! can I get a replacement since I bought this only end April!!! why is IPAD still black out and fail to switch on again after restore? I restore 3 times and still same black out happens,... this is so frustrating!!
tried that but it is now at Error1611, so will need to have them look into the hardware !!! thanks for advice !
-
Connections to Exchange CAS Array from UAG start failing shortly after start up
We are publishing Exchange 2010 services via UAG 2010.
After a short period where connectivity works as expected, clients start failing to connect and IIS fails on the UAG with the UAG Web Monitor failing to load and the system event logs showing WAS Event 5010 "A process serving application pool 'DefaultAppPool'
failed to respond to ping." with the process id corresponding to the w3wp.exe process
The IIS logs show HTTP error 503 - QueueFull and netstat shows no connections from the UAG to the CAS array servers. Increasing the IIS queue length has made no difference. According to our external firewall logs connections are still being received
but they're not getting past the UAG.
TMG firewall shows no dropped connections relating to the CAS addresses.
Any suggestions?Microsoft support resolved it for us.
There were a number of layered issues that because apparent as we solved each one.
Firstly our UAGs coudln't reach DCs for all domains in our forest. In our case we'd only got routes and local IP ranges set for our own domain as we didn't expect the UAG to need to talk to any other domains in the forest. Once we added the routes
from our DMZ and the relevant internal IP address ranges to the UAG config LSASS calmed right down.
You can test this with 'nltest /DSGETDC:FQDNofADDomain /FORCE'
We then also had to change the Base DN from DC=us,DC=parent,DC=root to DC=parent,DC=root in the UAG portal Authentication settings as the UAG accesses DC=Other,DC=parent,DC=root by ADSI if it has to change from DC=us rather than LDAP if it just works down the
tree. ADSI is apprently much worse for thread locking and performance.
The final piece of the puzzle for us was that we had a separate Exchange deployment in the other sub-domain which didn't have Outlook Anywhere turned on. Their clients were still trying to use it, hit out UAGs as they got the address from autodiscover
and when they got through our UAGs to the CAS servers the CASs tried to proxy this to the right CAS servers in their domain. Thier CAS servers dropped the connections as they didn't have it turned on, but the sessions stayed active on our UAGs and eventually
brought the whole thing crashing down.
The quick and dirty fix was to block the main addresses the clients were coming in via on the TMG firewall component. The administrators in the other sub-domain subsequently turned on Outlook Anywhere on their CAS servers and we stopped seeing the connections.
Maybe you are looking for
-
Error while uploading MT940 format
Hi Experts, While uploading MT940 format file through t.code ff_5 following error come: External transaction N155 + and N475- is not found. What these external transactions stand for and what should be the posting rule and interpretation alogrith fo
-
Unable to delete PO line item if GR qty is different from IV qty
Dear all, Please help me to check this issue. The PO line item purchased with 10pcs (quantity), and the goods receipt (GR) is 10pcs as well as the invoice verification for 10pcs. However, weeks later, they performed a movement type of 102 to cancel 2
-
How can i get my facetime to work?
Hello?
-
KE24 and KKBC_HOE balance does not match....
Hi, We are facing a big issues at the end of the perio 2 of 2009. Our KE24 and KKBC_HOE balance does not match. We have ccompared/hecked all our previous months balance and there it was matching accurately. But for period 2, there is a mismatch.
-
Hi there, I've just tried to run an air app on iOS 6 but all the vistual elements doesn't render properly, e.g. the tab view cannot render tab icons/tab bar, the action bar cannot render anything at all plus all other components... Please let me know