Crosspost: migration errors greenlight v2 -> v3
Martin Thomas Schrott
as nobody answered in the greenlight list, I try to get help here ...
thanks!
Martin
Am 16.10.2025 um 18:09 schrieb 'Martin Thomas Schrott' via
bigbluebutton-greenlight:
> Hi guys,
>
>
> we eventually started a migration test of our greenlight instance and
> got some errors - hope somebody can help us to get it running:
>
>
> * setup:
>
> I updated the old gl to last v2 and the new gl to last v3 version.
>
> Both work as expected with their own data - the new one only has one
> test room of admin for now.
>
>
> When trying to migrate following the guide, we geht the errors below
> for a lot of users and rooms, the roles seem to work allthough.
>
> I hope someone can help to get this fixed.
>
>
> thanks and
>
> best wishes
>
>
> Martin
>
>
> --
>
>
> * general: we get this warning:
>
>
> /usr/src/app/vendor/bundle/ruby/2.7.0/gems/net-protocol-0.1.3/lib/net/protocol.rb:68:
> warning: already initialized const
> ant 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 cons
> tant 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 cons
> tant 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: they seem to have worked well
>
>
> Successfully migrated Role:
> ID: 6
> Name: Manager
> Provider: greenlight
> Successfully migrated Role:
> ID: 7
> Name: Sci
> Provider: greenlight
> Successfully migrated Role:
> ID: 8
> Name: Edu
> Provider: greenlight
> Successfully migrated Role:
> ID: 9
> Name: External
> Provider: greenlight
>
>
> Roles migration complete.
>
>
>
> * users: we got 187 identical errors with no information as shown
> below - a few thousand users have worked though. The name is
> anonymized and does not include any strange characters.
>
>
> Unable to migrate User:
> UID: gl-ncbrnizwbmuu
> Name: X, X
> Provider: ldap
> Errors: ["SomethingWentWrong"]
>
>
>
> * rooms (please note we already set the client_max_body_size 2g; -
> tryed 512m and then 2g - in http, server, and all locations. as
> setting in one of them did not solve the issue - anyway also all those
> did not help)
>
>
> Unable to migrate Room:
> UID: hocheXXXr
> Name: X X
> Provider: ldap
> rake aborted!
> JSON::ParserError: 859: unexpected token at '<html>
> <head><title>413 Request Entity Too Large</title></head>
> <body>
> <center><h1>413 Request Entity Too Large</h1></center>
> <hr><center>nginx</center>
> </body>
> </html>
> '
>
>
Ahmad Farhat
Can you check the logs from v3 and post them here please
Martin Thomas Schrott
Hi Ahmad
and thanks for your answer!
In the meantime I could solve all the problems with quite a big amount of investigation and debugging ;-)
But I have some feedback that might help to improve some things ...
1. it currently is not possible to rerun migrations - the migration does not remigrate users when the email already exists in the new system ... I think this should really be possible to rerun in case of earlier errors as I had them.
2. to rerun I had to db:reset on v3 and after that the user migration failed for all users that had the role users, as the v3 had no user role after the reset.
Either I would have had to run some init command? (is not documented in the migration or installation guide)
-> what would this init command be and should I run it after a db:reset?
or the role should be created during the migration to allow to migrate users of role user anyway.
-> I think the migration script should in any case create the role if it is missing :-)
3. the users that crashed had either no email or a role that was missing on the new system. in either case the error should be reflecting that and not be "something went wrong" ;-) (I have added some code to get more debug output that lead me to this information)
Maybe you could document how one can output debug level messages or / and add that in the code if necessary.
4. the nginx body size problem could be solved by adding the attribute after the include line in the greenlight site-enabled config file. (on all other places it did not help - this could be documented or a commented out line with the large size for migrations could be included by default ;-) ).
5. for oidc setup there are two settings missing in the documentation that are needed:
ClientAuthenticationType: client_secret_basic
and the redirect uri for the provider is:
https://greenlight.your.site/auth/openid_connect/callback
we did fetch these information from the error logs on our oidc provider host by error and tryal.
6. it seems that role settings are not migrated - I have to reconfigure all roles manually on v3.
7. Would you mind to make the room names on the rooms page as headings for better accessibility? (now all text is same and so it is hard to navigate using the keyboard with screenreaders)
8. in the admin panel / users list
should there be some kind of actions? edit users or delete users?
For screenreader users there is nothing aside the list. I cannot do anything here as admin, just list the users.
9. could the site <title> value be placed in the locales as it was in v2? We had it changed to something personal and would like to keep that for our users. Currently we would have to change it in the files directly.
so far my first feedback on and after the migration ;-)
Hope that helps to improve further
thanks and best wishes
Martin
--
You received this message because you are subscribed to the Google Groups "BigBlueButton-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bigbluebutton-...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/bigbluebutton-dev/129105eb-f19a-4cee-989d-ca117f8960e2n%40googlegroups.com.
Martin Thomas Schrott
Hi Ahmad
I figured out some of the answers meanwhile ...
2. to rerun I had to db:reset on v3 and after that the user migration failed for all users that had the role users, as the v3 had no user role after the reset.
Either I would have had to run some init command? (is not documented in the migration or installation guide)-> what would this init command be and should I run it after a db:reset?
or the role should be created during the migration to allow to migrate users of role user anyway.
-> I think the migration script should in any case create the role if it is missing :-)
db:prepare would be needed - anyway the migrate script should do it upfront I guess.
6. it seems that role settings are not migrated - I have to reconfigure all roles manually on v3.
ok I overread the note about the room limit that has to be set per role after migration. sorry - this is already documented.
I found the javascript file in app/app/javascript that sets the title. In my opinion this should be read from the locales to make it customizable ;-)
Martin
To view this discussion visit https://groups.google.com/d/msgid/bigbluebutton-dev/386dc0c6-b651-421d-8a31-ee46f39b646f%40mtsonline.at.