Hi Yi-Wen, On Wed, Nov 11, 2015 at 1:47 AM, Yi-Wen Liu <[email protected]> wrote:
> Hello, > > When I ran the project on DUCC, it finally reached "running" but then it > showed "MonitorWarning", and canceled by driver. > Cancelled by driver indicates that the Job Driver process failed, probably because of a problem in the application CR. > > I tried to debug using all_in_one local/remote, but it didn't have error > which I thought it was working, however there's no output... > No output is not right if some was expected. > > Could it be any privilege setting problem? > Are there any custom environmental parameters required for the application code? DUCC does *not* pass on the environment active when submitting work. Any parameters must be explicitly specified. Is DUCC running as user=ducc? If so, is ducc_ling properly configured to spawn application processes as the submitting user? > Really hope somebody can help me out, I didn't find other keyword useful > in log file, the connection refused error showed up 12 times in total. > This error is because the Job Driver process terminated. Eddie
