1

Quite recently (like since yesterday), I have noticed that my team's pushes are no longer showing up in the kiln web UI push view. The changesets are still in the repo, and can be fetched, but they don't show on the web.

Recent pushes have been showing this message:

remote: kiln: successfully pushed one changeset
remote: Exception RuntimeError: 'maximum recursion depth exceeded while calling a Python object' in <class 'socket.error'> ignored
remote: error: changegroup hook raised an exception: [Errno 10054] An existing connection was forcibly closed by the remote host

How would I go about fixing this?

flag

1 Answer

2

So, that happens when the queueing system crashes within the Kiln Storage Service. As a quick fix, restart the Kiln Storage Service. It'd also be really useful to us if you could contact us directly through customer support and send us your C:\KilnRepositories\errors.txt file.

link|flag
will do! Is there a webui way to bounce the storage service? – Jeff Paulsen Oct 14 2010 at 21:11
There's no way to bounce, because it really shouldn't happen to begin with. The missing changesets will be filled in on your next push automatically, though. – Benjamin Pollack Oct 14 2010 at 21:19

Your Answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.