Thanks Burn - I'm going to try with a secondary broker and see how it goes.
-John -----Original Message----- From: Burn Lewis [mailto:[email protected]] Sent: Thursday, July 20, 2017 6:58 AM To: [email protected] Subject: Re: DUCC Web Server Service Visibility and Default Reservations I think this is one of the reasons we don't encourage use of the DUCC broker ... it uses non-standard ports (to avoid conflicts with a user-created broker) and your error message probably means that the default pinger cannot access the default JMX port of 1099. There is a way to specify the JMX port for the pinger but I think the simple and more general approach is for you to use a separate broker. The DUCC installation includes UIMA-AS so from some shell set UIMA_HOME and start a broker, e.g. export UIMA_HOME=$DUCC_HOME/apache-uima $UIMA_HOME/bin/startBroker.sh ~Burn On Wed, Jul 19, 2017 at 4:25 PM, Osborne, John David (Campus) < [email protected]> wrote: > Thanks Burn, looks like it is deployed but not healthy due to a > refused RMI connection. The web services page is refreshed, in > addition to displaying no services it does not display values for some > other fields (Updated, Utilization) that are displayed on other web server > pages. > > Any info appreciated, I'm not seeing anything more in sm.log than I am > seeing here from the ducc_services --query I ran. Both of the lines > end at the number 38 for the MetaPid. > > -John > > > [X] > > > Service: UIMA-AS:MRN_Document_Pull_Queue:tcp://localhost:61617 > Service Class : Registered as ID 33 Owner[ducc] instances[1] > linger[300000] > Implementors : 31.0 > References : None > Dependencies : none > Service State : Available > Ping Active : true > Start Mode : manual, Enabled > Last Use : N/A > Last Ping : Wed Jul 19 15:02:54 CDT 2017 > Last Runnable : Wed Jul 19 15:03:18 CDT 2017 > Registration Date : Tue Jul 18 14:55:18 CDT 2017 > Service Statistics: > Alive[true] Healthy[false] + Info: JMX Failure[Failed to > retrieve RMIServer stub: javax.naming.ServiceUnavailableException > [Root exception is java.rmi.ConnectException: Connection refused to > host: localhost; nested exception is: > java.net.ConnectException: Connection refused (Connection > refused)]]] MetaNode[10.23.142.165] MetaPid[1988:38 > > > ________________________________ > From: Burn Lewis <[email protected]> > Sent: Wednesday, July 19, 2017 2:50:18 PM > To: [email protected] > Subject: Re: DUCC Web Server Service Visibility and Default > Reservations > > Did you refresh the Services page? Ensure that the Users field is > empty (except for the hint)? Also try $DUCC_HOME/bin/ducc_services > --query > > Reservations made by the "System" user are for internal use. > > ~Burn > > On Wed, Jul 19, 2017 at 3:21 PM, Lou DeGenaro <[email protected]> > wrote: > > > It should always be the case that if you successfully "ducc_services > > --register..." a service it should appear on the ducc-mon Services page. > > When you click on the Id for a Service you should see zero of more > > deployments, each Running instance corresponding to an O/S process. > > > > If you ever want to run DUCC Jobs you need to have the JobDriver > > Reservation. > > > > Lou. > > > > On Wed, Jul 19, 2017 at 11:53 AM, Osborne, John David (Campus) < > > [email protected]> wrote: > > > > > I have (according the log files in $HOME/ducc/logs) started as > registered > > > service successfully via ducc_services. I can see the process > > > running > via > > > the ps command, but it does not appear in the webserver under the > > services > > > section. Is this because I am running ducc anonymously using > > > active-ducc-unsecure.xml? I did not implement a pinger for this > service, > > > but I assume that since it is an AS service a default pinger will > > > be provided for me. I'm guessing only services with pingers appear > > > in the service page on the ducc webserver...? > > > > > > I also noticed a reservation in DUCC, dating back to when I first > > > installed DUCC with an ID of 0. It is of class JobDriver, from the > system > > > user, is in the state Assigned with 0 user processes and does not > > > have > > the > > > option for termination. Is this some reservation I created > > > errorenously > > or > > > is this standard on all ducc systems? I would like to cancel it if > > > I > > don't > > > need it, it taking up 2 GBS of memory. > > > > > > Thanks for any help, > > > > > > -John > > > > > >
