Jump to content


Photo

WSA 4.4.5 Suddenly Stopped Working

wsa offline bypass

  • Please log in to reply
1 reply to this topic

#1 Technical Services

Technical Services
  • Members
  • 1 posts

Posted 20 September 2017 - 11:55 AM

Anyone experienced issues with WSA 4.4.5 suddenly failing?

We experienced a problem when EVERY client stopped filtering and went into offline/bypass mode.

Logged with support and advised a Window Update had caused it to fail – but we hadn’t released any updates!

Upgrading to version WSA 5 fixes this issue but this is not so straight forward to deploy due to the .Net dependencies.

(We have .Net apps that need to be tested first for compatibility)

So far, we have had very little useful feedback from support and have just been advised to upgrade.

But for all clients to stop with no explanation worries me - could this happen again, even if we do upgrade?

 

For info these are the logs from the WSA client. 

 

09/13/17 09:05:42, BARRACUDAWSA.EXE started (V3.0.0.19)

09/13/17 09:05:42, Time since boot: 30217

09/13/17 09:05:42, OS: Windows 7 64bit

09/13/17 09:05:42, Going to load data

09/13/17 09:05:42, File MD5: 94ccb381a5eab8912ae77dd4e2379e51

09/13/17 09:05:42, Data loaded successfuly

09/13/17 09:05:42, Flag: dlltoload with value: C:\WINDOWS\syswow64\barracudawsadll64.dll

09/13/17 09:05:42, Data loaded successfuly

09/13/17 09:05:42 ** Error **, No default cert and no custom cert found!

09/13/17 09:05:42, CDLLManager, trying to load: C:\WINDOWS\syswow64\barracudawsadll64.dll

09/13/17 09:05:43 ** Error **, CDLLManager, DLLQueryData not found, it means first generation DLL that can't be queried

09/13/17 09:05:43 ** Error **, CDLLManager, DLLCanInterceptSSL not found, it means first generation DLL that can't be queried for SSL bypass

09/13/17 09:05:43, CDLLManager, DLL loaded successfuly

09/13/17 09:05:43, Trying to start UDP channel

09/13/17 09:05:43, Starting relay on port: 12344

09/13/17 09:05:43, Relay started successfuly

09/13/17 09:05:43, Statistics data loaded successfuly

09/13/17 09:05:43, Started as a service

09/13/17 09:05:43, Started main message loop

09/13/17 09:05:43 ** Error **, CWFP::SetPID - Failed to open file: 2

09/13/17 09:05:43 ** Error **, Failed to set PID for WFP: CWFP::SetPID - Failed to open file: 2

09/13/17 09:05:43, KeepAlive thread in standby

09/13/17 09:05:44 ** Error **, CWFP::UpdateWFPBadList - Failed to open file: 2

09/13/17 09:05:44 ** Error **, CWFP::HandleWFPExcludes - Failed to update WFP list with error: CWFP::UpdateWFPBadList - Failed to open file: 2

09/13/17 09:05:55 ** Error **, CWFP::UpdateWFPBadList - Failed to open file: 2

09/13/17 09:05:55 ** Error **, CWFP::HandleWFPExcludes - Failed to update WFP list with error: CWFP::UpdateWFPBadList - Failed to open file: 2

09/13/17 09:08:02, Going to call set enable (user called method): 0

09/13/17 09:08:03, Going to call set enable (user called method): 1

09/13/17 09:08:03, Going to save data (user called method)

09/13/17 09:08:03, Going to save data, caller is: user called method

09/13/17 09:08:03, Flag: dlltoload with value: C:\WINDOWS\syswow64\barracudawsadll64.dll

09/13/17 09:08:03, Data saved successfuly

09/13/17 09:08:08, Going to get table (user called method)

09/13/17 09:08:08, Going to get table (user called method)

09/13/17 09:08:08, Going to get table (user called method)

09/13/17 09:08:08, Going to get table (user called method)

09/13/17 09:08:08, Going to get table (user called method)

09/13/17 09:08:08, Going to clear data table (user called method)

09/13/17 09:08:08, Going to clear data table (user called method)

09/13/17 09:08:08, Going to commit data table (user called method)

09/13/17 09:08:08, Going to get table (user called method)

09/13/17 09:08:08, Going to clear data table (user called method)

09/13/17 09:08:08, Going to commit data table (user called method)

09/13/17 09:08:08, Going to commit data table (user called method)

09/13/17 09:08:08, Going to commit data table (user called method)

09/13/17 09:08:08, Going to commit data table (user called method)

09/13/17 09:08:08, Going to commit data table (user called method)

09/13/17 09:08:08, Going to save data (user called method)

09/13/17 09:08:08, Going to save data, caller is: user called method

09/13/17 09:08:08, Flag: dlltoload with value: C:\WINDOWS\syswow64\barracudawsadll64.dll

09/13/17 09:08:08, Data saved successfuly

09/13/17 09:08:08, Going to call set enable (user called method): 0

09/13/17 09:08:09, Going to call set enable (user called method): 0

09/13/17 09:08:09, Going to call set enable (user called method): 1

09/13/17 09:08:09, Going to save data (user called method)

09/13/17 09:08:09, Going to save data, caller is: user called method

09/13/17 09:08:09, Flag: dlltoload with value: C:\WINDOWS\syswow64\barracudawsadll64.dll

09/13/17 09:08:09, Data saved successfuly

09/13/17 09:08:09, Going to call set enable (user called method): 0



#2 Richard Lamphiear

Richard Lamphiear
  • Barracuda Team Members
  • 3 posts

Posted 20 September 2017 - 04:02 PM

Hi,

 

Unfortunately that log may not be the most useful one to look at in this case.  If the WSAs are having connectivity issues, the WSA.log is probably the one that may give clearer answers.

 

That having been said, these logs are very verbose and may not make a lot of sense to the layman.  I know this may be frustrating to hear, but my recommendation would be calling in to tech support again.  A tech should be able to help you figure out exactly what is going on with your WSAs but it will probably take more than just looking at the logs to do it.


Richard Lamphiear

Tier 2 Technical Support Representative

Barracuda Networks