After a couple of days, some commands related to the disk (df) or files (ls) or killing process (kill -9) doesn't respond. Even I can't reboot or shutdown my server. After an hard reboot, some files are not here anymore or the log files are not filled anymore until I restart.My disk are behind the RAID controller i6 and are configure in RAID 1. The disks are two HP SCSI 72,8GB 10k RPM.Maybe I am totally wrong to check the disk access side, so I am open to other explanation.I can also add that my CPU is running under 1% et my RAM under 10%.
I need to know how to configure automate sending sms if server reboot and shutdown? Now i just set sms notification once my server it's UP by create scripts in /etc/rc.d/rc.local while booting then from server sending sms notification. SMS - using gnokii attached mobibe phone. Server - Fedora 10
Further to this LQ thread which Tinkster solved by suggesting the last command (thanks Tinkster) I have been exploring last -x reboot and have found that the reported duration is incorrect for the last reboot and shutdown when a old wtmp file is used. Not having a record for the following shutdown, last assumes that the system has been up until the current time and similarly for the shutdown.
The output comes in time order, latest first, each line showing the time of the reboot and the uptime from then to shutdown. Using last -x reboot shutdown to show the shutdown time, here's an illustration
shutdown system down 22.214.171.124-smp Sun Mar 7 15:35 - 03:02 (11:27) reboot system boot 126.96.36.199-smp Sun Mar 7 09:35 (05:59) 09:35 until 15:35 is 05:59.
When the uptime exceeds 24 hours it is shown as (<days>+<hours:minutes) like this Code: shutdown system down 188.8.131.52-smp Sun Feb 21 12:39 - 13:20 (00:40) reboot system boot 184.108.40.206-smp Sat Feb 20 09:39 (1+02:59) 09:39 until 12:39 the next day is 1 day 02:59.
The time in parentheses at the end of the shutdown lines is normally the time until the next shutdown.
So far so good. The incorrect output is for the last reboot and shutdown of an old wtmp file. Here's the output of last /var/log/wtmp -x reboot shutdown; last -f /var/log/wtmp.1 -x reboot shutdown
[snip] reboot system boot 220.127.116.11-smp Fri Mar 12 07:42 (01:54) shutdown system down 18.104.22.168-smp Fri Mar 12 01:31 - 09:37 (08:05) wtmp begins Thu Mar 11 08:25:26 2010 [snip] reboot system boot 22.214.171.124-smp Wed Mar 10 14:12 (15+01:42) shutdown system down 126.96.36.199-smp Wed Mar 10 12:41 - 15:54 (15+03:13) [snip]
The boot started at "Wed Mar 10 14:12" which had an actual uptime of 1 day 11:20 is reported as 15 days 03:13 which is the time from then until the last -f /var/log/wtmp.1 -x reboot shutdown command was issued. The time from shutdown to shutdown is similarly affected.
Recently I installed Fedora 12 64bit in my HP Compaq 6720s. Among many other problems that I had and I solved with your help, I have the following problem:When I restart or shut-down Fedora 12 it crushes and hangs and only thing that I can do is to stop and restart my laptop by means of ON/OFF button.My question is:Is there any way to see this error (maybe some log file or something) so I can send this message or log file here in this forum and get some help?
I hoping someone can point me in a direction. I installed F13 KDE from the live cd and now when I Shutdown or Reboot, it takes 2 minutes and 8 seconds for the machine to power off. Yes, I timed it.Happens everytime like that. Even when booting from both "mainstream" live cd and the KDE spin live cd. When I hit the Shutdown or Reboot, it goes through the daemons/services shutdown the flashes up the Halting System or Please wait while the system reboots messages (respectivley), turns off the LCD and then just... sits with the power light on and hard drive activity light on. I should mention this is on a Toshiba Laptop about 2 years old now. Intel Chipsets. (Satellite Pro S300M-S2142 if anyone is really curious). The hard drive light stays on for about 1:03 minutes and then it turns off, at 2:08 minutes - the Power light finally turns off and the thing finally shuts down or reboots. If this sounds familiar, it's because it is and I've posted about it with F12 and it's still there with F13. Running kernel-188.8.131.52-85.fc13.x86_64
I don't follow why the Suspend option is there and the Reboot and Shutdown is not. Can anyone guide me to the code needed to add the selections. I know I can use a Terminal to shutdown or reboot but a simpler solution would be nice. I expect there are methods to fix most of what I don't like about Gnome 3 but I haven't found them yet. Is there a central place for the solutions needed to deminimalize Gnome 3? I really prefer one click control.
I installed 11.04 server and had samba share /tmp (as advised by the server pdf doc) shared to my windows 7 laptop, which was all well and good, so copied some files to it and rebooted the server, and they had been removed.i guess i shouldnt have put anything in /tmp as i presume this is cleared on reboot, so why did the documentation advise to create /tmp share?
Ok so I followed the instructions here [url] and this works great for the install however if the machine is rebooted the VMWare server refuses to start back up stating that it knows that its installed but it was not installed with the right installer.
This is on a Dell Server I can't remember the model right now but its got Dual PIII in it. I'm running Ubuntu Server 32bit 10.10 on the box as well. Thank you in advance for your assistance with this. Once I get this first server figured out I'll get my other one fired back up.
I'm writing you to ask some help with administrating a server remotely. I have a machine I use remotely when I have to travel, some time for quite long periods like from one to three months. Last time it happened to me that after upgrading I send the reboot command and the machine didn't turn down, so I couldn't be able to access it. My question is: how can I avoid such situations? Is there any best practice to follow?
I'm a light linux user over the last couple of years and I decided to built a HTPC/NAS device.
Setup: 40gb ide -> usb boot drive 3x2tb sata (4k Sector) drives
I've got another 2tb identical drive but it's holding data that is going to be copied to the raid after it's up and running and then be 'grown' into the raid array to yield a final 5+tb array. I tried doing a disk util raid array and it ended up failing after reboot due to it using the /dev/sd* designations and they swapped. I have no idea how to do the UUID version, my googlefu and practical guide to ubuntu. So I decided to do it manually in order to also fix the sector issue as disk util wasn't formatting them correctly and once formatted wouldn't let me create a raid array from the discs.
Ok this is one of those questions that have probably been made often. But I just CANNOT find a way around this on Fedora, and i have searched for it alot. Basically, after remotely rebooting my server, i'm not able to connect through vnc because the server needs to login. I've looked into an automatic login, but this is not the way i want to go. Edit: I'm using the default fedora vnc server, and RealVNC on my Windows computer. Been to ##linux on freenode, but at the time, noone there could answer me either.
After booting I noticed that sometimes nmb was not running. The command # service nmb status gives nmbd dead but pid file exists The timestamp of the pid file suggests that at the last shutdown the pid file was not removed, and I guess this prevented nmb to start properly during booting (Although during booting the messages is [OK]).
If I shut down nmb manually, everything is fine. I checked the log in /var/log/samba/log.nmbd and it doesn't show any error. As mentioned, this occurs only occasionally, and I have no idea what may be causing this.
I have recently upgraded to the 10.04 Alpha and have been unable to reboot or shutdown. I know it's just an alpha and therefore problems are bound to exist, so I tried reinstalling from a live cd of Alpha 3. But I am still unable to reboot or shutdown.To clarify what happens, I click on shutdown or reboot, the pop-up appears, I click on the shutdown/reboot button and it seems to complete it. It says that processes have been killed and something has exited with 255. But my computer is still on. I am guessing that Ubuntu is shutting down, it's just not actually shutting my computer down or restarting it.
I have a remote server (Xubuntu 10.04) which suffered an electricity brownout yesterday. The server itself is backed with an ups, but it is connected to a external firewire disk, which is not, and this disk malfunctioned as a result of the brownout.
The problem: Now, any process trying to access the external disk freezes and ends up in eternal D state in the process list, including ls and umount. Even trying to ls a directory which contains a symbolic link to a file in that drive just causes ls to freeze. These processes cannot be killed even with SIGKILL, so I proceeded to reboot but...
None of the reboot commands work. Instead they just get added to the ever increasing list of D state processes. I tried (sudo) shutdown -r now, reboot -f now and finally plain shutdown -h now. Is there anything else to try other than ask somebody to actually go to the server and pull the plug (which is not at all trivial)? Some way to tell kernel not to worry about messing stuff up, and just reboot?
we've just bought 30 newest nettops ACER Aspire R3700 with ION 2. I've tried ubuntu, kubuntu, xubuntu. Everything works as expected, but... the first one freezes when trying to reboot, shutdown or enter sleep mode. Checked on several hardware units. The desktop just freezes and nothing happens (ubuntu 10.10, both x32 and amd64). Also no one installs the wi-fi drivers, only ethernet
From a 11.04 Ubuntu, I installed the meta-package xfce4 (*). Now, in the xfce4 session, "suspend" and "logout" (from the xfce4-panel button) works, but "shutdowmn" and "reboot" not, they only lead to GDM. (the shutdowm option there works.)
I tried to solve that by installing the meta-package "xubuntu-desktop" (maybe there are some necessary settings included?), and in fact, the login-screen changed (it's still GDM, I suppose) and there is now a "xubuntu" session, but in that, the probem is just the same: shutdown only leads to the login screen.
In Gnome Classic or Unity, shutdowmn works as it shoulds, so it's not a general problem with my computer.
In Detail, in forst tried to install xfce4 with ubuntu-software-center, but although it seemed to succeed, there was no xfce session. In Synaptic, installing the xfce3 metapackage worked. In fact, software-center seemed to have overlooked some dependencies...
I am facing the issue that the PC not capable to shutdown or reboot; In order to debug that, htop tells me the running processes but all seems normal, I killed few but still cold reset is needed.There is certainly a problem somewhere. the best would be to know which process are weirdly hanging. It could make this testing debian bit better to know which package has these issues.
I have installed a cluster computer with 10 nodes . The manufacturer is HP . All nodes and the master node have redhat enterprise linux installed in them . When I shutdown the nodes from the master terminal using "shutdown -h now" they get shutdown . But they dont get completely turned off . This issue bothers me when the power supply is given , all nodes boot up simultaneously generating a huge heat .
Thing to note : When we shutdown our PC they get completely turned off . When the power supply is given , a press on the Power On button is required to boot the system. But , why does it not happpen in the case of cluster? Is there any other way of completely turning off the nodes from the master terminal ?
A couple of little niggles seen with KDE4.6. On 32bit install, (openSUSE11.3 was clean install)
-- reboot and shut down do nothing but hibernate and sleep are ok, can only powerdown with su privileges, -- order of applications in plasma bar change after reboot.
On 64bit install, (openSUSE11.3 was update of openSUSE11.2)
-- slow poweroff overcome with new user profile, (no longer a problem with latest update) -- inconsistent mouse curser theme, over desktop theme is Oxygen White, over application windows its DMZ (resolved mouse cursor theme issue on 64bit install. -- /etc/sysconfig, parameter X_MOUSE_CURSOR="DMZ" -- and -- /usr/share/icons/default was a link to DMZ -- /usr/share/icons/default.kde4 was a link to oxygen -- changed so that both were linked to DMZ -- mouse cursor now consistent within windows and across desktop.
On one of my computers that I upgraded from 11.3 to 11.4 with a SSD HDD, it no longer umounts any disks on reboot or shutdown, there are no errors shown, it goes from sending TERM and KILL to rebooting.here is my fstab:
I recently migrated from Hardy 8.04 LTS (32) to Karmic 9.10 (32) so that the restricted ATI drivers and CCC would work correctly - that part is basically fine.
The problem for the past couple of weeks has been Karmic randomly shutting down, and rebooting the system after 1 or 2 hours up-time.
Why would this be happening, it was fine for the first few weeks after installing Karmic.
My system currently consists of the following; Gigabyte MA790FX-DS5 mainboard - Jan '08 AMD 3.0Ghz Phenom II X4 945 CPU - Oct '09 4GB DDR2 Kingston HyperX RAM (1066 MHz) - Jul '09 Sapphire ATI HD5770 1GB GDDR5 video - Dec '09 Cooler Master Extreme Power Plus 640 watt power supply - Nov '09 Cooler Master Centurion 5 CAC-T05 case - Jan '08 1 pata 500 GB, 3 sata 500 GB & 1 sata 640 GB drives 2 DVD burners (Pioneer and LG) 2 x 19" (4:3) Samsung SyncMaster 943N LCD monitors
I used to have lmsensors working with the Athlon 2.8GHz dual core in Hardy, but they wouldn't work with the new Phenom 3.0 GHz 945 CPU in Hardy (and they still won't work in Karmic).
Th upshot is that I don't have cpu, system, or graphics temps; nor do I have any fan speeds, so I don't know what temps or fan speeds my system is running without rebooting into BIOS (which isn't much good as I really need to know what's happening when I'm using the OS itself).
Does anyone know what could be causing this random shut-down/reboot problem?
I've added entries to my Openbox menu labeled Reboot and Shutdown. Problem is, reboot and shutdown h only work as root, and I never login as root. I've tried su-to-root -c reboot, but the menu entries remain unresponsive. I do not have sudo installed because I feel it is a security issue. However, I found that sudo reboot works with the menu entry, but only if my account is set to use sudo without a password in /etc/sudoers. I use tint2 as my panel, but have had no luck with finding a shutdown/reboot button.
I want to do a shutdown -rF 3:00 to reboot my RHEL server at 3am tomorrow and force an e2fsck on each volume. But I want the e2fsck to run with the -y switch so it automatically answers yes so it will fix any problems it find automatically.
I can't find anywhere where it says if it will do this or not. does anyone know or have proof? Or is there a better way to do what I'm trying to accomplish?
I am experiencing serious trouble with my nfs server at office. That server contains the home directory which is exported to all our desktops. Since a few days now, it gets freezed and thus our desktops as well. I found a way to unfreeze it by pushing the power button, the server does not reboot but instead open the boot popup, i then click on cancel. I checked the dmesg file and found these messages: