在新的服务器上命令行安装obproxy无法启动


【 使用环境 】测试环境
【 OB or 其他组件 】obproxy-ce
【 使用版本 】4.2.3.0
【问题描述】部署方式:使用rpm安装obproxy-ce-4.2.3.0-3.el8.x86_64.rpm,安装完成后路径是在/home/admin/obproxy-4.2.3.0,然后将该目录复制到oceanbase的home_path,根据官网说明,使用启动命令
./bin/obproxy -p 2883 -r ‘10.252.210.161:2881;10.252.210.163:2881;10.252.210.164:2881;10.252.210.165:2881;10.252.210.166:2881’ -o observer_sys_password=7e709441c42630f943a863d8bdf67a4278a796a9,obproxy_sys_password=8f2aba9e6e0303689d933fd5972661de822c7eb3,enable_cluster_checkout=false -n sfjh-obcluster进行启动,但是无法启动。
【复现路径】问题出现前后相关操作
【附件及日志】启动的相关日志如下:
[2024-05-24 15:04:00.381637] INFO [PROXY] init_log (ob_proxy_main.cpp:598) [3192685][Y0-0000000000000000] [lt=0] [dc=0] succ to init logger(max_log_file_size=268435456, async_tid=140529585354496)
[2024-05-24 15:04:00.381720] INFO open (ob_file.cpp:59) [3192685][Y0-0000000000000000] [lt=0] [dc=0] open fname=[/dev/urandom] fd=16 flags=0 succ
[2024-05-24 15:04:00.382413] INFO [PROXY] start (ob_proxy_main.cpp:492) [3192685][Y0-0000000000000000] [lt=0] [dc=0] ObProxy-OceanBase 4.2.3.0-3.el8-1-local-301841698608231dcec7a7a8b033ee9600ad874e
[2024-05-24 15:04:00.382428] INFO [PROXY] start (ob_proxy_main.cpp:497) [3192685][Y0-0000000000000000] [lt=0] [dc=0] has no inherited sockets, start new obproxy((info={is_inherited:false, upgrade_version:-1, need_conn_accept:true, user_rejected:0, ipv4_fd:-1, ipv6_fd:-1, received_sig:-1, sub_pid:-1, graceful_exit_end_time:0, graceful_exit_start_time:0, active_client_vc_count:-1, local_addr:, rc_status:"", hu_cmd:"", state:“HU_STATE_WAIT_HU_CMD”, hu_status:"", is_parent:true, sub_status:"", last_parent_status:"", last_sub_status:"", upgrade_version_buf:"", argc:9, argv[0]="./bin/obproxy", argv[1]="-p", argv[2]=“2883”, argv[3]="-r", argv[4]=“10.252.210.161:2881;10.252.210.163:2881;10.252.210.164:2881;10.252.210.165:2881;10.252.210.166:2881”, argv[5]="-o", argv[6]=“observer_sys_password=,obproxy_sys_password=,enable_cluster_checkout=false”, argv[7]="-n", argv[8]=“sfjh-obcluster”, inherited_argv[0]="./bin/obproxy", inherited_argv[1]="(null)", inherited_argv[2]="(null)", inherited_argv[3]="(null)"})
[2024-05-24 15:04:00.395920] INFO [PROXY] init_local_config (ob_proxy.cpp:668) [3192685][Y0-0000000000000000] [lt=0] [dc=0] fail to load config from file, but we can get the config from OCP by sql later(ret=0)
[2024-05-24 15:04:00.395940] INFO [SHARE] add_config (ob_common_config.cpp:135) [3192685][Y0-0000000000000000] [lt=0] [dc=0] Load config succ(name=“observer_sys_password”, value=“7e709441c42630f943a863d8bdf67a4278a796a9”)
[2024-05-24 15:04:00.395945] INFO [SHARE] add_config (ob_common_config.cpp:135) [3192685][Y0-0000000000000000] [lt=0] [dc=0] Load config succ(name=“obproxy_sys_password”, value=“8f2aba9e6e0303689d933fd5972661de822c7eb3”)
[2024-05-24 15:04:00.395952] INFO [SHARE] add_config (ob_common_config.cpp:135) [3192685][Y0-0000000000000000] [lt=0] [dc=0] Load config succ(name=“enable_cluster_checkout”, value=“false”)
[2024-05-24 15:04:00.396047] WDIAG [PROXY] get_kernel_release_by_uname (ob_config_server_processor.cpp:1082) [3192685][Y0-0000000000000000] [lt=0] [dc=0] unknown uname release(u_info.release=“4.19.0-240.23.21.el8_2.bclinux.x86_64”, ret=-4016)
[2024-05-24 15:04:00.396053] WDIAG [PROXY] init_proxy_kernel_release (ob_config_server_processor.cpp:1195) [3192685][Y0-0000000000000000] [lt=0] [dc=0] fail to get_kernel_release_by_uname(ret=-4016)
[2024-05-24 15:04:00.396056] WDIAG [PROXY] init (ob_config_server_processor.cpp:122) [3192685][Y0-0000000000000000] [lt=0] [dc=0] fail to init proxy kernel release(ret=-4016)
[2024-05-24 15:04:00.396058] EDIAG [PROXY] init_conn_pool (ob_proxy.cpp:614) [3192685][Y0-0000000000000000] [lt=0] [dc=0] fail to init config server processor(ret=-4016) BACKTRACE:0x211c73 0x1f300a 0x1b6a36 0x484fc5 0x48508c 0x485442 0x46965f 0x46f57b 0x19cdc4 0x7fcf9d8f36a3 0x1b1fde
[2024-05-24 15:04:00.396099] WDIAG [PROXY] init_config (ob_proxy.cpp:851) [3192685][Y0-0000000000000000] [lt=0] [dc=0] fail to init connection pool(ret=-4016)
[2024-05-24 15:04:00.396102] EDIAG [PROXY] init (ob_proxy.cpp:178) [3192685][Y0-0000000000000000] [lt=0] [dc=0] fail to init config(ret=-4016) BACKTRACE:0x211c73 0x1f300a 0x1b6a36 0x4857c2 0x46965f 0x46f57b 0x19cdc4 0x7fcf9d8f36a3 0x1b1fde
[2024-05-24 15:04:00.396114] WDIAG [PROXY] init (ob_proxy.cpp:238) [3192685][Y0-0000000000000000] [lt=0] [dc=0] fail to init obproxy(ret=-4016)
[2024-05-24 15:04:00.396117] EDIAG [PROXY] do_start_work (ob_proxy_main.cpp:704) [3192685][Y0-0000000000000000] [lt=0] [dc=0] obproxy init failed(ret=-4016) BACKTRACE:0x211c73 0x1f300a 0x1b6a36 0x469855 0x46f57b 0x19cdc4 0x7fcf9d8f36a3 0x1b1fde

obproxy [OPTIONS]
[2024-05-24 15:04:00.396140] EDIAG [PROXY] start (ob_proxy_main.cpp:500) [3192685][Y0-0000000000000000] [lt=0] [dc=0] fail to do start work(ret=-4016) BACKTRACE:0x211c73 0x1f300a 0x1b6a360x46f845 0x19cdc4 0x7fcf9d8f36a3 0x1b1fde
-h,–help print this help
-p,–listen_port LPORT obproxy listen port
-l,–promethues_listen_port PLPORT obproxy prometheus listen port
-o,–optstr OPTSTR extra options string
-n,–appname APPNAME application name
-r,–rs_list RS_LIST root server list(format ip:sql_port)
-c,–cluster_name CLUSTER_NAME root server cluster name
-d,–dump_config_sql DSQL dump config sql to file
-e,–execute_config_sql ESQL exectue config sql(create tables, insert initial data)
-N,–nodaemon don’t run in daemon
-V,–version VERSION current obproxy version
-R,–releaseid RELEASEID current obproxy kernel release id
-t,–regression_test TEST_NAME regression test
example:
run without config server:
./bin/obproxy -p6789 -r’ip:port;ip:port’ -n test -o enable_cluster_checkout=false,syslog_level=INFO
OR ./bin/obproxy -p6789 -r’ip:port;ip:port’ -c ‘ob_test’ -n test -o syslog_level=INFO

run with config server:
./bin/obproxy -p6789 -e -n test -o obproxy_config_server_url=‘your config url’,syslog_level=INFO

Non-first start with local config file:
./bin/obproxy

dump config update sql:
./bin/obproxy -d

run regression tests:
./bin/obproxy -p6789 -rip:port -ntest -o obproxy_config_server_url=’’ -t ‘’

【SOP系列 22 】——故障诊断第一步(自助诊断和诊断信息收集)

启动参数带上 -o enable_strict_kernel_release=false 试试

感谢,就是这个参数,加上就启动成功了。现在也可以使用obproxyd.sh脚本来进行启停和退出自动拉起了。
感觉文档很多和实际的对不上,希望能不断更新文档。

麻烦提供下文档呢。

我是参照官方文档来的。

使用上面的方式部署的obproxy有个问题,不能使用账号root@proxysys登陆,会提示账号权限问题: