Hi Julio,

Can you post a copy of your script to the mailing list? It's hard to diagnose what may be happening without seeing what you are doing to shut down.

Thanks, Robert

Robert Hodges, CTO, Continuent, Inc.
Email:  [EMAIL PROTECTED]
Mobile:  +1-510-501-3728  Skype:  hodgesrm


On Jul 30, 2007, at 12:06 PM, Julio Leyva wrote:

Hi all

We have migrated from sequoia 2.10 to 2.10.8

We have a script that stops and starts sequoia , the script was working ok until we installed sequoia 2.10.8

Apparently the script stops sequoia but we can see the controller still running




ps -ef | grep controller



root 22660 22659 1 14:46 pts/12 00:00:09 /usr/lib64/jvm/java/ bin/java -classpath :/opt/sequoia/lib/octopus/Octopus.jar:/opt/ sequoia/lib/octopus/OctopusGenerator.jar:/opt/sequoia/lib/octopus/ csvjdbc.jar:/opt/sequoia/lib/sequoia-controller.jar:/opt/sequoia/ lib/sequoia-backend.jar:/opt/sequoia/lib/sequoia-backupers.jar:/opt/ sequoia/lib/sequoia-cache.jar:/opt/sequoia/lib/sequoia-commons.jar:/ opt/sequoia/lib/sequoia-jmx.jar:/opt/sequoia/lib/sequoia-sql.jar:/ opt/sequoia/lib/octopus:/opt/sequoia/drivers:/opt/sequoia/lib/ hedera-commons.jar:/opt/sequoia/lib/hedera-jgroups.jar:/opt/sequoia/ lib/hedera-appia.jar:/opt/sequoia/lib/appia.jar:/opt/sequoia/lib/ jgroups-core.jar:/opt/sequoia/lib/concurrent.jar:/opt/sequoia/lib/ commons-logging.jar:/opt/sequoia/lib/dom4j-1.6.1.jar:/opt/sequoia/ lib/jaxen-1.1-beta-8.jar:/opt/sequoia/lib/log4j.jar:/opt/sequoia/ lib/activation.jar:/opt/sequoia/lib/mail.jar:/opt/sequoia/lib/ commons-cli.jar:/opt/sequoia/lib/jmx/mx4j.jar:/opt/sequoia/lib/jmx/ mx4j-remote.jar:/opt/sequoia/lib/jmx/mx4j-tools.jar:/opt/sequoia/ xml:/opt/sequoia/lib/crimson.jar:/opt/sequoia/lib/xml-apis.jar:/opt/ sequoia/config/controller:/opt/sequoia/config/virtualdatabase:/opt/ sequoia/config/: -Dsequoia.home=/opt/sequoia -Dsequoia.log=/opt/ sequoia/log -Djava.security.policy=/opt/sequoia/config/java.policy - Xms1024m -Xmx1024m -Djava.net.preferIPv4Stack=true org.continuent.sequoia.controller.core.Controller -f /opt/sequoia/ config/controller/abrazo.xml

So every time we need to kill the process to start sequoia again.

Output in the log files

2007-07-30 14:46:43,789 INFO Controller 172.20.200.15:25322 ready, listening to requests ... 2007-07-30 14:47:11,041 INFO Shutting down virtual database abrazo in force mode : immediate without consistency 2007-07-30 14:47:11,042 INFO Database backend abrazo.abrazo1 is now in state disabled 2007-07-30 14:47:11,435 INFO Database backend abrazo.abrazo2 is now in state disabled 2007-07-30 14:47:11,607 INFO The virtual database abrazo has been successfully shut down 2007-07-30 14:47:11,619 INFO Shutting down controller 172.20.200.15:25322 2007-07-30 14:47:12,095 INFO Shutdown of controller 172.20.200.15:25322 completed


BTW this version has different log files (cluster.log and full_cluster.log) , Do I need to change something to migrate from 2.10 to 2.10.8? I assume it should be transparent...



Any suggestions?

Thanks in advance


JulioC.








_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia

_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia

Reply via email to