Received a message that is too large

19 views
Skip to first unread message

jont...@gmail.com

unread,
Jun 15, 2024, 8:10:52 AMJun 15
to beegfs-user
Hi, I have problems getting beegfs-7.4.2/7.4.3 to work on AlmLinux-9.3 on new hardware. Have previously gotten it to work on different set of machines.

In both cases I have one meta and four OSTs. When I try to write to the filesystem the client reports:

"Peer reported indirect communication error: beegfs-meta bond10 [ID: 1]; Reason: Communication with storage targets failed"

the storage writes:

"Worker7 [Work (process incoming msg)] >> Received a message that is too large. Disconnecting: 192.168.0.50:40906"

and the META:

"CommSlave15 [Messaging (RPC)] >> Failed to receive response from: beegfs-storage bond11 [ID: 1]; 192.168.0.51:8003. (Message type: SetLocalAttr (2033))

CommSlave12 [Messaging (RPC)] >> Communication error: Received disconnect from: 192.168.0.53:8003; Peer: beegfs-storage bond13 [ID: 3]. (Message type: SetLocalAttr (2033))"

beegfs-net:
"mgmt_nodes
=============
bond10 [ID: 1]
   Connections: TCP: 1 (192.168.0.50:8008);

meta_nodes
=============
bond10 [ID: 1]
   Connections: TCP: 1 (192.168.0.50:8005);

storage_nodes
=============
bond11 [ID: 1]
   Connections: TCP: 1 (192.168.0.51:8003);
bond12 [ID: 2]
   Connections: TCP: 1 (192.168.0.52:8003);
bond13 [ID: 3]
   Connections: TCP: 1 (192.168.0.53:8003);
bond14 [ID: 4]
   Connections: TCP: 1 (192.168.0.54:8003);"

Any hints on this one?

Thanks,
/jon
Reply all
Reply to author
Forward
0 new messages