[WARN] OBD-4521: The config observer_sys_password in obproxy-ce did not take effect, please config it in oceanbase-ce

按照以下步骤操作试试:

  1. obclient -h192.168.146.27 -P2881 -uroot -p’Z:-}f!7z-c),RqjSv’ -Doceanbase -A
    登录后执行alter user proxyro identified by “NubeWTJtZj”;

  2. obclient -h192.168.146.27 -P2883 -uroot@proxysys -p’NubeWTJtZj’ -Doceanbase -A
    执行两条sql:
    alter proxyconfig set observer_sys_password=“NubeWTJtZj”;
    alter proxyconfig set observer_sys_password1=“NubeWTJtZj”;

  3. obd cluster start obtest

执行了您给的命令。现在提示[ERROR] 192.168.146.27: failed to connect meta db

[admin@obd-4231 log]$ obd cluster start obtest
Get local repositories ok
Search plugins ok
Load cluster param plugin ok
Open ssh connection ok
Check before start observer ok
Check before start obproxy ok
[WARN] OBD-4521: The config observer_sys_password in obproxy-ce did not take effect, please config it in oceanbase-ce

Check before start obagent ok
Check before start ocp-express ok
Start observer ok
observer program health check ok
obshell program health check ok
Connect to observer 192.168.146.27:2881 ok
Start obproxy ok
obproxy program health check ok
Connect to obproxy ok
Initialize obproxy-ce ok
Start obagent ok
obagent program health check ok
Connect to Obagent ok
Start ocp-express x
[ERROR] 192.168.146.27: failed to connect meta db

[ERROR] ocp-express start failed
Wait for observer init ok
±-------------------------------------------------+
| observer |
±---------------±--------±-----±------±-------+
| ip | version | port | zone | status |
±---------------±--------±-----±------±-------+
| 192.168.146.27 | 4.2.4.0 | 2881 | zone1 | ACTIVE |
±---------------±--------±-----±------±-------+
obclient -h192.168.146.27 -P2881 -uroot -p’Z:-}f!7z-c),RqjSv’ -Doceanbase -A

cluster unique id: 9241407d-07ae-5648-91be-1ccd318afb5d-190cbd4ee56-00040204

±-------------------------------------------------+
| obproxy |
±---------------±-----±----------------±-------+
| ip | port | prometheus_port | status |
±---------------±-----±----------------±-------+
| 192.168.146.27 | 2883 | 2884 | active |
±---------------±-----±----------------±-------+
obclient -h192.168.146.27 -P2883 -uroot@proxysys -p’NubeWTJtZj’ -Doceanbase -A

±------------------------------------------------------------------+
| obagent |
±---------------±-------------------±-------------------±-------+
| ip | mgragent_http_port | monagent_http_port | status |
±---------------±-------------------±-------------------±-------+
| 192.168.146.27 | 8089 | 8088 | active |
±---------------±-------------------±-------------------±-------+
See OceanBase分布式数据库-海量数据 笔笔算数 .
Trace ID: d50ad004-48d0-11ef-a4d1-000c291dacdb
If you want to view detailed obd logs, please run: obd display-trace d50ad004-48d0-11ef-a4d1-000c291dacdb
[admin@obd-4231 log]$ obd cluster list
±-----------------------------------------------------------+
| Cluster List |
±-------±--------------------------------±----------------+
| Name | Configuration Path | Status (Cached) |
±-------±--------------------------------±----------------+
| obtest | /home/admin/.obd/cluster/obtest | stopped |
±-------±--------------------------------±----------------+
Trace ID: c99c5980-48d1-11ef-9803-000c291dacdb
If you want to view detailed obd logs, please run: obd display-trace c99c5980-48d1-11ef-9803-000c291dacdb
[admin@obd-4231 log]$

obproxy.zip (1.8 MB)
obproxy_error.log (445.1 KB)

借用下obdiag工具查一下问题在哪吧

  1. 使用obdiag巡检下日志
  2. obdiag check 巡检
  3. obdiag analyze log 日志分析
  4. obdiag gather scene run --scene=observer.unknown 未知问题信息采集回来

obdiag文档:OceanBase分布式数据库-海量数据 笔笔算数1

把巡检结果和日志分析结果先发出来,定位不了再把3收集的信息发出来

check_report.zip (2.0 KB)

election.7z (3.9 MB)
observer.7z (581.1 KB)
observer.log.20240723202010887.7z (9.9 MB)
observer.log.20240723204302562.7z (9.9 MB)
observer.log.wf.7z (1.0 KB)
rootservice.7z (8.6 MB)

swapon: command not found。 命令不存在,还有27节点的data路径跟log路径也不存在

我检查过路径,data和redo路径肯定是在的,没有这俩路径,也能启动吗?

看样子可能是meta db密码问题,试一下这样能否连上
obclient -h192.168.146.27 -P2881 -umeta@ocp_meta -pc5B989Vesj

同时再验证一下obclient -h192.168.146.27 -P2881 -uproxyro@sys -p’Z:-}f!7z-c),RqjSv’能否连上证明密码修改成功了

obclient -h192.168.146.27 -P2883 -uroot -p’Z:-}f!7z-c),RqjSv’ -Doceanbase -A如果这个连不上,大概率proxyro的密码问题

我重新装了个 ob 4.2.4 的三节点集群。启动是也提示 OBD-4521: The config observer_sys_password in obproxy-ce did not take effect, please config it in oceanbase-ce

但是 ocp 是启动成功的。

我用您给的这俩语句去连,也是联不通的。

[admin@obd ~]$ mysql -h192.168.146.21 -uproxyro@sys -P2881 -p’bkKvhFZAMw’ -A
ERROR 1045 (42000): Access denied for user ‘proxyro’@‘xxx.xxx.xxx.xxx’ (using password: YES)
[admin@obd ~]$ mysql -h192.168.146.21 -uproxyro@sys -P2881 -p’J[;Lz~N.n*!=K’ -A
ERROR 1045 (42000): Access denied for user ‘proxyro’@‘xxx.xxx.xxx.xxx’ (using password: YES)

白屏化安装的么,安装时候的proxyro用户密码有设置么

我查了一下没有ocp_meta 租户,只有ocp租户,obclient -h192.168.146.27 -P2881 -umeta@ocp -pc5B989Vesj 将ocp_meta 改成ocp 是可以连通的。

但是我新装的v 4.2.4 版本的3节点集群是有 ocp_meta 租户的。难道是单机版本的没有吗?我单机版本的是从 v 4.2.3版本升级到 v 4.2.4的

是obd白屏装的,proxyro 用户的密码不用我设置啊,它安装好自动生成的,我把信息复制保留下来了

root@sys/Z:-}f!7z-c),RqjSv

OceanBase DataBase obclient -h192.168.146.27 -P2881 -uroot -p’Z:-}f!7z-c),RqjSv’ -Doceanbase -A

OBProxy obclient -h192.168.146.27 -P2883 -uroot@proxysys -p’NubeWTJtZj’ -Doceanbase -A

OCP Express http://192.168.146.27:8180

[

{

“component”: “oceanbase-ce”,

“access_url”: “192.168.146.27:2881”,

“user”: “root”,

“password”: “Z:-}f!7z-c),RqjSv”,

“connect_url”: “obclient -h192.168.146.27 -P2881 -uroot -p’Z:-}f!7z-c),RqjSv’ -Doceanbase -A”

},

{

“component”: “obproxy-ce”,

“access_url”: “192.168.146.27:2883”,

“user”: “root@proxysys”,

“password”: “NubeWTJtZj”,

“connect_url”: “obclient -h192.168.146.27 -P2883 -uroot@proxysys -p’NubeWTJtZj’ -Doceanbase -A \n”

},

{

“component”: “ocp-express”,

“access_url”: “192.168.146.27:8180”,

“user”: “admin”,

“password”: “L@v6O.8t”,

“connect_url”: “http://192.168.146.27:8180

}
]

我刚才查了下之前设置的内存,感觉有点小了
image
麻烦给一下这次的内存配置

这个和内存没啥关系吧,我刚看了一下,集群和单机版本内存给的都是8G

这是 今天装的 三节点的配置

[admin@obd ~]$ obd cluster edit-config obtest
Search param plugin and load ok

user:
username: admin
password: admin
port: 22
oceanbase-ce:
version: 4.2.4.0
release: 100000082024070810.el7
package_hash: 7dc8b049b3283ef4660cdf6e3cfa24f81e9d2a78
192.168.146.21:
zone: zone1
192.168.146.22:
zone: zone2
192.168.146.23:
zone: zone3
servers:

  • 192.168.146.21
  • 192.168.146.22
  • 192.168.146.23
    global:
    appname: obtest
    root_password: J[;Lz~N.n*!=K
    mysql_port: 2881
    rpc_port: 2882
    data_dir: /data
    redo_dir: /redo
    home_path: /home/admin/oceanbase/obtest/oceanbase
    cluster_id: 1721802786
    enable_syslog_recycle: true
    enable_syslog_wf: false
    max_syslog_file_count: 4
    memory_limit: 6144M
    datafile_size: 18432M
    system_memory: 2048M
    log_disk_size: 18432M
    cpu_count: 16
    production_mode: false
    datafile_maxsize: 185G
    datafile_next: 18957M
    ocp_agent_monitor_password: LXRvJawBkS
    proxyro_password: g6ct9kDGMp
    ocp_root_password: uA3Hvxj926
    ocp_meta_password: TeqnBaCHdb
    depends:
  • ob-configserver
    obproxy-ce:
    version: 4.2.3.0
    package_hash: 0490ebc04220def8d25cb9cac9ac61a4efa6d639
    release: 3.el7
    servers:
  • 192.168.146.21
  • 192.168.146.22
  • 192.168.146.23
    global:
    prometheus_listen_port: 2884
    listen_port: 2883
    home_path: /home/admin/oceanbase/obtest/obproxy
    obproxy_sys_password: bkKvhFZAMw
    skip_proxy_sys_private_check: true
    enable_strict_kernel_release: false
    enable_cluster_checkout: false
    rs_list: 192.168.146.21:2881;192.168.146.22:2881;192.168.146.23:2881
    observer_sys_password: g6ct9kDGMp
    cluster_name: obtest
    observer_root_password: J[;Lz~N.n*!=K
    192.168.146.21:
    proxy_id: 5919
    client_session_id_version: 2
    192.168.146.22:
    proxy_id: 5920
    client_session_id_version: 2
    192.168.146.23:
    proxy_id: 5921
    client_session_id_version: 2
    depends:
  • oceanbase-ce
  • ob-configserver
    obagent:
    version: 4.2.2
    package_hash: 19739a07a12eab736aff86ecf357b1ae660b554e
    release: 100000042024011120.el7
    servers:
  • 192.168.146.21
  • 192.168.146.22
  • 192.168.146.23
    global:
    monagent_http_port: 8088
    mgragent_http_port: 8089
    home_path: /home/admin/oceanbase/obtest/obagent
    http_basic_auth_password: h5d8eE1CZ
    ob_monitor_status: active
    depends:
  • oceanbase-ce
    ocp-express:
    version: 4.2.2
    package_hash: 09ffcf156d1df9318a78af52656f499d2315e3f7
    release: 100000022024011120.el7
    servers:
  • 192.168.146.21
    global:
    port: 8180
    home_path: /home/admin/oceanbase/obtest/ocpexpress
    admin_passwd: 1@AepP5@
    ocp_root_password: 5.1up(NX
    memory_size: 872M
    depends:
  • obagent
  • oceanbase-ce
  • obproxy-ce
    ob-configserver:
    version: 1.0.0
    release: 2.el7
    servers:
  • 192.168.146.21
    global:
    listen_port: 8080
    home_path: /home/admin/oceanbase/obtest/obconfigserver

我看单机版的 obproxy_error.log 日志一直报这个

2024-07-24 16:16:47.936765,undefined,obtest:ocp_meta:,OB_MYSQL,OB_MYSQL_COM_LOGIN,failed,-4016,820us,0us,0us,0us,Y0-00002AAEF7A44650,192.168.146.26:42816,0,Internal error,
2024-07-24 16:16:48.941254,undefined,obtest:ocp_meta:,OB_MYSQL,OB_MYSQL_COM_LOGIN,failed,-4016,1198us,0us,0us,0us,Y0-00002AAEF896A650,192.168.146.26:42818,0,Internal error,
2024-07-24 16:16:49.945886,undefined,obtest:ocp_meta:,OB_MYSQL,OB_MYSQL_COM_LOGIN,failed,-4016,1618us,0us,0us,0us,Y0-00002AAEF7A44650,192.168.146.26:42820,0,Internal error,
2024-07-24 16:16:50.949898,undefined,obtest:ocp_meta:,OB_MYSQL,OB_MYSQL_COM_LOGIN,failed,-4016,846us,0us,0us,0us,Y0-00002AAEF896A650,192.168.146.26:42822,0,Internal error,
2024-07-24 16:16:51.953755,undefined,obtest:ocp_meta:,OB_MYSQL,OB_MYSQL_COM_LOGIN,failed,-4016,1125us,0us,0us,0us,Y0-00002AAEF7A44650,192.168.146.26:42824,0,Internal error,
2024-07-24 16:16:52.957589,undefined,obtest:ocp_meta:,OB_MYSQL,OB_MYSQL_COM_LOGIN,failed,-4016,865us,0us,0us,0us,Y0-00002AAEF896A650,192.168.146.26:42826,0,Internal error,
2024-07-24 16:16:53.963431,undefined,obtest:ocp_meta:,OB_MYSQL,OB_MYSQL_COM_LOGIN,failed,-4016,1225us,0us,0us,0us,Y0-00002AAEF7A44650,192.168.146.26:42828,0,Internal error,

再详细描述一下之前start失败的步骤呢,我这边手动复现一下,
按理说升级ob后,集群状态是running,不需要start,中间是不是有其它步骤或者start前有步骤失败了

  1. 用 oceanbase-all-in-one-4.2.3.0-100000112024042411.el7.x86_64.tar.gz 包 安装部署 ob 单机。

  2. 将 oceanbase-all-in-one-4.2.4.0-100000082024070810.el7.x86_64.tar.gz 包 中的 oceanbase rpm包 加载到第一步安装的obd 本地镜像中。

  3. 升级ob
    obd cluster upgrade obtest -c oceanbase-ce -V 4.2.4.0 --usable=eda524874ce5daff6685f114bd28965b8c1834ef

  4. 验证
    – 使用 root 用户登录 OceanBase 数据库的 sys 租户,执行如下命令查看数据库版本。
    obclient -h192.168.146.27 -P2881 -uroot -p’Z:-}f!7z-c),RqjSv’ -Doceanbase -A
    SELECT version();

  5. 升级 obd 2.8 到 2.9.2

5.1 检查当前 obd 版本
obd --version

5.2 将第二步中的 obdrpm包装载到本地镜像库中
obd mirror clone ob-deploy-*.rpm

5.3 查询本地镜像库版本
obd mirror list local | grep ob-deploy

5.4 升级obd
obd update

5.6 检查obd版本
obd --version

  1. 第二天,打开虚拟机,obd 启动单机版ob
    obd cluster start obtest

启动时 提示 [[WARN] OBD-4521: The config observer_sys_password in obproxy-ce did not take effect, please config it in oceanbase-ce

启动截图与截图1一致

  1. 按您昨天说的,修改密码
    按照以下步骤操作试试:

  2. obclient -h192.168.146.27 -P2881 -uroot -p’Z:-}f!7z-c),RqjSv’ -Doceanbase -A
    登录后执行alter user proxyro identified by “NubeWTJtZj”;

  3. obclient -h192.168.146.27 -P2883 -uroot@proxysys -p’NubeWTJtZj’ -Doceanbase -A
    执行两条sql:
    alter proxyconfig set observer_sys_password=“NubeWTJtZj”;
    alter proxyconfig set observer_sys_password1=“NubeWTJtZj”;

  4. obd cluster start obtest

多了一个[ERROR] 192.168.146.27: failed to connect meta db 报错,参考截图2

昨天发现执行 obd cluster start obtest 命令后,在执行
obd cluster display obtest 结果提示 obtest 状态是 stop,但是我在observer上看到ob进程是存在的,并且在obd 中控机中,使用obclient -h192.168.146.27 -P2883 -uroot -p’Z:-}f!7z-c),RqjSv’ -Doceanbase -A 命令可以登录到ob中进行操作。

参考一下操作日志,可以用note ++ 之类的软件打开查看格式会整齐一些。
操作日志.txt (8.5 KB)