-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
sr3 3.0.53 mkdir crash when configurations have statehost set. #1080
Comments
crash addressed by #1076 but not root cause. |
diagnosis:
Actual fix is to create the correct state directory, rather than the wrong one. work-around: create the correct state directory manually/outside sr3. If it exists, it's lack won't be detected, and it won't mkdir it.
repair by building the missing state directory:
on each host where the command is to be invoked... this may be quite tedious on a large cluster where hundreds of hosts are involved. |
A second work-around, in the case of missing directories, is to start them up on the machine. |
There is an additional weirdness where two host directories are created, one with fqdn, the other with just the hostname. the fqdn one gets the an empty log file created, and the the other gets the rest of the state files (including a functional log file.) fix is here: dfe67d8 |
Alternative approach to fixing this problem: why are there mkdirs in that part of the code at all... it means that if we run "sr3 status" it creates a whole bunch of state directories... feels wrong and odd. It should be just reading the state that is there. another branch is taking that approach. |
remove unneded statehost print 4ac239a |
The text was updated successfully, but these errors were encountered: