Skip to content
0
  • Home
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
  • Home
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (Sketchy)
  • No Skin
Collapse

Wandering Adventure Party

  1. Home
  2. Uncategorized
  3. Update on my website maintenance woes: My websites had been down for the last 12 hours or so, so I decided to look on some way to restart them.

Update on my website maintenance woes: My websites had been down for the last 12 hours or so, so I decided to look on some way to restart them.

Scheduled Pinned Locked Moved Uncategorized
texlatex
5 Posts 3 Posters 5 Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • Jürgen HubertJ This user is from outside of this forum
    Jürgen HubertJ This user is from outside of this forum
    Jürgen Hubert
    wrote last edited by
    #1

    Update on my website maintenance woes: My websites had been down for the last 12 hours or so, so I decided to look on some way to restart them. Then I found a button in my provider's administration interface that purged all objects in my "Varnish Cache". I remembered that the "Varnish Cache" came up from time to time in the error messages, so I clicked it.

    And my websites were suddenly online again.

    This is an obvious improvement to my prior situation, and gives me hope that this trick will work in the future as well. But I would like to understand what the actual problem was (beyond it having to do with the Varnish Cache), so that maybe I can prevent from reoccurring in the future in the first place.

    I don't want this to become another "sacrifice a black goat at midnight" thing, like with certain aspects of my #TeXLaTeX installation - where I know that some things will work, but not _why_ they work.

    Link Preview Image
    Crash Bandicoot 🌳 100/80/30C EndlessMasonE 2 Replies Last reply
    0
    • Jürgen HubertJ Jürgen Hubert

      Update on my website maintenance woes: My websites had been down for the last 12 hours or so, so I decided to look on some way to restart them. Then I found a button in my provider's administration interface that purged all objects in my "Varnish Cache". I remembered that the "Varnish Cache" came up from time to time in the error messages, so I clicked it.

      And my websites were suddenly online again.

      This is an obvious improvement to my prior situation, and gives me hope that this trick will work in the future as well. But I would like to understand what the actual problem was (beyond it having to do with the Varnish Cache), so that maybe I can prevent from reoccurring in the future in the first place.

      I don't want this to become another "sacrifice a black goat at midnight" thing, like with certain aspects of my #TeXLaTeX installation - where I know that some things will work, but not _why_ they work.

      Link Preview Image
      Crash Bandicoot 🌳 100/80/30C This user is from outside of this forum
      Crash Bandicoot 🌳 100/80/30C This user is from outside of this forum
      Crash Bandicoot 🌳 100/80/30
      wrote last edited by
      #2

      @juergen_hubert How often does it happen? Can you switch off the Varnish cache at Gandi? Tip: Monitoring free of charge with e.g. pingtide.com (Hosted in Germany).

      Jürgen HubertJ 1 Reply Last reply
      0
      • Crash Bandicoot 🌳 100/80/30C Crash Bandicoot 🌳 100/80/30

        @juergen_hubert How often does it happen? Can you switch off the Varnish cache at Gandi? Tip: Monitoring free of charge with e.g. pingtide.com (Hosted in Germany).

        Jürgen HubertJ This user is from outside of this forum
        Jürgen HubertJ This user is from outside of this forum
        Jürgen Hubert
        wrote last edited by
        #3

        @crash_bandicoot The last time it happened was about two weeks or so.

        1 Reply Last reply
        0
        • Jürgen HubertJ Jürgen Hubert

          Update on my website maintenance woes: My websites had been down for the last 12 hours or so, so I decided to look on some way to restart them. Then I found a button in my provider's administration interface that purged all objects in my "Varnish Cache". I remembered that the "Varnish Cache" came up from time to time in the error messages, so I clicked it.

          And my websites were suddenly online again.

          This is an obvious improvement to my prior situation, and gives me hope that this trick will work in the future as well. But I would like to understand what the actual problem was (beyond it having to do with the Varnish Cache), so that maybe I can prevent from reoccurring in the future in the first place.

          I don't want this to become another "sacrifice a black goat at midnight" thing, like with certain aspects of my #TeXLaTeX installation - where I know that some things will work, but not _why_ they work.

          Link Preview Image
          EndlessMasonE This user is from outside of this forum
          EndlessMasonE This user is from outside of this forum
          EndlessMason
          wrote last edited by
          #4

          @juergen_hubert
          You need to know why clearing the cache helped.

          often its a bot scraping everything on your site and leaving the cache full of less useful pages.

          Can you see stats like hit vs miss and backend timeouts / errors vs responses?

          There's usually a ramp up of something, (likely misses) and you can use that ramp up to find the time to look for in the logs for sus behaviour.

          Jürgen HubertJ 1 Reply Last reply
          0
          • EndlessMasonE EndlessMason

            @juergen_hubert
            You need to know why clearing the cache helped.

            often its a bot scraping everything on your site and leaving the cache full of less useful pages.

            Can you see stats like hit vs miss and backend timeouts / errors vs responses?

            There's usually a ramp up of something, (likely misses) and you can use that ramp up to find the time to look for in the logs for sus behaviour.

            Jürgen HubertJ This user is from outside of this forum
            Jürgen HubertJ This user is from outside of this forum
            Jürgen Hubert
            wrote last edited by
            #5

            @EndlessMason

            Hmmm... comparing my error log with my access log, it seems that the most likely culprit is the "blex-crawler" - at least, it made a _lot_ of requests right around the time the latest error wave started.

            1 Reply Last reply
            0

            Reply
            • Reply as topic
            Log in to reply
            • Oldest to Newest
            • Newest to Oldest
            • Most Votes


            • Login

            • Login or register to search.
            Powered by NodeBB Contributors
            • First post
              Last post