spacewalk-repo-sync take too much time

[gabardyne]

Question

When I do "mgrctl exec "spacewalk-repo-sync --no-strict -p rockylinux8-x86_64"", the synchronisation is very slow. Although the server is far from overload. What can possibly block that?

Information for package Uyuni-Server-release:

Repository : @System Name : Uyuni-Server-release Version : 2024.12-241000.225.1.uyuni5 Arch : x86_64 Vendor : obs://build.opensuse.org/systemsmanagement:Uyuni Support Level : unknown Installed Size : 1.4 KiB Installed : Yes (automatically) Status : up-to-date Source package : Uyuni-Server-release-2024.12-241000.225.1.uyuni5.src Upstream URL : https://www.uyuni-project.org/ 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.

[rjmateus]

I would advise checking the database properties and see if they are stunned. You can check some more information in here: https://www.uyuni-project.org/uyuni-docs/en/uyuni/specialized-guides/large-deployments/tuning.html

[gabardyne]

I would advise checking the database properties and see if they are stunned. You can check some more information in here: https://www.uyuni-project.org/uyuni-docs/en/uyuni/specialized-guides/large-deployments/tuning.html

Hello Ricardo,

Thanks for reply. I've already checked the DB, and done some tuning, but no results.

When I check the postgresql service, I see a lot of threads idle, and nothing strange in the log.

uyuni-server:/var/cache/rhn/reposync/1/RockyLinux_8_Main_x86_64/etc/zypp/repos.d # systemctl status postgresql ● postgresql.service - PostgreSQL database server Loaded: loaded (/usr/lib/systemd/system/postgresql.service; disabled; preset: disabled) Active: active (running) since Tue 2025-06-03 10:52:25 CEST; 23min ago Process: 345 ExecStart=/usr/share/postgresql/postgresql-script start (code=exited, status=0/SUCCESS) Main PID: 371 (postgres) CGroup: /machine.slice/libpod-9bd20caae218fd45c16ca60eea8a16bd3e70085b80c8051972cc738d929e98d7.scope/system.slice/postgresql.service ├─ 371 /usr/lib/postgresql16/bin/postgres -D /var/lib/pgsql/data ├─ 372 "postgres: logger " ├─ 373 "postgres: checkpointer " ├─ 374 "postgres: background writer " ├─ 376 "postgres: walwriter " ├─ 377 "postgres: autovacuum launcher " ├─ 378 "postgres: archiver " ├─ 379 "postgres: logical replication launcher " ├─1005 "postgres: uyuni_db uyuni 127.0.0.1(57588) idle" ├─1006 "postgres: uyuni_db uyuni 127.0.0.1(57590) idle" ├─1007 "postgres: uyuni_db uyuni 127.0.0.1(57600) idle" ├─1033 "postgres: uyuni_db uyuni 127.0.0.1(57604) idle" ├─1034 "postgres: uyuni_db uyuni 127.0.0.1(57606) idle" ├─1035 "postgres: uyuni_db uyuni 127.0.0.1(57602) idle" ├─1036 "postgres: uyuni_db uyuni 127.0.0.1(57618) idle" ├─1037 "postgres: uyuni_db uyuni 127.0.0.1(57632) idle" ├─1039 "postgres: uyuni_db uyuni 127.0.0.1(57644) idle" ├─1044 "postgres: uyuni_db uyuni 127.0.0.1(57660) idle" ├─1172 "postgres: uyuni_db uyuni ::1(56022) idle" ├─3266 "postgres: uyuni_db uyuni 127.0.0.1(57552) idle" ├─3340 "postgres: uyuni_db uyuni 127.0.0.1(33602) idle" ├─3648 "postgres: uyuni_db uyuni 127.0.0.1(44234) idle" ├─3649 "postgres: uyuni_db uyuni 127.0.0.1(44242) SELECT" ├─3650 "postgres: uyuni_db uyuni 127.0.0.1(44248) SELECT" ├─3718 "postgres: uyuni_db uyuni 127.0.0.1(44286) idle" ├─3719 "postgres: uyuni_db uyuni 127.0.0.1(44280) idle" ├─3720 "postgres: uyuni_db uyuni 127.0.0.1(44288) idle" ├─3735 "postgres: uyuni_db uyuni 127.0.0.1(44308) idle" ├─6314 "postgres: uyuni_db uyuni 127.0.0.1(45670) idle" ├─7397 "postgres: uyuni_db uyuni 127.0.0.1(55198) idle" ├─7961 "postgres: uyuni_db uyuni 127.0.0.1(45182) idle" ├─7963 "postgres: uyuni_db uyuni 127.0.0.1(45200) idle" └─7968 "postgres: uyuni_db uyuni 127.0.0.1(45226) idle"

[gabardyne]

I change those options:

max_connections = 400 shared_buffers = 4096MB

[gabardyne]

I also have those warnings in taskomatic log:

2025-06-04 13:57:00,657 [DefaultQuartzScheduler_Worker-20] WARN com.redhat.rhn.taskomatic.task.SystemOverviewUpdateQueue - Maximum number of workers already put ... skipping. 2025-06-04 13:58:00,079 [DefaultQuartzScheduler_Worker-73] WARN com.redhat.rhn.taskomatic.task.ErrataCacheTask - Maximum number of workers already put ... skipping.

How can I update maximum workers number?

[gabardyne]

Hello,

Finally we installed the DB on a different server. It's ok now

Gab