Re: [CentOS] SOLVED: Mate desktop crashes at startup after update to Centos 8.5.2111

[isdtor]

Frank Cox writes:
> On Thu, 18 Nov 2021 10:27:32 -0700
> Greg Bailey wrote:
> 
> > > >From the GDM login screen I enter my password and select Mate.  The 
> > > >screen
> > > >goes blank and appears to be loading the Mate desktop as usual, but just
> > > >at the point where the desktop should appear it returns to the GDM login
> > > >menu.
> > >
>  
> > The only difference in my case is that I use lightdm from the 
> > stenstorp/lightdm copr repo instead of GDM.
> 
> Installing lightdm from the stenscorp/lightdm was indeed the fix.
> 
> Now my desktop is back to looking and working like it's supposed to be.
> 
> For the next guy who needs to do this, here are the exact commands needed:
> 
> dnf copr enable stenstorp/lightdm
> dnf install lightdm
> systemctl disable gdm.service
> systemctl enable lightdm.service
> 
> Then reboot.  You'll probably have to select Mate from the drop-down list at 
> the top right of the login screen but you only have to make that selection 
> once.
> 
> Thank you ever so much for the help, Greg!

I had the same experience with Rocky - not able to login after the update and 
being returned to the login screen. In this case, the solution was to install 
the latest vbox guest additions (this is a vbox VM). And I'm still using gdm.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] livestatus.o addon on Nagios 4.4.6 on CentOS Stream 8 OS

[isdtor]

> I am following https://www.thruk.org/documentation/install.html to install
> Livestatus addon for Nagios which provides real time status data. Is there
> a way to enable the below entry in /usr/local/nagios/etc/nagios.cfg file. I
> did search using yum and dnf package manager on CentOS Stream release 8 but
> unable to locate livestatus.o addon or install it.
> 
> broker_module=/opt/local/livestatus/livestatus.o /tmp/live.sock
> 
> 
> Any help will be highly appreciable. Please guide/suggest. Thanks in
> advance.

It seems you're looking for MK-livestatus.

https://www.thruk.org/api/Monitoring/Livestatus/
https://checkmk.com/download/sources-download

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Mirror problem

[isdtor]

Johnny Hughes writes:
> On 8/30/21 8:52 AM, isdtor wrote:
> > 
> > Updating my local mirror, I noticed
> > 
> > x86_64/Packages/exiv2-0.27.0-4.el7_8.src.rpm
> > x86_64/Packages/firefox-78.13.0-2.el7.centos.src.rpm
> > x86_64/Packages/thunderbird-78.13.0-1.el7.centos.src.rpm
> > 
> > which seem have been pushed into the wrong repo by accident. Confirmed by 
> > checking another random mirror in the US from 
> > https://www.centos.org/download/mirrors/.
> > 
> 
> Fixed in the latest update set.

Thanks, Johnny.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] MATE 1.20 test build for CentOS 7 available

[isdtor]

> Just launched dconf-editor as the user and was greeted by the following error 
> messages the signficance of which I do not understand:
> 
>  dbind-WARNING **: 14:40:01.469: Couldn't connect to accessibility bus: 
> Failed to connect to socket /tmp/dbus-IU3DS9yULv: Connection refused
> 
> ** (dconf-editor:33157): WARNING **: 14:40:01.594: source-manager.vala:108: 
> The following schemas:
>   org.mate.terminal.profiles
>   org.freedesktop.Tracker.Miner
> contain neither keys nor children.
> 
> Not sure what they are trying to tell me (apart from the text in the message 
> itself...)?

 E.g. 
https://unix.stackexchange.com/questions/230238/x-applications-warn-couldnt-connect-to-accessibility-bus-on-stderr

 export NO_AT_BRIDGE=1

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] Mirror problem

[isdtor]

Updating my local mirror, I noticed

x86_64/Packages/exiv2-0.27.0-4.el7_8.src.rpm
x86_64/Packages/firefox-78.13.0-2.el7.centos.src.rpm
x86_64/Packages/thunderbird-78.13.0-1.el7.centos.src.rpm

which seem have been pushed into the wrong repo by accident. Confirmed by 
checking another random mirror in the US from 
https://www.centos.org/download/mirrors/.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] MATE 1.20 test build for CentOS 7 available

[isdtor]

H writes:
> >
> >Thanks for your quick response! I'll try building from the sources
> >while I'm stuck with C7 :-).
> >
> >
> >Regards,
> 
> I have an interest in the latest version of Mate for CentOS 7 as well.

Versions newer than 1.20 don't build on 7. Or, rather, they build but don't 
result in a stable system.

A newer gcc might work, but I've never tried that as I also moved on to 8.

Rocky, that is.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Login failure with Secure Boot

[isdtor]

isdtor writes:
> Hi all,
> 
> I have a laptop in UEFI mode running CentOS 8.2. All works fine but when I 
> enable Secure Boot, login via gdm is no longer possible. Console login is ok.
> 
> I found some related discussions over on Ubuntu forums, suggesting that this 
> could be related to 3rd-party kernel modules, such as nvidia. This laptop has 
> only Intel builtin graphics, and every single module installed is part of the 
> CentOS distribution.
> 
> This is from a file /tmp/xses-.XX (random 6-char string)
> 
> xrdb: Can't open display ''
> xmodmap: unable to open display ''
> Failed to import environment: Process org.freedesktop.systemd1 exited with 
> status 1
> /usr/bin/xmbind: Can't open display
> Unable to init server: Could not connect: Connection refused
> 
> Something is different in the way Xorg is started. In this situation, the 
> first part of the Xorg log file (under ~/.local) is a dump of X command line 
> options.
> 
> use: X [:] [options]
> -a # ...
> -ac ...
> ...

I haven't been able to make any progress on this setup, except that after 
disabling Secure Boot again, it still keeps happening, probably 90% of the 
time. It could be some kind of race, but even waiting for a while after gdm is 
up and the text consoles have a prompt did not help. Rebooting and retrying 
until it works is the only option right now.

What does seem to work, however, is switching back to Wayland, from Xorg. I had 
changed to Xorg in gdm custom.conf to look at some remote connectivity problems 
(can't get x2go to work).

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] Login failure with Secure Boot

[isdtor]

Hi all,

I have a laptop in UEFI mode running CentOS 8.2. All works fine but when I 
enable Secure Boot, login via gdm is no longer possible. Console login is ok.

I found some related discussions over on Ubuntu forums, suggesting that this 
could be related to 3rd-party kernel modules, such as nvidia. This laptop has 
only Intel builtin graphics, and every single module installed is part of the 
CentOS distribution.

This is from a file /tmp/xses-.XX (random 6-char string)

xrdb: Can't open display ''
xmodmap: unable to open display ''
Failed to import environment: Process org.freedesktop.systemd1 exited with 
status 1
/usr/bin/xmbind: Can't open display
Unable to init server: Could not connect: Connection refused

Something is different in the way Xorg is started. In this situation, the first 
part of the Xorg log file (under ~/.local) is a dump of X command line options.

use: X [:] [options]
-a # ...
-ac ...
...

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] Updating ca-certificates

[isdtor]

This is probably a stupid question: what is the correct way to update 
certificates if one has installed additional certs with update-ca-trust and the 
distro releases a new version of ca-certificates?

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] CentOS 8 installer bug

[isdtor]

isdtor writes:
> Has anyone managed to create an encrypted disk partition with CentOS 8 
> kickstart?
> 
> 1 reqpart --add-boot
> 2 part /boot --fstype ext3 --size=1024 --ondrive=sda
> 3 part pv.1 --size=1 --grow --ondrive=sda --encrypted --pashphrase="bla"
> 4 volgroup vol0 pv.10
> 5 logvol / --vgname=vg_00 --name=lv_root --size=102400 --fstype=ext4
> ...
 
So, yeah, apologies for the typos. The actual ks file is correct and consistent.

The problem was line 3 - apparently, "--size=1 --grow" doesn't cut it anymore. 
Increasing size to a reasonable number, e.g in the order of "sum of all lvols", 
got me over the hump.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] CentOS 8 installer bug

[isdtor]

Has anyone managed to create an encrypted disk partition with CentOS 8 
kickstart?

1 reqpart --add-boot
2 part /boot --fstype ext3 --size=1024 --ondrive=sda
3 part pv.1 --size=1 --grow --ondrive=sda --encrypted --pashphrase="bla"
4 volgroup vol0 pv.10
5 logvol / --vgname=vg_00 --name=lv_root --size=102400 --fstype=ext4
...

No matter what I specify in line 3, the installer bombs out. The only way to 
successful kickstart is to not encrypt the lvm pv. The contents of the 
passphrase are not to blame, installer still dies after accepting a passphrase 
from the console.

15:57:45,280 DBG kickstart: Looking for platform-specific boot requirements.
15:57:45,281 DBG kickstart: Applying requirements:
PartSpec instance (0x7fbd40f44320) -- 
  mountpoint = /boot/efi  lv = False  thin = False  btrfs = False
...
PartSpec instance (0x7fbd4048b4e0) -- 
  mountpoint = /boot  lv = False  thin = False  btrfs = False
...
15:57:45,283 DBG bootloader: stage1 device cannot be of type disk
15:57:45,334 DBG exception: running handleException
15:57:45,334 CRT exception: Traceback (most recent call last):

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Laptop and NFS homedir

[isdtor]

Thanks for all the replies. It looks like local home directory is the best 
solution.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] Laptop and NFS homedir

[isdtor]

Afternoon,

Are there any documented best practices for using NFS home directories on 
laptops? Right now, and this is on CentOS 7, when I disconnect the machine from 
the network, the desktop freezes, and I can't even tell if the machine switches 
to the wireless network. If this sort of adapter switching, which is standard 
in e.g. Windows 10, is even supported.

Thanks for any insights.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] CentOS 8 DNS resolution not working as expected

[isdtor]

Pete Biggs writes:
> 
> > > man host
> > > 
> > >-N ndots
> > >The number of dots that have to be in name for it to be 
> > > considered absolute. The default value is that defined using
> > >the ndots statement in /etc/resolv.conf, or 1 if no ndots 
> > > statement is present. Names with fewer dots are interpreted
> > >as relative names and will be searched for in the domains 
> > > listed in the search or domain directive in
> > >/etc/resolv.conf.
> > 
> > As per man resolv.conf, the default setting hasn't changed. It is n=1 on 
> > all of CentOS 6/7/8.
> > 
> 
> Does
> 
>host -N2 foo.subdomain
> 
> work on CentOS 8?  Does it work if you put ndots: 2 in resolv.conf?
> 
> There may have been a change in behaviour - from the tests I've done it
> seems more like it's fixing a bug/inconsistency somewhere because doing
>  
>host -N1 foo.subdomain 
> 
> should not work, but it does on CentOS 7.

Interesting. Yes, host -N2 works, as does ndots:2.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] CentOS 8 DNS resolution not working as expected

[isdtor]

Pete Biggs writes:
> On Thu, 2020-08-06 at 10:26 +0100, isdtor wrote:
> > [root@localhost ~]# lsb_release -d
> > Description:CentOS Linux release 8.2.2004 (Core) 
> > [root@localhost ~]# cat /etc/resolv.conf 
> > # Generated by NetworkManager
> > search subdomain.company.com company.com
> > nameserver 1.2.3.4
> > nameserver 5.6.7.8
> > 
> > [root@localhost ~]# host foo
> > foo.subdomain.company.com has address 1.2.3.4
> > 
> > [root@localhost ~]# host foo.subdomain
> > Host foo.subdomain not found: 3(NXDOMAIN)
> > 
> > [root@localhost ~]# host foo.subdomain.company.com
> > foo.subdomain.company.com has address 1.2.3.4
> > [root@localhost ~]# 
> > 
> > The expected result is that the lookup for foo.subdomain works, like it 
> > does under CentOS < 8.
> 
> man host
> 
>-N ndots
>The number of dots that have to be in name for it to be considered 
> absolute. The default value is that defined using
>the ndots statement in /etc/resolv.conf, or 1 if no ndots 
> statement is present. Names with fewer dots are interpreted
>as relative names and will be searched for in the domains listed 
> in the search or domain directive in
>/etc/resolv.conf.

As per man resolv.conf, the default setting hasn't changed. It is n=1 on all of 
CentOS 6/7/8.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] CentOS 8 DNS resolution not working as expected

[isdtor]

[root@localhost ~]# lsb_release -d
Description:CentOS Linux release 8.2.2004 (Core) 
[root@localhost ~]# cat /etc/resolv.conf 
# Generated by NetworkManager
search subdomain.company.com company.com
nameserver 1.2.3.4
nameserver 5.6.7.8

[root@localhost ~]# host foo
foo.subdomain.company.com has address 1.2.3.4

[root@localhost ~]# host foo.subdomain
Host foo.subdomain not found: 3(NXDOMAIN)

[root@localhost ~]# host foo.subdomain.company.com
foo.subdomain.company.com has address 1.2.3.4
[root@localhost ~]# 

The expected result is that the lookup for foo.subdomain works, like it does 
under CentOS < 8.

I tested this also on a RHEL8 machine and followed 
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/configuring_and_managing_networking/manually-configuring-the-etc-resolv-conf-file_configuring-and-managing-networking
 to disable DNS processing by NM, but this did not change the outcome.

How can the pre-CentOS 8 behaviour be restored?

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Can't access Squirrelmail on Centos 8

[isdtor]

Jay Hart writes:
> Good evening,
> 
> I have not able able to run the http://ip-addr/src/configtest.php script, nor 
> access Squirrelmail. Looking for suggestions on what I might
> have missed.  When I try either http://ip-... or https://ip-..., I get the 
> following reply
> 
> Forbidden You don't have permission to access /webmail/src/configtest.php on 
> this server.
 
mod_security?

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] CentOS 8.2 corrupt pxeboot kernel

[isdtor]

> pxe is working for me in this test virtualbox build.
> 
> $ md5sum initrd.img vmlinuz
> 89251241a484010b98280ce00b3a3763  initrd.img
> 9261bb24add6bb4ff9ef6aaf348aaf35  vmlinuz
> 
> ( yum updated )
> 
> [centos@localhost ~]$ uname -a
> Linux localhost.localdomain 4.18.0-193.6.3.el8_2.x86_64 #1 SMP Wed Jun 
> 10 11:09:32 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
> 
> [centos@localhost ~]$ cat /etc/redhat-release
> CentOS Linux release 8.2.2004 (Core)

And it is working here now, too. After replacing the trusty, 8-year old 
pxelinux.0 with a slightly newer version. Strange that it should break just 
after C8.1.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Compile gnutls yo install samba-4.12.3

[isdtor]

Rommel Rodriguez Toirac writes:
> Hello all;
>  Has anyone installed samba4 from sources (samba-4.12.3.tar.gz) on CentOS 7?
>  I explain the problem: to install samba-4.12.3 you need to install a version 
> equal to or greater than 3.4.7 of gnutls; this (gnutls) depends on nettle and 
> gmp. 
>  I am trying to install gnutls-3.6.14; I already have gmp (gmp-6.2.0) and 
> nettle (nettle-3.6) installed (compiled from sources), but gnutls doesn't 
> want to install, it tells me "Libnettle 3.4.1 was not found" when I run the 
> ./configure
> 
>  Nettle is installed in /usr/local/include/nettle (all .h) and in 
> /usr/local/lib64/libnettle.s0.8.0
> 
>  I created a symbolic link for /usr/lib64 from 
> /usr/local/lib64/libnettle.s0.8.0 as libnettle.so and libnettle.so.8; I ran 
> the gnutls ./configure again, but it keeps saying it can't find libnettle 
> 3.4.1
>  
>  How can I do? 
>  Has anyone got CentOS 7 and samba-4.12.3 installed and fixed this situation?

I've just been through a very similar exercise on CentOS 6, not for samba, but 
involving gnutls. My respect for those who manage to build gnutls at all has 
grown considerably. The code below works for my purposes.

In the p11-kit section, consider that your system does have systemd. In the 
libtasn1 section, I'm applying a patch that changes the perlesque C99 for loops 
into something gcc 4.4.7 can digest. I don't know if gcc 4.8.5 knows C99 
(probably not). If you know a little C you can easily figure out what to do if 
needed. I didn't investigate building gnutls without external libtasn1 etc.

Now, linking your code against this version of gnutls is also a fun exercise. 
You need to configure against the same --prefix, for starters. You may also 
require the same PKG_CONFIG_PATH= stanza as below for gnutls. In your 
Makefiles, you may need to change anything "-lgnutls" to "-lgnutls -lgmp 
-ltasn1".


# keep it out of system directories!
prefix=/foo/bar

gmp_version=6.2.0
nettle_version=3.6
libtasn1_version=4.16.0
libffi_version=3.3
p11_kit_version=0.23.20
gnutls_version=3.6.14

tar xf gmp-${gmp_version}.tar.xz
pushd gmp-${gmp_version} >/dev/null
./configure --prefix=${prefix}
make install clean
popd >/dev/null
rm -rf gmp-${gmp_version}

tar xf nettle-${nettle_version}.tar.gz
pushd nettle-${nettle_version} >/dev/null
./configure --prefix=${prefix}   --with-include-path=${prefix}/include 
--with-lib-path=${prefix}/lib
make install clean
popd >/dev/null
rm -rf nettle-${nettle_version}

tar xf libtasn1-${libtasn1_version}.tar.gz
pushd libtasn1-${libtasn1_version} >/dev/null
#optional?# patch -p1 < ../libtasn1-4.16.0-c99-for-loop.patch
./configure --prefix=${prefix}
make install clean
popd >/dev/null
rm -rf libtasn1-${libtasn1_version}

tar xf libffi-${libffi_version}.tar.gz
pushd libffi-${libffi_version} >/dev/null
LIBFFI_CFLAGS="-I${prefix}/include" LIBFFI_LIBS="-L${prefix}/lib64" \
  ./configure --prefix=${prefix}
make install clean
popd >/dev/null
rm -rf libffi-${libffi_version}

tar xf p11-kit-${p11_kit_version}.tar.xz
pushd p11-kit-${p11_kit_version} >/dev/null
PKG_CONFIG_PATH=${prefix}/lib/pkgconfig \
  ./configure --prefix=${prefix} --without-systemd --disable-nls
make install clean
popd >/dev/null
rm -rf p11-kit-${p11_kit_version}

tar xf gnutls-${gnutls_version}.tar.xz
pushd gnutls-${gnutls_version} >/dev/null
PKG_CONFIG_PATH=${prefix}/lib64/pkgconfig:${prefix}/lib/pkgconfig: \
  GMP_CFLAGS="-I ${prefix}/include" \
  GMP_LIBS="-L${prefix}/lib -lm" \
  LIBTASN1_CFLAGS="-I${prefix}/include" LIBTASN1_LIBS="-L${prefix}/lib" \
  ./configure --prefix=${prefix} --with-included-unistring 
--disable-hardware-acceleration --disable-doc --disable-gtk-doc 
--disable-gtk-doc-html --disable-nls
sed -i 's%^#am__append_13.*%am__append_13 = -I${prefix}/include%' src/Makefile
for d in doc/examples src tests ; do
  sed -i 's%^LIBS = .*%LIBS = -L${prefix}/lib -lgmp -ltasn1%' ${d}/Makefile
done
make install clean
popd >/dev/null
rm -rf gnutls-${gnutls_version}

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] CentOS 8.2 corrupt pxeboot kernel

[isdtor]

Attempting to PXE boot from the BaseOS/x86_64/kickstart/images/pxeboot/ files 
results in repeating messages

Invalid or corrupt kernel image

eventually changing to

Could not find kernel image: centos8.2.x86_64/vmlinuz

I downloaded the files again, from a different mirror, and they are all the 
same. Wiped the files and recreated /tftpboot/linux-install/centos8.2.x86_64/. 
No dice.

First mirror

89251241a484010b98280ce00b3a3763  os/images/pxeboot/initrd.img
9261bb24add6bb4ff9ef6aaf348aaf35  os/images/pxeboot/vmlinuz

Second mirror

89251241a484010b98280ce00b3a3763  os/images/pxeboot/initrd.img
89251241a484010b98280ce00b3a3763  kickstart/images/pxeboot/initrd.img

9261bb24add6bb4ff9ef6aaf348aaf35  os/images/pxeboot/vmlinuz
9261bb24add6bb4ff9ef6aaf348aaf35  kickstart/images/pxeboot/vmlinuz

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Minicom and Ncurses

[isdtor]

Nicolas Kovacs writes:
> Hi,
> 
> I have to do some maintenance on a CentOS 7 proxy installed on a routerboard
> without a video card. The only way to access this machine directly is via
> Minicom and serial port.
> 
> I'm using NetworkManager TUI (nmtui) to configure network interfaces, but
> Ncurses rendering in Minicom works in the sense that chickens fly and horses
> swim. What you get is a forest of question marks with a few barely 
> recognizable
> options lost in between.
> 
> Is there some magical trick to render Ncurses interfaces correctly in Minicom 
> ?

What about nmcli?

Might be a long shot - try export LANG=C.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] how does autofs deal with stuck NFS mounts and suspending to RAM?

[isdtor]

> That's what I thought.  Should I make a bug report?  Sshfs is clearly 
> intended 
> to reconnect automatically when mounted like that, and it doesn't do that.
 
Not so clearly. Look at the sshfs reconnect option, and also ssh/ssfs 
ServerAliveInterval/ServerAliveCountMax.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] CentOS 8 installer bug

[isdtor]

CentOS 8.1.1911 has a bug in the installer. It is not possible to use more than 
one NFS repo via kickstart repo directive as the installer tries to mount all 
of them on /run/install/.nfs. You get this

DBG payload: /run/install/.nfs already has something mounted on it

message for all but the first one. The problem was reported for Fedora 29/30.

https://bugzilla.redhat.com/show_bug.cgi?id=1669711

Do we know if this is fixed in RHEL 8.2?

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] CentOS 8 installation

[isdtor]

Leon Fauster via CentOS writes:
> Am 08.05.20 um 13:53 schrieb isdtor:
> > Here's another interesting observation.
> > 
> > For previous versions, I was able to reduce the size of the updates mirror 
> > significantly by running repomange -o and deleting the resulting files on 
> > next sync. With the AppStream repo, this no longer works, the anaconda 
> > installer will complain that at least one package has an incorrect 
> > checksum, and the only way to remove this error is to restore the complete 
> > package set, multiple versions and all. I've not been able to narrow it 
> > down more.
> > 
> 
> How does the observation looks like, when all
> kickstart/ sub directories are untouched?

I'm not mirroring or using kickstart. os only.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] CentOS 8 installation

[isdtor]

Here's another interesting observation.

For previous versions, I was able to reduce the size of the updates mirror 
significantly by running repomange -o and deleting the resulting files on next 
sync. With the AppStream repo, this no longer works, the anaconda installer 
will complain that at least one package has an incorrect checksum, and the only 
way to remove this error is to restore the complete package set, multiple 
versions and all. I've not been able to narrow it down more.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] CentOS 8 installation

[isdtor]

Are there still a lot of rough edges in this area? There are some things I 
simply can't get to work.

This is about kickstart installations. Finding the right stuff for the 
%packages sections is lucky dip at best. The RHEL manual points to the comps 
file, really? This file isn't meant to be parsed by humans.

Specifying an environment - the example "Infrastructure Server" doesn't exist. 
Is this one of the areas where CentOS deviates from RHEL? I did find 
server-product-environment, custom-environment, minimal-environment.

I followed the link in the documentation to the kickstart file generator. The 
generated file isn't usable as is, specifically the %packages section - 
anaconda says there is no group dns-server, for instance. Which dnf later 
confirms. The group list in dnf also seems to be a lot shorter than it used to 
be under 7?

Specifying %packages --multilib, this is where it breaks down completely. For 
the chosen group/package mix, which works perfectly without multilib, anaconda 
complains about conflicts for files provided by both the i686 and the x86_64 
version of, in this case, gdb-headless and sssd-common. Attempting to fix this 
with

-gdb-headless.i686
-sssd-common.i686

fails, these lines are being ignored. Excluding gdb-headless altogether fails 
also because the main gdb package pulls it in.

Honestly, I'm not sure where to go from here.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS-virt] VM migration problems

[isdtor]

Chris Wik writes:
> 
> I may have run into this issue before too, but in my case the VMs ran fine 
> with only 1 vcpu so I booted them that way and left them like that. It was 
> just a few small legacy VMs and I didn't spend any more time on it.
> 
> Did you try booting with only 1 vcpu?

Yes, and it works.

Good to know but I was really looking for some sort of technical explanation.

___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-virt] VM migration problems

[isdtor]

Helmut Drodofsky writes:
> migrated or moved? I move vm from C6 to C7 without any problem, C5
> guests too.
> 
> - copy disk files (rsync or scp)
> - create in virtual manager
> - change HWADDR in nic
> 
> start guest
 
Moved. Just like you, minus the MAC change.

___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt

[CentOS-virt] VM migration problems

[isdtor]

I have migrated KVM VMs from a CentOS 6 to a CentOS 7 host. All work fine 
post-migration, CentOS 3 (don't ask ...), CentOS 6, CentOS 7, Windows. But the 
CentOS 5 VMs failed. At some point during the boot process, they became 
unpingable and also inaccessible.

I have correlated this to the start of the irqbalance service and was wondering 
if it is generally considered best practice to turn it off. The VMs in question 
all have at least 2 vcpus, and the C5 VMs are the odd ones out.

___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS] CentOS 8 NIS

[isdtor]

Nicolas Kovacs writes:
> Le 09/04/2020 à 11:05, isdtor a écrit :
> > NIS works fine on CentOS 8. Certainly the client side. But how it's enabled
> > is different, check the manual. authconfig is replaced with authselect.
> 
> NIS "works fine" in the sense that telnet works fine.
> 
> :o)

It is not our job here to second-guess implementation decisions made by others 
as only the people concerned are familiar with their environment's restraints 
and business requirements.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] CentOS 8 NIS

[isdtor]

Nicolas Kovacs writes:
> Le 09/04/2020 à 02:42, Mark LaPierre a écrit :
> > Does anyone know where I can get NIS for CentOS 8?
> 
> According to the Release Notes, NIS has been officially deprecated in CentOS 
> 8.
> 
> You might want to move to 389 Directory Server. Robust, secure and 
> well-documented.

NIS works fine on CentOS 8. Certainly the client side. But how it's enabled is 
different, check the manual. authconfig is replaced with authselect.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Monitor email for office365.com with fetchmail

[isdtor]

Jerry Geis writes:
> I am trying to use fetchmail to monitor box in office365.com.
> Its not working.
> 
> Is there a "better" way to monitor and inbox ?
> 
> I have verified all the ports are open, using 993, using ssl, using
> sslproto SSL3 etc..
> 
> Anyone done this ? Got it working.
> 
> I basically have:
> machine outlook.office365.com
> login myuser@mydomain
> password mypassword
> 
> fetchmail --ssl --sslproto SSL3 --smtpname X -u X outlook.office365.com

Yes - but I'm using a custom version of fetchmail 6.4, rebuilt from Fedora 
IIRC. It does SSL things a bit differently, so I built it with a static copy of 
the latest openssl rather than what comes with centos.

set invisible
poll outlook.office365.com protocol IMAP service 993 auth password
   user "username" password "password" folder Inbox is mylocalname here
   no idle
   no rewrite
   sslcertpath /home/mylocalname/.certs

The .certs directory contains the complete certificate chain for O365, hashed 
with c_rehash (three certs), so fetchmail is independent of the OS certificate 
store.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] CentOS 7 kickstart repo directive

[isdtor]

On 2019-10-03, isdtor writes:
> Is the kickstart repo directive broken under CentOS 7? Every attempt with a 
> repo directive in the kickstart file fails during the software selection 
> step. Removing the repo directives and the packages from those repos under 
> %packages makes it work.
> 
> On console 2, I have verified that the (NFS) repos specified in the kickstart 
> file are mounted and that the repo metadata has been copied over to 
> /tmp/yum.cache. One of the packages from one of the repos that is explicitly 
> listed under the %packages section appears in packaging.log for dependency 
> checking.
> 
> The custom repos work fine with yum on a running machine, so there is no 
> problem with the metadata.
> 
> Logging is poor and does not log what is actually wrong.

Here is my theory: the installer runs into some hard-coded limit for the list 
of installation packages, or another hard-coded limit that indirectly affects 
the list of installation packages.

Basis for the assumption: packages from a "repo" in the %packages section 
install fine if the installation package set is limited. Installation fails if 
the effective number of packages in %packages is high, in the thousands. I 
cannot narrow it down further for the moment, my reference points are 700 or so 
vs. 6000.

Is anyone aware of bug reports in this area for RHEL or Fedora? I'v looked at 
the changelog sections of the F22 and F30 anaconda rpms but didn't see anything 
obvious.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Centos 7 + samba / some win 10 systems can mount and some not

[isdtor]

Ralf Prengel writes:
> Hallo,
> 
> We are using centos 7 and samba in combination with Win10 1903.
> The problem:
> Some systems are able to map a share and some can t.
> Any ideas and hints?

Make sure server and all clients are on the same page wrt smb protocol 
versions. Clients should have SMBv1 disabled. The server should enforce SMBv2 
minimum. What you describe sounds like the server uses v1 and some clients, 
i.e. the ones that can't map shares, require v2.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Firefox 68 jnlp files

[isdtor]

Leroy Tennison writes:
> Not knowing what kind of server management you're looking for I can only make 
> general suggestions.  We found that the removal of Java support (actually 
> NSAPI in favor of the Pepper API which Oracle has stated they won't support) 
> left us with limited IPMI (iLO, DRAC, whatever) functionality.  And, looking 
> at https://en.wikipedia.org/wiki/Java_Web_Start, Oracle has stopped 
> supporting javaws.  In our case (SuperMicro) we found two things: their newer 
> hardware had switched to HTML5/iKVM which didn't require Java and SuperMicro 
> had supplied non-browser-based (but Java-based) programs which supplied 
> equivalent functionality for the legacy hardware.  My recommendation would be 
> to look into those alternatives.
> Java Web Start - Wikipedia
> In computing, Java Web Start (also known as JavaWS, javaws or JAWS) is a 
> framework developed by Sun Microsystems (now Oracle) that allows users to 
> start application software for the Java Platform directly from the Internet 
> using a web browser.Some key benefits of this technology include seamless 
> version updating for globally distributed applications and greater control of 
> memory allocation to ...
> en.wikipedia.org

This is about firefox. I was able to add custom helper applications on previous 
versions, or pick an executable from the filesystem tree to achieve this. This 
version of firefox doesn't allow that, it has a predefined list of helper apps 
taht cannot be updated. If it somehow generates that list from OS config files, 
I am wondering which those are.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Firefox 68 jnlp files

[isdtor]

isdtor writes:
> It seems that firefox 68.x, as distributed with CentOS6 updates, no longer 
> allows opening jnlp files with javaws
> 
> The "Choose Helper Application" window popping up after selecting "Open 
> with/Other" has a predefined list of applications that cannot be customised.
> 
> I'm sure it must be a configuration issue as this works fine with the same 
> browser on other distributions, but what to look for?
> 
> # alternatives --display javaws  
> javaws - status is auto.
>  link currently points to /usr/java/latest/jre/bin/javaws
> /usr/java/latest/jre/bin/javaws - priority 20
> Current `best' version is /usr/java/latest/jre/bin/javaws.
> # ll -L /etc/alternatives/javaws
> -rwxr-xr-x 1 root root 140296 Dec 15  2018 /etc/alternatives/javaws
> # 

No replies, really? Lack of this facility makes browser and platform unusable 
for server management.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] Firefox 68 jnlp files

[isdtor]

It seems that firefox 68.x, as distributed with CentOS6 updates, no longer 
allows opening jnlp files with javaws

The "Choose Helper Application" window popping up after selecting "Open 
with/Other" has a predefined list of applications that cannot be customised.

I'm sure it must be a configuration issue as this works fine with the same 
browser on other distributions, but what to look for?

# alternatives --display javaws  
javaws - status is auto.
 link currently points to /usr/java/latest/jre/bin/javaws
/usr/java/latest/jre/bin/javaws - priority 20
Current `best' version is /usr/java/latest/jre/bin/javaws.
# ll -L /etc/alternatives/javaws
-rwxr-xr-x 1 root root 140296 Dec 15  2018 /etc/alternatives/javaws
# 

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] UEFI and PXE

[isdtor]

Cracked it.

Failure to boot was the result of including tboot in the install package set, 
for some reason or other. It's not needed and removing it does the trick.

https://access.redhat.com/articles/2217041

And I thought I was going spare when it worked with one install package set and 
not another ...

When using a kickstart file, the bootloader, clearpart and zerombr directives 
also need attention. Used without the correct options they will install an MBR 
which is not exactly desired.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] UEFI and PXE

[isdtor]

isdtor writes:
> Gordon Messmer writes:
> > On 10/21/19 6:38 AM, isdtor wrote:
> > > Booting with CentOS6 /boot/efi/EFI/redhat/grub.efi, and the older style 
> > > pxe config file as per ... results in a grub (legacy) prompt on the 
> > > target machine.
> > 
> > 
> > Have you tried using the file from the installation tree?
> > 
> > http://centos.s.uw.edu/centos/6/os/x86_64/EFI/BOOT/
> > 
> > or with files extracted from one of the ISOs?
> > 
> > http://centos.s.uw.edu/centos/6/os/x86_64/images/
> 
> They are all identical to the installed one (distributed with grub).
 
I'm tantalizingly close. CentOS6 UEFI PXE is working, but the machine won't 
boot.

It is best to use the CentOS7 BOOTX64.EFI loader. The "kernel too old" message 
is due to the fact that the PXE config file uses linuxefi and initrdefi 
directives. They need to be changed to linux/initrd, respectively. 
linux16/initrd16 may also work. The arguments to those directives need to 
adhere to CentOS6 legacy grub syntax (ks instead of inst.ks etc.).

This will cause error messages on the client that both linux and initrd are 
unknown commands. The fix is to add the linux module to the PXE config file,

insmod linux

The client now issues different error messages that flash past pretty quickly. 
tcpdump to the rescue, it becomes clear that it is seeking to download the grub 
linux module through tftp, so I added the complete contents of the CentOS7 
grub2-efi-x64-modules rpm under /tftpboot/EFI/centos/x86_64-efi.

These changes will lead to a successful PXE boot. If a kickstart installation 
is used, one also needs to add a /boot/efi partition. Looking at a CentOS7 
machine, type vfat and size 200MB should be fine; reqpart is not support under 
CentOS6. Last, and this untested as of yet, it looks like the bootloader 
location needs to be partition because the resulting disk is in GPT format.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] UEFI and PXE

[isdtor]

Gordon Messmer writes:
> On 10/21/19 6:38 AM, isdtor wrote:
> > Booting with CentOS6 /boot/efi/EFI/redhat/grub.efi, and the older style pxe 
> > config file as per ... results in a grub (legacy) prompt on the target 
> > machine.
> 
> 
> Have you tried using the file from the installation tree?
> 
> http://centos.s.uw.edu/centos/6/os/x86_64/EFI/BOOT/
> 
> or with files extracted from one of the ISOs?
> 
> http://centos.s.uw.edu/centos/6/os/x86_64/images/

They are all identical to the installed one (distributed with grub).

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] UEFI and PXE

[isdtor]

Chris Adams writes:
> Once upon a time, isdtor  said:
> > Yes, it looks like I'm out of luck and need to find a newer machine to test 
> > this with. Moving the tftp server works to an extent - server boots right 
> > into a grub prompt.
> 
> Weird.  I have a couple of Intel-based systems that do UEFI PXE boot
> okay, but they're much newer than the 11th gen PowerEdge (I have some of
> those still in service but they're not running UEFI mode).  Also,
> they're client-type systems, not servers (a Thinkpad notebook and an
> Intel NUC), so possibly different firmware base.
> 
> I vaguely remember in the distant past having some kind of problem like
> this, and I think on those systems, I used a boot floppy (yes, that long
> ago!) with gPXE on it.

Not too happy to revive this old thread ...

Has anyone managed to UEFI/PXE boot CentOS6? I managed to find newer hw and 
have this working perfectly with CentOS7. With 6, however, I again cannot boot 
beyond a grub prompt.

CentOS7 bootx64.efi does not work for CentOS6 as it complains "kernel too old". 
Booting with CentOS6 /boot/efi/EFI/redhat/grub.efi, and the older style pxe 
config file as per 
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/6/html/installation_guide/s1-netboot-pxe-config-efi
 results in a grub (legacy) prompt on the target machine.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] easy way to stop old ssl's

[isdtor]

> Yes, breaking changes.  Doing this *will* cut off support for older browsers. 
>  On purpose.

Old browsers aren't really the problem. Even ff 45 (?) from CentOS5 will 
happily access a TLSv1.2-only server. The problem is user that have old 
versions of software installed with no TLSv1.2 support. SVN, python 2.7 
scripts, etc.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] MATE 1.20 test build for CentOS 7 available

[isdtor]

Greg Bailey writes:
> Hi everyone,
> 
> There's been discussions in the past about updating MATE RPMs in EPEL-7:
> https://bugzilla.redhat.com/show_bug.cgi?id=1436260
> https://lists.centos.org/pipermail/centos/2019-August/173154.html
> (and lots of others...)
> 
> As a proof-of-concept, I've written some scripts that clone specific commits
> from the Fedora master branches, and then runs a tool to re-apply RPM
> scriptlets that are required by EL7 but removed from the Fedora .spec files.
> 
> The scripts are available at:
> https://github.com/gebailey/mate-rpms/tree/master/1.20/el7
> 
> There's also instructions there if you want to try upgrading to MATE 1.20
> w/o rebuilding them yourself.
> 
> If these packages work for others, perhaps we can revisit the idea of
> updating the epel7 branches of the Fedora git repos and submitting an
> official update.
> 
> There's nothing here (yet) about building MATE 1.22 (which might require a
> newer gcc for EL7), or building anything on CentOS 8, but thought the CentOS
> 7 users might find this helpful.
 
I've had 1.20 running on CentOS7 for a while, based on my own updates to the 
1.16 rpms from EPEL.

Not so lucky for mate 1.22. Updating my own rpms to 1.22 as well as a rebuild 
of the Fedora 30 rpms do not create functional rpms. Some components work, some 
don't.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] CentOS 7 kickstart repo directive

[isdtor]

Is the kickstart repo directive broken under CentOS 7? Every attempt with a 
repo directive in the kickstart file fails during the software selection step. 
Removing the repo directives and the packages from those repos under %packages 
makes it work.

On console 2, I have verified that the (NFS) repos specified in the kickstart 
file are mounted and that the repo metadata has been copied over to 
/tmp/yum.cache. One of the packages from one of the repos that is explicitly 
listed under the %packages section appears in packaging.log for dependency 
checking.

The custom repos work fine with yum on a running machine, so there is no 
problem with the metadata.

Logging is poor and does not log what is actually wrong.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] VirtualBox extensions and the new kernel

[isdtor]

Klaus Kolle writes:
> I've been running Centos for different purposes in a VirtualBox
> environment for quite long now. But the newest kernels miss something so
> I can get the VirtualBox Extensions linked in.
> 
> I can see in the virtualbox log file that I shall run maken oldconfig
> and make, but I get these errors:
> 
> # make oldconfig && make prepare
> scripts/kconfig/conf --oldconfig Kconfig
> #
> # configuration written to .config
> #
> scripts/kconfig/conf --silentoldconfig Kconfig
> make[1]: *** No rule to make target `arch/x86/syscalls/syscall_32.tbl',
> needed by `arch/x86/syscalls/../include/generated/uapi/asm/unistd_32.h'.
>  Stop.
> make: *** [archheaders] Error 2
> 
> Probably it is something that I misses, but what, I cannot figure out.
> 
> I see the problem both in Centos 7.7 and 8

Known problem. The fixes are not released yet.

https://www.virtualbox.org/ticket/18917

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] Interesting update problem

[isdtor]

I had problems updating a 7.6 machine to 7.7, so I reinstalled it from scratch 
and applied all the 7.6 updates, then attempted the 7.7 upgrade again. It 
failed with the same errors. I'm wondering where the problem is?

# yum update
...
[hundreds of lines of the next line]
warning: Unable to get systemd shutdown inhibition lock
Error in PRETRANS scriptlet in rpm package 
1:java-1.8.0-openjdk-headless-1.8.0.222.b10-1.el7_7.x86_64
Error in PRETRANS scriptlet in rpm package 
1:java-11-openjdk-headless-11.0.4.11-1.el7_7.x86_64
Error in PRETRANS scriptlet in rpm package kmod-kvdo-6.1.2.41-5.el7.x86_64
mesa-libEGL-devel-18.3.4-5.el7.x86_64 was supposed to be installed but is not!
  Verifying  : mesa-libEGL-devel-18.3.4-5.el7.x86_64
 1/3285 
[repeating for dozens or hundreds of other packages]
...
Failed:

[list of all upgrade packages]

Of course mesa-libEGL-devel-18.3.4-5.el7.x86_64 is not installed, that's the 
new version. The installed version is mesa-libEGL-devel-18.0.5-4.el7_6.x86_64.

Where did it all go wrong? I tried clearing the yum cache and rebuilding the 
rpm db, no joy.

Another 7.6 machine upgraded fine, although from a smaller installed package 
set.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Postfix vs. Thunderbird on Mac OS

[isdtor]

Nicolas Kovacs writes:
> Hi,
> 
> I'm running our local school's mail server on CentOS 7, Postfix and
> Dovecot. We get quite a lot of spam, so I have the following sender
> restrictions in my /etc/postfix/main.cf:
> 
> --8<--
> # Restrictions SMTP
> smtpd_helo_restrictions = reject_unknown_helo_hostname
> smtpd_sender_restrictions = reject_unknown_sender_domain,
>   check_sender_access hash:/etc/postfix/sender_access
> smtpd_recipient_restrictions = permit_mynetworks,
>   permit_sasl_authenticated,
>   reject_rbl_client zen.spamhaus.org,
>   reject_rhsbl_reverse_client dbl.spamhaus.org,
>   reject_rhsbl_helo dbl.spamhaus.org,
>   reject_rhsbl_sender dbl.spamhaus.org
> smtpd_relay_restrictions = permit_mynetworks,
>   permit_sasl_authenticated,
>   reject_unauth_destination
> smtpd_data_restrictions = reject_unauth_pipelining
> --8<--
> 
> Most folks are using Thunderbird on Linux, and everything works
> perfectly. One single user has a MacBook Air with Thunderbird on Mac OS
> Mojave, and her outgoing mails are rejected with the following error
> message in /var/log/maillog on the server:
> 
> --8<--
> Sep 16 14:22:32 sd-48011 postfix/smtps/smtpd[14434]: NOQUEUE: reject:
> RCPT from villa.figaret.pck.nerim.net[62.212.106.47]: 450 4.7.1
> : Helo command rejected: Host not found;
> from= to= proto=ESMTP
> helo=
> --8<--
> 
> As far as I understand, it has to do with this MacBook's host
> configuration.
 
http://www.postfix.org/postconf.5.html#reject_unknown_helo_hostname

reject_unknown_helo_hostname (with Postfix < 2.3: reject_unknown_hostname)
Reject the request when the HELO or EHLO hostname has no DNS A or MX record.
The reply is specified with the unknown_hostname_reject_code parameter 
(default: 450) or unknown_helo_hostname_tempfail_action (default: 
defer_if_permit). See the respective parameter descriptions for details.
Note: specify "smtpd_helo_required = yes" to fully enforce this restriction 
(without "smtpd_helo_required = yes", a client can simply skip 
reject_unknown_helo_hostname by not sending HELO or EHLO). 

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] What about Mate Desktop on Centos 8?

[isdtor]

> >See the previous thread(s) on this list about newer versions of Mate
> >for 
> >el7:
> >
> >  https://lists.centos.org/pipermail/centos/2019-July/172916.html
> >
> >and:
> >
> >  https://lists.centos.org/pipermail/centos/2019-August/173150.html
> >
> >James Pearson
> >___
> >CentOS mailing list
> >CentOS@centos.org
> >https://lists.centos.org/mailman/listinfo/centos
> 
> Yes, those are previous posts of mine. I was hoping we would get the latest 
> version of Mate available on Centos 7.

I have successfuly built and run 1.20, based on EPEL 1.16. Upgrading those to 
1.22 was not successful, while everything builds, most desktop components just 
crash.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Mate on Centos 7

[isdtor]

Greg Bailey writes:
> On 8/7/19 8:02 AM, isdtor wrote:
> > isdtor writes:
> >
> >>>> Can I really be the only user of Mate on Centos 7??
> >>> No, definitely not. I use MATE on C7, because Gnome is, how do I
> >>> say this politely..., um, horrible. Not a KDE fan either.
> >>>
> >>> Gnome-2.x wasn't broken, didn't need to be thrown away and
> >>> replaced by something completely different.
> >> Not broken, but full of bugs that will never get fixed.
> >>
> >> I did a while back rebuild the EPEL rpms for 1.20. There are spec files I 
> >> could make available but I can't find the build environemnt setup now. It 
> >> involves mock, a custom local repo to receive the fresh builds as you 
> >> don't want to pull in the rpms from EPEL, and a build script that defines 
> >> the order, among other things. If I have time next week I can try and 
> >> locate everything.
> > I have done the hard lifting and rebuilt mate 1.22 on CentOS 7. It's not 
> > without quirks, and I haven't actually installed and tested, but I'm 
> > willing to make the srpms available - without any commitments. This might 
> > make a good addition to Nux :)
> >
> 
> 
> The person responsible for packaging the mate RPMs for EPEL offered to 
> hand that off to someone, which I considered (since I'm a Fedora/EPEL 
> packager), but was reluctant to offer without understanding how much 
> heavy lifting was involved.  Also, I wasn't sure how much the mate on 
> CentOS user community wants to stick with 1.16 vs. upgrade to 1.22.  
> What kind of "quirks" did you run into?

There's basically two.

I was building the packages under CentOS 7.5 with mock. One of the packages, 
mate-terminal, needs a newer version of vte291, i.e. the one from 7.6. No 
problem when building on 7.6+ (I hope - in process now).

The other is that mozo now requires python >= 3.5. While I managed to get SCLo 
rh-python35 into the mock chroot and the appropriate commands into the spec 
file, it would still not build because the rpm script processing python files 
was looking for /usr/bin/python3.5. Rather than figure out how to do this in 
mock, I built the rpm outside mock in an "scl enable"'d terminal and with 
/usr/bin/python3.5 a link to /opt/rh/rh-python35/...

Other than that I think I had to update one patch because the source files 
changed, and create another because some construct in C code requires C99; but 
it was easy to rewrite for older C (I'm putting this one down to sloppy coding 
by mate developers). Some rpms required updated build reqs.

All of this is relative to the 1.20 rpms I built back in December, which are in 
turn based on 1.16 from EPEL.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Mate on Centos 7

[isdtor]

isdtor writes:
> 
> > > Can I really be the only user of Mate on Centos 7??
> > 
> > No, definitely not. I use MATE on C7, because Gnome is, how do I
> > say this politely..., um, horrible. Not a KDE fan either.
> > 
> > Gnome-2.x wasn't broken, didn't need to be thrown away and
> > replaced by something completely different.
> 
> Not broken, but full of bugs that will never get fixed.
> 
> I did a while back rebuild the EPEL rpms for 1.20. There are spec files I 
> could make available but I can't find the build environemnt setup now. It 
> involves mock, a custom local repo to receive the fresh builds as you don't 
> want to pull in the rpms from EPEL, and a build script that defines the 
> order, among other things. If I have time next week I can try and locate 
> everything.

I have done the hard lifting and rebuilt mate 1.22 on CentOS 7. It's not 
without quirks, and I haven't actually installed and tested, but I'm willing to 
make the srpms available - without any commitments. This might make a good 
addition to Nux :)

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Installation question?

[isdtor]

Pete Biggs writes:
> On Tue, 2019-07-30 at 13:24 -0400, John Chludzinski wrote:
> > I've been doing a CentOS 7.6.1810 net-install since last night. The machine
> > seems ok but has been stuck with "performing post-installation setup tasks"
> > for hours. This is an old Dell T5400 box, so it isn't blazing fast but ...
> > 
> > Is there a way to pull up its skirt (so to speak) and check/monitor the
> > installation activity while installing it? Having already started the
> > installation?
> > 
> Yes, there are shells running on the alternative consoles, so if you
> are doing a GUI install then do Ctrl-Alt-F1 to get to the text console
> - that console is the one running the install and may have some error
> messages. Do Alt-F2 from there to get to a shell prompt with root
> privileges, Alt-F3 for the anaconda log, Alt-F4 for the storage log,
> Alt-F5 for other log messages and Alt-F6 to get back to the GUI
> install.

It is my experience too that starting with CentOS 7, "post-installation setup 
tasks" take up an inproportionate amount of time during. All I was able to find 
out was that the kickstart %post section was not the culprit.

It would be nice to have some detailed documentation what these 
post-installation tasks actually are. ISTR a lot of dracut this and that 
showing up in top.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Mate on Centos 7

[isdtor]

> > Can I really be the only user of Mate on Centos 7??
> 
> No, definitely not. I use MATE on C7, because Gnome is, how do I
> say this politely..., um, horrible. Not a KDE fan either.
> 
> Gnome-2.x wasn't broken, didn't need to be thrown away and
> replaced by something completely different.

Not broken, but full of bugs that will never get fixed.

I did a while back rebuild the EPEL rpms for 1.20. There are spec files I could 
make available but I can't find the build environemnt setup now. It involves 
mock, a custom local repo to receive the fresh builds as you don't want to pull 
in the rpms from EPEL, and a build script that defines the order, among other 
things. If I have time next week I can try and locate everything.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] RHSA-2019:1467 not fixed in centos

[isdtor]

> Our new build system set up uses mock on CentOS-7 to build CentOS-6 and
> CentOS-7 packages .. python seems to fail with that setup.
 
According to my notes, mock on C7 is currently broken for C5/C6 builds, but 
unfortunately I forgot to note the underlying reason ...

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Bash completion thrown by quoted option args?

[isdtor]

wwp writes:
> Hello isdtor,
> 
> 
> On Fri, 24 May 2019 09:33:55 +0100 isdtor  wrote:
> 
> > Leroy Tennison writes:
> > > I am going to take a really wild guess and say "Try replacing the 
> > > outermost quotes with single quotes or escape the double quotes around 
> > > the numeral 1".  Your second example has double quotes within double 
> > > quotes and I'm wondering if that's getting rendered as "yum 
> > > --debuglevel="  1  " install ..." (extra space added for 
> > > emphasis).  
> >  
> > The outermost quotes are not part of the command, they were only a means to 
> > set off the command typed from the surrounding text.
> > 
> > Single quotes around the option arg don't work either.
> 
> In that specific example (--debuglevel="1"), you don't need the quotes.
> But, if that's just an example and you really use command-line
> arguments that need to be quoted, for instance because they contain
> spaces, maybe you could just use \ to protect spaces like:
>  # command "a b" c
> would become:
>  # command a\ b c (2 params)
> which is different from:
>  # command a b c (3 params)
> just escaping the space to prevent bash from considering "a\ b" as two
> words).
> 
> Also, maybe it's bash completion for yum that is your problem, did you
> try disabling yum-specific completion? That would let you still the
> ability to use path completion.
 
In my case, the argument being quoted (different option) is a "*". Your method 
of escaping instead of quoting works.

I couldn't find anything yum-specific in bash-completion.

[root@localhost ~]# rpm -ql bash-completion |grep yum
[root@localhost ~]# 

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Bash completion thrown by quoted option args?

[isdtor]

Leroy Tennison writes:
> I am going to take a really wild guess and say "Try replacing the outermost 
> quotes with single quotes or escape the double quotes around the numeral 1".  
> Your second example has double quotes within double quotes and I'm wondering 
> if that's getting rendered as "yum --debuglevel="  1  " install ..." 
> (extra space added for emphasis).
 
The outermost quotes are not part of the command, they were only a means to set 
off the command typed from the surrounding text.

Single quotes around the option arg don't work either.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] Bash completion thrown by quoted option args?

[isdtor]

There was a thread about C7 bash completion back in August last year, but it 
doesn't have answers for this problem.

Example: "yum install /path/to/local/package" works fine with tab completion to 
fill in the path and package bits.

However, "yum --debuglevel="1" install ..." just gets stuck and doesn't offer 
anything. The only option is to type everything out, or type enough to use a 
wildcard. After more testing, I found that any option argument that is quoted 
breaks completion. Which in turn makes me think this is not even specific to 
yum but bash completion in general.

Bug? Upstream bug?

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] UEFI and PXE

[isdtor]

Chris Adams writes:
> Once upon a time, isdtor  said:
> > 11:06:51.413549 IP (tos 0x10, ttl 128, id 0, offset 0, flags [none], proto 
> > UDP (17), length 390)
> > 10.1.2.2.67 > 255.255.255.255.68: [udp sum ok] BOOTP/DHCP, Reply, 
> > length 362, xid 0x4007adc6, Flags [Broadcast] (0x8000)
> >   Your-IP 10.1.2.57
> >   Server-IP 10.1.2.1  <--
> >   Client-Ethernet-Address 00:1b:21:d8:69:1c
> >   file "linux-install/bootx64.efi"
> >   Vendor-rfc1048 Extensions
> > Magic Cookie 0x63825363
> > DHCP-Message Option 53, length 1: ACK
> > Server-ID Option 54, length 4: 10.1.2.2
> > Lease-Time Option 51, length 4: 43200
> > Subnet-Mask Option 1, length 4: 255.255.255.0
> > Default-Gateway Option 3, length 4: 10.1.2.250
> > Domain-Name-Server Option 6, length 8: 10.1.2.2
> > Hostname Option 12, length 5: "client"
> > Domain-Name Option 15, length 20: "foo.bar.com"
> > NTP Option 42, length 8: 10.1.2.2
> > RN Option 58, length 4: 21600
> > RB Option 59, length 4: 37800
> > TFTP Option 66, length 11: "10.1.2.1" <--
> > END Option 255, length 0
> 
> I do see a couple of differences - main one is that my boot file is in
> option 67, not the BOOTP "file" field.  Also, my option 66 is a
> hostname, not an IP.  I don't know how you tell ISC DHCP to use option
> 67 instead of the file field, but maybe that could trigger different
> client behavior?
> 
> More odd is that dnsmasq is adding a null terminator to both options 66
> and 67.  My UEFI PXE clients seem to accept it just fine though.

Yes, it looks like I'm out of luck and need to find a newer machine to test 
this with. Moving the tftp server works to an extent - server boots right into 
a grub prompt.

I went over the linux-poweredge archives and found this:

https://lists.us.dell.com/pipermail/linux-poweredge/2015-May/049810.html

In particular:
| 2.  Don't waste time w/ a R*10, the UEFI PXE boot code is buggy!  It 
misinterprets the NBP filename (DHCP option 67).  That's an old Intel bug; they 
fixed it years ago in their BIOS PXE implementation.  I'm guessing it was 
resurrected in their UEFI PXE implementation.
| 
| Most all NIC vendors (Intel, Broadcom, etc) use the Intel reference 
implementation for PXE.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] UEFI and PXE

[isdtor]

James Peltier writes:
> Welcome to the world of UEFI.  Certain UEFI versions have added additional 
> support for things like the next-server option to actually be honoured.  In 
> some versions this _is_ in fact _ignored_ and you are expected to place the 
> image on the server that answers the DHCP response.
> 
> I have been successfully booting both legacy BIOS and UEFI machines for at 
> least 3 years and know the pains.

Thanks. This appears to be the case here. The machine is a Dell 11G server. I 
upgraded all the firmwares with dsu, BIOS was at latest already. After dsu, I 
upgraded the NIC option ROM with bootutil (I'm not using the builtin BRCM NICs, 
but an Intel X520-T2 card). That's all I can do on the hardware front. And it 
*still* shows the same behaviour.

Moving tftp server it is then ...

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] UEFI and PXE

[isdtor]

> Just set up ISC DHCP on fresh CentOS 7 install and followed the redhat
> guide linked in this thread.
> Did what I thought was correct and duplicated the OPs problem.
> /me scratches head. . . off to `tcpdump -vv -nn -i ens192`. . . packets
> never lie. . .
> Vendor-Class Option 60, length 32:
> "PXEClient:Arch:7:UNDI:003000"
> 
> d'oh; I did _lower case_ a string in dhcpd.conf line on accident while
> transcribing:
> match if substring (option vendor-class-identifier, 0, 9) =
> "pxeclient";
 
Ok, this is not the case here, case is correct, and tcpdump shows that the 
correct file is requested.

However:

11:06:51.413549 IP (tos 0x10, ttl 128, id 0, offset 0, flags [none], proto UDP 
(17), length 390)
10.1.2.2.67 > 255.255.255.255.68: [udp sum ok] BOOTP/DHCP, Reply, length 
362, xid 0x4007adc6, Flags [Broadcast] (0x8000)
  Your-IP 10.1.2.57
  Server-IP 10.1.2.1  <--
  Client-Ethernet-Address 00:1b:21:d8:69:1c
  file "linux-install/bootx64.efi"
  Vendor-rfc1048 Extensions
Magic Cookie 0x63825363
DHCP-Message Option 53, length 1: ACK
Server-ID Option 54, length 4: 10.1.2.2
Lease-Time Option 51, length 4: 43200
Subnet-Mask Option 1, length 4: 255.255.255.0
Default-Gateway Option 3, length 4: 10.1.2.250
Domain-Name-Server Option 6, length 8: 10.1.2.2
Hostname Option 12, length 5: "client"
Domain-Name Option 15, length 20: "foo.bar.com"
NTP Option 42, length 8: 10.1.2.2
RN Option 58, length 4: 21600
RB Option 59, length 4: 37800
TFTP Option 66, length 11: "10.1.2.1" <--
END Option 255, length 0
11:06:51.413552 IP (tos 0x0, ttl 64, id 64565, offset 0, flags [none], proto 
UDP (17), length 84)
10.1.2.57.1943 > 10.1.2.2.69: [udp sum ok]  56 RRQ 
"linux-install/bootx64.efi" octet tsize 0 blksize 32768<--

Where: dhcp server = 10.1.2.2, tftp server 10.1.2.1, client 10.1.2.57. DHCP 
answer is all good and the client still requests the wrong server

I will check if there are any NIC fw updates. If not, the workaround is to move 
the tftp server to the dhcp server.

And I thought computers were supposed to do my bidding and not the other way 
round ...

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] UEFI and PXE

[isdtor]

Chris Adams writes:
> Once upon a time, isdtor  said:
> > We have a working PXE setup. I've tried to adapt it to UEFI as per
> > RHEL6 manual, but the client won't boot.
> 
> I have BIOS+UEFI PXE boot set up, although it took some doing.  I still
> use SYSLINUX for BIOS, but GRUB2 plus Red Hat's secure boot shim for
> UEFI.  I never could get SYSLINUX's UEFI support working very well or
> reliably, and it didn't support secure boot at all last I looked.
> 
> I also feed most of the content out via HTTP (much faster than TFTP).
> That includes generating menus on the fly from perl CGIs (I'm
> old-fashioned that way :) ).
> 
> I'm using dnsmasq as my DHCP server, so I have this in its config (where
> pxesrv.cmadams.net has IP 10.10.10.2):

Thanks for the detailed info. But my setup is different. ISC dhcpd is set up as 
per 
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/6/html/installation_guide/s1-netboot-pxe-config-efi,
 and grub.

next-server points to to the tftp server but seems to be ignored. When the 
client boots, tcpdump reports

09:02:02.911381 IP client.cisco-ipsla > dhcp-server.tftp:  56 RRQ 
"linux-install/bootx64.efi" octet tsize 0 blksize 32768
09:02:02.911403 IP dhcp-server > client: ICMP dhcp-server udp port tftp 
unreachable, length 92

on the dhcp server and nothing on the tftp server. The dhcp server also logs 
that a DHCPOFFER is made and accepted by the client.

This poster had the same problem and it was not resolved.
https://superuser.com/questions/1182862/uefi-mode-pxe-booting-doesnt-work

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] UEFI and PXE

[isdtor]

We have a working PXE setup. I've tried to adapt it to UEFI as per
RHEL6 manual, but the client won't boot.

Strangely, tcpdump shows that the client tries to download all files via
tftp from the dhcp server rather than the tftp server (they are
different). next-server is pointing to the tftp server.

Any clues?

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] howto monitor disks on a serveraid-8k?

[isdtor]

> I'd like to monitor the disks connected to a ServeRaid-8k controller in a
> server running Centos 7 such that I can know when one fails.
> 
> What's the best way to do that?

It's been a long time since I worked with ServeRaid, and things may have 
changed in the meantime.

IBM used to have a an iso with ServeRaid related tools (ibm_sw_srapp_.) 
that included Linux versions of RaidMan. There were also command line tools 
like arcconf and hrconf that I used to write my own nagios plugins.

Can't say how up to date this is.
https://www-01.ibm.com/support/docview.wss?uid=ibm1SERV-RAID

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] CentOS 7.6 kickstart error

[isdtor]

Steve Clark writes:
> On 03/06/2019 07:12 AM, isdtor wrote:
> > I am testing a CentOS 7.6 kickstart installation. After kickstart was 
> > initiated,
> > the installation stops at some point where a sort of table is printed under
> > "Installation", and the item that fails is 4 - Software selection, Error
> > checking software selection.
> >
> > I have checked /tmp/packaging.log and /tmp/anaconda.log, but cannot find any
> > errors here that would prevent installation.
> >
> > Poor error messages, no usable lead for debug.
> >
> Hi,
> 
> I have run into this - in my experience it means there is some dependency 
> missing.
> And you are correct trying to find the error is a PITA.
 
I figured out a different way, less involved than the one proposed by Gregory.

The package selection in the kickstart file essentially consists of a custom 
group to keep it short. So I took a 7.5 machine and then ran a group update off 
the 7.6 custom repo. The packages that make the update fail are new in 7.6, and 
the 7.6 kickstart started working once I removed them from the repo. They were 
the grub2-ppc* packages.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] CentOS 7.6 kickstart error

[isdtor]

I am testing a CentOS 7.6 kickstart installation. After kickstart was initiated,
the installation stops at some point where a sort of table is printed under
"Installation", and the item that fails is 4 - Software selection, Error
checking software selection.

I have checked /tmp/packaging.log and /tmp/anaconda.log, but cannot find any
errors here that would prevent installation.

Poor error messages, no usable lead for debug.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] VNC question

[isdtor]

> No.  Users can run vncserver and attach to them like you could before,
> or you can run Xvnc -inetd, just as a systemd service/socket pair
> instead of out of xinetd.
> 
> The black screen problem that you mentioned does sound familiar --
> I've seen it with VNC clients that don't support OpenGL, with the
> GNOME desktop (which uses a compositing display manager), it just
> crashes when you log in.

Looked at this a bit more. There is a crash, but for a different reason:

Dec 19 07:59:31 host dbus-daemon: YPBINDPROC_DOMAIN: Domain not bound
Dec 19 07:59:31 host dbus-daemon: YPBINDPROC_DOMAIN: Domain not bound
Dec 19 07:59:31 host gnome-session-binary[12324]: ERROR: Failed to connect to 
system bus: Exhausted all available authentication mechanisms (tried: EXTERNAL, 
DBUS_COOKIE_SHA1, ANONYMOUS) (available: EXTERNAL, DBUS_COOKIE_SHA1, 
ANONYMOUS)#012aborting...
Dec 19 07:59:31 host gnome-session: gnome-session-binary[12324]: ERROR: Failed 
to connect to system bus: Exhausted all available authentication mechanisms 
(tried: EXTERNAL, DBUS_COOKIE_SHA1, ANONYMOUS) (available: EXTERNAL, 
DBUS_COOKIE_SHA1, ANONYMOUS)
Dec 19 07:59:31 host gnome-session: aborting...

I've seen this before, and the solution was to make sure that the NISDOMAIN is 
defined in /etc/sysconfig/network.

https://marc.info/?l=centos=152806243921469=2

NIS setup is correct and working, question is why it is being ignored by dbus.

After restarting dbus, there is still a crash, but a different log.

Dec 19 08:22:30 host org.a11y.Bus: Activating service 
name='org.a11y.atspi.Registry'
Dec 19 08:22:31 host org.a11y.Bus: Successfully activated service 
'org.a11y.atspi.Registry'
Dec 19 08:22:31 host org.a11y.atspi.Registry: SpiRegistry daemon is running 
with well-known name - org.a11y.atspi.Registry
Dec 19 08:22:31 host dbus[25267]: [system] Activating via systemd: service 
name='org.freedesktop.login1' unit='dbus-org.freedesktop.login1.service'
Dec 19 08:22:56 host gnome-session-binary[28570]: WARNING: Failed to connect to 
systemd: Error calling StartServiceByName for org.freedesktop.login1: Timeout 
was reached
Dec 19 08:22:56 host kernel: gnome-session-b[28570]: segfault at 8 ip 
004216f1 sp 7ffdfcfc77b0 error 4 in 
gnome-session-binary[40+45000]
Dec 19 08:22:56 host gnome-session: gnome-session-binary[28570]: WARNING: 
Failed to connect to systemd: Error calling StartServiceByName for 
org.freedesktop.login1: Timeout was reached
Dec 19 08:22:56 host gnome-session: gnome-session-binary[28570]: 
GLib-GObject-WARNING: invalid (NULL) pointer instance
Dec 19 08:22:56 host gnome-session: gnome-session-binary[28570]: 
GLib-GObject-CRITICAL: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE 
(instance)' failed
Dec 19 08:22:56 host gnome-session: gnome-session-binary[28570]: 
GLib-GIO-CRITICAL: g_dbus_proxy_call_sync_internal: assertion 'G_IS_DBUS_PROXY 
(proxy)' failed
Dec 19 08:22:56 host gnome-session-binary[28570]: GLib-GObject-WARNING: invalid 
(NULL) pointer instance
Dec 19 08:22:56 host gnome-session-binary[28570]: GLib-GObject-CRITICAL: 
g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
Dec 19 08:22:56 host gnome-session-binary[28570]: GLib-GIO-CRITICAL: 
g_dbus_proxy_call_sync_internal: assertion 'G_IS_DBUS_PROXY (proxy)' failed
Dec 19 08:22:56 host dbus[25267]: [system] Failed to activate service 
'org.freedesktop.login1': timed out
Dec 19 08:22:56 host abrt-hook-ccpp: Process 28570 (gnome-session-binary) of 
user 14728 killed by SIGSEGV - dumping core

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] VNC question

[isdtor]

Jonathan Billings writes:
> On Wed, Dec 19, 2018 at 11:56:11AM +0000, isdtor wrote:
> > What you describe doesn't make much sense to me either.
> > 
> > In this case, there are no user logins on the console, this is meant
> > to be a remote login server. Anyone logging in via vnc gets the
> > black screen treatment. There is no login screen, only the vnc
> > password prompt. 
> 
> How are they 'logging in via vnc'?  How did you set up the VNC server? 

They are logging in through ssh to manually start vncserver, then connect to it.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] VNC question

[isdtor]

Mike McCarthy, W1NR writes:
> 
> On 12/19/18 4:36 AM, isdtor wrote:
> > We have run into the infamous black screen problem with tigervnc under 
> > CentOS7, which prompted me to look into how vnc is configured here.
> >
> > https://access.redhat.com/solutions/966063
> >
> > Am I reading this correctly - root needs to set up a systemd vnc service 
> > for every user and display individually? Compared to e.g. CentOS before 7, 
> > or indeed any other Linux/Unix system where vnc is completely under user 
> > control?
> >
> 
> openSUSE always spawned VNC sessions for each user through xinetd. The
> user did not have "control" of the sessions.
 
Noted.

> Do you get a login screen? Does the screen go "black" after login? If
> so, in my experience, the user logging in already has a desktop session
> running (usually on the console). Make sure to try logging in with a
> user that is not already logged in. Linux can deal with multiple
> DIFFERENT users logged in but the desktops can only deal with one login
> and home directory per user.

What you describe doesn't make much sense to me either.

In this case, there are no user logins on the console, this is meant to be a 
remote login server. Anyone logging in via vnc gets the black screen treatment. 
There is no login screen, only the vnc password prompt.

For this type of machine, multi-user.target should be sufficient, although it 
is set to graphical.target right now.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] VNC question

[isdtor]

We have run into the infamous black screen problem with tigervnc under CentOS7, 
which prompted me to look into how vnc is configured here.

https://access.redhat.com/solutions/966063

Am I reading this correctly - root needs to set up a systemd vnc service for 
every user and display individually? Compared to e.g. CentOS before 7, or 
indeed any other Linux/Unix system where vnc is completely under user control?

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] CentOS7 kickstart question

[isdtor]

Phelps, Matthew writes:
> On Fri, Dec 14, 2018 at 10:04 AM isdtor  wrote:
> 
> >
> > > > So the syntax looks to be
> > > >
> > > > repo --name=epel --baseurl=nfs://server:/path
> > > >
> > > > that colon after server is not a spelling error.
> > > > https://pykickstart.readthedocs.io/en/latest/kickstart-docs.html#id48
> > >
> > > That seems to work now. Some error messages made it look like nfs:
> > wasn't supported at all.
> > > Thanks.
> >
> > Well, I spoke too soon - forgot to update the template and the test vm
> > still kickstarted with http repos.
> >
> > This is not working, the problem persists as described in my original post.
> >
> >
> Try using the IP address of the nfs server. e.g:
> 
>  repo --name=epel --baseurl=nfs://10.0.0.10:/path
 
Have it working now as per documentation. Thanks for the responses.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] CentOS7 kickstart question

[isdtor]

Phelps, Matthew writes:
> On Fri, Dec 14, 2018 at 10:04 AM isdtor  wrote:
> 
> >
> > > > So the syntax looks to be
> > > >
> > > > repo --name=epel --baseurl=nfs://server:/path
> > > >
> > > > that colon after server is not a spelling error.
> > > > https://pykickstart.readthedocs.io/en/latest/kickstart-docs.html#id48
> > >
> > > That seems to work now. Some error messages made it look like nfs:
> > wasn't supported at all.
> > > Thanks.
> >
> > Well, I spoke too soon - forgot to update the template and the test vm
> > still kickstarted with http repos.
> >
> > This is not working, the problem persists as described in my original post.
> >
> >
> Try using the IP address of the nfs server. e.g:
> 
>  repo --name=epel --baseurl=nfs://10.0.0.10:/path

No joy.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] CentOS7 kickstart question

[isdtor]

> > So the syntax looks to be
> > 
> > repo --name=epel --baseurl=nfs://server:/path
> > 
> > that colon after server is not a spelling error.
> > https://pykickstart.readthedocs.io/en/latest/kickstart-docs.html#id48
>  
> That seems to work now. Some error messages made it look like nfs: wasn't 
> supported at all.
> Thanks.

Well, I spoke too soon - forgot to update the template and the test vm still 
kickstarted with http repos.

This is not working, the problem persists as described in my original post.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] CentOS7 kickstart question

[isdtor]

Stephen John Smoogen writes:
> On Fri, 14 Dec 2018 at 05:02, isdtor  wrote:
> >
> > Is it not possible to use an nfs based repo for kickstart under CentOS 7.5?
> >
> > E.g.
> >
> > repo --name=epel --baseurl=file://server/path/to/local/copy/of/epel
> >
> 
> So the syntax looks to be
> 
> repo --name=epel --baseurl=nfs://server:/path
> 
> that colon after server is not a spelling error.
> https://pykickstart.readthedocs.io/en/latest/kickstart-docs.html#id48
 
That seems to work now. Some error messages made it look like nfs: wasn't 
supported at all.
Thanks.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] CentOS7 kickstart question

[isdtor]

Is it not possible to use an nfs based repo for kickstart under CentOS 7.5?

E.g.

repo --name=epel --baseurl=file://server/path/to/local/copy/of/epel

With trial and error I figured out that this is the correct syntax to use for 
an nfs-based repo. But packages from this repo in the %packages section are not 
found.

You have specificed that the package 'bla' should be installed. This package 
does not exist. ...

It works with http off the same server and location, but I'd rather not use 
that.

NFS installation as such, using nfs --server ... -- dir ..., off the same 
server and filesystem is working fine. So there is no problem here with nfs or 
repo setup.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] [OT] EPEL update?

[isdtor]

Greg Bailey writes:
> On 12/03/2018 04:00 AM, isdtor wrote:
> > 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.
> > 
> > 
> 
> You're not the first person to make this request:
> 
> https://bugzilla.redhat.com/show_bug.cgi?id=1436260
> 
> In comment #2 of that bug report, there's a reference to enabling a copr
> repo with MATE 1.18.x, with more info at:
> 
> https://copr.fedorainfracloud.org/coprs/raveit65/Mate-GTK3/

Thanks, I'm unfamiliar with this repo. Looks like the owner is the same guy who 
built the F29 mate packages (1.20).

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] [OT] EPEL update?

[isdtor]

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.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Panic / EL6 / KVM / kernel-2.6.32-754.2.1.el6.x86_64

[isdtor]

> >>> Does some one have problems related to KVM with
> >>> kernel-2.6.32-754.3.5.el6.x86_64 ??
> >>
> >> Yes, the exact same thing happened here, and I suspect it is related to
> >> older cpus that don't get any Spectre/Meltdown updates.
> >
> >
> > Thanks for the feedback. I' was assuming that some kind of
> > Spectre/Meltdown fixes are causing this.
> >
> 
> Doesn downgrading qemu as I proposed in the other mail fix it in your case?
> 
> I'm interested because in my case I'm having the issue on two older AMD
> CPUs, not Intel.
 
Simon, downgrading does not fix the problem in my case. I upgraded to the 3.5 
kernel, disabled libvirtd and libvirtd-guests, and rebooted. Once the machine 
was up, I started the libvirtd service and the machine crashed immediately.

Old: qemu-img-0.12.1.2-2.506.el6_10.1, qemu-kvm-0.12.1.2-2.506.el6_10.1 (crash 
on 2.6.32-754.3.5)
New: qemu-img-0.12.1.2-2.503.el6_9.6,  qemu-kvm-0.12.1.2-2.503.el6_9.6  (crash 
on 2.6.32-754.3.5)

In Leon's and my case, the culprit is kernel 2.6.32-754.3.5. In CentOS bug 
0015067, the bad kernel is 2.6.32-754.2.1, wich works fine here. The difference 
might be how different cpus are handled.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Panic / EL6 / KVM / kernel-2.6.32-754.2.1.el6.x86_64

[isdtor]

Leon Fauster via CentOS writes:
> Since the update from kernel-2.6.32-754.2.1.el6.x86_64 
> to kernel-2.6.32-754.3.5.el6.x86_64 I can not boot my 
> KVM guests anymore!? The workstation panics immediately! 
> 
> I would not have expected this behavior now (last phase of OS). 
> It was very robust until now (Optiplex Workstation). I see some KVM 
> related lines in the changelog.diff. Before swimming upstream:
> 
> Does some one have problems related to KVM with 
> kernel-2.6.32-754.3.5.el6.x86_64 ??

Yes, the exact same thing happened here, and I suspect it is related to older 
cpus that don't get any Spectre/Meltdown updates.

IBM x3250
Intel(R) Xeon(R) CPU   E3110  @ 3.00GHz

This is a dual-core cpu of similar vintage to yours (can we have a model #?), 
pre-2010.

There goes a cheap and reliable VM dev machine :-/

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] CentOS 7.5 gui login root only

[isdtor]

isdtor writes:
> Prasad K writes:
> > I have seen similar issues when user shell profiles like .bash_profile or
> > .bashrc has some errors.
> > Are users invoking other shells from their default shell ? this usually
> > breaks X11 start-up scripts.
>  
> The same user can login find through the gui when the system was installed 
> with the CentOS DVD directly. Package selection was the last option (create 
> workstation or something) with most but not all extra package groups that are 
> selectable at this point.
> 
> This is a KVM machine, I have tried the default (cirrus) and vga, no change.
 
This bug report put me on the right track: 
https://bugs.freedesktop.org/show_bug.cgi?id=66867, with

/var/log/messages: gnome-session-binary[12345]: ERROR: Failed to connect to 
system bus: Exhausted all available authentication mechanisms

and associated YPPROC_DOMAIN not found entries.

The NIS domain must be defined and correct in /etc/sysconfig/network so that 
it's known to dbus when it starts. This is different from CentOS6 and before 
where the contents of this file largely didn't matter for NIS and /etc/yp.conf 
was sufficient.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] CentOS 7.5 gui login root only

[isdtor]

Prasad K writes:
> I have seen similar issues when user shell profiles like .bash_profile or
> .bashrc has some errors.
> Are users invoking other shells from their default shell ? this usually
> breaks X11 start-up scripts.
 
The same user can login find through the gui when the system was installed with 
the CentOS DVD directly. Package selection was the last option (create 
workstation or something) with most but not all extra package groups that are 
selectable at this point.

This is a KVM machine, I have tried the default (cirrus) and vga, no change.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] CentOS 7.5 gui login root only

[isdtor]

> Sounds like an authorization issue. Have you checked both
> /var/log/messages and /var/log/secure? If you're using /etc/password, are
> its permissions and ownership correct? Are the user's home directories
> owned by them?
 
Nothing relevant in these log files.  The test user is in NIS and home 
directory is auto-mounted.  All of this works, user can login through text 
console and ssh.  selinux is disabled.  But even startx isn't working, and 
again the Xorg log doesn't give any indication what might be the problem.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] CentOS 7.5 gui login root only

[isdtor]

Taking first steps on CentOS 7 1804.

Logging into the Gnome/Gnome classic desktop from gdm works only for root. For 
other users, the screen flashes and the login screen returns. KDE/Plasma login 
is successful but ends up with a black screen with mouse pointer while all 
desktop processes appear to be running.

The CentOS 7 system is running in a CentOS6 KVM virtual machine, which may be 
the problem. I have no physical machine for testing right now.

These logins work for non-root users when the system is built from the CentOS 7 
DVD. The non-working installation stems from a kickstart install which 
essentially includes a much larger number of packages, some 6k vs. 2.5k from 
DVD install). Maybe there are conflicts, but I have not been able to isolate 
anything.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] How insecure is NIS ? Possible alternatives ?

[isdtor]

> You don't even need to crack them yourself.
> If you have the hashes, you can just use rainbow-tables available online,
> sometimes for a small fee.
 
There are salted hashes for that ...

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] How insecure is NIS ? Possible alternatives ?

[isdtor]

> Over the next month I have to setup a new network in a local school, and
> I wonder if I should use NIS/NFS. I still have my own documentation,
> it's simple and somewhat bone-headed to setup, and it just works.
 
In my opionion, there is a serious gap in this area. It's either NIS, simple, 
easy to setup yet insecure, or LDAP/FreeIPA/RH Id management server at a 
complexity at least one order of magnitude beyond NIS.

There's also the option of using AD if such infrastructure exists. RH ID 
management has been completely dismissed by colleagues who know both it and AD, 
and favour the latter.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Install CentOS 7 over serial port on router board ?

[isdtor]

Nicolas Kovacs writes:
> Hi,
> 
> I have to install CentOS 7 for a client, to act as cache & filtering
> proxy using Squid.
> 
> I'd like to use this piece of specialized hardware :
> 
> http://store.calexium.com/fr/systeme-pre-assemble/869-systeme-pre-assemble-rackmatrix-apu-amd-gx-412tc-quatre-coeurs-1-ghz.html
> 
> There is no VGA or HDMI video output, just a serial port to connect to,
> and then three NICs and two USB ports.
> 
> I've never installed CentOS over a serial console, so I don't even know
> if it's possible in the first place. Has anyone ever done something like
> that ?
> 
> Any suggestions ?

I haven't done this with Linux, only Soekris+OpenBSD, but the principles are 
the same. PXE, kickstart, monitoring via serial port. Change console settings 
to point to the serial port as per Giles. Use a USB-to-serial converter to 
connect to a laptop running a terminal program, or serial cable with a dekstop 
that still has a serial port. May need a null-modem cable, I don't remember.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] Good work, Red Hat!

[isdtor]

Delivered as per https://access.redhat.com/articles/3311301. This is good news. 
Backporting those updates across three gcc versions does not look like the 
easiest exercise to me.

$ rpm -qp --changelog gcc-4.4.7-18.el6_9.2.x86_64.rpm |head -n 6
* Wed Jan 31 2018 Jeff Law  4.4.7-18.2
- Fix indirect_jump/tablejump patters for retpolines (#1535656)

* Tue Jan 23 2018 Jeff Law  4.4.7-18.1
- Retpoline support (#1535656)

$ rpm -qp --changelog kernel-2.6.32-696.23.1.el6.x86_64.rpm
...
* Sat Feb 10 2018 Jan Stancek  [2.6.32-696.23.1.el6]
- [scsi] avoid a permanent stop of the scsi device's request queue (Ewan Milne) 
[1519857 1513455]
- [x86] retpoline/hyperv: Convert assembler indirect jumps (Waiman Long) 
[1543022 1535645]
- [x86] spec_ctrl: Upgrade GCC retpoline warning to an error for brew builds 
(Waiman Long) [1543022 1535645]
- [x86] retpoline: Don't use kernel indirect thunks in vsyscalls (Waiman Long) 
[1543022 1535645]
- [x86] spec_ctrl: Add a read-only retp_enabled debugfs knob (Waiman Long) 
[1543022 1535645]
...
 
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] Meltdown and Spectre

[isdtor]

Does anyone know if Red Hat are working on backporting improved mitigation 
techniques and features from newer, 4.14.14+ kernels?

$ grep . /sys/devices/system/cpu/vulnerabilities/*
/sys/devices/system/cpu/vulnerabilities/meltdown:Mitigation: PTI
/sys/devices/system/cpu/vulnerabilities/spectre_v1:Vulnerable
/sys/devices/system/cpu/vulnerabilities/spectre_v2:Vulnerable: Minimal generic 
ASM retpoline
$ 

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] /lib/firmware/microcode.dat update on CentOS 6

[isdtor]

> OK, so color me confused about the timing in all this.
> 
> Do we update the microcode now or do we wait until the latest microcode_ctl
> rpm is available and then tackle this issue?
 
The message is: stay away from microcode updates because they're broken right 
now. Intel may or may not release fixes next week to be tested by OEMs.

Once working updates are available, OEMs will integrate them into their 
firmware/BIOS releases. That is one method to avail of microcode updates. The 
other method is loading during OS boot (via udev rule), with codes provided by 
the microcode_ctl rpm. It looks like Red Hat are now staying away from that; in 
any case, their previous rpm only included ucodes for three cpus. I did not 
check if the microcode.dat included more updates than that.

Method number 2b is to download the firmware from Intel directly and provide it 
in the locations defined by the microcode_ctl rpm. Then it's up to you to do 
the QA.

If your RHEL/CentOS is fully up to date, you're protected against variant 
1/Spectre and Meltdown. Red Hat have done a pretty good job to backport those 
patches from upstream. GKH's blog is worth a read.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] C6 KPTI cpuinfo flag?

[isdtor]

Robert Arkiletian writes:
> Noticed C6 had a kernel update on Friday.
> 2.6.32-696.18.7.el6.x86_64
> What is the flag in /proc/cpuinfo that indicates the KPTI patch for
> Meltdown CVE-2017-5754 for C6?
> 
> Some distros are using "kaiser" some like Fedora are using "pti". Also
> noticed some (like Fedora) are displaying "cpu_insecure" under the
> bugs: heading of cpuinfo.

None that I know of, but check out https://access.redhat.com/articles/3311301.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] dbus-daemon and CentOS6

[isdtor]

We are seeing high load developing over time on some machines that have dozens 
of user sessions. One common characteristic is that dbus-daemon uses near 100% 
cpu.

Red Hat seems to be aware of the problem, but the solutions are available to 
subscribers only.

https://access.redhat.com/solutions/110403
https://access.redhat.com/solutions/363554

Does anyone have access and can summarize here?

Thanks.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Cron sending to root after changing MAILTO

[isdtor]

> Best is to define a mail alias for the root user. That way you have it
> defined at a single place for all occurances of mail destined to root.

postfix only uses the aliases map for local delivery. If the recipient email 
address is fully qualified, local delivery is not even in the picture (and I 
literally mean "the big picture", 
http://www.porcupine.org/postfix/doc/big-picture.html). The only way to get 
local delivery involved here is to add root to masquerade_exceptions.

postfix is not the problem here as the log shows

... to=, orig_to= ...

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] CentOS 6 and pxeboot

[isdtor]

> Also, in case you're ever interested, I've written a script that 
> generates suitable IPv4-based filenames for pre-default usage:
> 
>https://github.com/heinlein/pxehex
 
gethostip ... I simply rebuilt the relevant C5 rpms for C6, 
system-config-netboot and system-config-netboot-cmd, IIRC.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] OT: systemd Poll

[isdtor]

Leroy Tennison writes:
> Another huge concern: It breaks, someone else has to fix it because it's in 
> the C source - after it reaches a high enough priority.  At least with 
> scripts you could conceivably hack it.  From what I've read there is some 
> ability to get systemd to defer to a script, I'm going to have to become an 
> expert at that.

Best of both worlds - power-grabbing systemd plus convoluted init scripts.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] OT: systemd Poll

[isdtor]

> er, I meant to add that the 09: seems to correspond with the enp9s* and the
> 0a: seems to correspond with the enp10s*

I wrote myself a little script that uses /sys/class/net, ethtool and lspci to 
identify which interface corresponds to which bus slot/lspci entry.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] From Networkmanager to self managed configuration files

[isdtor]

Did I see an implicit "do as Red Hat says or else" there somewhere? Not 
appropriate. Linux is not Windows (yet). In the heat of the moment it may 
easily be forgotton that Linux is all about choice. We choose to run CentOS, 
and we choose to run it the way we see fit. We appreciate the efforts that go 
into the *Community* *Enterprise* OS, and if you have dealt with buggy crap 
like Ubuntu or Fedora, you appreciate it even more. This does not imply 
deference to upstream.

That statement about "effectively [running] your own Linux distribution" is 
scaremongering, at best. If there's one thing I've learned on this list, it's 
realizing how many use cases, scenarios and solutions there are that can make 
approaching the topic at hand without prejudice challenging at times.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] MRTG and eth0

[isdtor]

Matt writes:
> Is there an easy way to graph ethernet eth0 on Centos 7 with MRTG
> without using SNMP?  I thought I found a way to do this in past by
> using a shell script to poll the interface but cannot find it back.

Yes, this is very easy and the required script is very simple. See 
http://oss.oetiker.ch/mrtg/doc/mrtg-reference.en.html, "External Monitoring 
Scripts". You can write a small script around ifconfig or ip, as you wish.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Wich web browser on CentOS6 ?

[isdtor]

>   You can also try the mainline version of Pale Moon if you want 64-bit.
> http://linux.palemoon.org/  It uses gtk2, but I don't know if it's
> compatible with other old libraries that CentOS 6 uses.  My build goes
> out of its way to be compatible with older libraries.

I did once build pm on CentOS6 as poc, but after switched to the distributed 
binaries. 26.x is the end of line for CentOS6, and I haven't tried building 
27.x. Maybe I'll try that, addressing the library situation with custom or 
static versions.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] How to avoid "firstboot" in CentOS 7 kickstart

[isdtor]

> Has this been tested?  My understanding is that systemctl doesn't work in
> chroots, and can't be used in %post.

I've certainly used it that way in Fedora. chroot /mnt/systemimage
systemctl --no-reload disable ...
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] OT: Blank mails from this list

[isdtor]

> The problem seems to occur with all sorts of content types and encoding.
> I've now installed Office 2016, and the same problem occurs, only worse.

Irrelevant. It's Exchange that messes things up. Switching to tb will
most likely not help.

Set yourself up with a personal email account that is not going
through Exchange, subscribe to this list, and then compare the full
messages, headers and all, from both sources. This place of ork uses
O365, and the Exchange server is adding so much crap to headers and
body that message size triples or worse. Certain MIME types break. MS
support doesn't have the technical background to understand these
issues when you open a case.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Flash player beta

[isdtor]

 
> FYI, this has been reported on the Adobe "Flash Player Beta Channel" forum,
> and I've +1ed it. I would suggest doing the same to add some more pressure
> on them.
> 
> 
> https://forums.adobe.com/thread/2209127   (Adobe sign-in required)
 
I didn't see anything in the release notes, but the current release is working 
now on 6.8. Looks like they were listening.

It doesn't change my opinion about luser corporations who think it's ok to 
build a flash-based management interface for their wares (looking at you, 
VMware).

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] An 'orrible question: Outlook 365 under wine on CentOS?

[isdtor]

Fabian Arrotin writes:
[...] 
> For a previous job, I was using davmail (http://davmail.sourceforge.net)
> to act as a imap/caldav/ldap gateway between my Thunderbird and the OWA.
> I never tested against outlook365 but a simple google search seems to
> indicate that it's doable/working

Going through various stages of the corporate email outsourcing craze with 
different versions of Exchange, I have never ever gotten davmail to work. Never 
tested it with o365, and don't care as long as they don't cancel imap here. 
Don't see that happening, however. 

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos