Author Archive for Mads Petersen

Announcing Service Window: More replacement of old infrastructure..

Posted on: January 20th, 2023 by

This Friday’s service window was being executed well, and while assisting in replacing some old infrastructure, it opened opportunities to proceed down the same track. With that in mind, the Kolab Now operations team will perform more maintenance on the infrastructure of the Kolab Now platform on Friday, 27th of January 2023 at 10:00 UTC.  The update will move more of backend services to newer infrastructure. No new features visible to end users will be enabled during this maintenance.

The service window is expected to last for no more than 4 hours, ending on Friday, 27th of January 2023, at 13:00 UTC.

> Continue Reading

Incident report: ‘Gateway Timed-out’ at login

Posted on: January 14th, 2023 by

On Saturday January 14th, 2023, from approximately 03:47:12 UTC a group of Kolab Now users observed an error stating: “Gateway time-out” when trying to login to the webclient, the dashboard, or connect with any desktop or mobile client. The Kolab Now main page https://kolabnow.com/ and all other services (Support, blog and knowledge base) were available with no issues for these same users.

The issue lasted until approximately 08:04:22 UTC, and was caused by a db server in one of the clusters being stuck in a large operation. The issue caused troubles with the login procedure, but had no impact on the mail flow. No mail was lost or delayed during the incident.

> Continue Reading

Announcing Service Window: The death of old infrastructure..

Posted on: January 13th, 2023 by

On Friday, 20th of January 2023 at 09:00 UTC, the Kolab Now operations team will perform maintenance on the infrastructure of the Kolab Now platform.  The update will move a part of the backend services to newer infrastructure. The updates will bring more stability and better manageability to the backoffice systems. No new features visible to end users will be enabled during this maintenance.

The service window is expected to last for no more than 4 hours, ending on Friday, 20th of January 2023, at 13:00 UTC.

> Continue Reading

The Annual Certificate Refresh

Posted on: January 2nd, 2023 by

Another year past and we needed to again refresh our certificates.

As in previous years, e.g. 2018, 2019, 2020, etc, we rolled over certificates across all systems over the last few days of the year.

The new certificate is in place, and applies to https://kolabnow.com/, imaps://imap.kolabnow.com and smtps://smtp.kolabnow.com.

As in previous years, we publish the fingerprint here:

SHA-256:

FA:2A:BF:A9:F8:FA:67:E7:7B:0D:B2:2C:C2:F2:8B:F8:30:4C:77:84:55:38:02:B4:DD:66:7F:DA:F4:C7:DC:49

SHA-1:

B6:FE:BF:F6:3A:17:CD:E4:2D:02:7F:AF:C9:EF:0C:45:32:F9:0A:3B

 

Incident report: db server stuck in large operation..

Posted on: June 7th, 2022 by

On Monday June 06 2022, from approximately 11:24 UTC a group of Kolab Now users observed an error stating: “Gateway time-out” when trying to login to the webclient, the dashboard, or connect with any desktop or mobile client. The Kolab Now main page https://kolabnow.com/ and all other services (Support, blog and knowledge base) were available with no issues for these same users.

The issue lasted for about an hour, until approximately 12:19 UTC, and was caused by a db server in one of the clusters being stuck in a large operation. The issue caused troubles with the login procedure, but had no impact on the mail flow. No mail was lost or delayed during the incident.

The operations team was warned by the monitoring system about a stuck db server in the cluster, and was having hands on keyboards right away. The issue lasted for about an hour (some users in the group saw return of service earlier than others), and was caused by this db server in the cluster being stuck in a large operation.

Further investigation and action is going into reevaluating the amount of resources assigned to the db clusters and other servers for such large operations of this type.

If you were among the group of users that was impacted by this, then please accept our apologies for any inconvenience caused.

Updates to Kolab Now..

Posted on: April 22nd, 2022 by

This Friday the operations team is rolling over the Kolab Now system and deploying a set of new updates. However, thanks to the redundancy in the architecture, users will not see any downtime or service interruptions.

The update contains a lot of code, preparing the system for future features, and one update to the Voice & Video feature.

> Continue Reading

Is your password ‘123456’?

Posted on: February 14th, 2022 by

If so, you share your password with thousand – perhaps 100s of thousands of others. Password complexity is being talked a lot about in the media these days. You have probably seen messages from your bank or your badminton club membership administrator about how your password should be complex to avoid password cracking.

Last Friday, 2022-02-11, Kolab Now released a number of enhancements, most of which are not directly visible to end users. However one change that could have impact for users is the option to implement password policies.

Take a look at the knowledge base article, to see how password policies can be leveraged by group owners to ensure all users have adequate passwords at all times.

This release also brings some interesting updates for the users in the Private beta program, who now have access to Shared folders, Distribution lists, and Resource management – more information to follow on that.

More interesting updates are on the way. Keep an eye on this blog for news and updates.

 

 

Our Statistics for 2021

Posted on: February 4th, 2022 by

Again this year we deliver you the numbers according to our terms of service, that states there’s basically no way for anyone to get any access to your data without us letting the world know that it happened.

We have again counted the interactions and here is our statistics for 2021.

> Continue Reading

Incident report: Failing front ends

Posted on: January 26th, 2022 by

On Friday January 21 at 15:48 UTC  users observed that the main page https://kolabnow.com/ became unaccessible and reviled an error: 503 – Server unavailable. The webclient (https://kolabnow.com/apps) was still available, but with seriously degraded performance – to the point where the service would give up and reveal the ‘Maintenance’ page.

Also IMAP, SMTP, ActiveSync, and $DAV was impacted by the failing frontends.

The service was unavailable for about 50 minutes, during which time all mails, in and out, were queued. When the service again was available, those mail queues first had to be delivered before new mail could be sent or received. This caused users to experience a delay in the traffic.

> Continue Reading

Incident Report: WebDAV/CalDAV/CardDAV services unavailable..

Posted on: January 17th, 2022 by

On Monday morning at 03:22 CET the kolab Now $DAV services stopped working.

While resolving a performance issue for $DAV connections, we moved around  servers from an old infrastructure to a new infrastructure, and with that the rotation of logs. Unfortunately a tiny bit were missed while configuring the new servers, which caused the log rotation attempting to reload httpd (while that wasn’t needed). In turn, reloading httpd didn’t succeed and timed out, and the new DAV servers were left in a maintenance state;  unavailable.

This happened at ~ 03:22 CET. As these are new DAV servers, they were only included in the standard monitoring, and no one got notified about the problem until it was discovered at 07:47 CET. The configuration was promptly corrected and the new DAV servers came back online right away (and was added to the monitoring notifications). At this time everything should be available and working as expected.

We apologize for any inconvenience that this may have caused.