Apis Networks

Borel will be taken down on Saturday, October 18th at 12:00 AM EDT (-0400 GMT) for a planned RAM upgrade. We will be doubling Borel’s RAM to 8 GB in anticipation of an exciting, new Tomcat change. We expect the outage to last approximately 10 minutes. Our standby power supply will also be tested at this time.

If you are running a service on the server, then please be sure to create the necessary init scripts in /etc/rc3.d. Commands found in this directory will be executed upon start-up.

12:23 AM: Borel is up and running after going down at approximately 12:10 AM.  Memory is at 8 GB:

top - 00:22:17 up 1 min,  1 user,  load average: 3.50, 1.02, 0.35
Tasks: 253 total,   2 running, 251 sleeping,   0 stopped,   0 zombie
Cpu(s): 14.0% us,  1.5% sy,  0.0% ni, 60.0% id, 24.4% wa,  0.0% hi,  0.1% si
Mem:   8312116k total,  1218524k used,  7093592k free,    57600k buffers
Swap:  2104496k total,        0k used,  2104496k free,   361748k cached

All Basic and higher packages now have start-up and shutdown script support activated through scripts in /etc/rc3.d and /etc/rc6.d respectively.  Tiered thresholds are set with the number of PIDs that may start-up on your account in addition to the total time spent starting up all processes on an account.  Basic includes a 5 process limit and 15 second execution time.  Advanced includes 10 processes with 30 seconds, and Super tentatively includes 15 processes with a 60 second execution timeout.

Toss your start-up scripts in /etc/rc3.d and they will be executed in sequential order.  Optionally, if you would like any commands to be executed during shutdown, create the scripts in /etc/rc6.d.  Scripts should be executable from the command-line, i.e. /etc/rc3.d/myscript.sh should be capable of being run directly.  This requires execute privileges on the script.  chmod 755 /etc/rc3.d/myscript.sh will make the script executable from the command-line.  An example script is provided below:

#!/bin/sh
# Declare any necessary environment variables
ENV_VAR=FOO
# Optionally export variables to the process if you need them
export ENV_VAR
# Start the process.  This is one process, so we are permitted
# 4 additional PIDs per the Basic package limits
svnserve -d -r /home/user/REPO –listen-port=40010
# Start-up memcached for Rails
memcached -d -p 40011 -m 64