Я вот вижу несколько моментов.
1. Переезд с 2015 (на systemd)
Много сервисов при старте сперва ругаются на lookup юзеров. И томкат и апач итд. Похоже лдап едира чуть запаздывает. Но потом все работает нормально.
При этом с eDir LDAP'ом все в порядке и LUM тоже живой.
Вот примеры:
---------------- apache2
systemctl status apache2
● apache2.service - The Apache Webserver
Loaded: loaded (/usr/lib/systemd/system/apache2.service; enabled; vendor preset: disabled)
Active: active (running) since Tue 2022-09-06 10:23:42 +07; 4min 31s ago
Main PID: 1448 (httpd-prefork)
Status: "Processing requests..."
Tasks: 6
CGroup: /system.slice/apache2.service
├─1448 /usr/sbin/httpd-prefork -DSYSCONFIG -DSSL -DNAGIOSDCH -C PidFile /var/run/httpd.pid -C Include /etc/apache2/sysconfig.d//loadmodule.conf -C Include /etc/apache2/sysconfi...
├─1674 /usr/sbin/httpd-prefork -DSYSCONFIG -DSSL -DNAGIOSDCH -C PidFile /var/run/httpd.pid -C Include /etc/apache2/sysconfig.d//loadmodule.conf -C Include /etc/apache2/sysconfi...
├─1675 /usr/sbin/httpd-prefork -DSYSCONFIG -DSSL -DNAGIOSDCH -C PidFile /var/run/httpd.pid -C Include /etc/apache2/sysconfig.d//loadmodule.conf -C Include /etc/apache2/sysconfi...
├─1676 /usr/sbin/httpd-prefork -DSYSCONFIG -DSSL -DNAGIOSDCH -C PidFile /var/run/httpd.pid -C Include /etc/apache2/sysconfig.d//loadmodule.conf -C Include /etc/apache2/sysconfi...
├─1677 /usr/sbin/httpd-prefork -DSYSCONFIG -DSSL -DNAGIOSDCH -C PidFile /var/run/httpd.pid -C Include /etc/apache2/sysconfig.d//loadmodule.conf -C Include /etc/apache2/sysconfi...
└─1678 /usr/sbin/httpd-prefork -DSYSCONFIG -DSSL -DNAGIOSDCH -C PidFile /var/run/httpd.pid -C Include /etc/apache2/sysconfig.d//loadmodule.conf -C Include /etc/apache2/sysconfi...
Sep 06 10:23:26 sles11test1 systemd[1]: Starting The Apache Webserver...
Sep 06 10:23:42 sles11test1 start_apache2[1448]: [Tue Sep 06 10:23:42.051325 2022] [alias:warn] [pid 1448] AH00671: The Alias directive in /etc/opt/novell/httpd/conf.d/gw.conf...rlier Alias.
Sep 06 10:23:42 sles11test1 systemd[1]: Started The Apache Webserver.
Sep 06 10:23:45 sles11test1 httpd-prefork[1674]: nds_nss_GetGroupsbyMember: Failed to init socket, status = 0
Sep 06 10:23:45 sles11test1 httpd-prefork[1677]: nds_nss_GetGroupsbyMember: Failed to init socket, status = 0
Sep 06 10:23:45 sles11test1 httpd-prefork[1678]: nds_nss_GetGroupsbyMember: Failed to init socket, status = 0
Sep 06 10:23:45 sles11test1 httpd-prefork[1675]: nds_nss_GetGroupsbyMember: Failed to init socket, status = 0
Sep 06 10:23:45 sles11test1 httpd-prefork[1676]: nds_nss_GetGroupsbyMember: Failed to init socket, status = 0
Hint: Some lines were ellipsized, use -l to show in full.
--------------tomcat8
systemctl status tomcat8 -l
● tomcat8.service - Tomcat 8 Servlet Container
Loaded: loaded (/etc/systemd/system/tomcat8.service; enabled; vendor preset: disabled)
Active: active (running) since Tue 2022-09-06 10:23:30 +07; 8min ago
Process: 1445 ExecStart=/opt/tomcat8/bin/startup.sh (code=exited, status=0/SUCCESS)
Main PID: 1497 (java)
Tasks: 33 (limit: 512)
CGroup: /system.slice/tomcat8.service
└─1497 /usr/lib64/jvm/java/bin/java -Djava.util.logging.config.file=/opt/tomcat8/conf/logging.properties -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Djdk.tls.ephemeralDHKeySize=2048 -Djava.protocol.handler.pkgs=org.apache.catalina.webresources -Dignore.endorsed.dirs= -classpath /opt/tomcat8/bin/bootstrap.jar:/opt/tomcat8/bin/tomcat-juli.jar -Dcatalina.base=/opt/tomcat8 -Dcatalina.home=/opt/tomcat8 -Djava.io.tmpdir=/opt/tomcat8/temp org.apache.catalina.startup.Bootstrap start
Sep 06 10:23:26 sles11test1 systemd[1]: Starting Tomcat 8 Servlet Container...
Sep 06 10:23:26 sles11test1 systemd[1445]: nds_nss_GetGroupsbyMember: Failed to init socket, status = 0
Sep 06 10:23:30 sles11test1 systemd[1]: Started Tomcat 8 Servlet Container.
При этом:
id admin
uid=601(admin) gid=601(admingroup) groups=601(admingroup)
id wwwrun
uid=30(wwwrun) gid=8(www) groups=8(www),115(nagcmd),81(novlxtier)
В общем мне кажется что из-за параллельной загрузки SystemD демоны не дожидаются полной инициализации LUM.
2. После старта systemd --failed вываливает кучу nit сервисов. Но novell-nit говорит что статус ок.
Насколько это критично ?
systemctl --failed
UNIT LOAD ACTIVE SUB DESCRIPTION
● nitTelemetry.service loaded failed failed NIT Telemetry Data service
● oes-cis-agent.service loaded failed failed CIS agent for OES
● oes-cis-recall-agent.service loaded failed failed CIS recall agent for OES
● oes-cis-scanner.service loaded failed failed CIS scanner for OES
● oes-dashboard-agent.service loaded failed failed Dashboard agent for OES
● oes-telemetry-agent.service loaded failed failed OES Telemetry agent for OES
[color=#FF0000]● sblim-sfcb.service loaded failed failed Small Footprint CIM Broker Service
LOAD = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB = The low-level unit activation state, values depend on unit type.
7 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.
systemctl status novell-nit -l
● novell-nit.service - Novell Identity Translator(NIT)
Loaded: loaded (/usr/lib/systemd/system/novell-nit.service; enabled; vendor preset: disabled)
Active: active (running) since Tue 2022-09-06 10:24:25 +07; 20min ago
Docs: man:nitconfig
man:nit
Process: 2223 ExecStart=/usr/sbin/nitd (code=exited, status=0/SUCCESS)
Process: 2219 ExecStartPre=/usr/bin/rm -f /var/opt/novell/log/nit/.nitnotloaded (code=exited, status=0/SUCCESS)
Process: 2218 ExecStartPre=/usr/bin/rm -f /var/opt/novell/log/nit/.nitloaded (code=exited, status=0/SUCCESS)
Main PID: 2235 (nitd)
Tasks: 3
CGroup: /system.slice/novell-nit.service
└─2235 /usr/sbin/nitd
Sep 06 10:24:25 sles11test1 nitd[2235]: [NIT_DMN 0x7f64c3aab740]: INFORMATION: main: System Boot time since epoch: 1662434555
Sep 06 10:24:25 sles11test1 nitd[2235]: [NIT_DMN 0x7f64c3aab740]: INFORMATION: main: /var/opt/novell/nit/db/.g_i_info file change time:1661828874
Sep 06 10:24:25 sles11test1 nitd[2235]: [NIT_DMN 0x7f64c3aab740]: INFORMATION: main: Clearing NIT persistent cache from G2I DB
Sep 06 10:24:25 sles11test1 nitd[2235]: [NIT_THRD 0x7f64c3aab740]: INFORMATION: populate_hash_from_g2idb: All entries fetched from g2i database
Sep 06 10:24:25 sles11test1 nitd[2235]: [NIT_DMN 0x7f64c3aab740]: INFORMATION: main: Data base and hash table initialization/build is done
Sep 06 10:24:25 sles11test1 nitd[2235]: [NIT_DMN 0x7f64c3aab740]: INFORMATION: main: Unix Domain IPC Socket /tmp/.nitd is created
Sep 06 10:24:25 sles11test1 nitd[2235]: [NIT_DMN 0x7f64c3aab740]: INFORMATION: main: IPC Channel is ready
Sep 06 10:24:25 sles11test1 nitd[2235]: [NIT_DMN 0x7f64c3aab740]: INFORMATION: main: Starting in eDirectory only mode.
Sep 06 10:24:25 sles11test1 nitd[2235]: [NIT_THRD 0x7f64bdc3c700]: INFORMATION: refresh_func: User Cache refresh thread started
Sep 06 10:24:25 sles11test1 systemd[1]: Started Novell Identity Translator(NIT).
3. При выполнении shutdown он задумывается на несколько минут с сообщением, что shutdown-systemd ожидает volmnd и adminusd
Потом shutdown завершается успешно.
Можете глянуть у кого в работе оно везде так ?
А особые гуру может скажут критично ли это в работе ?