(Migrated) Re: strange beaviour

I’ve searched my file and I found it in
./server1/work/hot-deploy/current/zimbra_queues.py
./server1/work/hot-deploy/current/zimbra-queues.py
./server2/work/hot-deploy/current/zimbra_queues.py
./server2/work/hot-deploy/current/zimbra-queues.py

zimbra_queues.py is the old ones and zimbra-queues.py is the new ones. Is
it correct to find both?

Giovanni

On Fri, Mar 28, 2014 at 12:51 AM, coeuz@coeuz.net coeuz@coeuz.net wrote:

Hi,

I observed a similar behavior once after deploying a wrong sqlalchemy
model.
I tried to deploy a fixed version of my service and its model but the
errors kept appearing even after a full restart.

At the end I found that my service was being deployed but that the
model.py file was still in the pick-up dir, so it hadn’t been deployed
after the error.

I don’t remember for sure, but think I fixed it running something like:
find -name my_service.py -or -name model.py -delete
from the root folder of the zato servers.

After that, I was able to redeploy the new version.

I hope it helps!
Carles