File ownership changes even when services are stopped
Article ID: 229808
Updated On:
Products
Issue/Introduction
On the Data Aggregator and on the Data Collectors the activemq, dadaemon, and dcmd script files change their ownership to root after a reboot even when the application is properly shut down.
This cause at least an extra 2 hours of down time last night bringing the servers up after a scheduled patch reboot.
Need to stop these files from changing owners to reduce our down time.
Environment
Release : 21.2
Component : IM Data Aggregator
Cause
Currently, if the DA/DC doesn't shutdown cleanly and remove .lock, AND it's running as NON-root,
there is an issue (fixed by 21.2.8) where it recreates the data directory as root and DA/DC can't write to it as non-root.
Resolution
workaround until 21.2.8 would be to edit scripts/karaffunctions on DA/DCs..
find checklockandcleanup function.
change:
if [ ! -e $karaf_root/data ]; then
# We need to create the karaf.out file as startup fails instead of creating it
mkdir $karaf_root/data/;
touch $karaf_root/data/karaf.out;
fi
to:
if [ ! -e $karaf_root/data ]; then
# We need to create the karaf.out file as startup fails instead of creating it
mkdir $karaf_root/data
touch $karaf_root/data/karaf.out
chown -R <installuser> $karaf_root/data
fi
And:
if [ ! -e $karaf_root/deploy ]; then
mkdir $karaf_root/deploy/;
fi
To:
if [ ! -e $karaf_root/deploy ]; then
mkdir $karaf_root/deploy/
chown -R <installuser> $karaf_root/deploy
fi
replace <installuser> with whoever is running/owns the DA/DC install dir
Additional Information
This will be fixed in 21.2.8 by adding code to chown the directories to the non-root owner.
similar techdoc, different path to get there:
Feedback
