Uyuni on openSUSE Leap 15.5

schilling · June 11, 2024, 3:13pm

Hello,
I am trying to get an Uyuni server running on openSUSE LEAP 15.5 in my lab.
I am following the “legacy” instruction from: Install Uyuni Server with openSUSE | Uyuni Documentation
I installed openSUSE LEAP 15.5 from DVD and applied latest online updates from today.
After adding the necessary repos and running “zypper in patterns-uyuni_server” I am able to launch the setup wizard via yast.

The last step fails:

uyunitst:/var/log # /usr/lib/susemanager/bin/mgr-setup -s -l /var/log/mgr_setup.log
Asserting correct java version...
  /var/spacewalk already exists. Leaving it untouched.
  Filesystem type for /var/cache is xfs - ok.
  Open needed firewall ports...
  Warning: ALREADY_ENABLED: suse-manager-server
  success
  Performing forced re-installation!
  Shutting down spacewalk services...
  Done.
  Delete existing database...
  Delete existing salt minion keys
  CREATE ROLE
  * Loading answer file: /root/spacewalk-answers.
  ** Database: Setting up database connection for PostgreSQL backend.
  ** Database: Populating database.
  ** Database: --clear-db option used.  Clearing database.
  ** Database: Shutting down spacewalk services that may be using DB.
  ** Database: Services stopped.  Clearing DB.
  Running spacewalk-sql --select-mode-direct /usr/share/susemanager/db/postgres/deploy.sql
  *** Progress: #
  * Performing initial configuration.
  * Configuring apache SSL virtual host.
  * Creating SSL certificates.
  ** SSL: Generating server certificate.
  ** Database: Setting up report database.
  ** Database: --clear-db option used.  Clearing report database.
  Running /usr/bin/uyuni-setup-reportdb create --db reportdb --user pythia_susemanager --host localhost --address * --remote 0.0.0.0/0,::/0 --autogenpw
  *** Progress: #
  ** Database: Installation complete.
  * Report DB Configured.
  * Update configuration in database.
  * Setting up Cobbler..
  * Deploying configuration files.
  * Restarting services.
  Could not restart spacewalk services.  Exit value: 1.
  Please examine /var/log/rhn/rhn_installation.log for more information.
  ERROR: spacewalk-setup failed

The logfile shows the following:

[...]
 * Making backup of /etc/rhn/rhn.conf.2024-06-11_14:44:37.256714 to /etc/sysconfig/rhn/backup-2024-06-11-16:44/etc/rhn/rhn.conf.2024-06-11_14:44:37.256714
Shutting down spacewalk services...
Done.
Starting spacewalk services...
  Checking DB schema and running DB schema upgrade if needed. This may take a while.
  Call the following command to see progress: journalctl -f -u uyuni-check-database.service
A dependency job for spacewalk.target failed. See 'journalctl -xe' for details.
FAILED

journalctl -xe shows:

uyunitst:/var/log # journalctl -xe
Jun 11 16:45:03 uyunitst systemd[1]: Registering bus object implementation for path=/org/freedesktop/systemd1/unit iface=org.freedesktop.systemd1.Socket
Jun 11 16:45:03 uyunitst systemd[1]: Registering bus object implementation for path=/org/freedesktop/systemd1/unit iface=org.freedesktop.systemd1.Swap
Jun 11 16:45:03 uyunitst systemd[1]: Registering bus object implementation for path=/org/freedesktop/systemd1/unit iface=org.freedesktop.systemd1.Target
Jun 11 16:45:03 uyunitst systemd[1]: Registering bus object implementation for path=/org/freedesktop/systemd1/unit iface=org.freedesktop.systemd1.Timer
Jun 11 16:45:03 uyunitst systemd[1]: Registering bus object implementation for path=/org/freedesktop/LogControl1 iface=org.freedesktop.LogControl1
Jun 11 16:45:03 uyunitst systemd[1]: Accepted new private connection.
Jun 11 16:45:03 uyunitst systemd[1]: Bus private-bus-connection: changing state AUTHENTICATING → RUNNING
Jun 11 16:45:03 uyunitst systemd[1]: Got message type=method_call sender=n/a destination=org.freedesktop.systemd1 path=/org/freedesktop/systemd1/unit/uyuni_2dcheck_2ddatabase_2eservice interface=org.f>
Jun 11 16:45:03 uyunitst systemd[1]: Failed to read pids.max attribute of cgroup root, ignoring: No data available
Jun 11 16:45:03 uyunitst systemd[1]: Found unit uyuni-check-database.service at /usr/lib/systemd/system/uyuni-check-database.service (regular file)
Jun 11 16:45:03 uyunitst systemd[1]: Preset files say disable uyuni-check-database.service.
Jun 11 16:45:03 uyunitst systemd[1]: Sent message type=method_return sender=org.freedesktop.systemd1 destination=n/a path=n/a interface=n/a member=n/a cookie=1 reply_cookie=1 signature=a{sv} error-nam>
Jun 11 16:45:03 uyunitst systemd[1]: Bus private-bus-connection: changing state RUNNING → CLOSING
Jun 11 16:45:03 uyunitst systemd[1]: Bus private-bus-connection: changing state CLOSING → CLOSED
Jun 11 16:45:03 uyunitst systemd[1]: Got disconnect on private connection.
Jun 11 16:45:03 uyunitst systemd[1]: Received SIGCHLD from PID 19202 (mgr-setup).
Jun 11 16:45:03 uyunitst systemd[1]: Child 19202 (mgr-setup) died (code=exited, status=0/SUCCESS)
Jun 11 16:45:03 uyunitst systemd[1]: session-1.scope: Failed to read oom_kill field of memory.events cgroup attribute: No such file or directory
Jun 11 16:45:03 uyunitst systemd[1]: session-1.scope: Child 19202 belongs to session-1.scope.
Jun 11 16:45:24 uyunitst server[21929]: 11-Jun-2024 16:45:24.493 INFO [pool-4-thread-1] org.apache.catalina.loader.WebappClassLoaderBase.checkStateForResourceLoading Illegal access: this web applicati>
Jun 11 16:45:24 uyunitst server[21929]:         java.lang.IllegalStateException: Illegal access: this web application instance has been stopped already. Could not load [java.util.function.Consumer]. T>
Jun 11 16:45:24 uyunitst server[21929]:                 at org.apache.catalina.loader.WebappClassLoaderBase.checkStateForResourceLoading(WebappClassLoaderBase.java:1349)
Jun 11 16:45:24 uyunitst server[21929]:                 at org.apache.catalina.loader.WebappClassLoaderBase.checkStateForClassLoading(WebappClassLoaderBase.java:1337)
Jun 11 16:45:24 uyunitst server[21929]:                 at org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1174)
Jun 11 16:45:24 uyunitst server[21929]:                 at org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1141)
Jun 11 16:45:24 uyunitst server[21929]:                 at com.suse.manager.webui.websocket.WebsocketHeartbeatService.clearStaleSessions(WebsocketHeartbeatService.java:84)
Jun 11 16:45:24 uyunitst server[21929]:                 at com.suse.manager.webui.websocket.WebsocketHeartbeatService.lambda$initScheduler$2(WebsocketHeartbeatService.java:123)
Jun 11 16:45:24 uyunitst server[21929]:                 at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
Jun 11 16:45:24 uyunitst server[21929]:                 at java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305)
Jun 11 16:45:24 uyunitst server[21929]:                 at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305)
Jun 11 16:45:24 uyunitst server[21929]:                 at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
Jun 11 16:45:24 uyunitst server[21929]:                 at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
Jun 11 16:45:24 uyunitst server[21929]:                 at java.base/java.lang.Thread.run(Thread.java:829)
Jun 11 16:45:42 uyunitst systemd[1]: systemd-journald.service: Got notification message from PID 795 (WATCHDOG=1)
Jun 11 16:46:26 uyunitst spacewalk-startup-helper[23295]: taskomatic still not up and running
Jun 11 16:46:26 uyunitst systemd[1]: Received SIGCHLD from PID 23295 (spacewalk-start).
Jun 11 16:46:26 uyunitst systemd[1]: Child 23295 (spacewalk-start) died (code=exited, status=0/SUCCESS)
Jun 11 16:46:26 uyunitst systemd[1]: spacewalk-wait-for-taskomatic.service: Failed to read oom_kill field of memory.events cgroup attribute: No such file or directory
Jun 11 16:46:26 uyunitst systemd[1]: spacewalk-wait-for-taskomatic.service: Child 23295 belongs to spacewalk-wait-for-taskomatic.service.
Jun 11 16:46:26 uyunitst systemd[1]: spacewalk-wait-for-taskomatic.service: Main process exited, code=exited, status=0/SUCCESS (success)
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ An ExecStart= process belonging to unit spacewalk-wait-for-taskomatic.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 0.
Jun 11 16:46:26 uyunitst systemd[1]: spacewalk-wait-for-taskomatic.service: Changed start -> exited
Jun 11 16:46:26 uyunitst systemd[1]: spacewalk-wait-for-taskomatic.service: Job 17501 spacewalk-wait-for-taskomatic.service/start finished, result=done
Jun 11 16:46:26 uyunitst systemd[1]: Finished Spacewalk wait for taskomatic.
░░ Subject: A start job for unit spacewalk-wait-for-taskomatic.service has finished successfully
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit spacewalk-wait-for-taskomatic.service has finished successfully.
░░
░░ The job identifier is 17501.
Jun 11 16:46:26 uyunitst systemd[1]: Sent message type=signal sender=n/a destination=n/a path=/org/freedesktop/systemd1/unit/spacewalk_2dwait_2dfor_2dtaskomatic_2eservice interface=org.freedesktop.DBu>
Jun 11 16:46:26 uyunitst systemd[1]: Sent message type=signal sender=n/a destination=n/a path=/org/freedesktop/systemd1/unit/spacewalk_2dwait_2dfor_2dtaskomatic_2eservice interface=org.freedesktop.DBu>
Jun 11 16:46:26 uyunitst systemd[1]: Sent message type=signal sender=n/a destination=n/a path=/org/freedesktop/systemd1 interface=org.freedesktop.systemd1.Manager member=JobRemoved cookie=17388 reply_>
Jun 11 16:46:26 uyunitst systemd[1]: Sent message type=signal sender=n/a destination=n/a path=/org/freedesktop/systemd1/unit/spacewalk_2dwait_2dfor_2dtaskomatic_2eservice interface=org.freedesktop.DBu>
Jun 11 16:46:26 uyunitst systemd[1]: Sent message type=signal sender=n/a destination=n/a path=/org/freedesktop/systemd1/unit/spacewalk_2dwait_2dfor_2dtaskomatic_2eservice interface=org.freedesktop.DBu>
Jun 11 16:46:26 uyunitst systemd[1]: spacewalk-wait-for-taskomatic.service: Control group is empty.
Jun 11 16:46:26 uyunitst systemd[1]: systemd-journald.service: Received EPOLLHUP on stored fd 79 (stored), closing.
Jun 11 16:46:26 uyunitst systemd[1]: systemd-logind.service: Got notification message from PID 1105 (WATCHDOG=1)
Jun 11 16:46:39 uyunitst systemd[1]: systemd-udevd.service: Got notification message from PID 807 (WATCHDOG=1)

One additional thing I was able to figure out - although I don’t know if this is the cause or a result of another issue - was that taskomatic stops right after starting

Jun 11 16:40:47 uyunitst systemd[1]: Started Taskomatic.
░░ Subject: A start job for unit taskomatic.service has finished successfully
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit taskomatic.service has finished successfully.
░░
░░ The job identifier is 15682.
Jun 11 16:40:47 uyunitst taskomatic[18934]: WARNING: Unknown module: java.annotation specified to --add-exports
Jun 11 16:40:47 uyunitst taskomatic[18934]: WARNING: Unknown module: java.annotation specified to --add-opens
Jun 11 16:40:48 uyunitst systemd[1]: taskomatic.service: Main process exited, code=exited, status=255/EXCEPTION
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ An ExecStart= process belonging to unit taskomatic.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 255.
Jun 11 16:40:48 uyunitst systemd[1]: taskomatic.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ The unit taskomatic.service has entered the 'failed' state with result 'exit-code'.
Jun 11 16:40:49 uyunitst systemd[1]: taskomatic.service: Scheduled restart job, restart counter is at 5.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ Automatic restarting of the unit taskomatic.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
Jun 11 16:40:49 uyunitst systemd[1]: Stopped Taskomatic.
░░ Subject: A stop job for unit taskomatic.service has finished
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A stop job for unit taskomatic.service has finished.
░░
░░ The job identifier is 15837 and the job result is done.
Jun 11 16:40:49 uyunitst systemd[1]: taskomatic.service: Start request repeated too quickly.
Jun 11 16:40:49 uyunitst systemd[1]: taskomatic.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ The unit taskomatic.service has entered the 'failed' state with result 'exit-code'.
Jun 11 16:40:49 uyunitst systemd[1]: Failed to start Taskomatic.
░░ Subject: A start job for unit taskomatic.service has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit taskomatic.service has finished with a failure.
░░
░░ The job identifier is 15837 and the job result is failed.

I would very much appreciate your help to point me into the right direction.

Best,
Daniel

lalaman · July 10, 2024, 5:03am

Creating an account just to potentially help you because I was stuck with something similar.
I had a similar error and it was due to bytebuddy being incompatible/broken and you need to upload the new bytebuddy into the system

In your opensuse type

cat /var/log/rhn/rhn_taskomatic_daemon.log | grep bytebuddy

If you see fatal errors regarding it, you need to replace the bytebuddy that was default installed. I downloaded the latest version from https://mvnrepository.com/artifact/net.bytebuddy/byte-buddy

Then placed the file in the server (you can use scp for this). In the location /usr/share/java/byte-buddy make a backup copy and replace the new jar file you downloaded as byte-buddy.jar

mv byte-buddy.jar byte-buddybackup,jar
mv byte-buddy-1.14.17.jar byte-buddy.jar

schilling · July 15, 2024, 10:13pm

Thank you very much lalaman!
This exactly fixed the issue for me. In the meantime, I also found this thread related to this problem: https://github.com/uyuni-project/uyuni/issues/8859

schilling · July 15, 2024, 10:28pm

This here also describes the issue:

github.com/uyuni-project/uyuni

New Uyuni install fails

opened 10:37AM - 03 Jul 24 UTC

darrynl

bug P5

### Problem description When doing a fresh installation of Uyuni, the Uyuni set…up fails. ### Steps to reproduce 1. Build new openSUSE 15.5 VM from openSUSE-Leap-15.5-DVD-x86_64-Build491.1-Media.iso. 4 cores, 16GB RAM, 40GB root filesytem, 5GB var filesystem, 10BG /var/cache filesystem, 3 GB swap 2. After build is complete, add 102GB /var/spacewalk filesystem and 52GB /var/lib/pgsql filesystem 3. Use zypper to confirm all updates applied. 4. Add entry to /etc/hosts so that machine can resolve it's own FQDN. 5. Install patterns-uyuni_server exactly as per: https://www.uyuni-project.org/uyuni-docs/en/uyuni/installation-and-upgrade/install-uyuni.html 6. Run Uyuni setup as detailed: https://www.uyuni-project.org/uyuni-docs/en/uyuni/installation-and-upgrade/uyuni-server-setup.html I made sure the passwords used adhere to the requirements specificed. 7. Setup fails with "Could not restart spacewalk services. Exit value: 1." ![image_2024-07-03_122121401](https://github.com/uyuni-project/uyuni/assets/19905416/31927177-f18b-4a0b-baef-e8c468d5b374) ... ### Uyuni version ```bash Information for package Uyuni-Server-release: --------------------------------------------- Repository : uyuni-server-stable Name : Uyuni-Server-release Version : 2024.05-230900.217.1.uyuni3 Arch : x86_64 Vendor : obs://build.opensuse.org/systemsmanagement:Uyuni Support Level : Level 3 Installed Size : 1.4 KiB Installed : Yes (automatically) Status : up-to-date Source package : Uyuni-Server-release-2024.05-230900.217.1.uyuni3.src Summary : Uyuni Server Description : Uyuni lets you efficiently manage physical, virtual, and cloud-based Linux systems. It provides automated and cost-effective configuration and software management, asset management, and system provisioning. ``` ### Uyuni proxy version (if used) ```bash N/A ``` ### Useful logs ```bash Installation log (domain name replaced with xxxxxx): Installation log of Uyuni Command: /usr/bin/spacewalk-setup hibernate.connection.driver_proto hibernate.dialect hibernate.connection.driver_class readline() on unopened filehandle TARGET at /usr/bin/rhn-config-satellite.pl line 72. hibernate.connection.driver_proto hibernate.connection.driver_class hibernate.dialect db_host db_name db_password db_user db_port db_backend db_host db_backend db_name db_password db_port db_user Shutting down spacewalk services... Done. Enabling spacewalk services... Done product_name /var/lib/rhn/rhn-satellite-prep/etc/rhn/rhn.conf /var/lib/rhn/rhn-satellite-prep/etc/rhn/rhn.conf.2024-07-03_09:53:25.067683 /var/lib/rhn/rhn-satellite-prep/etc -> /etc /var/lib/rhn/rhn-satellite-prep/etc/rhn -> /etc/rhn /var/lib/rhn/rhn-satellite-prep/etc/rhn/rhn.conf -> /etc/rhn/rhn.conf * Making backup of /etc/rhn/rhn.conf to /etc/sysconfig/rhn/backup-2024-07-03-11:53/etc/rhn/rhn.conf /var/lib/rhn/rhn-satellite-prep/etc/rhn/rhn.conf.2024-07-03_09:53:25.067683 -> /etc/rhn/rhn.conf.2024-07-03_09:53:25.067683 Generating private CA key: /root/ssl-build/RHN-ORG-PRIVATE-SSL-KEY Generating public CA certificate: /root/ssl-build/RHN-ORG-TRUSTED-SSL-CERT Using distinguishing variables: --set-country = "ZA" --set-state = "Western Cape" --set-city = "Cape Town" --set-org = "xxxxxx" --set-org-unit = "Technical" --set-common-name = "apoc.xxxxxx.co.za" --set-email = "" CA Cert for OS Images: Packaging /root/ssl-build/RHN-ORG-TRUSTED-SSL-CERT into /srv/susemanager/salt/images/rhn-org-trusted-ssl-cert-osimage-1.0-1.noarch.rpm CA Cert for OS Images: Packaging /root/ssl-build/RHN-ORG-TRUSTED-SSL-CERT into /srv/susemanager/salt/images/rhn-org-trusted-ssl-cert-osimage-sle11-1.0-1.noarch.rpm Generating the web server's SSL private key: /root/ssl-build/apoc.xxxxxx/server.key Generating web server's SSL certificate request: /root/ssl-build/apoc.xxxxxx/server.csr Using distinguished names: --set-country = "ZA" --set-state = "Western Cape" --set-city = "Cape Town" --set-org = "xxxxxx" --set-org-unit = "Technical" --set-hostname = "apoc.xxxxxx.co.za" --set-email = "uyuni@xxxxxx.co.za" Rotated: rhn-ca-openssl.cnf --> rhn-ca-openssl.cnf.1 Generating/signing web server's SSL certificate: server.crt After changing the server certificate please execute: $> spacewalk-service stop $> systemctl restart postgresql.service $> spacewalk-service start As the CA certificate has been changed, please deploy the CA to all registered clients. On salt-managed clients, you can do this by applying the highstate. /var/lib/rhn/rhn-satellite-prep/etc/rhn -> /etc/rhn /var/lib/rhn/rhn-satellite-prep/etc/rhn/rhn.conf -> /etc/rhn/rhn.conf /var/lib/rhn/rhn-satellite-prep/etc/rhn/rhn.conf.2024-07-03_09:53:25.067683 -> /etc/rhn/rhn.conf.2024-07-03_09:53:25.067683 * Making backup of /etc/rhn/rhn.conf.2024-07-03_09:53:25.067683 to /etc/sysconfig/rhn/backup-2024-07-03-11:53/etc/rhn/rhn.conf.2024-07-03_09:53:25.067683 Shutting down spacewalk services... Done. Starting spacewalk services... Checking DB schema and running DB schema upgrade if needed. This may take a while. Call the following command to see progress: journalctl -f -u uyuni-check-database.service A dependency job for spacewalk.target failed. See 'journalctl -xe' for details. FAILED journalctl -xe apoc:/var/log/rhn # journalctl -xe Jul 03 11:54:14 apoc server[4406]: 03-Jul-2024 11:54:14.625 INFO [pool-4-thread-1] org.apache.catalina.loader.WebappClassLoaderBase.checkStateForResourceLoading Illega> Jul 03 11:54:14 apoc server[4406]: java.lang.IllegalStateException: Illegal access: this web application instance has been stopped already. Could not load [jav> Jul 03 11:54:14 apoc server[4406]: at org.apache.catalina.loader.WebappClassLoaderBase.checkStateForResourceLoading(WebappClassLoaderBase.java:1349) Jul 03 11:54:14 apoc server[4406]: at org.apache.catalina.loader.WebappClassLoaderBase.checkStateForClassLoading(WebappClassLoaderBase.java:1337) Jul 03 11:54:14 apoc server[4406]: at org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1174) Jul 03 11:54:14 apoc server[4406]: at org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1141) Jul 03 11:54:14 apoc server[4406]: at com.suse.manager.webui.websocket.WebsocketHeartbeatService.clearStaleSessions(WebsocketHeartbeatService.java:84) Jul 03 11:54:14 apoc server[4406]: at com.suse.manager.webui.websocket.WebsocketHeartbeatService.lambda$initScheduler$2(WebsocketHeartbeatService.java:> Jul 03 11:54:14 apoc server[4406]: at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) Jul 03 11:54:14 apoc server[4406]: at java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305) Jul 03 11:54:14 apoc server[4406]: at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.ja> Jul 03 11:54:14 apoc server[4406]: at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) Jul 03 11:54:14 apoc server[4406]: at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) Jul 03 11:54:14 apoc server[4406]: at java.base/java.lang.Thread.run(Thread.java:829) Jul 03 11:54:30 apoc sshd[6726]: Accepted keyboard-interactive/pam for root from 192.168.101.115 port 55227 ssh2 Jul 03 11:54:30 apoc systemd-logind[971]: New session 3 of user root. ░░ Subject: A new session 3 has been created for user root ░░ Defined-By: systemd ░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel ░░ Documentation: sd-login(3) ░░ ░░ A new session with the ID 3 has been created for the user root. ░░ ░░ The leading process of the session is 6726. Jul 03 11:54:30 apoc systemd[1]: Started Session 3 of User root. ░░ Subject: A start job for unit session-3.scope has finished successfully ░░ Defined-By: systemd ░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel ░░ ░░ A start job for unit session-3.scope has finished successfully. ░░ ░░ The job identifier is 2593. Jul 03 11:54:30 apoc sshd[6726]: pam_unix(sshd:session): session opened for user root by (uid=0) Jul 03 11:55:17 apoc spacewalk-startup-helper[6094]: taskomatic still not up and running Jul 03 11:55:17 apoc systemd[1]: Finished Spacewalk wait for taskomatic. ░░ Subject: A start job for unit spacewalk-wait-for-taskomatic.service has finished successfully ░░ Defined-By: systemd ░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel ░░ ░░ A start job for unit spacewalk-wait-for-taskomatic.service has finished successfully. ░░ ░░ The job identifier is 1843. Jul 03 11:55:20 apoc sshd[6904]: Connection closed by 192.168.101.15 port 34582 [preauth] ``` ### Additional information _No response_

system · July 22, 2024, 10:29pm

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.