[Discuss-gnuradio] Log Level/Format Not Changing With Config File

I'm having an odd problem with the GR logger - no matter what I do the logger logs messages at all log levels and ignores my formatting configuration.  I have another machine with the same configuration that behaves as I expect.  

I'm writing an OOT module and testing it using the same code on two different RHEL7 machines. I have the same version of GR and log4cpp on both machines:

$ python -c 'from gnuradio import gr; print gr.version()'

3.7.10.1

$ sudo yum info 'log4cpp*'

Loaded plugins: langpacks, product-id, rhnplugin, search-disabled-repos, subscription-manager, versionlock

This system is receiving updates from RHN Classic or Red Hat Satellite.

Installed Packages

Name        : log4cpp

Arch        : x86_64

Version     : 1.1.1

Release     : 1.el7

Size        : 394 k

Repo        : installed

From repo   : epel

Summary     : C++ logging library

URL         : http://sourceforge.net/projects/log4cpp/

License     : LGPLv2+

Description : A library of C++ classes for flexible logging to files, syslog, IDSA and

            : other destinations. It is modeled after the Log for Java library

            : (http://www.log4j.org), staying as close to their API as is reasonable.

Name        : log4cpp-devel

Arch        : x86_64

Version     : 1.1.1

Release     : 1.el7

Size        : 206 k

Repo        : installed

From repo   : epel

Summary     : Header files, libraries and development man pages  log4cpp

URL         : http://sourceforge.net/projects/log4cpp/

License     : LGPLv2+

Description : This package contains the header files, static libraries and development

            : man pages for log4cpp. If you like to develop programs using log4cpp,

            : you will need to install log4cpp-devel.

I've used strace to look at all the files my flowgraph opens and the config files it opens are configured the same way on both machines.  I also try to change the log level env variable like below without success 

export GR_CONF_LOG_LOG_LEVEL=INFO

Here are two sample messages, the first one is correct and the second is not

INFO: sample message

Root :INFO: top_block - sample message

Why is this happening?

Thanks for any help,

Devin