There doesn’t seem to be anything of relevance in the user logs. In fact, there 
doesn’t seem to be much in them at all!

> On 3 Nov 2014, at 14:43, Lou DeGenaro <[email protected]> wrote:
> 
> If you navigate to http://uima-ducc-demo.apache.org:42133/jobs.jsp (that's
> for the live demo - you'd substitute your own host:port accordingly, of
> course) then click on the id of the failing job that should give you access
> to the user's log files (under the Proceses and/or Files tabs).
> 
> Lou.
> 
> On Mon, Nov 3, 2014 at 9:30 AM, James Baker <[email protected]> wrote:
> 
>> We've looked at all the logs we can find, but we'll have another look and
>> see if there are any we missed.
>> 
>> Yes, there's a shared file system set up and both the data and the job
>> files are located on it.
>> 
>> On 3 November 2014 14:23, Lou DeGenaro <[email protected]> wrote:
>> 
>>> Log files may be informative.  There are system and user log files.
>> System
>>> log files are located in ducc_runtime/logs.  User log files (which may be
>>> more helpful here) are located in --log_directory <path> that was
>> specified
>>> on the submit command (and can also be seen by employing the WebServer).
>>> 
>>> Do you have a shared file system amongst your machines and is your user
>>> data located there?
>>> 
>>> Lou.
>>> 
>>> On Mon, Nov 3, 2014 at 8:34 AM, James Baker <[email protected]>
>>> wrote:
>>> 
>>>> I'm trying, without much success, to run DUCC in
>> multi-user-multi-machine
>>>> mode. We've had it running successfully in single-user-single-machine
>>> mode,
>>>> and have followed the installation guide to move to a
>>>> multi-user-multi-machine configuration, but we keep getting an
>> Excessive
>>>> Initialize Failure error from JobDriverTerminateException.java.
>>>> 
>>>> This has happened with both the example job and our own job. We've
>> looked
>>>> through the logs and can't see anything that might suggest what is
>>> causing
>>>> the issue.
>>>> 
>>>> Any one got any idea how to fix the issue?
>>>> 
>>>> Thanks,
>>>> James
>>>> 
>>> 
>> 

Reply via email to