Mailing List Archives
Authenticated access
|
|
|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [HTCondor-users] condor_status nodename shows nothing when HOSTNAME=shortname in /etc/sysconfig/network
- Date: Mon, 15 Dec 2014 15:33:32 -0600
- From: Brian Bockelman <bbockelm@xxxxxxxxxxx>
- Subject: Re: [HTCondor-users] condor_status nodename shows nothing when HOSTNAME=shortname in /etc/sysconfig/network
Hi Gang,
I found the ticket I was thinking about:
https://htcondor-wiki.cs.wisc.edu/index.cgi/tktview?tn=3694
Unfortunately, that should be fixed in 8.2.x. It looks like Jaime and Erik worked on that ticket - do either have a suggestion?
Brian
> On Dec 15, 2014, at 11:12 AM, qing <gang.qin@xxxxxxxxxxxxx> wrote:
>
> Hi, Brian:
>
> I am using condor-8.2.2-265643.x86_64.
>
> Cheers,Gang
>
>
> On 15/12/2014 16:33, Brian Bockelman wrote:
>> Hi Gang,
>>
>> What version of HTCondor is this? I seem to recall a few bugfixes along these lines to make the "condor_status $HOSTNAME" behavior more natural.
>>
>> Brian
>>
>>> On Dec 11, 2014, at 9:13 AM, qing <gang.qin@xxxxxxxxxxxxx> wrote:
>>>
>>> Dear Condor Expert:
>>>
>>> In /etc/sysconfig/network, when we have HOSTNAME=node103.beowulf.cluster, e.g. the $fqdn, condor_status nodename works fine.
>>>
>>> But when we change it to HOSTNAME=node103, e.g. the shortname, then condor_status nodename shows nothing, but condor_status | grep nodename still has something, and condor_status slot1@shortname still works, nslookup between this WN and the central server is good, so it this a bug or developed to be like this?
>>>
>>> Here are detailed info:
>>>
>>> node103:~# hostname
>>> node103
>>>
>>> node103:~# hostname -f
>>> node103.beowulf.cluster
>>>
>>> node103:~# cat /etc/sysconfig/network
>>> NETWORKING=yes
>>> HOSTNAME=node103
>>> GATEWAY=10.141.246.7
>>>
>>> node103:~# condor_status | grep node103
>>> slot1@node103 LINUX X86_64 Owner Idle 0.000 112875 0+00:00:04
>>> slot1_1@node103 LINUX X86_64 Claimed Busy 0.000 3000 0+00:00:04
>>> slot1_2@node103 LINUX X86_64 Claimed Busy 0.000 3000 0+00:00:04
>>> slot1_3@node103 LINUX X86_64 Claimed Idle 0.000 3000 0+00:00:04
>>>
>>> node103:~# condor_status node103
>>> node103:~# condor_status node103.beowulf.cluster
>>>
>>> node103:~# condor_status slot1@node103
>>> Name OpSys Arch State Activity LoadAv Mem ActvtyTime
>>>
>>> slot1@node103 LINUX X86_64 Owner Idle 0.000 112875 0+00:00:04
>>> Total Owner Claimed Unclaimed Matched Preempting Backfill
>>>
>>> X86_64/LINUX 1 1 0 0 0 0 0
>>>
>>> Total 1 1 0 0 0 0 0
>>> node103:~# condor_status slot1_1@node103
>>> Name OpSys Arch State Activity LoadAv Mem ActvtyTime
>>>
>>> slot1_1@node103 LINUX X86_64 Claimed Busy 0.000 3000 0+00:00:04
>>> Total Owner Claimed Unclaimed Matched Preempting Backfill
>>>
>>> X86_64/LINUX 1 0 1 0 0 0 0
>>>
>>> Total 1 0 1 0 0 0 0
>>>
>>> Cheers,Gang
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> HTCondor-users mailing list
>>> To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx with a
>>> subject: Unsubscribe
>>> You can also unsubscribe by visiting
>>> https://lists.cs.wisc.edu/mailman/listinfo/htcondor-users
>>>
>>> The archives can be found at:
>>> https://lists.cs.wisc.edu/archive/htcondor-users/
>>
>> _______________________________________________
>> HTCondor-users mailing list
>> To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx with a
>> subject: Unsubscribe
>> You can also unsubscribe by visiting
>> https://lists.cs.wisc.edu/mailman/listinfo/htcondor-users
>>
>> The archives can be found at:
>> https://lists.cs.wisc.edu/archive/htcondor-users/
>
> _______________________________________________
> HTCondor-users mailing list
> To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx with a
> subject: Unsubscribe
> You can also unsubscribe by visiting
> https://lists.cs.wisc.edu/mailman/listinfo/htcondor-users
>
> The archives can be found at:
> https://lists.cs.wisc.edu/archive/htcondor-users/