Free on-demand webinars: Learn how to set up, configure, and get more out of Checkmk – Pick your webinar

Werk #22490: mk_oracle: Fix 'sqlnet.ora can not be read' in single-directory deployment

Component Agent bakery
Title mk_oracle: Fix 'sqlnet.ora can not be read' in single-directory deployment
Date Nov 8, 2026
Level Trivial Change
Class Bug Fix
Compatibility Incompatible - Manual interaction might be required
Checkmk versions & editions
3.0.0b1
Not yet released
Checkmk Pro, Checkmk Ultimate, Checkmk Cloud, Checkmk Ultimate MT
2.5.0p20 Checkmk Pro, Checkmk Ultimate, Checkmk Cloud, Checkmk Ultimate MT
2.4.0p41 Checkmk Pro, Checkmk Ultimate, Checkmk Cloud, Checkmk Ultimate MT

With the single-directory deployment (Werk #17900), the Oracle checks failed with the following error, even if the setting 'sqlnet.ora permission group' of the rule 'Oracle databases (Linux, Solaris, AIX, Windows)' was configured:

.../package/config/sqlnet.ora can not be read by user "oracle"!

The agent plug-in mk_oracle reads sqlnet.ora as the owner of the Oracle binaries. The setting gives sqlnet.ora the configured group, but the folder package/config below the agent installation directory had the mode 750. The Oracle user therefore couldn't reach the file. The workaround was chmod o+x on the folder. On RPM-based systems, every agent update reset the mode to 750 again.

The folder now has the mode 751. Other users can traverse it to reach a file they have read access to, but they can't list its contents. The files the bakery puts there stay readable only for their owner and group.

On DEB-based systems, an agent update never changes the mode of an existing folder. There, only new installations get the new mode. If you use the setting 'sqlnet.ora permission group' on an existing DEB host, or have applied the workaround there, run the following command once. With the default installation directory, it is:

chmod 751 /opt/checkmk/agent/default/package/config

To the list of all Werks