We are currently experiencing issues with Printix Cloud. We are working to resolve the issues. We will post updates to this announcement when we have news. Select Follow if you wish to be notified about these updates.
During this period you may experience slow performance, inability to sign in and release documents via Printix App. Direct print to printers on the local network is still possible.
- 2022-02-14 17:20 CET
This announcement is published. -
2022-02-14 17:30 CET
Issue marked as resolved. - 2022-02-21 06:53 CET
Incident report published below.
Incident report
On 2022-02-14 (Monday, February 14th. 2022) at 16:20 CET connections to a single node in our Cassandra database cluster began to intermittently timeout. Printix was still functional for most customers, but especially sign in started to fail for some users. At 16.32 CET we got the first PagerDuty alert indicating the system was not working as expected.
Attempts to fix the problematic node failed. And at 16.53 CET a reboot of the entire machine was initiated. Unfortunately the reboot hung in Azure, and the machine was completely unreachable.
A hard reboot was initiated at 17.16 CET, and the machine was back online at 17.20 CET. After a few minutes of datasynchronization, the system was fully functional again.
Actions
- The initial problems with the database node, was caused by an excessive amount of data stored in a few tablespaces. most of that data is no longer useful, and cleanup procedures are being instated to make sure the issue does not occur again (PP-7322).
Friendly regards
The Printix Team
Comments
0 comments
Article is closed for comments.