CentOS 5 :: Server Does Not Shutdown Properly Sometimes
Aug 17, 2010I have noticed my server do not shutdown properly sometimes.It should do it with this command in a cron with root session /sbin/shutdown -h now
View 3 RepliesI have noticed my server do not shutdown properly sometimes.It should do it with this command in a cron with root session /sbin/shutdown -h now
View 3 RepliesI have a centos 5.5 server running great, but i am having issues with my xen vm01 virtual machine. The first probelm is, i have created the vm01 fine and it was running ( even though i can not login into it ) by running:
vm console vm01
I use centro 5 to run a game server with the command ./srcds_run quit -game cstrike -nocrashdialog +map de_dust2 +maxplayers 36 +ip 95.154.192.34 +port 27015 -tickrate 67
which then starts a 36 slot CSS game server but as soon as i close putty it ends now i tried nohub ./srcds_run quit -game cstrike -nocrashdialog +map de_dust2 +maxplayers 36 +ip 95.154.192.34 +port 27015 -tickrate 67 and ./srcds_run quit -game cstrike -nocrashdialog +map de_dust2 +maxplayers 36 +ip 95.154.192.34 +port 27015 -tickrate 67 > srcds.log 2>&1 &
i'm woundering if it something to do with centro 5 why nohub isn't working becouse it works for others either
2 times now our server has randomly shut down. Completely powered off as if the power cable was pulled or something. Both around the same time. 7:30ish. Once was on Friday June 5th, then last night, Wednesday June 10th.
Here is the log from last nights crash/shutdown:
Quote:
Jun 10 19:23:18 mail avahi-daemon[2564]: Server startup complete. Host name is mail.local. Local service cookie is 1312323680.
Jun 10 19:23:18 mail avahi-daemon[2564]: Service "SFTP File Transfer on mail" (/services/sftp-ssh.service) successfully established.
Jun 10 19:23:21 mail smartd[2625]: smartd version 5.38 [i686-redhat-linux-gnu] Copyright (C) 2002-8 Bruce Allen .....
I'm able to connect to ftp as a virtual user. It was also difficult as nowhere mentioned, that it should be done with SSL. Anyway I found the answer and got connection. But now I can't connect to ftp server as system user. It gives me "530 Permission denied", or if I delete the user from the file denied_users, - "530 Login incorrect".
1. Still I can't understand, how I can log in to FTP server with a system user.Also some other questions regarding this matter:
2. My httpd server Apache has a virtual hosts located in "/home" directory.The scripts create users in "/var/ftp virtual_users". Will it cause any problem if I will change them to "/home"? All I need to do with this is ability to have several virtual hosts in one server with separate access to each of them via FTP. And 1 account with access to all files in "/home".
3. In my ftp client I can see the owner of virtual host "ftp" instead of username.
I have built a Centos 5.3 server for a friend of mine that is being used as a NAS server. The server has 4 1TB drives in a RAID 5 configuration and a dedicated non raid system drive for the OS. My friend isnt very Linux literate so I need this bow to be relatively simple. I have worked most of it out but have a question with regards to remote reboot.
I need to be able to shut this device down through the power switch without human intervention (at the moment when the power switch is pushed the server asks to confirm shutdown) the server wont have a Monitor connected so this isn't practical. Is it possible to use the power switch to do an clean, immediate shutdown?
The other option is shutdown through a web page is this something that has been done before? I know he can do it through terminal by issuing a shutdown now command but as I said this guy wants something simple. I don't really want to explain everytime he needs to shut the Server down how to do it if he can just do it via a website or even with the power button.
I have a very weird issue here. At work I have a machine that runs ubuntu 10.04.1 and whenever I do a "shutdown -h now" the system shutsdown for a few seconds and the comes back up again.
The system itself is a HP DC7900 SFF machine. It was the network setup along with wild flying magic packages that caused this.
I am unable to shutdown the ubuntu system properly. As i click the logout button, the desktop icons and taskbar and everything disappears and only i can see the wall paper... Then i hav to do a hard shutdown by pressing the power button...
View 2 Replies View RelatedI'm sure there's an underlying hardware problem for this... but I figured I'd start here as I do not know the specific hardware issue.
I'm in Ubuntu 9.10 (Ubuntu Studio actually) and my computer will not shut down properly. I get the splash, then a black screen, then something like #terminating processes, #closing connections, #blah blah blah, #will now halt(or will now restart if rebooting)
I'm trying to reboot the server (shutdown -r now).But it seems like nothing happened.
When I try "shutdown -c", the system prompts "shutdown: cannot find pid of running shutdown."
I am running a quad core centos 5.4 box that is having a strange problem with dovecot. The administration panel is able to send emails through dovecot but not any of the user accounts (ie with webmail). I've done a bit of research with what could be wrong but haven't had any luck so far I am also having a weird problem with apache: on a c++/php bittorrent application I was going to be running on a subdomain of my main site I get a 500 error every time I try to log in. The only way to get rid of the 500 error is to clear the chache (so its horribly broken somehow). The error generated in the log whenever I try to log in is that "ffmpeg is already loaded" (which I am running on the main site and is critical). Is there a way of either repairing my apache install or excluding ffmpeg on the subdomain in the conf or something?
View 2 Replies View RelatedI have an mysql innodb ~ 20gigs. Normally shutting down mysql (service mysql stop) takes a few seconds. When I reboot Ubuntu with the reboot or shutdown command it just reboots it super fast without mysql logging (/usr/sbin/mysqld: Shutdown complete) Also during this shutdown the following is failed: umount2: device or resource busy /data: device is busy.
mysql is setup to read from /data . Why is ubuntu not waiting for mysql to properly shutdown before unmounting the filesystem and rebooting?
I just installed apt-get hibernate and when my computer shuts down, it will go to a recovery menu. I have to end up killing the machine.
Also when I try to hibernate the machine this error msg will appear: hibernate:Warning: Tuxonice binary signature file not found.
How should I rectify this error?
I have an user space application that performs file I/O operations, when a SIGKILL is captured, some routines are done first to ensure that all I/O operations are completed before rebooting the application or system. My question is, this won't work if the power button is pressed or the power supply is disconnected, so there can be incomplete I/O operation or corrupted data written into the file, so is there a way to prevent data corruption or at least complete any ongoing operation when this scenario happens? Assuming there is at most 1 second before the power really went out, can I/O be still completed?' I'm running the application on a busybox 2.6.14 kernel on an embedded system board.
View 1 Replies View RelatedI know the problem has been partly solved in this old thread [URL] .....
Now we have Jessie as stable, yet LXDE doesn't shutdown properly:
On the same computers, Wheezy LXDE shut down very fast
I installed Jessie from the netinstall image.
On a 2007 computer, it's like the old days with a Pentium II running some version of Puppy Linux or Slitaz. The system shuts down after a while but the computer remains on.
On a 2013 laptop, I added the line init=/bin/systemd in the Grub default file as advised on the old thread above. The laptop shuts down after a while, the system first, then the hard disk goes to sleep, then all the leds are off.
If I run the magic command, the computer shutdowns in a breeze, perhaps even quicker than good old Wheezy:
Code: Select all# systemctl poweroff
Now, is this still a systemd bug? Doesn't look like it since the systemctl command works. Is it an LXDE bug? Looks like it in a way - if the LXDE shutdown button enabled the systemctl poweroff command, I suppose the button would work?
Is there a way to make the LXDE shutdown button run the systemctl poweroff command?
I'm glad Wheezy is still with us because I wouldn't install Jessie for newbies — they'd think shutdown (through clicking on a button) is even worse than in Windows.
The startup and shutdown displays are a series of vertical black and white lines, and the text displayed on them appears as more or less white blobs. Otherwise, the displays when 11.04 is running are fine, but this startup looks so naff it would be nice to change it so that the diplays can be read. I would hate to demonstrate Ubuntu to someone and have to explain such a display.
View 7 Replies View RelatedI 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 ?
When i use the shutdown-command in the terminal as root, it nearly works. It starts to shut down, and it looks like all programs and the kernels shuts down. I end up with a black screen, sometimes with the ubuntu-logo on, but it never powers off. I have to force it off by holding the power button. When i use the graphical interface to shut it down, it works perfectly. The poweroff-command works without problem too.
Here is the command i use:
Code:
I installed Mythbuntu 9.04 about 9 months to a year ago and (for the most part) I haven't had any problems with mythwelcome, automatic shutdown or the system clock. The "for the most part" relates to the fact that the clock on mythbuntu has always been 4 minutes fast. Then, just last week, the system started acting up - for some reason the system clock changed to 8-10 minutes fast (6 minutes faster than it was previously). To fix this problem, I have tried manually setting the "time and date" setting, and I have also tried setting the "time and date" setting to sync with an internet server. Lastly, I tried changing the system time through the motherboard bios. In each situation, mythwelcome would initially start up with the correct time. Then, several seconds later, the time shown in mythwelcome would change to being 4 minutes fast (as I described above). The time would also be 4 minutes fast when I enter the frontend.
I was willing to live with this, but the weird part is that when I start the system now (assuming I don't have any programs scheduled to record), mythwelcome boots up fine and I see the indication that "MythTV is idel and will shutdown in XXX seconds". Then, it flashes to "MythTV is idle" - like it used to; except now, it doesn't flash back to the countdown for shutting down mythtv. One time when I started the system when I was adjusting the time as mentioned above, I noticed that mythwelcome went to the "MythTV is idle" around the same time it changed the clock to 4 minutes fast - I think there is definitely a correlation here.
I checked out all the settings and nothing else has been changed that would otherwise affect MythTV from shutting itself down. The other interesting part is that I can get the shutdown countdown back if I go to "Utilities / Setup", "Setup", and "Mythbuntu". In the popup screen I choose "MythTV Configuration" and select "Launch MythTV Setup". I get a popup box that says that the mythbackend must be closed (as expected). Then I immediately exit mythtv-setup and the system runs "mythfilldatabase". I exit the Mythbuntu Control Centre and exit the frontend. When I get back to mythwelcome, the shutdown countdown comes back.
I had a sata drive go down on my software raid array a couple days ago..After replacing the defective drive, I rebuilt it using fdisk to set partitions and mdadm to add the drive back into the raid array.After getting md2 to mount to /mnt I copied the /mnt/etc/fstab and /mnt/etc/mdadm.conf to the /etc directory and rebooted..When I boot, my /dev/md2 partition is not mounting to / It is not loading all of the services at boot time it should.. the size of /dev/md2 on / is even wrong.. it should be about 1.3TBwhen I manually mount /dev/md2 to /mnt I can access all of my data, through /mnt/var/www/vhosts and so on.. I am at a loss, why is the machine booting to this craziness?All of my data, that I know of can be accessed when md2 is mounted to /mnt[root@ESS000272 etc]# cat mdadm.conf
# mdadm.conf written out by anaconda
DEVICE partitions
MAILADDR root
[code]....
Is there something that blocks cron from running a shutdown command? I'm doing a daily bounce to break an attack (I have thread about that in security forum), but I always end up doing it manually. The cron log shows it being fired off at the right time...but the server never bounces. I thought maybe I just missed it, but there is nothing in messages that shows the server restarting (unlike when i do it manually, you see the start-up logging).
View 2 Replies View RelatedI have a Windows 2003 server that runs a Win32 time server which synchronizes with off site time sources. I have a CentOS 5.4 server which I just configured and installed NTP on. For some reason, I keep getting time discrepancies even after the server is (apparently) synching with my local NTP server on the Windows box.
Hwclock is set to UTC true/etc/localtime is properly symlinked to appropriate /usr/share/zoneinfo fileNTPD is setup as a service which loads on startupNTP.conf is configured to only retrieve from my local Windows 2003 time serverntpq -p seems to verify that the system is indeed synching up properlyThe problem is, whenever I run the 'date' command it is displaying my system time in (presumably) UTC. That is, even though my the CentOS box appears to be synching up to the local time, it's not translating it into my proper time zone. Consequently, the date is always at -6 hours from the actual local time. It was my understanding that the hwclock is fine to remain at UTC as ntpd should be synching with my local Windows 2003 time server periodically and updating it, and the system time should be getting translated to my localtime.
what I do, after rebooting the box the hwclock and system clock display the improper time.Maybe I just have a fundamental misunderstanding of how this is supposed to operate.Update: I'm not sure why, but after I commented out the other servers and added a fudge declaration for my internal server and rebooted, everything is working as it should and the time is correct.I'm still not really sure if it was adding the "fudge <hostname> stratum 2" declaration that corrected things, or commenting out the additional hosts, so I'll leave this open if anyone cares to comment or contribute.
I am about to put a server in a data center for the first time.I have got Wake on Lan/Network working on the server, however I have noticed that if the server is shutdown from the front button, it is unabled to be awoken via WOL.Is there a centos solution to this, or is this a BIOS issue, or something else? The server is a Super Micro X7SBi
View 3 Replies View Relatedi am trying to add a script on rc6.d using chkconfig but it doesn't work. I am missing something but i dunno what. I try with a test script /etc/init.d/test cat test
#
# test test
#
# Author: Maurizio Marini
#
# chkconfig: 2345 98 02
# description: this is a test
[Code]...
I have a server Hp proliant DL160 G6 with CentOS 5.4 . When I do shutdown -h now it doesn't poweroff.
I try differents options for acpi in menu.lst file. acpi=force, acpi=noacpi,acpi=off,acpi=ht but there's the same problem.
This the stdout when I do shutdown:
Halting system...
md: stopping all md devices.
Completed flushing cache on controller 0
ACPI: PCI interrupt for device 0000:05:00.1 disabled
xenbr0: port 2(peth0) entering disabled state
ACPI: PCI interrupt for device 0000:05:00.1 disabled
Power down.
acpi_power_off called
I show you any specific information about my server:
Reboot works fine
I am running a server at home, and on rare occasion my server will shut down. Is there a logfile I can check to determine whether the server was shutdown due to a script on the computer, a power loss, or someone hitting the power button? I am not by any means a linux guru, but I know enough to get around.
View 9 Replies View RelatedI am running Centos 5.5 X86_64 and recently after updating my server, I am having problem loading gnome. When the server boots, and begins to bring up the login screen theme, I get an error that states "Could not recognize the image file format for /usr/share/gdm/themes/TreeFlower/background.png" I am able to login after clicking ok to this message, and using the "simplistic" login manager. But when the users desktop loads, there are several errors pertaining to "unsupported image format" and none of the icons are displaying correctly. They are just the default "curvy page" icon for an unassociated file type. Some of the icons do not even show up at all.
Another thing I noticed wierd is that when I try to view a png, nothing happens. When I try to open one using gimp, I get an "unsupported file type" error. When I tried to click on the "add/remove software" button I get prompted for root pass, but nothing happens. So, I tried launching pirut from CLI, and I received the following error:
Quote:
[root@server ~]# pirut
Traceback (most recent call last):
File "/usr/sbin/pirut", line 41, in ?
from pirut import *
[code]...
I haven't manually configured XWindows in a very long time, so I'm not very certain what I need to do anymore. Hopefully someone can provide some guidance. I just built up a new system that I'm trying to connect to a 47" LCD TV that provides a VGA connection. When the computer starts booting all of the text comes up just fine (1 or 2 characters on the left are chopped, but otherwise fine). When I tried to run the installer for CentOS5.5 I ran into a problem. The monitor(TV) wasn't getting a proper signal to display XWindows. In an effort to keep going, I reconnected the PC to an old monitor and did the install from there. That worked no problem. I ran all the latest updates hoping that maybe this was fixed in a patch. I then shutdown and reconnected to my TV. no luck. When it starts XWindows the screen doesn't display anything. I've tried fooling around with modifying the xorg.conf and adding an explicit "Monitor" section and set it to 640x480 with a VertRefresh of 60 (which is supposedly an acceptable format), but no luck. Can anyone provide any guidance on how to solve this problem. BTW I do know that the VGA connector on the TV works just fine because I can hook up my laptop (Windows XP) to it.
H/W Monitor: Olevia 747i (when nVidia on my laptop detects it, it is reported as 747-b11) Motherboard: Biostar MCP6PB M2+ Motherboard - Socket AM2+, �ATX, Audio, GeForce 6150 Graphics, SATA, RAID Graphics: Using the integrated GeForce 6150 chipset
I have just configure RAID 1 on my IBM X3400 Server in CENTOS 5 ..Partition information is md0 boot , md1 swap and md2 is root ....but after resyn when i run cat /proc/mdstat I realize that md0 and md1 is ok and present with [UU] status. BUT the md2 is showing on one [U_].. that means my root partition is not properly in RAID 1.. how can i make it active in both drive. Or i need to reinstall complete system again. Screen shot attached [URL]
View 2 Replies View RelatedI'm running V5.3 (newly installed) on an FJ E8020 laptop. The problem I have is when shutting down (*not* rebooting). NetworkManager fails to stop and after (during?) the postfix shutdown, the system seems to hang.I cannot access via another screen or remotely. I can't find any clues in the log files.
[Code]...