【 使用环境 】生产环境 or 测试环境
测试环境
【 OB or 其他组件 】
OB-all
【 使用版本 】
4.1
【问题描述】清晰明确描述问题
部署完OB4.1版本，在OB-express界面修改了ocp租户的登录密码，重启集群，OCP-express启动失败
【复现路径】问题出现前后相关操作
OCP-express界面修改了OCP租户的密码后，OBD重启集群，
【问题现象及影响】
不能访问ocp-express界面
【附件】
后台命令行连接下ocp租户看下正常吗？确认下使用的是哪个用户。
感觉是改完密码后，odb不知道这个密码更新了，所以连接不了数据库，ocp启动失败
cd ~/.obd/log/ 下的obd日志 看下连接的ocp的配置信息是哪个、
日志显示用的是oceanbase这个密码连接不上，如果你修改了这个密码，可以先用root@ocp租户连接上去修改下meta用户的密码为oceanbase看下。
set password for meta = password(‘oceanbase’);
从2883这个口登录不了数据库了，我还改了proxyro这个用户的密码，是不是因为这个原因导致的
是的，你先还原下这个密码。
这个密码是obd配置文件里管控的，修改后obd无法拿到修改后的密码，后续版本会解决这个问题。
proxyro这个默认密码是啥，改成了oceanbase，还是不行
proxyro@sys默认密码是空。
多谢，终于恢复了
所以说这个租户是不能去改密码的是吧
租户密码可以修改，但可能影响obd连接observer，一般来说不改比较好。
遇到一样的问题，meta密码在web界面修改后，发现重启集群的ob-express服务无法启动，查看日志发现连接用的是初始密码。感觉这是一个bug.
[2023-08-18 13:34:28.655] [DEBUG] – connect 192.168.207.154 -P2883 -umeta@ocp -p7iP0j5aSoU
[2023-08-18 13:34:29.672] [DEBUG] – connect 192.168.207.154 -P2883 -umeta@ocp -p7iP0j5aSoU
[2023-08-18 13:34:30.680] [ERROR] 192.168.207.154: failed to connect meta db
[2023-08-18 13:34:30.777] [INFO] [ERROR] 192.168.207.154: failed to connect meta db
[2023-08-18 13:34:30.777] [INFO]
根据日志把密码修改回初始后，启动正常。
60 history|grep start
[admin@ora01 ~]$ obd cluster start myoceanbase -c ocp-express
Get local repositories ok
Search plugins ok
Open ssh connection ok
Load cluster param plugin ok
Cluster status check ok
Check before start ocp-express ok
Start ocp-express ok
ocp-express program health check ok
Connect to ocp-express ok
±-------------------------------------------------------------------+
| ocp-express |
±----------------------------±---------±-----------------±-------+
| url | username | initial password | status |
±----------------------------±---------±-----------------±-------+
| http://192.168.207.154:8180 | admin | 5Z#3vwC) | active |
±----------------------------±---------±-----------------±-------+
succeed
Trace ID: 54cd2ccc-3d8a-11ee-9afd-722403f5b3f3
If you want to view detailed obd logs, please run: obd display-trace 54cd2ccc-3d8a-11ee-9afd-722403f5b3f3
1 个赞
[admin@ora01 ~]$ obd display-trace 2f79d864-3d88-11ee-bde3-722403f5b3f3
[2023-08-18 13:29:21.643] [DEBUG] - cmd: [‘myoceanbase’]
[2023-08-18 13:29:21.643] [DEBUG] - opts: {‘servers’: None, ‘components’: ‘ocp-express’, ‘force_delete’: None, ‘strict_check’: None, ‘without_parameter’: None}
[2023-08-18 13:29:21.644] [DEBUG] - mkdir /home/admin/.obd/lock/
[2023-08-18 13:29:21.644] [DEBUG] - unknown lock mode
[2023-08-18 13:29:21.644] [DEBUG] - try to get share lock /home/admin/.obd/lock/global
[2023-08-18 13:29:21.645] [DEBUG] - share lock /home/admin/.obd/lock/global, count 1
[2023-08-18 13:29:21.645] [DEBUG] - Get Deploy by name
[2023-08-18 13:29:21.645] [DEBUG] - mkdir /home/admin/.obd/cluster/
[2023-08-18 13:29:21.645] [DEBUG] - mkdir /home/admin/.obd/config_parser/
[2023-08-18 13:29:21.646] [DEBUG] - try to get exclusive lock /home/admin/.obd/lock/deploy_myoceanbase
[2023-08-18 13:29:21.646] [DEBUG] - exclusive lock /home/admin/.obd/lock/deploy_myoceanbase, count 1
[2023-08-18 13:29:21.658] [DEBUG] - Deploy status judge
[2023-08-18 13:29:21.658] [INFO] Get local repositories
…
[2023-08-18 13:34:18.545] [DEBUG] – connect 192.168.207.154 -P2883 -umeta@ocp -p7iP0j5aSoU
[2023-08-18 13:34:19.557] [DEBUG] – connect 192.168.207.154 -P2883 -umeta@ocp -p7iP0j5aSoU
[2023-08-18 13:34:20.565] [DEBUG] – connect 192.168.207.154 -P2883 -umeta@ocp -p7iP0j5aSoU
[2023-08-18 13:34:21.577] [DEBUG] – connect 192.168.207.154 -P2883 -umeta@ocp -p7iP0j5aSoU
[2023-08-18 13:34:22.584] [DEBUG] – connect 192.168.207.154 -P2883 -umeta@ocp -p7iP0j5aSoU
[2023-08-18 13:34:23.592] [DEBUG] – connect 192.168.207.154 -P2883 -umeta@ocp -p7iP0j5aSoU
[2023-08-18 13:34:24.605] [DEBUG] – connect 192.168.207.154 -P2883 -umeta@ocp -p7iP0j5aSoU
[2023-08-18 13:34:25.622] [DEBUG] – connect 192.168.207.154 -P2883 -umeta@ocp -p7iP0j5aSoU
[2023-08-18 13:34:26.633] [DEBUG] – connect 192.168.207.154 -P2883 -umeta@ocp -p7iP0j5aSoU
[2023-08-18 13:34:27.643] [DEBUG] – connect 192.168.207.154 -P2883 -umeta@ocp -p7iP0j5aSoU
[2023-08-18 13:34:28.655] [DEBUG] – connect 192.168.207.154 -P2883 -umeta@ocp -p7iP0j5aSoU
[2023-08-18 13:34:29.672] [DEBUG] – connect 192.168.207.154 -P2883 -umeta@ocp -p7iP0j5aSoU
[2023-08-18 13:34:30.680] [ERROR] 192.168.207.154: failed to connect meta db
[2023-08-18 13:34:30.777] [INFO] [ERROR] 192.168.207.154: failed to connect meta db
[2023-08-18 13:34:30.777] [INFO]
[2023-08-18 13:34:30.778] [DEBUG] - sub start ref count to 0
[2023-08-18 13:34:30.778] [DEBUG] - export start
[2023-08-18 13:34:30.778] [ERROR] ocp-express start failed
[2023-08-18 13:34:30.785] [INFO] See https://www.oceanbase.com/product/ob-deployer/error-codes .
[2023-08-18 13:34:30.786] [INFO] Trace ID: 2f79d864-3d88-11ee-bde3-722403f5b3f3
[2023-08-18 13:34:30.787] [INFO] If you want to view detailed obd logs, please run: obd display-trace 2f79d864-3d88-11ee-bde3-722403f5b3f3
[2023-08-18 13:34:30.787] [DEBUG] - share lock /home/admin/.obd/lock/mirror_and_repo release, count 3
[2023-08-18 13:34:30.787] [DEBUG] - share lock /home/admin/.obd/lock/mirror_and_repo release, count 2
[2023-08-18 13:34:30.787] [DEBUG] - share lock /home/admin/.obd/lock/mirror_and_repo release, count 1
[2023-08-18 13:34:30.788] [DEBUG] - share lock /home/admin/.obd/lock/mirror_and_repo release, count 0
[2023-08-18 13:34:30.788] [DEBUG] - unlock /home/admin/.obd/lock/mirror_and_repo
[2023-08-18 13:34:30.788] [DEBUG] - exclusive lock /home/admin/.obd/lock/deploy_myoceanbase release, count 0
[2023-08-18 13:34:30.788] [DEBUG] - unlock /home/admin/.obd/lock/deploy_myoceanbase
[2023-08-18 13:34:30.788] [DEBUG] - share lock /home/admin/.obd/lock/global release, count 0
[2023-08-18 13:34:30.788] [DEBUG] - unlock /home/admin/.obd/lock/global
使用新密码可登录：
[admin@ora01 ~]$ obclient -h192.168.207.154 -P2883 -umeta@ocp -pAAbb33@@ -A
Welcome to the OceanBase. Commands end with ; or \g.
Your OceanBase connection id is 305
Server version: OceanBase_CE 4.1.0.2 (r103000072023081111-694f84c4faf0067e2512e18ea2c9a3687fa013c7) (Built Aug 11 2023 11:38:01)
Copyright (c) 2000, 2018, OceanBase and/or its affiliates. All rights reserved.
Type ‘help;’ or ‘\h’ for help. Type ‘\c’ to clear the current input statement.
obclient [(none)]> alter use meta identified by 7iP0j5aSoU;
ERROR 1064 (42000): You have an error in your SQL syntax; check the manual that corresponds to your OceanBase version for the right syntax to use near ‘use meta identified by 7iP0j5aSoU’ at line 1
obclient [(none)]> use oceanbase;
Database changed
obclient [oceanbase]> alter use meta identified by 7iP0j5aSoU;
ERROR 1064 (42000): You have an error in your SQL syntax; check the manual that corresponds to your OceanBase version for the right syntax to use near ‘use meta identified by 7iP0j5aSoU’ at line 1
obclient [oceanbase]> set password for meta = password(‘7iP0j5aSoU’);
Query OK, 0 rows affected (0.462 sec)
obclient [oceanbase]> exit
Bye
修改为初始密码后在启动ob-express成功
60 history|grep start
[admin@ora01 ~]$ obd cluster start myoceanbase -c ocp-express
Get local repositories ok
Search plugins ok
Open ssh connection ok
Load cluster param plugin ok
Cluster status check ok
Check before start ocp-express ok
Start ocp-express ok
ocp-express program health check ok
Connect to ocp-express ok
±-------------------------------------------------------------------+
| ocp-express |
±----------------------------±---------±-----------------±-------+
| url | username | initial password | status |
±----------------------------±---------±-----------------±-------+
| http://192.168.207.154:8180 | admin | 5Z#3vwC) | active |
±----------------------------±---------±-----------------±-------+
succeed
Trace ID: 54cd2ccc-3d8a-11ee-9afd-722403f5b3f3
If you want to view detailed obd logs, please run: obd display-trace 54cd2ccc-3d8a-11ee-9afd-722403f5b3f3
[admin@ora01 ~]$
1 个赞
请问这个是用obclient联通后用sql改，还是直接修改配置文件？
改配置文件最稳妥。