Mantis - syslog_ng
Viewing Issue Advanced Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
3869 packaging major always 2009-08-25 11:39 2009-10-11 09:24
Reporter: tim Platform:  
Assigned To: maciej OS:  
Priority: normal OS Version:  
Status: closed Product Version:  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version:  
Summary: 0003869: syslog_ng package can no longer be installed on Solaris 8 or 9
Description: I was able to install the CSWsyslogng package on Solaris 8 or 9 machines just recently. However the latest package that's on the mirrors requires svcadm to install, therefore restricting it to Solaris 10 only:


Do you want to continue with the installation of <CSWsyslogng> [y,n,?] y

Installing syslog_ng - A powerful syslogd replacement as <CSWsyslogng>

## Executing preinstall script.
Disabling svc:/system/system-log:default
/var/sadm/pkg/CSWsyslogng/install/preinstall: svcadm: not found
pkgadd: ERROR: preinstall script did not complete successfully

Installation of <CSWsyslogng> failed.
ERROR: could not add CSWsyslogng.
Steps To Reproduce:
Additional Information:
Relationships
Attached Files:
Issue History
Date Modified Username Field Change
2009-08-25 11:39 tim New Issue
2009-08-30 10:00 maciej Issue Monitored: maciej
2009-08-30 11:01 maciej Note Added: 0006649
2009-08-31 11:10 tim Issue Monitored: tim
2009-08-31 11:24 tim Note Added: 0006651
2009-08-31 13:52 maciej Note Added: 0006652
2009-08-31 16:50 tim Note Added: 0006653
2009-09-21 00:47 maciej Note Added: 0006736
2009-09-21 00:47 maciej Status new => assigned
2009-09-21 00:47 maciej Assigned To => maciej
2009-09-27 15:26 maciej Note Added: 0006761
2009-09-27 15:26 maciej Status assigned => feedback
2009-10-11 09:24 maciej Note Added: 0006826
2009-10-11 09:24 maciej Status feedback => closed
2009-10-11 09:24 maciej Resolution open => fixed

Notes
(0006649)
maciej   
2009-08-30 11:01   
To remove the broken package:

sudo rm /var/sadm/pkg/CSWsyslogng/install/postremove
sudo touch /etc/opt/csw/syslog-ng.conf.CSW
sudo pkgrm CSWsyslogng
sudo rm /etc/opt/csw/syslog-ng.conf.CSW

The updated packages are in testing.
(0006651)
tim   
2009-08-31 11:24   
I've tried the new package and unfortunately I encountered some problems, although different ones.
The first is this error:
bash-2.05# /etc/init.d/cswsyslog_ng start
syslog-ng service starting.
ld.so.1: syslog-ng: fatal: relocation error: file /opt/csw/sbin/syslog-ng: symbol g_option_context_new: referenced symbol not found
Killed

My default LD_LIBRARY_PATH is /usr/lib:/usr/server/X11/lib:/usr/openwin/lib:/usr/sfw/lib:/usr/local/lib. I got it work work by doing LD_LIBRARY_PATH='' /etc/init.d/cswsyslog_ng start but even then it still didn't work as it had started 2 syslog_ng processes:
bash-2.05# ps -ef | grep syslo
    root 1513 1 0 11:05:36 ? 0:00 /opt/csw/sbin/syslog-ng -f /etc/opt/csw/syslog-ng.conf -p /var/run/syslog-ng.pi
    root 1514 1513 0 11:05:36 ? 0:00 /opt/csw/sbin/syslog-ng -f /etc/opt/csw/syslog-ng.conf -p /var/run/syslog-ng.pi

(killing one didn't get it to work either)
(0006652)
maciej   
2009-08-31 13:52   
With your LD_LIBRARY_PATH you're on your own[1], I'm afraid. I'd suggest you do a local modification of your own to make syslog_ng run.

About the two processes, I'm seeing the them on Solaris 8 as well. My suspicion is that there's something going wrong when syslog attempts to daemonize itself. I'm thinking whether it would make sense to try syslog-ng-2.x instead of 3.x. Did 2.x version work for you on Solaris 8?

[1] http://www.opencsw.org/userguide/#using [^]
(0006653)
tim   
2009-08-31 16:50   
Yes I've already reverted to 2.x. BTW it's actually a Solaris 9 machine, sparc processor.

I'd might still be able to test packages though if you think you have a fix
(0006736)
maciej   
2009-09-21 00:47   
I believe this is fixed, the updated package has been released into current and is available from mirrors. Tim, can you check please if it's working for you?

Maciej
(0006761)
maciej   
2009-09-27 15:26   
Tim, can you check please if it's working for you?
(0006826)
maciej   
2009-10-11 09:24   
This issue has been fixed (in 3.0.4,REV=2009.08.30) and released. Closing this issue.