Impact: PHP errors on the Power cluster
Services: PHP on Power cluster
Date: Friday 22 August 2008
Duration: 12:40 AEST – 15:17 AEST
Status: Resolved

Summary:
Some PHP scripts on the power cluster are experiencing issues with DNS resolution. This may result in a PHP error saying “Temporary failure in name resolution”. Technicians are currently working to resolve this issue.

This issue has now been resolved.

Impact: No connectivity to the mysqlx MySQL server
Services: MySQL
Date: Thursday 21 August 2008
Duration: 10:35 AEST – 10:47 AEST
Status: Resolved

Summary:
Sites using the mysqlx MySQL server would have experienced connectivity problems for the time mentioned above. This was due to a network configuration issue. This has now been resolved.

Impact: Delayed mail sent to Ilisys’ support or sales inboxes
Services: Ilisys Support & Customer Service
Date: Monday 18 August 2008
Duration: 09:00 AEST – 15:00 AEST
Status: Resolved

Summary:
Due to a configuration issue with our problem ticketing system, email sent to our support@ilisys.com.au or sales@ilisys.com.au email addresses may have been delayed. Ilisys apologises for any inconveniences caused and will respond promptly to those delayed emails.

Impact: PHP pages on Power cluster giving open_basedir errors
Services: PHP on Power cluster
Date: Friday 15 August 2008
Duration: 19:50 AEST – 0:55 AEST
Status: Resolved

Summary:
Sites across the Power cluster running PHP pages were subject to intermittent PHP errors (Warning: Unknown: open_basedir restriction in effect). This issue has now been resolved and sites are now functioning correctly.

Impact: Site statistics unavailable
Services: Urchin 5
Date: Wednesday 13 August 2008
Duration: 00:00 AEST – 10:55 AEST
Status: Resolved

Summary:
Due to an error in a processing script last night, all urchin statistics are currently unavailable. The Ilisys Operations team are working on a fix at the moment and expect it to be resolved shortly. We apologise for any inconveniences caused by this issue.

Update 10:55AM: The issue that was showing “No Reports to View!” in Urchin has been corrected, however the back-processing of statistics will take some time. We expect this to be up to date by tomorrow morning at the latest.

Change: SMTP response codes when greylisting
Services: Mail
Expected impact: More predictable, and faster, retry cycles with mail servers due to tighter RFC compliant status codes.
Potential adverse impact: Longer ‘retry’ times by external servers sending email to Ilisys systems.
Date of rollout: ~14:00 AEST Thursday 7 August 2008
Status: Done
Summary:
We have a potential solution for the greylisting issue where providers such as Bigpond bounce greylisted mail around their mail pools with fairly long retry cycles. There appears to be a bug in how Postfix handles greylisting SMTP response codes. The current greylist response code is 450 which means there was an error accessing the mailbox, and to retry. There is internet discussion, and we’ve witnessed this, that this results in some providers immediately retrying a few seconds later and then passing it to fallback servers that have long retry cycles. Instead we’re going to use response code 451 which means there was a temporary error, try again soon.

Impact: Sales via the Ilisys website/toolkit
Services: Camtech
Date: Monday 4 August 2008
Duration: 10:30 AEST – 12:00 AEST
Status: Resolved

An issue on the Camtech server resulted in all Ilisys payments to be returning failure messages. The issue has now been rectified, our apologies for any inconveniences caused.

Impact: IMAP mail/retrieval
Services: Email
Date: Monday 4th August 2008
Duration: 10:45 AEST – 11:30 AEST
Status: Resolved

Platform staff are investigating the cause of intermittent IMAP timeouts when accessing mail services. There appears to be one network with an inordinate amount of connections and measures are being taken.

Impact: Issues logging in to receive email
Services: Email
Date: Friday 1st August 2008
Duration: 11:20 AEST – 11:56 AEST
Status: Resolved

Customers may receive intermittent login issues when trying to receive email. Technicians are in the process of resolving the issue now.

Update 11:56 AEST: This issue has now been resolved.