Advertisement
kmajumder

Untitled

Apr 23rd, 2019
143
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 3.72 KB | None | 0 0
  1. [2019-04-10 10:50:00.350075] I [MSGID: 100030] [glusterfsd.c:2771:main] 0-/usr/sbin/glusterd: Started running /usr/sbin/glusterd version 6dev (args: /usr/sbin/glusterd -p /var/run/glusterd.pid --log-level INFO)
  2. [2019-04-10 10:50:00.353318] I [MSGID: 101097] [xlator.c:368:xlator_dynload_newway] 0-xlator: dlsym(xlator_api) on /usr/lib64/glusterfs/6dev/xlator/mgmt/glusterd.so: undefined symbol: xlator_api. Fall back to old symbols
  3. [2019-04-10 10:50:00.353643] I [MSGID: 106478] [glusterd.c:1422:init] 0-management: Maximum allowed open file descriptors set to 65536
  4. [2019-04-10 10:50:00.353664] I [MSGID: 106479] [glusterd.c:1478:init] 0-management: Using /var/lib/glusterd as working directory
  5. [2019-04-10 10:50:00.353671] I [MSGID: 106479] [glusterd.c:1484:init] 0-management: Using /var/run/gluster as pid file working directory
  6. [2019-04-10 10:50:00.358116] I [socket.c:931:__socket_server_bind] 0-socket.management: process started listening on port (24007)
  7. [2019-04-10 10:50:00.358243] E [rpc-transport.c:297:rpc_transport_load] 0-rpc-transport: /usr/lib64/glusterfs/6dev/rpc-transport/rdma.so: cannot open shared object file: No such file or directory
  8. [2019-04-10 10:50:00.358252] W [rpc-transport.c:301:rpc_transport_load] 0-rpc-transport: volume 'rdma.management': transport-type 'rdma' is not valid or not found on this machine
  9. [2019-04-10 10:50:00.358260] W [rpcsvc.c:1995:rpcsvc_create_listener] 0-rpc-service: cannot create listener, initing the transport failed
  10. [2019-04-10 10:50:00.358266] E [MSGID: 106244] [glusterd.c:1785:init] 0-management: creation of 1 listeners failed, continuing with succeeded transport
  11. [2019-04-10 10:50:00.359825] I [socket.c:902:__socket_server_bind] 0-socket.management: closing (AF_UNIX) reuse check socket 12
  12. [2019-04-10 10:50:02.454887] I [MSGID: 106513] [glusterd-store.c:2402:glusterd_restore_op_version] 0-glusterd: retrieved op-version: 31101
  13. [2019-04-10 10:50:02.598434] I [MSGID: 106544] [glusterd.c:152:glusterd_uuid_init] 0-management: retrieved UUID: e1254523-4dcc-4bdf-896c-1f39a780fc78
  14. [2019-04-10 10:50:02.599192] E [mem-pool.c:351:__gf_free] (-->/usr/lib64/glusterfs/6dev/xlator/mgmt/glusterd.so(+0x4d849) [0x7f05b5747849] -->/usr/lib64/glusterfs/6dev/xlator/mgmt/glusterd.so(+0x4d60d) [0x7f05b574760d] -->/lib64/libglusterfs.so.0(__gf_free+0x24e) [0x7f05c0e1a48e] ) 0-: Assertion failed: mem_acct->rec[header->type].size >= header->size
  15. [2019-04-10 10:50:02.601634] E [MSGID: 101032] [store.c:447:gf_store_handle_retrieve] 0-: Path corresponding to /var/lib/glusterd/vols/vmstore/bricks/10.70.37.28:-gluster_bricks-vmstore-vmstore. [No such file or directory]
  16. [2019-04-10 10:50:02.601676] E [MSGID: 106201] [glusterd-store.c:3650:glusterd_store_retrieve_volumes] 0-management: Unable to restore volume: vmstore
  17. [2019-04-10 10:50:02.601703] E [MSGID: 101019] [xlator.c:751:xlator_init] 0-management: Initialization of volume 'management' failed, review your volfile again
  18. [2019-04-10 10:50:02.601713] E [MSGID: 101066] [graph.c:362:glusterfs_graph_init] 0-management: initializing translator failed
  19. [2019-04-10 10:50:02.601719] E [MSGID: 101176] [graph.c:725:glusterfs_graph_activate] 0-graph: init failed
  20. [2019-04-10 10:50:02.601772] W [glusterfsd.c:1515:cleanup_and_exit] (-->/usr/sbin/glusterd(glusterfs_volumes_init+0xfd) [0x56456e121b0d] -->/usr/sbin/glusterd(glusterfs_process_volfp+0x255) [0x56456e1219f5] -->/usr/sbin/glusterd(cleanup_and_exit+0x6d) [0x56456e120dfd] ) 0-: received signum (-1), shutting down
  21. [2019-04-10 10:50:02.601802] W [mgmt-pmap.c:127:rpc_clnt_mgmt_pmap_signout] 0-glusterfs: failed to create XDR payload
  22. [2019-04-10 10:55:00.302347] I [MSGID: 100030] [glusterfsd.c:2771:main] 0-/usr/sbin/glusterd: Started running /usr/sbin/glusterd version 6dev (args: /usr/sbin/glusterd -p /var/run/glusterd.pid --log-level INFO)
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement