Support Centre

Find articles, help and advice.

 
Welcome, Guest Login

Support Center

Name is required.
Email address is required.
Invalid email address
Answer is required.
Exceeding max length of 5KB

Finishing Installation and Starting the Business Enterprise Server

Mathew Allbright Feb 11, 2014 11:45AM UTC

Hi

I have managed to get my .NET stuff sorted out and can now launch BSD correctly.

I am now trying to verify all is working by following your instructions on pages 86 - 89 of the BES 3.6 install guide, however, I cannot seem to get any alerts from ISS after running the ./QSDown and ./QSUp scripts.

I have verified all required BES processes are running (also restarted BES (./ppServer stop / ./ppServer Start), but still no joy.

The only alert I can see when performing an alert query is 'Service Example_Service Type (Peak) Availability at 100.00%' This come from ALERTSERVER.

Having looked in the POWERpack_Log all appears OK but often get the below messages written into it and was wondering if this was related in anyway?

20140211 11:42:47 POWERpackTrans:(System) Alert Server Connection failed(145 Connection timed out) -1
20140211 11:42:47 POWERpackTrans:(ISS) Alert Server Connection failed(145 Connection timed out) -1
20140211 11:42:52 POWERpackTrans:(System) Establishing Connection to Alert Server Socket 30000
20140211 11:42:52 POWERpackTrans:(ISS) Establishing Connection to Alert Server Socket 30000

Regards

Up 0 rated Down
Colin Griffiths Feb 11, 2014 12:23PM UTC Interlink Software Agent
Hi Matthew,

This type of error is indicative of AlertServer not having initialised.

Things to check

1. Issue 'ppState AlertServer' and check the pid under the Processes column. Validate via 'ps -ef |grep <PID>' that it is the AlertServer java process
2. Is the dbi running 'ppState dbi'. AlertServer can not fully initialise until the dbi has finished databasing all outstanding alerts/events. 'tail -f $PPLOG/dbi_Log' has it initialised?
3. Setup and active 'tail -f $PPLOG/POWERpack_Log' and then recycle AlertServer. This is a typical startup sequence.

20140211 12:22:19 AlertServer: Query Port set to default 40000
20140211 12:22:19 AlertServer: Starting AlertServer version 3.5.5.129
20140211 12:22:19 AlertServer: Setting Database type to SYBASE
20140211 12:22:19 AlertServer: Setting host to devtest
20140211 12:22:20 AlertServer: AlertServer TimeZone id:GB
20140211 12:22:20 AlertServer: AlertServer TimeZone offset:0
20140211 12:22:20 AlertServer: Testing database connection...
20140211 12:22:20 AlertServer: URL = jdbc:sybase:Tds:devtest:5000
20140211 12:22:22 AlertServer: Database connection OK
20140211 12:22:22 AlertServer: Sending all alerts to Admin users turned off
20140211 12:22:22 AlertServer: No maintenance config file.
20140211 12:22:22 AlertServer: No remote Maintenance config found - using internal Maintenance
20140211 12:22:22 LicenseCheck: Starting License Check program
20140211 12:22:26 EventDaemon: Unable to connect to AlertServer - Retry in 10 seconds
20140211 12:22:26 UserConnection: Current Date = Tue Feb 11 12:22:26 GMT 2014
20140211 12:22:26 UserConnection: License Date = Thu Jan 01 23:59:59 GMT 2099
20140211 12:22:26 UserConnection: License expires at 2099/01/01 23:59:59
20140211 12:22:26 UserConnection: Full License count = 50
20140211 12:22:26 UserConnection: RO License count = 10
20140211 12:22:26 PPDbiInterface Launching PPDbiInterface version 3.5.0.2
20140211 12:22:26 PPDbiInterface DbiPort is 36000
20140211 12:22:26 PPDbiInterface Appending to 319187288
20140211 12:22:26 PPDbiInterface Dbi file age size is set to 2000
20140211 12:22:26 PPDbiInterface Dbi will check the EOF markers in work files
20140211 12:22:26 PPDbiInterface PPDbiInterfaceWriter thread started.
20140211 12:22:26 PPDbiInterface Connected to dbi at localhost, 36000
20140211 12:22:26 PPDbiInterface Changing file owner: null SUCCESS
20140211 12:22:26 PPDbiInterface PPDbiInterfaceQueue instance started.
20140211 12:22:26 PPDbiInterface DbiInterface startup completed.
20140211 12:22:26 PPDbiInterface isReady received [<A>Dbi is ready</A>]
20140211 12:22:27 AlertServer: Max alert set from PP table: 0006957587
20140211 12:22:27 Maintenance: Maintenance Server started
20140211 12:22:27 Maintenance: Waiting for initialisation...
20140211 12:22:27 MaintenanceReturns: Maintenance Return Connection Starting
20140211 12:22:27 AlertServer: No hothot config file.
20140211 12:22:27 AlertServer: Not using HotHot mode
20140211 12:22:27 LoginManager: LoginManager starting
20140211 12:22:27 Correlation: Correlation waiting for data...
20140211 12:22:28 Maintenance: Waiting for data load...
20140211 12:22:28 BES3Client: Supervisor assignees listed by user name
20140211 12:22:28 ServiceTrack: Added 1 tracking services
20140211 12:22:28 ServiceTrack: Added 21 non-tracking services
20140211 12:22:28 ServiceTrack: Added Holiday times
20140211 12:22:29 BES3Client: Correlation initialised
20140211 12:22:29 BES3Client: Starting Correlation
20140211 12:22:29 ServiceTrack: Added all Service details
20140211 12:22:29 ServiceTrack: Set ready
20140211 12:22:29 BES3Client: Token:_service already exists
20140211 12:22:29 BES3Client: Token:_impact already exists
20140211 12:22:29 BES3Client: Token:_group_name added
20140211 12:22:29 BES3Client: Token:_redundant already exists
20140211 12:22:29 BES3Client: Getting Service Structure from File
20140211 12:22:29 BES3Client: Finished getting Service Structure from File
20140211 12:22:29 BES3Client: Looking for Active Maintenance Records to load...
20140211 12:22:29 BES3Client: Active maintenance records loaded
20140211 12:22:30 ServiceUpdate: runSQLQueryInitial - 0 ImpactRules loaded
20140211 12:22:30 ServiceUpdate: Waiting for alerts to load
20140211 12:22:31 BES3Client: Waiting for ServiceUpdate to initialise
20140211 12:22:31 ServiceUpdate: Initialised
20140211 12:22:31 BES3Client: Resetting Service Alerts in database
20140211 12:22:31 BES3Client: Closed Service Alerts in PP_Alerts_Table
20140211 12:22:31 BES3Client: Starting load of active alerts...
20140211 12:22:33 BES3Client: Total alerts fetched = 1
20140211 12:22:33 BES3Client: Finished load of active alerts
20140211 12:22:33 BES3Client: Inform ServiceUpdate to check active alerts
20140211 12:22:33 ServiceUpdate: Getting all Service Messages ...
20140211 12:22:33 BES3Client: AlertServer initialised
20140211 12:22:33 ServiceUpdate: Getting all unavailable Serviced alerts
20140211 12:22:33 ServiceUpdate: Got all unavailable Serviced alerts
20140211 12:22:33 ServiceUpdate: Checking ServiceTrack has initialised
20140211 12:22:33 ServiceUpdate: Waiting for ServiceTrack to initialise
20140211 12:22:33 ServiceTrack: Initialised
20140211 12:22:33 Automation: Starting on 10.0.0.162 ...
20140211 12:22:33 Automation: Automation turned ON for standalone system
20140211 12:22:33 MonitorServer: MonitorServer starting - listening on port 30000
20140211 12:22:34 AlertServer: Stop sending to DBI
20140211 12:22:34 AlertServer: Start sending to DBI
20140211 12:22:34 AlertServer: Stop sending to DBI
20140211 12:22:34 AlertServer: Start sending to DBI
20140211 12:22:34 Automation: Found 3 groups
20140211 12:22:34 Automation: Started.
20140211 12:22:34 Automation: Turned OFF
20140211 12:22:34 Automation: Turned ON
20140211 12:22:34 Automation: Turned OFF
20140211 12:22:34 Automation: Turned ON
Up 0 rated Down
Mathew Allbright Feb 11, 2014 12:41PM UTC
Hi

Thanks for a quick response.

Here is what I can see when following point 1 above:

dvbesw02(ppadmin)289$ ppState AlertServer
Filter=AlertServer

BES State Table

Mon Name Type Processes
======= ==================== ========== ============================
20709 AlertServer Daemon 20713
======= ==================== ========== ============================[1]

dvbesw02(ppadmin)290$ ps -ef | grep 20713
ppadmin 20713 1 0 12:36:37 ? 0:08 ./java -Xmx1024m -Djava.net.preferIPv4Stack=true -Duser.language=en -Duser.regi
ppadmin 21066 15958 0 12:39:44 pts/2 0:00 grep 20713
dvbesw02(ppadmin)291$

I have recycled AlertServer and captured the POWERpack_Log entries for this as follows:

20140211 12:36:34 EventDaemon: ASConnection: Setting the EventDaemon Queue to not ready
20140211 12:36:34 EventDaemon: ASConnection disconnected...
20140211 12:36:34 EventDaemon: Closing ASConnection
20140211 12:36:34 EventDaemon: Unable to connect to AlertServer - Retry in 10 seconds
20140211 12:36:37 AlertServer: Query Port set to default 40000
20140211 12:36:37 AlertServer: Starting AlertServer version 3.5.5.127
20140211 12:36:37 AlertServer: Setting Database type to SYBASE
20140211 12:36:37 AlertServer: Setting host to dvbesw02
20140211 12:36:37 AlertServer: AlertServer TimeZone id:GB
20140211 12:36:37 AlertServer: AlertServer TimeZone offset:0
20140211 12:36:37 AlertServer: Testing database connection...
20140211 12:36:37 AlertServer: URL = jdbc:sybase:Tds:dvbesw02:5000
20140211 12:36:37 AlertServer: Database connection OK
20140211 12:36:37 AlertServer: Sending all alerts to Admin users turned off
20140211 12:36:37 LicenseCheck: Starting License Check program
20140211 12:36:38 UserConnection: Current Date = Tue Feb 11 12:36:38 GMT 2014
20140211 12:36:38 UserConnection: License Date = Thu Jan 01 23:59:59 GMT 2099
20140211 12:36:38 UserConnection: License expires at 2099/01/01 23:59:59
20140211 12:36:38 UserConnection: Full License count = 50
20140211 12:36:38 UserConnection: RO License count = 0
20140211 12:36:38 PPDbiInterface Launching PPDbiInterface version 3.5.0.2
20140211 12:36:38 PPDbiInterface DbiPort is 36000
20140211 12:36:38 PPDbiInterface Appending to 318782598
20140211 12:36:38 PPDbiInterface Dbi file age size is set to 2000
20140211 12:36:38 PPDbiInterface Dbi will check the EOF markers in work files
20140211 12:36:38 PPDbiInterface Connected to dbi at localhost, 36000
20140211 12:36:38 PPDbiInterface PPDbiInterfaceWriter thread started.
20140211 12:36:38 PPDbiInterface Changing file owner: null SUCCESS
20140211 12:36:38 PPDbiInterface PPDbiInterfaceQueue instance started.
20140211 12:36:38 PPDbiInterface DbiInterface startup completed.
20140211 12:36:38 PPDbiInterface isReady received [<A>Dbi is ready</A>]
20140211 12:36:38 AlertServer: Max alert set from PP table
20140211 12:36:38 Maintenance: Maintenance Server started
20140211 12:36:38 Maintenance: Waiting for initialisation...
20140211 12:36:38 AlertServer: No hothot config file.
20140211 12:36:38 AlertServer: Not using HotHot mode
20140211 12:36:38 LoginManager: LoginManager starting
20140211 12:36:38 Correlation: Correlation waiting for data...
20140211 12:36:38 BES3Client: No results from Supervisor assign query
20140211 12:36:38 BES3Client: Supervisor assignees listed by userid
20140211 12:36:38 BES3Client: No Correlation pathways found
20140211 12:36:38 BES3Client: No Correlation Master Recs found
20140211 12:36:38 BES3Client: No Correlation found
20140211 12:36:38 BES3Client: No Correlation Links found
20140211 12:36:38 BES3Client: Correlation initialised
20140211 12:36:38 BES3Client: Starting Correlation
20140211 12:36:38 BES3Client: Token:_service already exists
20140211 12:36:38 BES3Client: Token:_impact already exists
20140211 12:36:38 BES3Client: Token:_group_name added
20140211 12:36:38 BES3Client: Token:_redundant already exists
20140211 12:36:38 BES3Client: Getting Service Structure from File
20140211 12:36:38 BES3Client: Finished getting Service Structure from File
20140211 12:36:38 BES3Client: Looking for Active Maintenance Records to load...
20140211 12:36:38 BES3Client: Active maintenance records loaded
20140211 12:36:38 ServiceTrack: Added 1 tracking services
20140211 12:36:38 ServiceTrack: Added 21 non-tracking services
20140211 12:36:38 ServiceTrack: Added Holiday times
20140211 12:36:38 ServiceTrack: Added all Service details
20140211 12:36:38 ServiceTrack: Set ready
20140211 12:36:38 Maintenance: Waiting for data load...
20140211 12:36:40 ServiceUpdate: runSQLQueryInitial - no ImpactRules to load
20140211 12:36:40 BES3Client: Waiting for ServiceUpdate to initialise
20140211 12:36:40 ServiceUpdate: Waiting for alerts to load
20140211 12:36:41 ServiceUpdate: Initialised
20140211 12:36:41 BES3Client: Resetting Service Alerts in database
20140211 12:36:41 BES3Client: Closed Service Alerts in PP_Alerts_Table
20140211 12:36:41 BES3Client: Starting load of active alerts...
20140211 12:36:41 BES3Client: Total alerts fetched = 0
20140211 12:36:41 BES3Client: Finished load of active alerts
20140211 12:36:41 BES3Client: Inform ServiceUpdate to check active alerts
20140211 12:36:41 BES3Client: AlertServer initialised
20140211 12:36:41 Automation: Starting on 172.30.193.13 ...
20140211 12:36:41 Automation: Automation turned ON for standalone system
20140211 12:36:41 MonitorServer: MonitorServer starting - listening on port 30000
20140211 12:36:41 JavaServer: No denyaccess file - bypassing.
20140211 12:36:41 AlertServer: Stop sending to DBI
20140211 12:36:41 AlertServer: Start sending to DBI
20140211 12:36:41 Automation: Found 2 groups
20140211 12:36:41 Automation: Started.
20140211 12:36:41 Automation: Turned OFF
20140211 12:36:41 Automation: Turned ON
20140211 12:36:42 DotNetServer: No denyaccess file - bypassing.
20140211 12:36:42 ServiceUpdate: Getting all Service Messages ...
20140211 12:36:42 ServiceUpdate: Getting all unavailable Serviced alerts
20140211 12:36:42 ServiceUpdate: Got all unavailable Serviced alerts
20140211 12:36:42 ServiceUpdate: Checking ServiceTrack has initialised
20140211 12:36:42 AlertServer: Stop sending to DBI
20140211 12:36:42 ServiceUpdate: Waiting for ServiceTrack to initialise
20140211 12:36:42 ServiceTrack: Initialised
20140211 12:36:42 AlertServer: Start sending to DBI
20140211 12:36:42 Automation: Turned OFF
20140211 12:36:42 Automation: Turned ON
20140211 12:36:44 EventDaemon: ASConnection: Clearing the EventDaemon Queue
20140211 12:36:44 MonitorConnections: New connection: EventDaemon
20140211 12:36:46 DotNetServer: IP address:10.200.50.185 is not blocked
20140211 12:36:46 DotNetServer: IP address:10.200.35.56 is not blocked
20140211 12:36:47 AlertServer: User name: ppadmin@GuestGroup is an Admin user
20140211 12:36:47 AlertServer: Group:GuestGroup User:ppadmin
20140211 12:36:47 AlertServer: Using server time for alerts
20140211 12:36:47 AlertServer: User name: ppadmin@GuestGroup is an Admin user
20140211 12:36:47 AlertServer: Cannot read response.cfg file
20140211 12:36:47 AlertServer: SendWebMessage starting for ppadmin(10.200.35.56:0.0) connection type DotNet
20140211 12:36:47 AlertServer: Group:GuestGroup User:ppadmin
20140211 12:36:47 AlertServer: Using server time for alerts
20140211 12:36:47 AlertServer: Cannot read response.cfg file
20140211 12:36:47 AlertServer: SendWebMessage starting for ppadmin(10.200.50.185:0.0) connection type DotNet
20140211 12:36:48 LoginAssistant: Started with 2 connections
20140211 12:36:48 LoginManager: Users added in pre-processing:2
20140211 12:36:48 LoginAssistant: LoginAssistant Completed successfully
20140211 12:36:48 AlertServer: DotNet Connection ready to send for user:ppadmin
20140211 12:36:48 AlertServer: DotNet Sending remaining messages
20140211 12:36:48 AlertServer: DotNet Sent all login messages
20140211 12:36:48 AlertServer: DotNet Messages sent:29
20140211 12:36:48 AlertServer: DotNet Connection ready user:ppadmin
20140211 12:36:48 AlertServer: SendWebMessage normal running for ppadmin(10.200.35.56:0.0) connection type DotNet
20140211 12:36:48 AlertServer: DotNet Connection ready to send for user:ppadmin
20140211 12:36:48 AlertServer: DotNet Sending remaining messages
20140211 12:36:48 AlertServer: DotNet Sent all login messages
20140211 12:36:48 AlertServer: DotNet Messages sent:29
20140211 12:36:48 AlertServer: DotNet Connection ready user:ppadmin
20140211 12:36:48 AlertServer: SendWebMessage normal running for ppadmin(10.200.50.185:0.0) connection type DotNet
20140211 12:37:14 ServiceUpdate: Services Changed due to events = 20
20140211 12:37:42 LicenseCheck: Days left in license = 31005
20140211 12:37:42 AlertServer: Information:License file check OK

Here is the Dbi_Log entry during and after recycle of Alert Server:

20140211 12:36:38 AServer: New socket connection received
20140211 12:36:38 AServer: Waiting for input
20140211 12:36:38 AServer: Received 'Is Ready' query from AlertServer
20140211 12:36:38 AServer: Replied 'Is Ready' to AlertServer
20140211 12:36:43 HandleFlow(DbiJM Thd1): TN message number of tokens = 60
20140211 12:37:00 DbiJM: ===================== DbiJM check ======================
20140211 12:37:00 DbiJM: Queue 1 : 0 entries
20140211 12:37:00 DbiJM: Thread 1: Messages Processed = 2 Database Errors = 0
20140211 12:37:00 DbiJM: Queue 2 : 0 entries
20140211 12:37:00 DbiJM: Thread 2: Messages Processed = 0 Database Errors = 0
20140211 12:37:00 DbiJM: Queue 3 : 0 entries
20140211 12:37:00 DbiJM: Thread 3: Messages Processed = 0 Database Errors = 0
20140211 12:37:00 DbiJM: ===================== DbiJM check ======================
20140211 12:38:23 WorkFileServer: Work file not changed - checking
20140211 12:38:23 WorkFileServer: Next file - no more files in list
20140211 12:38:23 WorkFileServer: Check OK - No newer work files available

Any ideas?

Regards
Up -1 rated Down
Colin Griffiths Feb 13, 2014 10:56AM UTC Interlink Software Agent
Hi Mathew, Everything looks normal! Are you still getting these?

20140211 11:42:47 POWERpackTrans:(System) Alert Server Connection failed(145 Connection timed out) -1
20140211 11:42:47 POWERpackTrans:(ISS) Alert Server Connection failed(145 Connection timed out) -1
20140211 11:42:52 POWERpackTrans:(System) Establishing Connection to Alert Server Socket 30000
20140211 11:42:52 POWERpackTrans:(ISS) Establishing Connection to Alert Server Socket 30000

Could you supply the full POWERpack_Log (zipped) following a ppServer start - say after 20 minutes or so.
Up 0 rated Down
David Harwood Feb 19, 2014 02:30PM UTC Interlink Software Agent
Hi Mathew,

Are you still experiencing issues with the AlertServer? Can I resolve this case?

Regards,
David
Up 1 rated Down
Mathew Allbright Feb 21, 2014 08:36AM UTC
Hi,

This is the first of the 5 servers we have installed Sybase and BES and are now in the process of configuring accordingly.

We have one message channel configured (SCOM) and all appears to be OK and seem to be no longer seeing the following in the POWERpack log:

POWERpackTrans:(System) Alert Server Connection failed(145 Connection timed out) -1
POWERpackTrans:(ISS) Alert Server Connection failed(145 Connection timed out) -1
POWERpackTrans:(System) Establishing Connection to Alert Server Socket 30000
POWERpackTrans:(ISS) Establishing Connection to Alert Server Socket 30000

Perhaps this was happening because AlertServer had nothing to do / process.

Thanks for your continued support.

Regards

This question has received the maximum number of answers.

Contact Us

desk.com@interlinksoftware.com
https://cdn.desk.com/
false
desk
Loading
seconds ago
a minute ago
minutes ago
an hour ago
hours ago
a day ago
days ago
about
false
Invalid characters found
/customer/en/portal/articles/autocomplete