# Warn nfs/rpc.go - multifragment rpc message in logs

**URL:** <https://discuss.elastic.co/t/warn-nfs-rpc-go-multifragment-rpc-message-in-logs/346743>\
**Category:** Beats\
**Tags:** packetbeat\
**Created:** [November 8, 2023, 8:38pm UTC](https://discuss.elastic.co/t/warn-nfs-rpc-go-multifragment-rpc-message-in-logs/346743 "2023-11-08T20:38:17Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![tomaskcz](https://avatars.discourse-cdn.com/v4/letter/t/7bcc69/32.png) [@tomaskcz](https://discuss.elastic.co/u/tomaskcz)\
**Post date:** [November 8, 2023, 8:38pm UTC](https://discuss.elastic.co/t/warn-nfs-rpc-go-multifragment-rpc-message-in-logs/346743/1 "2023-11-08T20:38:17Z")

</div>

I am getting lots of logs messages for packebeat with

`{"log.level":"warn","@timestamp":"2023-11-08T20:27:29.998Z","log.origin":{"file.name":"nfs/rpc.go","file.line":227},"message":"multifragment rpc message","service.name":"packetbeat","ecs.version":"1.6.0"}`

I get also lots of nfs":{"unmatched\_requests":}.

I cannot find any relevant information.

Does it mean it is not supported for NFS protocol monitoring ?

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [December 6, 2023, 10:38pm UTC](https://discuss.elastic.co/t/warn-nfs-rpc-go-multifragment-rpc-message-in-logs/346743/2 "2023-12-06T22:38:43Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.