Re: [HTCondor-users] stuck submit jobs

[Hiroshi Yamaguchi <yamaguchi@xxxxxxxxxxxxxxxxxxx>]

Dear Ben and Nate

Great thanks for your advice.
I fix the ALLOW_WRITE value as 
ALLOW_WRITE=hkt*.bepp.rcapp.kyushu-u.ac.jp, 192.168.12.0/24 (hkt* are 
client node and 192.* are their IP address) on the configuration files 
of all nodes, and restart them.
After that, the jobs are working now.

Thank you again for your helps.
Best regards,

Hiroshi

On 2014/10/08 1:46, Ben Cotton wrote:
> On Tue, Oct 7, 2014 at 10:55 AM, Hiroshi Yamaguchi
> <yamaguchi@xxxxxxxxxxxxxxxxxxx> wrote:
>
> > Great thanks for your comment.
> > Do you mean I should set the values as "IP_ADDRESS = 192.168.12.1" and
> > "ALLOW_READ =  $(CONDOR_HOST), $(IP_ADDRESS)" ?
> > The condor does not work on this configuration.
> Not quite. IP_ADDRESS is a pre-defined macro, so you shouldn't need to
> set it. But you will need to allow hosts in your pool to write to the
> central manager. For example, if 192.168.12.0/24 contains your pool,
> you would add:
>
> ALLOW_WRITE = $(ALLOW_WRITE), 192.168.12.0/24
>
> See http://research.cs.wisc.edu/htcondor/manual/v8.2/3_6Security.html
> for more information on ALLOW/DENY settings. Looking at the logs
> again, it looks like the host is identifying itself as
> bepp01.bepp.rcapp.kyushu-u.ac.jp but that's not in the ALLOW_WRITE
> settings, so you may just need to adjust your ALLOW_WRITE to match
> ALLOW_READ.
>
>
> Thanks,
> BC