Discuss May 2008

discuss@lists.centos.org

268 participants
281 discussions

saslauthd for sendmail SMTP relay
by Bernd Bartmann 25 May '08

25 May '08

Hi, I'm running a Centos 5.1 server that uses saslauthd to allow sendmail SMTP relaying for some clients. saslauthd is configured to use method "shadow" to lookup the username / password directly from /etc/shadow. This setup has been working for several month now, but is broken since last Monday. I haven't changed anything neither on the server nor on the clients. Now whenever a client tries to relay email I see this messages in the logs: /var/log/maillog: AUTH failure (LOGIN): authentication failure (-13) SASL(-13): authentication failure: checkpass failed /var/log/messages: saslauthd[3665]: do_auth : auth failure: [user=username] [service=smtp] [realm=] [mech=shadow] [reason=Unknown] Does someone have an idea how to debug this further, esp. how to find the real reason as the message [reason=Unknown] is not very helpful at all. Thanks in advance, Bernd.

2 5

RE: [CentOS] Hourly restart
by Gregg McClintic 25 May '08

25 May '08

Anything in the bios called watchdog turned on?

2 1

Hourly restart
by Linux 25 May '08

25 May '08

Hi, Without any update, hardware/software modification, etc... one of my systems "Hourly restart" problem started again. Currently, I counted 5 restarts at 59th minute. No log entry, no console error, nothing really interesting. If I do not see camera records with my own eyes, I'll suspect about someone from D.C. hardreseting the box. Now, I guess /var failed mounting and ssh not available. Maybe next hour restart does a magic... Last time, a kernel update solved hourly restart problem. Before loosing access, I checked and saw a new kernel with -21 ending number (x86_64, forgot to mention) and waiting for XFS module to be ready (Well, I wish I had left it ext3) After that, perhaps update will solve the problem again, but why? Last time I stopped all crons, unneeded services, remote access, etc.. Put a man in front of the monitor and made him monitor everything. Only thing he saw was a welcoming BIOS without any sign at the 60th minute. Replaced power cords, power supply, some disks, RAM modules, etc... Currently I have the last recovered remote logs of temperature and voltage sensors of the system, all seems fine, nothing suspicious. I am out of ideas. I have many gentoo boxes on the almost same hardware and a few centos boxes. Only this one failes continuously... I'd like to hear advice and suggestions about how to debug / repair this situation. Thanks. P.S.: Complete hardware replacement plan is currently in action, new hardware will be ready soon but I'm not so sure about hardware failure. Why did it stopped last time after a simple kernel update?

1 0

How is this possible?
by MHR 25 May '08

25 May '08

As an experiment, I am attempting to build a more recent version of GNOME than 2.16.0 on CentOS 5.1. I've tried both garnome and jhbuild, and neither one works quite right. Jhbuild blows out looking for a dbus-glib-1 revision >= 0/74 (the release rev is 0.70), so I downloaded that and tried to build it. This results in the following error: gcc -g -O2 -Wall -Wchar-subscripts -Wmissing-declarations -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wcast-align -Wfloat-equal -Wsign-compare -o .libs/dbus-binding-tool dbus-binding-tool-glib.o dbus-glib-tool.o ./.libs/libdbus-gtool.a -L/lib64 ./.libs/libdbus-glib-1.so -ldbus-1 -lgobject-2.0 -lglib-2.0 /usr/lib/libexpat.so -lnsl /usr/lib/libexpat.so: could not read symbols: File in wrong format collect2: ld returned 1 exit status make[4]: *** [dbus-binding-tool] Error 1 make[4]: Leaving directory `/home/mhr/Download/dbus-glib-0.74/dbus' make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory `/home/mhr/Download/dbus-glib-0.74/dbus' make[2]: *** [all] Error 2 make[2]: Leaving directory `/home/mhr/Download/dbus-glib-0.74/dbus' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/mhr/Download/dbus-glib-0.74' make: *** [all] Error 2 When I try to use garnome, it eventually runs into exactly the same error. I've checked /usr/lib/libexpat.so, and this is what I get: $ ls -l /usr/lib/libexpat.so lrwxrwxrwx 1 root root 27 Jan 8 13:11 /usr/lib/libexpat.so -> ../../lib/libexpat.so.0.5.0 $ ls -l /lib/libexpat.so.0.5.0 -rwxr-xr-x 1 root root 133056 Jan 6 2007 /lib/libexpat.so.0.5.0 $ file /lib/libexpat.so.0.5.0 /lib/libexpat.so.0.5.0: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), stripped When I look at this library with nm, lld and objdump, they all seem to be able to read it just fine. There is also the 64 bit version that lives in /ib64 and has a .ink from /usr/lib64, and that also reads fine. What did I miss here? Thanks. mhr

4 6

USBDisk question
by Todd Cary 25 May '08

25 May '08

I have an external USB drive, and when mounted, it was /media/usbdisk. When I recently tried my rsync backup, a usbdisk1 had been created...I guess by the auto-mounting (when the disk is turned on). Is there a way to remove the usbdisk1 and set it up so that the auto-mounting will use usbdisk? Or should I just leave it be? I needed to change my command line for the rsync backup to usbdisk1. Many thanks... Todd -- Ariste Software Petaluma, CA 94952 http://www.toddcary.com/aristephotography/

2 1

resizing partition
by Al Sparks 25 May '08

25 May '08

I'm going to have to resize a partition (shrink it) to make room for more swap space. This is actually not too big of a deal, since we're not talking about a "system" partition (/, /var, /usr, etc), but one where an application resides. So I won't even have to go to "rescue" mode to do this. I can umount this thing live. (and since I'm working on it remotely, that's important). But this system was not configured with LVM. So it occurs to me, that in dealing with a non-LVM partition(s), if the swap space I want to enlarge isn't next to the partition I shrink, my options would be to: 1. Manually "move" the other partitions, probably very risky 2. Simply make a second swap space that's next to the partition I shrink. Have I got the right idea? === Al

2 1

small annoying problem with Ati video driver
by Juan C. Valido 24 May '08

24 May '08

I have a small annoying problem with Ati video driver, when Centos 5.1 starts and gets to the login screen the resolution is too high for my monitor (better than out of range) and it's annoying can I have it start in a lower resolution. Thanks...

2 2

samba question
by david chong 24 May '08

24 May '08

Hi, I am running Centos5.1, trying to configure samba now. I am quite new in this area and hope help from the list. I could not connect to it from a windows xp pc >From the console, I log in and do a >smbclient -L localhost -U% Domain=[MYGROUP] OS=[Unix] Server=[Samba 3.0.25b-0.el5.4] Sharename Type Comment --------- ---- ------- samba Disk IPC$ IPC IPC Service (Samba 3.0.25b-0.el5.4) Domain=[MYGROUP] OS=[Unix] Server=[Samba 3.0.25b-0.el5.4] Server Comment --------- ------- ANTIOCH Samba 3.0.25b-0.el5.4 Workgroup Master --------- ------- MYGROUP ANTIOCH Could you pls help. Thanks David

8 15

CentOS-announce Digest, Vol 39, Issue 12
by centos-announce-request＠centos.org 24 May '08

24 May '08

Send CentOS-announce mailing list submissions to centos-announce(a)centos.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request(a)centos.org You can reach the person managing the list at centos-announce-owner(a)centos.org When replying, please edit your Subject line so it is more specific than "Re: Contents of CentOS-announce digest..." Today's Topics: 1. CESA-2008:0287 Important CentOS 3 ia64 libxslt - security update (Pasi Pirhonen) 2. CESA-2008:0287 Important CentOS 4 ia64 libxslt - security update (Pasi Pirhonen) 3. CESA-2008:0492 Important CentOS 4 ia64 gnutls - security update (Pasi Pirhonen) 4. CESA-2008:0287 Important CentOS 3 s390(x) libxslt - security update (Pasi Pirhonen) 5. CESA-2008:0492 Important CentOS 4 s390(x) gnutls - security update (Pasi Pirhonen) 6. CESA-2008:0287 Important CentOS 4 s390(x) libxslt - security update (Pasi Pirhonen) ---------------------------------------------------------------------- Message: 1 Date: Fri, 23 May 2008 19:19:15 +0300 From: Pasi Pirhonen <upi(a)centos.fi> Subject: [CentOS-announce] CESA-2008:0287 Important CentOS 3 ia64 libxslt - security update To: centos-announce(a)centos.org Message-ID: <20080523161914.GN2456(a)centos.fi> Content-Type: text/plain; charset="us-ascii" CentOS Errata and Security Advisory 2008:0287 https://rhn.redhat.com/errata/RHSA-2008-0287.html The following updated files have been uploaded and are currently syncing to the mirrors: ia64: updates/ia64/RPMS/libxslt-1.0.33-6.ia64.rpm updates/ia64/RPMS/libxslt-devel-1.0.33-6.ia64.rpm updates/ia64/RPMS/libxslt-python-1.0.33-6.ia64.rpm -- Pasi Pirhonen - upi(a)iki.fi - http://pasi.pirhonen.eu/ Top-postings silently ignored

1 0

read only root file system
by Fred Noz 24 May '08

24 May '08

Responding to a question posted earlier this month, Centos 5.1 includes configuration files for enabling the read-only root filesystem. Actually, all filesystems can be mounted read-only with particular files and directories mounted on a read-write tmpfs (in RAM). This capability comes directly from the upstream provider. You can have your Centos system running read-only root in two easy steps: 1. Edit /etc/sysconfig/readonly-root and change READONLY=no to READONLY=yes 2. Reboot When your computer comes back up, the root and any other system partitions will be mounted read-only. All the files and directories listed in /etc/rwtab will be mounted read-write on a tmpfs filesystem. You can add additional files and directories to rwtab to make them writable after reboot. Note that this system is stateless. When you reboot again, everything written to the tmpfs filesystem vanishes and the system will be exactly as it was the last time it was booted. You could add a writable filesystem on disk or NFS for writing files you want to retain after rebooting. Take a look at /etc/rc.d/rc.sysinit to see how the magic is done. This capability is a "technology preview" (beta) and is buggy. Note that /etc/mtab and thus "mount" do not show the complete list of filesystems because the /etc directory is on a read-only filesystem. /proc/mounts always shows the correct mount information. You could update /etc/mtab from /proc/mounts to correct it both after boot and after running the mount or umount commands to change mounts. Run "fgrep -v rootfs /proc/mounts >/etc/mtab" to correct /etc/mtab. Note that mounting or symlinking /proc/mounts to /etc/mtab causes other problems such as breaking the df command. You can change your read-only root filesystem to read-write mode immediately with this command run by the root user: mount -n -o remount,rw / - Fred

2 1

← Newer
1
...
6
7
8
9
10
11
12
...
29
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss May 2008