VPS isn't rebooting by itself when it goes down. Anyone has any program/script that monitors heartbeat of the server? Like when it goes down, the program will automatically reboots the system. I know there's such a script out there but I forgot what it called.
View 2 RepliesI have Plesk 8 installed I would like to create Scheduled Task as root to reboot the server in every 8 hours.
View 7 Replies View RelatedI have a dedicated server, on Debian Etch.
When I type a command with putty, the connection is closed immediately. I tried shutdown-r now and reboot, halt, do nothing to console closes and nothing happens.
After a hundred connection, I can use ls, su and kill.
I think it's the fact that the partition is corrupted. I can not Hardware reboot the server because CTN1 is "out of business".
Do you know another way to restart the server
how to configure a periodic reboot, for example, each 4h the server will be reboot automatic.
i think i do configure a cron, but i can't find anything for periodic rebooting on freebsd.
this is a temporary solution for a issue of php.
I had to reboot my server and about 20 minutes later I tried to access the web site but the page was not found... I am able to login to SSH. However, I am not familiar with *nix or the workings of CPanel... What should I do to get the sites back online?
View 9 Replies View RelatedAfter a graceful reboot I am having problems with a few things.
First cpsrvd and lfd failed to start, but I fixed it doing this:
rm -f /usr/local/cpanel/cpanel
rm -f /scripts/installgd
rm -f /scripts/cleanmd5
rm -f /scripts/upcp
But next to all the drives it says "No DMA! (Click to Enable)", I click that and it says things:
Quote:
EIDE Hard Drive Optimizations Enabled
/dev/hdc:
setting 32-bit IO_support flag to 1
IO_support = 1 (32-bit)
But after going back to Service Status it still says that.
So I tried to enable it through a command by typing:
sudo hparm -d1 /dev/hdc5
And get this error:
Quote:
/dev/hdc5:
setting using_dma to 1 (on)
HDIO_SET_DMA failed: Invalid argument
using_dma = 0 (off)
so my server dies every day and requires human intervention to fully restart all service to have my site work properly. i suspect sigterm issues as it fails to restart all service as website is still down so i always have to reboot it.
Tried recompile apache with no success
[Tue Mar 18 06:51:27 2008] [error] [client 203.160.1.39] request failed: erroneous characters after protocol string: If-Modified-Since: Wed, 21 Nov 2007 06:16:52 GMT
[Tue Mar 18 10:03:18 2008] [error] Bad pid (7465) in scoreboard slot 16
[Tue Mar 18 10:03:18 2008] [error] Bad pid (27848) in scoreboard slot 17
[Tue Mar 18 10:03:18 2008] [error] Bad pid (27434) in scoreboard slot 18
[Tue Mar 18 10:03:18 2008] [error] Bad pid (30782) in scoreboard slot 19
[Tue Mar 18 10:03:18 2008] [error] Bad pid (7465) in scoreboard slot 16
[Tue Mar 18 10:03:18 2008] [error] Bad pid (27848) in scoreboard slot 17
[Tue Mar 18 10:03:18 2008] [error] Bad pid (27434) in scoreboard slot 18
[Tue Mar 18 10:03:18 2008] [error] Bad pid (30782) in scoreboard slot 19
[Tue Mar 18 10:03:18 2008] [error] Bad pid (7465) in scoreboard slot 16
[Tue Mar 18 10:03:18 2008] [error] Bad pid (27848) in scoreboard slot 17
[Tue Mar 18 10:03:18 2008] [error] Bad pid (27434) in scoreboard slot 18
[Tue Mar 18 10:03:18 2008] [error] Bad pid (30782) in scoreboard slot 19
[Tue Mar 18 10:03:18 2008] [notice] caught SIGTERM, shutting down
[Tue Mar 18 10:03:20 2008] [notice] mod_security/1.9.5 configured - Apache/1.3.39 (Unix) PHP/5.2.5
[Tue Mar 18 10:03:20 2008] [notice] Any You Like mod_ssl/2.8.30 OpenSSL/0.9.8g mod_perl/1.29 FrontPage/5.0.2.2510 configured -- resuming normal operations
[Tue Mar 18 10:03:20 2008] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Tue Mar 18 10:03:20 2008] [notice] Accept mutex: sysvsem (Default: sysvsem)
I'm finding that my server doesn't like to reboot gracefully. Either selecting "graceful server reboot" in WHM or actually typing "reboot" in SSH, which then tells me the server is shutting down. My server is then incommunicato indefinitely until I actually do a hard reset remotely.
Is this common? Is there some way to find out why this is happening?
I'm worried a server is dead, and I haven't made any backups of the database
Server went down last night, submitted a reboot request and now the server is not responding to SSH.
It does respond to ping, so I'm assuming Linux might have booted up OK
Has anyone experience with this type of issue?
What's an acceptable time for rebooting a machine?
I send an email to midphase to get my machine rebooted and I wait nearly half an hour. Even put 911.
Pacifirack would have got it done in under 5 minutes
reboot my vps every 30 min automatically in my hypervm control panel. How can i do that?
View 12 Replies View Relatedfor testing reboots? Basically, the goal is to avoid having a reboot fail leading to support or reinstall costs.
Right now, I'm using qemu -snapshot /dev/hda, but that obviously has limitations.
way to make remote reboot/start/shutdown?
it could be cool to be able to do it from a web interface in stead off by hand
So I was trying to run a backup process in Plesk 8.1 and the whole panel froze up on me (it's happened numerous times before).
Anyway, since the panel was all frozen up I just went into SSH and did a simple "reboot" (also, as done before many times). Only problem is, this time after I did the reboot the server never actually came back online... it seems to be locked up or something, I have no idea what.
I called my host and they are looking into it but they have no idea what's going on either and it's taking them forever to figure it out all the meanwhile my sites are down.... this isn't good.
Does anyone have any suggestions or advice as to why this could be occuring?
I know there are tons out there, but what's the best bang for your buck?
What's a good remote reboot that allows client to do it themselves that doesn't hurt your pockets too much?
Just a general question regarding the frequency which you all reboot your linux servers.
Mine has been up for 178 days, and is running sweet as a nut (touch wood). I was just wondering if it's worth giving it a reboot anytime soon, or if not, how long to give it before rebooting?
I'm running CentOS 4.4 32 bit.
At the moment every time I reboot my server I have to execute:
# iptables --flush
# iptables --zero
just to be able to access the server. (Though it does allow SSH to access before executing those).
And I figured out that I must do something to /etc/sysconfig/iptables to permanently be able to access the server without those commands after reboot. Right?
Below is the file's contents:
# Firewall configuration written by system-config-securitylevel
# Manual customization of this file is not recommended.
*filter
:INPUT ACCEPT [0:0]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
:RH-Firewall-1-INPUT - [0:0]
-A INPUT -j RH-Firewall-1-INPUT
-A FORWARD -j RH-Firewall-1-INPUT
-A RH-Firewall-1-INPUT -i lo -j ACCEPT
-A RH-Firewall-1-INPUT -p icmp --icmp-type any -j ACCEPT
-A RH-Firewall-1-INPUT -p 50 -j ACCEPT
-A RH-Firewall-1-INPUT -p 51 -j ACCEPT
-A RH-Firewall-1-INPUT -p udp --dport 5353 -d 224.0.0.251 -j ACCEPT
-A RH-Firewall-1-INPUT -p udp -m udp --dport 631 -j ACCEPT
-A RH-Firewall-1-INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT
-A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 22 -j ACCEPT
-A RH-Firewall-1-INPUT -j REJECT --reject-with icmp-host-prohibited COMMIT
What do I need to do?
We changed our SSH port (for the slight added security that this offers) and updated our CSF config with the new port so that we can accept connections on this port.
We restarted CSF and we could connect successfully on the new port. When the server is rebooted connections are refused on the port until we *RESTART* CSF then it's all good again.
I would think being that we opened the port in CSF's config that on reboot the port would be opened back up but this is not happening and any time the server is rebooted we have to restart the firewall.
Does anybody have any suggestions on how to "fix" this or at least make it so we don't have to manually restart the firewall?
Does anyone have any recommendations for colocation providers in the LA area or recommendations for a PDU that has remote reboot capabilities (small budget, nonprofit organization)? We have a total of 9 servers.
View 9 Replies View Relatedmy VPS didn't come online after a reboot(reboot via SSH). After that I tried to reboot it via HyperVM but I got an error like Couldn't stop VPS.
I'm wondering, is one of those files chmoded to 700 and chowned to root:root a problem?
chmod 700 /usr/bin/perl
chmod 700 /usr/bin/python
chmod 700 /bin/rm
chmod 700 /bin/uname
chmod 700 /bin/top
chmod 700 /bin/chown
chmod 700 /usr/bin/id
chmod 700 /usr/bin/as
chmod 700 /usr/bin/finger
chmod 700 /usr/bin/w
chmod 700 /usr/bin/locate
chmod 700 /usr/bin/whereis
chmod 700 /sbin/ifconfig
chmod 700 /usr/bin/pico
chmod 700 /usr/bin/which
chmod 700 /usr/bin/make
chmod 700 /bin/rpm
chmod 700 /bin/ls
chmod 700 /usr/bin/wget
chmod 700 /bin/cat
chmod 700 /usr/bin/nano
chmod 700 /usr/bin/vim
chmod 700 /bin/vi
chmod 700 /bin/grep
chmod 700 /usr/bin/find
chmod 700 /bin/ln
I ordered a leaseweb express server 4 box with windows server 2003 and have been running it, installed some software etc which worked out fine.
Anyways, I wanted to disable tcp/ip filtering which I did and afterwards it prompted me that I would have to reboot the server for the changes to take place, I clicked ok and it rebooted. Now I just can't connect with remote desktop, I tried everything.
I'm guessing it either shut down or didn't reboot properly? I tried sending an email to leaseweb support 2 days ago but still no shadow of any reply..
It says that I can reboot the server using the SSC but when I log in there, I can't really find any reboot option.
Any advice on setup of remote hard reboot/reset on colocated server.
View 11 Replies View RelatedI've got an old passivley cooled Pentium II box which I am turning into a silent File/Backup server for our LAN at home. Naturally for stability and performance on old hardware, I am running Linux.
The problem I have is that when you reboot the machine, it ends all processes, unmounts etc as usual, but after that the screen just blacks out and it doesn't go anywhere. I have to physically reboot the machine.
During startup theres a message saying BIOS is earlier than 1999, you should set ACPI=FORCE in Grub. I added this and also tried the noacpi and noacip options to no avail.
Windows ran on this fine before so I don't see why Linux would have an issue.
I have a Centos 5.2 box with Cpanel/WHM. A couple days ago it rebooted.
I checked /var/log/messages and I can see where it rebooted, but I can't find anything that indicates why.
I'm trying to figure out if this is a hardware issue or software issue/crash.
I do have Nagios istalled, and it seems it saved some data right before the server rebooted. Not sure if this is a simple coincidence.
Dec 4 11:53:35 miles nagios: Auto-save of retention data completed successfully.
Dec 4 11:56:14 miles syslogd 1.4.1: restart.
Dec 4 11:56:14 miles kernel: klogd 1.4.1, log source = /proc/kmsg started.
Dec 4 11:56:14 miles kernel: Linux version 2.6.18-92.1.17.el5PAE (mockbuild@builder16.centos.org) (gcc version 4.1.2 20071124 (Red Hat 4.1.2-42)) #1 SMP Tue Nov 4 14:17:52 EST 2008
Dec 4 11:56:14 miles kernel: BIOS-provided physical RAM map:
Dec 4 11:56:14 miles kernel: BIOS-e820: 0000000000000000 - 000000000009f000 (usable)
how to trouble shoot this?
problem on one server with debian, the last month it have a 100% f uptime, but since yesterday automaticly it reboot every 1 hour exactly!
this is a game server , dont have service like httpd , mysql dns , nothing! , I uninstall cron jobs thinking that will solve the problem, but no .....
I install firewall, run rkhunter and chkrootkit, check whell gruop and nothing
logs:
Jan 17 05:20:00 debian -- MARK --
Jan 17 05:40:00 debian -- MARK --
Jan 17 06:00:18 debian syslogd 1.4.1#18: restart.
Jan 17 06:00:18 debian kernel: klogd 1.4.1#18, log source = /proc/kmsg started.
Jan 17 06:00:18 debian kernel: Bootdata ok (command line is root=/dev/sda1 ro )
I change root password and ssh port but nothing... I think that could be a issue on debian or some exploit cause it, this was happend Suddenly one day to another it is very Strange....
somebody know about this?
SERVER:
debian:~# uname -a
Linux debian 2.6.18-5-amd64
CORE 2 QUAD - 2GB ram - debian 64 bits
I have an dedicated server 2 x Xeon CPU 3.20GHz (2GB RAM), now 30 minutes ago my admin tryed to make a benchmark test on it and after a period the server was not responding ( SSH or http.. ftp ) we asked DN to reboot the server. After the reboot in Service Status page (WHM) there ware many services down and the load was ~ 45.00 (4 cpus) .. after aprox. 5 - 10 minutes the load has droped:
Server Load 2.61 (4 cpus)
is it normal to have such a higher load 45.00 (4 cpus) after an reboot ? The memory used was 32%.
I recently created a /tmp partition to get it secured to avoid file execution from that dir.
So, created a partition for tmp:
cd /dev/; dd if=/dev/zero of=tmpMnt bs=1024 count=1000000
mkfs.ext3 /dev/tmpMnt
Then mounted the partition
mount -o loop,noexec,nosuid,rw /dev/tmpMnt /tmp
Configured /etc/fstab so the partition is mounted after every reboot:
[root@server.myhost.com:~]cat /etc/fstab
LABEL=/ / ext3 defaults 1 1
LABEL=/boot /boot ext3 defaults 1 2
tmpfs /dev/shm tmpfs defaults 0 0
devpts /dev/pts devpts gid=5,mode=620 0 0
sysfs /sys sysfs defaults 0 0
proc /proc proc defaults 0 0
LABEL=SWAP-sda2 swap swap defaults 0 0
LABEL=/tmp /dev/tmpMnt ext3 loop,noexec,nosuid,rw 0 0
[root@server.myhost.com:~]
[root@server.myhost.com:~]df -ah
Filesystem Size Used Avail Use% Mounted on
/dev/sda3 224G 3.1G 210G 2% /
proc 0 0 0 - /proc
sysfs 0 0 0 - /sys
devpts 0 0 0 - /dev/pts
/dev/sda1 99M 21M 73M 23% /boot
tmpfs 1014M 0 1014M 0% /dev/shm
none 0 0 0 - /proc/sys/fs/binfmt_misc
/dev/tmpMnt 962M 18M 896M 2% /tmp
[root@server.myhost.com:~]ls -alh /dev/tmpMnt
-rw-r--r-- 1 root root 977M Dec 12 18:00 /dev/tmpMnt
[root@server.myhost.com:~]s
Now, after rebooting the system the partition is no longer there?? (and of course, not mounted /tmp due to this)
[root@server.myhost.com:~]ls -alh /dev/tmpMnt
ls: /dev/tmpMnt: No such file or directory
[root@server.myhost.com:~]
This was done under a plain RHEL 5.2 box.
Is it possible to use a APC remote reboot power strip for a server in a blade?
Like for example, say there are 16 servers in a blade, can you remote reboot them individually?
Because blade servers have only like 3-4 redundant power supplies and I am assuming all the 16 servers are powered by the onboard power supplies in the blade enclosure. So...if thats the case, how is it possible to reboot each individual server?
I just purchased my first Opteron 248 (normally use 170's). The reboot time is about 20 minutes. The 170's reboot in under 5 minutes.
I watched it reboot through IPMI and it says:
PXE-M0F No DHCP or ProxyDHCP offers were received.
PXE-M0F: Exiting NVIDIA Boot Agent
Then it retries to connect to DHCP over and over for about 15 minutes before finally starting the normal boot process.
Is this normal? The data center is telling me it is, but I find it hard to believe anything would take that long to boot on a new system.
I was suggested to post my q in colo forum (it was posted in hosting lounge).
View 14 Replies View Related