Hi,
Got this after 19.5 upgrade (came from build 365):
On-device reporting is currently off. Report migration failed.
Is there any other solution to this, than go CLI and flush the reports?:
This thread was automatically locked due to age.
Hi,
Got this after 19.5 upgrade (came from build 365):
On-device reporting is currently off. Report migration failed.
Is there any other solution to this, than go CLI and flush the reports?:
Hi twister5800 Thank you for reaching out to the Sophos community team and sharing the details with us. The report flush will rebuild the database and may help to fix the issue but you would like to confirm any other solution apart from flushing the report and that may require investigation with Support and then the next details can be shared/concluded over the case with you by Suppor team based on investigation and logs observation.
Regards,
Vishal Ranpariya
Technical Account Manager | Sophos Technical Support
Sophos Support Videos | Knowledge Base | @SophosSupport | Sign up for SMS Alerts |
If a post solves your question use the 'This helped me' link.
Hi Vishal,
Thanks for the reply :-)
The devices is running HA (Active/passive), what will happen if I do this on the primary?
Will it also fix the DB on the slave/aux.?
-----
Best regards
Martin
Sophos XGS 2100 @ Home | Sophos v19 Architect
Hi Vishal,
Thanks for the reply :-)
The devices is running HA (Active/passive), what will happen if I do this on the primary?
Will it also fix the DB on the slave/aux.?
-----
Best regards
Martin
Sophos XGS 2100 @ Home | Sophos v19 Architect
Hi twister5800 : What is the status of reportdb on Aux Device? If you will do it on primary, primary will go for reboot action after flushing the report, and due to that reboot action HA fail over will be initiated there in your network.
Regards,
Vishal Ranpariya
Technical Account Manager | Sophos Technical Support
Sophos Support Videos | Knowledge Base | @SophosSupport | Sign up for SMS Alerts |
If a post solves your question use the 'This helped me' link.
Hi Vishal_R
I did the above here out of office, and everything came up again, on the other node, reporting error was gone, then did a failover to the before "defective" node, but it came out all "green"
Thanks for your help :-)
-----
Best regards
Martin
Sophos XGS 2100 @ Home | Sophos v19 Architect
Hi twister5800 thanks for the latest feedback and I am glad that you managed to fix the issue with given suggestions.
Regards,
Vishal Ranpariya
Technical Account Manager | Sophos Technical Support
Sophos Support Videos | Knowledge Base | @SophosSupport | Sign up for SMS Alerts |
If a post solves your question use the 'This helped me' link.