Quantcast
Channel: SCN: Message List - SAP Adaptive Server Enterprise (SAP ASE) for Custom Applications
Viewing all articles
Browse latest Browse all 3587

ASE Cockpit Problems on Linux

$
0
0

Anyone out there able to start ASE Cockpit using:

 

Adaptive Server Enterprise/16.0 SP02 GA/EBF 24951 SMP/P/x86_64/Enterprise Linux/asecorona/2424/64-bit/FBO/Tue Aug 11 05:28:54 2015

 

I can't get an instance started, getting this (partial) output in the agent.log

 

2015-09-30 17:39:16,043 [INFO ] [repository.RepositoryService                 ] [main] - Starting repository database repository
2015-09-30 17:39:18,367 [INFO ] [upgrade.UpgradeManager                       ] [main] - Checking if repository upgrade is required.
2015-09-30 17:39:18,447 [INFO ] [upgrade.UpgradeManager                       ] [main] - Cockpit Version: 4.0.10.5826.
2015-09-30 17:39:18,447 [INFO ] [upgrade.UpgradeManager                       ] [main] - Repository Version: 4.0.10.5826
2015-09-30 17:39:18,448 [INFO ] [repository.Repository                        ] [main] - Repository upgrade is not required.
2015-09-30 17:39:23,878 [INFO ] [messaging.MessagingService                   ] [main] - Starting Messaging Service...
2015-09-30 17:39:23,878 [INFO ] [messaging.MessagingService                   ] [main] - About to start the queueing system.
2015-09-30 17:39:23,878 [INFO ] [messaging.MessagingService                   ] [main] - Checking for which provider to use.
2015-09-30 17:39:24,573 [WARN ] [activemq.ActiveMQMessagingProvider           ] [main] - Adjusting messaging provider Main:temp spac
e usage to 75% of available space on /opt/ase160_sp02/COCKPIT-4/services/Messaging/activemq-data/COCKPIT-4993/tmp_storage partition
(15801 MB).
2015-09-30 17:39:24,574 [WARN ] [activemq.ActiveMQMessagingProvider           ] [main] - Adjusting messaging provider Main:store spa
ce usage to 75% of available space on /opt/ase160_sp02/COCKPIT-4/services/Messaging/activemq-data partition (15801 MB).
2015-09-30 17:39:27,241 [INFO ] [messaging.MessagingService                   ] [main] - Queueing system has been started.
2015-09-30 17:39:27,269 [INFO ] [alert.AlertService                           ] [main] - Starting Alert Service...
2015-09-30 17:39:27,269 [INFO ] [alert.AlertService                           ] [main] - AlertService cannonical name AgentService:n
ame=AlertService
2015-09-30 17:39:27,316 [INFO ] [alert.AlertService                           ] [main] - Loading Alert Server Configuration.
2015-09-30 17:39:27,336 [INFO ] [alert.AlertService                           ] [main] - Starting message senders.
2015-09-30 17:39:27,574 [ERROR] [alert.AlertService                           ] [main] - Failed to start MessageSender: Failed to ac
quire JMS Session
2015-09-30 17:39:27,574 [ERROR] [alert.AlertService                           ] [main] - com.sybase.ua.service.AgentServiceException
: Failed to start MessageSender. com.sybase.alert.message.api.ConnectionException: Failed to acquire JMS Session
2015-09-30 17:39:27,576 [ERROR] [services.Agent                               ] [main] - Failed to successfully start agent: Failed
to start AlertService. Failed to start MessageSender. com.sybase.alert.message.api.ConnectionException: Failed to acquire JMS Sessio
n com.sybase.ua.service.AgentServiceException: Failed to start MessageSender. com.sybase.alert.message.api.ConnectionException: Fail
ed to acquire JMS Session
com.sybase.ua.service.AgentServiceException: Failed to start AlertService. Failed to start MessageSender. com.sybase.alert.message.a
pi.ConnectionException: Failed to acquire JMS Session com.sybase.ua.service.AgentServiceException: Failed to start MessageSender. co
m.sybase.alert.message.api.ConnectionException: Failed to acquire JMS Session        at com.sybase.ua.services.AgentLifecycleManager.startService(Unknown Source)        at com.sybase.ua.services.AgentLifecycleManager.startServices(Unknown Source)        at com.sybase.ua.services.AgentLifecycleManager.startAgent(Unknown Source)        at com.sybase.ua.services.Agent.doStart(Unknown Source)        at com.sybase.ua.service.AgentServiceBase.start(Unknown Source)        at com.sybase.ua.services.Agent.startAgent(Unknown Source)        at com.sybase.ua.startup.Main.startAgent(Unknown Source)        at com.sybase.ua.startup.Main.start(Unknown Source)        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)        at java.lang.reflect.Method.invoke(Method.java:606)        at com.sybase.ua.startup.Startup.doLoadMainClass(Unknown Source)        at com.sybase.ua.startup.Startup.start(Unknown Source)        at com.sybase.ua.startup.Startup.main(Unknown Source)
Caused by: com.sybase.ua.service.AgentServiceException: Failed to start MessageSender. com.sybase.alert.message.api.ConnectionExcept
ion: Failed to acquire JMS Session        at com.sybase.ua.services.alert.AlertService.doRunning(Unknown Source)        at com.sybase.ua.services.alert.AlertService.doStart(Unknown Source)        at com.sybase.ua.service.AgentServiceBase.start(Unknown Source)        ... 15 more

Viewing all articles
Browse latest Browse all 3587

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>