Why am I seeing this in the log?

I replaced usernames with xxxx

This first line is referencing an internal user, so why is the ldap searcher looking externally?
WARN sonia.scm.auth.ldap.UserSearcher - no user with username xxxx found

This one is an external user. What is it trying to modify?
INFO sonia.scm.user.DefaultUserManager - modify user xxxxx of type null

Hey Marlene,

we will look into it and get back to you.

Hi,

First things first: These two log messages are nothing to worry about. Probably the level β€˜warn’ in your first example is not appropriate and should be an β€˜info’ at most.

So what does it mean: Users can have many sources in SCM-Manager, the LDAP plugin is just one example. So when a user logs in, all these sources (aka authentication realms) are queried. The first log message is just an info, that this user could not have been found in your LDAP directory.

The second message for your external (LDAP) user is just a hint, that the internal database of SCM-Manager was updated with the information found by the LDAP plugin, so that you can see this user on the Users page and assign permissions and groups.

I hope this helps, if not, just keep asking.

RenΓ©

I see. Thank you for explaining. But I was seeing very poor performance of the application with 8 cpus at 100%, so I was looking at the log and it was recording these entries every minute or so. It seemed like it was not necessary.

I also looked at the configuration and realized that I have the java memory option set to 1g. So, I raised it to 4g and rebooted the server. Things are running much better now. Do you have any recommended server configurations in your docs? I am running an ubuntu linux vm.

~WRD0348.jpg

image001.png

image002.png

image009.png

image004.png

image011.png

image006.jpg

NOTE: Below settings are for RPM based flavors - tested on CentOS-8.4, RockY-Linux-8.4 and AlmaLinux-8.4

  1. System environment:
    1.1. OS: Rocky Linux release 8.4 (Green Obsidian)
    1.2. CPU: 16 CORES
    1.3. RAM: 16 GB
    1.4. HDD: SSD
    1.5. SCM-Manager version: 2.27.2
    1.6. JDK:
       Openjdk version "11.0.13" 2021-10-19 LTS
       OpenJDK Runtime Environment 18.9 (build 11.0.13+8-LTS)
       OpenJDK 64-Bit Server VM 18.9 (build 11.0.13+8-LTS, mixed mode, sharing)
  1. STOP the scm-manager service
  2. Change the file β€œ/etc/default/scm-server”
    3.1. Comment out β€œEXTRA_JVM_ARGUMENTS”
    #EXTRA_JVM_ARGUMENTS="$EXTRA_JVM_ARGUMENTS -Djetty.host=$HOST -Djetty.port=$PORT"

  1. Change the file β€œ/opt/scm-server/bin/scm-server”
    4.1. Add or update these arguments and values carefully
# ----------------------------------------------------------------------------

#   Copyright (c) 2001-2002 The Apache Software Foundation.  All rights
#   reserved.

# scm-server host interface
HOST="0.0.0.0"

# scm-server port
PORT="8080"

# extra jvm arguments
#############################################################################
#EXTRA_JVM_ARGUMENTS="-Djava.awt.headless=true -Dlogback.configurationFile=logging.xml"
EXTRA_JVM_ARGUMENTS="-Djetty.host=${HOST} \
-Djetty.port=${PORT} \
-Xms1024m \
-Xmx8192m \
-XX:+UseG1GC \
-XX:MaxMetaspaceSize=2048m \
-XX:MaxGCPauseMillis=200 \
-XX:+ParallelRefProcEnabled \
-XX:+AlwaysPreTouch \
-XX:+UseStringDeduplication \
-XX:+DisableExplicitGC \
-XX:+ExplicitGCInvokesConcurrent \
-Djava.awt.headless=true \
-Dlogback.configurationFile=logging.xml \
-Dcom.sun.management.jmxremote \
-Dcom.sun.management.jmxremote.port=10053 \
-Dcom.sun.management.jmxremote.authenticate=false \
-Dcom.sun.management.jmxremote.ssl=false"
###############################################################################

BASEDIR="/opt/scm-server"

Note that the β€œcom.sun.management.jmxremote” are for Zabbix JMX monitoring interface.

  1. START SCM-Manager service

  2. The load on the server can be monitored with Zabbix through the JMX interface (Java default monitoring console also can give a quick overview)

These are the enterprise scalable production JVM settings that are working for me and I am seeing a crisp experience with the SCM-Manager 2.27.2

3 Likes