Remote Reboot
May 6, 2007way 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
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
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?
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 RelatedAny advice on setup of remote hard reboot/reset on colocated server.
View 11 Replies View RelatedIs 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 was suggested to post my q in colo forum (it was posted in hosting lounge).
View 14 Replies View RelatedI want to setup KVM over IP/remote reboot for my server. Do i need datacenter support or just need to install the hardware?
View 14 Replies View RelatedIs there a way to remotely use APC remote reboot's features rather than logging into APC control panel and doing it?
Like you know how softlayer and ev1 servers do.
Like write a small php script to access the power strip and execute the orders. May be an API or something.
I'm here to ask a few questions, and hoping any burst resellers/customers can possibly answer them for me.
Q1.) How long do additional Ip's take normally?
Q2.) How long do remote reboot details take normally?
Q3.) Do Staff ever ignore your tickets?
I've been waiting for both Remote/Ip's since Saturday ( was told Friday they would be sent within 24hours) and tickets being ignored by the looks
What is a good value IP remote rebooter? Looking for one I can place in a cabinet, hopefully to control 12-16 servers.
It needs to allow me to create users and assign them to manage X ports on. If it has KVM IP it would be a plus.
I have read all the recomendations about the APC 793* series of PDU's. I have bought 2 but I cannot figure out how they do the powering off/on of ports. I did see some reference to mib's but haven't been able to figure out how to use them.
View 8 Replies View Relatedon remote reboot switches that will allow us to cycle power on two plugs at once for use with servers that have redundant power supplies.
Brands and models welcome. We should also be able to access the units remotely to cycle power.
Any experiences with Supermicro IPMI Card - (AOC-IPMI20-E)? I need basic Power managment like APC reboot ports.
Since its very likely that we will get some Supermicro servers, I thought why not add the IPMI card.
I 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
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 Replies View Relatedhow 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.
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?
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?
how to transfer file(s) from remote server to remote ftp using ssh(on remote server)?
View 3 Replies View RelatedI'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?
my 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