Discuss February 2020

discuss@lists.centos.org

85 participants
65 discussions

Problems with reposync and createrepo on CentOS 7 for RHEL8/CentOS8 repo?
by rainer＠ultra-secure.de 25 Feb '20

25 Feb '20

Hi, I'm trying to mirror the PostgreSQL12 RHEL8 repo: https://download.postgresql.org/pub/repos/yum/12/redhat/rhel-8-x86_64/ [root@cobbler yum.repos.d]# cat pgdg-12-centos8.repo # PGDG Red Hat Enterprise Linux / CentOS stable repositories: [pgdg12-rhel8] name=PostgreSQL 12 for RHEL/CentOS $releasever - $basearch baseurl=https://download.postgresql.org/pub/repos/yum/12/redhat/rhel-8-x86_… enabled=1 gpgcheck=1 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-PGDG # Source RPMs (SRPM), and their testing repositories: Then I run: reposync --repoid=pgdg12-rhel8 --download_path=/repo/8 createrepo /repo/8/pgdg12-rhel8 However, when I try to install it on the target-server, it just doesn't find the postgresql12 binaries. [root@my-db11-test yum.repos.d]# dnf search postgresql12 Last metadata expiration check: 0:24:06 ago on Mon 24 Feb 2020 11:18:20 AM CET. ==================================================================================================================== Name & Summary Matched: postgresql12 ===================================================================================================================== postgresql12-debugsource.x86_64 : Debug sources for package postgresql12 postgresql12-debuginfo.x86_64 : Debug information for package postgresql12 postgresql12-libs-debuginfo.x86_64 : Debug information for package postgresql12-libs postgresql12-test-debuginfo.x86_64 : Debug information for package postgresql12-test postgresql12-devel-debuginfo.x86_64 : Debug information for package postgresql12-devel postgresql12-pltcl-debuginfo.x86_64 : Debug information for package postgresql12-pltcl postgresql12-plperl-debuginfo.x86_64 : Debug information for package postgresql12-plperl postgresql12-server-debuginfo.x86_64 : Debug information for package postgresql12-server postgresql12-contrib-debuginfo.x86_64 : Debug information for package postgresql12-contrib postgresql12-llvmjit-debuginfo.x86_64 : Debug information for package postgresql12-llvmjit postgresql12-plpython-debuginfo.x86_64 : Debug information for package postgresql12-plpython postgresql12-plpython3-debuginfo.x86_64 : Debug information for package postgresql12-plpython3 ========================================================================================================================= Name Matched: postgresql12 ========================================================================================================================== postgresql12-libs.x86_64 : The shared libraries required for any PostgreSQL clients postgresql12-odbc.x86_64 : PostgreSQL ODBC driver postgresql12-devel.x86_64 : PostgreSQL development header files and libraries postgresql12-llvmjit.x86_64 : Just-in-time compilation support for PostgreSQL postgresql12-plpython.x86_64 : The Python procedural language for PostgreSQL Is there something obvious (or not so obvious) that I forgot?

2 2

OwnCloud vs NextCloud
by H 25 Feb '20

25 Feb '20

I am planning to install either ownCloud or NextCloud on a CentOS 7 VPS server I control. I have previously used ownCloud on another server but have not updated the host application for quite some time. On this new server, I am not sure which one is the "best" and since I am doing a new install I need to decide which one to use. Looking at the Android apps for these cloud solutions, they both seem to have a fair number of critical reviews... Does anyone have a preference and, if so, why?

7 12

tftp server different from dhcp one
by Mauricio Tavares 24 Feb '20

24 Feb '20

In https://docs.centos.org/en-US/centos/install-guide/pxe-server/#chap-install… they show the following example for setting dhcpd.conf to point to the tftp server for pxe booting: option space pxelinux; option pxelinux.magic code 208 = string; option pxelinux.configfile code 209 = text; option pxelinux.pathprefix code 210 = text; option pxelinux.reboottime code 211 = unsigned integer 32; option architecture-type code 93 = unsigned integer 16; subnet 10.0.0.0 netmask 255.255.255.0 { option routers 10.0.0.254; range 10.0.0.2 10.0.0.253; class "pxeclients" { match if substring (option vendor-class-identifier, 0, 9) = "PXEClient"; next-server 10.0.0.1; if option architecture-type = 00:07 { filename "shim.efi"; } else { filename "pxelinux/pxelinux.0"; } } } If the server is a different one, how would the option architecture-type{} change to reflect the file location?

2 1

Mr. Teo En Ming's Guide to Deploying CentOS Web Panel (CWP) Web Hosting Control Panel on Amazon AWS Cloud
by Turritopsis Dohrnii Teo En Ming 23 Feb '20

23 Feb '20

Redundant Links to Teo En Ming's Guide to Deploying CentOS Web Panel (CWP) Web Hosting Control Panel on Amazon AWS Cloud [1] https://lkml.org/lkml/2020/2/23/71 [2] http://lkml.iu.edu/hypermail/linux/kernel/2002.2/08712.html [3] https://marc.info/?l=linux-kernel&m=158246414013004&w=2 [4] http://lists.linuxfromscratch.org/pipermail/lfs-chat/2020-February/029096.h… [5] https://marc.info/?l=apache-httpd-users&m=158246714513728&w=2 [6] https://lists.launchpad.net/maria-discuss/msg05714.html [7] https://marc.info/?l=php-general&m=158246811013917&w=2 -----BEGIN EMAIL SIGNATURE----- The Gospel for all Targeted Individuals (TIs): [The New York Times] Microwave Weapons Are Prime Suspect in Ills of U.S. Embassy Workers Link: https://www.nytimes.com/2018/09/01/science/sonic-attack-cuba-microwave.html ******************************************************************************************** Singaporean Mr. Turritopsis Dohrnii Teo En Ming's Academic Qualifications as at 14 Feb 2019 and refugee seeking attempts at the United Nations Refugee Agency Bangkok (21 Mar 2017), in Taiwan (5 Aug 2019) and Australia (25 Dec 2019 to 9 Jan 2020): [1] https://tdtemcerts.wordpress.com/ [2] https://tdtemcerts.blogspot.sg/ [3] https://www.scribd.com/user/270125049/Teo-En-Ming -----END EMAIL SIGNATURE-----

1 0

C8 network install
by Robert G (Doc) Savage 23 Feb '20

23 Feb '20

I'm building a new storage server. I was unable to use the CentOS-8- x86_64-1905-dvd1.iso image written to a 256GB thumb drive. It kept failing the integrity check. I had to use the much smaller CentOS-8- x86_64-1905-boot.iso image and do a network install from a mirror site. That's a first for me. Even though I selected "Server with GUI", the resulting installation boots to a text prompt. I've installed the GNOME and GNOME Applications groups, and I can get to them by typing 'startx'. How do I change this behavior and make it boot directly to a graphical desktop? --Doc Savage Fairview Heights, IL

2 1

running .jar files on Centos 7
by Fred Smith 22 Feb '20

22 Feb '20

OT!!!!! I'm trying to learn to use audio cleanup tools from clickrepair.net. they're written in Java and distributed as .jar files. I'm having trouble running them, due, I'm sure, largely to my ignorance. I have icedtea installed, but it just errors out when I try to use it to run any of the jar files: Fatal: Read Error: Could not read or parse the JNLP file. You can try to download this file manually and send it as a bug report to IcedTea-Web team. if I press the "Show Details" button from the box containing that message I get this: net.sourceforge.jnlp.LaunchException: Fatal: Read Error: Could not read or parse the JNLP file. You can try to download this file manually and send it as bug report to IcedTea-Web team. at net.sourceforge.jnlp.Launcher.fromUrl(Launcher.java:487) at net.sourceforge.jnlp.Launcher.launch(Launcher.java:287) at net.sourceforge.jnlp.runtime.JnlpBoot.run(JnlpBoot.java:67) at net.sourceforge.jnlp.runtime.Boot.run(Boot.java:258) at net.sourceforge.jnlp.runtime.Boot.run(Boot.java:62) at java.security.AccessController.doPrivileged(Native Method) at net.sourceforge.jnlp.runtime.Boot.main(Boot.java:198) Caused by: net.sourceforge.jnlp.ParseException: Invalid XML document syntax. at net.sourceforge.jnlp.XMLParser.getRootNode(XmlParser.java:118) at net.sourceforge.jnlp.MalformedXMLParser.getRootNode(MalformedXMLParser.java:79) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at net.sourceforge.jnlp.Parser.getRootNode(Parser.java:1321) at net.sourceforge.jnlp.JNLPFile.parse(JNLPFile.java:815) BTW, I don't see any .jnlp files anywhere in these packages.... I have no clue, can anyone enlighten me? Thanks in advance! Fred -- ---- Fred Smith -- fredex(a)fcshome.stoneham.ma.us ----------------------------- "For the word of God is living and active. Sharper than any double-edged sword, it penetrates even to dividing soul and spirit, joints and marrow; it judges the thoughts and attitudes of the heart." ---------------------------- Hebrews 4:12 (niv) ------------------------------

1 1

Centos 8 hardware compatibility testing
by Frank Cox 21 Feb '20

21 Feb '20

With Centos 7 I've used the Live Image in stores like Staples to test (mostly) laptops for compatibility simply by booting the computer off of a flash drive and getting the desktop up and trying stuff out (sound, networking, touchpad, etc.) If it doesn't work, shut down, remove the flash drive and nothing has changed on the laptop that I just tested. Since there is no Live Image for Centos 8 (that I can find, anyway) what's the recommended procedure for doing this sort of compatibility testing? Maybe a Fedora live image? If so, which one? -- MELVILLE THEATRE ~ Real D 3D Digital Cinema ~ www.melvilletheatre.com

1 0

Re: [CentOS] Renaming virtio devices names on CentOS 8 VM guest
by Chris Card 21 Feb '20

21 Feb '20

Thanks Robert, I was doing that but it was still renaming to ens*. However, I now know why, and have fixed it. For those who are interested, the problem was that when I created the base image from a kickstart I didn't pass net.ifnames=0 to virt-create, and I ended up with an image that had forgotten about eth0 completely. I have now redone the kickstart with net.ifnames=0 and all is well. Chris Sent from Samsung Mobile on O2 -------- Original message -------- From: "Robert G (Doc) Savage via CentOS" <centos(a)centos.org> Date: 21/02/2020 16:08 (GMT+00:00) To: CentOS mailing list <centos(a)centos.org> Subject: Re: [CentOS] Renaming virtio devices names on CentOS 8 VM guest On Fri, 2020-02-21 at 13:03 +0100, Gianluca Cecchi wrote: > On Fri, Feb 21, 2020 at 10:57 AM Chris Card <ctcard(a)hotmail.com> > wrote: > > > I have built a CentOS 8 base image from a kickstart, for use in > > OpenStack. > > This image boots fine but the problem I have is that I can't stop > > udev > > from renaming the network device from eth0 to ens<something>. > > I have /etc/sysconfig/network-scripts/ifcfg-eth0 with the correct > > HWADDR > > defined in it, and have set net.ifnames=0 and biosdevname=0 in the > > grub > > configuration, but nothing I have tried has stopped the renaming. > > I found this bug: > > https://bugzilla.redhat.com/show_bug.cgi?id=1660179 > > which describes the same situation, but the comments in the bug > > didn't help. > > I'd like to keep the eth* device names because we have various heat > > templates and other scripts which assume that the network devices > > are > > called eth0, eth1 etc. > > Any ideas? Is this even possible with a CentOS 8 VM guest? > > > > Chris > > > > > It is strongly discouraged, for Openstack and when you have more than > one > adapter. See here if you have access: > https://access.redhat.com/solutions/2435891 > > Anyway perhaps you could manage order of names customizing > /usr/lib/systemd/network/99-default.link > At least as described here: > https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/ht… > but I never tried it > HIH, > Gianluca Gianluca, What you are trying to do is documented at https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/ht… You need to edit the GRUB_CMDLOINE_LINUX line in /etc/default/grub as shown below; ~]# cat /etc/default/grub GRUB_TIMEOUT=5 GRUB_DISTRIBUTOR="$(sed 's, release .*$,,g' /etc/system-release)" GRUB_DEFAULT=saved GRUB_DISABLE_SUBMENU=true GRUB_TERMINAL_OUTPUT="console" GRUB_CMDLINE_LINUX="rd.lvm.lv=rhel_7/swap rd.luks.uuid=luks- cc387312-6da6-469a-8e49-b40cd58ad67a crashkernel=auto vconsole.keymap=us vconsole.font=latarcyrheb-sun16 rd.lvm.lv=rhel_7/root rhgb quiet net.ifnames=0 biosdevname=0" GRUB_DISABLE_RECOVERY="true" Then for an EUFI system run this: ~]# grub2-mkconfig -o /boot/efi/EFI/redhat/grub.cfg Reboot and you should have your old eth0, eth1, etc. naming convention back again. WATCH YOUR TYPING. BE CAREFUL NOT TO OMIT OR ADD EXTRANEOUS SPACES !!! Hope this helps. --Doc Savage Fairview Heights, IL 62208-3432 _______________________________________________ CentOS mailing list CentOS(a)centos.org https://lists.centos.org/mailman/listinfo/centos

1 0

Renaming virtio devices names on CentOS 8 VM guest
by Chris Card 21 Feb '20

21 Feb '20

I have built a CentOS 8 base image from a kickstart, for use in OpenStack. This image boots fine but the problem I have is that I can't stop udev from renaming the network device from eth0 to ens<something>. I have /etc/sysconfig/network-scripts/ifcfg-eth0 with the correct HWADDR defined in it, and have set net.ifnames=0 and biosdevname=0 in the grub configuration, but nothing I have tried has stopped the renaming. I found this bug: https://bugzilla.redhat.com/show_bug.cgi?id=1660179 which describes the same situation, but the comments in the bug didn't help. I'd like to keep the eth* device names because we have various heat templates and other scripts which assume that the network devices are called eth0, eth1 etc. Any ideas? Is this even possible with a CentOS 8 VM guest? Chris

3 3

CentOS-announce Digest, Vol 180, Issue 5
by centos-announce-request＠centos.org 21 Feb '20

21 Feb '20

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-2020:0550 Important CentOS 7 openjpeg2 Security Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Thu, 20 Feb 2020 16:14:42 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2020:0550 Important CentOS 7 openjpeg2 Security Update Message-ID: <20200220161442.GA11686(a)bstore1.rdu2.centos.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2020:0550 Important Upstream details at : https://access.redhat.com/errata/RHSA-2020:0550 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 62531e53dd42a38ffb4462a435c693d5acaac00b31db4387e7cecc100518b57e openjpeg2-2.3.1-3.el7_7.i686.rpm b29b8912e5a83589e7860ce99dd4d83830710245ffcb7d6846ca0bcb5f61d1de openjpeg2-2.3.1-3.el7_7.x86_64.rpm f938ba6cf59d8d2620fdb3badf02c11c205ffafc4d5f3832b4fbe3bcf4d19038 openjpeg2-devel-2.3.1-3.el7_7.i686.rpm f06d2b1b8c1d85904896c567ffdfbb33d46ab29f3de2b3d6c1b0d6053b4fe88f openjpeg2-devel-2.3.1-3.el7_7.x86_64.rpm 30438a1c778d164a9fbea5da66dc77097af6adedc7ea8a7eef4872e45906c71c openjpeg2-devel-docs-2.3.1-3.el7_7.noarch.rpm d3710e60ba45ef3127e9f118eecea89d6695ea949e743ceee179b7abd1cb4144 openjpeg2-tools-2.3.1-3.el7_7.i686.rpm cb91d18fb7f2dd08f5551bbd30bb00b3f0278ee98111551c9d1fe973c3ed2908 openjpeg2-tools-2.3.1-3.el7_7.x86_64.rpm Source: a8aff69e4e8ffde39e16fd40a5354162b499fdce3023381378805911af76b080 openjpeg2-2.3.1-3.el7_7.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 180, Issue 5 ***********************************************

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss February 2020