Discuss December 2018

discuss@lists.centos.org

96 participants
99 discussions

XFS, NVMe
by Helmut Drodofsky 10 Dec '18

10 Dec '18

For me it's a new problem. I have never had problems like this: kernel:XFS: mysqld(112843) possible memory allocation deadlock size 65552 in kmem_realloc (mode:0x250) My first server with soft raid1 and NVMee. CentOS 7.5. Are there special recommendations for configuring XFS with NVMe's? -- 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

Crackers?
by Arun I. Gurung 10 Dec '18

10 Dec '18

Hi, just wishing you a merry christmas and happy new year, by presenting to you a new trojan for Linux. It`s professionally made by Apple Computer Inc. (must be somebody who threatened them to do it). <https://www.anubis-ca.com/tmp/IMG_20181210_173521.jpg> <https://www.anubis-ca.com/tmp/IMG_20181210_175350.jpg> ---------Videresendt melding------- Fra: Arun I. Gurung <arun-g(a)anubis-ca.com> Til: Ian Mapleson <mapesdhs(a)yahoo.com>, rbowen(a)centosproject.org Emne: Re: Crackers? Dato: Mon, 10 Dec 2018 19:30:20 +0100 > I will take backup of my personal files and reinstall CentOS 1804 > (version 7.5). > > The trojan is a metadata crawler which infiltrates as a systemd > service. It arrived today, when I did a "yum distribution- > synchronization". > > > -----Original Message----- > From: "Arun I. Gurung" <arun-g(a)anubis-ca.com> > To: Ian Mapleson <mapesdhs(a)yahoo.com> > Sent: man., 10 des. 2018 17:54 > Subject: Re: Crackers? > > Apple sold their soul to Mr. Satan. > > -----Original Message----- > From: "Arun I. Gurung" <arun-g(a)anubis-ca.com> > To: Ian Mapleson <mapesdhs(a)yahoo.com> > Sent: man., 10 des. 2018 17:38 > Subject: Re: Crackers? > > Looks like the trojan has infiltrated as a systemd service. It > changed the MAC address on my WLAN interface, but it can't locate any > WLANs. Check the attached photo. > > -----Original Message----- > From: "Arun I. Gurung" <arun-g(a)anubis-ca.com> > To: Ian Mapleson <mapesdhs(a)yahoo.com> > Sent: man., 10 des. 2018 17:25 > Subject: Re: Crackers? > > Godammit, Ian. This time we must be really careful when talking, > because I see a trojan for Linux. A hint is that it's a "new package > manager" for Linux (it's Flatpak) and it's very dangerous. -- Arun I. Gurung <arun-g(a)anubis-ca.com> Anubis C A

2 1

Centos7 broken after update
by Patrick Bégou 10 Dec '18

10 Dec '18

I've launch a "yum update" while I was going to lunch. 1 hour later the system was completely freezed (no mouse, no keyboard, screen black, no network). I try a hard reboot => kernel panic on the new kernel I boot on the old kernel => boot hangs with gnome-shell failure. SSH was OK so I remove the new kernel and re-install gnome shell. Reboot is ok but now the computer freeze (no mouse, no keyboard, screen black) after some time. Yum asks to run yum-complete-transaction Running yum-complete-transaction says: There are 1 outstanding transactions to complete. Finishing the most recent one The remaining transaction had 1537 elements left to run then many package to be removed and start a very long dependances check and show a lot of errors at the end with a depsolving loop limit reached: Erreur : Depsolving loop limit reached. Erreur : Paquet : gtk3-3.22.30-3.el7.i686 (base) Requiert : libXext.so.6 Suppression : libXext-1.3.3-3.el7.i686 (@base) libXext.so.6 Erreur : Paquet : evolution-mapi-3.28.3-2.el7.x86_64 (base) Requiert : libemail-engine.so()(64bit) Suppression : evolution-3.22.6-14.el7.x86_64 (@base) libemail-engine.so()(64bit) Suppression : evolution-3.28.5-2.el7.x86_64 (installed) libemail-engine.so()(64bit) ....... and then: Vous pouvez essayer d'utiliser --skip-broken pour contourner le problème ** 775 problèmes RPMDB préexistants trouvés, la sortie de « yum check » est la suivante : GeoIP-1.5.0-13.el7.x86_64 est un doublon de GeoIP-1.5.0-11.el7.x86_64 1:NetworkManager-1.12.0-8.el7_6.x86_64 est un doublon de 1:NetworkManager-1.10.2-16.el7_5.x86_64 1:NetworkManager-glib-1.12.0-8.el7_6.x86_64 des conflits sont installés NetworkManager-libnm < ('1', '1.12.0', '8.el7_6'): 1:NetworkManager-libnm-1.10.2-16.el7_5.x86_64 1:NetworkManager-glib-1.12.0-8.el7_6.x86_64 est un doublon de 1:NetworkManager-glib-1.10.2-16.el7_5.x86_64 1:NetworkManager-libnm-1.12.0-8.el7_6.x86_64 des conflits sont installés NetworkManager-glib < ('1', '1.12.0', '8.el7_6'): ...etc and fails. Any idea to go back to a normal situation before a full re-install ? Thanks Patrick

4 6

Weird problems with CentOS 7.6 1810 installer
by Nicolas Kovacs 10 Dec '18

10 Dec '18

Hi, I just updated my installation media for CentOS. I have a few sandbox PCs in my office, and I'm testing CentOS 7.6 1810 on them. There seem to be a few issues with the CentOS 7.6 1810 DVD. Checked DVD integrity on startup : OK. First attempt : installer froze on root password dialog. Second attempt : installer froze on dependency calculation. Third attempt : installer froze on network interface definition. Similar behavior on two different machines. On the same machine, the minimal DVD seems to work OK. I could manage to switch to another virtual console, and I have the following kernel log messages: WARNING: kernel:perf: interrupt took too long Any idea what's going on here? I should add that all the previous CentOS 7 installation DVDs worked perfectly on these PCs (Dell Optiplex 330). Cheers, Niki -- Microlinux - Solutions informatiques durables 7, place de l'église - 30730 Montpezat Site : https://www.microlinux.fr Blog : https://blog.microlinux.fr Mail : info(a)microlinux.fr Tél. : 04 66 63 10 32

5 4

Still getting Dropbox warning at login after uninstalling Dropbox
by Gary Stainburn 09 Dec '18

09 Dec '18

Lke many people I have received the message from Dropbox about their changes including the non-support for the old Linux RPM. As I no longer use Dropbox I thought I would just remove the nautilus-dropbox RPM. However, I am still receiving the warning every time I log in. Can anyone tell me what I need to do to stop this please. Gary

2 1

[OT] EPEL update?
by isdtor 09 Dec '18

09 Dec '18

Hi, OT for this list, but maybe I can get some pointers - how hard is it to get some packages updated in EPEL? The project web site sends you from link to link, and the ML web interface is horrible. No interest here to become a package maintainer or regular contributor. I have taken it upon myself to rebuild MATE from Fedora 29, seeing that the current EPEL-7 packages are four revisions behind. Also updated a few packages to their latest upstream version.

7 10

rescue - UEFI revert to BIOS boot - how?
by lejeczek 08 Dec '18

08 Dec '18

hi guys I have a box on which UEFI boot has gone haywire and instead of boot it power the box down, that is before even going to grub2. (displays some error message) I if change to BIOS boot then I can start Centos' rescue - my question is: how can I rescue, re-build grub so it would boot from tradition BIOS? many thanks, L.

4 3

unable to stop drive timeout was reached
by Frank Cox 08 Dec '18

08 Dec '18

On a fully updated Centos 7 system with the Mate desktop, I've just encountered what appears to be a bug in.. something? I connected a USB portable hard drive and copied some files onto it, then right-clicked the icon and "Safely remove drive". After about thirty seconds I then unplugged the portable hard drive and removed it. Several minutes later a window appeared on my desktop that said "unable to stop drive timeout was reached". This is new; I've never seen it before so I think it's related to the last updates in some way. Google finds several mentions of this error message, here is one example: https://forum.manjaro.org/t/usb-drive-safely-remove-causes-delayed-error-me… -- MELVILLE THEATRE ~ Real D 3D Digital Cinema ~ www.melvilletheatre.com

1 0

// RESEND // 7.6: Software RAID1 fails the only meaningful test
by Benjamin Smith 08 Dec '18

08 Dec '18

(Resend: message didn't show, was my original message too big? Posted one of the output files to a website to see) The point of RAID1 is to allow for continued uptime in a failure scenario. When I assemble servers with RAID1, I set up two HDDs to mirror each other, and test by booting from each drive individually to verify that it works. For the OS partitions, I use simple partitions and ext4 so it's as simple as possible. Using the CentOS 7.6 installer (v 1810) I cannot get this test to pass in any way, with or without LVM. Using an older installer, it works fine (v 1611) and I am able to boot from either drive but as soon as I do a yum update then it fails. I think this may be related or the same issue reported in "LVM failure after CentOS 7.6 upgrade" since that also involves booting from a degraded RAID1 array. This is a terrible bug. See below for some (hopefully) useful output while in recovery mode after a failed boot. ### output of fdisk -l Disk /dev/sda: 500.1 GB, 500107862016 bytes, 976773168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk label type: dos Disk identifier: 0x000c1fd0 Device Boot Start End Blocks Id System /dev/sda1 2048 629409791 314703872 fd Linux raid autodetect /dev/sda2 * 629409792 839256063 104923136 fd Linux raid autodetect /dev/sda3 839256064 944179199 52461568 fd Linux raid autodetect /dev/sda4 944179200 976773119 16296960 5 Extended /dev/sda5 944181248 975654911 15736832 fd Linux raid autodetect ### output of cat /prod/mdstat Personalities : md126 : inactive sda5[0](S) 15727616 blocks super 1.2 md127 : inactive sda2[0](S) 104856576 blocks super 1.2 unused devices: <none> ### content of rdosreport.txt It's big; see http://chico.benjamindsmith.com/rdsosreport.txt

2 2

Can't configure GDM after update to CentOS 7.6
by Nicolas Kovacs 07 Dec '18

07 Dec '18

Hi, It looks like the upgrade to CentOS 7.6 has been unusually disruptive with the GNOME desktop version bump and a series of moving targets under the hood. The result is some wreckage at my client's desktop installations, which I've been busy to repair since yesterday. First things first. I have a custom configuration of GDM, which consists mainly of two things. 1. Display my company's logo instead of the CentOS logo. 2. Disable the user list (since I have about 100 users here). Until CentOS 7.5, here's what I did. 1. Create a file /etc/dconf/profile/gdm : user-db:user system-db:gdm file-db:/usr/share/gdm/greeter-dconf-defaults 2. Create a file /etc/dconf/db/gdm.d/01-logo : [org/gnome/login-screen] logo='/usr/share/pixmaps/microlinux-logo.png' 3. Create a file /etc/dconf/db/gdm.d/00-login-screen : [org/gnome/login-screen] disable-user-list=true 4. Update dconf : # dconf update Now with CentOS 7.6 this doesn't work anymore. The /etc/dconf/db/gdm.d directory is nowhere to be found, and I'm currently mildly cursing the GNOME developers' (and Red Hat's) policy of releasing moving targets. Until now, the whole purpose of Enterprise Linux seemed to be low-risk updates. </rant> I've documented the whole GDM customization process until CentOS 7.5 in a short article on my french blog : * https://blog.microlinux.fr/gdm-centos/ Any idea how I can configure GDM with the new version ? Cheers, Niki -- Microlinux - Solutions informatiques durables 7, place de l'église - 30730 Montpezat Site : https://www.microlinux.fr Blog : https://blog.microlinux.fr Mail : info(a)microlinux.fr Tél. : 04 66 63 10 32

7 8

← Newer
1
2
3
4
5
6
7
8
9
10
Older →

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss December 2018