cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
982
Views
0
Helpful
1
Replies

WSA went down for 5 mins

Sakun Sharma
Level 1
Level 1

Hi Guys,

 

One of my WSA went down for approximately 5 mins, i couldn't even ping on Proxy server IP address but was able to ping Management IP Address but very slow, many drops in that too. Within 5 mins everything automatically came up and worked fine.

 

Can you suggest me what logs i should look for to find the issue, logs are forwared and stored in SMA ftp server, so i can see few logs are missing during that time, and proxy logs shows:

Time around when it was not accessible :

Thu Jul 23 14:45:17 2015 Warning: WBRS : - : Couldn't find corresponding request for wbrsId: 52011427 This verdict will be ignored.
Thu Jul 23 14:45:17 2015 Info: PROXY : - : FastRPCClientSocketRead(WBRSD2): FastRPCProcessReadBuf failed: path=/data/tmp/wbrsd_fastrpc.sock.2 fd=95
Thu Jul 23 14:45:17 2015 Info: PROXY : - : FastRPCReset(WBRSD2): path=/data/tmp/wbrsd_fastrpc.sock.2 fd=95
Thu Jul 23 14:45:17 2015 Info: PROXY : - : FastRPCClientConnect(WBRSD2): connected: path=/data/tmp/wbrsd_fastrpc.sock.2 fd=95

 

When came up:

Thu Jul 23 14:48:25 2015 Info: PROX_AUTH : - : [DOMAIN]Added domain DOMAIN S-1-5-21-xxxxx
Thu Jul 23 14:48:25 2015 Info: PROX_AUTH : - : [WESLEYCOLLEGE.NET]Added domain IRONPORT S-1-5-21-xxxx
Thu Jul 23 14:48:25 2015 Info: PROX_AUTH : - : [WESLEYCOLLEGE.NET]Added domain BUILTIN  S-1-5-32
Thu Jul 23 14:48:25 2015 Info: PROXY : - : EarlyInit: _SC_IOV_MAX = 1024
Thu Jul 23 14:48:25 2015 Info: PROXY : - : EarlyInit: _SC_IOV_MAX = 512
Thu Jul 23 14:48:25 2015 Info: PROXY : - : Early Init AMP Engine

...

.

.

 

.

.

Thu Jul 23 14:48:27 2015 Info: PROXY : - : proxy initialization underway...
Thu Jul 23 14:48:27 2015 Info: PROXY : - : initialization complete - proxy running...
Thu Jul 23 14:48:27 2015 Info: PROXY : - : FastRPCClientConnect(UDSCLIENT): connected: path=/tmp/uds_fastrpc.sock fd=93
Thu Jul 23 14:48:27 2015 Info: PROXY : - : FastRPCClientConnect(WBRSD1): connected: path=/data/tmp/wbrsd_fastrpc.sock.1 fd=94
Thu Jul 23 14:48:27 2015 Info: PROXY : - : FastRPCClientConnect(WBRSD2): connected: path=/data/tmp/wbrsd_fastrpc.sock.2 fd=95
Thu Jul 23 14:48:27 2015 Info: PROXY : - : FastRPCClientConnect(WEBROOTCLIENT): connected: path=/tmp/webroot_fastrpc.sock fd=96
Thu Jul 23 14:48:27 2015 Info: PROXY : - : FastRPCClientConnect(WEBROOTURLSCANCLIENT): connected: path=/tmp/webroot_fastrpc_urlscan.sock fd=97
Thu Jul 23 14:48:27 2015 Info: PROXY : - : FastRPCClientConnect(SOPHOSCLIENT): connected: path=/tmp/sophos_fastrpc.sock fd=98
Thu Jul 23 14:48:27 2015 Info: PROXY : - : FastRPCClientConnect(FIRESTONECLIENT): connected: path=/tmp/firestone_fastrpc.sock fd=99
Thu Jul 23 14:48:27 2015 Info: PROXY : - : FastRPCClientConnect(ASCLIENT1): connected: path=/data/tmp/wbrsd_fastrpc.sock.1 fd=100
Thu Jul 23 14:48:27 2015 Info: PROXY : - : FastRPCClientConnect(ASCLIENT2): connected: path=/data/tmp/wbrsd_fastrpc.sock.2 fd=101
Thu Jul 23 14:48:27 2015 Info: PROXY : - : FastRPCClientConnect(OCSPDCLIENT): connected: path=/tmp/ocspd_fastrpc.sock fd=102
Thu Jul 23 14:48:27 2015 Info: PROXY : - : FastRPCClientConnect(SNMPMASTER): connected: path=/data/tmp/snmp_master.sock fd=103
Thu Jul 23 14:48:27 2015 Info: PROXY : - : FastRPCServerSocketAccept(WEBROOTSERVER): accepted: path=/tmp/webroot_cb_fastrpc.sock clientFd=105 listenFd=59
Thu Jul 23 14:48:27 2015 Info: HTTPS : - : Appliance ID for certificate signing is 62E64F9D
Thu Jul 23 14:48:28 2015 Info: PROXY : - : FastRPCServerSocketAccept(SOPHOSSERVER): accepted: path=/tmp/sophos_cb_fastrpc.sock clientFd=541 listenFd=61
Thu Jul 23 14:48:29 2015 Info: DISK_MGR : - : initialization process #0 exiting normally

 

I have also noticed that after that in System Capacity --> Proxy Buffer Memory (%) usage is 0%, before it was around 20-30%.

 

Any suggestion why this happened, or how can i troubleshoot this? Command line to check system status, disk status etc?

 

Regards,

Sakun

1 Reply 1

Sakun Sharma
Level 1
Level 1

Just as an update for other who got same problem, I opened a TAC case and after looking at the logs they said its a bug in the software.

Issue was identified as software defect CSCus10922, please find external description here:

https://tools.cisco.com/bugsearch/bug/CSCus10922

 

Suggested upgrade to 8.0.8-113 or 8.5.2-027.

 

Regards,

Sakun

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: