I will reboot a redhat server that do not reboot for over 3 years , the servers is installed and adminstered by former staffs , I am worry what will be missed after reboot , what is most possibly missed after reboot , what I need to know before reboot ? I just think about the mount point , ps service running , is there else I need to know to ensure the server will be restarted without error ?

thanks

There's no way for anyone here to answer that question in a meaningful way. If you are the admin now, then YOU should already know what services are running on them, what the mount points are for what devices, etc. We don't know any of that, so we can't tell you what to check. Perform basic admin tasks, list the running services, and be sure you have a backup of everything before rebooting.

3 members found this post helpful.

Additionally, if you don't know that: it is exactly you who can collect all the relevant info. But actually there is no guarantee, you can never be sure.

You should also make your higher-ups aware of the possibility that: you might NOT be able to get the machine running again!

Another (wild?) idea:
IDK if it's technically reasonable to: make like a `dd` copy of the boot disk, without disturbing the running machine, and try booting it on a spare machine. You would likely run into expected issues because the environment is different, like other disks and networking, but this would give you the opportunity to evaluate your troubleshooting ability!

P. S. Remotely: https://unix.stackexchange.com/quest...o-a-local-disk

And, these days, one might ask chat.openai.com how to do their work!

IF you've forgotten your original LQ account (like ck_chik), you can use the 'Contact Us' link, at the very bottom of any page.

You can improve your thread's title
by clicking the Edit button on #1,
Then clicking the 'Go Advanced' button.

1 members found this post helpful.

"what I need to" do is rename my title as something that makes sense to my needs? Red Hat Servers have support: (as said :) https://www.redhat.com/en/contact

1 members found this post helpful.

Ensure you have got a root login on the console (not over ssh). Then you can repair nearly everything on the console.
Any changes to the system bear a little risk. If lots of changes have accumulated over the years then the resulting risk is high, especially if they are not documented.
Patches are well tested and documented, and can be backed out. They are changes with the lowest risk.
Firmware patches bare a risk, obviously some cause a switch from BIOS to UEFI. Easy to fix if you know the problem.
The biggest risk are the bad admin guys that remove or spoil files. E.g. it is easy to spoil /etc/fstab ... fixable at the root console.

1 members found this post helpful.

Means that the kernel has not been updated/booted into in 3 years. You may want to look through what problems that the kernel versions have introduced and have been fixed over the years. And what open kernel bugs are in the kernel that you are going to update to.

Since about kernel 5.5, the kernel itself has been a source of problems. Or perhaps everything else is not keeping up with the kernel development.

Something to ask redhat about.

1 members found this post helpful.

My 2 cents to check:

- mount point, fstab
- check services that are running, export it to a file like
like systemctl > systemctl_backup
- cron jobs
- network settings
- as what other suggest make sure you got root access
- do a ss or netstat check open ports or connection save it to a file who knows you might need it
- check firewall settings / iptables
- backup if you got a chance
- its on your environment check what you think is important or might be needed

- what I will do before restarting is turn off the nic if possible, or just simply plugged out the network cable if it is a physical machine
let it be down as long as time allows
- check what will happen to your environment, if someone complains this one is not online, or other users will complain i don't have access to this
then you will know or will have an idea what to check

Goodluck..pray hard nothing will happen.

And this is the second time you've posted in someone elses thread, your other being in one that was closed for three years.