glv2 move to other host

29 views
Skip to first unread message

Martin Thomas Schrott

unread,
Mar 8, 2024, 9:53:51 AMMar 8
to bigbluebutto...@googlegroups.com
Hi,


for our Greenlight v2 (standalone) I need to move it to a new host.

I shut it down and move all files.

on the new host I set the same version (2.13) and start it.


It shows up, but when I try to login with my ldap user it tells the user
or password are wrong.

the log does only show that:

2024-03-08 14:48:49 +0000 - DEBUG:
[2b8a81c2-c65a-481a-afad-8b724f4f3b82] [x.x.68.39] [1m [36mSetting Load
(0.3ms) [0m  [1m [34mSELECT  "settings".* FROM "settings" WHERE
"settings"."provider" = $1 LIMIT $2 [0m [["provider", "greenlight"],
["LIMIT", 1]]
2024-03-08 14:48:49 +0000 - DEBUG:
[2b8a81c2-c65a-481a-afad-8b724f4f3b82] [x.x.68.39] [1m [36mFeature Load
(0.3ms) [0m  [1m [34mSELECT "features".* FROM "features" WHERE
"features"."setting_id" = $1 [0m [["setting_id", 1]]
2024-03-08 14:48:49 +0000 - DEBUG:
[2b8a81c2-c65a-481a-afad-8b724f4f3b82] [x.x.68.39]   [1m [36mUser Load
(0.4ms) [0m  [1m [34mSELECT  "users".* FROM "users" WHERE
"users"."deleted" = $1 AND "users"."id" IS NULL LIMIT $2 [0m
[["deleted", false], ["LIMIT", 1]]
2024-03-08 14:48:49 +0000 - DEBUG:
[2b8a81c2-c65a-481a-afad-8b724f4f3b82] [x.x.68.39] [1m [36mCACHE User
Load (0.0ms) [0m  [1m [34mSELECT  "users".* FROM "users" WHERE
"users"."deleted" = $1 AND "users"."id" IS NULL LIMIT $2 [0m 
[["deleted", false], ["LIMIT", 1]]
2024-03-08 14:48:49 +0000 - DEBUG:
[2b8a81c2-c65a-481a-afad-8b724f4f3b82] [x.x.68.39] [1m [36mCACHE User
Load (0.0ms) [0m  [1m [34mSELECT  "users".* FROM "users" WHERE
"users"."deleted" = $1 AND "users"."id" IS NULL LIMIT $2 [0m 
[["deleted", false], ["LIMIT", 1]]
2024-03-08 14:48:49 +0000 - DEBUG:
[2b8a81c2-c65a-481a-afad-8b724f4f3b82] [x.x.68.39] [1m [36mCACHE User
Load (0.0ms) [0m  [1m [34mSELECT  "users".* FROM "users" WHERE
"users"."deleted" = $1 AND "users"."id" IS NULL LIMIT $2 [0m 
[["deleted", false], ["LIMIT", 1]]
2024-03-08 14:48:49 +0000 - INFO: [2b8a81c2-c65a-481a-afad-8b724f4f3b82]
[x.x.68.39] method=POST path=/b/auth/ldap format=html
controller=SessionsController action=ldap status=302 duration=35.79
view=0.00 db=1.10
location=https://classroom-standby.domain/b/ldap_signin host=greenlight
2024-03-08 14:48:49 +0000 - DEBUG:
[1c2310c8-f6d1-4f28-92c2-a43f34779ed3] [x.x.68.39] [1m [36mSetting Load
(0.5ms) [0m  [1m [34mSELECT  "settings".* FROM "settings" WHERE
"settings"."provider" = $1 LIMIT $2 [0m [["provider", "greenlight"],
["LIMIT", 1]]
2024-03-08 14:48:49 +0000 - DEBUG:
[1c2310c8-f6d1-4f28-92c2-a43f34779ed3] [x.x.68.39] [1m [36mFeature Load
(0.3ms) [0m  [1m [34mSELECT "features".* FROM "features" WHERE
"features"."setting_id" = $1 [0m [["setting_id", 1]]
2024-03-08 14:48:49 +0000 - DEBUG:
[1c2310c8-f6d1-4f28-92c2-a43f34779ed3] [x.x.68.39]   [1m [36mUser Load
(0.5ms) [0m  [1m [34mSELECT  "users".* FROM "users" WHERE
"users"."deleted" = $1 AND "users"."id" IS NULL LIMIT $2 [0m
[["deleted", false], ["LIMIT", 1]]
2024-03-08 14:48:49 +0000 - DEBUG:
[1c2310c8-f6d1-4f28-92c2-a43f34779ed3] [x.x.68.39] [1m [36mCACHE User
Load (0.0ms) [0m  [1m [34mSELECT  "users".* FROM "users" WHERE
"users"."deleted" = $1 AND "users"."id" IS NULL LIMIT $2 [0m 
[["deleted", false], ["LIMIT", 1]]
2024-03-08 14:48:49 +0000 - DEBUG:
[1c2310c8-f6d1-4f28-92c2-a43f34779ed3] [x.x.68.39] [1m [36mCACHE User
Load (0.0ms) [0m  [1m [34mSELECT  "users".* FROM "users" WHERE
"users"."deleted" = $1 AND "users"."id" IS NULL LIMIT $2 [0m 
[["deleted", false], ["LIMIT", 1]]
2024-03-08 14:48:49 +0000 - DEBUG:
[1c2310c8-f6d1-4f28-92c2-a43f34779ed3] [x.x.68.39] [1m [36mCACHE User
Load (0.0ms) [0m  [1m [34mSELECT  "users".* FROM "users" WHERE
"users"."deleted" = $1 AND "users"."id" IS NULL LIMIT $2 [0m 
[["deleted", false], ["LIMIT", 1]]
2024-03-08 14:48:49 +0000 - DEBUG:
[1c2310c8-f6d1-4f28-92c2-a43f34779ed3] [x.x.68.39] [1m [36mCACHE User
Load (0.0ms) [0m  [1m [34mSELECT  "users".* FROM "users" WHERE
"users"."deleted" = $1 AND "users"."id" IS NULL LIMIT $2 [0m 
[["deleted", false], ["LIMIT", 1]]
2024-03-08 14:48:49 +0000 - DEBUG:
[1c2310c8-f6d1-4f28-92c2-a43f34779ed3] [x.x.68.39] [1m [36mCACHE User
Load (0.0ms) [0m  [1m [34mSELECT  "users".* FROM "users" WHERE
"users"."deleted" = $1 AND "users"."id" IS NULL LIMIT $2 [0m 
[["deleted", false], ["LIMIT", 1]]
2024-03-08 14:48:49 +0000 - DEBUG:
[1c2310c8-f6d1-4f28-92c2-a43f34779ed3] [x.x.68.39] [1m [36mCACHE User
Load (0.0ms) [0m  [1m [34mSELECT  "users".* FROM "users" WHERE
"users"."deleted" = $1 AND "users"."id" IS NULL LIMIT $2 [0m 
[["deleted", false], ["LIMIT", 1]]
2024-03-08 14:48:49 +0000 - INFO: [1c2310c8-f6d1-4f28-92c2-a43f34779ed3]
[x.x.68.39] method=GET path=/b/ldap_signin format=html
controller=SessionsController action=ldap_signin status=200
duration=39.77 view=28.89 db=1.44 host=greenlight
2024-03-08 14:48:49 +0000 - DEBUG:
[166712a6-469d-4783-8e76-1895ec36342e] [x.x.68.39] [1m [36mSetting Load
(0.3ms) [0m  [1m [34mSELECT  "settings".* FROM "settings" WHERE
"settings"."provider" = $1 LIMIT $2 [0m [["provider", "greenlight"],
["LIMIT", 1]]
2024-03-08 14:48:49 +0000 - DEBUG:
[166712a6-469d-4783-8e76-1895ec36342e] [x.x.68.39] [1m [36mFeature Load
(0.3ms) [0m  [1m [34mSELECT "features".* FROM "features" WHERE
"features"."setting_id" = $1 [0m [["setting_id", 1]]



I checked it the host is reachable, if all user and passwords are correct.

I searched the net for any help but had no luck.


As I have no more ideas I hope anyone has an idea, that could help to
solve the problem.


Thanks!

Martin


Jean Pluzo

unread,
Mar 11, 2024, 3:56:37 AMMar 11
to bigbluebutton-greenlight
Hi,
just moving the files might not be enough, since there may be some sha1 hashes (or the like) done by using docker compose.
How did you exactly move the files?
I have move glv2 installations before, but you have to be very careful.

Regards,
J.

Martin Thomas Schrott

unread,
Mar 11, 2024, 5:07:32 AMMar 11
to Jean Pluzo, bigbluebutton-greenlight

hi Jean,


thanks for your answer.


i  did stop greenlight with docker compose down.

then rsync or scp the folder with all files and the db and so on. (both do not work as it seems)

on the other side changed the save host in .env to the new hostname

and started gl with docker compose up.


I am thankful for any hint where the error might be that I am overseeing. ;-)


cheers

Martin

--
You received this message because you are subscribed to the Google Groups "bigbluebutton-greenlight" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bigbluebutton-gree...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/bigbluebutton-greenlight/71d3069c-047b-497e-a0bd-0fd69ed20f57n%40googlegroups.com.

Jean Pluzo

unread,
Mar 11, 2024, 8:17:40 AMMar 11
to bigbluebutton-greenlight
Hi,

a few ideas since I don't know how/what exactly you did to move the files:
- make a db dump from the postgres container and restore said dump to the new postgres container
- let the gl container generate a new secret_key_base. update said secret on the db (it should be there somewhere)
- make a complete new glv2 installation in your new server making sure it works. Make a db dump from your old glv2 instance and restore it to the new functioning glv2 instance
- post errors so that other can help

Regards,
J.

Martin Thomas Schrott

unread,
Mar 11, 2024, 9:55:23 AMMar 11
to Jean Pluzo, bigbluebutton-greenlight

Thanks for your answer.


I already posted the complete logs I get on the login attempt.


Greenlight does work normally just the ldap does not authenticate. It just gives "email or password wrong"


I can request the users from the rails console without any problems.

Or even list their rooms via the rails console.


as the db works I do not see what it should help to dump it again. The ldap auth does not need the db at all, does it?


If noone has further ideas I might set up a new greenlight v2 and try ldap out there ... but as it loads the container on startup I can't see where the difference should be ...

thanks

Martin

Martin Thomas Schrott

unread,
Mar 11, 2024, 10:05:19 AMMar 11
to Jean Pluzo, bigbluebutton-greenlight

did start a clean greenlight (only copied the .env settings that are correct)

starts up and gives the same "wrong user or password" on ldap auth.

wtf ...

I really have no idea what I might do wrong here.


:-(

Martin

Martin Thomas Schrott

unread,
Mar 11, 2024, 10:31:49 AMMar 11
to Jean Pluzo, bigbluebutton-greenlight

ok got it.

the newer docker version needed '' arround the values in the .env file

because of that the ldap bind password was not correctly set.

i don't understand why greenlight cannot give an error on that - instead it gives the error, that hints to wrong user data.


anyway, as gl v2 is no longer supported this won't be fixed anymore ;-)


if someone still has to use gl v2 and ends in this problem, that was the solution.


best

Martin

Jean Pluzo

unread,
Mar 12, 2024, 12:00:46 PMMar 12
to bigbluebutton-greenlight
Hi,
this is not an error of glv2 itself, but from the linux shell. The parameters are read from a shell, which means they will be interpreted as commands unless you do exactly what you describe (encasing some parameters in quotes). Glv2 has no way of knowing if the parameter is wrong. It only knows that the values are not sufficient and will try to throw an error accordingly.
In your error logs there seems to be only database queries. From which container did you get these logs?
Regards,
J.

Martin Thomas Schrott

unread,
Mar 12, 2024, 5:56:46 PMMar 12
to Jean Pluzo, bigbluebutton-greenlight

Jean,


thanks for your reply.

the logs are from the greenlight-v2 container and this was the output during the login attempt.


this is exactly what I am missing, that this gl-v2 container outputs some logs regarding the failed ldap bind (of course caused by an docker error, due to non quotet values - so not caused by greenlight itself, but should be noticed by it)

in the logs you see, that gl is not giving any logging regarding the ldap bind or auth. That made  investigating of the issue very hard ;-)

anyway, as gl v2 is not supported anymore and ldap was not included in v3 - nothing to solve here I guess :-)


but if someone hits the problem the solution should be found here ... always - of course - caused by an update of docker version at the same time of moving gl to another host. 

 

thanks for trying to help!


best

Martin

Reply all
Reply to author
Forward
0 new messages