alphasupremicus wrote:
> We are zeroing in on it, but still odd to me. I guess I need to understand
> the zenoss start script and see how it works.
Voila! I figured it out!
I had a skeleton .bashrc script in /etc/skel that is used when new user
accounts are created.
My skeleton .bashrc script has an early exit in the script that determines if
the user is logging on interactively or bails early if so.
One could argue it is a bad design, but the zenoss installation rpm sets up the
zeonss user account and appends some exports to the zenoss .bashrc script that
*MUST* be present before starting the services.
This explains why when logged on as zenoss interactively it all worked.
So clearly it is my own doing that caused this problem, but I though I'd shared
the final solution. Here's my bashrc script for the zenoss user after I fixed
the problem:
Code:
# .bashrc
# User specific aliases and functions
export ZENHOME="/opt/zenoss"
export PATH="${ZENHOME}/bin:${PATH}"
export PYTHONPATH="/opt/zenoss/lib/python"
export LD_LIBRARY_PATH="/opt/zenoss/lib"
# If not running interactively, don't do anything:
[ -z "$PS1" ] && return
# Source global definitions
if [ -f /etc/bashrc ]; then
. /etc/bashrc
fi
fastprompt
I had to move the four export statements to prior to my "early return". The
four export statements were at the bottom of the .bashrc script before I
corrected this file.
Sorry about the trouble and I really appreciate the troubleshooting.
Cheers,
John
-------------------- m2f --------------------
Read this topic online here:
http://community.zenoss.com/forums/viewtopic.php?p=14764#14764
-------------------- m2f --------------------
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
