- rocky - RESF Lists

TPM errors/warngings
by Lana Deere 11 Sep '23

11 Sep '23

On Rocky Linux 9.2, I am seeing miscellanous programs (e.g. Matlab) spew a bunch of messages which look TPM-relasted. First I get a small number of messages all at once, WARNING:fapi:src/tss2-fapi/ifapi_io.c:282:ifapi_io_check_create_dir() Directory /var/lib/tpm2-tss/system/keystore/policy does not exist, creating (skipped several errors that it couldn't be created, then) ERROR:fapi:src/tss2-fapi/api/Fapi_Initialize.c:212:Fapi_Initialize_Finish() ErrorCode (0x0006000b) Keystore could not be initialize Maybe 30 seconds later I get a longer set of errors which say things like CRITICAL: failed to allocate dbus proxy object: Error calling StartServiceByName for com.intel.tss2.Tabrmd: Timeout was reached WARNING: tcti:src/tss2-tcti/tctildr.c:79:tcti_from_init() TCTI init for function 0x7f9ae5e3c210 failed with a0008 ERROR: tcti:src/tss2-tcti/tctildr-dl.c:154:tcti_from_file() Could not initialize TCTI file: libtss2-tcti-tabrmd.so.0 etc. Some of the messages reference /dev/tpm0, but this system has no TPM in the hardware. How do I make the messages go away? .. Lana (lana.deere(a)gmail.com)

1 0

Very confused about Rocky Linux version
by Turritopsis Dohrnii Teo En Ming 07 Jul '23

07 Jul '23

Subject: Very confused about Rocky Linux version Good day from Singapore, I am very confused about my Rocky Linux version. My Rocky Linux CLI console shows that I have Rocky Linux 9.2. [root@vmi701385 ~]# cat /etc/os-release NAME="Rocky Linux" VERSION="9.2 (Blue Onyx)" ID="rocky" ID_LIKE="rhel centos fedora" VERSION_ID="9.2" PLATFORM_ID="platform:el9" PRETTY_NAME="Rocky Linux 9.2 (Blue Onyx)" ANSI_COLOR="0;32" LOGO="fedora-logo-icon" CPE_NAME="cpe:/o:rocky:rocky:9::baseos" HOME_URL="https://rockylinux.org/" BUG_REPORT_URL="https://bugs.rockylinux.org/" SUPPORT_END="2032-05-31" ROCKY_SUPPORT_PRODUCT="Rocky-Linux-9" ROCKY_SUPPORT_PRODUCT_VERSION="9.2" REDHAT_SUPPORT_PRODUCT="Rocky Linux" REDHAT_SUPPORT_PRODUCT_VERSION="9.2" But when I login to my Webmin web UI, the dashboard says I have Rocky Linux 9.1. Do I have Rocky Linux 9.1 or 9.2? Anyone can advise? Thank you. Regards, Mr. Turritopsis Dohrnii Teo En Ming Targeted Individual in Singapore Blogs: https://tdtemcerts.blogspot.com https://tdtemcerts.wordpress.com GIMP also stands for Government-Induced Medical Problems.

2 2

ldapmodify can't contact LDAP server inside an podman container
by Meikel 23 Jun '23

23 Jun '23

Hi folks, inside Podman I run Rocky Linux 8 podman run -dt --name rl8 docker.io/rockylinux/rockylinux:8 podman exec -it rl8 bash This is not for production, I use it as an interactive shell for playing around with OpenLDAP server for leraning purposes. After I finished my leraning I' ll get rid of the container and the image. Because inside the container I do not have any infrastructure like "systemd" I start OpenLDAP server simply with slapd and it seems to be running as I can see with ps aux | grep slapd root 547 0.0 2.2 482424 371196 ? Ssl 11:28 0:00 slapd root 553 0.0 0.0 16404 2176 pts/1 S+ 12:07 0:00 grep --color=auto slapd Now from inside the same container I want to run ldapmodify against that OpenLDAP server but I get an error: ldapmodify -Q -Y EXTERNAL -H ldapi:/// -d 5 -f grund.ldif ldap_url_parse_ext(ldapi:///) ldap_create ldap_url_parse_ext(ldapi:///??base) ldap_sasl_interactive_bind: user selected: EXTERNAL ldap_int_sasl_bind: EXTERNAL ldap_new_connection 1 1 0 ldap_int_open_connection ldap_connect_to_path ldap_new_socket: 4 ldap_connect_to_path: Trying /var/run/ldapi ldap_connect_timeout: fd: 4 tm: -1 async: 0 ldap_ndelay_on: 4 ldap_close_socket: 4 ldap_msgfree ldap_err2string ldap_sasl_interactive_bind_s: Can't contact LDAP server (-1) In the /etc/openldap/ldap.conf file I did NOT specify the BASE and URI configurations, not sure if this might cause a problem. With Netcat I see nc localhost 636 Ncat: Connection refused. and time nc localhost 389 ... nothing happesn, seems to hang forever Why can' t I connect from ldapmodify to the slapd? How can I further investigate the problem? Regards, Meikel

2 2

mock fails on lxc container with error read-only filesystem (selinux-related)
by Сергей Спиридонов 11 May '23

11 May '23

Hi I am running rocky linux in privileged lxc container on Debian 11 host. If I try to build any rpm I am getting an error from mock ERROR: Could not create dir /var/lib/mock/rocky+epel-9-x86_64-bootstrap/root/sys/fs/selinux. Error: [Errno 30] Read-only file system: '/var/lib/mock/rocky+epel-9-x86_64-bootstrap/root/sys/fs/selinux' I guess the reason is that selinux is disabled on Debian. Is there a way to tell mock to work with selinux disabled? I am afraid proper set up of selinux on Debian host would be not simple. -- Best regards, Sergey Spiridonov

2 1

Virt-install'ing Rocky with location url & kickstart not working
by Jos Vos 01 May '23

01 May '23

Hi, With CentOS I’m used to install VM’s using kickstart without local media (e.g. a boot iso) with a command like: virt-install ... -location "http://..../9-stream/BaseOS/x86_64/os/" \ --initrd-inject ks.cfg --extra-args="inst.ks=file:///ks.cfg" When I try a similar command with Rocky Linux (I tried both .../os/ and .../kickstart/ in the URL paths) it loads vmlinuz and initrd.img, but it fails later: for version 8 and 9 different things happen (timeouts in 8 and endless loops in 9). Is there a way to achieve a virt-install with kickstart (and without downloading and mounting stuff)? Thanks, Jos -- -- Jos Vos <jos(a)xos.nl> -- X/OS Experts in Open Systems BV | Office: +31 20 6938364 -- Amsterdam, The Netherlands | Mobile: +31 6 26216181

2 3

How to configure equal cost multi-path routing with NetworkManager?
by Uwe Sauter 28 Apr '23

28 Apr '23

Hi folks, With CentOS 7/Rocky 8 and "network-scripts" I was able to configure static routes using "equal cost multi-path" (ECMP) routing. /etc/sysconfig/network-scripts/route-eth0 would contain a line like 172.16.0.0/16 nexthop via 192.168.1.250 nexthop via 192.168.1.251 which would then look like: # ip r default via 192.168.1.254 dev eth0 172.16.0.0/16 nexthop via 192.168.1.250 dev eth0 weight 1 nexthop via 192.168.1.251 dev eth0 weight 1 It seems that the NetworkManager keyfile format is not able to handle that situation. How can I configure static ECMP routes with Rocky 8/9 and NetworkManager? Thanks, Uwe

2 4

Re: [rocky-announce] Installing Rocky 9.x in a system with CPU not x86-64-v2
by John Broome 24 Apr '23

24 Apr '23

Mentioning exactly the model of the CPU you're trying to install on would get you a much more accurate answer. On Fri, Apr 21, 2023 at 11:35 AM Gestió Servidors via rocky-announce < rocky-announce(a)lists.resf.org> wrote: > Hello, > > > > if there any way to install Rocky-9.x in a system with CPU not x86-64-v2? > Any kernel boot install parameter or similar? > > > > Thanks > > > > > > > _______________________________________________ > rocky-announce mailing list -- rocky-announce(a)lists.resf.org > To unsubscribe send an email to rocky-announce-leave(a)lists.resf.org >

2 1

Re: Installing Rocky 9.x in a system with CPU not x86-64-v2
by BARESICH, JIM 21 Apr '23

21 Apr '23

No sir, it’s a requirement for the libc version the kernel is built on and is part of the OS. Jim Baresich AT&T - Infrastructure Technology Planning and Engineering Mobile - 7329273072 MS Teams – 9083261982 Chat on MS Teams<https://teams.microsoft.com/l/chat/0/0?users=jb2592@att.com&topicname=Chat> From: Gestió Servidors via rocky-announce <rocky-announce(a)lists.resf.org> Sent: Friday, April 21, 2023 11:35 AM To: rocky-announce(a)lists.resf.org Cc: Gestió Servidors <sysadmin.caos(a)uab.cat> Subject: [rocky-announce] Installing Rocky 9.x in a system with CPU not x86-64-v2 Hello, if there any way to install Rocky-9.x in a system with CPU not x86-64-v2? Any kernel boot install parameter or similar? Thanks

1 0

Issues installing the minimum version of RL 9.1
by H 31 Mar '23

31 Mar '23

I am new to RL and decided to convert a CentOS 7 system to RL 9.1. This also entailed repartitioning the system since I wanted a combination of LUKS, LVM and RAID1. I ran into two issues with Anaconda, the same installation software RHEL uses, suggesting a lack of robustness. First, the partition scheme with LUKS, LVM and RAID1 took a lot of tinkering to get right. If there was something wrong the script aborted and I had to start over again booting the installation DVD. Second, a couple of times the script got stuck on 'configuring storage' and then aborted. Back to booting the installation DVD. In the end I finished the installation but I was amazed that the script is not more robust after being widely used for multiple versions of the RHEL software. How widely are these problems encountered?

5 9

[Rocky8.7] Question about pv_mmu_ops kernel header field
by 박영준 26 Mar '23

26 Mar '23

I debug the rocky 8.7 kernel. (4.18.0-425.3.1.el8.x86_64 and 4.18.0-425.13.1.el8.x86_64) for our company module issue. And I have a question . why pv_mmu_ops notify_page_enc_status_changed field is moved to reserved1 field on (4.18.0-425.13.1.el8.x86_64)? I think pv_mmu_ops structure reserved filed may exist for compatibility. By moving field to reserved, size reduced. (I think notify_page_enc_status_changed location dummy field needed or must not change the location) Is there any reson I don't know ? 4.18.0-425.3.1.el8.x86_64 crash> struct pv_mmu_ops struct pv_mmu_ops { unsigned long (*read_cr2)(void); void (*notify_page_enc_status_changed)(unsigned long, int, bool); void (*write_cr2)(unsigned long); unsigned long (*read_cr3)(void); void (*write_cr3)(unsigned long); void (*activate_mm)(struct mm_struct *, struct mm_struct *); void (*dup_mmap)(struct mm_struct *, struct mm_struct *); void (*exit_mmap)(struct mm_struct *); void (*flush_tlb_user)(void); void (*flush_tlb_kernel)(void); void (*flush_tlb_one_user)(unsigned long); void (*flush_tlb_others)(const struct cpumask *, const struct flush_tlb_info *); void (*tlb_remove_table)(struct mmu_gather *, void *); int (*pgd_alloc)(struct mm_struct *); void (*pgd_free)(struct mm_struct *, pgd_t *); void (*alloc_pte)(struct mm_struct *, unsigned long); void (*alloc_pmd)(struct mm_struct *, unsigned long); void (*alloc_pud)(struct mm_struct *, unsigned long); void (*alloc_p4d)(struct mm_struct *, unsigned long); void (*release_pte)(unsigned long); void (*release_pmd)(unsigned long); void (*release_pud)(unsigned long); void (*release_p4d)(unsigned long); void (*set_pte)(pte_t *, pte_t); void (*set_pte_at)(struct mm_struct *, unsigned long, pte_t *, pte_t); void (*set_pmd)(pmd_t *, pmd_t); pte_t (*ptep_modify_prot_start)(struct vm_area_struct *, unsigned long, pte_t *); void (*ptep_modify_prot_commit)(struct vm_area_struct *, unsigned long, pte_t *, pte_t); struct paravirt_callee_save pte_val; struct paravirt_callee_save make_pte; struct paravirt_callee_save pgd_val; struct paravirt_callee_save make_pgd; void (*set_pud)(pud_t *, pud_t); struct paravirt_callee_save pmd_val; struct paravirt_callee_save make_pmd; struct paravirt_callee_save pud_val; struct paravirt_callee_save make_pud; void (*set_p4d)(p4d_t *, p4d_t); struct paravirt_callee_save p4d_val; struct paravirt_callee_save make_p4d; void (*set_pgd)(pgd_t *, pgd_t); struct pv_lazy_ops lazy_mode; void (*set_fixmap)(unsigned int, phys_addr_t, pgprot_t); unsigned long rh_reserved1; unsigned long rh_reserved2; unsigned long rh_reserved3; unsigned long rh_reserved4; } SIZE: 392 4.18.0-425.13.1.el8.x86_64 crash> struct pv_mmu_ops struct pv_mmu_ops { unsigned long (*read_cr2)(void); void (*write_cr2)(unsigned long); unsigned long (*read_cr3)(void); void (*write_cr3)(unsigned long); void (*activate_mm)(struct mm_struct *, struct mm_struct *); void (*dup_mmap)(struct mm_struct *, struct mm_struct *); void (*exit_mmap)(struct mm_struct *); void (*flush_tlb_user)(void); void (*flush_tlb_kernel)(void); void (*flush_tlb_one_user)(unsigned long); void (*flush_tlb_others)(const struct cpumask *, const struct flush_tlb_info *); void (*tlb_remove_table)(struct mmu_gather *, void *); int (*pgd_alloc)(struct mm_struct *); void (*pgd_free)(struct mm_struct *, pgd_t *); void (*alloc_pte)(struct mm_struct *, unsigned long); void (*alloc_pmd)(struct mm_struct *, unsigned long); void (*alloc_pud)(struct mm_struct *, unsigned long); void (*alloc_p4d)(struct mm_struct *, unsigned long); void (*release_pte)(unsigned long); void (*release_pmd)(unsigned long); void (*release_pud)(unsigned long); void (*release_p4d)(unsigned long); void (*set_pte)(pte_t *, pte_t); void (*set_pte_at)(struct mm_struct *, unsigned long, pte_t *, pte_t); void (*set_pmd)(pmd_t *, pmd_t); pte_t (*ptep_modify_prot_start)(struct vm_area_struct *, unsigned long, pte_t *); void (*ptep_modify_prot_commit)(struct vm_area_struct *, unsigned long, pte_t *, pte_t); struct paravirt_callee_save pte_val; struct paravirt_callee_save make_pte; struct paravirt_callee_save pgd_val; struct paravirt_callee_save make_pgd; void (*set_pud)(pud_t *, pud_t); struct paravirt_callee_save pmd_val; struct paravirt_callee_save make_pmd; struct paravirt_callee_save pud_val; struct paravirt_callee_save make_pud; void (*set_p4d)(p4d_t *, p4d_t); struct paravirt_callee_save p4d_val; struct paravirt_callee_save make_p4d; void (*set_pgd)(pgd_t *, pgd_t); struct pv_lazy_ops lazy_mode; void (*set_fixmap)(unsigned int, phys_addr_t, pgprot_t); union { void (*notify_page_enc_status_changed)(unsigned long, int, bool); struct { unsigned long rh_reserved1; } rh_kabi_hidden_308; union { <no data fields> }; }; unsigned long rh_reserved2; unsigned long rh_reserved3; unsigned long rh_reserved4; } SIZE: 384 4.18.0-425.13.1.el8.x86_64 Thanks "안전해서 더욱 자유로운 세상 – 안랩" youngjun park / Base Technology team / Endpoint research laboratory T 031-722-8369 F 031-722-8277 youngjun.park(a)ahnlab.com www.ahnlab.com<http://www.ahnlab.com/> (13493) 경기도 성남시 분당구 판교역로 220 (주)안랩 본 메일은 지정된 수취인만을 위해 작성되었으며, 중요한 정보나 저작권을 포함하고 있을 수 있습니다. 어떠한 권한 없이, 본 문서에 포함된 정보의 전부 또는 일부를 무단으로 제3자에게 공개, 배포, 복사 또는 사용하는 것을 엄격히 금지합니다. 만약, 본 메일이 잘못 전송된 경우, 발신인 또는 당사에 알려주시고, 본 메일을 즉시 삭제하여 주시기 바랍니다.

2 2

2026

2025

2024

2023

2022

2021

rocky