bugzilla-daemon at main.slony.info bugzilla-daemon at main.slony.info
Mon May 28 23:11:38 PDT 2012
http://www.slony.info/bugzilla/show_bug.cgi?id=267

           Summary: 2.1.1 RPM Problem.
           Product: Slony-I
           Version: devel
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: low
         Component: rpm
        AssignedTo: slony1-bugs at lists.slony.info
        ReportedBy: nakamura_kenichi_d7 at lab.ntt.co.jp
                CC: devrim at gunduz.org
   Estimated Hours: 0.0


hi,

I found two problems about the RPM of Slony-I.
Please fix the problem.


(1)Get an error while installing.
--
# rpm -ivh slony1-91-II-2.1.1-1.rhel6.x86_64.rpm
warning: slony1-91-II-2.1.1-1.rhel6.x86_64.rpm: Header V4 DSA/SHA1 Signature,
key ID 442df0f8: NOKEY
Preparing...                ########################################### [100%]
   1:slony1-91-II           ########################################### [100%]
error reading information on service slony1-II-91: No such file or directory
--

"slony1-91-II" is the startup script that is created during the slony-I
installation, 
but "slony1-II-91" is described for the argument of "checkconfig".

I think there is a need to modify the SPEC file.
--
NG  : chkconfig --add slony1-II-91
OK  : chkconfig --add slony1-91-II
--

I got the RPM from the site below.
http://yum.postgresql.org/9.1/redhat/rhel-6.1-x86_64/slony1-91-II-2.1.1-1.rhel6.x86_64.rpm

and I found same problem in several RPMs.



(2)Can not start with "/etc/init.d/slony1-91-II start".

The value of the variable that is described in the "/ etc/init.d/slony1-91-II"
is incorrect.

I fixed the three place , I can start Slony-I.


Original
---
> SLONENGINE=/usr/bin
> SLONCONF=/etc/slon.conf
> SLONLOG=/var/log/slony

Fix
---
> SLONENGINE=/usr/pgsql-9.1/bin
> SLONCONF=/etc/slony1-91-II/slon.conf
> SLONLOG=/var/log/slony.log


regards,

-- 
Configure bugmail: http://www.slony.info/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.


More information about the Slony1-bugs mailing list