Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 7 replies
  • Subscribers 3 subscribers
  • Views 846 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

[7.301] Proxies Report Zero Requests After HA Failover

James Bourne
Hi All,

We had to failover an ASG425a active/passive cluster yesterday. The dashboard continues to report:

HTTP Proxy is active, 0 requests served today
FTP Proxy is active
SMTP Proxy is active, 0 emails processed, 0 emails blocked
POP3 Proxy is active, 0 emails processed, 0 emails blocked

I've checked the logs and I'm seeing HTTP, FTP, SMTP and POP3 traffic.

Also the daily Executive Report traffic statistics are now blank.

Any idea how to re-enable or reset these stats?

TIA,

James


This thread was automatically locked due to age.
  • 0
    Hi James

    the same issue here at our ASG320 cluster since the update to 7.300 as you can read at:

    https://community.sophos.com/products/unified-threat-management/astaroorg/f/56/t/48403

    Still no solution availabe. [:(]

    David
  • 0 in reply to Copyright
    It's definitely a bad bug.

    I found on another post that a user had been requested to run:

    /var/storage/pgsql/init/reporting_db_init.sh

    That script looks like it initialises the reporting database.

    On the "working-node" the directory /var/log/reporting/pgsql exists and is being populated with RRD data. On the "non-working node" this directory does not exist. The characteristics of that directory are:

    chown postgres.postgres
    chmod 600 

    If you run that script on the "non-working node" you get:

    ./reporting_db_init.sh 
    ERROR:  could not set permissions on directory "/var/log/reporting/pgsql": No such file or directory
    createdb: database creation failed: ERROR:  tablespace "reporting" does not exist
    createlang: could not connect to database reporting: FATAL:  database "reporting" does not exist
    psql: FATAL:  database "reporting" does not exist
    psql: FATAL:  database "reporting" does not exist

    So it looks like the entire reporting database and directory structure containing RRD data is not present on the slave - hence no statistics.

    That's pretty poor quality assurance IMHO.
  • 0 in reply to James Bourne
    I've reported this to Astaro. Let's see what happens ...
  • 0 in reply to James Bourne
    I'm still getting 
    HTTP Proxy is active, 0 requests served today

    But it looks like it is working as Astaro is handling web downloads. Is there another way to confirm it definitely is working?
  • 0
    As James found above, the solution is to reinitialize the reporting database.  You can watch the Content Filter live log when you want to confirm that specific sites are being managed by the proxy.

    Cheers - Bob
     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
  • 0 in reply to BAlfson
    I would also consider up2dating up to 7.405; I understand there have been some significant improvements in the HA and reporting systems in 7.4xx.

    CTO, Convergent Information Security Solutions, LLC

    https://www.convergesecurity.com

    Advice given as posted on this forum does not construe a support relationship or other relationship with Convergent Information Security Solutions, LLC or its subsidiaries.  Use the advice given at your own risk.