We're looking at /proc/<pid>/environ to see the environment of the
tomcat process. We're not using SELinux, and in this case everything
is being run by root, though tomcat does switch over to a tomcat user
at some point during it's startup. What really confuses me is why it
works in with all of the debug flags, but not when run normally as a
daemon.
On Thu, Feb 3, 2011 at 6:26 AM, jcbollinger <john.bollin...@stjude.org> wrote:
>
>
> On Feb 2, 1:12 pm, robertbogdon <robertbog...@gmail.com> wrote:
>> I'm running into a bizarre issue. What it boils down to is that when
>> I start tomcat through puppetd, certain UTF-8 settings do not appear
>> to take effect and the end result is garbage characters on a web
>> page. However, when we run puppetd with --no-daemonize --debug --
>> trace --one-time, everything works fine. Tomcat also starts
>> appropriately when started on boot, or manually with the service start
>> command. Our initial thought was that potentially there was a
>> difference in the environment variables being passed to tomcat
>> depending on how it was started, but we've examined the environments
>> and altered the start command puppet is using to ensure that they are
>> identical. I've included our service entry below, any help would be
>> appreicated.
>>
>> service { tomcat6:
>> enable => false,
>> #hasrestart => true,
>> start => '/bin/bash -c "unset LANGUAGE; unset LC_ALL; unset
>> LC_MESSAGES; /usr/sbin/service tomcat6 start"',
>> require => [ Package[tomcat6] ],
>> subscribe => [ File["/etc/tomcat6/tomcat-users.xml"], File["/etc/
>> tomcat6/server.xml"], File["/etc/tomcat6/config.properties"], File["/
>> etc/tomcat6/context.xml"] ],
>> ensure => running,
>> }
>>
>> enable is set to false in this entry to ensure that the correct
>> configuration is in place before the service is started and picked up
>> by the load balancer.
>
> I concur that the difference is probably related to the environment.
> How are you testing / verifying that the environments are identical?
> For instance, have you inserted code in the init script to dump the
> environment to a file at runtime?
>
> Other than environment *variables*, the most suspect environmental
> influence is the user identity (effective *and* real) on whose behalf
> the service is started. Do you perchance have SELinux running in
> enforcing mode? In that case, you need to expand the notion of
> "identity" to security context. These considerations could affect
> whether Tomcat is able to read various configuration files, especially
> any that have been locally modified.
>
>
> John
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To post to this group, send email to puppet-users@googlegroups.com.
> To unsubscribe from this group, send email to
> puppet-users+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.
>
>
--
---
Robert Bogdon
Sr. Systems Engineer, DivX
http://www.blah.net
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
