Hi Jim, That did it, thanks. I was able to run everything for single user in the ducc-install application. I have a couple notes that might help with the documentation. And if you like me to submit notes while I'm working with it, I can help with that also.
1. Set ducc.head in resource/ducc.properties 1a. Make ducc.head doesn't have trailing spaces (e.g. "jameson ").. Whatever calls it down the line doesn't strip() them out. the sample returned a "Cannot initialize: java.lang.IllegalArgumentException: Invalid uri 'http://jameson :19988/or': Invalid authority" Error I noted these rules in multi - user, but had to apply to my single setup. 2. chown root:ducc ducc_runtime/admin/ducc_ling 3. chmod 4750 ducc_runtime/admin/ducc_ling ( the ./start_ducc script says to set to 0750, then setuid , but I think that it also wants setgid) 4. ssh-copy-id [email protected] Thank you! I'm excited to begin working with this system. -Neal From: Jim Challenger <[email protected]> To: [email protected], Date: 10/23/2013 11:07 AM Subject: Re: DUCC install and ActiveMQ Start Neal, The ActiveMQ that is shipped with DUCC is configured to take various parameters from ducc.properties. To do that, I've set up start_ducc to read ducc.properties and issue the 'activemq start' command for you after setting env and java -D parameters used by AMQ.. So to start just the broker, try this: start_ducc -c broker However it looks like the actual problem is that somehow you got <head-mode> into your ducc.properties. You should set this line: # ducc.head is the node where the main DUCC daemons run ducc.head = blah To specify the name of the node you want to run the ducc 'head'. E.g. if your head node is 'agent86.secret.com', you specify ducc.head = agent86.secret.com [ or perhaps in your case, ducc.head = jameson] Then a normal start_ducc or start_ducc -c broker to get just the broker, should work. Jim On Oct 23, 2013, at 1:28 PM, Neal R Lewis <[email protected]> wrote: > Hi All, > > I'm installing DUCC and am running into a problem starting activemq . I'm > following the steps outlined in the DUCC Install pdf: checkout the src, > run mvn install, and then run the post installation scripts for > verification. > > When I run ./check_ducc, the output says that activemq isn't running. > When I trying to start activemq via > "$HOME/ducc_runtime/activemq/bin/activemq start", It says that it will run > default, but doesn't seem to start. I'm posting the output for the steps > below, any guidance would be helpful. I'm not showing "start_ducc" since > the broker isn't running. > > > > [ducc@jameson admin]$ ./ducc_post_install > Python version: > 2.7.3 (default, Aug 9 2012, 17:23:57) > [GCC 4.7.1 20120720 (Red Hat 4.7.1-5)] > Ducc head is configured as <head-mode> > > Verified existence of default nodefile > /home/ducc/ducc_runtime/resources/ducc.nodes > > Verified existence of default JobDriver nodepool > /home/ducc/ducc_runtime/resources/jobdriver.nodes > > ActiveMQ is automanaged on node > tcp://<head-mode>:61616?wireFormat.maxInactivityDuration=0&jms.useCompression=true&closeAsync=false > JAVA: java version "1.7.0_45" > JAVA: OpenJDK Runtime Environment (fedora-2.4.3.0.fc18-x86_64 > u45-b15) > JAVA: OpenJDK 64-Bit Server VM (build 24.45-b08, mixed mode) > Java version: "1.7.0_45" > WARNING: DUCC is only tested under Java 1.6 > > WARNING > WARNING The default ssl pw of quackquack is configured. For > security, change the property > ducc.ws.port.ssl.pw to a secure password in > ducc.properties and rerun ducc_post_install. > WARNING > > None > keystore created. > > Web server keystore generated from ducc.properties > > DUCC book installed into webserver root > > cc -g ducc_ling.c -o ducc_ling > Initial ducc_ling is installed. See the installation guide for > multi-user setup. > > > [ducc@jameson ducc_runtime]$ ./activemq/bin/activemq start > INFO: Using default configuration > you can configure options in one of these file: > /etc/default/activemq /home/ducc/.activemqrc) > > INFO: Invoke the following command to create a configuration file > ./activemq/bin/activemq setup [ /etc/default/activemq | > /home/ducc/.activemqrc ] > > INFO: Using java '/usr/lib/jvm/java-1.7.0-openjdk.x86_64/bin/java' > INFO: Starting - inspect logfiles specified in logging.properties > and log4j.properties to get details > ;: line 2: > /home/ducc/ducc_runtime/activemq/data/activemq-jameson.pid: Permission > denied > INFO: pidfile created : > '/home/ducc/ducc_runtime/activemq/data/activemq-jameson.pid' (pid '32058') > > [ducc@jameson admin]$ ./check_ducc > 050 ducc_ling Version 0.8.10 compiled Oct 23 2013 at 13:19:34 > ENV: Java is configured as: /usr/bin/java > ENV: java full version "1.7.0_45-mockbuild_2013_10_16_17_51-b00" > ENV: Threading enabled: True > MEM: memory is 3 gB > ENV: system is Linux > ENV: uima-ducc-rm.jar: 0.8.0-SNAPSHOT compiled at > 10-23-2013 12:51 > ENV: uima-ducc-pm.jar: 0.8.0-SNAPSHOT compiled at > 10-23-2013 12:51 > ENV: uima-ducc-orchestrator.jar: 0.8.0-SNAPSHOT compiled at > 10-23-2013 12:51 > ENV: uima-ducc-sm.jar: 0.8.0-SNAPSHOT compiled at > 10-23-2013 12:51 > ENV: uima-ducc-web.jar: 0.8.0-SNAPSHOT compiled at > 10-23-2013 12:51 > ENV: uima-ducc-cli.jar: 0.8.0-SNAPSHOT compiled at > 10-23-2013 12:51 > ENV: uima-ducc-agent.jar: 0.8.0-SNAPSHOT compiled at > 10-23-2013 12:51 > ENV: uima-ducc-common.jar: 0.8.0-SNAPSHOT compiled at > 10-23-2013 12:51 > ENV: uima-ducc-jd.jar: 0.8.0-SNAPSHOT compiled at > 10-23-2013 12:51 > ActiveMQ is not running on tcp://<head-mode>:61616 > Checking 1 nodes > Waiting for Completion > > Checking jameson ... > no processes found. > Host key verification failed. > All threads returned > >
