Gerrit Trigger strange behavior

[李大明]

I have a Jenkins server which runs build verification by Gerrit Trigger plugin.

This worked fine for months. But after last time I restart my Jenkins, strange behavior happens:

Each Gerrit uploaded patchset will trigger two build. One is correct, but the other use the build ID. Like:

Jenkins

Patch Set 1: Build Started http://server/job/linux_verify/291/

Patch Set 1: Build Started http://server/job/linux_verify/166/

In Jenkins WebUI I only see build 291 running but I got error like 

Fatal: Unable to create '/home/jenkins/jenkins_slave/workspace/linux_verify/kernel/linux/linux-3.10.0/.git/index.lock': File exists.

This means I have two git processes accessing the same repository.

I try to restart Jenkins server and slave node, also try to  reconnect GerritTrigger servers.

None of this work.

Anyone have idea?

[李大明]

It's a dumb mistake. 

We tested our Jenkins backup mechanism but forgot shutting it down. 

Sorry for asking such a stupid question.

李大明於 2015年2月26日星期四 UTC+8下午5時51分17秒寫道：