3. Shore Side Data System (600031 and 900823) : SQL 2008 Upgrade and Move to Dione This page last changed on Jul 15, 2011 by kgomes. In July of 2011, the database server that SSDS was running against was a an older version of SQL Server (2000) and SSDS was filling up the disk on Solstice. For this reason, it was decided to create a whole new server in the DMZ running SQL 2008 and to move the SSDS databases to that machine. Here are the steps taken during that work: 7:41 AM: SSH'd into pismo as kgomes 7:44 AM: edited the crontab using 'crontab -e' and commented out the entries that ran the data checker and the graphing routines. 7:45 AM: Verified the updatebot was runnning using 'ps -ef'
       root      4203     1  0 Jul07 ?        00:00:15 /usr/java/jdk1.6.0_06/bin/java -Duser.timezone=UTC -Xms512m -Xmx1024m -classpath /opt/ssds/updatebot/ssds-updatebot-client-new-ssds.jar moos.ssds.clients.updateBot.UpdateBotRunner
7. 7:45 AM: stopped the updatebot service using 'sudo /sbin/service updatebot stop' 7:49 AM: ssh'd into new-ssds.mbari.org as kgomes 7:50 AM: in another windows, ssh'd into bob.shore.mbari.org as kgomes 7:50 AM: verified JBoss was running on bob, using 'ps -aux' and getting:
       root   11926   0.4 -4.8  1325572 100336  ??  S    27Jun11 1313:48.61 /usr/bin/java -server -Xmx1024M -Djboss.server.temp.dir=/var/tmp/jbosstmpdata11922 -classpath /Library/JBoss/3.2/bin/run.jar org.jboss.Main -c deploy-standalone
8. 7:50 AM: on bob.shore.mbari.org, shut off the JBoss instance using:
       sudo serveradmin stop appserver
9. 7:54 AM: could not shutdown JBoss on new-ssds.mbari.org using 'sudo /sbin/service jboss stop' and figured out that I had to use:
       cd /opt/jboss/bin
       ./shutdown.sh -S -s 134.89.2.25
10. 8:16 AM: bob.shore.mbari.org had some oddities with iagadmin account, so I rebooted bob remotely using
        sudo shutdown -r now
and then stopped the jboss service again. I then copied all the pertinent files from bob.shore.mbari.org, new-ssds and pismo to my local machine so I could edit them locally. While I don't think this is really an issue, all the editing of files that I do here is done with vi from the command line due to the fact that I am running on OS X and I don't want any editing software doing anything funny. I decided that in order to keep my changes consistent with what was in the source code repo, I used the new-ssds.mbari.org build I had on my laptop and edited the new-ssds.mbari.org configuration properties and just ran the build again.

Document generated by Confluence on Feb 04, 2026 08:56