09/08/15-09:21:54 :: adadminsrvctl.sh version 120.10.12020000.

9
Validated the passed arguments for the option ebs-get-serverstatus
AdminServer is currently not running.

Validated the passed arguments for the option ebs-nmstart-adminsrv

Checking if the Admin Server is already up.
The Admin Server is not already up.
Checking if the Node Manager is already up..
Connecting to Node Manager ...
Successfully Connected to Node Manager.

The Node Manager is already up.

Starting server AdminServer ...

Successfully started server AdminServer ...

09/08/15-09:22:43 :: adadminsrvctl.sh: exiting with status 0

================================================================================

stty: standard input: Invalid argument

Enter the APPS user password:
stty: standard input: Invalid argument
stty: standard input: Invalid argument
Enter the WebLogic AdminServer password:
stty: standard input: Invalid argument
The log file is
/u02/applmgr/fs1/inst/apps/CLN1_picerpcln1/logs/appl/rgf/Tue_Sep_8_09_22_44_2015/ad
RegisterWLSListeners.log

Validated the passed arguments for the option ebs-get-serverstatus

AdminServer is in RUNNING mode.

Validated the passed arguments for the option ebs-get-serverstatus

AdminServer is in RUNNING mode.

09/08/15-10:03:06 :: adadminsrvctl.sh version 120.10.12020000.9

Validated the passed arguments for the option ebs-get-serverstatus
AdminServer is in RUNNING mode.

Validated the passed arguments for the option ebs-nmstop-adminsrv

Connecting to t3://picerpcln1.pic.com.kw:7002 with userid weblogic ...
Successfully connected to Admin Server 'AdminServer' that belongs to domain
'EBS_domain_CLN1'.

Warning: An insecure protocol was used to connect to the

server. To ensure on-the-wire security, the SSL port or
Admin port should be used instead.

Sep 08, 2015 10:03:15 AM ClientCommunicatorAdmin restart

WARNING: Failed to restart: java.rmi.NoSuchObjectException: The object identified
by: '284' could not be found. Either it was has not been exported or it has been
collected by the distributed garbage collector.
Sep 08, 2015 10:03:15 AM ClientCommunicatorAdmin restart
WARNING: Failed to restart: java.rmi.NoSuchObjectException: The object identified
by: '283' could not be found. Either it was has not been exported or it has been
collected by the distributed garbage collector.

Shutting down the server AdminServer with force=true while connected to AdminServer
...
WLST lost connection to the WebLogic Server that you were
connected to, this may happen if the server was shutdown or
partitioned. You will have to re-connect to the server once the
server is available.
Disconnected from weblogic server: AdminServer
Disconnected from weblogic server:

09/08/15-10:03:17 :: adadminsrvctl.sh: exiting with status 0

================================================================================

09/08/15-11:02:05 :: adadminsrvctl.sh version 120.10.12020000.9

Validated the passed arguments for the option ebs-get-serverstatus
AdminServer is currently not running.

Validated the passed arguments for the option ebs-nmstart-adminsrv

Checking if the Admin Server is already up.
The Admin Server is not already up.
Checking if the Node Manager is already up..
Connecting to Node Manager ...
Successfully Connected to Node Manager.

The Node Manager is already up.

Starting server AdminServer ...

Successfully started server AdminServer ...

09/08/15-11:03:17 :: adadminsrvctl.sh: exiting with status 0

================================================================================

stty: standard input: Invalid argument

Enter the APPS user password:
stty: standard input: Invalid argument
stty: standard input: Invalid argument
Enter the WebLogic AdminServer password:
stty: standard input: Invalid argument
The log file is
/u02/applmgr/fs1/inst/apps/CLN1_picerpcln1/logs/appl/rgf/Tue_Sep_8_11_03_18_2015/ad
RegisterWLSListeners.log

Validated the passed arguments for the option ebs-get-serverstatus

AdminServer is in RUNNING mode.

09/09/15-09:26:46 :: adadminsrvctl.sh version 120.10.12020000.9

Validated the passed arguments for the option ebs-get-serverstatus
AdminServer is in RUNNING mode.
09/09/15-09:26:50 :: adadminsrvctl.sh: exiting with status 2

================================================================================

Validated the passed arguments for the option ebs-get-serverstatus

AdminServer is in RUNNING mode.

Validated the passed arguments for the option ebs-get-serverstatus

AdminServer is in RUNNING mode.

09/09/15-10:40:11 :: adadminsrvctl.sh version 120.10.12020000.9

Validated the passed arguments for the option ebs-get-serverstatus
AdminServer is in RUNNING mode.

Validated the passed arguments for the option ebs-nmstop-adminsrv

Connecting to t3://picerpcln1.pic.com.kw:7002 with userid weblogic ...
Successfully connected to Admin Server 'AdminServer' that belongs to domain
'EBS_domain_CLN1'.

Warning: An insecure protocol was used to connect to the

server. To ensure on-the-wire security, the SSL port or
Admin port should be used instead.

Sep 09, 2015 10:40:19 AM ClientCommunicatorAdmin restart

WARNING: Failed to restart: java.rmi.NoSuchObjectException: The object identified
by: '283' could not be found. Either it was has not been exported or it has been
collected by the distributed garbage collector.
Sep 09, 2015 10:40:19 AM ClientCommunicatorAdmin restart
WARNING: Failed to restart: java.rmi.NoSuchObjectException: The object identified
by: '284' could not be found. Either it was has not been exported or it has been
collected by the distributed garbage collector.

Shutting down the server AdminServer with force=true while connected to AdminServer
...
Disconnected from weblogic server: AdminServer

09/09/15-10:40:20 :: adadminsrvctl.sh: exiting with status 0

================================================================================

09/09/15-11:39:30 :: adadminsrvctl.sh version 120.10.12020000.9

Validated the passed arguments for the option ebs-get-serverstatus
AdminServer is in RUNNING mode.

Validated the passed arguments for the option ebs-nmstop-adminsrv

Connecting to t3://picerpcln1.pic.com.kw:7002 with userid weblogic ...
Successfully connected to Admin Server 'AdminServer' that belongs to domain
'EBS_domain_CLN1'.

Warning: An insecure protocol was used to connect to the

server. To ensure on-the-wire security, the SSL port or
Admin port should be used instead.
Shutting down the server AdminServer with force=true while connected to AdminServer
...
WLST lost connection to the WebLogic Server that you were
connected to, this may happen if the server was shutdown or
partitioned. You will have to re-connect to the server once the
server is available.
Disconnected from weblogic server: AdminServer
Disconnected from weblogic server:

09/09/15-11:39:42 :: adadminsrvctl.sh: exiting with status 0

================================================================================

09/09/15-12:17:56 :: adadminsrvctl.sh version 120.10.12020000.9

Validated the passed arguments for the option ebs-get-serverstatus
AdminServer is currently not running.

09/09/15-12:18:00 :: adadminsrvctl.sh: exiting with status 2

================================================================================

09/09/15-14:02:15 :: adadminsrvctl.sh version 120.10.12020000.9

Validated the passed arguments for the option ebs-get-serverstatus
AdminServer is in RUNNING mode.

Validated the passed arguments for the option ebs-nmstop-adminsrv

Connecting to t3://picerpcln1.pic.com.kw:7002 with userid weblogic ...
Successfully connected to Admin Server 'AdminServer' that belongs to domain
'EBS_domain_CLN1'.

Warning: An insecure protocol was used to connect to the

server. To ensure on-the-wire security, the SSL port or
Admin port should be used instead.

Shutting down the server AdminServer with force=true while connected to AdminServer
...
Disconnected from weblogic server: AdminServer

09/09/15-14:02:28 :: adadminsrvctl.sh: exiting with status 0

================================================================================

09/21/15-10:35:25 :: adadminsrvctl.sh version 120.10.12020000.9

Validated the passed arguments for the option ebs-get-serverstatus
AdminServer is in RUNNING mode.

Validated the passed arguments for the option ebs-nmstop-adminsrv

Connecting to t3://picerpcln1.pic.com.kw:7002 with userid weblogic ...
Successfully connected to Admin Server 'AdminServer' that belongs to domain
'EBS_domain_CLN1'.

Warning: An insecure protocol was used to connect to the

server. To ensure on-the-wire security, the SSL port or
Admin port should be used instead.

Shutting down the server AdminServer with force=true while connected to AdminServer
...
WLST lost connection to the WebLogic Server that you were
connected to, this may happen if the server was shutdown or
partitioned. You will have to re-connect to the server once the
server is available.
Disconnected from weblogic server: AdminServer
Disconnected from weblogic server:

09/21/15-10:35:39 :: adadminsrvctl.sh: exiting with status 0

================================================================================

09/22/15-09:23:07 :: adadminsrvctl.sh version 120.10.12020000.9

Validated the passed arguments for the option ebs-get-serverstatus
AdminServer is in RUNNING mode.

Validated the passed arguments for the option ebs-nmstop-adminsrv

Connecting to t3://picerpcln1.pic.com.kw:7002 with userid weblogic ...
Successfully connected to Admin Server 'AdminServer' that belongs to domain
'EBS_domain_CLN1'.

Warning: An insecure protocol was used to connect to the

server. To ensure on-the-wire security, the SSL port or
Admin port should be used instead.

Shutting down the server AdminServer with force=true while connected to AdminServer
...
WLST lost connection to the WebLogic Server that you were
connected to, this may happen if the server was shutdown or
partitioned. You will have to re-connect to the server once the
server is available.
Disconnected from weblogic server: AdminServer
Disconnected from weblogic server:

09/22/15-09:23:21 :: adadminsrvctl.sh: exiting with status 0

================================================================================

09/22/15-09:39:31 :: adadminsrvctl.sh version 120.10.12020000.9

Validated the passed arguments for the option ebs-get-serverstatus
AdminServer is in RUNNING mode.
Validated the passed arguments for the option ebs-nmstop-adminsrv
Connecting to t3://picerpcln1.pic.com.kw:7002 with userid weblogic ...
Successfully connected to Admin Server 'AdminServer' that belongs to domain
'EBS_domain_CLN1'.

Warning: An insecure protocol was used to connect to the

server. To ensure on-the-wire security, the SSL port or
Admin port should be used instead.

Shutting down the server AdminServer with force=true while connected to AdminServer
...
WLST lost connection to the WebLogic Server that you were
connected to, this may happen if the server was shutdown or
partitioned. You will have to re-connect to the server once the
server is available.
Disconnected from weblogic server: AdminServer
Disconnected from weblogic server:

09/22/15-09:39:45 :: adadminsrvctl.sh: exiting with status 0

================================================================================

09/22/15-10:53:23 :: adadminsrvctl.sh version 120.10.12020000.9

Validated the passed arguments for the option ebs-get-serverstatus
AdminServer is in RUNNING mode.

Validated the passed arguments for the option ebs-nmstop-adminsrv

Connecting to t3://picerpcln1.pic.com.kw:7002 with userid weblogic ...
Successfully connected to Admin Server 'AdminServer' that belongs to domain
'EBS_domain_CLN1'.

Warning: An insecure protocol was used to connect to the

server. To ensure on-the-wire security, the SSL port or
Admin port should be used instead.

Shutting down the server AdminServer with force=true while connected to AdminServer
...
WLST lost connection to the WebLogic Server that you were
connected to, this may happen if the server was shutdown or
partitioned. You will have to re-connect to the server once the
server is available.
Disconnected from weblogic server: AdminServer
Disconnected from weblogic server:

09/22/15-10:53:36 :: adadminsrvctl.sh: exiting with status 0

================================================================================
09/22/15-11:53:33 :: adadminsrvctl.sh version 120.10.12020000.9
Validated the passed arguments for the option ebs-get-serverstatus
AdminServer is in RUNNING mode.

Validated the passed arguments for the option ebs-nmstop-adminsrv

Connecting to t3://picerpcln1.pic.com.kw:7002 with userid weblogic ...
Successfully connected to Admin Server 'AdminServer' that belongs to domain
'EBS_domain_CLN1'.

Warning: An insecure protocol was used to connect to the

server. To ensure on-the-wire security, the SSL port or
Admin port should be used instead.

Shutting down the server AdminServer with force=true while connected to AdminServer
...
WLST lost connection to the WebLogic Server that you were
connected to, this may happen if the server was shutdown or
partitioned. You will have to re-connect to the server once the
server is available.
Disconnected from weblogic server: AdminServer
Disconnected from weblogic server:

09/22/15-11:53:47 :: adadminsrvctl.sh: exiting with status 0

================================================================================

09/28/15-10:14:42 :: adadminsrvctl.sh version 120.10.12020000.9

Validated the passed arguments for the option ebs-get-serverstatus
AdminServer is in RUNNING mode.

Validated the passed arguments for the option ebs-nmstop-adminsrv

Connecting to t3://picerpcln1.pic.com.kw:7002 with userid weblogic ...
Successfully connected to Admin Server 'AdminServer' that belongs to domain
'EBS_domain_CLN1'.

Warning: An insecure protocol was used to connect to the

server. To ensure on-the-wire security, the SSL port or
Admin port should be used instead.

Shutting down the server AdminServer with force=true while connected to AdminServer
...
WLST lost connection to the WebLogic Server that you were
connected to, this may happen if the server was shutdown or
partitioned. You will have to re-connect to the server once the
server is available.
Disconnected from weblogic server: AdminServer
Disconnected from weblogic server:

09/28/15-10:14:55 :: adadminsrvctl.sh: exiting with status 0

================================================================================

09/28/15-10:56:41 :: adadminsrvctl.sh version 120.10.12020000.9

Validated the passed arguments for the option ebs-get-serverstatus
AdminServer is in RUNNING mode.

Validated the passed arguments for the option ebs-nmstop-adminsrv

Connecting to t3://picerpcln1.pic.com.kw:7002 with userid weblogic ...
Successfully connected to Admin Server 'AdminServer' that belongs to domain
'EBS_domain_CLN1'.

Warning: An insecure protocol was used to connect to the

server. To ensure on-the-wire security, the SSL port or
Admin port should be used instead.

Shutting down the server AdminServer with force=true while connected to AdminServer
...
Disconnected from weblogic server: AdminServer

09/28/15-10:56:52 :: adadminsrvctl.sh: exiting with status 0

================================================================================

09/29/15-08:30:44 :: adadminsrvctl.sh version 120.10.12020000.9

Validated the passed arguments for the option ebs-get-serverstatus
AdminServer is in RUNNING mode.

Validated the passed arguments for the option ebs-nmstop-adminsrv

Connecting to t3://picerpcln1.pic.com.kw:7002 with userid weblogic ...
Successfully connected to Admin Server 'AdminServer' that belongs to domain
'EBS_domain_CLN1'.

Warning: An insecure protocol was used to connect to the

server. To ensure on-the-wire security, the SSL port or
Admin port should be used instead.

Shutting down the server AdminServer with force=true while connected to AdminServer
...
Disconnected from weblogic server: AdminServer

09/29/15-08:30:56 :: adadminsrvctl.sh: exiting with status 0

================================================================================

09/29/15-10:14:41 :: adadminsrvctl.sh version 120.10.12020000.9

Validated the passed arguments for the option ebs-get-serverstatus
AdminServer is in RUNNING mode.
Validated the passed arguments for the option ebs-nmstop-adminsrv
Connecting to t3://picerpcln1.pic.com.kw:7002 with userid weblogic ...
Successfully connected to Admin Server 'AdminServer' that belongs to domain
'EBS_domain_CLN1'.

Warning: An insecure protocol was used to connect to the

server. To ensure on-the-wire security, the SSL port or
Admin port should be used instead.

Shutting down the server AdminServer with force=true while connected to AdminServer
...
WLST lost connection to the WebLogic Server that you were
connected to, this may happen if the server was shutdown or
partitioned. You will have to re-connect to the server once the
server is available.
Disconnected from weblogic server: AdminServer
Disconnected from weblogic server:

09/29/15-10:14:57 :: adadminsrvctl.sh: exiting with status 0

================================================================================

09/29/15-10:26:41 :: adadminsrvctl.sh version 120.10.12020000.9

Validated the passed arguments for the option ebs-get-serverstatus
AdminServer is currently not running.

Validated the passed arguments for the option ebs-nmstart-adminsrv

Checking if the Admin Server is already up.
The Admin Server is not already up.
Checking if the Node Manager is already up..
Traceback (innermost last):
File "<string>", line 1, in ?
File "<iostream>", line 123, in nmConnect
File "<iostream>", line 648, in raiseWLSTException
WLSTException: Error occured while performing nmConnect : Cannot connect to Node
Manager. : Connection refused. Could not connect to NodeManager. Check that it is
running at picerpcln1.pic.com.kw:5557.
Use dumpStack() to view the full stacktrace

Connecting to Node Manager ...

Launching NodeManager ...

Properties: {Arguments=-
Djava.security.egd=file:/dev/./urandom,JavaHome=/u02/applmgr/fs1/EBSapps/comn/util/
jdk64,ListenAddress=picerpcln1.pic.com.kw,ListenPort=5557,LogAppend=false,NodeManag
erHome=/u02/applmgr/fs1/FMW_Home/wlserver_10.3/common/nodemanager/nmHome1,SecureLis
tener=false,StartScriptEnabled=false,StartScriptName=startWebLogic.sh,}
Command: /u02/applmgr/fs1/EBSapps/comn/util/jdk64/jre/bin/java -classpath
/u02/applmgr/fs1/EBSapps/comn/util/jdk64/jre/lib/rt.jar:/u02/applmgr/fs1/EBSapps/co
mn/util/jdk64/jre/lib/i18n.jar:/u02/applmgr/fs1/FMW_Home/patch_wls1036/profiles/def
ault/sys_manifest_classpath/weblogic_patch.jar:/u02/applmgr/fs1/EBSapps/comn/util/j
dk64/lib/tools.jar:/u02/applmgr/fs1/FMW_Home/wlserver_10.3/server/lib/weblogic_sp.j
ar:/u02/applmgr/fs1/FMW_Home/wlserver_10.3/server/lib/weblogic.jar:/u02/applmgr/fs1
/FMW_Home/modules/features/weblogic.server.modules_10.3.6.0.jar:/u02/applmgr/fs1/FM
W_Home/wlserver_10.3/server/lib/webservices.jar:/u02/applmgr/fs1/FMW_Home/modules/o
rg.apache.ant_1.7.1/lib/ant-
all.jar:/u02/applmgr/fs1/FMW_Home/modules/net.sf.antcontrib_1.1.0.0_1-0b2/lib/ant-
contrib.jar:/u02/applmgr/fs1/FMW_Home/oracle_common/modules/oracle.jdbc_11.1.1/ojdb
c6dms.jar:/u02/applmgr/fs1/FMW_Home/oracle_common/webcenter/modules/oracle.portlet.
server_11.1.1/oracle-portlet-
api.jar:/u02/applmgr/fs1/FMW_Home/oracle_common/modules/oracle.jrf_11.1.1/jrf.jar:/
u02/applmgr/fs1/FMW_Home/wlserver_10.3/common/derby/lib/derbyclient.jar:/u02/applmg
r/fs1/FMW_Home/Oracle_EBS-app1/shared-libs/ebs-appsborg/WEB-
INF/lib/ebsAppsborgManifest.jar:/u02/applmgr/fs1/EBSapps/comn/java/classes/oracle/a
pps/fnd/jar/adall.jar weblogic.NodeManager -v
Successfully launched the Node Manager.
The Node Manager process is running independent of the WLST process.
Exiting WLST will not stop the Node Manager process. Please refer
to the Node Manager logs for more information.
The Node Manager logs will be under
/u02/applmgr/fs1/FMW_Home/wlserver_10.3/common/nodemanager/nmHome1
Node Manager starting in the background

NodeManager is not fully up....Waiting for 10 sec....

NodeManager is not fully up....Waiting for 10 sec....

NodeManager is started now

Connecting to Node Manager ...
Successfully Connected to Node Manager.

Connected to the Node Manager.

Starting server AdminServer ...

Successfully started server AdminServer ...

09/29/15-10:28:27 :: adadminsrvctl.sh: exiting with status 0

================================================================================

stty: standard input: Invalid argument

Enter the APPS user password:
stty: standard input: Invalid argument
stty: standard input: Invalid argument
Enter the WebLogic AdminServer password:
stty: standard input: Invalid argument
The log file is
/u02/applmgr/fs1/inst/apps/CLN1_picerpcln1/logs/appl/rgf/Tue_Sep_29_10_28_27_2015/a
dRegisterWLSListeners.log

09/29/15-10:33:03 :: adadminsrvctl.sh version 120.10.12020000.9

Validated the passed arguments for the option ebs-get-serverstatus
AdminServer is in RUNNING mode.

Validated the passed arguments for the option ebs-nmstop-adminsrv

Connecting to t3://picerpcln1.pic.com.kw:7002 with userid weblogic ...
Successfully connected to Admin Server 'AdminServer' that belongs to domain
'EBS_domain_CLN1'.

Warning: An insecure protocol was used to connect to the

server. To ensure on-the-wire security, the SSL port or
Admin port should be used instead.

Sep 29, 2015 10:33:15 AM ClientCommunicatorAdmin restart

WARNING: Failed to restart: java.rmi.NoSuchObjectException: The object identified
by: '284' could not be found. Either it was has not been exported or it has been
collected by the distributed garbage collector.
Sep 29, 2015 10:33:15 AM ClientCommunicatorAdmin restart
WARNING: Failed to restart: java.rmi.NoSuchObjectException: The object identified
by: '283' could not be found. Either it was has not been exported or it has been
collected by the distributed garbage collector.

Shutting down the server AdminServer with force=true while connected to AdminServer
...
Disconnected from weblogic server: AdminServer

09/29/15-10:33:16 :: adadminsrvctl.sh: exiting with status 0

================================================================================

09/29/15-11:41:24 :: adadminsrvctl.sh version 120.10.12020000.9

Validated the passed arguments for the option ebs-get-serverstatus
AdminServer is in RUNNING mode.

Validated the passed arguments for the option ebs-nmstop-adminsrv

Connecting to t3://picerpcln1.pic.com.kw:7002 with userid weblogic ...
Successfully connected to Admin Server 'AdminServer' that belongs to domain
'EBS_domain_CLN1'.

Warning: An insecure protocol was used to connect to the

server. To ensure on-the-wire security, the SSL port or
Admin port should be used instead.

Shutting down the server AdminServer with force=true while connected to AdminServer
...
WLST lost connection to the WebLogic Server that you were
connected to, this may happen if the server was shutdown or
partitioned. You will have to re-connect to the server once the
server is available.
Disconnected from weblogic server: AdminServer
Disconnected from weblogic server:

09/29/15-11:41:37 :: adadminsrvctl.sh: exiting with status 0

================================================================================

10/07/15-11:34:54 :: adadminsrvctl.sh version 120.10.12020000.9

Validated the passed arguments for the option ebs-get-serverstatus
AdminServer is currently not running.
10/07/15-11:35:01 :: adadminsrvctl.sh: exiting with status 2

================================================================================

10/18/15-16:32:44 :: adadminsrvctl.sh version 120.10.12020000.9

Validated the passed arguments for the option ebs-get-serverstatus
AdminServer is in RUNNING mode.

Validated the passed arguments for the option ebs-nmstop-adminsrv

Connecting to t3://picerpcln1.pic.com.kw:7002 with userid weblogic ...
Successfully connected to Admin Server 'AdminServer' that belongs to domain
'EBS_domain_CLN1'.

Warning: An insecure protocol was used to connect to the

server. To ensure on-the-wire security, the SSL port or
Admin port should be used instead.

Shutting down the server AdminServer with force=true while connected to AdminServer
...
Disconnected from weblogic server: AdminServer

10/18/15-16:33:01 :: adadminsrvctl.sh: exiting with status 0

================================================================================

10/27/15-10:54:43 :: adadminsrvctl.sh version 120.10.12020000.9

Validated the passed arguments for the option ebs-get-serverstatus
AdminServer is in RUNNING mode.

Validated the passed arguments for the option ebs-nmstop-adminsrv

Connecting to t3://picerpcln1.pic.com.kw:7002 with userid weblogic ...
Successfully connected to Admin Server 'AdminServer' that belongs to domain
'EBS_domain_CLN1'.

Warning: An insecure protocol was used to connect to the

server. To ensure on-the-wire security, the SSL port or
Admin port should be used instead.

Shutting down the server AdminServer with force=true while connected to AdminServer
...
WLST lost connection to the WebLogic Server that you were
connected to, this may happen if the server was shutdown or
partitioned. You will have to re-connect to the server once the
server is available.
Disconnected from weblogic server: AdminServer
Disconnected from weblogic server:

10/27/15-10:55:01 :: adadminsrvctl.sh: exiting with status 0

================================================================================

10/29/15-08:28:21 :: adadminsrvctl.sh version 120.10.12020000.9

Validated the passed arguments for the option ebs-get-serverstatus
AdminServer is currently not running.

10/29/15-08:28:35 :: adadminsrvctl.sh: exiting with status 2

================================================================================

10/29/15-09:06:16 :: adadminsrvctl.sh version 120.10.12020000.9

Validated the passed arguments for the option ebs-get-serverstatus
AdminServer is currently not running.

10/29/15-09:06:21 :: adadminsrvctl.sh: exiting with status 2

================================================================================

10/29/15-09:10:42 :: adadminsrvctl.sh version 120.10.12020000.9

Validated the passed arguments for the option ebs-get-serverstatus
AdminServer is currently not running.

Validated the passed arguments for the option ebs-nmstart-adminsrv

Checking if the Admin Server is already up.
The Admin Server is not already up.
Checking if the Node Manager is already up..
Traceback (innermost last):
File "<string>", line 1, in ?
File "<iostream>", line 123, in nmConnect
File "<iostream>", line 648, in raiseWLSTException
WLSTException: Error occured while performing nmConnect : Cannot connect to Node
Manager. : Connection refused. Could not connect to NodeManager. Check that it is
running at picerpcln1.pic.com.kw:5557.
Use dumpStack() to view the full stacktrace

Connecting to Node Manager ...

Launching NodeManager ...

Properties: {Arguments=-
Djava.security.egd=file:/dev/./urandom,JavaHome=/u02/applmgr/fs1/EBSapps/comn/util/
jdk64,ListenAddress=picerpcln1.pic.com.kw,ListenPort=5557,LogAppend=false,NodeManag
erHome=/u02/applmgr/fs1/FMW_Home/wlserver_10.3/common/nodemanager/nmHome1,SecureLis
tener=false,StartScriptEnabled=false,StartScriptName=startWebLogic.sh,}
Command: /u02/applmgr/fs1/EBSapps/comn/util/jdk64/jre/bin/java -classpath
/u02/applmgr/fs1/EBSapps/comn/util/jdk64/jre/lib/rt.jar:/u02/applmgr/fs1/EBSapps/co
mn/util/jdk64/jre/lib/i18n.jar:/u02/applmgr/fs1/FMW_Home/patch_wls1036/profiles/def
ault/sys_manifest_classpath/weblogic_patch.jar:/u02/applmgr/fs1/EBSapps/comn/util/j
dk64/lib/tools.jar:/u02/applmgr/fs1/FMW_Home/wlserver_10.3/server/lib/weblogic_sp.j
ar:/u02/applmgr/fs1/FMW_Home/wlserver_10.3/server/lib/weblogic.jar:/u02/applmgr/fs1
/FMW_Home/modules/features/weblogic.server.modules_10.3.6.0.jar:/u02/applmgr/fs1/FM
W_Home/wlserver_10.3/server/lib/webservices.jar:/u02/applmgr/fs1/FMW_Home/modules/o
rg.apache.ant_1.7.1/lib/ant-
all.jar:/u02/applmgr/fs1/FMW_Home/modules/net.sf.antcontrib_1.1.0.0_1-0b2/lib/ant-
contrib.jar:/u02/applmgr/fs1/FMW_Home/oracle_common/modules/oracle.jdbc_11.1.1/ojdb
c6dms.jar:/u02/applmgr/fs1/FMW_Home/oracle_common/webcenter/modules/oracle.portlet.
server_11.1.1/oracle-portlet-
api.jar:/u02/applmgr/fs1/FMW_Home/oracle_common/modules/oracle.jrf_11.1.1/jrf.jar:/
u02/applmgr/fs1/FMW_Home/wlserver_10.3/common/derby/lib/derbyclient.jar:/u02/applmg
r/fs1/FMW_Home/Oracle_EBS-app1/shared-libs/ebs-appsborg/WEB-
INF/lib/ebsAppsborgManifest.jar:/u02/applmgr/fs1/EBSapps/comn/java/classes/oracle/a
pps/fnd/jar/adall.jar weblogic.NodeManager -v
Successfully launched the Node Manager.
The Node Manager process is running independent of the WLST process.
Exiting WLST will not stop the Node Manager process. Please refer
to the Node Manager logs for more information.
The Node Manager logs will be under
/u02/applmgr/fs1/FMW_Home/wlserver_10.3/common/nodemanager/nmHome1
Node Manager starting in the background

NodeManager is not fully up....Waiting for 10 sec....

NodeManager is started now

Connecting to Node Manager ...
Successfully Connected to Node Manager.

Connected to the Node Manager.

Starting server AdminServer ...

Successfully started server AdminServer ...

10/29/15-09:12:44 :: adadminsrvctl.sh: exiting with status 0

================================================================================

stty: standard input: Invalid argument

Enter the APPS user password:
stty: standard input: Invalid argument
stty: standard input: Invalid argument
Enter the WebLogic AdminServer password:
stty: standard input: Invalid argument
The log file is
/u02/applmgr/fs1/inst/apps/CLN1_picerpcln1/logs/appl/rgf/Thu_Oct_29_09_12_44_2015/a
dRegisterWLSListeners.log

10/29/15-09:13:10 :: adadminsrvctl.sh version 120.10.12020000.9

Validated the passed arguments for the option ebs-get-serverstatus
AdminServer is in RUNNING mode.

10/29/15-09:13:15 :: adadminsrvctl.sh: exiting with status 2

================================================================================

Validated the passed arguments for the option ebs-get-serverstatus

AdminServer is in RUNNING mode.

Validated the passed arguments for the option ebs-get-serverstatus

AdminServer is in RUNNING mode.

10/29/15-11:06:39 :: adadminsrvctl.sh version 120.10.12020000.9

Validated the passed arguments for the option ebs-get-serverstatus
AdminServer is in RUNNING mode.
Validated the passed arguments for the option ebs-nmstop-adminsrv
Connecting to t3://picerpcln1.pic.com.kw:7002 with userid weblogic ...
Successfully connected to Admin Server 'AdminServer' that belongs to domain
'EBS_domain_CLN1'.

Warning: An insecure protocol was used to connect to the

server. To ensure on-the-wire security, the SSL port or
Admin port should be used instead.

Oct 29, 2015 11:06:49 AM ClientCommunicatorAdmin restart

WARNING: Failed to restart: java.rmi.NoSuchObjectException: The object identified
by: '283' could not be found. Either it was has not been exported or it has been
collected by the distributed garbage collector.
Oct 29, 2015 11:06:49 AM ClientCommunicatorAdmin restart
WARNING: Failed to restart: java.rmi.NoSuchObjectException: The object identified
by: '284' could not be found. Either it was has not been exported or it has been
collected by the distributed garbage collector.

Shutting down the server AdminServer with force=true while connected to AdminServer
...
Disconnected from weblogic server: AdminServer

10/29/15-11:06:50 :: adadminsrvctl.sh: exiting with status 0

================================================================================

10/29/15-12:44:58 :: adadminsrvctl.sh version 120.10.12020000.9

Validated the passed arguments for the option ebs-get-serverstatus
AdminServer is in RUNNING mode.

Validated the passed arguments for the option ebs-nmstop-adminsrv

Connecting to t3://picerpcln1.pic.com.kw:7002 with userid weblogic ...
Successfully connected to Admin Server 'AdminServer' that belongs to domain
'EBS_domain_CLN1'.

Warning: An insecure protocol was used to connect to the

server. To ensure on-the-wire security, the SSL port or
Admin port should be used instead.

Shutting down the server AdminServer with force=true while connected to AdminServer
...
Disconnected from weblogic server: AdminServer

10/29/15-12:45:12 :: adadminsrvctl.sh: exiting with status 0

================================================================================

11/12/15-11:17:56 :: adadminsrvctl.sh version 120.10.12020000.9

Validated the passed arguments for the option ebs-get-serverstatus
AdminServer is in RUNNING mode.

Validated the passed arguments for the option ebs-nmstop-adminsrv

Connecting to t3://picerpcln1.pic.com.kw:7002 with userid weblogic ...
Successfully connected to Admin Server 'AdminServer' that belongs to domain
'EBS_domain_CLN1'.

Warning: An insecure protocol was used to connect to the

server. To ensure on-the-wire security, the SSL port or
Admin port should be used instead.

Shutting down the server AdminServer with force=true while connected to AdminServer
...
Disconnected from weblogic server: AdminServer

11/12/15-11:18:09 :: adadminsrvctl.sh: exiting with status 0

================================================================================

11/12/15-11:36:30 :: adadminsrvctl.sh version 120.10.12020000.9

Validated the passed arguments for the option ebs-get-serverstatus
AdminServer is currently not running.

11/12/15-11:36:33 :: adadminsrvctl.sh: exiting with status 2

================================================================================

11/12/15-11:38:38 :: adadminsrvctl.sh version 120.10.12020000.9

Validated the passed arguments for the option ebs-get-serverstatus
AdminServer is currently not running.

Validated the passed arguments for the option ebs-nmstart-adminsrv

Checking if the Admin Server is already up.
The Admin Server is not already up.
Checking if the Node Manager is already up..
Traceback (innermost last):
File "<string>", line 1, in ?
File "<iostream>", line 123, in nmConnect
File "<iostream>", line 648, in raiseWLSTException
WLSTException: Error occured while performing nmConnect : Cannot connect to Node
Manager. : Connection refused. Could not connect to NodeManager. Check that it is
running at picerpcln1.pic.com.kw:5557.
Use dumpStack() to view the full stacktrace

Connecting to Node Manager ...

Launching NodeManager ...

Properties: {Arguments=-
Djava.security.egd=file:/dev/./urandom,JavaHome=/u02/applmgr/fs1/EBSapps/comn/util/
jdk64,ListenAddress=picerpcln1.pic.com.kw,ListenPort=5557,LogAppend=false,NodeManag
erHome=/u02/applmgr/fs1/FMW_Home/wlserver_10.3/common/nodemanager/nmHome1,SecureLis
tener=false,StartScriptEnabled=false,StartScriptName=startWebLogic.sh,}
Command: /u02/applmgr/fs1/EBSapps/comn/util/jdk64/jre/bin/java -classpath
/u02/applmgr/fs1/EBSapps/comn/util/jdk64/jre/lib/rt.jar:/u02/applmgr/fs1/EBSapps/co
mn/util/jdk64/jre/lib/i18n.jar:/u02/applmgr/fs1/FMW_Home/patch_wls1036/profiles/def
ault/sys_manifest_classpath/weblogic_patch.jar:/u02/applmgr/fs1/EBSapps/comn/util/j
dk64/lib/tools.jar:/u02/applmgr/fs1/FMW_Home/wlserver_10.3/server/lib/weblogic_sp.j
ar:/u02/applmgr/fs1/FMW_Home/wlserver_10.3/server/lib/weblogic.jar:/u02/applmgr/fs1
/FMW_Home/modules/features/weblogic.server.modules_10.3.6.0.jar:/u02/applmgr/fs1/FM
W_Home/wlserver_10.3/server/lib/webservices.jar:/u02/applmgr/fs1/FMW_Home/modules/o
rg.apache.ant_1.7.1/lib/ant-
all.jar:/u02/applmgr/fs1/FMW_Home/modules/net.sf.antcontrib_1.1.0.0_1-0b2/lib/ant-
contrib.jar:/u02/applmgr/fs1/FMW_Home/oracle_common/modules/oracle.jdbc_11.1.1/ojdb
c6dms.jar:/u02/applmgr/fs1/FMW_Home/oracle_common/webcenter/modules/oracle.portlet.
server_11.1.1/oracle-portlet-
api.jar:/u02/applmgr/fs1/FMW_Home/oracle_common/modules/oracle.jrf_11.1.1/jrf.jar:/
u02/applmgr/fs1/FMW_Home/wlserver_10.3/common/derby/lib/derbyclient.jar:/u02/applmg
r/fs1/FMW_Home/Oracle_EBS-app1/shared-libs/ebs-appsborg/WEB-
INF/lib/ebsAppsborgManifest.jar:/u02/applmgr/fs1/EBSapps/comn/java/classes/oracle/a
pps/fnd/jar/adall.jar weblogic.NodeManager -v
Successfully launched the Node Manager.
The Node Manager process is running independent of the WLST process.
Exiting WLST will not stop the Node Manager process. Please refer
to the Node Manager logs for more information.
The Node Manager logs will be under
/u02/applmgr/fs1/FMW_Home/wlserver_10.3/common/nodemanager/nmHome1
Node Manager starting in the background

NodeManager is not fully up....Waiting for 10 sec....

NodeManager is started now

Traceback (innermost last):
File "<string>", line 1, in ?
File "<iostream>", line 123, in nmConnect
File "<iostream>", line 648, in raiseWLSTException
WLSTException: Error occured while performing nmConnect : Cannot connect to Node
Manager. : Access to domain 'EBS_domain_CLN1' for user 'weblogic' denied
Use dumpStack() to view the full stacktrace

Connecting to Node Manager ...

ERROR: Invalid credentials passed.

ERROR: Unable to connect to the Node Manager. The Admin Server cannot be started
up.
Successfully disconnected from Node Manager.

11/12/15-11:39:17 :: adadminsrvctl.sh: exiting with status 1

================================================================================

01/07/16-15:22:05 :: adadminsrvctl.sh version 120.10.12020000.9

Validated the passed arguments for the option ebs-get-serverstatus
AdminServer is in RUNNING mode.

Validated the passed arguments for the option ebs-nmstop-adminsrv

Connecting to t3://picerpcln1.pic.com.kw:7002 with userid weblogic ...
Successfully connected to Admin Server 'AdminServer' that belongs to domain
'EBS_domain_CLN1'.

Warning: An insecure protocol was used to connect to the

server. To ensure on-the-wire security, the SSL port or
Admin port should be used instead.

Shutting down the server AdminServer with force=true while connected to AdminServer
...
Disconnected from weblogic server: AdminServer

01/07/16-15:22:20 :: adadminsrvctl.sh: exiting with status 0

================================================================================

01/07/16-15:57:38 :: adadminsrvctl.sh version 120.10.12020000.9

Validated the passed arguments for the option ebs-get-serverstatus
AdminServer is in RUNNING mode.

Validated the passed arguments for the option ebs-nmstop-adminsrv

Connecting to t3://picerpcln1.pic.com.kw:7002 with userid weblogic ...
Successfully connected to Admin Server 'AdminServer' that belongs to domain
'EBS_domain_CLN1'.

Warning: An insecure protocol was used to connect to the

server. To ensure on-the-wire security, the SSL port or
Admin port should be used instead.

Shutting down the server AdminServer with force=true while connected to AdminServer
...
Disconnected from weblogic server: AdminServer

01/07/16-15:57:52 :: adadminsrvctl.sh: exiting with status 0

================================================================================

01/07/16-20:07:21 :: adadminsrvctl.sh version 120.10.12020000.9

Validated the passed arguments for the option ebs-get-serverstatus
AdminServer is currently not running.

01/07/16-20:07:27 :: adadminsrvctl.sh: exiting with status 2

================================================================================

01/07/16-20:17:03 :: adadminsrvctl.sh version 120.10.12020000.9

Validated the passed arguments for the option ebs-get-serverstatus
AdminServer is currently not running.

Validated the passed arguments for the option ebs-nmstart-adminsrv

Checking if the Admin Server is already up.
The Admin Server is not already up.
Checking if the Node Manager is already up..
Traceback (innermost last):
File "<string>", line 1, in ?
File "<iostream>", line 123, in nmConnect
File "<iostream>", line 648, in raiseWLSTException
WLSTException: Error occured while performing nmConnect : Cannot connect to Node
Manager. : Connection refused. Could not connect to NodeManager. Check that it is
running at picerpcln1.pic.com.kw:5557.
Use dumpStack() to view the full stacktrace

Connecting to Node Manager ...

Launching NodeManager ...

Properties: {Arguments=-
Djava.security.egd=file:/dev/./urandom,JavaHome=/u02/applmgr/fs1/EBSapps/comn/util/
jdk64,ListenAddress=picerpcln1.pic.com.kw,ListenPort=5557,LogAppend=false,NodeManag
erHome=/u02/applmgr/fs1/FMW_Home/wlserver_10.3/common/nodemanager/nmHome1,SecureLis
tener=false,StartScriptEnabled=false,StartScriptName=startWebLogic.sh,}
Command: /u02/applmgr/fs1/EBSapps/comn/util/jdk64/jre/bin/java -classpath
/u02/applmgr/fs1/EBSapps/comn/util/jdk64/jre/lib/rt.jar:/u02/applmgr/fs1/EBSapps/co
mn/util/jdk64/jre/lib/i18n.jar:/u02/applmgr/fs1/FMW_Home/patch_wls1036/profiles/def
ault/sys_manifest_classpath/weblogic_patch.jar:/u02/applmgr/fs1/EBSapps/comn/util/j
dk64/lib/tools.jar:/u02/applmgr/fs1/FMW_Home/wlserver_10.3/server/lib/weblogic_sp.j
ar:/u02/applmgr/fs1/FMW_Home/wlserver_10.3/server/lib/weblogic.jar:/u02/applmgr/fs1
/FMW_Home/modules/features/weblogic.server.modules_10.3.6.0.jar:/u02/applmgr/fs1/FM
W_Home/wlserver_10.3/server/lib/webservices.jar:/u02/applmgr/fs1/FMW_Home/modules/o
rg.apache.ant_1.7.1/lib/ant-
all.jar:/u02/applmgr/fs1/FMW_Home/modules/net.sf.antcontrib_1.1.0.0_1-0b2/lib/ant-
contrib.jar:/u02/applmgr/fs1/FMW_Home/oracle_common/modules/oracle.jdbc_11.1.1/ojdb
c6dms.jar:/u02/applmgr/fs1/FMW_Home/oracle_common/webcenter/modules/oracle.portlet.
server_11.1.1/oracle-portlet-
api.jar:/u02/applmgr/fs1/FMW_Home/oracle_common/modules/oracle.jrf_11.1.1/jrf.jar:/
u02/applmgr/fs1/FMW_Home/wlserver_10.3/common/derby/lib/derbyclient.jar:/u02/applmg
r/fs1/FMW_Home/Oracle_EBS-app1/shared-libs/ebs-appsborg/WEB-
INF/lib/ebsAppsborgManifest.jar:/u02/applmgr/fs1/EBSapps/comn/java/classes/oracle/a
pps/fnd/jar/adall.jar weblogic.NodeManager -v
Successfully launched the Node Manager.
The Node Manager process is running independent of the WLST process.
Exiting WLST will not stop the Node Manager process. Please refer
to the Node Manager logs for more information.
The Node Manager logs will be under
/u02/applmgr/fs1/FMW_Home/wlserver_10.3/common/nodemanager/nmHome1
Node Manager starting in the background

NodeManager is not fully up....Waiting for 10 sec....

NodeManager is started now

Connecting to Node Manager ...
Successfully Connected to Node Manager.

Connected to the Node Manager.

Starting server AdminServer ...

Successfully started server AdminServer ...

01/07/16-20:19:11 :: adadminsrvctl.sh: exiting with status 0

================================================================================

stty: standard input: Invalid argument

Enter the APPS user password:
stty: standard input: Invalid argument
stty: standard input: Invalid argument
Enter the WebLogic AdminServer password:
stty: standard input: Invalid argument
The log file is
/u02/applmgr/fs1/inst/apps/CLN1_picerpcln1/logs/appl/rgf/Thu_Jan_7_20_19_12_2016/ad
RegisterWLSListeners.log

01/07/16-20:19:32 :: adadminsrvctl.sh version 120.10.12020000.9

Validated the passed arguments for the option ebs-get-serverstatus
AdminServer is in RUNNING mode.

01/07/16-20:19:36 :: adadminsrvctl.sh: exiting with status 2

================================================================================

Validated the passed arguments for the option ebs-get-serverstatus

AdminServer is in RUNNING mode.

01/07/16-20:28:24 :: adadminsrvctl.sh version 120.10.12020000.9

Validated the passed arguments for the option ebs-get-serverstatus
AdminServer is in RUNNING mode.

01/07/16-20:28:27 :: adadminsrvctl.sh: exiting with status 2

================================================================================

Validated the passed arguments for the option ebs-get-serverstatus

AdminServer is in RUNNING mode.

01/24/16-09:08:55 :: adadminsrvctl.sh version 120.10.12020000.9

Validated the passed arguments for the option ebs-get-serverstatus
AdminServer is currently not running.

Validated the passed arguments for the option ebs-nmstart-adminsrv

Checking if the Admin Server is already up.
The Admin Server is not already up.
Checking if the Node Manager is already up..
Connecting to Node Manager ...
Successfully Connected to Node Manager.

The Node Manager is already up.

Starting server AdminServer ...

Successfully started server AdminServer ...

01/24/16-09:10:15 :: adadminsrvctl.sh: exiting with status 0

================================================================================
stty: standard input: Invalid argument
Enter the APPS user password:
stty: standard input: Invalid argument
stty: standard input: Invalid argument
Enter the WebLogic AdminServer password:
stty: standard input: Invalid argument
The log file is
/u02/applmgr/fs1/inst/apps/CLN1_picerpcln1/logs/appl/rgf/Sun_Jan_24_09_10_15_2016/a
dRegisterWLSListeners.log

Validated the passed arguments for the option ebs-get-serverstatus

AdminServer is in RUNNING mode.

Validated the passed arguments for the option ebs-get-serverstatus

AdminServer is in RUNNING mode.

02/03/16-09:19:59 :: adadminsrvctl.sh version 120.10.12020000.9

Validated the passed arguments for the option ebs-get-serverstatus
AdminServer is in RUNNING mode.

Validated the passed arguments for the option ebs-nmstop-adminsrv

Connecting to t3://picerpcln1.pic.com.kw:7002 with userid weblogic ...
Successfully connected to Admin Server 'AdminServer' that belongs to domain
'EBS_domain_CLN1'.

Warning: An insecure protocol was used to connect to the

server. To ensure on-the-wire security, the SSL port or
Admin port should be used instead.

Feb 03, 2016 9:20:09 AM ClientCommunicatorAdmin restart

WARNING: Failed to restart: java.rmi.NoSuchObjectException: The object identified
by: '283' could not be found. Either it was has not been exported or it has been
collected by the distributed garbage collector.
Feb 03, 2016 9:20:09 AM ClientCommunicatorAdmin restart
WARNING: Failed to restart: java.rmi.NoSuchObjectException: The object identified
by: '284' could not be found. Either it was has not been exported or it has been
collected by the distributed garbage collector.

Shutting down the server AdminServer with force=true while connected to AdminServer
...
WLST lost connection to the WebLogic Server that you were
connected to, this may happen if the server was shutdown or
partitioned. You will have to re-connect to the server once the
server is available.
Disconnected from weblogic server: AdminServer
Disconnected from weblogic server:

02/03/16-09:20:11 :: adadminsrvctl.sh: exiting with status 0

================================================================================

02/03/16-09:29:19 :: adadminsrvctl.sh version 120.10.12020000.9

Validated the passed arguments for the option ebs-get-serverstatus
AdminServer is currently not running.
Validated the passed arguments for the option ebs-nmstart-adminsrv
Checking if the Admin Server is already up.
The Admin Server is not already up.
Checking if the Node Manager is already up..
Connecting to Node Manager ...
Successfully Connected to Node Manager.

The Node Manager is already up.

Starting server AdminServer ...

Successfully started server AdminServer ...

02/03/16-09:30:32 :: adadminsrvctl.sh: exiting with status 0

================================================================================

stty: standard input: Invalid argument

Enter the APPS user password:
stty: standard input: Invalid argument
stty: standard input: Invalid argument
Enter the WebLogic AdminServer password:
stty: standard input: Invalid argument
The log file is
/u02/applmgr/fs1/inst/apps/CLN1_picerpcln1/logs/appl/rgf/Wed_Feb_3_09_30_32_2016/ad
RegisterWLSListeners.log

Validated the passed arguments for the option ebs-get-serverstatus

AdminServer is in RUNNING mode.

02/03/16-10:43:50 :: adadminsrvctl.sh version 120.10.12020000.9

Validated the passed arguments for the option ebs-get-serverstatus
AdminServer is in RUNNING mode.

Validated the passed arguments for the option ebs-nmstop-adminsrv

Connecting to t3://picerpcln1.pic.com.kw:7002 with userid weblogic ...
Successfully connected to Admin Server 'AdminServer' that belongs to domain
'EBS_domain_CLN1'.

Warning: An insecure protocol was used to connect to the

server. To ensure on-the-wire security, the SSL port or
Admin port should be used instead.

Feb 03, 2016 10:44:09 AM ClientCommunicatorAdmin restart

WARNING: Failed to restart: java.rmi.NoSuchObjectException: The object identified
by: '284' could not be found. Either it was has not been exported or it has been
collected by the distributed garbage collector.
Feb 03, 2016 10:44:09 AM ClientCommunicatorAdmin restart
WARNING: Failed to restart: java.rmi.NoSuchObjectException: The object identified
by: '283' could not be found. Either it was has not been exported or it has been
collected by the distributed garbage collector.

Shutting down the server AdminServer with force=true while connected to AdminServer
...
Disconnected from weblogic server: AdminServer
02/03/16-10:44:11 :: adadminsrvctl.sh: exiting with status 0

================================================================================

02/03/16-10:44:16 :: adadminsrvctl.sh version 120.10.12020000.9

Validated the passed arguments for the option ebs-get-serverstatus
AdminServer is currently not running.

Validated the passed arguments for the option ebs-nmstart-adminsrv

Checking if the Admin Server is already up.
The Admin Server is not already up.
Checking if the Node Manager is already up..
Connecting to Node Manager ...
Successfully Connected to Node Manager.

The Node Manager is already up.

Starting server AdminServer ...

Successfully started server AdminServer ...

02/03/16-10:45:29 :: adadminsrvctl.sh: exiting with status 0

================================================================================

stty: standard input: Invalid argument

Enter the APPS user password:
stty: standard input: Invalid argument
stty: standard input: Invalid argument
Enter the WebLogic AdminServer password:
stty: standard input: Invalid argument
The log file is
/u02/applmgr/fs1/inst/apps/CLN1_picerpcln1/logs/appl/rgf/Wed_Feb_3_10_45_29_2016/ad
RegisterWLSListeners.log

02/03/16-10:45:41 :: adadminsrvctl.sh version 120.10.12020000.9

Validated the passed arguments for the option ebs-get-serverstatus
AdminServer is in RUNNING mode.

02/03/16-10:45:55 :: adadminsrvctl.sh: exiting with status 0

================================================================================

Validated the passed arguments for the option ebs-get-serverstatus

AdminServer is in RUNNING mode.

02/03/16-11:54:42 :: adadminsrvctl.sh version 120.10.12020000.9

Validated the passed arguments for the option ebs-get-serverstatus
AdminServer is in RUNNING mode.

Validated the passed arguments for the option ebs-nmstop-adminsrv

Connecting to t3://picerpcln1.pic.com.kw:7002 with userid weblogic ...
Successfully connected to Admin Server 'AdminServer' that belongs to domain
'EBS_domain_CLN1'.

Warning: An insecure protocol was used to connect to the

server. To ensure on-the-wire security, the SSL port or
Admin port should be used instead.

Feb 03, 2016 11:54:51 AM ClientCommunicatorAdmin restart

WARNING: Failed to restart: java.rmi.NoSuchObjectException: The object identified
by: '284' could not be found. Either it was has not been exported or it has been
collected by the distributed garbage collector.
Feb 03, 2016 11:54:51 AM ClientCommunicatorAdmin restart
WARNING: Failed to restart: java.rmi.NoSuchObjectException: The object identified
by: '283' could not be found. Either it was has not been exported or it has been
collected by the distributed garbage collector.

Shutting down the server AdminServer with force=true while connected to AdminServer
...
WLST lost connection to the WebLogic Server that you were
connected to, this may happen if the server was shutdown or
partitioned. You will have to re-connect to the server once the
server is available.
Disconnected from weblogic server: AdminServer
Disconnected from weblogic server:

02/03/16-11:54:53 :: adadminsrvctl.sh: exiting with status 0

================================================================================

02/03/16-11:56:37 :: adadminsrvctl.sh version 120.10.12020000.9

Validated the passed arguments for the option ebs-get-serverstatus
AdminServer is currently not running.

Validated the passed arguments for the option ebs-nmstart-adminsrv

Checking if the Admin Server is already up.
The Admin Server is not already up.
Checking if the Node Manager is already up..
Connecting to Node Manager ...
Successfully Connected to Node Manager.

The Node Manager is already up.

Starting server AdminServer ...

Successfully started server AdminServer ...

02/03/16-11:57:38 :: adadminsrvctl.sh: exiting with status 0

================================================================================

stty: standard input: Invalid argument

Enter the APPS user password:
stty: standard input: Invalid argument
stty: standard input: Invalid argument
Enter the WebLogic AdminServer password:
stty: standard input: Invalid argument
The log file is
/u02/applmgr/fs1/inst/apps/CLN1_picerpcln1/logs/appl/rgf/Wed_Feb_3_11_57_38_2016/ad
RegisterWLSListeners.log

Validated the passed arguments for the option ebs-get-serverstatus

AdminServer is in RUNNING mode.

Validated the passed arguments for the option ebs-get-serverstatus

AdminServer is in RUNNING mode.

02/03/16-12:57:56 :: adadminsrvctl.sh version 120.10.12020000.9

Validated the passed arguments for the option ebs-get-serverstatus
AdminServer is in RUNNING mode.

Validated the passed arguments for the option ebs-nmstop-adminsrv

Connecting to t3://picerpcln1.pic.com.kw:7002 with userid weblogic ...
Successfully connected to Admin Server 'AdminServer' that belongs to domain
'EBS_domain_CLN1'.

Warning: An insecure protocol was used to connect to the

server. To ensure on-the-wire security, the SSL port or
Admin port should be used instead.

Feb 03, 2016 12:58:05 PM ClientCommunicatorAdmin restart

WARNING: Failed to restart: java.rmi.NoSuchObjectException: The object identified
by: '284' could not be found. Either it was has not been exported or it has been
collected by the distributed garbage collector.
Feb 03, 2016 12:58:05 PM ClientCommunicatorAdmin restart
WARNING: Failed to restart: java.rmi.NoSuchObjectException: The object identified
by: '283' could not be found. Either it was has not been exported or it has been
collected by the distributed garbage collector.

Shutting down the server AdminServer with force=true while connected to AdminServer
...
WLST lost connection to the WebLogic Server that you were
connected to, this may happen if the server was shutdown or
partitioned. You will have to re-connect to the server once the
server is available.
Disconnected from weblogic server: AdminServer
Disconnected from weblogic server:

02/03/16-12:58:07 :: adadminsrvctl.sh: exiting with status 0

================================================================================

02/03/16-13:03:14 :: adadminsrvctl.sh version 120.10.12020000.9

Validated the passed arguments for the option ebs-get-serverstatus
AdminServer is currently not running.

Validated the passed arguments for the option ebs-nmstart-adminsrv

Checking if the Admin Server is already up.
The Admin Server is not already up.
Checking if the Node Manager is already up..
Connecting to Node Manager ...
Successfully Connected to Node Manager.

The Node Manager is already up.

Starting server AdminServer ...

Successfully started server AdminServer ...

02/03/16-13:04:10 :: adadminsrvctl.sh: exiting with status 0

================================================================================

stty: standard input: Invalid argument

Enter the APPS user password:
stty: standard input: Invalid argument
stty: standard input: Invalid argument
Enter the WebLogic AdminServer password:
stty: standard input: Invalid argument
The log file is
/u02/applmgr/fs1/inst/apps/CLN1_picerpcln1/logs/appl/rgf/Wed_Feb_3_13_04_10_2016/ad
RegisterWLSListeners.log

Validated the passed arguments for the option ebs-get-serverstatus

AdminServer is in RUNNING mode.

Validated the passed arguments for the option ebs-get-serverstatus

AdminServer is in RUNNING mode.

02/04/16-08:50:37 :: adadminsrvctl.sh version 120.10.12020000.9

Validated the passed arguments for the option ebs-get-serverstatus
AdminServer is in RUNNING mode.

Validated the passed arguments for the option ebs-nmstop-adminsrv

Connecting to t3://picerpcln1.pic.com.kw:7002 with userid weblogic ...
Successfully connected to Admin Server 'AdminServer' that belongs to domain
'EBS_domain_CLN1'.

Warning: An insecure protocol was used to connect to the

server. To ensure on-the-wire security, the SSL port or
Admin port should be used instead.

Feb 04, 2016 8:50:46 AM ClientCommunicatorAdmin restart

WARNING: Failed to restart: java.rmi.NoSuchObjectException: The object identified
by: '284' could not be found. Either it was has not been exported or it has been
collected by the distributed garbage collector.
Feb 04, 2016 8:50:46 AM ClientCommunicatorAdmin restart
WARNING: Failed to restart: java.rmi.NoSuchObjectException: The object identified
by: '283' could not be found. Either it was has not been exported or it has been
collected by the distributed garbage collector.

Shutting down the server AdminServer with force=true while connected to AdminServer
...
WLST lost connection to the WebLogic Server that you were
connected to, this may happen if the server was shutdown or
partitioned. You will have to re-connect to the server once the
server is available.
Disconnected from weblogic server: AdminServer
Disconnected from weblogic server:

02/04/16-08:50:49 :: adadminsrvctl.sh: exiting with status 0

================================================================================

02/04/16-09:10:00 :: adadminsrvctl.sh version 120.10.12020000.9

Validated the passed arguments for the option ebs-get-serverstatus
AdminServer is currently not running.

Validated the passed arguments for the option ebs-nmstart-adminsrv

Checking if the Admin Server is already up.
The Admin Server is not already up.
Checking if the Node Manager is already up..
Connecting to Node Manager ...
Successfully Connected to Node Manager.

The Node Manager is already up.

Starting server AdminServer ...

Successfully started server AdminServer ...

02/04/16-09:11:17 :: adadminsrvctl.sh: exiting with status 0

================================================================================

stty: standard input: Invalid argument

Enter the APPS user password:
stty: standard input: Invalid argument
stty: standard input: Invalid argument
Enter the WebLogic AdminServer password:
stty: standard input: Invalid argument
The log file is
/u02/applmgr/fs1/inst/apps/CLN1_picerpcln1/logs/appl/rgf/Thu_Feb_4_09_11_17_2016/ad
RegisterWLSListeners.log

Validated the passed arguments for the option ebs-get-serverstatus

AdminServer is in RUNNING mode.

02/04/16-11:44:24 :: adadminsrvctl.sh version 120.10.12020000.9

Validated the passed arguments for the option ebs-get-serverstatus
AdminServer is in RUNNING mode.

Validated the passed arguments for the option ebs-nmstop-adminsrv

Connecting to t3://picerpcln1.pic.com.kw:7002 with userid weblogic ...
Successfully connected to Admin Server 'AdminServer' that belongs to domain
'EBS_domain_CLN1'.

Warning: An insecure protocol was used to connect to the

server. To ensure on-the-wire security, the SSL port or
Admin port should be used instead.
Feb 04, 2016 11:44:44 AM ClientCommunicatorAdmin restart
WARNING: Failed to restart: java.rmi.NoSuchObjectException: The object identified
by: '284' could not be found. Either it was has not been exported or it has been
collected by the distributed garbage collector.
Feb 04, 2016 11:44:44 AM ClientCommunicatorAdmin restart
WARNING: Failed to restart: java.rmi.NoSuchObjectException: The object identified
by: '283' could not be found. Either it was has not been exported or it has been
collected by the distributed garbage collector.

Shutting down the server AdminServer with force=true while connected to AdminServer
...
WLST lost connection to the WebLogic Server that you were
connected to, this may happen if the server was shutdown or
partitioned. You will have to re-connect to the server once the
server is available.
Disconnected from weblogic server: AdminServer
Disconnected from weblogic server:

02/04/16-11:44:46 :: adadminsrvctl.sh: exiting with status 0

================================================================================

02/04/16-11:44:58 :: adadminsrvctl.sh version 120.10.12020000.9

Validated the passed arguments for the option ebs-get-serverstatus
AdminServer is currently not running.

Validated the passed arguments for the option ebs-nmstart-adminsrv

Checking if the Admin Server is already up.
The Admin Server is not already up.
Checking if the Node Manager is already up..
Connecting to Node Manager ...
Successfully Connected to Node Manager.

The Node Manager is already up.

02/04/16-11:45:58 :: adadminsrvctl.sh: exiting with status 130

================================================================================

02/04/16-11:46:00 :: adadminsrvctl.sh version 120.10.12020000.9

Validated the passed arguments for the option ebs-get-serverstatus
AdminServer is in RUNNING mode.

02/04/16-11:46:14 :: adadminsrvctl.sh: exiting with status 2

================================================================================

Validated the passed arguments for the option ebs-get-serverstatus

AdminServer is in RUNNING mode.

02/04/16-11:48:14 :: adadminsrvctl.sh version 120.10.12020000.9

Validated the passed arguments for the option ebs-get-serverstatus
AdminServer is in RUNNING mode.

Validated the passed arguments for the option ebs-nmstop-adminsrv

Connecting to t3://picerpcln1.pic.com.kw:7002 with userid weblogic ...
Successfully connected to Admin Server 'AdminServer' that belongs to domain
'EBS_domain_CLN1'.

Warning: An insecure protocol was used to connect to the

server. To ensure on-the-wire security, the SSL port or
Admin port should be used instead.

Shutting down the server AdminServer with force=true while connected to AdminServer
...
WLST lost connection to the WebLogic Server that you were
connected to, this may happen if the server was shutdown or
partitioned. You will have to re-connect to the server once the
server is available.
Disconnected from weblogic server: AdminServer
Disconnected from weblogic server:

02/04/16-11:48:27 :: adadminsrvctl.sh: exiting with status 0

================================================================================

02/04/16-12:03:04 :: adadminsrvctl.sh version 120.10.12020000.9

Validated the passed arguments for the option ebs-get-serverstatus
AdminServer is currently not running.

Validated the passed arguments for the option ebs-nmstart-adminsrv

Checking if the Admin Server is already up.
The Admin Server is not already up.
Checking if the Node Manager is already up..
Traceback (innermost last):
File "<string>", line 1, in ?
File "<iostream>", line 123, in nmConnect
File "<iostream>", line 648, in raiseWLSTException
WLSTException: Error occured while performing nmConnect : Cannot connect to Node
Manager. : Connection refused. Could not connect to NodeManager. Check that it is
running at picerpcln1.pic.com.kw:5557.
Use dumpStack() to view the full stacktrace

Connecting to Node Manager ...

Launching NodeManager ...

Properties: {Arguments=-
Djava.security.egd=file:/dev/./urandom,JavaHome=/u02/applmgr/fs1/EBSapps/comn/util/
jdk64,ListenAddress=picerpcln1.pic.com.kw,ListenPort=5557,LogAppend=false,NodeManag
erHome=/u02/applmgr/fs1/FMW_Home/wlserver_10.3/common/nodemanager/nmHome1,SecureLis
tener=false,StartScriptEnabled=false,StartScriptName=startWebLogic.sh,}
Command: /u02/applmgr/fs1/EBSapps/comn/util/jdk64/jre/bin/java -classpath
/u02/applmgr/fs1/EBSapps/comn/util/jdk64/jre/lib/rt.jar:/u02/applmgr/fs1/EBSapps/co
mn/util/jdk64/jre/lib/i18n.jar:/u02/applmgr/fs1/FMW_Home/patch_wls1036/profiles/def
ault/sys_manifest_classpath/weblogic_patch.jar:/u02/applmgr/fs1/EBSapps/comn/util/j
dk64/lib/tools.jar:/u02/applmgr/fs1/FMW_Home/wlserver_10.3/server/lib/weblogic_sp.j
ar:/u02/applmgr/fs1/FMW_Home/wlserver_10.3/server/lib/weblogic.jar:/u02/applmgr/fs1
/FMW_Home/modules/features/weblogic.server.modules_10.3.6.0.jar:/u02/applmgr/fs1/FM
W_Home/wlserver_10.3/server/lib/webservices.jar:/u02/applmgr/fs1/FMW_Home/modules/o
rg.apache.ant_1.7.1/lib/ant-
all.jar:/u02/applmgr/fs1/FMW_Home/modules/net.sf.antcontrib_1.1.0.0_1-0b2/lib/ant-
contrib.jar:/u02/applmgr/fs1/FMW_Home/oracle_common/modules/oracle.jdbc_11.1.1/ojdb
c6dms.jar:/u02/applmgr/fs1/FMW_Home/oracle_common/webcenter/modules/oracle.portlet.
server_11.1.1/oracle-portlet-
api.jar:/u02/applmgr/fs1/FMW_Home/oracle_common/modules/oracle.jrf_11.1.1/jrf.jar:/
u02/applmgr/fs1/FMW_Home/wlserver_10.3/common/derby/lib/derbyclient.jar:/u02/applmg
r/fs1/FMW_Home/Oracle_EBS-app1/shared-libs/ebs-appsborg/WEB-
INF/lib/ebsAppsborgManifest.jar:/u02/applmgr/fs1/EBSapps/comn/java/classes/oracle/a
pps/fnd/jar/adall.jar weblogic.NodeManager -v
Successfully launched the Node Manager.
The Node Manager process is running independent of the WLST process.
Exiting WLST will not stop the Node Manager process. Please refer
to the Node Manager logs for more information.
The Node Manager logs will be under
/u02/applmgr/fs1/FMW_Home/wlserver_10.3/common/nodemanager/nmHome1
Node Manager starting in the background

Connecting to Node Manager ...

Successfully Connected to Node Manager.

Connected to the Node Manager.

Starting server AdminServer ...

Successfully started server AdminServer ...

02/04/16-12:04:27 :: adadminsrvctl.sh: exiting with status 0

================================================================================

stty: standard input: Invalid argument

Enter the APPS user password:
stty: standard input: Invalid argument
stty: standard input: Invalid argument
Enter the WebLogic AdminServer password:
stty: standard input: Invalid argument
The log file is
/u02/applmgr/fs1/inst/apps/CLN1_picerpcln1/logs/appl/rgf/Thu_Feb_4_12_04_27_2016/ad
RegisterWLSListeners.log

02/04/16-12:06:34 :: adadminsrvctl.sh version 120.10.12020000.9

Validated the passed arguments for the option ebs-get-serverstatus
ERROR: Invalid credentials passed.

02/04/16-12:06:37 :: adadminsrvctl.sh: exiting with status 1

================================================================================

Validated the passed arguments for the option ebs-get-serverstatus

ERROR: Invalid credentials passed.

02/04/16-12:13:56 :: adadminsrvctl.sh version 120.10.12020000.9

Validated the passed arguments for the option ebs-get-serverstatus
AdminServer is in RUNNING mode.

02/04/16-12:13:59 :: adadminsrvctl.sh: exiting with status 2

================================================================================

Validated the passed arguments for the option ebs-get-serverstatus

AdminServer is in RUNNING mode.

02/07/16-09:18:17 :: adadminsrvctl.sh version 120.10.12020000.9

Validated the passed arguments for the option ebs-get-serverstatus
AdminServer is in RUNNING mode.

02/07/16-09:18:32 :: adadminsrvctl.sh: exiting with status 0

================================================================================

02/07/16-09:19:08 :: adadminsrvctl.sh version 120.10.12020000.9

Validated the passed arguments for the option ebs-get-serverstatus
AdminServer is in RUNNING mode.

Validated the passed arguments for the option ebs-nmstop-adminsrv

Connecting to t3://picerpcln1.pic.com.kw:7002 with userid weblogic ...
Successfully connected to Admin Server 'AdminServer' that belongs to domain
'EBS_domain_CLN1'.

Warning: An insecure protocol was used to connect to the

server. To ensure on-the-wire security, the SSL port or
Admin port should be used instead.

Feb 07, 2016 9:19:28 AM ClientCommunicatorAdmin restart

WARNING: Failed to restart: java.rmi.NoSuchObjectException: The object identified
by: '284' could not be found. Either it was has not been exported or it has been
collected by the distributed garbage collector.
Feb 07, 2016 9:19:28 AM ClientCommunicatorAdmin restart
WARNING: Failed to restart: java.rmi.NoSuchObjectException: The object identified
by: '283' could not be found. Either it was has not been exported or it has been
collected by the distributed garbage collector.

Shutting down the server AdminServer with force=true while connected to AdminServer
...
WLST lost connection to the WebLogic Server that you were
connected to, this may happen if the server was shutdown or
partitioned. You will have to re-connect to the server once the
server is available.
Disconnected from weblogic server: AdminServer
Disconnected from weblogic server:

02/07/16-09:19:32 :: adadminsrvctl.sh: exiting with status 0

================================================================================
02/07/16-09:19:38 :: adadminsrvctl.sh version 120.10.12020000.9
Validated the passed arguments for the option ebs-get-serverstatus
AdminServer is currently not running.

02/07/16-09:19:49 :: adadminsrvctl.sh: exiting with status 0

================================================================================

02/07/16-09:19:57 :: adadminsrvctl.sh version 120.10.12020000.9

Validated the passed arguments for the option ebs-get-serverstatus
AdminServer is currently not running.

Validated the passed arguments for the option ebs-nmstart-adminsrv

Checking if the Admin Server is already up.
The Admin Server is not already up.
Checking if the Node Manager is already up..
Connecting to Node Manager ...
Successfully Connected to Node Manager.

The Node Manager is already up.

Starting server AdminServer ...

Successfully started server AdminServer ...

02/07/16-09:21:10 :: adadminsrvctl.sh: exiting with status 0

================================================================================

stty: standard input: Invalid argument

Enter the APPS user password:
stty: standard input: Invalid argument
stty: standard input: Invalid argument
Enter the WebLogic AdminServer password:
stty: standard input: Invalid argument
The log file is
/u02/applmgr/fs1/inst/apps/CLN1_picerpcln1/logs/appl/rgf/Sun_Feb_7_09_21_10_2016/ad
RegisterWLSListeners.log

Validated the passed arguments for the option ebs-get-serverstatus

AdminServer is in RUNNING mode.

02/07/16-10:40:02 :: adadminsrvctl.sh version 120.10.12020000.9

Validated the passed arguments for the option ebs-get-serverstatus
AdminServer is in RUNNING mode.

Validated the passed arguments for the option ebs-nmstop-adminsrv

Connecting to t3://picerpcln1.pic.com.kw:7002 with userid weblogic ...
Successfully connected to Admin Server 'AdminServer' that belongs to domain
'EBS_domain_CLN1'.

Warning: An insecure protocol was used to connect to the

server. To ensure on-the-wire security, the SSL port or
Admin port should be used instead.
Feb 07, 2016 10:40:11 AM ClientCommunicatorAdmin restart
WARNING: Failed to restart: java.rmi.NoSuchObjectException: The object identified
by: '284' could not be found. Either it was has not been exported or it has been
collected by the distributed garbage collector.
Feb 07, 2016 10:40:11 AM ClientCommunicatorAdmin restart
WARNING: Failed to restart: java.rmi.NoSuchObjectException: The object identified
by: '283' could not be found. Either it was has not been exported or it has been
collected by the distributed garbage collector.

Shutting down the server AdminServer with force=true while connected to AdminServer
...
WLST lost connection to the WebLogic Server that you were
connected to, this may happen if the server was shutdown or
partitioned. You will have to re-connect to the server once the
server is available.
Disconnected from weblogic server: AdminServer
Disconnected from weblogic server:

02/07/16-10:40:14 :: adadminsrvctl.sh: exiting with status 0

================================================================================

02/07/16-10:41:58 :: adadminsrvctl.sh version 120.10.12020000.9

Validated the passed arguments for the option ebs-get-serverstatus
AdminServer is currently not running.

Validated the passed arguments for the option ebs-nmstart-adminsrv

Checking if the Admin Server is already up.
The Admin Server is not already up.
Checking if the Node Manager is already up..
Connecting to Node Manager ...
Successfully Connected to Node Manager.

The Node Manager is already up.

Starting server AdminServer ...

Successfully started server AdminServer ...

02/07/16-10:42:49 :: adadminsrvctl.sh: exiting with status 0

================================================================================

stty: standard input: Invalid argument

Enter the APPS user password:
stty: standard input: Invalid argument
stty: standard input: Invalid argument
Enter the WebLogic AdminServer password:
stty: standard input: Invalid argument
The log file is
/u02/applmgr/fs1/inst/apps/CLN1_picerpcln1/logs/appl/rgf/Sun_Feb_7_10_42_49_2016/ad
RegisterWLSListeners.log

Validated the passed arguments for the option ebs-get-serverstatus

AdminServer is in RUNNING mode.

Validated the passed arguments for the option ebs-get-serverstatus

AdminServer is in RUNNING mode.

02/07/16-11:06:00 :: adadminsrvctl.sh version 120.10.12020000.9

Validated the passed arguments for the option ebs-get-serverstatus
AdminServer is in RUNNING mode.

Validated the passed arguments for the option ebs-nmstop-adminsrv

Connecting to t3://picerpcln1.pic.com.kw:7002 with userid weblogic ...
Successfully connected to Admin Server 'AdminServer' that belongs to domain
'EBS_domain_CLN1'.

Warning: An insecure protocol was used to connect to the

server. To ensure on-the-wire security, the SSL port or
Admin port should be used instead.

Feb 07, 2016 11:06:09 AM ClientCommunicatorAdmin restart

WARNING: Failed to restart: java.rmi.NoSuchObjectException: The object identified
by: '284' could not be found. Either it was has not been exported or it has been
collected by the distributed garbage collector.
Feb 07, 2016 11:06:09 AM ClientCommunicatorAdmin restart
WARNING: Failed to restart: java.rmi.NoSuchObjectException: The object identified
by: '283' could not be found. Either it was has not been exported or it has been
collected by the distributed garbage collector.

Shutting down the server AdminServer with force=true while connected to AdminServer
...
WLST lost connection to the WebLogic Server that you were
connected to, this may happen if the server was shutdown or
partitioned. You will have to re-connect to the server once the
server is available.
Disconnected from weblogic server: AdminServer
Disconnected from weblogic server:

02/07/16-11:06:12 :: adadminsrvctl.sh: exiting with status 0

================================================================================

02/07/16-11:07:14 :: adadminsrvctl.sh version 120.10.12020000.9

Validated the passed arguments for the option ebs-get-serverstatus
AdminServer is currently not running.

Validated the passed arguments for the option ebs-nmstart-adminsrv

Checking if the Admin Server is already up.
The Admin Server is not already up.
Checking if the Node Manager is already up..
Traceback (innermost last):
File "<string>", line 1, in ?
File "<iostream>", line 123, in nmConnect
File "<iostream>", line 648, in raiseWLSTException
WLSTException: Error occured while performing nmConnect : Cannot connect to Node
Manager. : Access to domain 'EBS_domain_CLN1' for user 'weblogic' denied
Use dumpStack() to view the full stacktrace
Connecting to Node Manager ...

ERROR: Invalid credentials passed.

ERROR: Unable to connect to the Node Manager. The Admin Server cannot be started
up.
Successfully disconnected from Node Manager.

02/07/16-11:07:22 :: adadminsrvctl.sh: exiting with status 1

================================================================================

Validated the passed arguments for the option ebs-get-serverstatus

AdminServer is currently not running.

02/07/16-11:08:08 :: adadminsrvctl.sh version 120.10.12020000.9

Validated the passed arguments for the option ebs-get-serverstatus
AdminServer is currently not running.

Validated the passed arguments for the option ebs-nmstart-adminsrv

Checking if the Admin Server is already up.
The Admin Server is not already up.
Checking if the Node Manager is already up..
Connecting to Node Manager ...
Successfully Connected to Node Manager.

The Node Manager is already up.

Starting server AdminServer ...

Successfully started server AdminServer ...

02/07/16-11:09:00 :: adadminsrvctl.sh: exiting with status 0

================================================================================

stty: standard input: Invalid argument

Enter the APPS user password:
stty: standard input: Invalid argument
stty: standard input: Invalid argument
Enter the WebLogic AdminServer password:
stty: standard input: Invalid argument
The log file is
/u02/applmgr/fs1/inst/apps/CLN1_picerpcln1/logs/appl/rgf/Sun_Feb_7_11_09_00_2016/ad
RegisterWLSListeners.log

Validated the passed arguments for the option ebs-get-serverstatus

AdminServer is in RUNNING mode.

Validated the passed arguments for the option ebs-get-serverstatus

AdminServer is in RUNNING mode.

02/07/16-11:27:12 :: adadminsrvctl.sh version 120.10.12020000.9

Validated the passed arguments for the option ebs-get-serverstatus
AdminServer is in RUNNING mode.
Validated the passed arguments for the option ebs-nmstop-adminsrv
Connecting to t3://picerpcln1.pic.com.kw:7002 with userid weblogic ...
Successfully connected to Admin Server 'AdminServer' that belongs to domain
'EBS_domain_CLN1'.

Warning: An insecure protocol was used to connect to the

server. To ensure on-the-wire security, the SSL port or
Admin port should be used instead.

Feb 07, 2016 11:27:22 AM ClientCommunicatorAdmin restart

WARNING: Failed to restart: java.rmi.NoSuchObjectException: The object identified
by: '284' could not be found. Either it was has not been exported or it has been
collected by the distributed garbage collector.
Feb 07, 2016 11:27:22 AM ClientCommunicatorAdmin restart
WARNING: Failed to restart: java.rmi.NoSuchObjectException: The object identified
by: '283' could not be found. Either it was has not been exported or it has been
collected by the distributed garbage collector.

Shutting down the server AdminServer with force=true while connected to AdminServer
...
WLST lost connection to the WebLogic Server that you were
connected to, this may happen if the server was shutdown or
partitioned. You will have to re-connect to the server once the
server is available.
Disconnected from weblogic server: AdminServer
Disconnected from weblogic server:

02/07/16-11:27:24 :: adadminsrvctl.sh: exiting with status 0

================================================================================

02/07/16-11:35:22 :: adadminsrvctl.sh version 120.10.12020000.9

Validated the passed arguments for the option ebs-get-serverstatus
AdminServer is currently not running.

Validated the passed arguments for the option ebs-nmstart-adminsrv

Checking if the Admin Server is already up.
The Admin Server is not already up.
Checking if the Node Manager is already up..
Connecting to Node Manager ...
Successfully Connected to Node Manager.

The Node Manager is already up.

Starting server AdminServer ...

Successfully started server AdminServer ...

02/07/16-11:36:18 :: adadminsrvctl.sh: exiting with status 0

================================================================================
stty: standard input: Invalid argument
Enter the APPS user password:
stty: standard input: Invalid argument
stty: standard input: Invalid argument
Enter the WebLogic AdminServer password:
stty: standard input: Invalid argument
The log file is
/u02/applmgr/fs1/inst/apps/CLN1_picerpcln1/logs/appl/rgf/Sun_Feb_7_11_36_19_2016/ad
RegisterWLSListeners.log

Validated the passed arguments for the option ebs-get-serverstatus

AdminServer is in RUNNING mode.

Validated the passed arguments for the option ebs-get-serverstatus

ERROR: Invalid credentials passed.

02/07/16-12:15:31 :: adadminsrvctl.sh version 120.10.12020000.9

Validated the passed arguments for the option ebs-get-serverstatus
ERROR: Invalid credentials passed.

02/07/16-12:15:34 :: adadminsrvctl.sh: exiting with status 1

================================================================================

Validated the passed arguments for the option ebs-get-serverstatus

AdminServer is in RUNNING mode.

02/07/16-12:31:11 :: adadminsrvctl.sh version 120.10.12020000.9

Validated the passed arguments for the option ebs-get-serverstatus
AdminServer is in RUNNING mode.

Validated the passed arguments for the option ebs-nmstop-adminsrv

Connecting to t3://picerpcln1.pic.com.kw:7002 with userid weblogic ...
Successfully connected to Admin Server 'AdminServer' that belongs to domain
'EBS_domain_CLN1'.

Warning: An insecure protocol was used to connect to the

server. To ensure on-the-wire security, the SSL port or
Admin port should be used instead.

Feb 07, 2016 12:31:20 PM ClientCommunicatorAdmin restart

WARNING: Failed to restart: java.rmi.NoSuchObjectException: The object identified
by: '284' could not be found. Either it was has not been exported or it has been
collected by the distributed garbage collector.
Feb 07, 2016 12:31:20 PM ClientCommunicatorAdmin restart
WARNING: Failed to restart: java.rmi.NoSuchObjectException: The object identified
by: '283' could not be found. Either it was has not been exported or it has been
collected by the distributed garbage collector.

Shutting down the server AdminServer with force=true while connected to AdminServer
...
WLST lost connection to the WebLogic Server that you were
connected to, this may happen if the server was shutdown or
partitioned. You will have to re-connect to the server once the
server is available.
Disconnected from weblogic server: AdminServer
Disconnected from weblogic server:
02/07/16-12:31:22 :: adadminsrvctl.sh: exiting with status 0

================================================================================

02/07/16-12:32:57 :: adadminsrvctl.sh version 120.10.12020000.9

Validated the passed arguments for the option ebs-get-serverstatus
AdminServer is currently not running.

Validated the passed arguments for the option ebs-nmstart-adminsrv

Checking if the Admin Server is already up.
The Admin Server is not already up.
Checking if the Node Manager is already up..
Connecting to Node Manager ...
Successfully Connected to Node Manager.

The Node Manager is already up.

Starting server AdminServer ...

Successfully started server AdminServer ...

02/07/16-12:33:51 :: adadminsrvctl.sh: exiting with status 0

================================================================================

stty: standard input: Invalid argument

Enter the APPS user password:
stty: standard input: Invalid argument
stty: standard input: Invalid argument
Enter the WebLogic AdminServer password:
stty: standard input: Invalid argument
The log file is
/u02/applmgr/fs1/inst/apps/CLN1_picerpcln1/logs/appl/rgf/Sun_Feb_7_12_33_51_2016/ad
RegisterWLSListeners.log

Validated the passed arguments for the option ebs-get-serverstatus

AdminServer is in RUNNING mode.

Validated the passed arguments for the option ebs-get-serverstatus

AdminServer is in RUNNING mode.

02/08/16-19:33:54 :: adadminsrvctl.sh version 120.10.12020000.9

Validated the passed arguments for the option ebs-get-serverstatus
AdminServer is in RUNNING mode.

Validated the passed arguments for the option ebs-nmstop-adminsrv

Connecting to t3://picerpcln1.pic.com.kw:7002 with userid weblogic ...
Successfully connected to Admin Server 'AdminServer' that belongs to domain
'EBS_domain_CLN1'.

Warning: An insecure protocol was used to connect to the

server. To ensure on-the-wire security, the SSL port or
Admin port should be used instead.
Feb 08, 2016 7:34:03 PM ClientCommunicatorAdmin restart
WARNING: Failed to restart: java.rmi.NoSuchObjectException: The object identified
by: '284' could not be found. Either it was has not been exported or it has been
collected by the distributed garbage collector.
Feb 08, 2016 7:34:03 PM ClientCommunicatorAdmin restart
WARNING: Failed to restart: java.rmi.NoSuchObjectException: The object identified
by: '283' could not be found. Either it was has not been exported or it has been
collected by the distributed garbage collector.

Shutting down the server AdminServer with force=true while connected to AdminServer
...
WLST lost connection to the WebLogic Server that you were
connected to, this may happen if the server was shutdown or
partitioned. You will have to re-connect to the server once the
server is available.
Disconnected from weblogic server: AdminServer
Disconnected from weblogic server:

02/08/16-19:34:05 :: adadminsrvctl.sh: exiting with status 0

================================================================================

02/08/16-19:42:13 :: adadminsrvctl.sh version 120.10.12020000.9

Validated the passed arguments for the option ebs-get-serverstatus
AdminServer is currently not running.

Validated the passed arguments for the option ebs-nmstart-adminsrv

Checking if the Admin Server is already up.
The Admin Server is not already up.
Checking if the Node Manager is already up..
Connecting to Node Manager ...
Successfully Connected to Node Manager.

The Node Manager is already up.

Starting server AdminServer ...

Successfully started server AdminServer ...

02/08/16-19:43:11 :: adadminsrvctl.sh: exiting with status 0

================================================================================

stty: standard input: Invalid argument

Enter the APPS user password:
stty: standard input: Invalid argument
stty: standard input: Invalid argument
Enter the WebLogic AdminServer password:
stty: standard input: Invalid argument
The log file is
/u02/applmgr/fs1/inst/apps/CLN1_picerpcln1/logs/appl/rgf/Mon_Feb_8_19_43_12_2016/ad
RegisterWLSListeners.log
Validated the passed arguments for the option ebs-get-serverstatus
AdminServer is in RUNNING mode.

02/09/16-07:55:48 :: adadminsrvctl.sh version 120.10.12020000.9

Validated the passed arguments for the option ebs-get-serverstatus
AdminServer is in RUNNING mode.

02/09/16-07:55:52 :: adadminsrvctl.sh: exiting with status 2

================================================================================

Validated the passed arguments for the option ebs-get-serverstatus

AdminServer is in RUNNING mode.