Description of problem:
After rhel7 update 6 (rsyslog-8.24.0-34.el7.x86_64) rsyslog imfile stopped working:
- when tomcat rotates for example access_log
(        <Valve className="org.apache.catalina.valves.AccessLogValve" directory="logs"
               prefix="access_log" rotatable="true" renameOnRotate="true"
               requestAttributesEnabled="true" buffered="true"
               fileDateFormat=".yyyyMMdd" 
               pattern="%h %l %u %t &quot;%r&quot; %s %b %D JSESSIONID=%{JSESSIONID}c" />)

- sometimes when logrotate rotates apache access_log (doesn't happen always)

Imfile example config for tomcat:
module(load="imfile" mode="inotify" PollingInterval="20")
input(type="imfile" ruleset="uef_imfile_fwd"
        File="/var/log/tomcat/access_log"
        PersistStateInterval="300"
        Tag="access-hostnamehere"
        Severity="info"
        Facility="local7"
)


Imfile example for apache:
module(load="imfile" mode="inotify" PollingInterval="20")
input(type="imfile" ruleset="uef_imfile_fwd"
        File="/var/log/httpd/access_log"
        PersistStateInterval="300"
        Tag="access-hostnamehere"
        Severity="info"
        Facility="local7"
)

(uef_imfile_fwd ruleset forwards logs to remote server).

Version-Release number of selected component (if applicable):
syslog-8.24.0-34.el7.x86_64

How reproducible:
- Tomcat/java rotated logs: seems to happen after every rotate
- logrotate/apache: happens sometimes

Steps to Reproduce:
1. use rsyslog imfile to monitor tomcat access_log 
2. let tomcat rotate logfile
3. rsyslog stops forwarding logs after 

Actual results:
For example after after apache logrotate, rsyslog was monitoring wrong file:
these are the files from /var/lib/rsyslog/

file: imfile-state:4237564
content:
{ "filename": "\/var\/log\/httpd\/access_log", "prev_was_nl": 0, "curr_offs": 2295391, "strt_offs": 2295391 }
file: imfile-state:4331555
content: { "filename": "\/var\/log\/httpd\/error_log", "prev_was_nl": 0, "curr_offs": 1242, "strt_offs": 1242 }

Actual /var/log/httpd/access_log was already using different inode:
 File: ‘/var/log/httpd/access_log’
  Size: 255753          Blocks: 512        IO Block: 4096   regular file
Device: fd03h/64771d    Inode: 4237513     Links: 1
Access: (0644/-rw-r--r--)  Uid: (    0/    root)   Gid: (    0/    root)
Context: system_u:object_r:httpd_log_t:s0
Access: 2018-11-11 04:02:02.936520161 +0200
Modify: 2018-11-12 10:09:36.723540441 +0200
Change: 2018-11-12 10:09:36.723540441 +0200

So AFAIK rsyslog(imfile) didn't recognise rotation.

Similar situation with tomcat access_log: /var/lib/rsyslog/imfile-state:164
({ "filename": "\/var\/log\/tomcat\/access_log", "prev_was_nl": 0, "curr_offs": 83250, "strt_offs": 83250 }) while the actual logfile is already using different inode:
  File: ‘/var/log/tomcat/access_log’
  Size: 38850           Blocks: 80         IO Block: 4096   regular file
Device: fd07h/64775d    Inode: 190         Links: 1
Access: (0644/-rw-r--r--)  Uid: (   91/  tomcat)   Gid: (   91/  tomcat)
Context: system_u:object_r:tomcat_log_t:s0
Access: 2018-11-13 10:15:54.450811462 +0200
Modify: 2018-11-13 10:28:30.741826028 +0200
Change: 2018-11-13 10:28:30.741826028 +0200


Expected results:
rsyslog(imfile) continues to monitor/forward logs after logrotation.

Additional info:
Workaround for tomcat access logs:
When using logrotate+copytruncate for tomcat accesslog(+rotatable="false")
(and reloadontruncate="on" with imfile) seems to work.

This sounds like the problem described in rsyslog bug 3051 (https://github.com/rsyslog/rsyslog/pull/3051 / https://github.com/rsyslog/rsyslog/commit/e929ee7220de8a81a8669573ac44526397bb3158)

AFAIK rsyslog-8.24.0-34.el7.x86_64 imfile is missing the above commit.