| Sven Willenberger 2005-07-27, 11:38 am |
| On Tue, 2005-07-26 at 16:29 -0400, Sven Willenberger wrote:
> On Tue, 2005-07-26 at 16:21 -0400, Vivek Khera wrote:
>
> I will take a look at using deamontools then. I had seen the thread to
> which you refer and that prompted my question (but I didn't want to
> hijack the thread).
>
> Thanks
The setup script worked fine and the service is running. I do have a
concern now though. It would appear from the logfiles that slon is
getting restarted every 12 minutes on the origin. Subsequently, the
replicant does the same an spits out warnings:
Jul 27 11:40:27 dbhost slon[48276]: [43-22] CONFIG storeListen:
li_origin=1 li_receiver=3 li_provider=1
Jul 27 11:40:27 dbhost slon[48276]: [43-23] CONFIG storeSet: set_id=1
set_origin=1 set_comment='custome
r tables'
Jul 27 11:40:27 dbhost slon[48276]: [43-24] WARN remoteWorker_wakeup:
node 1 - no worker thread
Jul 27 11:40:27 dbhost slon[48276]: [43-25] CONFIG storeSet: set_id=4
set_origin=1 set_comment='Temp set to integrate'
Jul 27 11:40:27 dbhost slon[48276]: [43-26] WARN remoteWorker_wakeup:
node 1 - no worker thread
Is this normal? or is svscan somehow under the impression that slon
stopped running?
Sven
|