메인 콘텐츠로 건너뛰기
블로그Linode셧다운 감시자, Lassie

래시, 셧다운 감시견

[b] 래시 – Linode 자율 시스템 셧다운 지능형 rEbooter[/b]

래시는 셧다운 감시견입니다. 예기치 않게 전원을 끄면 Linode를 자동으로 재부팅합니다. 전원 차단 조건에 대한 책임이 없는 상태에서 Linode가 전원을 끄고 있음을 감지하여 작동합니다. 루프를 방지하기 위해 15분 이내 5개의 부트가 발생한 후 포기합니다.

기본적으로 활성화되어 있지만 설정은 새로운 [url=https://www.linode.com/members/utilities/]유틸리티 하위 탭[/url]의 [url=https://www.linode.com/members/utilities/watchdog.cfm]래시 페이지[/url]에서 변경할 수 있습니다.

부작용은 현재의 경우 Linode 내부의 “재부팅”이 예상대로 작동하지만, Linode 내부의 “셧다운”으로 인해 래시가 개입해 부트를 발행하는 것입니다. 이전에는 두 명령어가 모두 셧다운을 발생시켰습니다. 어쩔 수 없어요 :). 이에 대한 해결 방법은 “셧다운”을 위한 별칭을 만들어 Lish를 통한 셧다운 작업을 발행하는 것입니다. “ssh LinodeUsername@hostXX.linode.com 셧다운”.            

이메일을 통한 알림이 계획되어 있습니다.

즐길!
-Chris

댓글 (10)

  1. Author Photo

    [quote:f17891f4fb=”caker”]
    A side effect of this is that now "reboot" from inside your Linode will function as expected, but a "shutdown" from inside your Linode will result in Lassie kicking in and issuing a boot. Previously both of those commands resulted in a shutdown. I can’t win :). [/quote]

    For what it’s worth, I think this a better default. I might reboot from inside the linode to make sure new libraries are in use, or just invoke the nostalgia of my WIndows day, but the only reason I shutdown is to re-arrange disks or somesuch, which I’m going to be doing from the Web UI anyway.

  2. Author Photo

    [quote:df0090ef37=”caker”][b]Lassie – Linode Autonomous System Shutdown Intelligent rEbooter[/b]

    Lassie is a shutdown watchdog.
    [/quote]

    Since it’s [i]almost[/i] Halloween, please rename it to:

    [b]L[/b]inode [b]A[/b]utonomous [b]S[/b]ystem [b]S[/b]hutdown [b]I[/b]ntelligent r[b]E[/b]booter ag[b]E[/b]nt [b]A[/b]nd [b]T[/b]im[b]ER[/b] (LASSIE EATER)

    James

  3. Author Photo

    I’m a little curious — have shutdowns been a problem?

    I’ve been on Linode since ’04, and mine has never gone down on its own.

    I’m not trying to diss a new and valuable feature — but is it solving a problem that people actually have?

  4. Author Photo

    [quote:c80aeb5696=”astrashe3″]I’m a little curious — have shutdowns been a problem?[/quote]
    Definitely not widespread. But, Linux has bugs from time to time, and so does UML. It’s just a nice thing to have, rather than having your Linode go down 5 minutes after you go to bed, and not knowing about it until you get up the next morning. This also solves the "It’s been 2 years since I’ve logged into linode.com, lost my password, the email address you have for me no longer works, and I typed reboot in my Linode and it didn’t come back up" issues (because I hack UML to shutdown on "reboot" so it’ll pick up any config changes between boots).

    -Chris

  5. Author Photo

    I got a pretty major problem when I went to resize my main drive with the new disk space we’ve just been given. Lassie started booting before it finished and pretty nastily barfed the drive.

    Lassie should check that another job isn’t already running before forcing a boot!

  6. Author Photo

    Lassie doesn’t boot your Linode — it just queues up a boot job. Jobs run one after another. And, the resize jobs *should* still be checking that your volume isn’t in use before doing anything… I’ll have a look at the logs.

    -Chris

  7. Author Photo

    OK, I found, and squashed a bug. It was a race. We use the pid file that UML writes out in determining if a Linode is running or not. It turns out that UML doesn’t immediately write this file. If another job ran just after the Linode booted and then checked to see if the Linode was active, it would not find the pid file and assume it was ok to do its thing.

    Now boot jobs wait a few seconds, while checking to see if UML wrote out its pid file, before completing.

    This bug has been in here for a LONG time (way before Lassie), so I’m grateful to you for reporting this, but sorry it ended up in your filesystem being munched on a bit.

    Regards,
    -Chris

  8. Author Photo

    [quote:2a883d7a6d=”caker”]
    This bug has been in here for a LONG time (way before Lassie), so I’m grateful to you for reporting this, but sorry it ended up in your filesystem being munched on a bit.
    [/quote]

    That’s cool. It seems to have e2fscked without any real problems. My only issue now is that the Linode dashboard reports the fs as 20 gigs but inside the linode it’s still 16 gigs. I suspect it might need some manual command-line hackery to get it back in shape, but not sure where to start.

    Feel free to bring my linode down if you think you can resize it to its proper size. Otherwise, any ideas on how to do it?

  9. Author Photo

    Try shrinking it to 16G (or 15G) and then re-enlarging? Also, what does fdisk show for the partition size? It’s possible that the partition got enlarged, but not the file
    system. If that’s the case, then you should be able to enlarge the file system from within the linode.

  10. Author Photo

    [quote:2a7ae073e2=”SteveG”]Try shrinking it to 16G (or 15G) and then re-enlarging?[/quote]

    That did the trick. Thanks!

댓글 남기기

이메일 주소는 게시되지 않습니다. 필수 필드가 표시됩니다 *