Loading

×Sorry to interrupt
This page has an error. You might just need to refresh it.
[NoErrorObjectAvailable] Uncaught ReferenceError: addCTracking is not defined
Failing descriptor: {markup://c:KM_ArticleThemeLayout}

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Tail input plugin in Fluent-bit is reporting "No space left on device" (78155)

Last Updated: 4/5/2022Categories: InformationalTotal Views: 7712Language:
English

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

Symptoms

You see errors similar to the following in the Tail input plugin in Fluent-bit:

No space left on device

When you check the Fluent-bit pods by running kubectl logs <fluent-bit-pod> -n pks-system, you see the entries similar to:

[2020/03/04 20:16:17] [error] [in_tail] could not register file into fs_events
[2020/03/04 20:16:17] [error] [plugins/in_tail/tail_fs.c:219 errno=28] No space left on device
[2020/03/04 20:16:17] [error] [in_tail] could not register file into fs_events
[2020/03/04 20:16:17] [error] [plugins/in_tail/tail_fs.c:219 errno=28] No space left on device
[2020/03/04 20:16:17] [error] [in_tail] could not register file into fs_events

You see that there is enough free space on /var/log inside the pod and the worker nodes also have enough free space.

Impact / Risks

If this situation occurs, the underlying log files are not lost or deleted.  They are still there.  However, they will no longer be monitored by fluent-bit after hitting that current limit.  This situation and error occurs because (at that time) the system kernel has reached the limit of filesystem "inodes" (not a limit of storage space).

Resolution

This is a known issue affecting VMware Enterprise PKS / VMware Tanzu Kubernetes Grid Integrated Edition. There is currently no resolution.

Workaround

As a work around, you can increase sysctl to 16384 to start with and see if this resolves the issue. You have to options on how to increase systctl parameter.

Method 1: This workaround will not persist across PKS upgrades or node recreation.

For more information, see https://github.com/fluent/fluent-bit/issues/1018

To Increase the sysctl parameter fs.inotify.max_user_watches on all the worker nodes:

Check the current value:

sysctl -a | grep fs.inotify.max_user_watches

Increase the value to 16384

sysctl -w  fs.inotify.max_user_watches=16384

Update the new value to the kernel:

sysctl -p

Check the updated value:

sysctl -a | grep fs.inotify.max_user_watches

You can also edit the file /etc/sysctl.conf and search for this parameter and overwrite the existing value and then perform kernel update by running sysctl -p.

Method 2: Use of bosh add-on. This workaround will persist upgrades/updates and be applied to all clusters.

For a detailed steps on how to add bosh add-on to include a customer kernel parameter and how to apply it to tkgi clusters, please see
https://github.com/svrc/tkgi-kernel-params

Related Information

https://bosh.io/docs/runtime-config/

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

No results for undefined

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware PKS

Related Versions:

VMware PKS 1.x

Take Our Survey

Support Assistant