Repository navigation
Error on upgrade to 8.3.1 #104
|
Hi folks Trying to resolve the issue in an earlier message by upgrading to 8.3.1 but I get the following For now I am going to roll back and do a full upgrade to 7.4.7 and a reboot of everything, but as I will want to go to v8 at the next downtime, any advice on how to deal with this? To the best of my knowledge all the storage servers were down. |
Replies: 4 comments
|
Hello, Can you share the output from these commands prior to the upgrade? The Note: This discussion forum is primarily community-driven. Maintainers may occasionally comment to clarify behavior or help determine whether something could be a bug, but support here is provided on a best-effort basis. If you require guaranteed assistance, please review our support policy. |
|
With --mirrorgroups this gives no output (we don't have mirror groups) but without I get: So this all looks OK I think. We had a mixture of 7.4.6 and 7.4.7 on the storage nodes so perhaps that was the issue? I have successfullly upgraded everything to 7.4.7 so I can try again at the next downtime. |
|
Just to sanity check, the management and metadata servers were also on 7.4.6+? What I would do is copy your management directory to another machine, install the BeeGFS 8 management there, then attempt to run the import and see if it works now. That way you can test and get to the bottom of any issues before your next upgrade window. If it still fails I would suspect the format of the Unfortunately because these situations vary and require more in-depth investigation what exactly is wrong, we advise opening a support ticket to investigate further and correct any issues. If you don't have a support contract you could still reach out to support@thinkparq.com and see what options exist. |
|
Yes management and metadata were also on 7.4.6. We had a couple of storage servers on 7.4.7 prior to the attempted upgrade. I'll try your suggestion with the management directory... Unfortunately we do not have a support contract but I'll see whether the problem still exists now and then think about the next steps. |
Just to sanity check, the management and metadata servers were also on 7.4.6+?
What I would do is copy your management directory to another machine, install the BeeGFS 8 management there, then attempt to run the import and see if it works now. That way you can test and get to the bottom of any issues before your next upgrade window.
If it still fails I would suspect the format of the
targetStatesfile has some issue(s) that need to be manually fixed. The BeeGFS 7 management was more relaxed about allowing invalid system states to exist silently, and that has been improved in BeeGFS 8.Unfortunately because these situations vary and require more in-depth investigation what exactly is wrong…