Error in Apache Connector after installing ColdFusion2018 Update2

Forum|Forum|7 years ago
February 14, 2019
2 replies
2009 views

Hi There,

As soon as ColdFusion 2018 update 2 was installed and the Apache connector was rebuilt, we are seeing this following error in mod_jk.log, repeatedly.

[Thu Feb 14 12:42:06 2019] [16186:139977799252096] [error] uri_worker_map_update::jk_uri_worker_map.c (1299): Unable to stat the /opt/coldfusion2018/config/wsconfig/1/uriworkermap.properties (errno=13)

The server is running RHEL 7, with SELinux and locked down. However the apache is running without any issues and the web application doesn't experience any issues. But the mod_jk.log is flooded with this entry.

It would be great, if someone could assist on this please. We didn't face this issue before.

This topic has been closed for replies.

pete_freitag

Participating Frequently

First - you should file a bug so Adobe is aware of the issue.

Next make sure that apache has permission to read that file

Finally make sure that selinux has the proper label on the file:

chcon -t httpd_config_t -u system_u /opt/coldfusion2018/config/wsconfig/1/uriworkermap.properties

A

Ann SamAuthor

Known Participant

Thank You Pete for your suggestions.

We resolved it and it was down to the file permissions. The right SELinux context was applied. as you had mentioned.

After the Apache Connector was re-built, the permissions of the files were 644. After this update 2 installation, the mod_jk.log file had its right SELinux type for the file and the permissions, without manually granting it.

Changing the permission of the file to 660, stopped the error entry in the log file. (Though CFLockdown guide recommendation was 540, which still didn't prevent the error from occurring). However the apache was starting up without any issues and CFadmin was accessible during the entire time.

pete_freitag

Participating Frequently

Thanks for clarifying Annie, that is odd that it would need write permission to that file. It is just a configuration file but perhaps the new autotuning feature now writes to it so it opens for writing instead of opens it for reading??

D

Dave Watts

Community Expert

Does that file exist? When you see "unable to stat" errors, sometimes that means the file no longer exists. I think you have to tell SELinux to no longer check that file. (Note: I am not an expert on SELinux.)

Dave Watts, Eidolon LLC

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded