AnsweredAssumed Answered

Java ownership

Question asked by rb0048204 on Feb 13, 2017
Latest reply on Feb 14, 2017 by mdeeprose

Hi all,

 

While getting support for a test install of Q4 2016 last week, we received a recommendation from a Tier 2 support tech to change ownership of the jdk from root to bbuser. We are wondering what other admins have typically done with ownership of /usr/java/latest (or alternative java location) when running past distributions of Learn, and with the new Q2 and Q4 2016 versions if applicable. Do you let bbuser own java?

 

I took the Blackboard Linux Sysadmin training course, and in that context root owned java.

 

More detail on the issue below. Note it is not really an error but a warning which fills up stdout-stderr very quickly on the new version:


INFO | jvm 1 | 2017/02/08 11:06:30 | Feb 08, 2017 11:06:30 AM java.util.prefs.FileSystemPreferences checkLockFile0ErrorCode
INFO | jvm 1 | 2017/02/08 11:06:30 | WARNING: Could not lock System prefs. Unix error code 32688.
INFO | jvm 1 | 2017/02/08 11:06:30 | Feb 08, 2017 11:06:30 AM java.util.prefs.FileSystemPreferences syncWorld
INFO | jvm 1 | 2017/02/08 11:06:30 | WARNING: Couldn't flush system prefs: java.util.prefs.BackingStoreException: Couldn't get file lock.

Learn Support said:
“This usually indicates a permissions issue with the JVM user not being able to read or write to the .systemPrefs directory for the current JRE, or not being able to read the location settings for the current .systemPrefs directory.  It doesn't seem to be stopping the JVM from starting, but is definitely filling the stdout log.”

 

When I google it, I do see that userRoot and systemRoot java permissions play a role in creating and writing to the systemPrefs directory, but I also see that the JVM option Djava.util.prefs.systemRoot=/examplepath/directory1 may be configured.

 

Any notes on your experience are greatly appreciated. Thanks!

Outcomes