[Nfd-dev] Fwd: [Operators] "No buffer space available"

Davide Pesavento davide.pesavento at lip6.fr
Tue Sep 5 09:34:24 PDT 2017


John,

On Tue, Sep 5, 2017 at 4:59 PM, Dehart, John <jdd at wustl.edu> wrote:
> All:
>
> (Moving this to nfd-dev)
>
> Seems like we are having a lot of FATAL errors and other issues with the
> current installation.

When did the instabilities start? Was anything updated recently?

>
> I am seeing this error on the CSU node right now.
>
> ndnops at mccoy:~$ nfdc status show
> error while connecting to the forwarder (No buffer space available)

"No buffer space available" is ENOBUFS, I believe, which could mean
that the socket buffers are full.

> ndnops at mccoy:~$
>
>
> I have also had the following error on UCLA recently:
>
> 1504524817.021009 FATAL: [NFD] std::bad_alloc
>
>
> I’m also investigating other nodes that have restarted in the last couple of
> days.
>
> I am about to install a scheme for running the nodes in the Testbed in DEBUG
> and when nfd
> restarts, capture the current set of nfd.log files. I have nfd.log being
> rotated and am only saving
> the last 10 copies of 10MB each. So, they can disappear fairly quickly with
> DEBUG turned on.
> But with my scheme I should be able to save copies of anything FATAL that
> happened recently.
> I’ll also be collecting ‘nfdc face list’ info so we can know what faces were
> pointing where when
> something FATAL happened.
>
> I’m open to other suggestions.
>
> John
>
>
> Begin forwarded message:
>
> From: Junxiao Shi <shijunxiao at email.arizona.edu>
> Subject: [Operators] "No buffer space available"
> Date: September 5, 2017 at 12:06:46 AM CDT
> To: "<operators at lists.named-data.net>" <operators at lists.named-data.net>
>
> Dear folks
>
> ARIZONA node is not working at the moment. `nfdc status` gives error:
> error while connecting to the forwarder (No buffer space available)
>
> The error went away when I restart NFD. However, I wonder what does this
> error message mean? I've never seen it.
> Neither system memory nor disk space was full, and there wasn't high CPU
> usage.
>
> Yours, Junxiao
> _______________________________________________
> Operators mailing list
> Operators at lists.named-data.net
> http://lists.named-data.net/mailman/listinfo/operators
>
>
>
> _______________________________________________
> Nfd-dev mailing list
> Nfd-dev at lists.cs.ucla.edu
> http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev
>


More information about the Nfd-dev mailing list