Reboot your servers
-
I directly only deal with the UNIX side. I schedule those to update themselves and then reboot when done updating; or we do auto updates during the week and then just reboot on the schedule.
-
@scottalanmiller said in Reboot your servers:
I directly only deal with the UNIX side. I schedule those to update themselves and then reboot when done updating; or we do auto updates during the week and then just reboot on the schedule.
Zabbix monitoring is super convenient for my weekly reboots. If something doesn't come back I will receive an e-mail but I also remote into it to verify everything is up and running too
-
@wirestyle22 said in Reboot your servers:
Zabbix monitoring is super convenient for my weekly reboots. If something doesn't come back I will receive an e-mail but I also remote into it to verify everything is up and running too
We use this...
for i in $(cat server_list); do echo $i $(ssh $i uptime); doneProduces a nice list of the uptimes for every system.
-
We reboot the second Wednesday after patch Tuesday at 3am.
-
we have a pair that are on a schedule to reboot,... one is a SAP server that has print issues if running for two or three weeks without reboot. It's weird,.. but hey,... it's SAP.
-
@gjacobse said in Reboot your servers:
we have a pair that are on a schedule to reboot,... one is a SAP server that has print issues if running for two or three weeks without reboot. It's weird,.. but hey,... it's SAP.
Weird that it has managed to keep working for two weeks?
-
@StrongBad said in Reboot your servers:
@gjacobse said in Reboot your servers:
we have a pair that are on a schedule to reboot,... one is a SAP server that has print issues if running for two or three weeks without reboot. It's weird,.. but hey,... it's SAP.
Weird that it has managed to keep working for two weeks?
weird that printing quits..
-
@scottalanmiller said in Reboot your servers:
@wirestyle22 said in Reboot your servers:
Zabbix monitoring is super convenient for my weekly reboots. If something doesn't come back I will receive an e-mail but I also remote into it to verify everything is up and running too
We use this...
for i in $(cat server_list); do echo $i $(ssh $i uptime); doneProduces a nice list of the uptimes for every system.
I now do:
ansible all -a "uptime" -
@gjacobse said in Reboot your servers:
we have a pair that are on a schedule to reboot,... one is a SAP server that has print issues if running for two or three weeks without reboot. It's weird,.. but hey,... it's SAP.
Hey my brother in law sells their stuff.
-
At work: every Friday for Workstations, if it is needed, and Every Sunday for Servers if it is needed.
Home: Autoreboot after they are installed on my laptop, cause I dont care, most my crap is web based. Home Lab: Every Sunday at 11AM.
My 1 rule, don't suck at patching. -
@Texkonc said in Reboot your servers:
At work: every Friday for Workstations, if it is needed, and Every Sunday for Servers if it is needed.
Home: Autoreboot after they are installed on my laptop, cause I dont care, most my crap is web based. Home Lab: Every Sunday at 11AM.
My 1 rule, don't suck at patching.What does "if it is needed" mean?
-
I'm updating and rebooting my servers right now.
-
@scottalanmiller said in Reboot your servers:
@Texkonc said in Reboot your servers:
At work: every Friday for Workstations, if it is needed, and Every Sunday for Servers if it is needed.
Home: Autoreboot after they are installed on my laptop, cause I dont care, most my crap is web based. Home Lab: Every Sunday at 11AM.
My 1 rule, don't suck at patching.What does "if it is needed" mean?
When patches are released, because you very well know, patching is the last thing customers think about. Although this is one thing I would like to audit as one of my other projects. New guy, fresh set of eyes.
-
@Texkonc said in Reboot your servers:
@scottalanmiller said in Reboot your servers:
@Texkonc said in Reboot your servers:
At work: every Friday for Workstations, if it is needed, and Every Sunday for Servers if it is needed.
Home: Autoreboot after they are installed on my laptop, cause I dont care, most my crap is web based. Home Lab: Every Sunday at 11AM.
My 1 rule, don't suck at patching.What does "if it is needed" mean?
When patches are released, because you very well know, patching is the last thing customers think about. Although this is one thing I would like to audit as one of my other projects. New guy, fresh set of eyes.
Why not call "updating for updating's sake" "needed" and then update every week
-
This post is deleted!
