Postings by Kai Schaetzl

smtpd_delay_reject with rspamd milter

I'm having trouble with access_maps kicking in after an upgrade from a
Postfix 2.something to Postfix 3.1. on Ubuntu 14.06 and using postscreen
and rspamd milter.

After some testing I'm not sure yet, but it looks like the recommended
smtpd_delay_reject = yes in connection with having the access_map checks
listed in the smtpd_recipient_restrictions is the cause of this.

how to update from 5.8 to 5.latest?


I revived an old disk with CentoS 5.8 on it and want to update it to
5.latest (=5.11). However, it insists on getting 5.8 files. From the past
I remember I would get a major release jump from 5.n to 5.m automatically.
Or do I remember this wrong?
I googled a bit around, but couldn't really find something similar.

How do I update now? The repo file looks exactly like on machines that are
up to 5.11.

sshd_config AllowUsers syntax wrong in documentation

It seems the syntax for AllowUsers in sshd_config is not the same that is
given in man sshd_config and in several documentation on the web.
(<a href="" title=""></a>)


AllowUsers root

does work.

AllowUsers root username

does not work.

If I try to login as root I get "User root from <hostname> not allowed
because not listed in AllowUsers".

Run one-time startup script

I have to change IP numbers across a number of virtual and physical
machines because of network center move. This has to be done before
network startup, of course. I'm thinking about the best method to do this.
Where should I include/init this script? Or would it rather make more
sense to do this on the last shutdown?

Changes largely involve removing old files and putting new files in place
(resolv.conf, hosts, sysconfig/network + network-scripts, firewall,
postfix, httpd etc.).

network connectivity lost after reboot/upgrade

I upgraded one of my old machines running 5.x to the latest kernel (from
308.24.1 to 348.1.1).
After rebooting network connectivity was gone. I rebooted with the old
kernel, I also tried the one before it (308.20.1) still no luck. So I
assume it's got nothing to do with the kernel or even CentOS. But a
hardware failure seems also unlikely, see below.

ethtool shows the link as up and if I remove the cable as down.
I attached a laptop via crossover cable, it detects the link, but same
I disabled iptables and set selinux to disabled.

cannot install glibc.i686 on x86_64

I cannot install glibc.i686 on a x86_64 system because I get

Error: Missing Dependency: glibc-common = 2.5-81 is needed by package
glibc-2.5-81.i686 (base)

glibc-common.x86_64 is installed, but it's apparently looking for i686.
There's indeed no glibc-common for i686.
There's also glibc.i386 and glibc-common.i386 available, but I think I
don't need them.

I have other x86_64 systems that have an installed glibc.i686 and no
glibc.i386 and glibc-common.i386.

Latest kernel produces kernel error on Dell R200 on boot-up

I accidentally noticed this error written to the warn log on my Dell
R200's when the machines booted up after latest kernel update. Google
doesn't have this exact error, only a few with differently named devices,
but all seem to have to do with USB.

Obscure behavior with filesystem update

I've been getting weird results with the recent filesystem update. It
appears to be hanging at the transaction test stage endlessly. I can close
the ssh connection and the update still goes on. When I use screen I
cannot reattach after logout because the screen still shows as attached
and I have to use -D -RR to get back to it.
Sometimes it succeeds eventually after half an hour, sometimes not.


Folks, it has been asked a few times: PLEASE STOP THE "6 UPDATE" THREAD
Developers: please just stop responding to that thread. It's not necessary
to defend yourselves over a certain point (that has long been reached).
Non-devs: if you think you can make a valuable contribution to centos
infrastructure/development, please move over to centos-devel and make your
serious offer *kindly* there.
Any one else: JUST STOP, thanks!

I'm really tired of this.

Ralph: please unsubscribe everyone who can't shut his mouth.


I noticed that I didn't get any of the 5.6 updates rsynced yet, so I
checked my mirror and then the mirrors list. This mirror is indeed not on
the list anymore and also not on the status page. However, I see other
mirrors still on the list that are lagging for days. And I see that this
mirror has a full 5.6 directory (maybe not complete, though, but quite

Best way to extend pv partition for LVM

I've replaced disks in a hardware RAID 1 with larger disks and enlarged
the array. Now I have to find a way to tell LVM about the extra space.
It seems there are two ways:
1. delete partition with fdisk and recreate a larger one. This is
obviously a bit tricky if you do not want to lose data, I haven't
investigated further yet.
2. create another partition on the disk, pvcreate another pv and then add
it to the existing volume group with vgextend
3. a possible third way: increase the partition size.

i386 packages on fresh x86_64 system

Even a minimal install with nobase installs about 40-50 i386 packages on a
64bit-System. I know this has come up before and thought it might be an
FAQ, but I can't find it on the wiki.
Some questions are answered here:
<a href="" title=""></a>

but I have these remaining:
- can I tell via kickstart to just install the 64bit packages?
- is it safe to rpm -e remove all i386 packages? (assuming I'm not going
to install any i386 packages later)



replace x86 with x64 system and reuse existing LVM

I want to replace an existing 32bit with a 64bit installation (Centos 5).
There's an existing LVM with lots of partitions. Most are used for Xen
guests. The system itself uses only one of them plus a separate /boot
partition that is not on LVM.
What's the best course of action here? Should I do the reinstall with
kickstart or better manually and reuse the existing filesystem? As I
understand once LVM gets loaded it should find the volumes by itself, but
will it be able to use the same naming scheme for instance?

Replacing disk in RAID array with bigger disk?

I have to replace a disk in a RAID-1 array (LSI 1068 controller in an HP
DL320 G3) and I assume it shouldn't be a problem if I use a bigger one?
(going from 500 MB to 1 GB) The controller should just be able to build
the same 500 MB disk as it did before, right?
Now, if in a next step I replace the other, still smaller disk with a 1 GB
disk, too, will the controller be able to build a 1 GB disk from that?

what is device dm-2?

According to some searches and the LVM documentation on a
"dmsetup ls" should give me more info. But it doesn't list devices with
dm- numbers. Only like so:

lv-name (major, minor)

The minor numbers seem to be the same numbers that I can see as dm-
numbers in an iostat. Is this by chance the dm- number, so that minor 2
would be dm-2?