Discuss

discuss@lists.centos.org

2 participants
34758 discussions

Re: [CentOS] SElinux AVC signull
by Sean 18 Jan '19

18 Jan '19

Hi Leon, I don't have access to a CentOS 6.10 system handy, but it looks like a policy issue. If I take you're ausearch output and pipe it to audit2allow on my CentOS 7.6 system, I get the following: #============= httpd_t ============== #!!!! This avc is allowed in the current policy allow httpd_t httpd_sys_script_t:process signull; Noting that on my 7.6 system with selinux enforcing with selinux policy packages at version 3.13.1-229, it notes that your denial would not happen. If you don't have it installed policycoreutils-python provides the audit2allow and audit2why binaries which can help you generate a policy to avoid this denial if you want. Also, I often find that to truly diagnose the issue, I need to run the following: # semodule --disable_dontaudit --build # setenforce permissive # tail -f /var/log/audit/audit.log | grep denied | tee ~/denials.out ... then reproduce the problem, and kill the tail. The resulting denials.out file will have a lot of unrelated denials, but if you run audit2allow against the entire file, you'll be able to determine which ones are not relevant by the comments produced (much like above where it told us the "avc is allowed"). You can also use this to generate a custom policy module for your system. Sometimes there are denials that are not audited which are relevant to the problem, which seems problematic to me...that there is a default set of things that get denied but do not appear in the audit logs. That's a different conversation though. Anyway, after the data is collected for the denials.out file you can reset to your normal operating stance... # semodule --build # setenforce enforcing From: Leon Fauster <leonfauster(a)googlemail.com> To: CentOS mailing list <centos(a)centos.org> Cc: Bcc: Date: Thu, 17 Jan 2019 18:35:23 +0100 Subject: [CentOS] SElinux AVC signull I have some perl scripts running via CGI to print some monitoring informations out. # cat /etc/redhat-release CentOS release 6.10 (Final) # getenforce Enforcing # LANG=C ausearch -m avc --start today type=SYSCALL msg=audit(1547733474.941:28): arch=c000003e syscall=62 success=no exit=-13 a0=641 a1=0 a2=7f33500079b0 a3=31372f656d6f7268 items=0 ppid=1399 pid=1439 auid=4294967295 uid=48 gid=48 euid=48 suid=48 fsuid=48 egid=48 sgid=48 fsgid=48 tty=(none) ses=4294967295 comm="httpd" exe="/opt/rh/httpd24/root/usr/sbin/httpd" subj=system_u:system_r:httpd_t:s0 key=(null) type=AVC msg=audit(1547733474.941:28): avc: denied { signull } for pid=1439 comm="httpd" scontext=system_u:system_r:httpd_t:s0 tcontext=system_u:system_r:httpd_sys_script_t:s0 tclass=process I see a lot of such entries but I don't see any service misbehaviour. All scripts are running fine. Any hints how to classify this AVC; "Denied Signull"?

2 1

C 7.6, radeon
by mark 18 Jan '19

18 Jan '19

Hi, folks, Got a user that's recently(? been having odd things with her workstation video. This morning, in the logs, long before she got in, I saw a ton of errors Jan 18 08:06:50 <workstation> kernel: VM fault (0x04, vmid 1) at page 10, write from CP (48) Jan 18 08:06:50 <workstation> kernel: radeon 0000:01:00.0: GPU fault detected: 146 0x01433014 Jan 18 08:06:50 <workstation> kernel: radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x0000000A Jan 18 08:06:50 <workstation> kernel: radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x03030014 I see that radeon.ko is part of the kernel, and there's no updates. She running kernel 3.10.0-957.1.3.el7.x86_64. I see no errors in Xorg.0.log. Anyone got a clue, or see this error? mark

1 0

SElinux AVC signull
by Leon Fauster 17 Jan '19

17 Jan '19

I have some perl scripts running via CGI to print some monitoring informations out. # cat /etc/redhat-release CentOS release 6.10 (Final) # getenforce Enforcing # LANG=C ausearch -m avc --start today type=SYSCALL msg=audit(1547733474.941:28): arch=c000003e syscall=62 success=no exit=-13 a0=641 a1=0 a2=7f33500079b0 a3=31372f656d6f7268 items=0 ppid=1399 pid=1439 auid=4294967295 uid=48 gid=48 euid=48 suid=48 fsuid=48 egid=48 sgid=48 fsgid=48 tty=(none) ses=4294967295 comm="httpd" exe="/opt/rh/httpd24/root/usr/sbin/httpd" subj=system_u:system_r:httpd_t:s0 key=(null) type=AVC msg=audit(1547733474.941:28): avc: denied { signull } for pid=1439 comm="httpd" scontext=system_u:system_r:httpd_t:s0 tcontext=system_u:system_r:httpd_sys_script_t:s0 tclass=process I see a lot of such entries but I don't see any service misbehaviour. All scripts are running fine. Any hints how to classify this AVC; "Denied Signull"? -- LF

1 0

CentOS-announce Digest, Vol 167, Issue 4
by centos-announce-request＠centos.org 17 Jan '19

17 Jan '19

Send CentOS-announce mailing list submissions to centos-announce(a)centos.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request(a)centos.org You can reach the person managing the list at centos-announce-owner(a)centos.org When replying, please edit your Subject line so it is more specific than "Re: Contents of CentOS-announce digest..." Today's Topics: 1. CESA-2019:0059 Important CentOS 7 libvncserver Security Update (Johnny Hughes) 2. CEBA-2019:0062 CentOS 6 cups BugFix Update (Johnny Hughes) 3. CEBA-2019:0063 CentOS 6 sssd BugFix Update (Johnny Hughes) 4. CEBA-2019:0064 CentOS 6 kernel BugFix Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Wed, 16 Jan 2019 16:58:43 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2019:0059 Important CentOS 7 libvncserver Security Update Message-ID: <20190116165843.GA29758(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2019:0059 Important Upstream details at : https://access.redhat.com/errata/RHSA-2019:0059 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: f9063672bd316bdb20907ca5477d6f7ee1aa0e057bd8dad70a76bfccd01de635 libvncserver-0.9.9-13.el7_6.i686.rpm 5b91b5ccf0f6dc305174707091e5b95d34c6d81fbaa13efce7041cfce07d7efb libvncserver-0.9.9-13.el7_6.x86_64.rpm 8adaa036f6ea9faba29c3e95e90fc83499a26d6b7b31993903b00d1a6e8f4f63 libvncserver-devel-0.9.9-13.el7_6.i686.rpm d17a31cb27129ad58d1ac49123ff1e2029c052f2f4961608d6b5ef1a6f483cc7 libvncserver-devel-0.9.9-13.el7_6.x86_64.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 2 Date: Wed, 16 Jan 2019 17:00:31 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEBA-2019:0062 CentOS 6 cups BugFix Update Message-ID: <20190116170031.GA29910(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2019:0062 Upstream details at : https://access.redhat.com/errata/RHBA-2019:0062 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: ae19fac733269fcbd488ea1c9c811883b0cd1f404ece42dd9d01ba479e468146 cups-1.4.2-80.el6_10.i686.rpm 9fbe0535c19671f54c5200871216fff5838e1d891733a780ca395fdb832d5c56 cups-devel-1.4.2-80.el6_10.i686.rpm 08ac58e388403758ffc76f35cd416b445f147956a67769b475a33972e84dbba9 cups-libs-1.4.2-80.el6_10.i686.rpm 232ec808cb65f41f52992350ddf78fc438e9d69f15b92f1751475d24a2d7f3d0 cups-lpd-1.4.2-80.el6_10.i686.rpm 9ddb2dab7f095c1a0f3b350944c429cd71c6d31456491ddeeef980095f3c5099 cups-php-1.4.2-80.el6_10.i686.rpm x86_64: 06d91b4bbea2a7c25090ed85caff95cd179179b2fe353944e2443da5f05342ad cups-1.4.2-80.el6_10.x86_64.rpm 9fbe0535c19671f54c5200871216fff5838e1d891733a780ca395fdb832d5c56 cups-devel-1.4.2-80.el6_10.i686.rpm 50a7345aaab5c79772830dc3d31edbbfa596dd898e925a6bb4c7136488cb044f cups-devel-1.4.2-80.el6_10.x86_64.rpm 08ac58e388403758ffc76f35cd416b445f147956a67769b475a33972e84dbba9 cups-libs-1.4.2-80.el6_10.i686.rpm 7a063ec88b995cbe796b412519e2e06d6d288429785fd8b102c3b87aee74ceae cups-libs-1.4.2-80.el6_10.x86_64.rpm f04c2d5d959a60259d2cb16cceddb4e40e6fdc819c97d3e2fe7adfe590b9ad18 cups-lpd-1.4.2-80.el6_10.x86_64.rpm c4f1c4934cddeeeb13c8efd8375a248fa6a50576753c13a72b06abbad891dfcd cups-php-1.4.2-80.el6_10.x86_64.rpm Source: d49aa1c4abe8c4ddfee1c2a795a4e5f99c329dfa0bb423388d6c6887055172b5 cups-1.4.2-80.el6_10.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 3 Date: Wed, 16 Jan 2019 17:00:46 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEBA-2019:0063 CentOS 6 sssd BugFix Update Message-ID: <20190116170046.GA30197(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2019:0063 Upstream details at : https://access.redhat.com/errata/RHBA-2019:0063 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: b22a1737a4e5697e44b3151c970a3433097410cf34039258b8fcfbfe8d1dc95b libipa_hbac-1.13.3-60.el6_10.2.i686.rpm 9579917eab870ae298b66132163c3d797a33aff256fa41b91394ca9581963de4 libipa_hbac-devel-1.13.3-60.el6_10.2.i686.rpm d2163b74511864ac8c115e3e45e647435eb99c7496cf182b3f84ad0958959ef0 libsss_idmap-1.13.3-60.el6_10.2.i686.rpm 7654514c0f4e2619b12f96cda69208d26fff1bf8ee49d7d723f7a2b04ac2898d libsss_idmap-devel-1.13.3-60.el6_10.2.i686.rpm 4a72cbcb94f17d7061d3ceec6ad78fb510f35c3c9b948f8c861e3547429324d9 libsss_nss_idmap-1.13.3-60.el6_10.2.i686.rpm 45c7ab78bf30829640762ae059fdfb2e57193fc9de962344ff37826b1d44bcdd libsss_nss_idmap-devel-1.13.3-60.el6_10.2.i686.rpm f35b71e0985e206b50dc63927886864dced1b5f36d1bef7573197808101d50ce libsss_simpleifp-1.13.3-60.el6_10.2.i686.rpm d86ab2a98c13f4c65ef7f9ef37b76c676c704bc30bc550cee8f889aadc950b60 libsss_simpleifp-devel-1.13.3-60.el6_10.2.i686.rpm cce1fa48695645e465a0aedc44f1e30b686c8b8c4ca32b58b4cdcec4a7d28a95 python-libipa_hbac-1.13.3-60.el6_10.2.i686.rpm 167017fa16eb91fa2b9dd702f844d3602d107c25db9f534e66e5a6396419b561 python-libsss_nss_idmap-1.13.3-60.el6_10.2.i686.rpm 47e22d53875a5a68df335b34c97ee3c7c26a62fcac0559730118a0525df2622c python-sss-1.13.3-60.el6_10.2.i686.rpm bfad805da74717748747662b2e40e6a04847737ca6e1ebd86a2f69d93d7af482 python-sssdconfig-1.13.3-60.el6_10.2.noarch.rpm af145bcfbe66b109d95d3583db38097e0f5bfd0fc034d7288e023fab7c86f5fe python-sss-murmur-1.13.3-60.el6_10.2.i686.rpm 6160b35856e1b77f1caa2a667eec9e187b1705ba7e076fc3112118e38d99c4b3 sssd-1.13.3-60.el6_10.2.i686.rpm 4fd8f81c72c5d182acf299fb7969d6468c5970de138bb66f2f516a7297a8cd49 sssd-ad-1.13.3-60.el6_10.2.i686.rpm 6a42040ae3d2ab2494f2c4d03d4b3b15df738a19e0f610083338607ae2791736 sssd-client-1.13.3-60.el6_10.2.i686.rpm 3b1b5c196ca1420669736dbe1bb00be2433f78fba8e592be01a89b845a77dd0c sssd-common-1.13.3-60.el6_10.2.i686.rpm 590c888642a8e7699133436c235d1e3d7cb44e8e4999d3220f9dd9a6457c57ae sssd-common-pac-1.13.3-60.el6_10.2.i686.rpm d4be7a8f81092c513ff5f8306d2fc9e2274f1387877fda51f3acb06b66cd4ec7 sssd-dbus-1.13.3-60.el6_10.2.i686.rpm 02bae49b270443bf5731afaa55ccc7f1fd9b2328438606a3843c26b379cc6820 sssd-ipa-1.13.3-60.el6_10.2.i686.rpm 4f9094c6e0cb3de191ae2966df24276511ec460063f1769872819cbda4ae7010 sssd-krb5-1.13.3-60.el6_10.2.i686.rpm 88b9c420282a5b5d80c8037980d0043bcbf8da1a7401520d73ba1707e292dcef sssd-krb5-common-1.13.3-60.el6_10.2.i686.rpm 9561ed3ec88d7fd79d9b30a7cb9fac45d9dd454f927b12341474b2d03dc7eb32 sssd-ldap-1.13.3-60.el6_10.2.i686.rpm fceb9bf37bb674eb0d50a04399267562b5dd5da8e200054e38c1c3b0fc895cc1 sssd-proxy-1.13.3-60.el6_10.2.i686.rpm 6266373e6038f672c05e0774718148187fa7e10339da25c447cd129c44473634 sssd-tools-1.13.3-60.el6_10.2.i686.rpm x86_64: b22a1737a4e5697e44b3151c970a3433097410cf34039258b8fcfbfe8d1dc95b libipa_hbac-1.13.3-60.el6_10.2.i686.rpm 4b8ba2a2eadd58d4650d33f9025e75d4fa12b5fe3be37cb7ec3bda67ae21eeea libipa_hbac-1.13.3-60.el6_10.2.x86_64.rpm 9579917eab870ae298b66132163c3d797a33aff256fa41b91394ca9581963de4 libipa_hbac-devel-1.13.3-60.el6_10.2.i686.rpm b9e3953546f9b0913615eb7fed07fa94091d41b35ea7fd5651713278626d4f06 libipa_hbac-devel-1.13.3-60.el6_10.2.x86_64.rpm d2163b74511864ac8c115e3e45e647435eb99c7496cf182b3f84ad0958959ef0 libsss_idmap-1.13.3-60.el6_10.2.i686.rpm 0bfc66082d0de5d35aeaf4e8d06ef7e2832d631bd718df6daf2cffd1aacb7061 libsss_idmap-1.13.3-60.el6_10.2.x86_64.rpm 7654514c0f4e2619b12f96cda69208d26fff1bf8ee49d7d723f7a2b04ac2898d libsss_idmap-devel-1.13.3-60.el6_10.2.i686.rpm c2d529420bb8a064b080d16b533838a76a2e54b1163fb07b7d0f2d055898d496 libsss_idmap-devel-1.13.3-60.el6_10.2.x86_64.rpm 4a72cbcb94f17d7061d3ceec6ad78fb510f35c3c9b948f8c861e3547429324d9 libsss_nss_idmap-1.13.3-60.el6_10.2.i686.rpm df7b79efc9d8345436cee514946c840c183ca65b59b7207caef938756d174b48 libsss_nss_idmap-1.13.3-60.el6_10.2.x86_64.rpm 45c7ab78bf30829640762ae059fdfb2e57193fc9de962344ff37826b1d44bcdd libsss_nss_idmap-devel-1.13.3-60.el6_10.2.i686.rpm 0c5b379f5c1c9eda709434e0b0afb079701afd5cd102d1b5898923656a16ceb2 libsss_nss_idmap-devel-1.13.3-60.el6_10.2.x86_64.rpm f35b71e0985e206b50dc63927886864dced1b5f36d1bef7573197808101d50ce libsss_simpleifp-1.13.3-60.el6_10.2.i686.rpm 30feb877eab60348fe8d664ba71e2adb831ffc8da2aa7b95474ff94e57a7cd78 libsss_simpleifp-1.13.3-60.el6_10.2.x86_64.rpm d86ab2a98c13f4c65ef7f9ef37b76c676c704bc30bc550cee8f889aadc950b60 libsss_simpleifp-devel-1.13.3-60.el6_10.2.i686.rpm 332d6c731a5513169a0e0c38c08f2e348b1602690d47386bf9193eecde22a43a libsss_simpleifp-devel-1.13.3-60.el6_10.2.x86_64.rpm c89fb8abb5b40d5408bd228e6b4285c5851298e9e544ab77abe81be793b7da40 python-libipa_hbac-1.13.3-60.el6_10.2.x86_64.rpm acf6a88d4248d90f1fccc20ac2a9c8b824eddb499202fef80b3b5202a0bed4d8 python-libsss_nss_idmap-1.13.3-60.el6_10.2.x86_64.rpm b24caa6e20691e3b8a81b95ef7a0287766bf47a6309c67e4cdd80489cef155b3 python-sss-1.13.3-60.el6_10.2.x86_64.rpm bfad805da74717748747662b2e40e6a04847737ca6e1ebd86a2f69d93d7af482 python-sssdconfig-1.13.3-60.el6_10.2.noarch.rpm a1c6ae6afe50e3499d06bdab308051371b0254fe3121af4c88fa7a806dcc4498 python-sss-murmur-1.13.3-60.el6_10.2.x86_64.rpm c9ff754eb80f31d4d86d8a09fd0566e901aa739b7f847647f93165c6044a82af sssd-1.13.3-60.el6_10.2.x86_64.rpm 07ea734345f5bcaea299c9bd619bc5ab7504f41dc9dab478067a8628e9f53f3c sssd-ad-1.13.3-60.el6_10.2.x86_64.rpm 6a42040ae3d2ab2494f2c4d03d4b3b15df738a19e0f610083338607ae2791736 sssd-client-1.13.3-60.el6_10.2.i686.rpm 17d812177e7be07f73b5efa961c18034de110ba9be1a365bce9dfcc429329663 sssd-client-1.13.3-60.el6_10.2.x86_64.rpm af71933e089e28597ca89984389a83aced948cb1f085b1701f58a59892b40be2 sssd-common-1.13.3-60.el6_10.2.x86_64.rpm 5414043e82746468dcc3dd7653eab24f52c9fce13f5fe64b6c45122e24c0e8ad sssd-common-pac-1.13.3-60.el6_10.2.x86_64.rpm a4ec13b36a5b935fea28430a686e72aade5211f6187da99bfa2f80f077c54dde sssd-dbus-1.13.3-60.el6_10.2.x86_64.rpm 7064499c4abef3ce57c5a57cb4a9bde174d921599d8d2a93715dc26e91f653fd sssd-ipa-1.13.3-60.el6_10.2.x86_64.rpm f31b60af9dd104d17725b0b14a1194a8a17b35697c2a0cf7bd303b24917f8013 sssd-krb5-1.13.3-60.el6_10.2.x86_64.rpm 7055b20e98bd8e937dcccd5923edecaaf1ac97d4ec70e75a43be6d2091b6c656 sssd-krb5-common-1.13.3-60.el6_10.2.x86_64.rpm d867a526e7c28bdda74947414aa9d383355d82a84150b3ceadb4e6d67f2d767e sssd-ldap-1.13.3-60.el6_10.2.x86_64.rpm 24bcc4c6f4ea60d81b7f65208641e324383708bfac2424d3b926ced00b8f5324 sssd-proxy-1.13.3-60.el6_10.2.x86_64.rpm ed2a63b1735c021ebfc5ed14b8b2ae2a338af52dd9bd3f058718f8286886a467 sssd-tools-1.13.3-60.el6_10.2.x86_64.rpm Source: 247b093ae72f99ece4eb1ec36ac48c8daf842a03f08a9fb876e77ffae1236c99 sssd-1.13.3-60.el6_10.2.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 4 Date: Wed, 16 Jan 2019 17:01:02 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEBA-2019:0064 CentOS 6 kernel BugFix Update Message-ID: <20190116170102.GA30359(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2019:0064 Upstream details at : https://access.redhat.com/errata/RHBA-2019:0064 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: b9c98cbf953323a56e67a0c28e53634cd6cf6aa600bd8450acde2720ac614075 kernel-2.6.32-754.10.1.el6.i686.rpm cad7a76980dc7d07e5f7533425a6f8b17632c96ce1bf25c92023a042878a6b2d kernel-abi-whitelists-2.6.32-754.10.1.el6.noarch.rpm aa9ca8cce2c5190226a13115b8c7af84128cd01f527d52edd96c1c98a16c7a35 kernel-debug-2.6.32-754.10.1.el6.i686.rpm 1ee4b5feee2525eb5dce2f1892e831dd8a7cde411a24f9b485f915b80c739d7d kernel-debug-devel-2.6.32-754.10.1.el6.i686.rpm 8174c559678952de8b6f41aae2fc347e6907e76ec2789eda52c65ee8aee46804 kernel-devel-2.6.32-754.10.1.el6.i686.rpm fa01abf5c0b25b8e43771abea710a991d721f08a7960c0c1d36ec852734bd11a kernel-doc-2.6.32-754.10.1.el6.noarch.rpm 6db0695340d175e24211a87b64c55ede3326ee32e7d9a226ab00dd075e6b1f8c kernel-firmware-2.6.32-754.10.1.el6.noarch.rpm 247bea5042897bfc78b1e73fc0cd7dfee2c847c8cc710de2a543fbba3e9db62a kernel-headers-2.6.32-754.10.1.el6.i686.rpm 7cab4fd35da0dd1833df81d93e4dd770bc6d0437fa6c0f29f31e5f01be861d50 perf-2.6.32-754.10.1.el6.i686.rpm 8bec1d14dcde36fbeb839f25b3418ec806d452e1108dcbbdbd3779b984ceb33d python-perf-2.6.32-754.10.1.el6.i686.rpm x86_64: 468171ef20cdd72a70bc06715fd76e64d4dafc4cbfd2648c7a3af66e4302b53f kernel-2.6.32-754.10.1.el6.x86_64.rpm cad7a76980dc7d07e5f7533425a6f8b17632c96ce1bf25c92023a042878a6b2d kernel-abi-whitelists-2.6.32-754.10.1.el6.noarch.rpm a22d933669af08e76a87bc55cce266635d907c291e1e662b62030bfc504a2cd0 kernel-debug-2.6.32-754.10.1.el6.x86_64.rpm 1ee4b5feee2525eb5dce2f1892e831dd8a7cde411a24f9b485f915b80c739d7d kernel-debug-devel-2.6.32-754.10.1.el6.i686.rpm 4db33312d3786ec278019f682110edc0cb437e32ce2fe1bac21ca1700483bc7b kernel-debug-devel-2.6.32-754.10.1.el6.x86_64.rpm 51cedf70c96c44256df09ad71bd24519d0b22aa3fcee22330f11378ab98aef37 kernel-devel-2.6.32-754.10.1.el6.x86_64.rpm fa01abf5c0b25b8e43771abea710a991d721f08a7960c0c1d36ec852734bd11a kernel-doc-2.6.32-754.10.1.el6.noarch.rpm 6db0695340d175e24211a87b64c55ede3326ee32e7d9a226ab00dd075e6b1f8c kernel-firmware-2.6.32-754.10.1.el6.noarch.rpm 5e7184f6fc68cd441d2195d1dc9854d2a79d3a260e4e755f118e17cf49576467 kernel-headers-2.6.32-754.10.1.el6.x86_64.rpm 9c8a146d2636171999782d38d5f18160e2bd27f17a9b2ecda74d6b7604a1717d perf-2.6.32-754.10.1.el6.x86_64.rpm 408d8d9b58dab7368191c819425d26b96f7abfed27212e60e5530a1845d231d1 python-perf-2.6.32-754.10.1.el6.x86_64.rpm Source: f65eb1b17c1e1589114aa9796f6c22df00607b850cd7ef6939c2b0836723668b kernel-2.6.32-754.10.1.el6.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Subject: Digest Footer _______________________________________________ CentOS-announce mailing list CentOS-announce(a)centos.org https://lists.centos.org/mailman/listinfo/centos-announce ------------------------------ End of CentOS-announce Digest, Vol 167, Issue 4 ***********************************************

1 0

Inconsistent NIS Client Behavior w/ Centos 7.6
by Capehart, William J 16 Jan '19

16 Jan '19

Hi All. I am working on bringing back a number of Centos 7 rigs in our student computer lab back online. No change was made to the existing server machine [running Scientific Linux 6] Right now there is one remaining thing to resolve: an inconsistency with the rigs' NIS Clients. I have configured rcpbind and ypbind following guidance from Server World ( https://www.server-world.info/en/note?os=CentOS_7&p=nis&f=2 ) identically on all of the client machines. I have done this before with previous installs before this. The last time was this summer. Three are behaving as they are supposed to do. Five, however, are not. In this process I have repeatedly checked that support files .. /etc/sysconfig/network /etc/yp.conf /etc/pam.d/system-auth-ac /etc/pam.d/system-auth /etc/login.defs /etc/sysconfig/authconfig They are identical. IP addresses, Netmasks, Gateways, DNS, etc. are correct and all rigs (Server and Clients) do not conflict on any of the machines or /etc/host files. Disabling firewalls don’t impact the problem. NFS and other services work fine. All other aspects of networking is fine. You can ssh and access the Server rig from the Client rigs and for locally installed accounts on the clients go the other way. Accounts that leverage NIS cannot log into the Client from the Server or any other remote system. rpcbind shows that the ypbind/ypserv services are up and Clients and Server, respectfully (and it works on some of the machines). The rigs that are not working exhibit the following (satisfactory) behavior. * yptest -u [valid nis username] works with no errors. * yppasswd will change a password on the NIS server with no errors and other commands like ypchfn will work as well. * ypwhich, ypcat, ypmap, etc. give the same values we'd see on the NIS server. ...BUT... * You cannot console-login, ssh, or su into the rigs with valid NIS accounts. * (The local ypbind -d "debug mode" shows no response to a login, the "secure" log responds to a valid NIS account login with an "invalid user" a the [preauth] phase) * uids of valid NIS users are not recognized. * With ls -l, we see the uid of a file’s owner and not the username. (gids are explicitly declared locally on all rigs so they’ll match anyway.) * The id command for any valid nis user fails with "no such user" * cd ~[Valid NIS User] responds with "no such directory" even if the home directory exists (and the uid matches the uid on the NIS server). I am totally at a loss here. I cannot see the difference in what I did on the machines that work and the machines that do not work. Is there any test that I am missing or are there any files or setting where the culprit(s) on the errant machines may be? Cheers and Thanks --------------------------------------------------------------------------------------- Dr. Bill Capehart <William.Capehart(a)sdsmt.edu<mailto:William.Capehart@sdsmt.edu>> Director, Atmospheric and Environmental Sciences Program Department of Civil and Environmental Engineering 201 Mineral Industries Building (MWRF) 123 Civil Mechanical Building (T) South Dakota School of Mines and Technology 501 East St Joseph Street Rapid City, SD 57701-3995 USA Ph: +1-605-394-1994 Mobile: +1-605-484-5692

3 3

CentOS 6.X, iptables 1.47 and GeoLite2 Country Database
by Jobst Schmalenbach 16 Jan '19

16 Jan '19

Hi Specs in subject line: CentOS 6.X all latest patches), iptables 1.47, Apache2.2 I use the Geolite legacy databases together with iptables 1.47 to filter traffic for a variety of ports and only allow .AU traffic to have access. Maxmind (https://dev.maxmind.com/geoip/geoip2/geolite2/) changed the default DB to the latest version which is GeoLite2, this leaves all users in need of the old Geolite Legacy database in the dark, they cannot update. If I download a later version of xtables it will complain that it requires iptable>1.6 which I do not think I can get going on CentOS 6.X. Is there a way that I can convert Geolite2 CSV files to Geolite Legacy CSV Files and then compile those into BE/LE? Are there any other ways I can use Geolite2 on a CentOS 6.X system? Does anyone have other ideas how to tackle this? (this made me really sleep well!) thanks Jobst -- "XP: If you are nine years old you are just going to love it. If you're a few years older you'll resent the choking paternalistic atmosphere of vapid gee-whiz kiddie entertainment (babysitting), euphemism and fake-friendly bullying." | |0| | Jobst Schmalenbach, | | |0| Barrett & Sales Essentials |0|0|0| Caulfield South, 3162, Australia

3 6

@reboot only some lines of a script are working (yum install not)
by Ralf Prengel 15 Jan '19

15 Jan '19

Hallo, I m using a script to install docker after a reboot. The script is starting and working. The problem: yum install doesn't work running the script via cron allthough yum remove works. Starting the script manual works fine . Has anyone a hint for me? Thanks Ralf xxx SHELL=/bin/bash PATH=/sbin:/bin:/usr/sbin:/usr/bin MAILTO=root # For details see man 4 crontabs # Example of job definition: # .---------------- minute (0 - 59) # | .------------- hour (0 - 23) # | | .---------- day of month (1 - 31) # | | | .------- month (1 - 12) OR jan,feb,mar,apr ... # | | | | .---- day of week (0 - 6) (Sunday=0 or 7) OR sun,mon,tue,wed,thu,fri,sat # | | | | | # * * * * * user-name command to be executed @reboot root /opt/install_via_pxe/centos_autoinstall/stage01/init_stage01_docker.sh xxx #! /bin/bash echo 'script init_stage01_docker.sh ist gestartet' >> /var/log/comline/autoinst.log /usr/bin/yum install -y cifs-utils systemctl stop packagekit.service systemctl disable packagekit.service yum remove PackageKit -y /usr/bin/yum install -y docker mv /var/lib/docker /mnt/platte02 cd /var/lib ln -s /mnt/platte02/docker docker cp /opt/install_via_pxe/centos_autoinstall/stage01/docker/daemon.json /etc/docker systemctl enable docker systemctl start docker docker run --rm --privileged -v /var/run/docker.sock:/var/run/docker.sock -v /var/lib/rancher:/var/lib/rancher rancher/agent:v1.2.10 http://192.168.242.x.y/v1/scripts/811F51C097F763ABA2E5:1546214400000:Nzpsvk… cp -r /opt/install_via_pxe/centos_autoinstall/stage02/etc/crontab /etc/ echo 'script init_stage01_docker.sh ist gelaufen' >> /var/log/comline/autoinst.log shutdown -r now xxx

3 6

CentOS-announce Digest, Vol 167, Issue 3
by centos-announce-request＠centos.org 15 Jan '19

15 Jan '19

1 0

Re: [CentOS] @reboot only some lines of a script are working (yum install not)
by Ralf Prengel 14 Jan '19

14 Jan '19

Hallo. solved. proxy in yum.conf is working when starting yum in an crontab-environment. Ralf Zitat von Ralf Prengel <ralf.prengel(a)rprengel.de>: > Zitat von Mogens Kjaer <mk(a)lemo.dk>: > >> On 1/10/19 11:32 AM, Ralf Prengel wrote: >>> yum install doesn't work running the script via cron allthough yum >>> remove works. >> >> Is the network up when the script executes? > > > Hallo, > > yes it is up. > Result of 10 pings is fine as first line in the script. > Any other ideas? > > Ralf > > _______________________________________________ > CentOS mailing list > CentOS(a)centos.org > https://lists.centos.org/mailman/listinfo/centos

1 0

Re: [CentOS] Yum excluding packages I need
by mark 12 Jan '19

12 Jan '19

Stephen Berg (Code 7309) wrote: > On 1/11/19 10:41 AM, mark wrote: > >> C7, and I did a yum update --disableexcludes=all, and yet it's telling >> me [nvidia]: excluding kmod-nvidia-410.66-1.el7_5.elrepo.x86_64 >> [nvidia]: excluding kmod-nvidia-410.73-1.el7_5.elrepo.x86_64 >> [nvidia]: excluding kmod-nvidia-410.73-2.el7_6.elrepo.x86_64 >> [nvidia]: excluding kmod-nvidia-410.78-1.el7_6.elrepo.x86_64 >> [nvidia]: excluding kmod-nvidia-410.93-1.el7_6.elrepo.x86_64 <...> >> Even with a -vvv flag, it doesn't tell me why it's excluding them. >> > Pretty sure that's the yum-plugin-nvidia.noarch doing it's thing to keep > the wrong nvidia drivers from getting installed. Y'all will love this: you *can't* update yum-plugin-nvidia - *it* is excluded by itself. mark

4 5

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss