Open bobwhitelock opened 7 years ago
@mjtko - I see you've been assigned to this, have you started investigating it at all?
From @mjtko on October 17, 2016 10:39
Nope, @vlj91 just auto-assigns me. :-)
OK! :)
I've not been able to reproduce this locally on develop
or on AWS using the 2016.3rc2
template (https://github.com/alces-software/flight-appliance-templates/blob/2016.3rc6/compute/aws/marketplace-solo-professional.json), which @vlj91 said is the same as the one which originally produced it. Seems to rely on something else in the environment or only occurs inconsistently, but does seem to be an issue with database access failing sometimes.
For future reference the command @vlj91 said produced this issue is this:
depots=$(alces gridware depot list -1); for depot in ${depots[@]}; do alces gridware depot install $depot; done; for depot in ${depots[@]}; do alces gridware --yes depot purge $depot; done; alces gridware depot install benchmark``
From @vlj91 on September 30, 2016 11:55
Received the following error whilst (re)installing a depot:
With
--trace
on (it happened the second time round trying to install as well):Steps performed:
2016.3r1
templatebenchmark
depot againCopied from original issue: alces-software/clusterware#213