http-replicator does not start anymore *SOLVED*

Message

Lomaxx · Post by **Lomaxx** » Wed Aug 12, 2009 8:36 am

Since ~2 weeks or so http-replicator is not starting anymore. Unfortunately i do not find any information what might be causing this. I didn't change anything. My guess is that it broke with some world-update.

Code: Select all

/etc/init.d/http-replicator start
 * Starting Http-Replicator ...
 * Failed to start Http-Replicator                                        [ !! ]

/var/log/messages shows nothing but "Aug 12 10:30:23 serum rc-scripts: Failed to start Http-Replicator".
/var/log/http-replicator show nothing but "12 Aug 2009 10:30:21 INFO: HttpReplicator started".

Reemerging does not solve it. Any idea what might be causing this or where else i might find information?

Thanks in advance.

Junkyboy · Post by **Junkyboy** » Thu Aug 13, 2009 2:28 pm

Yeah, this happened to me too after python 2.6 was marked stable. The app runs fine but it seems its returning 1 when launched which causes the init script to think it has failed. So I just run it manually for now..

Lomaxx · Post by **Lomaxx** » Thu Aug 13, 2009 2:37 pm

I noticed too that it starts when i run it manually. However i didn't manage to connect from my other machine then ("connection rejected"). But maybe i didn't collect the right parameters from /etc/conf.d/http-replicator when running it. I didn't try for long. Perhaps i will again later.

Thanks for the answer.

billk · Post by **billk** » Sat Aug 29, 2009 5:38 am

Edit /etc/init.d/http-replicator and add "--oknodo" to the start stanza

start-stop-daemon --help

BillK

Lomaxx · Post by **Lomaxx** » Sat Aug 29, 2009 10:02 am

That seems to work nicely - at least for a workaround.
Thanks.

Trainwreck · Post by **Trainwreck** » Sat Aug 29, 2009 11:03 am

billk wrote:Edit /etc/init.d/http-replicator and add "--oknodo" to the start stanza

start-stop-daemon --help

BillK

-o works for me as well. Thanks!

dahoste · Post by **dahoste** » Sun Sep 13, 2009 3:28 pm

Do we have any idea what changed that caused this?

After browsing through both the http-replicator source file itself, and the start-stop-daemon man page, I don't see any reason why start-stop-daemon wouldn't be satisified that http-replicator starts successfully, i.e. why it would think no actions were taken and therefore needs --oknodo to keep the init.d script happy.

I don't even see how the python2.6 upgrade would have any effect here. http-replicator starts just fine. Unless there's some kind of quirky change in how os.fork() or signal.signal() behave. Or a race condition got exposed that makes start-stop-daemon fail to see something it expects to see which would indicate an action was taken to start the process.

Hard to tell without looking at the start-stop-daemon source itself (which I haven't done).

Quincy · Post by **Quincy** » Sat Sep 26, 2009 6:58 pm

Same problem here and i dont really understand why this happens. the workaround for the init script helps to continue working, but isn't a real solution.

Perhaps it waits for some return value from http-replicator (i have no idea about python, so please dont blame me if this doesn't apply to the http-replicator <-> startstopdaemon interaction)

Condex · Post by **Condex** » Mon Oct 12, 2009 9:58 am

Thanks for the tip, I was facing the same problem here...

Junkyboy wrote:Yeah, this happened to me too after python 2.6 was marked stable. The app runs fine but it seems its returning 1 when launched which causes the init script to think it has failed. So I just run it manually for now..

I'm still runing Python 2.5 and it fails as well.

http-replicator does not start anymore SOLVED

http-replicator does not start anymore SOLVED