topic WSA - Report Query Failed in Web Security

WSA - Report Query Failed

fermendo — Mon, 18 Jul 2011 16:45:42 GMT

Hi all,

Recently, I'm receiving these two alerts from one WSA S370:

Report Query Failed

query_id: wsa_monitor_overview_web_proxy_summary

data_source: WSASimpleTotalRDS

error: <type 'type'> ('egg/command_client.py send_message|555', "<class 'Commandment.DaemonUnresponsiveError'>", 'S370B.NAME.net: The daemon is not responding.', '[database/ReportCatalog.py run_report_queries|332] [reportdatasource/CounterReportDataSource.py query|265] [reportdatasource/CounterReportDataSource.py _parse_overall_interval|581] [query/merged_result.py range|85] [query/client.py _call|235] [egg/command_client.py call|233] [egg/command_client.py send_message|555]')

AND

Report Query Failed

query_id: wsa_monitor_overview_clients_by_blocked_transactions

data_source: WSACommonRDS

error: <type 'type'> ('egg/command_client.py call|238', "<class 'reporting.query.exceptions.DatabaseQueryFailure'>", '', '[database/ReportCatalog.py run_report_queries|332] [reportdatasource/CounterReportDataSource.py query|251] [reportdatasource/CounterReportDataSource.py _run_api_query|482] [query/client.py time_merge_query|454] [query/client.py _call|235] [egg/command_client.py call|238]')

The code I'm using is 7.1.1-038

I started receiving the alerts only after upgrading to this code. Have you noticed something similar?

Thanks a lot for your help!!!

Fernando

WSA - Report Query Failed

Tery Le Febvere — Tue, 19 Jul 2011 12:43:43 GMT

Hi,

FOr this type of issue we will need to conect via tunnel, please give us a call

Toll-Free Customer Support

United States: 1-877-641-IRON (4766)

International: www.ironport.com/support/contact_support.html

Thanks,

Tery Le Febvere

WSA - Report Query Failed

fermendo — Tue, 19 Jul 2011 22:26:42 GMT

Thanks a lot Tery

WSA - Report Query Failed

Lovedeep Marwah — Thu, 14 Jun 2012 04:28:41 GMT

Hello Everyone,

I am in Australia (Melbourne) and i am using ironport s160 web security appliance version: 7.1.2-80. Reecently i have started receiving the following warning from ironport proxy.

The Warning message is:

Report Query Failed

query_id: wsa_monitor_overview_malware_categories

data_source: WSACommonRDS

error: ('egg/command_client.py send_message|555', "", 'proxymel3.sportsbet.com.au: The daemon is not responding.', '[database/ReportCatalog.py run_report_queries|332] [reportdatasource/CounterReportDataSource.py query|265] [reportdatasource/CounterReportDataSource.py _parse_overall_interval|581] [query/merged_result.py range|85] [query/client.py _call|235] [egg/command_client.py call|233] [egg/command_client.py send_message|555]')

Report Query Failed

query_id: wsa_monitor_overview_suspect_transactions_detected

data_source: CounterReportDataSource

error: ('egg/command_client.py send_message|555', "", 'proxymel3.sportsbet.com.au: The daemon is not responding.', '[database/ReportCatalog.py run_report_queries|332] [reportdatasource/CounterReportDataSource.py query|272] [reportdatasource/CounterReportDataSource.py _parse_api_results|506] [reportdatasource/CounterReportDataSource.py _parse_interval_result_set|525] [query/result.py next|112] [query/client.py _call|235] [egg/command_client.py call|233] [egg/command_client.py send_message|555]')

Report Query Failed

query_id: wsa_monitor_overview_suspect_transactions_summary

data_source: WSASimpleTotalRDS

Report Query Failed

query_id: wsa_monitor_overview_top_application_types

data_source: CounterReportDataSource

Report Query Failed

query_id: wsa_monitor_overview_top_url_categories

data_source: CounterReportDataSource

Product: IronPort S160 Web Security Appliance

Model: S160

Version: 7.1.2-080

Serial Number: 0025643CFD42-4GQYHL1

Timestamp: 14 Jun 2012 14:00:21 +1000

Thank you for your help.

Lovedeep

WSA - Report Query Failed

sfiebran — Thu, 14 Jun 2012 20:39:14 GMT

I would not recommend to stay on build 7.1.2 for a S160. As an upgrade is reinstalling the OS, you should first upgrade to the next GA release 7.1.3-021. Regarding the reporting problem, if it after the upgrade remains, you have to contact customer support (open a ticket) to get it resolved via service access.

-Stephan