April 2022 - WLUG - wlug.mailman3.com

Re: Uptime!

by Joseph G

Thankfully, fewer reboots and maximized uptime will become a feature in most distro/OSs. *RHEL has kpatch* https://www.redhat.com/en/blog/overcoming-vulnerabilities-live-kernel-patch… *Ubuntu has Live kernel patching and the new needrestart package* https://ubuntu.com/blog/an-overview-of-live-kernel-patching https://ubuntu.com/blog/ubuntu-server-21-10 *Windows 2022 (😂😁😂)* https://techcommunity.microsoft.com/t5/windows-server-essentials-and/window… Hopefully the future will have fewer reboots since the pace of vulnerabilities doesn't seem to be slowing down at all. I, for one, am very happy to see the technology maturing to match reality. 😁 Enjoy the weekend! On Thu, Apr 21, 2022 at 10:06 AM Michael Voorhis via WLUG < wlug(a)lists.wlug.org> wrote: > Additionally if you never reboot, how do you know the machine WILL > reboot? How do you know what the system will do after a power failure, > etc? Fate will intervene at some point and force you to reboot whether > you want to or not, so you should be prepared with the knowledge of how > the system will respond to that. > > On 4/21/22 09:54, David Glaser via WLUG wrote: > > It you kept it up all of the time, how would you apply updates that > > require a re-boot? > >

April 21, 2022

Re: Uptime!

by Tim Keller

This machine was a "ghost ship." It's use had long come and gone and people had moved their stuff off onto new machines. It was running 32bit RHEL 5.5 no patches, no nothing. It was a security risk at this point. To Mike's point, unless there's good change control, you run the danger of having a machine that's not ever going to reboot sensibly. A couple years ago I stumbled upon a linux box that was running an ancient version of mysql.. the database was up, but it was running out of a directory like /u01/mysql/bin The disk /u01 was LONG gone.. but the database continued to run.. it's data was being written off on to a different disk and things worked.. but it was clear that machine would never had rebooted. Tim. On Thu, Apr 21, 2022 at 10:06 AM Michael Voorhis via WLUG < wlug(a)lists.wlug.org> wrote: > Additionally if you never reboot, how do you know the machine WILL > reboot? How do you know what the system will do after a power failure, > etc? Fate will intervene at some point and force you to reboot whether > you want to or not, so you should be prepared with the knowledge of how > the system will respond to that. > > On 4/21/22 09:54, David Glaser via WLUG wrote: > > It you kept it up all of the time, how would you apply updates that > > require a re-boot? > > _______________________________________________ > WLUG mailing list -- wlug(a)lists.wlug.org > To unsubscribe send an email to wlug-leave(a)lists.wlug.org > Create Account: https://wlug.mailman3.com/accounts/signup/ > Change Settings: > https://wlug.mailman3.com/postorius/lists/wlug.lists.wlug.org/ > Web Forum/Archive: > https://wlug.mailman3.com/hyperkitty/list/wlug@lists.wlug.org/message/2CNXU… > -- I am leery of the allegiances of any politician who refers to their constituents as "consumers".

April 21, 2022

Re: Uptime!

by Michael Voorhis

Additionally if you never reboot, how do you know the machine WILL reboot? How do you know what the system will do after a power failure, etc? Fate will intervene at some point and force you to reboot whether you want to or not, so you should be prepared with the knowledge of how the system will respond to that. On 4/21/22 09:54, David Glaser via WLUG wrote: > It you kept it up all of the time, how would you apply updates that > require a re-boot?

April 21, 2022

Re: Uptime!

by David Glaser

It you kept it up all of the time, how would you apply updates that require a re-boot? -David On 4/21/2022 9:27 AM, THE HAMMER via WLUG wrote: > So I guess my question is if I'm just running a personal Linux machine > at home, what are the advantages or disadvantages to keeping it on, or > shutting down during non-use? > > -Ron > > (I might in the near future use one machine as a home server to share > files, so in that case see an advantage to possibly keeping it on 24/7) > ------------------------------------------------------------------------ > *From:* Tim Keller via WLUG <wlug(a)lists.wlug.org> > *Sent:* Wednesday, April 20, 2022 5:07 PM > *To:* Worcester Linux Users' Group General Discussion > <wlug(a)lists.wlug.org> > *Cc:* Tim Keller <turbofx(a)gmail.com> > *Subject:* [WLUG] Uptime! > I just shutdown a linux machine with 3169 days of uptime! > It had userland processes that have been actively running since 2013! > Tim. > > -- > I am leery of the allegiances of any politician who refers to their > constituents as "consumers". > > _______________________________________________ > WLUG mailing list --wlug(a)lists.wlug.org > To unsubscribe send an email towlug-leave(a)lists.wlug.org > Create Account:https://wlug.mailman3.com/accounts/signup/ > Change Settings:https://wlug.mailman3.com/postorius/lists/wlug.lists.wlug.org/ > Web Forum/Archive:https://wlug.mailman3.com/hyperkitty/list/wlug@lists.wlug.org… -- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus

April 21, 2022

Re: Uptime!

by THE HAMMER

So I guess my question is if I'm just running a personal Linux machine at home, what are the advantages or disadvantages to keeping it on, or shutting down during non-use? -Ron (I might in the near future use one machine as a home server to share files, so in that case see an advantage to possibly keeping it on 24/7) ________________________________ From: Tim Keller via WLUG <wlug(a)lists.wlug.org> Sent: Wednesday, April 20, 2022 5:07 PM To: Worcester Linux Users' Group General Discussion <wlug(a)lists.wlug.org> Cc: Tim Keller <turbofx(a)gmail.com> Subject: [WLUG] Uptime! I just shutdown a linux machine with 3169 days of uptime! It had userland processes that have been actively running since 2013! Tim. -- I am leery of the allegiances of any politician who refers to their constituents as "consumers".

April 21, 2022

Re: Uptime!

by Mike Peckar

Fun Story, Maddog. Around 20 yrs ago I was consulting for Bloomberg in Skillman, NJ, a big Solaris shop. The HP app I was working with bellied up with memory leaks and I suggested they reboot that server. I was told flat out they don't reboot Solaris servers period. They cleaned up the mess and isolated where in the HP code that the pointer was lost, leaving me the not-so-fun task of filing the bug report with HP. Mike On Wed, Apr 20, 2022 at 7:39 PM Jon "maddog" Hall via WLUG < wlug(a)lists.wlug.org> wrote: > Tim, > > What was the reason for shutting it down? > > This reminds me of a story from years ago where a young friend contacted > me before a trip to the University of New Hampshire for a Linux LUG meeting. > > He asked me if I would go to a particular dorm and knock on the door of > what had been his door room. I was to ask if I could unplug the box that > was in the corner of the closet in the room. The system had been running > for five years in his former dorm room and he had forgotten the login > password. He did not want the machine back, just wanted it unplugged. > > A young woman answered the door, heard my explanation and let me unplug > the machine. "We were afraid to unplug it" she said. > > Your machine beat his machine on uptime. > > md > > On Wed, Apr 20, 2022 at 5:07 PM Tim Keller via WLUG <wlug(a)lists.wlug.org> > wrote: > >> I just shutdown a linux machine with 3169 days of uptime! >> It had userland processes that have been actively running since 2013! >> Tim. >> >> -- >> I am leery of the allegiances of any politician who refers to their >> constituents as "consumers". >> _______________________________________________ >> WLUG mailing list -- wlug(a)lists.wlug.org >> To unsubscribe send an email to wlug-leave(a)lists.wlug.org >> Create Account: https://wlug.mailman3.com/accounts/signup/ >> Change Settings: >> https://wlug.mailman3.com/postorius/lists/wlug.lists.wlug.org/ >> Web Forum/Archive: >> https://wlug.mailman3.com/hyperkitty/list/wlug@lists.wlug.org/message/PW3ML… >> > _______________________________________________ > WLUG mailing list -- wlug(a)lists.wlug.org > To unsubscribe send an email to wlug-leave(a)lists.wlug.org > Create Account: https://wlug.mailman3.com/accounts/signup/ > Change Settings: > https://wlug.mailman3.com/postorius/lists/wlug.lists.wlug.org/ > Web Forum/Archive: > https://wlug.mailman3.com/hyperkitty/list/wlug@lists.wlug.org/message/KSUVD… >

April 21, 2022

Re: Uptime!

by Jon "maddog" Hall

Tim, What was the reason for shutting it down? This reminds me of a story from years ago where a young friend contacted me before a trip to the University of New Hampshire for a Linux LUG meeting. He asked me if I would go to a particular dorm and knock on the door of what had been his door room. I was to ask if I could unplug the box that was in the corner of the closet in the room. The system had been running for five years in his former dorm room and he had forgotten the login password. He did not want the machine back, just wanted it unplugged. A young woman answered the door, heard my explanation and let me unplug the machine. "We were afraid to unplug it" she said. Your machine beat his machine on uptime. md On Wed, Apr 20, 2022 at 5:07 PM Tim Keller via WLUG <wlug(a)lists.wlug.org> wrote: > I just shutdown a linux machine with 3169 days of uptime! > It had userland processes that have been actively running since 2013! > Tim. > > -- > I am leery of the allegiances of any politician who refers to their > constituents as "consumers". > _______________________________________________ > WLUG mailing list -- wlug(a)lists.wlug.org > To unsubscribe send an email to wlug-leave(a)lists.wlug.org > Create Account: https://wlug.mailman3.com/accounts/signup/ > Change Settings: > https://wlug.mailman3.com/postorius/lists/wlug.lists.wlug.org/ > Web Forum/Archive: > https://wlug.mailman3.com/hyperkitty/list/wlug@lists.wlug.org/message/PW3ML… >

April 20, 2022

Uptime!

by Tim Keller

I just shutdown a linux machine with 3169 days of uptime! It had userland processes that have been actively running since 2013! Tim. -- I am leery of the allegiances of any politician who refers to their constituents as "consumers".

April 20, 2022

Reminder! WLUG tonight! Hudson Public Library! Topic: Fotoxx!

by Tim Keller

Hey Everybody, This is the final reminder we've got a meeting tonight at 7pm! The speaker is going to be Dick Miller! He's going to be talking about Fotoxx! Fotoxx is an open source professional grade photo editing and collection manager! I hope to see you at the Hudson Public Library or online in our Jitsi Room! Later, Tim. -- I am leery of the allegiances of any politician who refers to their constituents as "consumers".

April 14, 2022

Re: Atlassian outage

by Tim Keller

It makes me think that what they're using for "backups" are actually snapshots of volumes.. But if you purge that volume, you purge the snapshots with it.. As for people getting fired..Eh, nobody inadvertently got feed into an industrial grinding machine because someone turned off all the safeties. People are just unable to look at the jira kanban boards.. Ironically the people who caused this are likely the ones most likely to fix it. I once wiped out 20TB+ of production data. I could go into all the gory details, but to say I deleted a bunch of poorly labeled volumes on a SAN. All the same I did delete the data.. and I then had to fix the mistake and part of the process was me writing up a full incident report and a RCA. This looks like it was a major breakdown in process control and testing. This is *exactly* why there are pre-prod testing environments that are cloned from real data.. so when your script that was supposed to expand your EBS volumes does so by first destroying them and then creating them larger you find that out. I'm suspecting this is going to be part of the lively conversation tonight! Later, Tim. On Wed, Apr 13, 2022 at 4:00 PM John Stoffel <john(a)stoffel.org> wrote: > >>>>> "Jared" == Jared Greenwald via WLUG <wlug(a)lists.wlug.org> writes: > > Jared> At least they're owning the mistake, which is something I guess... > Jared> https://www.atlassian.com/engineering/april-2022-outage-update > > I want people to carefully reade these four paragraphs and ask > themselves, what is the difference between restoring one customer > quickly using a well tested process, and restoring 400 customers? > > We also maintain immutable backups that are designed to be resilient > against data corruption events, which enable recovery to a previous > point in time. Backups are retained for 30 days, and Atlassian > continuously tests and audits storage backups for restoration. > > Using these backups, we regularly roll-back individual customers or a > small set of customers who accidentally delete their own data. And, if > required, we can restore all customers at once into a new environment. > > What we have not (yet) automated is restoring a large subset of > customers into our existing (and currently in use) environment without > affecting any of our other customers. > > Within our cloud environment, each data store contains data from > multiple customers. Because the data deleted in this incident was only > a portion of data stores that are continuing to be used by other > customers, we have to manually extract and restore individual pieces > from our backups. Each customer site recovery is a lengthy and complex > process, requiring internal validation and final customer verification > when the site is restored. > > > These paragraphs are carefully written to imply one things, but show > that they have no system in place for proper rollbacks when an entire > customer gets purged. I suspect that their "nuke it all from orbit" > script *also* nuked the immutable backups as well, which is why this > is all taking so long to restore. > > I do hope the people who messed up are fired, and if anyone is fired > it's the managers who set up this debacle. > > John > -- I am leery of the allegiances of any politician who refers to their constituents as "consumers".

April 14, 2022