Subject: Re: [Condor-users] NIC bind problem Windows
Hi Jaime,
Thank you for your prompt response.
I have tested and it worked fine.
I have not noticed the documentation
change from version 7.2.x to 7.6.x series, where wildcards usage are explicitly
described. I have had in mind the old version manual. My fault.
Regards,
Klaus
Jaime Frey <jfrey@xxxxxxxxxxx> Sent by: condor-users-bounces@xxxxxxxxxxx
01/08/2012 19:13
Please respond to
Condor-Users Mail List <condor-users@xxxxxxxxxxx>
I am using Condor Version 7.6.6 in a pool of Windows desktops, and I have
a NIC binding issue when the Desktop has more then one NIC. We also used
before the v7.2.4 and the 7.4.x series.
In a particular desktop (PC315286, Windows XP Pro x64 Edition), we have
two physical NIC e two VMware instances NICs.
It always binds to a NIC that has no cable connected and when I disable
it, it binds to one of the VMware NICs.
The network Condor should bind to is "Local
Area Connection" above!
The MasterLog shows:
08/01/12 11:21:17 DaemonCore: command socket at <169.254.127.217:24512>
08/01/12 11:21:17 DaemonCore: private command socket at <169.254.127.217:24512>
08/01/12 11:21:17 Setting maximum accepts per cycle 4.
08/01/12 11:21:18 Started DaemonCore process "C:\condor/bin/condor_schedd.exe",
pid and pgroup = 3232
08/01/12 11:21:19 Started DaemonCore process "C:\condor/bin/condor_startd.exe",
pid and pgroup = 3252
08/01/12 11:21:19 Started DaemonCore process "C:\condor/bin/condor_kbdd.exe",
pid and pgroup = 3260
08/01/12 11:21:30 PERMISSION DENIED to unauthenticated@unmapped from host
169.254.127.217 for command 60008 (DC_CHILDALIVE), access level DAEMON:
reason: DAEMON authorization policy contains no matching ALLOW entry for
this request; identifiers used for this host: 169.254.127.217,PC315286.corp.ad.emb
Using BIND_ALL_INTERFACES = TRUE
gives the same issue!
When I disable the second NIC, it shows:
08/01/12 11:31:32 DaemonCore: command socket at <192.168.206.1:61402>
08/01/12 11:31:32 DaemonCore: private command socket at <192.168.206.1:61402>
08/01/12 11:31:32 Setting maximum accepts per cycle 4.
08/01/12 11:31:33 Started DaemonCore process "C:\condor/bin/condor_schedd.exe",
pid and pgroup = 3264
08/01/12 11:31:34 Started DaemonCore process "C:\condor/bin/condor_startd.exe",
pid and pgroup = 3288
08/01/12 11:31:34 Started DaemonCore process "C:\condor/bin/condor_kbdd.exe",
pid and pgroup = 3296
08/01/12 11:31:48 PERMISSION DENIED to unauthenticated@unmapped from host
192.168.206.1 for command 60008 (DC_CHILDALIVE), access level DAEMON: reason:
DAEMON authorization policy contains no matching ALLOW entry for this request;
identifiers used for this host: 192.168.206.1,PC315286.corp.ad.emb
When I set NETWORK_INTERFACE = 10.3.28.14
:
08/01/12 11:56:43 DaemonCore: command socket at <10.3.28.14:38946>
08/01/12 11:56:43 DaemonCore: private command socket at <10.3.28.14:38946>
08/01/12 11:56:43 Setting maximum accepts per cycle 4.
08/01/12 11:56:44 Started DaemonCore process "C:\condor/bin/condor_schedd.exe",
pid and pgroup = 3208
08/01/12 11:56:45 Started DaemonCore process "C:\condor/bin/condor_startd.exe",
pid and pgroup = 3220
08/01/12 11:56:46 Started DaemonCore process "C:\condor/bin/condor_kbdd.exe",
pid and pgroup = 3264
it fixes the issue, but the IP addreses are dynamic IP and if it changes
I need to hardcode the new addres to the config file.
Prior to version 7.6.6, version 7.2.4 as an example, I used to rearrange
the order of the NICs in the "Network Connections" panel, "Advanced"
Menu option, "Advanced Settings...", under Connections, and Condor
always respected this settings. In v7.2.4, this avoids the use of the NETWORK_INTERFACE
config setting.
In version 7.6.6 Condor does not respect this settings.
Was this behavior changed from v7.2.4 to v7.6.6? Could someone point in
which stable release this was changed?
Is there any other way to overcome this issue?
Try setting this in your config file:
NETWORK_INTERFACE = 10.*
This should cause Condor to use the network interface
whose IP address matches the pattern.
Thanks and regards,
Jaime Frey
UW-Madison Condor Team
_______________________________________________
Condor-users mailing list
To unsubscribe, send a message to condor-users-request@xxxxxxxxxxx with
a
subject: Unsubscribe
You can also unsubscribe by visiting
https://lists.cs.wisc.edu/mailman/listinfo/condor-users
The archives can be found at:
https://lists.cs.wisc.edu/archive/condor-users/
This message is intended solely for the
use of its addressee and may contain privileged or confidential information.
All information contained herein shall be treated as confidential and shall
not be disclosed to any third party without Embraer’s prior written approval.
If you are not the addressee you should not distribute, copy or file this
message. In this case, please notify the sender and destroy its contents
immediately.
Esta mensagem é para uso exclusivo de seu destinatário e pode conter informações
privilegiadas e confidenciais. Todas as informações aqui contidas devem
ser tratadas como confidenciais e não devem ser divulgadas a terceiros
sem o prévio consentimento por escrito da Embraer. Se você não é o destinatário
não deve distribuir, copiar ou arquivar a mensagem. Neste caso, por favor,
notifique o remetente da mesma e destrua imediatamente a mensagem.
![[Computer Systems Lab]](https://www-auth.cs.wisc.edu/pics/csl_logo.gif){kind=logo}