[CentOS] systemd: SIGPWR handler for Centos 7.2?

[Harald Dunkel]

Hi folks,

it seems that sigpwr.target is just a dummy. Something
like
kill -PWR 1
or
systemctl isolate sigpwr.target

is visible in the journal, but it does not power down the
host.

This breaks a clean shutdown of LXContainers setup with
Centos 7.2. I would guess there are problems with UPS
monitors, too.


Is there a workaround? Every helpful comment is highly
appreciated

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

[CentOS] upgrade 7.4 --> 7.5: dbus broken

[Harald Dunkel]

Hi folks,

after upgrading a Centos container (LXC) from 7.4 to 7.5 I got
this:

# systemctl status
Failed to get D-Bus connection: Connection refused

# busctl
Failed to connect to bus: Connection refused

# ps -ef | grep db[u]s
dbus55 1  0 Jul02 ?00:00:00 /usr/bin/dbus-daemon --system 
--address=systemd: --nofork --nopidfile --systemd-activation

# lsof -p 55
COMMAND   PID USER   FD  TYPE DEVICE SIZE/OFF  NODE NAME
dbus-daem  55 dbus  cwd   DIR8,4 4096130819 /
dbus-daem  55 dbus  rtd   DIR8,4 4096130819 /
dbus-daem  55 dbus  txt   REG8,4   223344133569 
/usr/bin/dbus-daemon
dbus-daem  55 dbus  DEL   REG8,4 393485 
/var/lib/sss/mc/initgroups
dbus-daem  55 dbus  mem   REG8,437240150982 
/usr/lib64/libnss_sss.so.2
dbus-daem  55 dbus  mem   REG8,462184150786 
/usr/lib64/libnss_files-2.17.so
dbus-daem  55 dbus  mem   REG8,468192141459 
/usr/lib64/libbz2.so.1.0.6
dbus-daem  55 dbus  mem   REG8,490664140578 
/usr/lib64/libz.so.1.2.7
dbus-daem  55 dbus  mem   REG8,499944150835 
/usr/lib64/libelf-0.170.so
dbus-daem  55 dbus  mem   REG8,419896140110 
/usr/lib64/libattr.so.1.1.0
dbus-daem  55 dbus  mem   REG8,4   402384132708 
/usr/lib64/libpcre.so.1.2.0
dbus-daem  55 dbus  mem   REG8,488776150757 
/usr/lib64/libgcc_s-4.8.5-20150702.so.1
dbus-daem  55 dbus  mem   REG8,419776150776 
/usr/lib64/libdl-2.17.so
dbus-daem  55 dbus  mem   REG8,4   297360151443 
/usr/lib64/libdw-0.170.so
dbus-daem  55 dbus  mem   REG8,4   106848150792 
/usr/lib64/libresolv-2.17.so
dbus-daem  55 dbus  mem   REG8,419384141564 
/usr/lib64/libgpg-error.so.0.10.0
dbus-daem  55 dbus  mem   REG8,4   535064141290 
/usr/lib64/libgcrypt.so.11.8.2
dbus-daem  55 dbus  mem   REG8,485952150956 
/usr/lib64/liblz4.so.1.7.5
dbus-daem  55 dbus  mem   REG8,4   157424140323 
/usr/lib64/liblzma.so.5.2.2
dbus-daem  55 dbus  mem   REG8,48150794 
/usr/lib64/librt-2.17.so
dbus-daem  55 dbus  mem   REG8,4  1139680150778 
/usr/lib64/libm-2.17.so
dbus-daem  55 dbus  mem   REG8,420032140130 
/usr/lib64/libcap.so.2.22
dbus-daem  55 dbus  mem   REG8,4  2173512146385 
/usr/lib64/libc-2.17.so
dbus-daem  55 dbus  mem   REG8,4   144792144798 
/usr/lib64/libpthread-2.17.so
dbus-daem  55 dbus  mem   REG8,423968141464 
/usr/lib64/libcap-ng.so.0.0.0
dbus-daem  55 dbus  mem   REG8,4   127096146315 
/usr/lib64/libaudit.so.1.0.0
dbus-daem  55 dbus  mem   REG8,4   155784150814 
/usr/lib64/libselinux.so.1
dbus-daem  55 dbus  mem   REG8,4   173320140201 
/usr/lib64/libexpat.so.1.6.0
dbus-daem  55 dbus  mem   REG8,4   203800151456 
/usr/lib64/libsystemd.so.0.6.0
dbus-daem  55 dbus  mem   REG8,4   333408144514 
/usr/lib64/libdbus-1.so.3.14.14
dbus-daem  55 dbus  mem   REG8,4   164240150767 
/usr/lib64/ld-2.17.so
dbus-daem  55 dbus0u  CHR1,3  0t0 129677343 
/dev/null
dbus-daem  55 dbus1u unix 0x8f56b7b2cc00  0t0 129677608 socket
dbus-daem  55 dbus2u unix 0x8f56b7b2cc00  0t0 129677608 socket
dbus-daem  55 dbus3u unix 0x8f563800  0t0 129676115 
/run/dbus/system_bus_socket
dbus-daem  55 dbus4u  a_inode   0,110  8547 
[eventpoll]
dbus-daem  55 dbus5r  REG8,4 10406312393485 
/var/lib/sss/mc/initgroups (deleted)
dbus-daem  55 dbus6u sock0,8  0t0 129677256 
protocol: NETLINK
dbus-daem  55 dbus7r  a_inode   0,110  8547 inotify
dbus-daem  55 dbus8u unix 0x8f56b80c4c00  0t0 129677257 socket
dbus-daem  55 dbus9u unix 0x8f56ba3aec00  0t0 129677258 socket
dbus-daem  55 dbus   10u unix 0x8f56b7681000  0t0 129681025 
/run/dbus/system_bus_socket

Please note the "/run/dbus/system_bus_socket". AFAICT thats new. Shouldn't it 
listen
on /var/run/dbus/system_bus_socket for backward compatibility as well?


Is there is a way to fix this? Every helpful comment is highly appreciated.
Harri
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] upgrade 7.4 --> 7.5: dbus broken

[Harald Dunkel]

After a manual fix I have that, too. Point is that for historic
hosts this symlink doesn't exist. The upgrade fails due to dbus
becoming unavailable. And the next reboot fails, too, because
the symlink is not created automatically.

Can you confirm this?


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

Re: [CentOS] how to activate the network after an installation

[Harald Dunkel]

Hi Ralf,

On 1/21/19 11:39 AM, Ralf Prengel wrote:


Hallo,

I can t find the switch to activate the network after an installation without 
gui.
service network start doesn t work and I don t find any other commands.



If the setuptool package is not installed, then I would suggest to
use ip or ifconfig to temporarily assign a network configuration.
Then use yum to install the setuptool package.

Use "setup" to configure network devices, directory services and
runtime services in your favorite terminal window.


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

[CentOS] using RedHat binary packages?

[Harald Dunkel]

Hi folks,

AFAIK CentOS uses RedHat's source RPMs for building the next CentOS
release. I am not sure about the bootstrap procedure and the infra-
structure packages, so lets put these corner cases aside.

RedHat's "regular" binary and source packages are based on open source
(GPL2, GPL3, Apache license, whatever). For building the binary RPMs
other open source RPMs with compatible license conditions are used.

My question is:

Are RedHat's binary RPMs "poisoned" somehow, making it impossible for
CentOS to redistribute RedHat's *binary* packages without going to jail?


Every insightful comment is highly appreciated.

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