'Detected that slave is hanging after initialization -> Stopping slave.'
- slave hanging.PNG (4.76 KiB) Viewed 1414 times
'Detected that slave is hanging after initialization.'
Forum rules
Please add your OS and Hardware Configuration in your signature, it makes it easier for us to help you analyze problems. Example: Win 7 64 | Geforce GTX680 | i7 3770 | 16GB
Please add your OS and Hardware Configuration in your signature, it makes it easier for us to help you analyze problems. Example: Win 7 64 | Geforce GTX680 | i7 3770 | 16GB
This error message means that the slave got started and sent some initial information about itself to the daemon, but then didn't send the heartbeat to the daemon. The daemon then assumes that something went wrong and shuts down the slave.
I replied to the other thread. If you try out to produce some log files we can hopefully find out what's going on here.
I replied to the other thread. If you try out to produce some log files we can hopefully find out what's going on here.
In theory there is no difference between theory and practice. In practice there is. - Yogi Berra
-
DigitalOven
- Posts: 29
- Joined: Tue Jul 15, 2014 5:24 am
- Contact:
An observation/how I got this to work today:
I had the exact same issue with "slave hanging after initialization" with the C4d plugin (and LV window, not picture viewer) ... tried "run_installed_daemon" a few times and each time it would eventually give me error message.
When I closed out of C4D, started the slave daemon, then started C4D on the master, things are working fine.
Don't know if this is helpful for debugging or other people but thought I'd put it out there.
-m
EDIT: once I tried to use picture viewer, I also again got the daemon crashing problem and have not found a solution ... I'll try to collect logs over weekend
I had the exact same issue with "slave hanging after initialization" with the C4d plugin (and LV window, not picture viewer) ... tried "run_installed_daemon" a few times and each time it would eventually give me error message.
When I closed out of C4D, started the slave daemon, then started C4D on the master, things are working fine.
Don't know if this is helpful for debugging or other people but thought I'd put it out there.
-m
EDIT: once I tried to use picture viewer, I also again got the daemon crashing problem and have not found a solution ... I'll try to collect logs over weekend
C4D R17 | OSX Mavericks | GTX 780 6GB | Mac Pro 4,1|GTX 780 6GB + GTX 680 4GB on Windows 7 box for slave|