Cisco CDN (Alarm 550001 (SEKeepalive) SE keepalive timed-out )

Dear Cisco Experts,
My systems as below:
CDSM, SR: version 3.2.1
SE1: version 3.2.1
SE2: version 2.6.3
Status (all devices): online (from CDSM: cms connectivity from all devices are OK)
SE1 can work normally, but SE2 doesn't work, Alarm:"SE SE2 keepalive timed-out" from CDSM.
log from SR:
192.168.11.0/24 20 SE2 (Down, Static)
192.168.8.0/24 20 SE1 (Operational, Static) (Load 1%, Device Threshold not reached)
0.0.0.0/0 10 SE1 (Operational, Static) (Load 1%, Device Threshold not reached)
0.0.0.0/0 10 SE2 (Down, Static)
I found infor from cisco about this alarm:
Alarm 550001 (SEKeepalive) SE keepalive timed-out or SE is not reachable.
Explanation Either the SR has not received keepalives from the SE, or the SE is not reachable.
Recommended Action Check the cables connected to the network device and the SE.
I'm sure about network connectivy is OK, problem should be from Version mismatch between SE and SR, Could you help me for this?
Many thanks and rgds.

Hi Long,
The alarm message that you are querying is indicating the keepalive between SR and SE has timed out.
There is UDP based keepalive messages sent from each SE to all SR periodically, by default it is 2 seconds. It is configurable via CDSM GUI. The destination port is 2323. This message has SE load information inside.
To check the keepalive message, you can execute following command on SR
SR# tcpdump udp port 2323
To debug keepalive, you can enable
SR#debug service-router keepalive
Then check service router errorlog under /local1
SR#type-tail errorlog/service_monitor_errorlog.current follow
check any error message popup. quit by Ctrl+C, then undebug all
SR#undebug all
Between 2.6.3 and 3.2.1, there is major difference in the format of packet. We do not recommend you to mix the version in production network. If you are requesting urgent assistance because of the service impact by this alarm, please do contact Cisco TAC support.
Best Regards,
Richard Xie

Similar Messages

ScheduledThreadPoolExecutor core thread pool / keepalive/timing out threads

Hi,
I am using a ScheduledThreadPoolExecutor - java1.6 on Windows(currently).
I would like to minimise the number of threads in the pool running at any one time to around the number of threads required to run the number of tasks that are concurrently executing.
However, I don't seem to be able to get the thread pool to minimise the number of threads below the max threads in the constructor.
I want to do this mainly because I have a large delay queue and the performance of the pool seems to be better when the number of threads in the pool is minimised to roughly the number of threads required to service the concurrently executing tasks.
Any ideas?
Thanks,
Alex
                ThreadFactory tf = new MyThreadFactory();
          ScheduledThreadPoolExecutor scheduler = new ScheduledThreadPoolExecutor(50,tf);
          scheduler.setCorePoolSize(10);
          //scheduler.setMaximumPoolSize(50);
          scheduler.setKeepAliveTime(1, TimeUnit.NANOSECONDS);
          scheduler.allowCoreThreadTimeOut(true);
          scheduler.schedule(aTask, 10, TimeUnit.SECONDS);
...

because of how a scheduledthreadpoolexecutor works, it doesn't really make sense to have a variable number of threads. since threads are only added when tasks are added to the pool (aka, when submit is called), once the core threads timed out they would never get replaced (e.g. you would eventually get down to 1 thread and never get anymore added). one way to achieve what you want would be to have a single threaded ScheduledThreadPoolExecutor, where the scheduled jobs do the real work in a separate, variable size thread pool (e.g. the scheduled tasks do not do anything but submit a task to the real work thread pool). this solution would work fine for "schedule at fixed rate" but not for "schedule with fixed delay". you would actually have to simulate the latter by scheduling a one-off task which resubmits itself to the scheduler each time it completes.

Cisco Prime and WLC packet capture error - Request Timed Out

Hello,
We have a Cisco Prime installation (2.2.0) and a WLC (Cisco 5508)
I’ve been trying to test the wireless packet capture function, but have now run into problems, a quick rundown of my actions so far:
Selected a wireless access point in Prime and clicked ‘Packet Capture’
Did a packet capture saving to the PI, the capture worked fine
Could not find any way to delete the packet capture
Selected a wireless access point in Prime and clicked ‘Packet Capture’
Did a packet capture saving to an FTP server, the capture worked fine
The 1st capture had finished (10 minute capture) before testing the second
The 2nd capture has also finished and saved the files to the FTP server as specified
Now though I cannot capture from any access point as when I click ‘Packet Capture’ I get the error:
“Request Timed out. Error in getting data from server.”
The error is ‘instant’ as in no delay indicating something actually timing out.
So the 2 problems I have are:
How do I fix the ‘request timed out’ error above
How do I delete old packet captures from the PI
I hope someone can help as I can’t find any info on either of the problems.
Cheers
Adrian

I think I've solved (2) by deleting the files from the FTP directory on the prime box through SSH.
So I'm now just stuck on the timed out error.

Cisco Mobile 8.0 For CME 8.6 : Verification Timed Out

Hi Guys,
Good day!
Anyone tried to implement Cisco Mobile on CME?
I have followed some guide lines from other forums such as:
http://www.ccierants.com/2011/05/finally-cisco-mobile-81-supports-cme-86.html
But I encounter some problems -> Verification Timed Out
Attached is the logs from CME router.
Thank you.

Have you restarted the "Cisco CallManager" service? Do you have IP address configured under CUCM > System > Servers?
Thanks!
Michael
http://htluo.blogspot.com

Cisco Agent Desktop (CAD) Timed Out

Hello Everybody,
I'm looking for a little insight into a problem that was encountered recently with a customer that essentially caused downtime. When the Agents were attempting to log into Cisco Agent Desktop it gave the following error:
"The request to log into the Cisco Unified CCX application server timed out. Please verify your system is online and try again."
CCX Version : 8.0.2.11002-3
CUCM: 8.0.3.21011-1 with LDAP integration/authentication
The customer does have high availability and after restarting both CCX servers the problem still occurred. Finally, once the CUCM publisher was restarted everything the login started working again. As the resolution was a server restart I'm looking for further information regarding this problem, why it may have occurred, and what can be done to prevent it in the future. It seems that LDAP issues are a common cause of this error but why? Can IPA be used as a backup if another situation like this occurs again?
I appreciate the time,
Thanks.

Hi Keith,
We could never state it will never happen again. CUCM, AD or UCCX could have a latency issue later on. However if you see the technote that I sent it explains what tracing is needed and how to verify that LDAP is not sending the acknowledgement back in time. Below is an example of the MIVR logs;
//Initiating login
461102: Jan 28 08:01:34.909 PST %MIVR-SS_RM-7-UNK:Trying to authenticate agent MSmith
The login ID is the same ID that is used to login to CAD. For our test MSmith was used.
The next message should be that login was successful; however, a time out may have occurred since the CAD timer has expired (10 seconds). We then see after the 10th second CUCM finishes the authentication.
//CUCM returns login successful after the 10 second CAD timer expires causing the timeout message to be displayed
461107: Jan 28 08:01:45.206 PST %MIVR-SS_RM-7-UNK:Successfully authenticated agent MSmith at extension 1904
CAD has ten second timer. If the successful message is not sent within that time CAD fails to login. The port change for the AD server that is the Global Catalog server is also documented in the CUCM SRND and should be used regardless.
I hope that answers your question.
Joe

VPN client get connect but Request Timed out when ping

Hi, I'm using the cisco 837 router as my VPN server. I get connected using Cisco VPN Client Version 5. But when I ping the router ip, i get request timed out. Here is my configuration :
Building configuration...
Current configuration : 3704 bytes
version 12.4
no service pad
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
hostname michael
boot-start-marker
boot-end-marker
memory-size iomem 5
no logging console
enable secret 5 $1$pZLW$9RZ8afI8QdGRq0ssaEJVu0
aaa new-model
aaa authentication login default local
aaa authentication login sdm_vpn_xauth_ml_1 local
aaa authorization exec default local
aaa authorization network sdm_vpn_group_ml_1 local
aaa session-id common
resource policy
ip subnet-zero
no ip dhcp use vrf connected
ip dhcp excluded-address 192.168.1.1
ip dhcp pool michael
   network 192.168.1.0 255.255.255.0
   default-router 192.168.1.1
   dns-server 202.134.0.155
ip dhcp pool excluded-address
   host 192.168.1.4 255.255.255.0
   hardware-address 01c8.d719.957a.b9
ip cef
ip name-server 202.134.0.155
ip name-server 203.130.193.74
vpdn enable
username michael privilege 15 secret 5 $1$ZJQu$KDigCvYWKkzuzdYHBEY7f.
username danny privilege 10 secret 5 $1$BDs.$Ez0u9wY7ywiBzVd1ECX0N/
crypto isakmp policy 1
encr 3des
authentication pre-share
group 2
crypto isakmp xauth timeout 15
crypto isakmp client configuration group michaelvpn
key vpnpassword
pool SDM_POOL_1
acl 199
netmask 255.255.255.0
crypto ipsec transform-set ESP-3DES-SHA esp-3des esp-sha-hmac
crypto dynamic-map SDM_DYNMAP_1 1
set transform-set ESP-3DES-SHA
crypto map SDM_CMAP_1 client authentication list sdm_vpn_xauth_ml_1
crypto map SDM_CMAP_1 isakmp authorization list sdm_vpn_group_ml_1
crypto map SDM_CMAP_1 client configuration address respond
crypto map SDM_CMAP_1 65535 ipsec-isakmp dynamic SDM_DYNMAP_1
interface Ethernet0
description $FW_INSIDE$
ip address 192.168.1.1 255.255.255.0
ip nat inside
ip virtual-reassembly
ip tcp adjust-mss 1452
hold-queue 100 out
interface Ethernet2
no ip address
shutdown
hold-queue 100 out
interface ATM0
no ip address
no atm ilmi-keepalive
dsl operating-mode auto
pvc 0/35
pppoe-client dial-pool-number 1
interface FastEthernet1
duplex auto
speed auto
interface FastEthernet2
duplex auto
speed auto
interface FastEthernet3
duplex auto
speed auto
interface FastEthernet4
duplex auto
speed auto
interface Virtual-PPP1
no ip address
interface Dialer1
description $FW_OUTSIDE$
mtu 1492
ip address negotiated
ip nat outside
ip virtual-reassembly
encapsulation ppp
dialer pool 1
ppp chap hostname ispusername
ppp chap password 0 isppassword
ppp pap sent-username ispusername password 0 isppassword
crypto map SDM_CMAP_1
ip local pool SDM_POOL_1 192.168.2.1 192.168.2.5
ip classless
ip route 0.0.0.0 0.0.0.0 Dialer1
ip http server
no ip http secure-server
ip nat inside source static udp 192.168.1.0 1723 interface Dialer1 1723
ip nat inside source static tcp 192.168.1.4 21 interface Dialer1 21
ip nat inside source route-map SDM_RMAP_1 interface Dialer1 overload
access-list 1 remark SDM_ACL Category=16
access-list 1 permit 192.0.0.0 0.255.255.255
access-list 102 remark SDM_ACL Category=2
access-list 102 deny   ip 192.168.1.0 0.0.0.255 192.168.2.0 0.0.0.255
access-list 102 permit ip 192.168.1.0 0.0.0.255 any
access-list 199 permit ip 192.168.1.0 0.0.0.255 192.168.2.0 0.0.0.255
route-map SDM_RMAP_1 permit 1
match ip address 102
control-plane
banner motd ^C
Authorized Access Only
UNAUTHORIZED ACCESS TO THIS DEVICE IS PROHIBITED
You must have explicit permission to access this device.
All activities performed on this device are logged.
Any violations of access policy will result in disciplinary action.
^C
line con 0
no modem enable
line aux 0
line vty 0 4
scheduler max-task-time 5000
end
Thank you, anny help will be appreciated.

Thank you for your response, here is the debug :
Log Buffer (4096 bytes):
1 15:19:47.011: ISAKMP: set new node 856647599 to QM_IDLE
May 1 15:19:47.015: ISAKMP:(0:8:SW:1):Sending NOTIFY DPD/R_U_THERE_ACK protocol 1
     spi 2182802952, message ID = 856647599
May 1 15:19:47.015: ISAKMP:(0:8:SW:1): seq. no 0xA3285B8A
May 1 15:19:47.015: ISAKMP:(0:8:SW:1): sending packet to 120.168.1.24 my_port 4500 peer_port 52667 (R) QM_IDLE
May 1 15:19:47.019: ISAKMP:(0:8:SW:1):purging node 856647599
May 1 15:19:47.019: ISAKMP:(0:8:SW:1):Input = IKE_MESG_FROM_PEER, IKE_MESG_KEEP_ALIVE
May 1 15:19:47.019: ISAKMP:(0:8:SW:1):Old State = IKE_P1_COMPLETE New State = IKE_P1_COMPLETE
May 1 15:19:49.979: %SYS-2-BADSHARE: Bad refcount in pak_enqueue, ptr=81B4F274, count=0
-Traceback= 0x80137488 0x801DC350 0x801DDDA8 0x801E6860 0x807103F4 0x807F99F8 0x801E698C 0x8043FB10 0x8043FDC8 0x80D23CD0 0x80D24304 0x80D24400 0x8027B3C4 0x8027E9E0
May 1 15:19:49.983: %SYS-2-BADSHARE: Bad refcount in datagram_done, ptr=81B4F274, count=0
-Traceback= 0x80137488 0x801D8830 0x801DDFD8 0x801E6860 0x807103F4 0x807F99F8 0x801E698C 0x8043FB10 0x8043FDC8 0x80D23CD0 0x80D24304 0x80D24400 0x8027B3C4 0x8027E9E0
May 1 15:19:55.127: %SYS-2-BADSHARE: Bad refcount in pak_enqueue, ptr=81B51C44, count=0
-Traceback= 0x80137488 0x801DC350 0x801DDDA8 0x801E6860 0x807103F4 0x807F99F8 0x801E698C 0x8043FB10 0x8043FDC8 0x80D23CD0 0x80D24304 0x80D24400 0x8027B3C4 0x8027E9E0
May 1 15:19:55.127: %SYS-2-BADSHARE: Bad refcount in datagram_done, ptr=81B51C44, count=0
-Traceback= 0x80137488 0x801D8830 0x801DDFD8 0x801E6860 0x807103F4 0x807F99F8 0x801E698C 0x8043FB10 0x8043FDC8 0x80D23CD0 0x80D24304 0x80D24400 0x8027B3C4 0x8027E9E0
May 1 15:19:58.383: ISAKMP (0:134217736): received packet from 120.168.1.24 dport 4500 sport 52667 Global (R) QM_IDLE
May 1 15:19:58.383: ISAKMP: set new node -1340288848 to QM_IDLE
May 1 15:19:58.387: ISAKMP:(0:8:SW:1): processing HASH payload. message ID = -1340288848
May 1 15:19:58.387: ISAKMP:(0:8:SW:1): processing NOTIFY DPD/R_U_THERE protocol 1
     spi 0, message ID = -1340288848, sa = 81A7DCEC
May 1 15:19:58.387: ISAKMP:(0:8:SW:1):deleting node -1340288848 error FALSE reason "Informational (in) state 1"
May 1 15:19:58.387: ISAKMP:(0:8:SW:1):Input = IKE_MESG_FROM_PEER, IKE_INFO_NOTIFY
May 1 15:19:58.387: ISAKMP:(0:8:SW:1):Old State = IKE_P1_COMPLETE New State = IKE_P1_COMPLETE
May 1 15:19:58.391: ISAKMP:(0:8:SW:1):DPD/R_U_THERE received from peer 120.168.1.24, sequence 0xA3285B8B
May 1 15:19:58.391: ISAKMP: set new node -752454119 to QM_IDLE
May 1 15:19:58.395: ISAKMP:(0:8:SW:1):Sending NOTIFY DPD/R_U_THERE_ACK protocol 1
     spi 2182802952, message ID = -752454119
May 1 15:19:58.395: ISAKMP:(0:8:SW:1): seq. no 0xA3285B8B
May 1 15:19:58.395: ISAKMP:(0:8:SW:1): sending packet to 120.168.1.24 my_port 4500 peer_port 52667 (R) QM_IDLE
May 1 15:19:58.399: ISAKMP:(0:8:SW:1):purging node -752454119
May 1 15:19:58.399: ISAKMP:(0:8:SW:1):Input = IKE_MESG_FROM_PEER, IKE_MESG_KEEP_ALIVE
May 1 15:19:58.399: ISAKMP:(0:8:SW:1):Old State = IKE_P1_COMPLETE New State = IKE_P1_COMPLETE
May 1 15:19:59.887: %SYS-2-BADSHARE: Bad refcount in pak_enqueue, ptr=81B51C44, count=0
-Traceback= 0x80137488 0x801DC350 0x801DDDA8 0x801E6860 0x807103F4 0x807F99F8 0x801E698C 0x8043FB10 0x8043FDC8 0x80D23CD0 0x80D24304 0x80D24400 0x8027B3C4 0x8027E9E0
May 1 15:19:59.887: %SYS-2-BADSHARE: Bad refcount in datagram_done, ptr=81B51C44, count=0
-Traceback= 0x80137488 0x801D8830 0x801DDFD8 0x801E6860 0x807103F4 0x807F99F8 0x801E698C 0x8043FB10 0x8043FDC8 0x80D23CD0 0x80D24304 0x80D24400 0x8027B3C4 0x8027E9E0
May 1 15:20:05.667: %SYS-2-BADSHARE: Bad refcount in pak_enqueue, ptr=81F84148, count=0
-Traceback= 0x80137488 0x801DC350 0x801DDDA8 0x801E6860 0x807103F4 0x807F99F8 0x801E698C 0x8043FB10 0x8043FDC8 0x80D23CD0 0x80D24304 0x80D24400 0x8027B3C4 0x8027E9E0
May 1 15:20:05.667: %SYS-2-BADSHARE: Bad refcount in datagram_done, ptr=81F84148, count=0
-Traceback= 0x80137488 0x801D8830 0x801DDFD8 0x801E6860 0x807103F4 0x807F99F8 0x801E698C 0x8043FB10 0x8043FDC8 0x80D23CD0 0x80D24304 0x80D24400 0x8027B3C4 0x8027E9E0
After searching thru the internet, I've found :
CSCsb46264
Symptoms: When a dialer interface is configured as an endpoint for a IPSec+GRE tunnel, tracebacks with bad refcount may be generated.
Conditions: This symptom is observed on a Cisco 837 when router-generated packets such as routing updates are being switched.
Is that possible that the root of the problem was that ? Thank you.

Error: Network Connection Timed Out

I am beyond ****** off at the moment. My iTunes was working perfectly until two weeks ago, and now it insists my Network Connection Timed Out when I try to access the store or update podcasts.
It can't be my internet connection, because as you can see, I'm able to access the internet. For some reason it's this specific copy of iTunes (7.5), because the iT7 downstairs works perfectly. Of course, since Apple are so fecking stingy, I can't add a few files from there without wiping everything off my iPod.
So here's the run-down:
I'm using a Dell Inspiron 8600, Windows XP, browsing with Firefox and attempting to load the latest podcasts onto my iPod Shuffle. I don't give a toss about downloading songs, I just want to update my podcasts without having to search the net for the source file.
I ran the Network Diagnostics and it insists the Conneciton to iTunes failed, suggesting I adjust my cable (i don't have one - it's wireless) or flush my dns settings (which i've done several times).
I found a thread on these forums from March and tried every solution:
- uninstalling and reinstalling itunes... doesn't work.
- opening Internet Explorer 7, then opening iTunes... doesn't work.
- searching for a host file and removing the phobos apple line... doesn't work. The phobos line wasn't there
- using itunes 7... doesn't work.
- flushing my dns... doesn't work.
- turning off my firewall.... doesn't work.
- avoiding clashes with mcafee or zone alarm... doesn't work, cos i don't use those
I think it's appalling that I've tried all this, and i'm still no closer to knowing what the problem is, and that Apple failed to respond to any of the other people's problems in the earlier thread. And that i spent about ten minutes signing up to this fecking forum just to ask for help. Surely support should be readily available to anyone!
Can anybody help me? In the other thread, people found alternative sites for buying music, but has anyone got an alternative, ipod-compatible podcasting program?

I have this same problem. Here's what I can add to this discussion - iTunes accessed the iTunes store a day or two ago. I have a home network and can access the internet from all of the networked PCs. I can access the iTunes store from all of the networked PCs using Internet Explorer. I can access the iTunes store from my laptop iTunes. I can not access the iTunes store from my workstation PC. I get the same "network connection timed out" message. I downloaded and installed a new (same version) of iTunes on the workstation PC. both the laptop and the workstation are running the same OS (Windows XP SP2), both are Dell computers, both are accessing the internet via a wired connection to the same switch and the same router. All other internet connections work fine.
What's different? In the last couple of days my Workstation lost access to a network printer. I worked with HP for over an hour to re-establish network connection to that printer with no success. I have access to the same networked printer from my laptop.
The IP address for the network printer is identical to what it was when it was installed - HP suggests looking for a change to the IP address. I made no changes to the workstation PC, the home network or the router, ISP, or internet connection.
But, it seems to me that the loss of access to the HP networked printer and the inability of iTunes to access the iTunes store are related.
I also called Apple and attempted to get technical support. I own 4 iPods with 104 Gbs of storage on them, I own 1900 CDs and iTunes has 36.5 days of music loaded into it.
I purchased Apple Care on all of the iPods - it's expired and they never warned me. They want to charge me $29 to fix this problem - even though I no longer can purchase music via the iTunes Store, so I need to pay $29 in order to gain access to the iTunes store to spend more money with Apple?! Not a smart business decision. I own a few other PC based music programs and more than willing to transfer all of it out of iTunes and into one of the other products. I'll sell all the iPods on eBay and purchase other MP3 players if I must.
But, I suspect the problem is (1) Apple doesn't have a documented answer to this problem, (2) the level 1 techs that answer the support phone are clueless - they just e-mailed me the same article from the Apple website that I told them I read and does not apply to my problem, and obviously does not resolve my problem. (3) Apple is not setup to resolve this type of problem with their level 1 support, and they can't escalate the problem without charging us.
I'll try again on Monday, may even purchase Apple Care first and then use that. The Apple Care Tech Support is typically better than the free level 1 call in support.
Suggestions, comments, etc. are all appreciated.
nlc
<SCRIPT language=JavaScript>

</SCRIPT>

Request Timed Out when server is plugged in!

jonathanmendez wrote:
1 - Error - DNS-Server-Service 404
The DNS server could not bind a transmission Control Protocol (TCP) scoket to address 10.10.10.3. The event data is the error code. An IP address of 0.0.0.0 can indicate a valid "any address" configuration in which all configured IP addresses on the computer are available for use. Restart the DNS server or reboot the computer.
Does the DNS Service stop?
Can you confirm that no other application is listening on port 53?
Also, what is handling DHCP?

So I am facing the weirdest network/server problem ever!I have a customer which had a Supermicro server (Was there before me!). It was never used and they didn't know the password so i decided to format and re-install Windows Server 2012 R2 on it. I promoted it to a new domain and setup Windows Essentials so I could setup RDWeb for them quickly. They were up and running great. I also installed Trend Micro on the server and pushed it out to the client PC's. A little more info about my network before i get into the gritty. I have Brighthouse cable 35Mbps as an ISP with an ARRIS modem, a Ubiquiti Edgerouter Lite as my firewall and a cisco sg200-26 as my core switch. It's not a big location. We randomly started getting request timed out at the gateway level and the firewall level from outside and internet was dropping. We worked for weeks...
This topic first appeared in the Spiceworks Community

500 Connection timed out

Hello,
I receive a 500 Connection timed out error.
I know that there are some threads to this error but I can´t find a solution for us.
This is the error description:
Error:            -5
Version:        7000
Component: ICM
Date/Time:    Tue Mar 04 07:02:38 2008
Module:        icxxthr.c
Line:             2698
Server:         crmprod_CRP_01
Error Tag:     {-}
Detail:          Connection to partner timed out after 60s
Now I have found in this forum some information about the parameters icm/keep_alive_timeout, icm/conn_timeout and icm/server_port_*
Our settings for this parameters are:
icm/server_port_0 = PROT=HTTP,PORT=8001
icm/server_port_1 = PROT=SMTP,PORT=25
icm/keep_alive_timeout (sec.) = 600
icm/conn_timeout (msec.) = 5000
Can someone please explain me which parameters occurs this error and which parameters I can change that the connection time is longer than 60 seconds?
Where can I change the parameters?
Regards
Philipp

Hi,
Parameter icm/conn_timeout
icm/conn_timeout is used to set the timeout when setting up the connection. If the timeout is exceeded, an error page is generally displayed with the information "404 Resource not found" "Partner not reached".
Therefore, exceeding the icm/conn_timeout does not lead to a "500 Connection timed out" error message.
Processing timeout and keepalive timeout
The icm/keep_alive_timeout and icm/server_port_< n > parameters define the keepalive timeout and the processing timeout.
ICM distinguishes between these two types of timeout.
The processing timeout is the timeout between the HTTP request being issued and the HTTP response being received.
If the ICM is used as a server for the relevant HTTP request (in other words, when it forwards an incoming request to the SAP Web Application Server), the processing timeout is the time that the ICM will wait until a response is received from the SAP Web Application Server (ABAP or J2EE). This interval may be exceeded with long-running applications in ABAP or the J2EE engine. If the processing timeouts are exceeded, the ICM sends the client an HTTP response with the error code "500 Connection timed out".
If the ICM serves as a client for the relevant HTTP request (that is, when it forwards outgoing requests from the SAP Web Application Server), the processing timeout is the time that the ICM waits until a response is received from the network. This interval may also be exceeded in the case of long-running applications in the network.
The keepalive timeout specifies how long the network should remain open after a request has been processed successfully so that the TCP/IP connection does not have to be reestablished if additional requests are received.
When you set the keepalive timeout, this does not normally lead to timeout errors. You should set the keepalive timeout high enough that the connection does not have to be reestablished for requests that are sent within a short time of each other, but low enough that the number of unused open TCP/IP connections is not unnecessarily high. Exceeding the Keepalive timeout should never cause an error.
Configuration of the ICM parameters for the processing timeout and the keepalive timeout
For the ICM, the parameters mentioned here are in the instance profile.
The processing timeout is set for individual services with the following parameter:
icm/server_port_ < n > = ...,PROCTIMEOUT=< s >.
The keepalive timeout can be set globally for all services of the ICM with the parameter icm/keepalive_timeout.
You can also set it for individual services by using the following parameter:
icm/server_port_ < n > = ...,TIMEOUT=< s >.
If you set this parameter, it overwrites parameter icm/keepalive_timeout for the specified service.
Even if the ICM serves as client for a request, the TIMEOUT and PROCTIMEOUT parameters of icm/server_port_ < n > control the timeouts for the relevant protocol, provided that you have set TIMEOUT or PROCTIMEOUT.
If you have not set the PROCTIMEOUT parameter, TIMEOUT (or icm/keepalive_timeout) defines both the processing timeout and the keepalive timeout. Also, as of release 6.40, the keepalive timeout is limited to a maximum of 30 seconds.
In a system where the default timeout settings of 30 seconds for the keepalive timeout and the processing timeout are not sufficient because of long-running applications, we recommend that you set the TIMEOUT and PROCTIMEOUT parameters for the relevant services so that you can configure them independently of each other. In addition, we recommend that you do not set the TIMEOUT value higher than necessary, for example, to the usual default value of 30 seconds.
We recommend, for example, the following settings:
icm/server_port_0 = PROT=HTTP,PORT=1080,TIMEOUT=30,PROCTIMEOUT=600
to allow a maximum processing time of 10 minutes.
I hope this info will help you to sort out the error you getting.
Regards
Aashish Sinha
PS : reward points if helpful

Io_getevents timed out 600 sec

We have one server with OEL5.5 and two oracle databases 10.2.0.4. We are using nfs for the databases. There were no errors about a long time.
Both of these databases hung on weekend after an automatic restart with the same error for 12 hours, no connection possible:
Fri May 20 21:18:39 2011
Completed: ALTER DATABASE OPEN
Fri May 20 21:29:13 2011
WARNING:io_getevents timed out 600 sec
Fri May 20 21:29:14 2011
WARNING:io_getevents timed out 600 sec
Fri May 20 21:39:13 2011
WARNING:io_getevents timed out 600 sec
Fri May 20 21:39:14 2011
WARNING:io_getevents timed out 600 sec
Fri May 20 21:49:13 2011
WARNING:io_getevents timed out 600 sec
Fri May 20 21:49:14 2011
After 12 hours both databases are online back again without doing anything.
In my opinion (and with the help of metalink) i think this is os- and not db-related, but there an no errors at all on os level (/var/log/messages). Ideas?
Thank you!

Then it's really strange. How about a problem with the network, if the network was involved? If there was some network congestion it may not necessarily show up as an error in the NFS logs. Are you managing the network? From my experience, If you have a fancy network and i.e Cisco equipment, administrators often like to play around on weekends and evenings or during other system maintenance windows, not necessarily informing since it is not supposed to interfere. Of course the problem could also be with your systems or the NFS server you mentioned. I would leave the problem for now and monitor the next system restart to see if it happens again. If it does, then you have more options to analyze and troubleshoot, e.g. power reset.
Edited by: Dude on Jun 7, 2011 2:31 AM

TAC+: TCP/IP open to 10.20.17.2/49 failed -- Connection timed out; remote host not responding

TACACS+ configured on router and router is in ACS. I can ping the ACS but the router cannot establish a connection to authenticate users.
aaa group server tacacs+ hq_acs-1
server 10.20.17.2
ip tacacs source-interface GigabitEthernet0/0
aaa authentication login default group tacacs+ local
aaa authorization config-commands
aaa authorization exec default group tacacs+ local
aaa authorization commands 10 default group tacacs+ local
aaa authorization commands 15 default group tacacs+ local
aaa accounting nested
aaa accounting update newinfo periodic 60
aaa accounting auth-proxy default start-stop group tacacs+
aaa accounting exec default start-stop group tacacs+
aaa accounting commands 15 default start-stop group tacacs+
aaa accounting network default start-stop group tacacs+
aaa accounting connection default start-stop group tacacs+
aaa accounting system default start-stop group tacacs+
aaa accounting resource default start-stop group tacacs+
BigTree_3945#sh ip int br
Interface                  IP-Address      OK? Method Status                Protocol
GigabitEthernet0/0         10.4.3.1        YES NVRAM down                  down
GigabitEthernet0/1         10.12.10.26     YES NVRAM up                    up
Serial0/2/0                unassigned      YES NVRAM down                  down
Serial0/2/0.602            10.12.15.10     YES NVRAM down                  down
Apr 13 11:08:13.673: TPLUS: Queuing AAA Authentication request 79 for processing
Apr 13 11:08:13.673: TPLUS: processing authentication start request id 79
Apr 13 11:08:13.675: TPLUS: Authentication start packet created for 79(cisscdb)
Apr 13 11:08:13.675: TPLUS: Using server 10.20.17.2
Apr 13 11:08:13.675: TPLUS(0000004F)/0/NB_WAIT/1BDD9C34: Started 5 sec timeout
Apr 13 11:08:18.676: TPLUS(0000004F)/0/NB_WAIT/1BDD9C34: timed out
Apr 13 11:08:18.676: TPLUS(0000004F)/0/NB_WAIT/1BDD9C34: timed out, clean up
Apr 13 11:08:18.676: TPLUS(0000004F)/0/1BDD9C34: Processing the reply packet
Apr 13 11:08:25.834: TPLUS: Queuing AAA Authentication request 79 for processing
Apr 13 11:08:25.834: TPLUS: processing authentication start request id 79
Apr 13 11:08:25.834: TPLUS: Authentication start packet created for 79(cisscdb)
Apr 13 11:08:25.834: TPLUS: Using server 10.20.17.2
Apr 13 11:08:25.834: TPLUS(0000004F)/0/NB_WAIT/1BDD9C34: Started 5 sec timeout
Apr 13 11:08:30.836: TPLUS(0000004F)/0/NB_WAIT/1BDD9C34: timed out
Apr 13 11:08:30.836: TPLUS(0000004F)/0/NB_WAIT/1BDD9C34: timed out, clean up
Apr 13 11:08:30.836: TPLUS(0000004F)/0/1BDD9C34: Processing the reply packet
Apr 13 11:08:43.689: TAC: Using default tacacs server-group "tacacs" list.
Apr 13 11:08:43.689: TAC+: Opening TCP/IP to 10.20.17.2/49 timeout=5
Apr 13 11:08:51.057: TPLUS: Queuing AAA Authentication request 79 for processing
Apr 13 11:08:51.057: TPLUS: processing authentication start request id 79
Apr 13 11:08:51.057: TPLUS: Authentication start packet created for 79(cisscdb)
Apr 13 11:08:51.057: TPLUS: Using server 10.20.17.2
Apr 13 11:08:51.057: TPLUS(0000004F)/0/NB_WAIT/1BDD9C34: Started 5 sec timeout
Apr 13 11:08:54.692: TAC+: TCP/IP open to 10.20.17.2/49 failed -- Connection timed out; remote host not responding
Apr 13 11:08:54.692: TPLUS: Queuing AAA Accounting request 76 for processing
Apr 13 11:08:54.692: TPLUS: processing accounting request id 76
Apr 13 11:08:54.692: TPLUS: Sending AV task_id=332
Apr 13 11:08:54.692: TPLUS: Sending AV timezone=EDT
Apr 13 11:08:54.692: TPLUS: Sending AV service=shell
Apr 13 11:08:54.692: TPLUS: Sending AV start_time=1334329734
Apr 13 11:08:54.692: TPLUS: Sending AV priv-lvl=15
Apr 13 11:08:54.692: TPLUS: Sending AV cmd=show logging <cr>
Apr 13 11:08:54.692: TPLUS: Accounting request created for 76(n20j03t)
Apr 13 11:08:54.692: TPLUS: Using server 10.20.17.2
Apr 13 11:08:54.692: TPLUS(0000004C)/1/NB_WAIT/20FD90EC: Started 5 sec timeout
Apr 13 11:08:56.058: TPLUS(0000004F)/0/NB_WAIT/1BDD9C34: timed out
Apr 13 11:08:56.058: TPLUS(0000004F)/0/NB_WAIT/1BDD9C34: timed out, clean up
Apr 13 11:08:56.058: TPLUS(0000004F)/0/1BDD9C34: Processing the reply packet
Apr 13 11:08:59.693: TPLUS(0000004C)/1/NB_WAIT/20FD90EC: timed out
Apr 13 11:08:59.693: TPLUS(0000004C)/1/NB_WAIT/20FD90EC: timed out, clean up
Apr 13 11:08:59.693: TPLUS(0000004C)/1/20FD90EC: Processing the reply packet
BigTree_3945#
AAA Client IP Address
10.4.3.* 10.12.15.10
Key
Network Device Group
Test
NJT
AccessLink
(Not Assigned)
Authenticate Using
TACACS+ (Cisco IOS)
RADIUS (Cisco Aironet)
RADIUS (Cisco BBSM)
RADIUS (Cisco IOS/PIX)
RADIUS (Cisco VPN 3000)
RADIUS (Cisco VPN 5000)
RADIUS (IETF)
RADIUS (Ascend)
RADIUS (Juniper)
RADIUS (Nortel)
RADIUS (iPass)
Single Connect TACACS+ AAA Client (Record stop in accounting on failure).
The 10.12.10.* range is listed under the HQ site.
Your help is greatly appreciated.

You stated that you can ping ACS from the router, did you try sourcing the packets from the GigabitEthernet 0/0 interface (which is the one TACACS+ will try to use, given the configuration that you posted)?
What does the network path between the router and ACS look like (ie, any firewalls, NAT, etc)?
Can you connect to port 49 at the ACS IP address from the router sourcing the packets from GigabitEthernet 0/0 ?
Are you using VRFs?
What version of IOS?

Connection timed out, when server is present in far-off place

We have a web application on JBoss-3.2.3. It makes use of Applets. To paint the applet, a request is sent to a server using a HttpURLConnection. Evertyhing works fine when the browser(client) and the server are on the same network. However, if the client(browser) is in Australia and the server in India(i.e. long distance between server and client), then the Applet crashes with a Connection timed out exception. Any solution for this?
The code looks something like:
URL url = new URL(urlString);
HttpURLConnection connection = (HttpURLConnection) url.openConnection();
connection.setDoOutput(true);
connection.connect();

So I am facing the weirdest network/server problem ever!I have a customer which had a Supermicro server (Was there before me!). It was never used and they didn't know the password so i decided to format and re-install Windows Server 2012 R2 on it. I promoted it to a new domain and setup Windows Essentials so I could setup RDWeb for them quickly. They were up and running great. I also installed Trend Micro on the server and pushed it out to the client PC's. A little more info about my network before i get into the gritty. I have Brighthouse cable 35Mbps as an ISP with an ARRIS modem, a Ubiquiti Edgerouter Lite as my firewall and a cisco sg200-26 as my core switch. It's not a big location. We randomly started getting request timed out at the gateway level and the firewall level from outside and internet was dropping. We worked for weeks...
This topic first appeared in the Spiceworks Community

Tuxedo 6.5 Timed out error is locking up the server

Hello all,
I am hoping someone will be able to help me with my problem.
When a client tries some updates using our software, they get the following error
message:
"Timed out waiting for server to acknowledge attention"
Any subsequent processing on this server causes the following messages:
"Attempt to initiate a new SQL Server operation with results pending"
"Unable to Rollback() monitor:'AmsDatabaseConnection'! due to unknown exception!"
"Cannot perform more than one read"
As best as I can tell (which could be wrong), this only occurs to specific clients
that have to go through a firewall. However once those clients encounter the
original problem, everyone is affected.
I don't what is causing the problem. The only way I am able to "fix" the problem
is by restarting the servers. Is there a way for tuxedo to clean up these processes?
Under tmadmin on the server, there is nothing running on the offending servers,
there are no messages in the queue. I do not know what could be the problem.
I have added the -K both flag to the WSL, and I have also added the -N flag to
the WSL, I have also increased the BLOCKTIME to allow the client processes more
time to work. HOwever, none of these changes seem to work.
In the client's ULOG are the following messages:
1065 ERROR: Unable to close WSH connection
1025 ERROR: Unable to send tpterm() request
Any help or suggestions would be greatly appreciated, as I have been pulling my
hair out trying to figure this out.
- Ted

Ted,
The error you posted below is not a Tuxedo error. It is your application error, in
response to some Tuxedo error code, I would imagine.
The WSL has a -K option to turn on Keepalive at the network level. This can keep a
firewall from disconnecting due to lack of traffic.
The SQL errors are from the sequence of operations that your are executing from
your application code. Unless you are using transactions, the database can not
distinguish one service request from the next. The database simply receives a
comtinuing series of requests. It looks like it never cleaned up from the previous
service call.
As Wayne suggested, TMTRACE might show you the sequence of Tuxedo operations
interleaved with your application errors, so that you can better track down what
has happened.
Scott Orshan
Ted Unnikumaran wrote:
Hello all,
I am hoping someone will be able to help me with my problem.
When a client tries some updates using our software, they get the following error
message:
"Timed out waiting for server to acknowledge attention"
Any subsequent processing on this server causes the following messages:
"Attempt to initiate a new SQL Server operation with results pending"
"Unable to Rollback() monitor:'AmsDatabaseConnection'! due to unknown exception!"
"Cannot perform more than one read"
As best as I can tell (which could be wrong), this only occurs to specific clients
that have to go through a firewall. However once those clients encounter the
original problem, everyone is affected.
I don't what is causing the problem. The only way I am able to "fix" the problem
is by restarting the servers. Is there a way for tuxedo to clean up these processes?
Under tmadmin on the server, there is nothing running on the offending servers,
there are no messages in the queue. I do not know what could be the problem.
I have added the -K both flag to the WSL, and I have also added the -N flag to
the WSL, I have also increased the BLOCKTIME to allow the client processes more
time to work. HOwever, none of these changes seem to work.
In the client's ULOG are the following messages:
1065 ERROR: Unable to close WSH connection
1025 ERROR: Unable to send tpterm() request
Any help or suggestions would be greatly appreciated, as I have been pulling my
hair out trying to figure this out.
- Ted

Timed Out using iPad

When using GoodReader App on the iPAd to access our Mac server from another location I get timed out, any suggestions?

I would suggest....
1. Going to Settings>Safari, and then deleting cookies and data
2. Then going to your home screen. Double click the home button, a shelf should appear at the bottom of the screen. - Hold your finger on the first app on the bottom shelf until it starts to shake. Once they are shaking, tap the Red circle with the white minus sign in it in the upper left corner of each app on the shelf until they are all closed. Note - this will NOT delete the apps, only close those running in the background.
3. Restart the device (hold sleep/wake button until you see a red "slide to power off" slider. Power down iPad. Then when screen is black, turn back on normally.
4. Try again.
5. If issue persists, if you have a cellular model, you'll probably want to try using cellular data instead of wifi to connect, turn Wifi to OFF in settings>wifi, then try again.
6. After this go back to settings>wifi and turn it back on
7. If using cellular didnt work, try again, now that wifi has been turned off then back on.
8. if still doesnt work, reset network settings, (will need to reenter you wifi passcode if you do this). You can reset these by going to Settings>General>Reset>Reset network settings. This will restart your iPad so dont be alarmed.
8. Try again.

The Opration timed out occurred on calling REST Service in Addin in windows 7 ultimate 64 bit

Hi,
I have created VSTO solution for Outlook Addin in Visual studio 2010.
In that on button it will call Java REST webservice and validating the username and password.
Evrything working fine in few systems.But it showing "The operation timed out" in WIndows 7 64 bit office 2013.
In other windows 7 machine with office 2010 and 2007 its working perfectly.
Below is the code :
var responseMessage = (String)null;
var request = WebRequest.Create(string.Concat(serviceUrl, resourceUrl)) as HttpWebRequest;
if (request != null)
request.ContentType = "application/xml";
request.MediaType = "text/xml";
request.Method = method;
request.keepalive=false;
request.ContentLength = xmlRequestBody.Length;
ServicePointManager.Expect100Continue = false;
//var objContent = HttpContentExtensions.CreateDataContract(requestBody);
if (method == "POST" && xmlRequestBody != null)
byte[] requestBodyBytes = ASCIIEncoding.UTF8.GetBytes(xmlRequestBody.ToString());
request.ContentLength = requestBodyBytes.Length;
using (Stream postStream = request.GetRequestStream())
postStream.Write(requestBodyBytes, 0, requestBodyBytes.Length);
if (request != null)
request.Credentials = new NetworkCredential("Username", "password");
//request.ProtocolVersion = HttpVersion.Version11;
var response = request.GetResponse() as HttpWebResponse;
if (response.StatusCode == HttpStatusCode.OK)
Stream responseStream = response.GetResponseStream();
if (responseStream != null)
var reader = new StreamReader(responseStream);
responseMessage = reader.ReadToEnd();
else
responseMessage = response.StatusDescription;
return responseMessage;
Could you please help what could be the reason.Any firewall issue or any serviced related issue.Kidly suggest.

Hi,
I have created the windows application using REST Service and tested the application on
windows 7 64 bit Ultimate edition but I'm getting the same error "The
operation timed out" attached the screen shot for your reference.
http://www.screencast.com/t/YeIJxl383a
I developed the application on Windows 7 Ultimate 64 bit version it is working on my machine. while the executing exe on another windows 7 64 bit Ultimate
edition which is on the virutal machine Im getting the error.
There is no visual studio installed on the Virtual machine , i have installed the Dot Net frame work 4.0 client profile on the virtual machine.
Could you please suggest is there any issues related to opearating system or related to framework.
Kindly help with some suggestions.

Cisco CDN (Alarm 550001 (SEKeepalive) SE keepalive timed-out )

Similar Messages

Maybe you are looking for