Bug#572971: upgrade fails if mongodb not currently started

2010-03-30 Thread Michal Politowski
On Mon, 15 Mar 2010 14:18:48 +0100, Antonin Kral wrote: Hi Michal, could you please check the file /etc/init.d/mongodb ? I am suspicious that it will be symlink: mongodb - /lib/init/upstart-job This is caused by the incorrect implementation of upstart / upgrade path from the upstart

Bug#572971: upgrade fails if mongodb not currently started

2010-03-15 Thread Antonin Kral
Hi Michal, could you please check the file /etc/init.d/mongodb ? I am suspicious that it will be symlink: mongodb - /lib/init/upstart-job This is caused by the incorrect implementation of upstart / upgrade path from the upstart script. Please remove the file and reinstall the package. It

Bug#572971: upgrade fails if mongodb not currently started

2010-03-12 Thread Michal Politowski
On Mon, 8 Mar 2010 08:11:34 +0100, Antonin Kral wrote: Hello Michal, to be honest I am not able to replicate your problem. I am a bit confused with the message: stop: Unknown instance: I have just went through multiple upgrade scenarios (like stopped daemon, killed...) and all of

Bug#572971: upgrade fails if mongodb not currently started

2010-03-07 Thread Michal Politowski
Package: mongodb Version: 1:1.2.2-1 Severity: normal Preparing to replace mongodb 1:1.2.2-1 (using .../mongodb_1.2.2-2_i386.deb) ... arg: upgrade Stopping mongodb... stop: Unknown instance: invoke-rc.d: initscript mongodb, action stop failed. dpkg: warning: old pre-removal script returned error

Bug#572971: upgrade fails if mongodb not currently started

2010-03-07 Thread Antonin Kral
Hello Michal, to be honest I am not able to replicate your problem. I am a bit confused with the message: stop: Unknown instance: I have just went through multiple upgrade scenarios (like stopped daemon, killed...) and all of them were pretty successful. One thing came on mi mind through -