bigbluebutton / greenlight

A really simple end-user interface for your BigBlueButton server.
GNU Lesser General Public License v3.0
794 stars 3.8k forks source link

Migrate from greenlight2 to greenlight v3 #5595

Closed miladstar77 closed 10 months ago

miladstar77 commented 10 months ago

I'm currently working to migrate my greenlight-v2 to greenlight-v3 using migrations.rake script, the roles moved successfully but moving users show these error:

Errors: Unable to migrate User:

how can i check logs or errors ? what is the problem?

JeanPluzo commented 10 months ago

Hi,

try docker logs greenlight-v2 (or the name of the greenlight container). Afterwards post the resulting logs so that the developers get a better idea of what's going on on your setup specifically.

Regards, J.

miladstar77 commented 10 months ago

this error : /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.

awo-in-sachsen commented 10 months ago

please notice: V3_ENDPOINT=https://bbb.yourserver.com/ you have to write the url with https and slash at end

miladstar77 commented 10 months ago

i have already set this in my .env in greenlight v2 folder

awo-in-sachsen commented 10 months ago

Have you set your full DNS name at file /etc/hosts like 127.0.1.1 bbb.yourserver.com bbb ? if yes, remove it, because GL v2 try to connect to 127.0.1.1 and get not connection to GLv3

awo-in-sachsen commented 10 months ago

no, i have used a german tutorial for installation, where you should set 127.0.1.1 bbb to 127.0.1.1 bbb.yourserver.com bbb 127.0.0.1 is everytime localhost with a hostentry for bbb.yourserver.com at /etc/hosts it was not possible to migrate users after I removed the hosts entry everything worked great.

I ended up following these instructions: https://andersgood.de/blog/bigbluebutton-2-6-installieren-und-daten-aus-2-4-uebergehen#teil-2-daten-aus-einer-existen -install-bigbluebutton-2-4

I updated directly from 2.4 to 2.7

miladstar77 commented 10 months ago

no, i have used a german tutorial for installation, where you should set 127.0.1.1 bbb to 127.0.1.1 bbb.yourserver.com bbb 127.0.0.1 is everytime localhost with a hostentry for bbb.yourserver.com at /etc/hosts it was not possible to migrate users after I removed the hosts entry everything worked great.

I ended up following these instructions: https://andersgood.de/blog/bigbluebutton-2-6-installieren-und-daten-aus-2-4-uebergehen#teil-2-daten-aus-einer-existen -install-bigbluebutton-2-4

I updated directly from 2.4 to 2.7

Did you use migration script? did it go well ?

awo-in-sachsen commented 10 months ago

yes, the script worked like a charm. I used it several times, first on a test environment, then on the productive system

Since I don't use an email connection, I had to set the passwords manually afterwards

1- docker exec -it greenlight-v3 bash 2- bundle exec rails c 3- User.find_by(email: "bbb@yourdomain.com").update_attribute(:password,"Secret123Key-for-BBB")

PhilippKilian commented 10 months ago

we have the same issue with migration users (especially the password_digest database entry), I have described it here: #5419

farhatahmad commented 10 months ago

@PhilippKilian As mentioned in the release notes, v2 must be upgraded to v2.14.8.4 and v3 must be upgraded to atleast v3.1.0

PhilippKilian commented 10 months ago

@PhilippKilian As mentioned in the release notes, v2 must be upgraded to v2.14.8.4 and v3 must be upgraded to atleast v3.1.0

That v3 must be at least v3.1.0 wasn't part of the relase notes, but I checked it and it works fine with version v3.1+