碉堡的問題：(59) access to the client was not allowed

ZoneJ

傷了，最近遇到個碉堡的問題，機器是MediaServer，測試備份自身/tmp文件時報59錯誤，而且測試了其他的備份情況，只有自身的SAN備份時出現了這種狀況，截個圖：




命令檢測：
nburestore1/usr/openv/netbackup/bin/admincmd#./bptestbpcd -client nburestore1 -debug
11:09:18.954 [5701962] <2> bptestbpcd: VERBOSE = 5
11:09:19.039 [5701962] <2> init_cache: vnet_hosts.c.1045: host_cache_size: 200 0x000000c8
11:09:19.040 [5701962] <2> init_cache: vnet_hosts.c.1046: cache_time: 3600 0x00000e10
11:09:19.040 [5701962] <2> init_cache: vnet_hosts.c.1060: host_failed_cache_size: 40 0x00000028
11:09:19.040 [5701962] <2> init_cache: vnet_hosts.c.1061: cache_time: 3600 0x00000e10
11:09:19.046 [5701962] <2> init_cache: vnet_hosts.c.1045: host_cache_size: 200 0x000000c8
11:09:19.046 [5701962] <2> init_cache: vnet_hosts.c.1046: cache_time: 3600 0x00000e10
11:09:19.046 [5701962] <2> init_cache: vnet_hosts.c.1060: host_failed_cache_size: 40 0x00000028
11:09:19.046 [5701962] <2> init_cache: vnet_hosts.c.1061: cache_time: 3600 0x00000e10
11:09:19.052 [5701962] <2> vnet_async_connect: vnet_vnetd.c.4039: connect in progress: 0 0x00000000
11:09:19.082 [5701962] <2> vnet_vnetd_service_socket: vnet_vnetd.c.2048: VN_REQUEST_SERVICE_SOCKET: 6 0x00000006
11:09:19.082 [5701962] <2> vnet_vnetd_service_socket: vnet_vnetd.c.2062: service: bpdbm
11:09:19.247 [5701962] <2> vnet_async_connect: vnet_vnetd.c.4225: in progress connect: 0 0x00000000
11:09:19.247 [5701962] <2> vnet_async_connect: vnet_vnetd.c.4228: connect: async CONNECT FROM 192.168.155.23.40933 TO 192.168.130.176.13724 fd = 3
11:09:19.247 [5701962] <2> logconnections: BPDBM CONNECT FROM 192.168.155.23.40933 TO 192.168.130.176.13724
11:09:19.247 [5701962] <2> vauth_get_user_name: vauth_comm.c.687: cached_user_name: root
11:09:19.248 [5701962] <2> vauth_get_user_name: vauth_comm.c.689: cached_user_name: :root
11:09:19.248 [5701962] <2> vauth_get_user_name: vauth_comm.c.695: user_name: :root
11:09:19.248 [5701962] <2> vauth_authentication_required: vauth_comm.c.749: no methods for address: no authentication required
11:09:19.248 [5701962] <2> vauth_connector: vauth_comm.c.182: no methods for address: no authentication required
11:09:19.248 [5701962] <2> check_authentication: no authentication required
11:09:19.249 [5701962] <2> vnet_check_vxss_client_magic_with_info: vnet_vxss_helper.c.770: Ignoring VxSS authentication: 2 0x00000002
11:09:19.249 [5701962] <2> vnet_check_vxss_client_magic_with_info: vnet_vxss_helper.c.926: Not using VxSS authentication: 2 0x00000002
11:09:19.649 [5701962] <2> db_getCLIENT: db_CLIENTreceive: no entity was found 227
11:09:19.650 [5701962] <2> ConnectToBPCD: db_getCLIENT(nburestore1) failed: 227
11:09:19.655 [5701962] <2> local_bpcr_connect: bpcr.c.276: connect_opts = 0x01000100 connect_opts2 = 0x01000100
11:09:19.655 [5701962] <2> local_bpcr_connect: bpcr.c.283: connect_opts = 0x01000100
11:09:19.656 [5701962] <2> local_bpcr_connect: bpcr.c.322: daemon_port_type = 0
11:09:19.685 [5701962] <2> vnet_vnetd_service_socket: vnet_vnetd.c.2048: VN_REQUEST_SERVICE_SOCKET: 6 0x00000006
11:09:19.685 [5701962] <2> vnet_vnetd_service_socket: vnet_vnetd.c.2062: service: bpcd
11:09:19.800 [5701962] <2> vnet_async_connect: vnet_vnetd.c.3992: immediate connect: 0 0x00000000
11:09:19.800 [5701962] <2> vnet_async_connect: vnet_vnetd.c.3995: connect: immediate CONNECT FROM 192.168.155.23.38062 TO 192.168.155.23.13724 fd = 3
11:09:19.800 [5701962] <2> logconnections: BPCD CONNECT FROM 192.168.155.23.38062 TO 192.168.155.23.13724
11:09:19.801 [5701962] <2> vauth_authentication_required: vauth_comm.c.749: no methods for address: no authentication required
11:09:19.801 [5701962] <2> vauth_connector: vauth_comm.c.182: no methods for address: no authentication required
11:09:19.801 [5701962] <2> bpcr_authenticate_connection: no authentication required
11:09:19.801 [5701962] <2> vnet_connect_to_vnetd_extra: vnet_vnetd.c.182: msg: VNETD CONNECT FROM 192.168.155.23.53731 TO 192.168.155.23.13724 fd = 4
11:09:19.824 [5701962] <2> vnet_vnetd_connect_forward_socket_begin: vnet_vnetd.c.535: VN_REQUEST_CONNECT_FORWARD_SOCKET: 10 0x0000000a
11:09:20.017 [5701962] <2> vnet_vnetd_connect_forward_socket_begin: vnet_vnetd.c.552: ipc_string: /tmp/vnet-12172372648160000398000000000-X6awMa
11:09:20.200 [5701962] <2> vnet_vnetd_connect_forward_socket_begin: vnet_vnetd.c.563: hash_str1: d0059af814ffd45ec78f8c27ba6f918b
11:09:20.203 [5701962] <2> ConnectToBPCD: bpcd_connect_and_verify(nburestore1, nburestore1) failed: 46
<16>bptestbpcd main: Function ConnectToBPCD(nburestore1) failed: 46
11:09:20.204 [5701962] <16> bptestbpcd main: Function ConnectToBPCD(nburestore1) failed: 46
<2>bptestbpcd: server not allowed access
11:09:20.204 [5701962] <2> bptestbpcd: server not allowed access
<2>bptestbpcd: EXIT status = 46
11:09:20.204 [5701962] <2> bptestbpcd: EXIT status = 46
server not allowed access

檢查過bp.conf文件hosts文件確定過都沒問題，NBU的軟件也重裝過，悲催的仍然是59錯誤，，，急，請各位大俠指點迷津！

無牙

用bptestbpcd先測試一下

ZoneJ

回復 2# 無牙


    恩，檢測如上~

ZoneJ

回復 2# 無牙


    nburestore1/usr/openv/netbackup/bin/admincmd#./bptestbpcd
<16>bptestbpcd main: Function ConnectToBPCD(nburestore1) failed: 46
server not allowed access

無牙

nburestore1是哪個IP?
192.168.155.23

192.168.130.176

ZoneJ

回復 5# 無牙


    解決了，是這個系統原來配置過域名解析，系統重裝后有殘留，現在把/etc/resolv.conf這個文件刪了就好了~QQQ!

無牙

呵呵，解決就好！

w3wu

雖然解決了，可是。。。不是應該優(yōu)先用hosts的嘛？

ZoneJ

回復 8# w3wu


    我也不大明白，hosts里面的配置的確沒問題，但是測試一直不成功，后來把那個文件刪掉就OK了~

w3wu

可能是nsswitch.conf里hosts查詢次序設置問題。