Error: Unknown Storage Target in CentOS 7

126 views
Skip to first unread message

이재현

unread,
Dec 14, 2017, 12:06:47 AM12/14/17
to beegfs-user

I am running beeond on CentOS 7. If I run a signle beeond instance on a single node, beegfs-client is fine for mounting, but on multi-nodes the client refuse to mount. (In the case of CentOS 6, any problem occured.) When executed beeond starting commands, shell shows …


INFO: Starting beegfs-client on host: node1

mount: mount beegfs_ondemand on /mnt/beegfs failed: 

ERROR: Unable to start BeeGFS client on host: node1


and beegfs-client.log file is as follows…

....

(2) 11:51:19 *mount(105660) [Remoting (stat storage targets)] >> Error target (storage): 2; Msg: Unknown storage target

(0) 11:51:19 *mount(105660) [Mount sanity check] >> Retrieval of storage server free space info failed. Are the storage servers running and registered at the management daemon? Did you remove a storage target directory on a server? (Error: Unknown storage target)

(2) 11:51:19 *mount(105660) [App (stop components)] >> Stopping components...

(2) 11:51:19 *beegfs_XNodeSyn(105662) [Deregistration] >> Node deregistration successful.

(2) 11:51:21 *mount(105660) [App (wait for component termination)] >> Still waiting for this component to stop: beegfs_AckMgr

(2) 11:51:21 *mount(105660) [App (wait for component termination)] >> Component stopped: beegfs_AckMgr

(1) 11:51:21 *mount(105660) [App (stop)] >> All components stopped.



I think a line marked with a bold is a hint. Then I followed the solution suggested in https://www.beegfs.io/wiki/FAQ#unknown_storage_target . But the problem still occurs. There is no problem with centos6, but I have to use beegfs in centos7, so I need to fix this. Have you ever solved this problem?


guig...@gmail.com

unread,
Dec 18, 2017, 3:55:32 AM12/18/17
to beegfs-user
Hi, I am also trying beeond for myself, and found the same problem.

Are you testing under a VMware VM?
If so, you could check your NIC configurations, I passed this problem after I have the virbr0 iface down.

I don't known exactly why, but it seems to relate to NIC port listening, maybe beeond should have an option to let user select which NIC to listen on.

在 2017年12月14日星期四 UTC+8下午1:06:47,이재현写道:
Reply all
Reply to author
Forward
0 new messages