I have a system considering of 3 nodes that are connected to the same network:
anubis: compile node (running also the scheduler)
titania: laptop
carbon: vm running on titania
My usual setup is that I trigger a compile inside the vm and have it distribute it to the compile node. Up until last week that was working fine, but when I tried today, the compile node no longer receives the environment.
I recompiled icecream on the compile node with #define DEBUG_SCHEDULER 3, but I'm not getting any wiser.
What i see is this:
iceccd
[1433] 2021-01-30 14:26:24: ignoring localhost lo for broadcast
[1433] 2021-01-30 14:26:24: broadcast eth0 192.168.1.255
[1433] 2021-01-30 14:26:24: scheduler not yet found/selected.
[1433] 2021-01-30 14:26:24: Suitable scheduler found at 192.168.1.101:8765 (version: 42)
[1433] 2021-01-30 14:26:24: scheduler not yet found/selected.
[1433] 2021-01-30 14:26:27: scheduler is on 192.168.1.101:8765 (net liwjatan.org)
[1433] 2021-01-30 14:26:29: Connected to scheduler (I am known as 192.168.1.101)
I have a system considering of 3 nodes that are connected to the same network:
My usual setup is that I trigger a compile inside the vm and have it distribute it to the compile node. Up until last week that was working fine, but when I tried today, the compile node no longer receives the environment.
I recompiled icecream on the compile node with
#define DEBUG_SCHEDULER 3
, but I'm not getting any wiser.What i see is this:
iceccd
icecc-scheduler
But even though it says
anubis.liwjatan.org is busy installing since 0 seconds
, nothing's actually happening and eventually I just see:I also tried deploying the environment manually, but that doesn't change anything either. iceccd is just sitting there doing nothing.
Is there anything else I can enable to see why iceccd never picks up the environment?