Greenlight v2 => v3 migration script fails #5742
Comments
|
What's the command that you ran? |
|
I used: |
|
Can you try updating both v2 and v3 please |
|
Yes, the containers are in the latest version and so is bbb. |
|
What's the output of |
|
It seems there is no rails command: |
|
Try either |
|
Thanks for reply. with command :
|
|
Thats very strange - everything looks good from here. re-running it will give you the same errors? |
|
Yes migration role command Is normal command
isn't there a problem with the database that would cause this kind of error? |
|
Nope that's fine. Can you confirm your v2 and v3 versions please? |
isn't there a problem with the BBB version ? |
|
Nope, this is unrelated to BBB. One final thing, maybe this will work Try that and then re-run the commands |
|
Return : And run again commands migrate role do same things: |
|
Oh - I just looked through your env variables This should be pointing at wherever your v3 server is deployed, not at your BigBlueButton server. How did you install v3? |
|
BigBlueButton server, v2 and v3 are on same server. Web interface v3 on But endpoint already same on v2 and v3 env |
try |
|
Same issue with do the containers have to be on the same docker network ? |
|
No, v2 only needs to be able to reach the url specified via Try |
|
Yes both versions run under the same domain and use greenlights nginx config. Command |
|
lgtm. i'm out of ideas. |
|
Hello, I've been suffering from the "same" problem, and I have read on other threads that this issue is at least 1 year old. In my case, I have the Greenlight v3 running in a different VM than the v2. I followed the same instructions and checks as above with similar results. Indeed, nobody above commented on this, but I suppose that the OP did it: put the same SECRET KEY in both .env files, for SECRET_KEY_BASE (v2 & v3) and for V3_SECRET_KEY_BASE (v2). In my case, the return of the command: sudo docker exec -it greenlight-v2 bundle exec rake migrations:rolesis this: /usr/src/app/vendor/bundle/ruby/2.7.0/gems/net-protocol-0.1.3/lib/net/protocol.rb:68: warning: already initialized constant Net::ProtocRetryError
/usr/local/lib/ruby/2.7.0/net/protocol.rb:66: warning: previous definition of ProtocRetryError was here
/usr/src/app/vendor/bundle/ruby/2.7.0/gems/net-protocol-0.1.3/lib/net/protocol.rb:208: warning: already initialized constant Net::BufferedIO::BUFSIZE
/usr/local/lib/ruby/2.7.0/net/protocol.rb:206: warning: previous definition of BUFSIZE was here
/usr/src/app/vendor/bundle/ruby/2.7.0/gems/net-protocol-0.1.3/lib/net/protocol.rb:504: warning: already initialized constant Net::NetPrivate::Socket
/usr/local/lib/ruby/2.7.0/net/protocol.rb:503: warning: previous definition of Socket was here
warning: parser/current is loading parser/ruby27, which recognizes2.7.6-compliant syntax, but you are running 2.7.7.
Please see https://github.com/whitequark/parser#compatibility-with-ruby-mri.
Roles migration complete.I think the message "Roles migration complete" is wrong, isn't it? I think that if the migrations were successful, I should see a list of the roles migrated. Am I wrong? When i run the next command (to migrate users): sudo docker exec -it greenlight-v2 bundle exec rake migrations:usersthen i get this: /usr/src/app/vendor/bundle/ruby/2.7.0/gems/net-protocol-0.1.3/lib/net/protocol.rb:68: warning: already initialized constant Net::ProtocRetryError
/usr/local/lib/ruby/2.7.0/net/protocol.rb:66: warning: previous definition of ProtocRetryError was here
/usr/src/app/vendor/bundle/ruby/2.7.0/gems/net-protocol-0.1.3/lib/net/protocol.rb:208: warning: already initialized constant Net::BufferedIO::BUFSIZE
/usr/local/lib/ruby/2.7.0/net/protocol.rb:206: warning: previous definition of BUFSIZE was here
/usr/src/app/vendor/bundle/ruby/2.7.0/gems/net-protocol-0.1.3/lib/net/protocol.rb:504: warning: already initialized constant Net::NetPrivate::Socket
/usr/local/lib/ruby/2.7.0/net/protocol.rb:503: warning: previous definition of Socket was here
warning: parser/current is loading parser/ruby27, which recognizes2.7.6-compliant syntax, but you are running 2.7.7.
Please see https://github.com/whitequark/parser#compatibility-with-ruby-mri.
Unable to migrate User:
UID: gl-mzyagccgkozf
Name: personal_user_name_1
Provider: greenlight
Errors: ["InvalidParams"]
Unable to migrate User:
UID: gl-wymjnjolxued
Name: personal_user_name_2
Provider: greenlight
Errors: ["InvalidParams"]
Unable to migrate User:
UID: gl-bnbdsokhbqbl
Name: personal_user_name_3
Provider: greenlight
Errors: ["InvalidParams"]
Unable to migrate User:
UID: gl-kctsrjtrpejx
Name: personal_user_name_4
Provider: greenlight
Errors: ["InvalidParams"]
Unable to migrate User:
UID: gl-elkertszzprw
Name: personal_user_name_5
Provider: greenlight
Errors: ["InvalidParams"]
Unable to migrate User:
UID: gl-jvwfwvxiusmp
Name: personal_user_name_6
Provider: greenlight
Errors: ["InvalidParams"]
Users migration completed.
In case of an error please retry the process to resolve.
If you have not migrated your roles, kindly run 'rake migrations:roles' first and then retry.So, I understand that the migrations didn't complete, and I suppose that this is the cause of the "unable to migrate user" error messages. I'm really not sure about what the expected result of each command is because this is my first migration from v2 to v3. Although the official guide for it (https://docs.bigbluebutton.org/greenlight/v3/migration/) mentions the results for a successful migration, it doesn't cover a "strange mid-successful migration". I'm not very clear on how to understand these messages. So, any help will be very welcomed. |
|
Here's the grammatically corrected version: Corrected VersionPlease, can at least someone guide me on a way to migrate recordings done in v2 to the v3 server MANUALLY and enable users on v3 to manage and share those recordings from Greenlight v3? I've manually recreated the roles and users of v2 in v3. But we need now to copy the recordings of the last 2 years from v2 to the v3 server and make them accessible for users on v3. How can I do that? Taking into account that the official "migration script" is failing and nobody is able to help us make it run. 🤗 Any help is welcomed. Thanks in advance. Note: just after install the v3 server i set the same SECRET_KEY (editing |
|
Hello, We migrated again. We removed the roles. We added instructions to the script like this: We didn't migrate settings or records We check again but it seem solved for us |
|
Same issue here.. I wonder why they changed the whole DB structure making it virtually impossible to migrate correctly any data at all. If anyone wants to migrate recordings just create the old rooms with the same room name and add to the docker compose file pgadmin on both sides login to both postgres db and just clone the old meeting id to the new room and resync recordings. |
Hello,
I have a system setup with V2 and V3 and I am trying to migrate my roles, users etc.
BBB is on 2.7.
Greenlight (v2 and v3) docker already in last version.
.env V2
.env V3
Command to migrate rôle:
docker exec -it greenlight-v2 bundle exec rake migrations:rolesNginx logs show 400 code
Docker Greenlight-v3 logs same status 400
Is there any special configuration for these errors?
It's as if API V1 is no longer available. Do I need to backtrack to BBB version 2.6 or even 2.5?
Thanks
The text was updated successfully, but these errors were encountered: