My thor failed to start, reading the /var/log/HPCCSystems/thor/init_thor_2016_06_06_10_58_35.log
It gives an invalid path to the frunssh logs in the error, pointing you to /var/log/frunssh instead of /var/log/HPCCSystems/frunssh
2016-06-06T14:58:35: Starting thor 2016-06-06T14:58:35: removing any previous sentinel file 2016-06-06T14:58:35: Ensuring a clean working environment ... 2016-06-06T14:58:35: Killing slaves 2016-06-06T14:58:35: --------------------------
2016-06-06T14:58:35: starting thorslaves ... 2016-06-06T14:58:35: Error 255 in frunssh 2016-06-06T14:58:35: Please check /var/log/frunssh for more details 2016-06-06T14:58:35: Stopping thor 2016-06-06T14:58:35: thor Stopped 2016-06-06T14:58:35: Killing slaves 2016-06-06T14:58:35: removing init.pid file and slaves file
Conclusion
None
Activity
Show:
Russell Wagner III June 8, 2016 at 1:53 PM
Yes and no... I was testing with a build that didn't have a changelog, hpccsystems-platform-internal_6.0.0-2.el6.x86_64.rpm, and I couldn't get the thor to start. I then re-installed using build hpccsystems-platform-internal_6.0.0-1.el6.x86_64.rpm and everything worked as expected.
Michael Gardner June 6, 2016 at 7:46 PM
Is this an issue with just a misnamed log file, or (from the output) is there actually an issue with thor not starting up correctly?
Fixed
Pinned fields
Click on the next to a field label to start pinning.
My thor failed to start, reading the /var/log/HPCCSystems/thor/init_thor_2016_06_06_10_58_35.log
It gives an invalid path to the frunssh logs in the error, pointing you to /var/log/frunssh instead of /var/log/HPCCSystems/frunssh