search for: reboots

Hi, I''m working on a method to manage packages which require a reboot after being installed. I''m curious how other people are handling this problem. Consider the resource: pkg_deploy { "MacOSXUpdCombo10.4.9Intel.dmg": alias => macosx1049 } I''d like to only install the package under if the following conditions are met: - No user is logged into the

...is being rebooted virsh # reboot test1 Domain test1 is being rebooted virsh # reboot test1 Domain test1 is being rebooted virsh # destroy test1 Domain test1 destroyed If the VM shutdown and then start, the problem does not occur. The problem does not occur if the VM CentOS 7.3.1611 (10 successful reboots of 10) or if the VM Windows Server 2008 R2 (10 successful reboots of 10). If the VM CentOS 6.8 and HV CentOS 6.8 the problem does not occur. First HV is: CentOS 7.3.1611 with 3.10.0-514.6.2.el7.x86_64 and 3.10.0-514.6.1.el7.x86_64 qemu-kvm-ev.x86_64 10:2.6.0-28.el7_3.3.1 libvirt...

...is being rebooted virsh # reboot test1 Domain test1 is being rebooted virsh # reboot test1 Domain test1 is being rebooted virsh # destroy test1 Domain test1 destroyed If the VM shutdown and then start, the problem does not occur. The problem does not occur if the VM CentOS 7.3.1611 (10 successful reboots of 10) or if the VM Windows Server 2008 R2 (10 successful reboots of 10). If the VM CentOS 6.8 and HV CentOS 6.8 the problem does not occur. First HV is: CentOS 7.3.1611 with 3.10.0-514.6.2.el7.x86_64 and 3.10.0-514.6.1.el7.x86_64 qemu-kvm-ev.x86_64 10:2.6.0-28.el7_3.3.1 libvirt...

Add support to the reboot command so an argument for the 4th parameter of the syscall can be passed around. --- usr/include/sys/reboot.h | 4 ++-- usr/klibc/reboot.c | 6 +++--- usr/utils/halt.c | 36 ++++++++++++++++++++++-------------- 3 files changed, 27 insertions(+), 19 deletions(-) diff --git a/usr/include/sys/reboot.h b/usr/include/sys/reboot.h index 3337d27..b46a1c5

Commit-ID: 6b621b8705ce5901dcf49607c8a3523c9e521901 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=6b621b8705ce5901dcf49607c8a3523c9e521901 Author: Alfonso Sanchez-beato <alfonso.sanchez-beato at canonical.com> AuthorDate: Wed, 31 May 2017 08:34:04 +0200 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Wed, 2 Jan 2019 03:06:15 +0000 [klibc] Add

...ong the lines of: "If you have to reboot, your server isn't set up correctly" to which I say piffle. Even NASA has rebooted the Mars probes after they land and I understand that they run VXWorks, incidentally, the same RTOS that my Mitel 3300 uses, and *even Mitel* recommends periodic reboots, which we duly cron every night, 2 AM. 24/7/365 installs aside, is there a reason why reboots seem to be frowned upon? Again, not trolling, just curious.

What is the rule of thumb for reboots after updates... Certainly if I update from 5.2 to 5.3 I reboot. But if you update something like krb5 or pam does that require a reboot? Does the "fix" get automatically loaded and used or do you just do a reboot always? Thanks, Jerry

Hi, I was just wondering if I should reboot some servers that are running over 180 days? They are still stable and have no problems, also top shows no zombie processes or such, but maybe it's better for the hardware (like ext3 disk checks f.e.) to reboot every six months... btw this uptime really confirms me how stable Centos 4.x really is and so I wonder how long some people's

Hi, I have a CentOS 5.0 running as a web server. # uname -a Linux hostnamehidden.net 2.6.18-53.1.14.el5 #1 SMP Wed Mar 5 11:37:38 EST 2008 x86_64 x86_64 x86_64 GNU/Linux Every 59 minutes (maybe every hour) it reboots without any logs, without any traces and unfortunately with breaking software raid. After reboot dmesg does not have any strange entries. I double-checked crons, any strange services, nothing suspicious. I did "yum update" recently. I went to Datacenter and waited before the monitor bu...

***Do you perform downtimes just for the purpose of rebooting the systems? ***Is there a recommended interval Linux system should be rebooted? -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos/attachments/20050602/189d0dbf/attachment-0004.html>

Hello, I have a machine that seemed to reboot by itself yesterday, in /var/log/messages I only see: Mar 25 14:26:45 asterisk shutdown[19256]: shutting down for system reboot When I type: last reboot I see: reboot system boot 2.6.18-8.1.8.el5 Tue Mar 25 14:28 (18:41) So it seems like the kernel rebooted, but I'm not sure how I can track down why, any pointers? Thanks!

Is there a way to remote reboot a Cisco 7940 or 7960 phone via some kind of command? The idea is to force a reboot automatically after changing one of the configuration files. Regards, Paul -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20070527/857bdda8/attachment.htm

Hi, Can you give me some councils of remotely rebooting sip phones in asterisk server? How to configure sip_notify.conf and sip.conf? Kind regards, Guan ; Reboot Polycom Phone Event=>check-sync Content-Length=>0 ; Untested (Reboot Sipura Phone) Event=>resync Content-Length=>0 ; Untested (Reboot GrandStream Phone) Event=>sys-control ; Untested (Reboot Cisco Phone)

With Asterisk 1.4 I could use commands like: /usr/sbin/asterisk -rx "sip notify reboot-snom mjc_home" to reboot a snom phone. Now, with 1.6, when I try that, I get: Unable to find notify type 'reboot-snom' Command 'sip notify reboot-snom mjc_home' failed. Do I need to add some magic to sip_notify.conf? I haven't quite figured out how to make it work. - Mike

...1 on a HP ProLiant DL 165 G7 server. Recentely I upgraded to CentOS 6.2 but at reboot the system didn't startup. So I removed new kernel kernel-2.6.32-220.4.2.el6 and CentOS was again able to startup with original kernel-2.6.32-71.el6.x86_64. But now every two days the system automatically reboots as you can see below: reboot system boot 2.6.32-71.el6.x8 Wed Feb 22 22:53 - 17:10 (18:16) reboot system boot 2.6.32-71.el6.x8 Wed Feb 22 20:04 - 17:10 (21:06) reboot system boot 2.6.32-71.el6.x8 Fri Feb 17 22:55 - 17:10 (5 +18:14) reboot system boot 2.6.32-71.el6.x...

Thank you Roger, I appreciate the response. I'll have to check my commands, I believe I started it with those systemctl commands you provided. What I can say is that oddly enough after completing the server config and after two more reboots a reboot of the Pi doesn't seem to be causing the UPS to reboot anymore. I have a bit more config to do on slave machines tomorrow but after that I'll do testing - including pulling the plug - and see what happens. I do recall from reading the documentation that the master can initiate a r...

Hepp! I am sitting in a remote country trying to reboot my server at home. Services are running, but the filesystem seems to be unreachable. I can ssh into the system, but when entering interactive mode, nothing happens and the session is terminated. Then I thought - what if sshd had builtins like bash, so that i could send a "reboot" command to the ssh daemon instead "ssh system

Hello all, I've got a CentOS box that became non-responsive today for some obscure reason and had to be rebooted. Is there a way to find out when it last had to be rebooted before today? uptime gives you no history past the very last reboot, so obviously I need to find some other way to get an answer to my question. Thanks for any and all tips. Boris. -------------- next part --------------

Forgot on the Snom 200 it won't reboot if under the Memory tab in the web interface, Connections > 0 then remote reboot is not possible. Manually cycling the power allows the phone to be rebooted by Sipsak remotely. HOWTO: Reboot a Snom with Sipsak Checklist: 1. Under Advanced in the web interface, is Network Identity set to 5060? 2. Under Advanced in the web interface, is Challenge for

I'm curious why any user logged in at the console can issue the 'reboot' command and reboot the system.? I've tested/verified this to work, and read some older posts about this.? If it were a bug, I suspect it would be fixed by now. Also, if a user is logged into the console, and then logs in via ssh from another system, that user can also reboot the system from that ssh