Farm machines no longer active
Posted: Wed Nov 27, 2024 10:02 am
Hello,
I'm looking for some help on my farming machines stopping working after a failed upgrade.
I have the following:
Dedicated Machine.
Cache stored on network drive.
2x Farm Machines.
After a failed upgrade, the farm machines no longer show as enabled in the web interface and their heartbeat stopped.
I've rolled back the install and tried reinstalling the service multiple times but they never reconnect. Can anyone advise on where the config on the host machine might sit that could be preventing the farm machines re-connecting?
It's worth stating that I have not installed the farm service from the running instance, rather I take a clone of the folder and run it on the farm machines locally. This seemed to work fine before and even when I try the corrected approach of installing on the farm from the Host then the farm machines still don't work.
Any thoughts/advice appreciated.
I'm looking for some help on my farming machines stopping working after a failed upgrade.
I have the following:
Dedicated Machine.
Cache stored on network drive.
2x Farm Machines.
After a failed upgrade, the farm machines no longer show as enabled in the web interface and their heartbeat stopped.
I've rolled back the install and tried reinstalling the service multiple times but they never reconnect. Can anyone advise on where the config on the host machine might sit that could be preventing the farm machines re-connecting?
It's worth stating that I have not installed the farm service from the running instance, rather I take a clone of the folder and run it on the farm machines locally. This seemed to work fine before and even when I try the corrected approach of installing on the farm from the Host then the farm machines still don't work.
Any thoughts/advice appreciated.