Some more information about my doing/setup:
- My setup is only intend for developing/evaluation/training purpose, so it is very small:
4x cpus and 8GB memory - running only foreman on this system worked fine for months
- For comparison I do an installation in a virtual system (kvm) with the same performance data as my physical system. There it works !
- The only obvious different I can see til now is the disk layout: In the vm it is all one partition, on the physical system it looks like this
[root@scotty ~]# df -h
Filesystem Size Used Avail Use% Mounted on
devtmpfs 3.8G 0 3.8G 0% /dev
tmpfs 3.8G 28K 3.8G 1% /dev/shm
tmpfs 3.8G 8.9M 3.8G 1% /run
tmpfs 3.8G 0 3.8G 0% /sys/fs/cgroup
/dev/mapper/vgsys-lvroot 16G 3.1G 12G 21% /
/dev/mapper/vgsys-lvpgsql 7.9G 138M 7.3G 2% /var/lib/pgsql
/dev/mapper/vgsys-lvforeman 976M 385M 525M 43% /var/lib/foreman
/dev/mapper/vgsys-lvhome 976M 2.6M 907M 1% /home
/dev/mapper/vgsys-lvlog 976M 55M 855M 7% /var/log
/dev/mapper/vgsys-lvtmp 2.0G 13M 1.8G 1% /tmp
/dev/sdb2 976M 221M 689M 25% /boot
/dev/mapper/vgsys-lvopt 976M 236M 674M 26% /opt
/dev/sdb1 599M 6.9M 592M 2% /boot/efi
/dev/mapper/vgdata-lvtftp 976M 4.4M 905M 1% /var/lib/tftpboot
/dev/mapper/vgdata-lvwiki 976M 2.6M 907M 1% /var/www/dokuwiki
/dev/mapper/vgdata-lvpuppet 976M 2.6M 907M 1% /etc/puppetlabs/code
/dev/mapper/vgdata-lvpulp 9.8G 40M 9.3G 1% /var/lib/pulp
/dev/mapper/vgdata-lvqpid 976M 15M 894M 2% /var/lib/qpidd
tmpfs 767M 0 767M 0% /run/user/0
[root@scotty ~]#
- differing from the instructions at What is the state of Katello support on EL8 - #8 by ehelms for rhel it is not powertools but codeready-builder
- I saw some hints in the logs regarding selinux, so I try to set selinux to permissive (with no luck)
- no selinux profiles are enabled
- cockpit is disabled on the system because of port conflicts with the smart-proxy (9090)