Discuss March 2019

discuss@lists.centos.org

85 participants
69 discussions

RPM Transaction Failure
by Mark LaPierre 03 Mar '19

03 Mar '19

Hey Y'all, I have a yum update failure that remains consistent and repeatable. This is what happens every time I try to update the java package. This a new computer with a fresh network install of CentOS 6.10. How can I fix this? CentOS release 6.10 (Final) Linux nicotine.patch 2.6.32-754.11.1.el6.x86_64 #1 SMP Tue Feb 26 15:38:56 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux Number of cores = 4 01:51:37 up 3 days, 4:02, 1 user, load average: 0.00, 0.04, 0.08 Is this ok [y/N]: y Downloading Packages: java-1.7.0-openjdk-1.7.0.201-2.6.16.0.el6_10.x86_64.rpm | 27 MB 00:02 Running rpm_check_debug Running Transaction Test Transaction Test Succeeded Running Transaction Error in PRETRANS scriptlet in rpm package 1:java-1.7.0-openjdk-1.7.0.201-2.6.16.0.el6_10.x86_64 error: lua script failed: /usr/libexec/copy_jdk_configs.lua:272: attempt to index global 'file' (a nil value) Verifying : 1:java-1.7.0-openjdk-1.7.0.201-2.6.16.0.el6_10.x86_64 1/2 1:java-1.7.0-openjdk-1.7.0.181-2.6.14.10.el6.x86_64 was supposed to be removed but is not! -- _ °v° /(_)\ ^ ^ Mark LaPierre Registered Linux user No #267004 https://linuxcounter.net/ ****

2 2

Re: [CentOS] Mail Server Guides
by Adrian van Bloois 03 Mar '19

03 Mar '19

Am 01.03.19 um 18:53 schrieb Ben Archuleta: > I need to set up a new mail server to replace an aging CentOS 6.3 mail server. I was wondering what were some of the best guides on the web for Postfix (Maildir), Spamassassin, ClamAV, Dovecot? In the list I miss a program to control clamav and spamassassin. Many people use amavis, but my experience is not very favoufable with this script. I personally prefer MailScaaner, have a look at: www.mailscanner.info for further details. I use, and have used, this set in many circomstances even in large commercial envrionments, and I'm very pleased with it, functinally and in terms of stability. Good luck Adrian -- Adri P. van Bloois "Elegance is not a dispensable luxury but a factor that decides between success and failure." Edsger W. Dijkstra

2 1

Scanner problems HP4620 Jon LaBadie.
by Ger van Dijck 03 Mar '19

03 Mar '19

Hi Jon , I agree it is a little bit confusing : On USB all runs fine . So Hplip , cups , etc. is installed and functionates . On WLAN , believe it or not printing and faxing runs fine ; So the Wifi communication is present and functionating , but the scanner function is not ! When running hp-check under USB (Discouvered Devices) the laptopcamera and the scanner is present and all goes fine . Under WLAN (hp-check) the laptopcamera is present , but the scanner not . Clear is the scanner function cannot functionate , Uncear is why can I print to the HP4620 , fax with the HP4620 and NOT scan to the HP4620 while there must excists a wireless communication ? This is an enigma . I am curieus , Ger van Dijck. -- Using Opera's mail client: http://www.opera.com/mail/

1 0

gpg?
by mark 01 Mar '19

01 Mar '19

I just wanted to set up to send an encrypted message, so I went to generate a public/private key pair using gpg on C 6. Version 2.0.14, copyright 2009? Isn't there something newer than 10 years old? mark

5 4

Centos Digest Vol.169 Issue 26 HPlip Mark Roth/Jon LaBadie .
by Ger van Dijck 01 Mar '19

01 Mar '19

Hi Folks , The problems with HPlip goes on and on : I can not manage to establish a connection on WiFi with the HP4620 : I can print to the printer but not scan . Running hp-check results in cups is not running, hplip is not properly (HP) installed , xsane is not installed etc.. But I can assure you all this software is properly installed : Hp-check cannot detect the scanfunction on the HP4620. When running on USB cable all runs fine ! Maybe Bug 1683312 from Zdenek Dohnal (Red Hat) could be helpfull : I reported this bug . Hp does not support Unix/Linux applications ! Are they really so stupid to think that the world excist by MS and all other users do not need support: Arrogance or stupidity ? Regards , Ger van Dijck. -- Gemaakt met Opera's e-mailprogramma: http://www.opera.com/mail/

5 5

amanda 3.3.3.3-21
by Helmut Drodofsky 01 Mar '19

01 Mar '19

Helo, we have had well runnung amanda tape backup with 3.3.3.-17 in CentOS 7. Two weeks ago we updated the server und got the new release. Now LEOM will no longer be correct recognized. Other experince? How to downgrade? amanda is part of base repository and no former release will be found by yum search. -- Viele Grüße Helmut Drodofsky Internet XS Service GmbH Heßbrühlstraße 15 70565 Stuttgart Geschäftsführung Helmut Drodofsky HRB 21091 Stuttgart USt.ID: DE190582774 Fon: 0711 781941 0 <tel:+497117819410> Fax: 0711 781941 79 Mail: info(a)internet-xs.de www.internet-xs.de

1 0

Setting GDM resolution without knowing the monitor specs
by Warren Young 01 Mar '19

01 Mar '19

We had a complaint recently from a customer that received a server we shipped out that their monitor just showed a black screen. It turns out that they’d hooked it up to an ancient POS with 800x600 as its best resolution, and gdm in CentOS 7 apparently assumes at least 1024x768. It was apparently a major hassle for them to hunt down a reasonable monitor for us. Since we almost never use the GUI on these things, we thought we’d solve that problem going forward by shipping these boxes out to use a fixed 800x600, so they’ll work on any monitor the user plugs in. The first problem you run into is that the Settings > Devices > Display GUI only affects the login you do it under. GDM doesn’t pay attention to this, not even to the configuration set as root! Then you go web searching and find solutions involving xrandr and advice to just put it in /etc/gdm/Init/Default, but that doesn’t seem to work. I then got soooo close when I found the advice to set the monitor configuration in the GUI, then copy ~/.config/monitors.xml to /var/lib/gdm/.config. That works…until you plug in a different monitor, because that file has a hard tie to the monitor brand, model and *serial number*! The monitors.xml file looks like this: <monitors version="2"> <configuration> <migrated/> <logicalmonitor> <x>0</x> <y>0</y> <primary>yes</primary> <monitor> <monitorspec> <connector>VGA-1</connector> <vendor>SAM</vendor> <product>SyncMaster</product> <serial>H1AK500000</serial> </monitorspec> <mode> <width>800</width> <height>600</height> <rate>60</rate> </mode> </monitor> </logicalmonitor> </configuration> </monitors> I have tried: 1. Removing the <monitorspec> section entirely. gdm then gives me a black screen on “systemctl restart gdm” from a text console. 2. Filling out all fields except <connector> with values like “default”, “generic”, “any”, “*”, etc. GDM decides you couldn’t possibly mean for this configuration to apply to that monitor, since it differs, so it ignores you and does whatever it likes instead. 3. Lots and lots of web searching for documentation on the file format to see if I can find out if there is a different way of specifying “any monitor, I don’t care”. I was about to go reading the source code, but I thought I’d ask here first. Keep in mind that we ship these systems out without knowing what monitor they’ll plug in, and once the systems are out in the field, it’s often difficult to get remote access to them. That means we can’t just log in with SSH, probe it with xrandr, and fix it remotely; we’re probably having the customer log in via the GUI to fix the problem that prevents us from SSHing in in the first place! It’s fine in our case to pin the configuration to “VGA-1”, because we know what connectors are on the server itself. We just don’t know what the customer will plug into it. I assume there’s a minimum screen resolution for CentOS 7, probably 1024x768, but we’re installing these systems with a reasonable screen. We only need this low resolution post-install, and then only so the customer can pull up a terminal and maybe run the Network settings tool. For that, 800x600 is fine. You do have to drag the Settings app around a bit to see everything, but it works. Our current fallback is Ctrl-Alt-F2 and nano, which is tolerable for some things — “Okay, type ‘ifconfig’…now find the line that has ‘inet’ in it, and read that back to me…’ — but remotely talking someone through changing ifcfg-noisenoise via nano is a minor nightmare, especially now that Confusing Network Device Naming is the default.

5 11

CentOS-announce Digest, Vol 169, Issue 1
by centos-announce-request＠centos.org 01 Mar '19

01 Mar '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. CEBA-2019:C001 CentOS 7 shim BugFix Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Thu, 28 Feb 2019 09:49:58 -0600 From: Johnny Hughes <johnny(a)centos.org> To: CentOS-Announce <centos-announce(a)centos.org> Subject: [CentOS-announce] CEBA-2019:C001 CentOS 7 shim BugFix Update Message-ID: <6f52193b-46e6-65bc-a7d5-b9d967f31c62(a)centos.org> Content-Type: text/plain; charset="utf-8" CentOS Errata and Bugfix Advisory 2019:C001 This is a bug fix for for the following CentOS Bug: https://bugs.centos.org/view.php?id=15522 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 0ae55996308b507ba878377b35b71225c1fa28d4fb453c938a0d5dc9568501cc mokutil-15-2.el7.centos.x86_64.rpm 4e5cac6435cf60cd50610751e8dedc1df42d5b127a6aac033028d3dd049f01f6 shim-ia32-15-2.el7.centos.x86_64.rpm c8ba12bfa3c2cf5626e901e636536acba5c597a10d1081c0d5f780828c1a8a1d shim-unsigned-ia32-15-2.el7.centos.x86_64.rpm affdaf712818dfdaa17ebbad94f08361bb318baf0db038c0131a10a4b2fa40c7 shim-unsigned-x64-15-2.el7.centos.x86_64.rpm 8a8a958be8c80e53553199058f7612841e98f10bb1af4eb792f356353a6d985c shim-x64-15-2.el7.centos.x86_64.rpm Source: f951f93b68466e14772143f52f7903c9938b9914dc620cc96a45c8a1fb14ac16 shim-15-2.el7.centos.src.rpm 67e0ba835f68457eae9b437199a13a1ad8c0b740e419824e5f2d813c025170fd shim-signed-15-2.el7.centos.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos at irc.freenode.net <https://lists.centos.org/mailman/listinfo/centos-announce> Twitter: @JohnnyCentOS

1 0

Performing post-installation setup tasks - for 75 minutes
by Gary Stainburn 01 Mar '19

01 Mar '19

I'm doing a new install, and everything seems to have gone fine apart from the incredible amount of time it's taken. It does have 6 x 4TB drives in RAID6 and I am installing from a USB DVD drive as I had no SATA ports left, but this is getting rediculous. I chose a simple install (the one above file and print server) and added Postgresql but that was about it. It took over 5 hours to do the install and at 16:50 it changed to Performing post-installation setup tasks. That was 85 minutes ago. The HDD light keeps flashing, but other than that (and the circle swirling) there doesn't seem to be any activity. Is this normal and can I check to see if it is actually doing something?

4 6

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss March 2019