ACE : Connection failures counter

Hi,
In the command show serverfarm :
CH01AC03/P-115-A# sh serverfarm NCL_FARM_PROD
serverfarm : NCL_FARM_PROD, type: HOST
total rservers : 6
----------connections-----------
real weight state current total failures
---+---------------------+------+------------+----------+----------+---------
rserver: HQBUUN203
10.56.7.209:443 8 OPERATIONAL 16 130388 15
rserver: HQBUUN205
10.56.7.210:443 8 OPERATIONAL 10 130392 10
rserver: HQBUUN221
10.56.7.94:443 8 OPERATIONAL 9 130383 19
rserver: HQBUUN222
10.56.7.93:443 8 OPERATIONAL 7 130391 12
rserver: HQVEUN218
10.56.7.96:443 8 OPERATIONAL 13 130390 13
rserver: HQVEUN219
10.56.7.95:443 8 OPERATIONAL 9 130389 14
What does the connections failures field mean ? Is it the number of time the ACE did not receive a SYN-ACK packet within a time window after having sent a SYN ? If it is true, what is the timeout value and can I modify it ?
Thank you
Yves Haemmerli

Yves,
the timeout is the embryonic timeout and it can be configured within a parameter-map.
Other reason for this counter to increment is if the rserver responds with a RST.
We have also seen bugs where the client sending a RST results in this counter to increment.
If you can, verify with a sniffer trace in what condition you are before changing the embryonic timeout.
Gilles.

Similar Messages

  • ACE show serverfarm - failure counter does not incremented on Probe-Failure event

    Hi,
    Despite of probe-failure the failure counter is not incremented. Is there any correlation between the configured probe and the failure counter?
    (Custom script probe is used for this serverfarm)
    # sh serverfarm xxxxxSt
    serverfarm     : xxxxxSt, type: HOST
    total rservers : 2
                                                    ----------connections-----------
           real                  weight state        current    total      failures
       ---+---------------------+------+------------+----------+----------+---------
       rserver: xxxxx6
           10.222.0.90:8000      8      OPERATIONAL  13         157        0
       rserver: xxxxx7
           10.222.0.92:8000      8      PROBE-FAILED 0          0          0
    Thanks,
    Attila

    Hi Attila,
    The Connection Failure counter under show serverfarm is for Loadbalanced Connections which are failing.
    If Probes are failing, this counter will not increment.
    The Connection failure counter can increment for various reasons some of them are,
    - Server not responding to the SYN packet sent by ACE for Loadbalanced connection
    - Server sending Reset to the SYN packet sent by ACE for Loadbalanced connection
    To check on stats for Probe, you can run "show probe detail" command.
    Hope this helps,
    Best Regards,
    Rahul

  • ACE : Rserver connection failures ?

    Hi,
    In a productive environment, I observe rserver counters and I can read several connection failures. However, the site seems to work correctly.
    What are the conditions under which he ACE increments the connection failures counter ?
    Here is an extract of the show serverfarm command :
    CH01AC03/P-115-A# sh serverfarm NCL_FARM_PROD
    serverfarm     : NCL_FARM_PROD, type: HOST
    total rservers : 6
                                                    ----------connections-----------
           real                  weight state        current    total      failures
       ---+---------------------+------+------------+----------+----------+---------
       rserver: HQBUUN203
           10.56.7.209:443       12     OPERATIONAL  11         2363414    334
       rserver: HQBUUN205
           10.56.7.210:443       12     OPERATIONAL  11         2321347    2055
       rserver: HQBUUN221
           10.56.7.94:443        8      OPERATIONAL  10         1611561    1270
       rserver: HQBUUN222
           10.56.7.93:443        8      OPERATIONAL  20         1608550    189
       rserver: HQVEUN218
           10.56.7.96:443        8      OPERATIONAL  15         1532865    1307
       rserver: HQVEUN219
           10.56.7.95:443        8      OPERATIONAL  12         1607162    304
    Thank you for any hints
    Yves Haemmerli

    Yves,
    normally only RST from the rserver or no response to SYN from the rserver are counted as failure.
    However, we had issues with this as identified in  CSCtd22008 "ACE- Client RST in End-to-End SSL generates Rserver conn-failures."
    An old one is CSCsh14278 "sh serverfarm failure conn incremented for successful connection".
    So, if you want to be sure, the only option is to capture a sniffer trace.
    Gilles.

  • ACE serverfarm total connections failures

    I have many server farms in various contexts and every single serverfarm shows something like this:
    NDCD23ACERT1/Internal-1295# sh serverfarm FINPROD88_80 detail
    serverfarm : FINPROD88_80, type: HOST
    total rservers : 3
    description : -
    predictor : ROUNDROBIN
    failaction : purge
    total conn-dropcount : 0
    ----------connections-----------
    real weight state current total
    ---+---------------------+------+------------+----------+--------------------
    rserver: FINPRODAPP5
    10.1.129.39:8320 2 OUTOFSERVICE 2 138
    total conn-failures : 348
    rserver: FINPRODAW1
    10.1.129.29:8320 1 OPERATIONAL 25 179
    total conn-failures : 418
    rserver: FINPRODAW2
    10.1.129.30:8320 1 OPERATIONAL 8 165
    total conn-failures : 456
    The conn-failures counter keeps growning on all of the farms. What exactly could be the problem? People aren't complaining but it bothers me to see those counters grow.
    Casey

    total conn-failures counter can increment due to several reasons
    1. When Server sends RST to close the connection
    2. When Client Sends an invalid HTTP request
    3. If "persistence-rebalance" & "layer 7 class map" is configured and ACE doesnt find a L7 condition in client request.
    So increments in the counter doesnt always means that there is a server problem :)
    There are bugs reported for all the above conditions.I am not sure if they are fixed in the latest release.
    Hope it helps
    Syed

  • ACE showing many connection failures on server farm

    I just upgraded my ACE blade from A2(1.0 to A2(1.5a). After the upgrade I'm seeing an enormous amount of connection failures when I run the command show server xxx. Everything appears to be running fine. I can get to the web servers. I found an old posting and they reference Bug CSCsh1478, but when I looked at this bug the problem was corrected in version A2(1.0). Any ideas of what's going on?
    Thanks
    Mike

    you will need to take a sniffer trace to see if there are any un-answered SYN or RST from the server.
    Gilles.

  • Netstorage in VO : Unknown connection failure 500

    Hi,
    When I access Netstorage within Virtual Office I get the following message:
    NetStorage getData:PortalURLException
    URL = https://virtualoffice.rademaker.nl:4...et/xtier-login
    Unknown Connection Failure :500
    This happened after patching the server (SLES9SP2 (OES linux) to the latest
    available patches.
    I already reset the owner of /opt/novell/netstorage and below directories to
    wwwrun:www
    The same for /opt/novell/netstorage (acc. TID 3944596)
    However still the same errormessage.
    I checked out the /var/log/messages file and found this :
    Mar 26 20:27:32 orion httpd2-worker: XSrvCChannel::connectSocket- Connection
    creation failed, error = 111
    Mar 26 20:27:32 orion httpd2-worker: XSrvCChannel::init- Connection creation
    failed, error = 111
    Mar 26 20:27:32 orion httpd2-worker: IPCCLNT -getCChannel- Channel
    Initialization failed for socket /var/opt/novell/xtier/xsrvd/srv-socket-18
    Mar 26 20:27:32 orion httpd2-worker: IPCCLNT -SubmitReq- Channel unavailable
    Mar 26 20:27:32 orion httpd2-worker: IPCCLNT -SubmitReq- Will attempt to
    retry RPC, count = 1
    Mar 26 20:27:32 orion httpd2-worker: XSrvCChannel::connectSocket- Connection
    creation failed, error = 111
    Mar 26 20:27:32 orion httpd2-worker: XSrvCChannel::init- Connection creation
    failed, error = 111
    Mar 26 20:27:32 orion httpd2-worker: IPCCLNT -getCChannel- Channel
    Initialization failed for socket /var/opt/novell/xtier/xsrvd/srv-socket-18
    Mar 26 20:27:32 orion httpd2-worker: IPCCLNT -SubmitReq- Channel unavailable
    Mar 26 20:27:32 orion httpd2-worker: IPCCLNT -SubmitReq- Will attempt to
    retry RPC, count = 2
    Mar 26 20:27:32 orion httpd2-worker: XSrvCChannel::connectSocket- Connection
    creation failed, error = 111
    Mar 26 20:27:32 orion httpd2-worker: XSrvCChannel::init- Connection creation
    failed, error = 111
    Mar 26 20:27:32 orion httpd2-worker: IPCCLNT -getCChannel- Channel
    Initialization failed for socket /var/opt/novell/xtier/xsrvd/srv-socket-18
    Mar 26 20:27:32 orion httpd2-worker: IPCCLNT -SubmitReq- Channel unavailable
    Mar 26 20:27:32 orion httpd2-worker: IPCCLNT -SubmitReq- Will attempt to
    retry RPC, count = 3
    Mar 26 20:27:32 orion httpd2-worker: XSrvCChannel::connectSocket- Connection
    creation failed, error = 111
    Mar 26 20:27:32 orion httpd2-worker: XSrvCChannel::init- Connection creation
    failed, error = 111
    Mar 26 20:27:32 orion httpd2-worker: IPCCLNT -getCChannel- Channel
    Initialization failed for socket /var/opt/novell/xtier/xsrvd/srv-socket-18
    Mar 26 20:27:32 orion httpd2-worker: IPCCLNT -SubmitReq- Channel unavailable
    Mar 26 20:27:32 orion httpd2-worker: IPCCLNT -SubmitReq- Will attempt to
    retry RPC, count = 1
    Mar 26 20:27:32 orion httpd2-worker: XSrvCChannel::connectSocket- Connection
    creation failed, error = 111
    Mar 26 20:27:32 orion httpd2-worker: XSrvCChannel::init- Connection creation
    failed, error = 111
    Mar 26 20:27:32 orion httpd2-worker: IPCCLNT -getCChannel- Channel
    Initialization failed for socket /var/opt/novell/xtier/xsrvd/srv-socket-18
    Mar 26 20:27:32 orion httpd2-worker: IPCCLNT -SubmitReq- Channel unavailable
    Mar 26 20:27:32 orion httpd2-worker: IPCCLNT -SubmitReq- Will attempt to
    retry RPC, count = 2
    Mar 26 20:27:32 orion httpd2-worker: XSrvCChannel::connectSocket- Connection
    creation failed, error = 111
    Mar 26 20:27:32 orion httpd2-worker: XSrvCChannel::init- Connection creation
    failed, error = 111
    Mar 26 20:27:32 orion httpd2-worker: IPCCLNT -getCChannel- Channel
    Initialization failed for socket /var/opt/novell/xtier/xsrvd/srv-socket-18
    Mar 26 20:27:32 orion httpd2-worker: IPCCLNT -SubmitReq- Channel unavailable
    Mar 26 20:27:32 orion httpd2-worker: IPCCLNT -SubmitReq- Will attempt to
    retry RPC, count = 3
    Mar 26 20:27:32 orion httpd2-worker: XSrvCChannel::connectSocket- Connection
    creation failed, error = 111
    Mar 26 20:27:32 orion httpd2-worker: XSrvCChannel::init- Connection creation
    failed, error = 111
    Mar 26 20:27:32 orion httpd2-worker: IPCCLNT -getCChannel- Channel
    Initialization failed for socket /var/opt/novell/xtier/xsrvd/srv-socket-18
    Mar 26 20:27:32 orion httpd2-worker: IPCCLNT -SubmitReq- Channel unavailable
    Mar 26 20:27:32 orion httpd2-worker: IPCCLNT -SubmitReq- Will attempt to
    retry RPC, count = 1
    Mar 26 20:27:32 orion httpd2-worker: XSrvCChannel::connectSocket- Connection
    creation failed, error = 111
    Mar 26 20:27:32 orion httpd2-worker: XSrvCChannel::init- Connection creation
    failed, error = 111
    Mar 26 20:27:32 orion httpd2-worker: IPCCLNT -getCChannel- Channel
    Initialization failed for socket /var/opt/novell/xtier/xsrvd/srv-socket-18
    Mar 26 20:27:32 orion httpd2-worker: IPCCLNT -SubmitReq- Channel unavailable
    Mar 26 20:27:32 orion httpd2-worker: IPCCLNT -SubmitReq- Will attempt to
    retry RPC, count = 2
    Mar 26 20:27:32 orion httpd2-worker: XSrvCChannel::connectSocket- Connection
    creation failed, error = 111
    Mar 26 20:27:32 orion httpd2-worker: XSrvCChannel::init- Connection creation
    failed, error = 111
    Mar 26 20:27:32 orion httpd2-worker: IPCCLNT -getCChannel- Channel
    Initialization failed for socket /var/opt/novell/xtier/xsrvd/srv-socket-18
    Mar 26 20:27:32 orion httpd2-worker: IPCCLNT -SubmitReq- Channel unavailable
    Mar 26 20:27:32 orion httpd2-worker: IPCCLNT -SubmitReq- Will attempt to
    retry RPC, count = 3
    Mar 26 20:27:32 orion httpd2-worker: XSrvCChannel::connectSocket- Connection
    creation failed, error = 111
    Mar 26 20:27:32 orion httpd2-worker: XSrvCChannel::init- Connection creation
    failed, error = 111
    Mar 26 20:27:32 orion httpd2-worker: IPCCLNT -getCChannel- Channel
    Initialization failed for socket /var/opt/novell/xtier/xsrvd/srv-socket-18
    Mar 26 20:27:32 orion httpd2-worker: IPCCLNT -SubmitReq- Channel unavailable
    Mar 26 20:27:32 orion httpd2-worker: IPCCLNT -SubmitReq- Will attempt to
    retry RPC, count = 1
    Mar 26 20:27:32 orion httpd2-worker: XSrvCChannel::connectSocket- Connection
    creation failed, error = 111
    Mar 26 20:27:32 orion httpd2-worker: XSrvCChannel::init- Connection creation
    failed, error = 111
    Mar 26 20:27:32 orion httpd2-worker: IPCCLNT -getCChannel- Channel
    Initialization failed for socket /var/opt/novell/xtier/xsrvd/srv-socket-18
    Mar 26 20:27:32 orion httpd2-worker: IPCCLNT -SubmitReq- Channel unavailable
    Mar 26 20:27:32 orion httpd2-worker: IPCCLNT -SubmitReq- Will attempt to
    retry RPC, count = 2
    Mar 26 20:27:32 orion httpd2-worker: XSrvCChannel::connectSocket- Connection
    creation failed, error = 111
    Mar 26 20:27:32 orion httpd2-worker: XSrvCChannel::init- Connection creation
    failed, error = 111
    Mar 26 20:27:32 orion httpd2-worker: IPCCLNT -getCChannel- Channel
    Initialization failed for socket /var/opt/novell/xtier/xsrvd/srv-socket-18
    Mar 26 20:27:32 orion httpd2-worker: IPCCLNT -SubmitReq- Channel unavailable
    Mar 26 20:27:32 orion httpd2-worker: IPCCLNT -SubmitReq- Will attempt to
    retry RPC, count = 3
    Mar 26 20:27:32 orion httpd2-worker: XSrvCChannel::connectSocket- Connection
    creation failed, error = 111
    Mar 26 20:27:32 orion httpd2-worker: XSrvCChannel::init- Connection creation
    failed, error = 111
    Mar 26 20:27:32 orion httpd2-worker: IPCCLNT -getCChannel- Channel
    Initialization failed for socket /var/opt/novell/xtier/xsrvd/srv-socket-18
    Mar 26 20:27:32 orion httpd2-worker: IPCCLNT -SubmitReq- Channel unavailable
    Mar 26 20:27:32 orion httpd2-worker: IPCCLNT -SubmitReq- Will attempt to
    retry RPC, count = 1
    I checked out TID 3593388, verified everything, but it looks like it is all
    ok.
    Anyone experienced the same, or is maybe reconfiguring netstorage in the
    yast - network services- the best option?
    Any help would be really appreciated.
    Best regards,
    John M.

    Hi,
    I know the solution. You can buy it for $500. Novell does not patch their
    products properly.
    Most of all your current solution breaks. But I can fix it for you.
    regards,
    Pieter
    "John M." <[email protected]> wrote in message
    news:[email protected]...
    > Hi,
    >
    > When I access Netstorage within Virtual Office I get the following
    > message:
    >
    > NetStorage getData:PortalURLException
    > URL = https://virtualoffice.rademaker.nl:4...et/xtier-login
    > Unknown Connection Failure :500
    >
    > This happened after patching the server (SLES9SP2 (OES linux) to the
    > latest available patches.
    >
    > I already reset the owner of /opt/novell/netstorage and below directories
    > to wwwrun:www
    > The same for /opt/novell/netstorage (acc. TID 3944596)
    >
    > However still the same errormessage.
    >
    > I checked out the /var/log/messages file and found this :
    >
    > Mar 26 20:27:32 orion httpd2-worker: XSrvCChannel::connectSocket-
    > Connection creation failed, error = 111
    > Mar 26 20:27:32 orion httpd2-worker: XSrvCChannel::init- Connection
    > creation failed, error = 111
    > Mar 26 20:27:32 orion httpd2-worker: IPCCLNT -getCChannel- Channel
    > Initialization failed for socket /var/opt/novell/xtier/xsrvd/srv-socket-18
    > Mar 26 20:27:32 orion httpd2-worker: IPCCLNT -SubmitReq- Channel
    > unavailable
    > Mar 26 20:27:32 orion httpd2-worker: IPCCLNT -SubmitReq- Will attempt to
    > retry RPC, count = 1
    > Mar 26 20:27:32 orion httpd2-worker: XSrvCChannel::connectSocket-
    > Connection creation failed, error = 111
    > Mar 26 20:27:32 orion httpd2-worker: XSrvCChannel::init- Connection
    > creation failed, error = 111
    > Mar 26 20:27:32 orion httpd2-worker: IPCCLNT -getCChannel- Channel
    > Initialization failed for socket /var/opt/novell/xtier/xsrvd/srv-socket-18
    > Mar 26 20:27:32 orion httpd2-worker: IPCCLNT -SubmitReq- Channel
    > unavailable
    > Mar 26 20:27:32 orion httpd2-worker: IPCCLNT -SubmitReq- Will attempt to
    > retry RPC, count = 2
    > Mar 26 20:27:32 orion httpd2-worker: XSrvCChannel::connectSocket-
    > Connection creation failed, error = 111
    > Mar 26 20:27:32 orion httpd2-worker: XSrvCChannel::init- Connection
    > creation failed, error = 111
    > Mar 26 20:27:32 orion httpd2-worker: IPCCLNT -getCChannel- Channel
    > Initialization failed for socket /var/opt/novell/xtier/xsrvd/srv-socket-18
    > Mar 26 20:27:32 orion httpd2-worker: IPCCLNT -SubmitReq- Channel
    > unavailable
    > Mar 26 20:27:32 orion httpd2-worker: IPCCLNT -SubmitReq- Will attempt to
    > retry RPC, count = 3
    > Mar 26 20:27:32 orion httpd2-worker: XSrvCChannel::connectSocket-
    > Connection creation failed, error = 111
    > Mar 26 20:27:32 orion httpd2-worker: XSrvCChannel::init- Connection
    > creation failed, error = 111
    > Mar 26 20:27:32 orion httpd2-worker: IPCCLNT -getCChannel- Channel
    > Initialization failed for socket /var/opt/novell/xtier/xsrvd/srv-socket-18
    > Mar 26 20:27:32 orion httpd2-worker: IPCCLNT -SubmitReq- Channel
    > unavailable
    > Mar 26 20:27:32 orion httpd2-worker: IPCCLNT -SubmitReq- Will attempt to
    > retry RPC, count = 1
    > Mar 26 20:27:32 orion httpd2-worker: XSrvCChannel::connectSocket-
    > Connection creation failed, error = 111
    > Mar 26 20:27:32 orion httpd2-worker: XSrvCChannel::init- Connection
    > creation failed, error = 111
    > Mar 26 20:27:32 orion httpd2-worker: IPCCLNT -getCChannel- Channel
    > Initialization failed for socket /var/opt/novell/xtier/xsrvd/srv-socket-18
    > Mar 26 20:27:32 orion httpd2-worker: IPCCLNT -SubmitReq- Channel
    > unavailable
    > Mar 26 20:27:32 orion httpd2-worker: IPCCLNT -SubmitReq- Will attempt to
    > retry RPC, count = 2
    > Mar 26 20:27:32 orion httpd2-worker: XSrvCChannel::connectSocket-
    > Connection creation failed, error = 111
    > Mar 26 20:27:32 orion httpd2-worker: XSrvCChannel::init- Connection
    > creation failed, error = 111
    > Mar 26 20:27:32 orion httpd2-worker: IPCCLNT -getCChannel- Channel
    > Initialization failed for socket /var/opt/novell/xtier/xsrvd/srv-socket-18
    > Mar 26 20:27:32 orion httpd2-worker: IPCCLNT -SubmitReq- Channel
    > unavailable
    > Mar 26 20:27:32 orion httpd2-worker: IPCCLNT -SubmitReq- Will attempt to
    > retry RPC, count = 3
    > Mar 26 20:27:32 orion httpd2-worker: XSrvCChannel::connectSocket-
    > Connection creation failed, error = 111
    > Mar 26 20:27:32 orion httpd2-worker: XSrvCChannel::init- Connection
    > creation failed, error = 111
    > Mar 26 20:27:32 orion httpd2-worker: IPCCLNT -getCChannel- Channel
    > Initialization failed for socket /var/opt/novell/xtier/xsrvd/srv-socket-18
    > Mar 26 20:27:32 orion httpd2-worker: IPCCLNT -SubmitReq- Channel
    > unavailable
    > Mar 26 20:27:32 orion httpd2-worker: IPCCLNT -SubmitReq- Will attempt to
    > retry RPC, count = 1
    > Mar 26 20:27:32 orion httpd2-worker: XSrvCChannel::connectSocket-
    > Connection creation failed, error = 111
    > Mar 26 20:27:32 orion httpd2-worker: XSrvCChannel::init- Connection
    > creation failed, error = 111
    > Mar 26 20:27:32 orion httpd2-worker: IPCCLNT -getCChannel- Channel
    > Initialization failed for socket /var/opt/novell/xtier/xsrvd/srv-socket-18
    > Mar 26 20:27:32 orion httpd2-worker: IPCCLNT -SubmitReq- Channel
    > unavailable
    > Mar 26 20:27:32 orion httpd2-worker: IPCCLNT -SubmitReq- Will attempt to
    > retry RPC, count = 2
    > Mar 26 20:27:32 orion httpd2-worker: XSrvCChannel::connectSocket-
    > Connection creation failed, error = 111
    > Mar 26 20:27:32 orion httpd2-worker: XSrvCChannel::init- Connection
    > creation failed, error = 111
    > Mar 26 20:27:32 orion httpd2-worker: IPCCLNT -getCChannel- Channel
    > Initialization failed for socket /var/opt/novell/xtier/xsrvd/srv-socket-18
    > Mar 26 20:27:32 orion httpd2-worker: IPCCLNT -SubmitReq- Channel
    > unavailable
    > Mar 26 20:27:32 orion httpd2-worker: IPCCLNT -SubmitReq- Will attempt to
    > retry RPC, count = 3
    > Mar 26 20:27:32 orion httpd2-worker: XSrvCChannel::connectSocket-
    > Connection creation failed, error = 111
    > Mar 26 20:27:32 orion httpd2-worker: XSrvCChannel::init- Connection
    > creation failed, error = 111
    > Mar 26 20:27:32 orion httpd2-worker: IPCCLNT -getCChannel- Channel
    > Initialization failed for socket /var/opt/novell/xtier/xsrvd/srv-socket-18
    > Mar 26 20:27:32 orion httpd2-worker: IPCCLNT -SubmitReq- Channel
    > unavailable
    > Mar 26 20:27:32 orion httpd2-worker: IPCCLNT -SubmitReq- Will attempt to
    > retry RPC, count = 1
    > Mar 26 20:27:32 orion httpd2-worker: XSrvCChannel::connectSocket-
    > Connection creation failed, error = 111
    > Mar 26 20:27:32 orion httpd2-worker: XSrvCChannel::init- Connection
    > creation failed, error = 111
    > Mar 26 20:27:32 orion httpd2-worker: IPCCLNT -getCChannel- Channel
    > Initialization failed for socket /var/opt/novell/xtier/xsrvd/srv-socket-18
    > Mar 26 20:27:32 orion httpd2-worker: IPCCLNT -SubmitReq- Channel
    > unavailable
    > Mar 26 20:27:32 orion httpd2-worker: IPCCLNT -SubmitReq- Will attempt to
    > retry RPC, count = 2
    > Mar 26 20:27:32 orion httpd2-worker: XSrvCChannel::connectSocket-
    > Connection creation failed, error = 111
    > Mar 26 20:27:32 orion httpd2-worker: XSrvCChannel::init- Connection
    > creation failed, error = 111
    > Mar 26 20:27:32 orion httpd2-worker: IPCCLNT -getCChannel- Channel
    > Initialization failed for socket /var/opt/novell/xtier/xsrvd/srv-socket-18
    > Mar 26 20:27:32 orion httpd2-worker: IPCCLNT -SubmitReq- Channel
    > unavailable
    > Mar 26 20:27:32 orion httpd2-worker: IPCCLNT -SubmitReq- Will attempt to
    > retry RPC, count = 3
    > Mar 26 20:27:32 orion httpd2-worker: XSrvCChannel::connectSocket-
    > Connection creation failed, error = 111
    > Mar 26 20:27:32 orion httpd2-worker: XSrvCChannel::init- Connection
    > creation failed, error = 111
    > Mar 26 20:27:32 orion httpd2-worker: IPCCLNT -getCChannel- Channel
    > Initialization failed for socket /var/opt/novell/xtier/xsrvd/srv-socket-18
    > Mar 26 20:27:32 orion httpd2-worker: IPCCLNT -SubmitReq- Channel
    > unavailable
    > Mar 26 20:27:32 orion httpd2-worker: IPCCLNT -SubmitReq- Will attempt to
    > retry RPC, count = 1
    >
    > I checked out TID 3593388, verified everything, but it looks like it is
    > all ok.
    >
    > Anyone experienced the same, or is maybe reconfiguring netstorage in the
    > yast - network services- the best option?
    >
    > Any help would be really appreciated.
    >
    > Best regards,
    > John M.

  • Connection failures

    Dear Sir,
    I am getting the following error sometimes when browsers (using IE5.5) take
    a page from my website served up with Weblogic 5.1
    The page contains some JavaScript and HTML.
    Please note that this does not always happen but when it does it only
    happens from PCs on the same sub-network as the server.
    It looks like a weblogic error to me. Any ideas?
    Thanks,
    Spencer
    Thu Aug 31 22:38:21 GMT+01:00 2000:<E> <HTTP> Connection failure
    java.net.SocketException: ReadFile on fd=536 failed with err=64
    at weblogic.socket.NTSocketMuxer.initiateIO(Native Method)
    at weblogic.socket.NTSocketMuxer.read(NTSocketMuxer.java, Compiled
    Code)
    at weblogic.socket.MuxableSocketHTTP.requeue(MuxableSocketHTTP.java,
    Compiled Code)
    at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java,
    Compiled Code)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java, Compiled
    Code)

    What would cause a RESET from the server?
    I have a situation where a SSL connection through ACE to a server works fine from some workstations and it does not work from others. It is not a network connectivity issue. When it fails I get the message indicating there is a certificate error, then I click continue and get a page cannot be displayed.
    This works fine from other workstations.

  • A significant number of connection failures have occurred with a remote server (Event ID 14502)

    I see a number of these events on my Lync 2010 Server. NSlookup shows that 75.0.230.1 is an sbcglobal.net server. (See bolded text.) I have no federation or other connections to sbcglobal.net or AT&T, so why is my Lync server attempting to contact this
    server (and others) at all?
    Log Name:      Lync Server
    Source:        LS Protocol Stack
    Date:          3/14/2014 11:34:30 AM
    Event ID:      14502
    Task Category: (1001)
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      EdgeServer.mydomain.com
    Description:
    A significant number of connection failures have occurred with remote server  IP 75.0.230.1. There have been 75 failures in the last 184 minutes. There have been a total of 75 failures.
    The specific failure types and their counts are identified below.
    Instance count   - Failure Type
    75                 0x80072746(WSAECONNRESET)
    This can be due to credential issues, DNS, firewalls or proxies. The specific failure types above should identify the problem.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="LS Protocol Stack" />
        <EventID Qualifiers="50153">14502</EventID>
        <Level>2</Level>
        <Task>1001</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2014-03-14T16:34:30.000000000Z" />
        <EventRecordID>32141</EventRecordID>
        <Channel>Lync Server</Channel>
        <Computer>EdgeServer.mydomain.com</Computer>
        <Security />
      </System>
      <EventData>
        <Data>75.0.230.1</Data>
        <Data>
        </Data>
        <Data>75</Data>
        <Data>184</Data>
        <Data>75</Data>
        <Data>75</Data>
        <Data>0x80072746(WSAECONNRESET)</Data>
        <Data>
        </Data>
        <Data>
        </Data>
        <Data>
        </Data>
        <Data>
        </Data>
      </EventData>
    </Event>
    Blog /
    Facebook / Twitter

    To combat the issue, enable an HLB port on your FE servers (or any other pool you are using HLB on) and configure the health checks for the load balancer to use that port instead of the port used for TLS traffic.
    Start by configuring the pool in Topology Builder, right click the pool, and choose Edit Properties>General.  Place a check in the “Enable Hardware Load Balancer monitoring port” and specify a port.
    Also you can refer below link
    http://ocsguy.com/2011/11/02/lync-hardware-load-balancer-monitoring-port/
    Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question, please click "Mark As Answer"

  • ACE connection limit and remote TCP security scans

    We are currently running remote TCP security scans on our networks and are running into a major problem where when the scans are taking place the ACE connection resource usage sky rockets and easily reaches the maximum 4 million connections.  This means that anyone can run a simple TCP scan and take down our ACE by maxing the connection limit.  We have the following parameter-map applied to all of our policies but it does not help to clear the connection count on the ACE in a reasonable amount of time.  parameter-map type connection CONNECTION_TIMEOUT   set timeout inactivity 300   set tcp timeout half-closed 60  I should note that we do have normalization turned off because it causes way more problems then it's worth (no resolution with TAC).  Does anyone have an tips on how to accommodate security scan's on networks behind the ACE while not saturating the connection count limit?

    For vips, this particular context only has one class C applied to a class-map.  Not all IP's are in use but regardless the ACE creates connections for those as well.  I've set the timeout inactivity to 120 seconds and I still see connections from the remote scanning host idling well over 45mins for connections destined to the vip's.  Is turning on normalization my only option?  I know there are others who have turned off normalization due to performance and connectivity issues so there must be other ways around this.  Thanks for your help.

  • Sqlplus returns 0/SUCCESS on CONNECT failure

    Consider ..
    $ sqlplus /nolog <<EOF
    connect sys as foobar
    EOF$ echo $?
    0
    sqlplus returns success on a connect failure. I have tried to coax it to return non-0 exit code using
    sqlplus /nolog<<EOF
    whenever sqlerror exit 1
    whenever oserror exit 1
    connect sys as foobar
    EOFBut this doesn't work, looks like sqlplus disconnects after the connect failure and both the 'whenever' clauses don't fire.
    How can I get sqlplus to report a failure exit code. I understand I can parse the response from sqlplus, but that is not desirable at the moment.
    -srp

    srp
    I wonder if this is port specific? I only have access to Windows at the moment so can't tell.
    From the docs, it looks like expected behaviour; WHENEVER SQLERROR only fires if a SQL or PL/SQL fails - and CONNECT doesn't really count as SQL.
    A workaround would be to explicitly EXIT with a success code != 0 when you safely get to the end of your script. Then you could assume that 0 means a failed login.
    Alternatively, you can create a marker file when you successfully login; if the file isn't there, then you didn't log in:
    rm -rf /tmp/mydiagfile
    sqlplus /nolog <<EOF
        connect sys as foobar
        host touch /tmp/mydiagfile
        SQL statements
        EXIT
    EOF
    result=$?
    if [ result -eq 0 ]
    then
       # did we get in
       if [ ! -e /tmp/mydiagfile]
       then
          # login must have failed
          echo ERROR - ... etc
       fi
    fiAny help? At least it's simpler than parsing the log file...
    HTH
    Regards Nigel

  • I'm having strange random connection failures. Are there ineffieciency in my config?

    I've been having strange, random connection failures and I'm trying to eliminate possible causes.
    What happens is while I'm browsing on the net over wifi, a link will at random not connect to the site, but instead fault to the ISP error page. It happens with highly reliable sites like google, or ebay, or whatever. If I direct connect to the cable modem, the problem site is immediately available.
    I'm sitting <6 feet from a 871W router (with antenna). There's one router in my building and others are at my neighbors. 
    Below is the conf file. Just to imagine how rediculious this problem is, here's a screen shot from a web page. This shows a web page I visited, and after clicking on a link (an embedded youtube video), the error showed up within the page itself.
    Why would only some URLs fail to connect? Is there inefficiencies in my config?
        Building configuration...
        Current configuration : 4750 bytes
        version 12.4
        no service pad
        service timestamps debug datetime msec
        service timestamps log datetime msec
        no service password-encryption
        hostname TooterTurtle
        boot-start-marker
        boot-end-marker
        logging buffered 51200 warnings
        no logging console
        aaa new-model
        aaa authentication login default local
        aaa authorization exec default local
        aaa session-id common
        clock timezone NewYork -5
        clock summer-time NewYork date Apr 6 2003 2:00 Oct 26 2003 2:00
        dot11 syslog
        dot11 ssid TooterTurtle
           vlan 2
           authentication open
           authentication key-management wpa
           guest-mode
           wpa-psk ascii 0 [my wifi password]
        no ip source-route
        no ip gratuitous-arps
        ip cef
        no ip dhcp use vrf connected
        ip dhcp excluded-address 192.168.10.1 192.168.10.10
        ip dhcp excluded-address 10.0.0.1 10.0.0.10
        ip dhcp pool vlan1
           import all
           network 192.168.10.0 255.255.255.0
           dns-server 192.168.10.1
           default-router 192.168.10.1
           domain-name Ethernet
        ip dhcp pool vlan2
           import all
           network 10.0.0.0 255.255.255.0
           domain-name WiFi
           dns-server 10.0.0.1
           default-router 10.0.0.1
        ip dhcp pool MrWizard
           host 192.168.10.100 255.255.255.0
           hardware-address 0011.0917.66fa
           client-name MrWizard
        ip dhcp pool MasterShake
           host 192.168.10.101 255.255.255.0
           hardware-address 0022.681c.fbcc
           client-name mastershake
        ip auth-proxy max-nodata-conns 3
        ip admission max-nodata-conns 3
        no ip bootp server
        ip domain name mydomain.com
        ip ddns update method ccp_ddns1
         HTTP
          add [zone edit account and url]
          remove [zone edit account and url]
        username admin privilege 15 secret 5 [encrypted secret]
        archive
         log config
          hidekeys
        no ip ftp passive
        ip ssh version 1
        bridge irb
        interface FastEthernet0
         description AdminInterface
        interface FastEthernet1
         description MrWizard
        interface FastEthernet2
         description Belkin
        interface FastEthernet3
        interface FastEthernet4
         description ComcastCableModem
         ip address dhcp
         ip verify unicast source reachable-via rx allow-default 100
         no ip redirects
         no ip unreachables
         no ip proxy-arp
         ip nat outside
         ip virtual-reassembly
         speed auto
         full-duplex
        interface Dot11Radio0
         no ip address
         no ip redirects
         no ip unreachables
         no ip proxy-arp
         encryption vlan 1 mode ciphers tkip
         encryption vlan 2 mode ciphers tkip
         ssid TooterTurtle
         speed basic-1.0 basic-2.0 basic-5.5 basic-6.0 basic-9.0 basic-11.0 basic-12.0 basic-18.0 basic-24.0 basic-36.0 basic-48.0 basic-54.0
         station-role root
        interface Dot11Radio0.1
         description TootersWiFi
         encapsulation dot1Q 2
         no cdp enable
         bridge-group 2
         bridge-group 2 subscriber-loop-control
         bridge-group 2 spanning-disabled
         bridge-group 2 block-unknown-source
         no bridge-group 2 source-learning
         no bridge-group 2 unicast-flooding
        interface Vlan1
         description EthernetOnly
         no ip address
         no ip redirects
         no ip unreachables
         no ip proxy-arp
         ip nat inside
         ip virtual-reassembly
         bridge-group 1
        interface Vlan2
         description WiFiOnly
         no ip address
         bridge-group 2
        interface BVI1
         description EthernetOnly
         ip address 192.168.10.1 255.255.255.0
         ip nat inside
         ip virtual-reassembly
        interface BVI2
         description WiFiOnly
         ip address 10.0.0.1 255.255.255.0
         ip nat inside
         ip virtual-reassembly
        ip forward-protocol nd
        ip route 0.0.0.0 0.0.0.0 FastEthernet4
        ip http server
        ip http authentication local
        no ip http secure-server
        ip http timeout-policy idle 60 life 86400 requests 10000
        ip dns server
        ip nat inside source list 101 interface FastEthernet4 overload
        ip nat inside source list 102 interface FastEthernet4 overload
        ip nat inside source static tcp 192.168.10.100 80 interface FastEthernet4 80
        ip access-list extended vlan1
         deny   ip 10.0.0.0 0.0.0.255 any
         permit ip any any
        access-list 100 permit udp any any eq bootpc
        access-list 101 permit ip 192.168.10.0 0.0.0.255 any
        access-list 102 permit ip 10.0.0.0 0.0.0.255 any
        no cdp run
        control-plane
        bridge 1 protocol ieee
        bridge 1 route ip
        bridge 2 protocol ieee
        bridge 2 route ip
        line con 0
         no modem enable
        line aux 0
        line vty 0 4
         transport input telnet ssh
         transport output telnet ssh
        scheduler max-task-time 5000
        end

    I removed the ip router 0 0 to no great effect, which I consider to be a win.
    I'm guessing that since overload is what--I understand--translates the one outside to the many inside IPs, that the suggestion to have only one overload configured means I should combine the two ip ranges into one.
    I deleted 10.0.0.0 network. Changed the bridge references to 1 and vlan references to 1. Now wifi and ethernet should all be using the same internal network? That's the idea, right? Any more fat?
    [EDITED]
    dot11 syslog
    dot11 ssid TooterTurtle
       vlan 1
       authentication open
       authentication key-management wpa
       guest-mode
       wpa-psk ascii 0 [my passphrase]
    no ip source-route
    no ip gratuitous-arps
    ip cef
    no ip dhcp use vrf connected
    ip dhcp excluded-address 192.168.10.1 192.168.10.10
    ip dhcp pool vlan1
       import all
       network 192.168.10.0 255.255.255.0
       dns-server 192.168.10.1
       default-router 192.168.10.1
       domain-name Ethernet
    ip auth-proxy max-nodata-conns 3
    ip admission max-nodata-conns 3
    no ip bootp server
    ip domain name [my url]
    ip ddns update method ccp_ddns1
     HTTP
      add http:...[zoneedit]
      remove http:[zoneedit]
    no ip ftp passive
    ip ssh version 1
    bridge irb
    interface FastEthernet0
     description AdminInterface
    interface FastEthernet1
     description MrWizard
    interface FastEthernet2
     description Belkin
    interface FastEthernet3
    interface FastEthernet4
     description ComcastCableModem
     ip address dhcp
     ip verify unicast source reachable-via rx allow-default 100
     no ip redirects
     no ip unreachables
     no ip proxy-arp
     ip nat outside
     ip virtual-reassembly
     speed auto
     full-duplex
    interface Dot11Radio0
     no ip address
     no ip redirects
     no ip unreachables
     no ip proxy-arp
     encryption vlan 1 mode ciphers tkip
     ssid TooterTurtle
     speed basic-1.0 basic-2.0 basic-5.5 basic-6.0 basic-9.0 basic-11.0 basic-12.0 basic-18.0 basic-24.0 basic-36.0 basic-48.0 basic-54.0
     station-role root
    interface Dot11Radio0.1
     description TootersWiFi
     encapsulation dot1Q 2
     no cdp enable
     bridge-group 1
     bridge-group 1 subscriber-loop-control
     bridge-group 1 spanning-disabled
     bridge-group 1 block-unknown-source
     no bridge-group 1 source-learning
     no bridge-group 1 unicast-flooding
    interface Vlan1
     description EthernetOnly
     no ip address
     no ip redirects
     no ip unreachables
     no ip proxy-arp
     ip nat inside
     ip virtual-reassembly
     bridge-group 1
    interface BVI1
     description EthernetOnly
     ip address 192.168.10.1 255.255.255.0
     ip nat inside
     ip virtual-reassembly
    ip forward-protocol nd
    ip http server
    ip http authentication local
    no ip http secure-server
    ip http timeout-policy idle 60 life 86400 requests 10000
    ip dns server
    ip nat inside source list 101 interface FastEthernet4 overload
    ip nat inside source static tcp 192.168.10.100 80 interface FastEthernet4 80
    ip access-list extended vlan1
     permit ip any any
    access-list 100 permit udp any any eq bootpc
    access-list 101 permit ip 192.168.10.0 0.0.0.255 any
    no cdp run
    control-plane
    bridge 1 protocol ieee
    bridge 1 route ip

  • Datasocket connection failure requires restart of VI

    I'm using LabView RT 8.5 together with a cFP-2110. I have shared variables hosted on the cFP, as the cFP application works by itself without the need of a host PC application. However, a host PC application can be connected and read/write shared variables to work as a GUI. The shared variables are accessed with Datasocket VIs, as the same application is to be used on different cFPs with different IP addresses.
    The Datasocket connections is opened once and then the variables are accessed in a while loop. Before accessing the variables, RT Ping Controllers.vi checks if the cFP is still accessible. If not (or if the Datasocket Read operation fails), the Datasocket connection is closed. Now here comes the problem. When I want to re-establish the connection with Datasocket Open, I only get Error 66 (Connection closed by the peer). The only way I have found to "reset" this behaviour, is to close/stop the host VI and start it again. Is there an easier way to solve this? I assume the reason lies in something not being reset in the connection between the PC and the cFP. But what, and how can it be reset? Note that I have closed the connection with Datasocket Close in case of a failure.
    I do not need answers about how I can avoid the connection failures in the first place. They can e.g. be caused by the cFP being temporarily too busy or something. The issue is when a failure HAS occurred, I want to be able to re-establish the connection without restarting the VI. How?

    Isn't there anyone with similar experiences?
    I would assume that someone would be interested in being able to restore a connection after a failure. Improving connections to minimize the risk of failures is not anyway a 100% solution. Sooner or later a failure will occur. And in that case I am not pleased with having to restart the application in order to get the system back on track.
    I have already tried searching for previous posts regarding this, but the search results are very poor. Any ideas?
    Tom C

  • Can not connect to the App store I keep getting a connection failure message. Mail and Safari are working fine. Also Iphoto wont update to newer version and itunes does open up properly.

    I have recently bought a new imac. Imported all my files etc. from my G5 using Timemachine.
    Iphoto requires updating but wont!
    itunes wont open up properly the text is wrong!!
    I keep getting a connection failure message when trying to visit the App store.
    Safari and Mail are working fine.
    My Apple Id is also fine as it works with my ipad.
    Any suggestions?

    Hello Ben, see if this might be it...
    Anonymous
    Post subject: NSURLErrorDomain error -1100 in OS X 10.8
    If you check for software updates using the App Store in OS X 10.8 and get "NSURLErrorDomain error -1100" the problem may be with your Software Update preferences. This is particularly likely if you were using a custom Apple Software Update server. To solve the problem, quit the App Store, move the following two files (if present) to the trash, restart, and only then rerun App Store updates:
    /Library/Preferences/com.apple.SoftwareUpdate.plist
    /Library/Preferences/com.apple.SoftwareUpdate.plist.lockfile
    http://x704.net/bbs/viewtopic.php?f=12&t=6130

  • I'm unable to login to facebook though I reinstalled twice, but as i try to login it gives an error message as timeout, connection failure or check internet connection.

    Dear service provider, I'm unable to login to facebook even though i tried to uninstall and again reinstall as per the observation from the forum discussion.. but still it gives me arror as Timeout connection, or connection failure and check internet connection.. how to troubleshoot, pls suggest me..
    2ndly I'm unable to search by some of the keywords in itunes. means iTune is not fetching the required information rather it gives no result found message..

    Have you tried a hard reset of the iPod to see if that helps?  To do this, press and hold both the Sleep/Wake and Home buttons together long enough for the Apple logo to appear. 
    Otherwise, work through each of the troubleshooting suggestions in this Apple support document as necessary.
    iOS: Troubleshooting Wi-Fi networks and connections
    B-rock

  • BEA-101083 Connection failure.java.io.IOException: A complete message could not be read on socket: 'weblogic.servlet.internal.MuxableSocketHTTP@16907c  at weblogic.socket.SocketMuxer$TimeoutTrigger.trigger

    While trying to publish mesaage by MQ 5.3 .I got the following error
              Please help.
              <Error> <HTTP> <BEA-101083> <Connection failure.
              java.io.IOException: A complete message could not be read on socket: 'weblogic.servlet.internal.MuxableSocketHTTP@1c94ff
              3 - idle timeout: '30000' ms, socket timeout: '30000' ms', in the configured timeout period of '60' secs
              at weblogic.socket.SocketMuxer$TimeoutTrigger.trigger(SocketMuxer.java:775)
              at weblogic.time.common.internal.ScheduledTrigger.run(ScheduledTrigger.java:243)
              at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
              at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
              at weblogic.time.common.internal.ScheduledTrigger.executeLocally(ScheduledTrigger.java:229)
              at weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigger.java:223)
              at weblogic.time.server.ScheduledTrigger.execute(ScheduledTrigger.java:49)
              at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
              at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
              

    Can you help me ? I have the same problem.

Maybe you are looking for