Upgrade 9.5.1 to 9.5.2 failed due to syslog reload

[turbomettwurst]

Hello Folks,
i have a problem upgrading a box to 9.5.2 on CentOS 5.5
The OS itself is fully up2date which is the problem i assume, a few weeks back centos switched the syslogger from sysklogd to syslog-ng, i assume that is where the installer fails...

Any Ideas or Workaround would be greatly appreciated.

Parallels Products Installer 3.6.0 (built on 2010-04-13 11:20 svn rev. 290858) started at (timezone CET) Thu Jun 24 15:08:03 2010
Command line arguments: /usr/local/psa/admin/bin/autoinstaller --enable-xml-output --source-type=plesk --target=/root/psa --select-release-id=PLESK_9_5_2 [email protected] --install-component=base --install-component=api --install-component=backup-ded --install-component=pmm-ded --install-component=psa-firewall --install-component=watchdog --install-component=spamassassin --install-component=ppwse --install-component=mailman --install-component=drweb --install-component=de-DE-locale --install-component=horde --install-component=php --install-component=qmail

Try to find rcfile...
Autoinstaller rcfile not found.
Checking hostname is sucessfull.
Opsys detected as: os_vendor=CentOS os_name=Linux version=5.5 arch=x86_64 environment=~empty
Final opsys (with overriding) is: os_vendor=CentOS os_name=Linux version=5.5 arch=x86_64 environment=~empty
File downloading products.inf3: 100% was finished.
<snip>
KeyUpdateChecker::doCheck: no components for check key update
repository: Get full packages info for all sources
Retrieving information about the installed packages...
read cache file
File downloading PSA_9.5.2/dist-rpm-CentOS-5-x86_64/build-9.5.2-cos5-x86_64.hdr.gz: 10%..20%..30%..40%..50%..60%..70%..80%..90%..100% was finished.
<snip>
Starting installation of packages
Warning: unresolved requires '/usr/bin/lp' from redhat-lsb-3.1-12.3.EL.el5.centos.x86_64
Warning: unresolved requires '/usr/bin/lpr' from redhat-lsb-3.1-12.3.EL.el5.centos.x86_64
Warning: unresolved requires '/usr/bin/lp' from redhat-lsb-3.1-12.3.EL.el5.centos.i386
Warning: unresolved requires '/usr/bin/lpr' from redhat-lsb-3.1-12.3.EL.el5.centos.i386
Warning: unresolved requires 'psa-locale-base = 9.5.1' from psa-9.5.1-cos5.build95100414.15.x86_64
Warning: unresolved requires 'plesk-skins-9.5.1' from psa-9.5.1-cos5.build95100414.15.x86_64
Installing the package psa-php5-configurator-1.5.3-cos5.build95100504.10.noarch
===> configuring php5 using /etc/php.ini file
Trying to set memory limit to 32M... done
Trying to add '.' to 'include_path'... nothing to be done
done
Trying to set 'short_open_tag' to On... done
Trying to set 'file_uploads' to On... done
Trying to set 'safe_mode' to On... done
Installing the package PPWSE-1.1-cos5.build95100504.10.x86_64
[Thu Jun 24 15:11:05 2010] [warn] module ssl_module is already loaded, skipping

Installing the package psa-migration-agents-9.5.2-cos5.build95100504.10.x86_64
Installing the package courier-imap-3.0.8-cos5.build95100504.10.x86_64
Stopping Courier-IMAP server:
Stopping imap [ OK ]
Stopping imap-ssl [ OK ]
Stopping pop3 [ OK ]
Stopping pop3-ssl [ OK ]

Trying to register service xinetd... using /sbin/chkconfig
done
Trying to executing mail_restore to synchronize mail server settings and Plesk Database... done
Installing the package psa-qmail-1:1.03-cos5.build95100504.10.x86_64
Checking for the system groups and users necessary for Qmail...
Checking for the group 'qmail'...
Group 'qmail' already exists

Checking for the group 'nofiles'...
Group 'nofiles' already exists

Checking for the user 'alias'...
User 'alias' already exists
Changing shell for alias.
Shell not changed.

Checking for the user 'qmaild'...
User 'qmaild' already exists
Changing shell for qmaild.
Shell not changed.

Checking for the user 'qmaill'...
User 'qmaill' already exists
Changing shell for qmaill.
Shell not changed.

Checking for the user 'qmailp'...
User 'qmailp' already exists
Changing shell for qmailp.
Shell not changed.

Checking for the user 'qmailq'...
User 'qmailq' already exists
Changing shell for qmailq.
Shell not changed.

Checking for the user 'qmailr'...
User 'qmailr' already exists
Changing shell for qmailr.
Shell not changed.

Checking for the user 'qmails'...
User 'qmails' already exists
Changing shell for qmails.
Shell not changed.

Trying to stop service qmail... qmail-send (pid 32542) is running...
Stopping : done

Trying to reload service syslog...
ERROR while trying to Unable to handle syslog
Check the error reason(see log file: /tmp/psa-qmail_1.03_cos5.build95100504.10_upgrade.100624.15.18.log), fix and try again

Aborting...

error: %post(psa-qmail-1.03-cos5.build95100504.10.x86_64) scriptlet failed, exit status 1
Error: An error occurred during installation of packages.
Attention! Your software might be inoperable.
Please, contact product technical support.

The mentioned logfile /tmp/psa-qmail_1.03_cos5.build95100504.10_upgrade.100624.15.18.log
isn't all that helpful:

START psa-qmail-1.03-cos5.build95100504.10 upgrading AT Thu Jun 24 15:18:27 CEST 2010
Checking for the system groups and users necessary for Qmail...
Checking for the group 'qmail'...
Group 'qmail' already exists

Checking for the group 'nofiles'...
Group 'nofiles' already exists

Checking for the user 'alias'...
User 'alias' already exists

Checking for the user 'qmaild'...
User 'qmaild' already exists

Checking for the user 'qmaill'...
User 'qmaill' already exists

Checking for the user 'qmailp'...
User 'qmailp' already exists

Checking for the user 'qmailq'...
User 'qmailq' already exists

Checking for the user 'qmailr'...
User 'qmailr' already exists

Checking for the user 'qmails'...
User 'qmails' already exists

Trying to stop service qmail... done
STOP psa-qmail-1.03-cos5.build95100504.10 upgrading AT Thu Jun 24 15:18:32 CEST 2010
START psa-qmail-1.03-cos5.build95100504.10 upgrading AT Thu Jun 24 15:18:36 CEST 2010

Trying to set... Trying to set... Trying to reload service syslog...
ERROR while trying to Unable to handle syslog

Aborting...

STOP psa-qmail-1.03-cos5.build95100504.10 upgrading AT Thu Jun 24 15:18:37 CEST 2010

 

[IgorG]

Thank you. I have forwarded it to developers for the further investigation. Will keep you updated in this thread.

 

[IgorG]

Try this workaround.

 

[thewolf]

The OS itself is fully up2date which is the problem i assume, a few weeks back centos switched the syslogger from sysklogd to syslog-ng, i assume that is where the installer fails...

Which version of CentOS switched from sysklogd to syslog-ng?
I cannot find any information on this on the web, can you point me in the right direction?

Thanks.

 

[turbomettwurst]

Which version of CentOS switched from sysklogd to syslog-ng?
I cannot find any information on this on the web, can you point me in the right direction?

Thanks.

Well i have boxes running CentOS release 5.5 (Final) one x86, one amd64 both running on stock repos+ epel and both of them were forcefully switched to syslog-ng a few weeks ago by yum-update. Didn't bother to check for why's since it worked without a hitch on both machines

 

[thewolf]

We have a stock CentOS 5.5 installation and there is no sign of the syslog-ng package.

Can you run this command to see where your syslog-ng package came from?
rpm -qi syslog-ng

Thanks.

 

[turbomettwurst]

server:~$ rpm -qi syslog-ng
Name : syslog-ng Relocations: (not relocatable)
Version : 2.1.4 Vendor: openSUSE Build Service
Release : 5.1 Build Date: Fri 04 Jun 2010 12:40:28 PM CEST
Install Date: Fri 04 Jun 2010 10:09:14 PM CEST Build Host: muc-build02
Group : System Environment/Daemons Source RPM: syslog-ng-2.1.4-5.1.src.rpm
Size : 565353 License: GPLv2+
Signature : DSA/SHA1, Fri 04 Jun 2010 12:38:53 PM CEST, Key ID 54ddd66a66215b7b
URL : http://www.balabit.com/products/syslog_ng/
Summary : Next-generation syslog server
Description :
syslog-ng, as the name shows, is a syslogd replacement, but with new
functionality for the new generation. The original syslogd allows
messages only to be sorted based on priority/facility pairs; syslog-ng
adds the possibility to filter based on message contents using regular
expressions. The new configuration scheme is intuitive and powerful.
Forwarding logs over TCP and remembering all forwarding hops makes it
ideal for firewalled environments.

strange.. i'm about to get worried...