Contents with the Emergency Tag Node

  • When you visit a concert, you visit Orchard: Troubleshooting Live Nation's Orchard platform

    Orchard, Case study, Emergency, Development, Live Nation
    Tuesday, May 29, 2018 6:38:54 PM -- Author: Zoltán Lehóczky
    No Comments

    Did you ever go to a concert? Well, then most possibly you've been a guest of Live Nation Clubs and Theaters: A subsidiary of the Fortune 500 entertainment company Live Nation, Live Nation Clubs and Theaters manages a wide array of venues within the United States. But this is not what they're famous for, they also use Orchard :). Specifically all of Live Nation Clubs and Theater venues and brands, including e.g. House of Blues, The Aztec Theatre, and the Coca Cola Roxy are part of a 50-site multi tenant Orchard application. And we helped to iron out a few issues.

    < More >

  • Solving a huge site's downtime - Parapolitika.gr case study

    Orchard, Case study, Emergency, Prapolitika.gr
    Thursday, October 17, 2013 6:18:00 PM -- Author: Zoltán Lehóczky
    No Comments

    Recently the maintainers of the big Greek news site Parapolitika, the guys from the Greek subsidiary of Tatchit contacted us asking for our help: the site was going down routinely for some reason after going live (it was rewritten on Orchard from the legacy engine). The Orchard application was sometimes using up all of the server's CPU (despite it being a 24-core beast) and crashing the IIS worker process in the end. This needed some urgent fix because websites tend to be only worthy if they're alive...

    < More >

  • Helping GI Joe Search & Rescue get back on track with their website

    Case study, Emergency
    Monday, July 15, 2013 5:39:00 PM -- Author: Zoltán Lehóczky
    2 Comments

    On Friday we completed a short but important emergency assignment: getting the GI Joe Search & Rescue team's website back online. The website was moved to a new hosting company but wasn't feeling all right (the standard IIS 404 page greeted the visitors). This was especially problematic given that the team needed the website for their communication on the weekend.

    That's when we got contacted on behalf of the team and started investigating. After checking the logs and verifying the integrity of the deployment we recognized the source of the error: although the site's database was seemingly restored all the tables were empty! Running the restore again fixed the database and thus solved the issue altogether.

    Naturally we didn't charge the team for this emergency fix: they don't charge you when you need their help either!

    < More >