My Oracle Support Banner

Dbus Daemon is not Closing the File Descriptors. (Doc ID 2481479.1)

Last updated on APRIL 15, 2021

Applies to:

Linux OS - Version Oracle Linux 7.0 and later
Linux x86-64

Symptoms

When starting Oracle Database RMAN backup job via DBMS_SCHEDULER dbus-daemon opens file /proc/<pid_of_RMAN>/cmdline and keeps it open. Even when RMAN process finishes the file descriptor stays open.

Over time the number of file descriptors that dbus-daemon has opened will reach the limit for opened files (about 2000). When dbus-daemon reached the limit of open files it starts to use 100% CPU.

While RMAN job starts journalctl shows systemd starting the fprintd.service:

dbus-daemon[906]: dbus[906]: [system] Activating via systemd: service name='net.reactivated.Fprint' unit='fprin
dbus[906]: [system] Activating via systemd: service name='net.reactivated.Fprint' unit='fprintd.service'
systemd[1]: Starting Fingerprint Authentication Daemon...
dbus[906]: [system] Successfully activated service 'net.reactivated.Fprint'
dbus-daemon[906]: dbus[906]: [system] Successfully activated service 'net.reactivated.Fprint'
systemd[1]: Started Fingerprint Authentication Daemon.
fprintd[22941]: Launching FprintObject
fprintd[22941]: ** Message: D-Bus service launched with name: net.reactivated.Fprint
fprintd[22941]: ** Message: entering main loop
fprintd[22941]: ** Message: No devices in use, exit

Changes

No specific changes made to the server.

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.