Server Health

Good day , 
Running Get-ServerHealth on Exchange 2013 Version 15.0 (Build 775.38) mailbox server show the following "Unhealthy" healthsets 
Name AlertValue 
MaintenanceFailureMonitor.FEP Unhealthy 
OutlookRpcDeepTestMonitor Unhealthy 
MicrosoftFailedUpdatesMonitor Unhealthy 
OutlookRpcSelfTestMonitor Unhealthy 
I've tried tracing the source and searching the internet with no luck ! 
any idea ? 
regards 
Best Regards Bisher Shbib

Seems to be everything back to its first status, actually there is only one new UnHealthy HealthSet which is "ECP"
this is the health report for all server 
Server State HealthSet AlertValue LastTransitionTime MonitorCount
CAS01 NotApplicable ECP Unhealthy 6/17/2014 9:36:00 AM 1
CAS01 NotApplicable FEP Unhealthy 6/17/2014 9:31:31 AM 1
CAS01 NotApplicable Network Unhealthy 6/17/2014 4:11:47 AM 2
Server State HealthSet AlertValue LastTransitionTime MonitorCount
CAS03 NotApplicable FEP Unhealthy 6/17/2014 9:31:50 AM 1
CAS03 NotApplicable Network Unhealthy 6/16/2014 9:19:05 AM 2
Server State HealthSet AlertValue LastTransitionTime MonitorCount
CAS02 NotApplicable ECP Unhealthy 6/17/2014 9:31:48 AM 1
CAS02 NotApplicable FEP Unhealthy 6/17/2014 9:32:28 AM 1
CAS02 NotApplicable Network Unhealthy 6/17/2014 4:25:09 AM 2
Server State HealthSet AlertValue LastTransitionTime MonitorCount
MBX01 NotApplicable FIPS Unhealthy 6/17/2014 10:42:53 PM 28
MBX01 NotApplicable FEP Unhealthy 6/17/2014 9:34:14 AM 1
MBX01 NotApplicable MailboxSpace Repairing 6/17/2014 9:39:04 AM 35
MBX01 NotApplicable Outlook.Protocol Unhealthy 6/17/2014 9:30:46 AM 11Server         State         HealthSet        AlertValue LastTransitionTime   MonitorCount
MBX02 NotApplicable FEP              Unhealthy   6/17/2014 9:31:31 AM 1
MBX02 NotApplicable MailboxSpace     Repairing   6/17/2014 9:38:53 AM 35
MBX02 NotApplicable Outlook.Protocol Unhealthy   6/17/2014 9:29:31 AM 11
I think the most important one is Outlook.Protocol HealthSet , Other HealthSets can be ignored or overried
Any thoughts ?
Best Regards Bisher Shbib

Similar Messages

  • Manages Exchange server health Service is NOT starting after installing EDGE role using Exchange2013 SP1+CU5 setup

    I used Exchange 2013 SP1+CU5 to install Edge role on Windows server 2012 R2 workgroup machine
    then after installation the service "Exchange server health Service" was not starting automatically or manually with the following error "Error 1075: The dependency service does not exist or has been marked for deletion"
    and in the Event Viewer I have this error:
    Event Id: 7003
    The Microsoft Exchange Health Manager service depends on the following service: MSExchangeADTopology. This service might not be installed.
    please advice

    The Exchange 2013 Edge Role has a reduced set of services compare to a CAS or MBX server role:
    Active Directory Web Services
    Microsoft Exchange ADAM
    Microsoft Exchange Anti-spam Update
    Microsoft Exchange Diagnostics
    Microsoft Exchange Credential Service
    Microsoft Exchange Health Manager
    Microsoft Exchange Service Host
    Microsoft Exchange Transport
    Microsoft Exchange Transport Log Search
    The above one was from Exchange 2013 Sp1. Not sure whether Microsoft Exchange Health Manager service has been replaced from CU5.
    Just restart the edge server once again and ensure that you are able to see this service again in services console.
    Remember to mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you Check out my latest blog posts on http://exchangequery.com

  • Weblogic 11g Admin console - Admin Server Health shows "Warning"

    Hi,
    My env details : db 11.1.0.7, wls1033, RCU 11.1.1.3, soa 11.1.1.3, AIA11gR1 PS2
    When I start only Admin server, Health shows "Ok" but when I start soa_server1, Admin Server Health becomes "Warning".
    When I checked "Health information details" for Admin server, threadpool subsystem is showing "Warning".
    Steps I tried to resolve this issue : increased "Stuck Thread Max Time" to "1200" and "Stuck Thread Timer Interval" to "120" and restarted server, but still it shows "Warning" for Admin server Health
    Once I start soa_server1, Admin Server log shows below trace
    <Sep 30, 2010 3:39:38 PM IST> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
    <Sep 30, 2010 5:17:34 PM IST> <Error> <org.apache.beehive.netui.pageflow.internal.AdapterManager> <BEA-000000> <ServletContainerAdapter manager not initialized correctly.>
    <Sep 30, 2010 5:21:34 PM IST> <Warning> <netuix> <BEA-423420> <Redirect is executed in begin or refresh action. Redirect url is /console/console.portal?_nfpb=true&_pageLabel=WLSServerControlTablePage.>
    <Sep 30, 2010 5:41:37 PM IST> <Error> <WebLogicServer> <BEA-000337> <[STUCK] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)' has been busy for "1,203" seconds working on the request "weblogic.kernel.WorkManagerWrapper$1@dbf6176", which is more than the configured time (StuckThreadMaxTime) of "1,200" seconds. Stack trace:
    Thread-21 "[STUCK] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'" <alive, in native, suspended, priority=1, DAEMON> {
    jrockit.net.SocketNativeIO.readBytesPinned(SocketNativeIO.java:???)
    jrockit.net.SocketNativeIO.socketRead(SocketNativeIO.java:24)
    java.net.SocketInputStream.socketRead0(SocketInputStream.java:???)
    java.net.SocketInputStream.read(SocketInputStream.java:107)
    sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:250)
    sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:289)
    sun.nio.cs.StreamDecoder.read(StreamDecoder.java:125)
    ^-- Holding lock: java.io.InputStreamReader@dbf1cdd[thin lock]
    java.io.InputStreamReader.read(InputStreamReader.java:167)
    java.io.BufferedReader.fill(BufferedReader.java:105)
    java.io.BufferedReader.readLine(BufferedReader.java:288)
    ^-- Holding lock: java.io.InputStreamReader@dbf1cdd[thin lock]
    java.io.BufferedReader.readLine(BufferedReader.java:362)
    weblogic.nodemanager.client.NMServerClient.checkResponse(NMServerClient.java:287)
    weblogic.nodemanager.client.NMServerClient.checkResponse(NMServerClient.java:312)
    weblogic.nodemanager.client.NMServerClient.start(NMServerClient.java:93)
    ^-- Holding lock: weblogic.nodemanager.client.PlainClient@dbf5115[thin lock]
    weblogic.nodemanager.mbean.StartRequest.start(StartRequest.java:75)
    weblogic.nodemanager.mbean.StartRequest.execute(StartRequest.java:45)
    weblogic.kernel.WorkManagerWrapper$1.run(WorkManagerWrapper.java:63)
    weblogic.work.ExecuteThread.execute(ExecuteThread.java:198)
    weblogic.work.ExecuteThread.run(ExecuteThread.java:165)
    >
    <Sep 30, 2010 5:41:37 PM IST> <Notice> <Diagnostics> <BEA-320068> <Watch 'StuckThread' with severity 'Notice' on server 'AdminServer' has triggered at Sep 30, 2010 5:41:37 PM IST. Notification details:
    WatchRuleType: Log
    WatchRule: (SEVERITY = 'Error') AND (MSGID = 'BEA-000337')
    WatchData: DATE = Sep 30, 2010 5:41:37 PM IST SERVER = AdminServer MESSAGE = [STUCK] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)' has been busy for "1,203" seconds working on the request "weblogic.kernel.WorkManagerWrapper$1@dbf6176", which is more than the configured time (StuckThreadMaxTime) of "1,200" seconds. Stack trace:
    Thread-21 "[STUCK] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'" <alive, in native, suspended, priority=1, DAEMON> {
    jrockit.net.SocketNativeIO.readBytesPinned(SocketNativeIO.java:???)
    jrockit.net.SocketNativeIO.socketRead(SocketNativeIO.java:24)
    java.net.SocketInputStream.socketRead0(SocketInputStream.java:???)
    java.net.SocketInputStream.read(SocketInputStream.java:107)
    sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:250)
    sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:289)
    sun.nio.cs.StreamDecoder.read(StreamDecoder.java:125)
    ^-- Holding lock: java.io.InputStreamReader@dbf1cdd[thin lock]
    java.io.InputStreamReader.read(InputStreamReader.java:167)
    java.io.BufferedReader.fill(BufferedReader.java:105)
    java.io.BufferedReader.readLine(BufferedReader.java:288)
    ^-- Holding lock: java.io.InputStreamReader@dbf1cdd[thin lock]
    java.io.BufferedReader.readLine(BufferedReader.java:362)
    weblogic.nodemanager.client.NMServerClient.checkResponse(NMServerClient.java:287)
    weblogic.nodemanager.client.NMServerClient.checkResponse(NMServerClient.java:312)
    weblogic.nodemanager.client.NMServerClient.start(NMServerClient.java:93)
    ^-- Holding lock: weblogic.nodemanager.client.PlainClient@dbf5115[thin lock]
    weblogic.nodemanager.mbean.StartRequest.start(StartRequest.java:75)
    weblogic.nodemanager.mbean.StartRequest.execute(StartRequest.java:45)
    weblogic.kernel.WorkManagerWrapper$1.run(WorkManagerWrapper.java:63)
    weblogic.work.ExecuteThread.execute(ExecuteThread.java:198)
    weblogic.work.ExecuteThread.run(ExecuteThread.java:165)
    SUBSYSTEM = WebLogicServer USERID = <WLS Kernel> SEVERITY = Error THREAD = [ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)' MSGID = BEA-000337 MACHINE = navistarlnx01.in.corp.sa TXID = CONTEXTID = a29dda85e23940b7:-4a5394b7:12b621e55e6:-8000-000000000000005d TIMESTAMP = 1285848697597
    WatchAlarmType: AutomaticReset
    WatchAlarmResetPeriod: 600000
    >
    <Sep 30, 2010 5:41:55 PM IST> <Alert> <Diagnostics> <BEA-320016> <Creating diagnostic image in /u01/app/ora11g/Oracle/Middleware/user_projects/domains/base_domain/servers/AdminServer/adr/diag/ofm/base_domain/AdminServer/incident/incdir_10 with a lockout minute period of 1.>
    <Sep 30, 2010 5:43:37 PM IST> <Error> <WebLogicServer> <BEA-000337> <[STUCK] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)' has been busy for "1,323" seconds working on the request "weblogic.kernel.WorkManagerWrapper$1@dbf6176", which is more than the configured time (StuckThreadMaxTime) of "1,200" seconds. Stack trace:
    Thread-21 "[STUCK] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'" <alive, in native, suspended, priority=1, DAEMON> {
    jrockit.net.SocketNativeIO.readBytesPinned(SocketNativeIO.java:???)
    jrockit.net.SocketNativeIO.socketRead(SocketNativeIO.java:24)
    java.net.SocketInputStream.socketRead0(SocketInputStream.java:???)
    java.net.SocketInputStream.read(SocketInputStream.java:107)
    sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:250)
    sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:289)
    sun.nio.cs.StreamDecoder.read(StreamDecoder.java:125)
    ^-- Holding lock: java.io.InputStreamReader@dbf1cdd[thin lock]
    java.io.InputStreamReader.read(InputStreamReader.java:167)
    java.io.BufferedReader.fill(BufferedReader.java:105)
    java.io.BufferedReader.readLine(BufferedReader.java:288)
    ^-- Holding lock: java.io.InputStreamReader@dbf1cdd[thin lock]
    java.io.BufferedReader.readLine(BufferedReader.java:362)
    weblogic.nodemanager.client.NMServerClient.checkResponse(NMServerClient.java:287)
    weblogic.nodemanager.client.NMServerClient.checkResponse(NMServerClient.java:312)
    weblogic.nodemanager.client.NMServerClient.start(NMServerClient.java:93)
    ^-- Holding lock: weblogic.nodemanager.client.PlainClient@dbf5115[thin lock]
    weblogic.nodemanager.mbean.StartRequest.start(StartRequest.java:75)
    weblogic.nodemanager.mbean.StartRequest.execute(StartRequest.java:45)
    weblogic.kernel.WorkManagerWrapper$1.run(WorkManagerWrapper.java:63)
    weblogic.work.ExecuteThread.execute(ExecuteThread.java:198)
    weblogic.work.ExecuteThread.run(ExecuteThread.java:165)
    Thx for your help.

    Is there any information on this StuckThread Issue ?
    It happens in every restart of the SOA Managed server.

  • Server Health Checkup

    Hi Gurus,
    Can any give tell me what is performance tunning in SAP and What are the major steps involved in a Server Health checkup for SAP servers which has more than 2000 users.
    Regards,
    Pradeep

    u can also try this tcodes
    Server Status                            SM51
    Process Overview                            SM50
    System Log                                                  SM21
    Dump(s) Abap/4                             ST22
    Update                                                   SM13
    Lock Entries                                                   SM12
    SAP Spool                                                    SP01
    TEMSE Administration                               SP12
    SAP Jobs (TMS and SAP*)                          SM37
    Client Overview                                SCC4
    Database Performance                                DB02
    DBA Planning Calendar                                DB13
    Database Archlog  Backup                           DB12
    SAP Buffers                                                     ST02
    Operating System Monitor                                ST06
    Database Performance Monitor           ST04
    you can do this daily or weekly
    Regards
    walata

  • OSB SB Console - Operations Dashboard /Monitoring/Dashboard/Server Health - Purge Alerts/Errors

    OSB SB Console - Operations Dashboard /Monitoring/Dashboard/Server Health
    has lots of errors/alerts/warnings that have not been purged. I don't see any provision to purge these alerts/messages ?
    1> How do I Purge these alerts/errors/messages
    2> How do I configure these
    Thank you!

    Hi,
    Go to operation, Pipeline Alerts (or SLA alerts depending on type). On the right site click on the Extended Alert History.
    In this page that follows you can click on the "Purge Alert History" link to purge all messages.
    For auto purging you can follow the steps below:
    Go in the Administration Console to Diagnostics -> Archives
    Then, for each OSB server add a Data Retirement Policy
    Choose a Custom Archive, and its name is the well known “CUSTOM/com.bea.wli.monitoring.pipeline.alert”.
    You can retirement age (in hours) for example 336 (14 days) and the interval of purging for example every 24 hours (retirement period) at 00:00 (retirement time = 0).
    Cheers,
    Robert van Mölken
    Oracle Integration Specialist

  • WEBLOGIC MANGED SERVER HEALTH STATE IS UNKNOWN

    Dear Team,
    I am working as support engineer in a production environment.
    I am facing some issue described below:
    1. One of Weblogic managed server health state is WARNING. I have checked in managed server log and found below error:
        <Jun 22, 2014 5:13:37 AM IST> <Error> <WebLogicServer> <BEA-000337> <[STUCK] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)' has been busy for "7,222" seconds working on the request "Workmanager: nlsi/wm/MarshallerWorkManager, Version: 0, Scheduled=true, Started=true, Started time: 7222299 ms
    ", which is more than the configured time (StuckThreadMaxTime) of "7,200" seconds. Stack trace:
    As the Health is in warning state managed server become fully unresponsive.
    Now I have following query:
    1. What is the risk if managed server health state is WARNING?
    2. Is Stuck thread will make the server go into an Unknown state?
    3. If managed server state in UNKNOWN then what is the risk?
    3. Could you please provide any solution so that in future we should not face this WARNING health state.
    4. Could you please investigate why this health state WARNING occur?
    Please help me.
    Regards,
    Maity

    Dear Team,
    I am working as support engineer in a production environment.
    I am facing some issue described below:
    1. One of Weblogic managed server health state is WARNING. I have checked in managed server log and found below error:
        <Jun 22, 2014 5:13:37 AM IST> <Error> <WebLogicServer> <BEA-000337> <[STUCK] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)' has been busy for "7,222" seconds working on the request "Workmanager: nlsi/wm/MarshallerWorkManager, Version: 0, Scheduled=true, Started=true, Started time: 7222299 ms
    ", which is more than the configured time (StuckThreadMaxTime) of "7,200" seconds. Stack trace:
    As the Health is in warning state managed server become fully unresponsive.
    Now I have following query:
    1. What is the risk if managed server health state is WARNING?
    2. Is Stuck thread will make the server go into an Unknown state?
    3. If managed server state in UNKNOWN then what is the risk?
    3. Could you please provide any solution so that in future we should not face this WARNING health state.
    4. Could you please investigate why this health state WARNING occur?
    Please help me.
    Regards,
    Maity

  • Managed Server Health Issue

    I have a warning on a fairly new managed server under health status...error is 'threadpool has stuck threads'. WHen I dump the thread stack I find this section. Any ideas?
    "[STUCK] ExecuteThread: '25' for queue: 'weblogic.kernel.Default (self-tuning)'" id=1691 idx=0x328 tid=3904 prio=1 alive, in native, daemon
    at jrockit/net/SocketNativeIO.readBytesPinned(Ljava/io/FileDescriptor;[BIII)I(Native Method)
                    at jrockit/net/SocketNativeIO.socketRead(SocketNativeIO.java:46)[optimized]
    at java/net/SocketInputStream.socketRead0(Ljava/io/FileDescriptor;[BIII)I(SocketInputStream.java)[inlined]
    at java/net/SocketInputStream.read(SocketInputStream.java:129)[optimized]
    at weblogic/jdbc/db2/drda/DRDAByteOrderedDataReader.receive()V(Unknown Source)
    at weblogic/jdbc/db2/drda/DRDARequest.submitRequest()V(Unknown Source)[inlined]
    at weblogic/jdbc/db2/DB2ImplResultSet.close()V(Unknown Source)[optimized]
    at weblogic/jdbc/db2/DB2ImplStatement.close()V(Unknown Source)[optimized]
    at weblogic/jdbc/db2/DB2ImplStatement.getAutoGeneratedKeyResultSet()Lweblogic/jdbc/db2base/BaseImplResultSet;(Unknown Source)
    at weblogic/jdbc/db2base/BaseStatement.getGeneratedKeys()Ljava/sql/ResultSet;(Unknown Source)
    at weblogic/jdbc/wrapper/PreparedStatement_weblogic_jdbc_db2base_BasePreparedStatement40.getGeneratedKeys()Ljava/sql/ResultSet;(Unknown Source)
    at sun/reflect/GeneratedMethodAccessor1009.invoke(Ljava/lang/Object;[Ljava/lang/Object;)Ljava/lang/Object;(Unknown Source)
                    at sun/reflect/DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)[optimized]
    at java/lang/reflect/Method.invoke(Method.java:597)[optimized]
    at org/hibernate/util/GetGeneratedKeysHelper.getGeneratedKey(GetGeneratedKeysHelper.java:59)
    at org/hibernate/persister/entity/BasicEntityPersister.insert(BasicEntityPersister.java:1761)
    at org/hibernate/persister/entity/BasicEntityPersister.insert(BasicEntityPersister.java:2178)
    at org/hibernate/action/EntityIdentityInsertAction.execute(EntityIdentityInsertAction.java:34)
    at org/hibernate/engine/ActionQueue.execute(ActionQueue.java:239)
    at org/hibernate/event/def/AbstractSaveEventListener.performSaveOrReplicate(AbstractSaveEventListener.java:240)
    at org/hibernate/event/def/AbstractSaveEventListener.performSave(AbstractSaveEventListener.java:160)
    at org/hibernate/event/def/AbstractSaveEventListener.saveWithGeneratedId(AbstractSaveEventListener.java:95)
    at org/hibernate/event/def/DefaultSaveOrUpdateEventListener.saveWithGeneratedOrRequestedId(DefaultSaveOrUpdateEventListener.java:184)
    at org/hibernate/event/def/DefaultSaveEventListener.saveWithGeneratedOrRequestedId(DefaultSaveEventListener.java:33)
    at org/hibernate/event/def/DefaultSaveOrUpdateEventListener.entityIsTransient(DefaultSaveOrUpdateEventListener.java:173)
    at org/hibernate/event/def/DefaultSaveEventListener.performSaveOrUpdate(DefaultSaveEventListener.java:27)
    at org/hibernate/event/def/DefaultSaveOrUpdateEventListener.onSaveOrUpdate(DefaultSaveOrUpdateEventListener.java:69)
    at org/hibernate/impl/SessionImpl.save(SessionImpl.java:481)
    at org/hibernate/impl/SessionImpl.save(SessionImpl.java:476)
    at com/fc/hibernate/DataContext.sessionSave(DataContext.java:71)
    at com/fc/commandnet/fdm/SubmitDocumentAction.onSave(SubmitDocumentAction.java:111)
    at com/fc/commandnet/fdm/FdmBaseAction.execute(FdmBaseAction.java:118)
    at org/apache/struts/action/RequestProcessor.processActionPerform(RequestProcessor.java:484)
    at org/apache/struts/action/RequestProcessor.process(RequestProcessor.java:274)
    at org/apache/struts/action/ActionServlet.process(ActionServlet.java:1482)
    at org/apache/struts/action/ActionServlet.doPost(ActionServlet.java:525)
    at javax/servlet/http/HttpServlet.service(HttpServlet.java:727)
    at javax/servlet/http/HttpServlet.service(HttpServlet.java:820)
    at weblogic/servlet/internal/StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
    at weblogic/servlet/internal/StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
    at weblogic/servlet/internal/ServletStubImpl.execute(ServletStubImpl.java:292)
    at weblogic/servlet/internal/ServletStubImpl.execute(ServletStubImpl.java:175)
    at weblogic/servlet/internal/WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3594)
    at weblogic/security/acl/internal/AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)[inlined]
    at weblogic/security/service/SecurityManager.runAs(SecurityManager.java:121)[optimized]
    at weblogic/servlet/internal/WebAppServletContext.securedExecute(WebAppServletContext.java:2202)
    at weblogic/servlet/internal/WebAppServletContext.execute(WebAppServletContext.java:2108)
    at weblogic/servlet/internal/ServletRequestImpl.run(ServletRequestImpl.java:1432)[optimized]
    at weblogic/work/ExecuteThread.execute(ExecuteThread.java:201)[inlined]
    at weblogic/work/ExecuteThread.run(ExecuteThread.java:173)[optimized]
    at jrockit/vm/RNI.c2java(JJJJJ)V(Native Method)
    -- end of trace

    And also the admin shows Health status of others OK very slowly it may take more than 30mins for all servers(13) to show the Heath state as OK untill then it shows Not reachable..

  • Get server health via SNMP get

    Hello,
    is it possible to get the health of a server (or deployment) in weblogic using snmpget?
    All documentation and examples I found so far assume that a use traps.
    I tried to walk over the bea tree once when a specific server is stopped and once when it is startet. But the only difference i found where some counters which have increased in the meantime.
    Thanks in advance for your help.

    There is no SNMP message that can be used to define a upper threshold for the connections that can be used to check the connection status. You can use a script that can automatically login and check the connections on your device or you can use some network management software for this.

  • Monitoring Sun Ray Server health

    I am interested in deploying Sun Ray Server as a component of a large VDI implementation. I want to be able to monitor the health of the Sun Ray Server software beyond the standard OS level stuff - number of concurrent Sun Ray Client connections for example. Is there an API (or some other mechanism) available for me to create an agent that can be monitored with standard monitoring software? Thanks!

    Thanks for the info, however, I'm not looking for monitoring software - my organization already uses the IBM Tivoli suite quite successfully. I'm interested in more info on the specific Sun Ray APIs available to me to mine some health data. Thanks.

  • Oracle listener port - server health monitoring

    I want to use Intermapper to monitor the health of my Oracle server. Which port should I have Intermapper watching? How do you monitor the health of your server?
    Thanks.

    Does Interapper have some guidance? If you're using the default listener port of 1521, you may be able to verify that the listener is up, but that doesn't mean that the database is up or accepting connections. Without actually logging in, I'm not sure what sort of monitoring you'd actually get...
    Justin
    Distributed Database Consulting, Inc.
    http://www.ddbcinc.com/askDDBC

  • Problem getting server health through WLST

    I wrote a WLST script to get the state and health of the servers in a domain. The script works properly but the information retrieved for the health of the servers is not accurate. When the health reported in the administration console changes to "Overloaded" or "Warning", the health retrieved through WLST is still "HEALTH_OK".
    I am using the getHealthState() method on the ServerRuntimeMBean to find the health of the servers.
    How can get via WLST the same information I see in the admin console?

    Yes, right , should be ServerRuntimeMBean not ServerLifeCycleRuntimeMBean .
    if you got chance have a look the Mbean reference http://download.oracle.com/docs/cd/E15523_01/apirefs.1111/e13951/core/index.html , you will found there is no other mbean to get server healthstatus, I sure admin console using same mbean .
    Your code looks fine to me , but I would suggest using different way to query ServerRuntimeMBean . connect directly to managed server , don't get it via domain runtime bean , using serverruntime() directly . if it still dosn't work , then you have to rasie a call with oracle :-)
    connect('weblogic','weblogic','t3://local:7002')
    serverRuntime()
    status = cmo.getHealthState()
    print str(status)

  • Manage Server Health Goes Blank in Admin Console

    Hello Team,
    I am continously facing issue with OSB manage server. It is running fine but health is blank in Admin Console.
    Due to which it is not responding to any user request.
    Kindly guide me to troubleshoot this issue.

    Hi,
    It is due to the problem with the JMX communication between and Admin and your OSB managed servers. Did you observed any messages related to it?
    Is it a SSL communication, then try to make sure that certificates are valid.
    As a general practice, make sure you have listen address configured for your servers. If left it blank(default), then it would be listening on the all the available host and communication would get messy in these situations.
    If still facing problem, i would suggest you enable the below debugs and raise a support case
    1. Apply the below three debug logs from console(for admin as well as Managed Server)
       weblogic->management->JMXCore
       weblogic->management->JMXDomain
       weblogic->management->JMXRuntime
    2. Restart all the servers
    If the issue, occurs, provide the debug along with the thread dump(take 5 thread dump at an interval of 5seconds) for the Managed Server(which is unknown state) and for the admin server.
    Regards
    Rosario

  • DirectAccess Server Health Check URL

    I am looking at using an external hardware load-balancer with a DirectAccess 2012 R2 implementation.  Besides an ICMP echo-reply, does anyone know of a specific URL I could plug in as a health check to determine the DA server availability.
    Thanks...

    Hi,
    A subject I'm currently working on. IPHTTPS, it's only TCP443, it does not proove that DirectAccess works. Because i wanted to avoid to write complex check rules, I choose to rely on Powershell.
    A simple Get-RemoteAccessHealth -verbose | Where {$_.HealthState -ne "Disabled"} return status for all involved components (whatever your configuration). Each component can be OK or KO. I have a script that parse this result and write a simple
    text file with OK or KO. This file is designed to be consumed by the HLB Appliance throught IIS (available on the DirectAccess Gateway). With such approach, monitoring DirectAccess health is becoming easy.
    So your HLB applicance can detect if one of your DirectAccess Gateway is not operational (eg Failing OTP or expired certificate) and remove it from your pools.
    BenoitS - Simple by Design http://danstoncloud.com/blogs/simplebydesign/default.aspx

  • SQL Server Health Check (T-SQL)

    I'm looking for a peer review from my fellow SQL Server DBA's.  I've written an 89-point health check that I'd really appreciate feedback on.  You can find the health check scripts at www.sqlhc.com.
     All scripts are free to use.
    Thanks,
    Chris Jones

    Excellent!!! Great work... thanks.

  • Server Health "failed logins per hour"

    I'm getting over 100 failures per hour from 3 jet direct cards
    The cards are all
    Model Number: J6057A
    Firmware Version: R.25.57
    I've updated the firmware, no help
    Is there a default user login that is incorrect?
    IPX Name: WAHWAH_PS
    IPX Address: 3.0001E697F790
    IPX/SPX Frame Type: Auto Select
    SAP Interval: 60
    Direct Mode
    Number of connections supported: 1
    Connections Available: 1
    Queue Server
    Print Server Name: WAHWAH_PS
    NDS Tree Name: NP_IC
    File Server Name: IBM_XSERIES1
    Connection Status: NetWare Password Error
    NCP Code: FF
    File Server Name: IBM_XSERIES1
    Connection Status: Queue Server Connected
    NCP Code: D5

    Originally Posted by peterkuo
    Was the JD configured with a password?
    Peter
    eDirectory Rules!
    No the Jet Direct cards were not setup with a password.
    When you login to the printer ... under protocol info ipx/spx
    Notice that the printer says there is a password error
    IPX Name: WAHWAH_PS
    IPX Address: 3.0001E697F790
    IPX/SPX Frame Type: Auto Select
    SAP Interval: 60
    Direct Mode
    Number of connections supported: 1
    Connections Available: 1
    Queue Server
    Print Server Name: WAHWAH_PS
    NDS Tree Name: NP_IC
    File Server Name: IBM_XSERIES1
    Connection Status: NetWare Password Error NCP Code: FF
    File Server Name: IBM_XSERIES1
    Connection Status: Queue Server Connected
    NCP Code: D5

Maybe you are looking for