could be serendipity...

Feel free to use this script as you see fit.  It is by no means perfect, if you have some suggestions, I’d love to hear them.

Hybris does not include a Linux System V init script, so we had to write our own. Here’s the first ‘stable’ version of the script. This can be placed in /etc/init.d/hybris, most likely renamed to hybris_<env>. Ex. hybris_dev

It can be installed to run when the system reboots like this:

$ sudo chkconfig --add hybris

This will install the script by default at runlevels 3, 4 and 5.

#!/bin/bash
#
# rc file for starting hybris
#
# On most distributions, this file may be called:
# /etc/rc.d/init.d/hybris or /etc/init.d/hybris
#
# If you are running multiple Hybris instances
# You may want to give a more reasoneble name
# Such as  /etc/init.d/hybris_instance
#
# For Redhat-ish systems
#
# chkconfig: 345 99 99
# processname: java
# config: $HYBRIS_HOME/config/local.properties
# description: starts hybris server

# Set the environment level for hybris, this determines directory structure for systems with multiple installations.
# Example settings: {dev|qa|uat|prod}
ENV="dev"

# Make sure the server starts as a non-root user, set that here.
RUNAS="hybris"

# Set the base path to your hybris installation.
HYBRIS_HOME="/common/apps/hybris.${ENV}/hybris"

# Set the path to the Tomcat 6 startup script included with Hybris.
SERVSCRIPT="${HYBRIS_HOME}/bin/platform/hybrisserver.sh"

HYBRUNNING=`ps auxwww | grep "hybris.${ENV}" | grep "jmxremote" | wc -l`

# Source function library.
. /etc/init.d/functions

# Make sure that this script is being run as the root user.
if (( `/usr/bin/id -u` != 0 )); then
{ echo "Sorry, this init script must be run as root.  Exiting...";
exit; }
fi


# Start the Hybris server.
start() {
        echo -n "Attempting to start up hybris_${ENV}: "
        echo
        sudo -u ${RUNAS} ${SERVSCRIPT} start
        touch /var/lock/subsys/hybris_${ENV}
        return 0
}

#Stop the Hybris server.
stop() {
        echo -n "Attempting to shut down hybris_${ENV}: "
        echo
        sudo -u ${RUNAS} ${SERVSCRIPT} stop
        rm -f /var/lock/subsys/hybris_${ENV}
        return 0
}

case "$1" in
    start)
        if [ ${HYBRUNNING} -eq 0 ]; then
                start
        else
                echo "Hybris appears to be running, and will not be started."
                echo "There are ${HYBRUNNING} related processes detected."
                echo "Try restarting the server, with '/etc/init.d/hybris restart'."
                exit 1
        fi
        ;;
    stop)
        if [ ${HYBRUNNING} -ne 0 ]; then
                stop
        else
                echo "Hybris does not appear to be running."
                echo "Total instances found running is ${HYBRUNNING}."
                exit 1
        fi
        ;;
    status)
        if [ ${HYBRUNNING} -ne 0 ]; then
                echo "Hybris appears to be running."
        else
                echo "Hybris is stopped."
        fi
        ;;
    restart)
        if [ ${HYBRUNNING} -ne 0 ]; then
                COUNTER=1
                while [ ${HYBRUNNING} -ne 0 ]; do
                        stop
                        echo "Sleeping for 10 seconds."
                        sleep 10
                        echo "Tried ${COUNTER} time(s)."
                        HYBRUNNING=`ps auxwww | grep "hybris.${ENV}" | grep "jmxremote" | wc -l`
                        COUNTER+=1
                done
                start
        else
                echo "Hybris appears to be stopped, please use '/etc/init.d/hybris start' to bring up the server."
                exit 1
        fi
        ;;
    reload)
        echo
        echo "To be implemented..."
        ;;
    *)
        echo "Usage: hybris {start|stop|status|reload|restart}"
        exit 1
        ;;
esac
exit $?

I’m performing a dd on all my drives to clear them out for an attempt at using my motherboard’s fakeRaid (AMD). I have 4x500 GB Sata II Disks.  The oldest disk was manufactured in 2008, the rest purchased at random, all have a 3 Gbps link and are on ‘separate’ channels.

Nothing fancy, just a standard one pass drive fill with zeros, 1M at a time.

Ex. dd if=/dev/zero of=/dev/sdX bs=1M

sda - Hitachi HDP72505 (The noisy one)
sdb - Western Digital (Caviar Green) WD5000AADS (The eco conscious one)
sdc - Seagate ST3500641NS (The old one)
sdd - Western Digital (Caviar Blue) WD5000AAKS (The new one)

What’s interesting is just how large of a performance gap there is between the drives, with the Hitachi and WD Caviar Green drives having a similar write speed (but lower utilization on the Hitachi), the Seagate is clearly at the bottom of the pack, and the WD Caviar Blue leading.  S.M.A.R.T. says all the drives are healthy.

Device:         rrqm/s   wrqm/s     r/s     w/s    rMB/s    wMB/s avgrq-sz avgqu-sz   await  svctm  %util
sda               0.00 176996.00    0.00 1140.50     0.00    83.90   150.66    26.98   23.29   0.67  76.80
sdb               0.00 19211.50    0.00  164.50     0.00    82.05  1021.54    54.74  344.27   6.09 100.15
sdc               0.00 14354.00    0.00  114.00     0.00    55.78  1002.00    41.93  374.39   8.79 100.15
sdd               0.00 28432.50    0.00  227.50     0.00   105.75   951.96    40.46  170.22   4.40 100.20

I also noticed that CPU use was the highest on the wipe of the Hitachi (21%), next highest on the Seagate (9%) then relatively low on both of the WD drives (5-6%).

This is just another example of why you should try to use all the same drives in a RAID.  If this were a server of course I’d be heading in that direction, but this is just my desktop.

This isn’t a perfect test by any means, but I thought I’d share…

Update:

sda - 500106780160 bytes (500 GB) copied, 6277.51 s, 79.7 MB/s
sdb - 500107862016 bytes (500 GB) copied, 6815.34 s, 73.4 MB/s
sdc - 500107862016 bytes (500 GB) copied, 10403.3 s, 48.1 MB/s  :(
sdd - 500107862016 bytes (500 GB) copied, 5148.57 s, 97.1 MB/s

clientsfromhell:

Client: ”When this gets printed, what sort of colors get mixed together?”

Me: “Well, anything that gets printed is basically a combination of black, yellow, cyan, and magenta ink or toner…”

Client: “That’s unacceptable! I’m printing these for boys, not girls. Magenta is a girls color. Take the magenta out of your printers and replace it with red. Red is much manlier.”