Should I always restart the system when I see “System restart required”?

1

Should I restart when prompted?

Yes, you should. For most cases, a restart is required when an update to the Linux kernel has been installed. These updates are usually security updates, and then only come into effect after a reboot. Updates to normal applications such as Firefox come into effect after you restart the program. Firefox should prompt you to do this automatically, but other programs may not, so it's something to bear in mind.

How to restart:

To restart the computer in Ubuntu 12.04, click the power icon in the upper right corner of the screen, and select "Shut down...". In the dialog that appears, a "Restart" button should be visible. In Ubuntu 12.10, the restart option appears in the power menu directly.

To restart from the command-line, run this command:

$ sudo reboot

The downsides of restarting:

On the whole, restarting is a very safe operation, and I would not consider it in any way unsafe. Of course, when you restart the...

0 0
2
Here is what shows up when I login:

Linux server1 2.6.32-21-generic-pae #32-Ubuntu SMP Fri Apr 16 09:39:35 UTC 2010 i686 GNU/Linux
Ubuntu 10.04 LTS

Welcome to Ubuntu!
* Documentation: https://help.ubuntu.com/

System information as of Wed Jun 9 13:44:41 EDT 2010

System load: 0.0 Memory usage: 21% Processes: 121
Usage of /: 1.1% of 140.41GB Swap usage: 0% Users logged in: 2

Graph this data and manage this system at https://landscape.canonical.com/

*** System restart required ***
Last login: Wed Jun 9 13:27:53 2010 from xxx.xxx.xx.xxx

We like the system information about the system load and the memory usage, etc, but "*** System restart required ***" always shows up, even after we restart the server. Looking at /etc/motd, it has everything that I displayed above. Notice that the time is given in the motd. Every time a user logs on the the server, the motd is updated and shows the current system information...

0 0
3

These two nice SE posts (1, 2) comment on restarting one's ubuntu machine but they leave me with a few questions:

Always try to Restarting the pc after ubuntu updates, install drivers and some application that wants to restart the OS(ubuntu).

when new updates are installed or driver is installed these wants to restart the OS for working performance and properly use.

Normal application or package don't need to restart the OS after installed.

Gaurav Sharma
February 19, 2013 17:39 PM

Should I restart when prompted?

Yes, you should. For most cases, a restart is required when an update to the Linux kernel has been installed. These updates are usually security updates, and then only come into effect after a reboot. Updates to normal applications such as Firefox come into effect after you restart the program. Firefox should prompt you to do this automatically, but other programs may not, so it's something to bear in mind.

How to...

0 0
4

To learn a bit of server administration I've set up a simple Ubuntu 14.04 server on which I run a personal website. I've set it to automatically install security updates, but leave out the other updates. This seems to work pretty fine. Occasionally I get a message when logging into the server (with ssh) saying:

*** System restart required ***

The times this happened I simple rebooted Ubuntu and all was fine. This is ok because it's a simple personal website. What I wonder about though, is how this works for webservers which should be up 99.9999etc% of the time? Do they simply not restart and risk the security being breached because security updates are not installed (which I cannot imagine)? Or do they take the downtime for granted (which I cannot imagine either)?

How should I handle this if this were a very important production server which I want to keep up and running? All tips are welcome!

[EDIT] I know I can do cat /var/run/reboot-required.pkgs to list the...

0 0
5

These two nice SE posts (1, 2) comment on restarting one's ubuntu machine but they leave me with a few questions:

How do you actually do the restart (I'm a beginner and using 12.04.1 LTS)? Should I always restart the system when prompted to? Does restarting the system affect access to it via SSH or there any other caveats one needs to think about before doing this?

Should I restart when prompted?

Yes, you should. For most cases, a restart is required when an update to the Linux kernel has been installed. These updates are usually security updates, and then only come into effect after a reboot. Updates to normal applications such as Firefox come into effect after you restart the program. Firefox should prompt you to do this automatically, but other programs may not, so it's something to bear in mind.

How to restart:

To restart the computer in Ubuntu 12.04, click the power icon in the upper right corner of the screen, and select "Shut down...". In the...

0 0
6

On Wed, 2011-04-27 at 13:27 +0100, Colin Law wrote:

> When this happens is it necessary to reboot fairly urgently or is it

> ok to delay this till a convenient time. In other words is there a

> significant difference between delaying the update because it will ask

> for a reboot, and delaying the update itself.

In my experience, you don't need to reboot immediately. But if it was a
kernel update (to the same number kernel, not a new one), suspending or
inserting new hardware may be unreliable. If it was an important library
like libc6, starting new applications may be unstable, but the
currently-loaded ones are fine.

My rule is: update immediately, and reboot at the end of the day, before
trying to put the laptop to sleep.

Regards,
Tyler

--
"The belief in immortality has always seemed cowardly to me. When very
young I learned that all things die, and all that we wish of good...

0 0
7

FIX : Your PC Ran Into a Problem and Needs to Restart. We're just collecting some error info, and then we'll restart for you. (0%)
If you'd like to know more, you can search online later for this error: INACCESSIBLE_BOOT_DEVICE

Many times the following error "Your PC Ran into a problem and needs to restart. We're just collecting some error info, and then we'll restart for you." makes a lot of trouble for you and it does not even let you login. It automatically goes into the infinite restart loop mode. So here is the solution.

Eventually this error message stands for a very short time. So when you start your system, this error pops up like for a second and then suddenly restarts the system.

So after the error pop up, immediately system restarts and then starts this "Automatic Repair". After sometime it starts "Diagnosing your PC" and finally when it finds out there is nothing to do more, comes up with these tow options "Restart and Advanced Option".
So...

0 0
8

With the default configuration on Debian, an unprivileged user will have access to neither the systemd-journald, nor syslog logs. If logged in as a normal user, you will receive this response from journalctl:

$ journalctl No journal files were found.

which is a bit confusing.

If you are logged in as root, journalctl --unit=yourservice should give you the information you are looking for. After a systemctl restart bind9 on my server, I get this after journalctl --unit=bind9:

Jun 03 18:20:24 ns systemd[1]: Stopping BIND Domain Name Server... Jun 03 18:20:24 ns named[27605]: received control channel command 'stop' Jun 03 18:20:24 ns systemd[1]: Starting BIND Domain Name Server... Jun 03 18:20:24 ns systemd[1]: Started BIND Domain Name Server.

If I kill bind9 explicitly with kill -9, journalctl --unit=bind9 gives:

Jun 03 18:46:25 ns systemd[1]: bind9.service: main process exited, code=killed, status=9/KILL Jun 03 18:46:25 ns rndc[28028]: rndc: connect failed:...
0 0
9

Fixed my issue! The steps that fixed it for me are:

1. Identify the base stations that are staying on.

2. Run up steam vr - wait for everything to go green.

3, Unplug or turn off at the socket all base stations identified in step 1 above.

4. Wait for a minute or two for the offending base stations to properly power down.

5. Plug back in, or turn on at the mains, the offending base stations.

6. Wait for everything to go green.

7. Go to the Vive's devices->reboot headset.

8. Wait for everything to go green again.

9. Close down steam vr - all base stations should shut down shortly thereafter.

Seemed to work for me. Almost like some status flag was out of sync between the headset and basestation. Your mileage may...

0 0
10

Wipton2,

I found this - there is no explanation on why Windows goes sideways, thinking it's crashing when it's only being shut downl; nonetheless, this setting may help until you do track it down or decide on a long term fix.

Control Panel > icon view > System > Advanced system settings > Startup and Recovery >

Settings > System failure > UNCHECK Automatically Restart > OK ...

You'll want to go back and check for recent changes - new devices added, updates... something has changed that makes your system think that the shutdown is a crash.

There may be something running, a process, that won't stop properly. If you have not done so, it might be time to run a deep scan of your file system: using sfc AND then using your best anti-virus software. The sfc scan will help make sure the file system is healthy and that is your first line of defence. The Anti-virus scan will help make sure you don't have anything on the system that does not belong...

0 0
11

Fedora Domain Join Error 0x0008O046: System Restart Required

Hello Jenny,

The first thing that I will ask you to do is to check that you indeed set up the correct time and date, and regional settings too during the installation. A mix in the time settings may be the one possible cause of the problem. Also ensure that Linux is running in the enforcing mode which allows you to perform system functions as a super user.

Otherwise you could just run the reboot command in the kernel to restart your computer system (but do this after enacting the changes that have been stated above, so that when the computer reboots the changes will take effect) and see if works well after restarting.

Hope this helps,

__

Regards,

Lee...

0 0
12

Every so often, I'll SSH into a box with unattended-upgrades and be greeted with "** System restart required ***" with no additional information.

My '/var/run/reboot-required.pkgs' file contains:

linux-image-3.13.0-61-generic linux-base linux-base linux-base

I don't mind rebooting, but I don't like rebooting without having details of WHY I should reboot in the first place. Above, I see two packages triggered the message, but there's no explanation beyond that.

Is there a way to get additional details about the reason for the reboot to also show up on SSH sign in?

Ideally, I would like to pull in a file that contains something human-readable like, "Package xyz was updated at [date/time]. It needed to modify files a, b, and c but could not because the system blocked/would block the action. During the next reboot, files a, b, and c will be replaced." But something not completely human-readable is probably okay too.

Edit: Another, probably relevant or...

0 0
13

Thank you for your feedback! In order for us to investigate this further, could you please give us a setup log file so that we can conduct further research?

You are able to get the files with the following steps:

1) Download collect.exe from the link http://aka.ms/vscollect .

2) You may choose to save the tool for later use, or to run directly.

3) The utility creates a compressed cabinet of all the VS and .NET logs to %TEMP%\vslogs.zip.

4) Upload your vslogs.zip by choosing insert file tag on add comment field then submit after signing in.

You can get more details about how to get the log files here: http://blogs.msdn.com/heaths/archive/2008/05/09/visual-studio-and-net-log-collection-utility.aspx

We look forward to hearing from...

0 0