Issue 1
To see if all the pipelines are up, use this command: »pss | grep ifw«. The output should look like this:
$ pss | grep ifw
pin 18601 18486 0 10:48:02 pts/0 00:00 /opt/portal/pin/bin/dm_ifw_sync
pin 24721 1 0 11:53:28 pts/0 01:00 bin/ifw -r ./custom/conf/dia_1_P.reg
pin 18603 18486 0 10:48:02 pts/0 00:00 /opt/portal/pin/bin/dm_ifw_sync
pin 18613 18486 0 10:48:03 pts/0 00:00 /opt/portal/pin/bin/dm_ifw_sync
pin 18607 18486 0 10:48:03 pts/0 00:00 /opt/portal/pin/bin/dm_ifw_sync
pin 18612 18486 0 10:48:03 pts/0 00:00 /opt/portal/pin/bin/dm_ifw_sync
pin 18605 18486 0 10:48:03 pts/0 00:00 /opt/portal/pin/bin/dm_ifw_sync
pin 18600 18486 0 10:48:02 pts/0 00:00 /opt/portal/pin/bin/dm_ifw_sync
pin 18618 18486 0 10:48:03 pts/0 00:00 /opt/portal/pin/bin/dm_ifw_sync
pin 18616 18486 0 10:48:03 pts/0 00:00 /opt/portal/pin/bin/dm_ifw_sync
pin 18611 18486 0 10:48:03 pts/0 00:00 /opt/portal/pin/bin/dm_ifw_sync
pin 18614 18486 0 10:48:03 pts/0 00:00 /opt/portal/pin/bin/dm_ifw_sync
pin 18486 1 0 10:48:00 pts/0 00:00 /opt/portal/pin/bin/dm_ifw_sync
pin 18610 18486 0 10:48:03 pts/0 00:00 /opt/portal/pin/bin/dm_ifw_sync
pin 18608 18486 0 10:48:03 pts/0 00:00 /opt/portal/pin/bin/dm_ifw_sync
pin 19123 1 0 10:50:47 pts/0 00:18 bin/ifw -r ./custom/conf/rt_1_P.reg
pin 18490 18486 0 10:48:00 pts/0 00:00 /opt/portal/pin/bin/dm_ifw_sync
pin 18609 18486 0 10:48:03 pts/0 00:00 /opt/portal/pin/bin/dm_ifw_sync
pin 18602 18486 0 10:48:02 pts/0 00:00 /opt/portal/pin/bin/dm_ifw_sync
pin 18617 18486 0 10:48:03 pts/0 00:00 /opt/portal/pin/bin/dm_ifw_sync
pin 18615 18486 0 10:48:03 pts/0 00:00 /opt/portal/pin/bin/dm_ifw_sync
pin 19130 1 0 10:50:59 pts/0 01:29 bin/ifw -r ./custom/conf/mbi_1_P.reg
pin 18606 18486 0 10:48:03 pts/0 00:00 /opt/portal/pin/bin/dm_ifw_sync
pin 18604 18486 0 10:48:02 pts/0 00:00 /opt/portal/pin/bin/dm_ifw_sync
pin 21975 1 0 11:23:18 pts/0 01:01 bin/ifw -r ./custom/conf/dcn_1_P.reg
pin 19126 1 0 10:50:53 pts/0 00:17 bin/ifw -r ./custom/conf/rt_1_S.reg
Issue 2
If you can’t start the pipeline and you get this error message: »Error: Could not start event handler, cannot proceed.», then you need to kill the event handler process. See the example that follows:
/opt/portal/pre_dia/log/process/ $ tail -f dia_1_P.out
;
Pipeline Server / Version 7.3 10095 started at 06.01.2009 16:23:11.
Copyright (c) 1998 – 2007 Oracle Corporation. All rights reserved.
Too many failed attempts at starting event handler daemon.
Error: Could not start event handler, cannot proceed.
Pipeline Server / Version 7.3 10095 finished at 06.01.2009 16:23:11.
Resolution:
$ pss | grep dia
pin 27727 1 0 15:50:21 pts/3 00:00 /opt/portal/pre_dia/bin/ifw_eventhandler64
pin 3055 4463 1 16:24:18 pts/3 00:00 grep dia
$ kill -9 27727
Issue 3
To rebalance the MBI pipeline, run the following command:
cd /opt/portal/pre_mbi/bin/
./pin_ctl snmpset rebalanceAaaGw aaa
To rebalance the DIAMETER pipeline, run the following command:
cd /opt/portal/pre_dia/bin/
./pin_ctl snmpset rebalanceAaaGw aaa
Issue 4
If you get this error message: »ERR_TAM_INIT_FAILED,« then you need to delete files in the tam directory.
bin/ifw: An error occurred during creation.
Originator : ifw.Pipelines.ExceptionPipeline.TransactionManager
Destination :
Message : ERR_TAM_INIT_FAILED
Arguments : ifw.Pipelines.ExceptionPipeline.TransactionManager
State : false
Severity : CRITICAL
Thread : 1
Resolution:
cd /opt/portal/
/tam
Backup the files to other location
rm TamTrans*.dat
rm ExceptionBinaryLogFile.dat
Issue 5
If you get this error message: »ERR_REG_LOCK_FILE_EXISTS,« then you need to delete the lock file.
*** Log not initialised.
*** Tried to write message ‘[T:1] ERR_REG_LOCK_FILE_EXISTS’
*** argument (0): ./custom/conf/rt_1_P.reg.lock
bin/ifw: An error occurred during creation.
Originator : ifw
Destination :
Message : ERR_REG_LOCK_FILE_EXISTS
Arguments : ./custom/conf/rt_1_P.reg.lock
State : false
Severity : CRITICAL
Thread : 1
Resolution:
cd /opt/portal/
/custom/conf
rm rt_1_P.reg.lock
