SVN polling problems after DNS change

[Daniel Becroft]

Hi,

Our SVN repositories are currently access via a standard name (svn://svn.domain.local/repository/trunk). We've just changed our DNS entry for 'svn.domain.local' to point to a different machine.

I've tried the 'ipconfig /flushdns' switch, and even restarting the Jenkins server (both the service and the actual machine). However, Jenkins does not seem to be picking up the DNS change.

Started on 7/12/2011 06:46:10
Location 'svn://svn.domain.local/repository/trunk' does not exist
One or more repository locations do not exist anymore for hudson.model.FreeStyleProject@41529e[moiauth-trunk], project will be disabled.
Done. Took 0.11 sec
No changes

Is Jenkins using some internal mapping that needs to be refreshed?

Cheers,
---
Daniel Becroft

[Daniel Becroft]

So more information: if I try and kick off a manual build for one of thise jobs, I get the following console log

Started by user Me
Building remotely on BUILD_SLAVE.domain.local
Location 'svn://svn.domain.local/foo/trunk' does not exist
Updating svn://svn.domain.local/foo/trunk

<snipped A/U/D paths />

At revision 14041
hudson.util.IOException2: revision check failed on svn://svn.domain.local/foo/trunk
    at hudson.scm.SubversionChangeLogBuilder.buildModule(SubversionChangeLogBuilder.java:170)
    at hudson.scm.SubversionChangeLogBuilder.run(SubversionChangeLogBuilder.java:112)
    at hudson.scm.SubversionSCM.calcChangeLog(SubversionSCM.java:562)
    at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:709)
    at hudson.model.AbstractProject.checkout(AbstractProject.java:1195)
    at hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:568)
    at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:457)
    at hudson.model.Run.run(Run.java:1404)
    at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
    at hudson.model.ResourceController.execute(ResourceController.java:88)
    at hudson.model.Executor.run(Executor.java:230)
Caused by: org.tmatesoft.svn.core.SVNException: svn: File not found: revision 14041, path '/trunk/trunk'
    at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:64)
    at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:51)
    at org.tmatesoft.svn.core.internal.io.svn.SVNReader.handleFailureStatus(SVNReader.java:269)
    at org.tmatesoft.svn.core.internal.io.svn.SVNReader.parse(SVNReader.java:248)
    at org.tmatesoft.svn.core.internal.io.svn.SVNConnection.read(SVNConnection.java:260)
    at org.tmatesoft.svn.core.internal.io.svn.SVNRepositoryImpl.read(SVNRepositoryImpl.java:1280)
    at org.tmatesoft.svn.core.internal.io.svn.SVNRepositoryImpl.logImpl(SVNRepositoryImpl.java:835)
    at org.tmatesoft.svn.core.io.SVNRepository.log(SVNRepository.java:1034)
    at org.tmatesoft.svn.core.wc.SVNLogClient.doLog(SVNLogClient.java:1027)
    at org.tmatesoft.svn.core.wc.SVNLogClient.doLog(SVNLogClient.java:894)
    at org.tmatesoft.svn.core.wc.SVNLogClient.doLog(SVNLogClient.java:826)
    at hudson.scm.SubversionChangeLogBuilder.buildModule(SubversionChangeLogBuilder.java:158)
    ... 10 more
Caused by: org.tmatesoft.svn.core.SVNErrorMessage: svn: File not found: revision 14041, path '/trunk/trunk'
    at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:200)
    at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:146)
    at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:89)
    at org.tmatesoft.svn.core.internal.io.svn.SVNReader.getErrorMessage(SVNReader.java:283)
    at org.tmatesoft.svn.core.internal.io.svn.SVNReader.handleFailureStatus(SVNReader.java:261)
    ... 19 more
Archiving artifacts
Recording fingerprints
Email was triggered for: Failure
Sending email for trigger: Failure
Sending email to: m...@domain.com.au
Finished: FAILURE

Some of the commands will work, but some won't. Very strange.

Cheers,
Daniel B.

[Daniel Becroft]

This appears to be a general problem with connecting to 1.7 repositories.
---
Daniel Becroft

[Maureen Barger]

Hi - your jvm is caching DNS. Restart Jenkins.

You can alter your jvm at the same time to cache for shorter time (right now it is probably at default of forever).

http://www.rgagnon.com/javadetails/java-0445.html

HTH.

[Daniel Becroft]

On Wed, Dec 7, 2011 at 11:48 AM, Maureen Barger <moba...@gmail.com> wrote:

Hi - your jvm is caching DNS. Restart Jenkins.

You can alter your jvm at the same time to cache for shorter time (right now it is probably at default of forever).

http://www.rgagnon.com/javadetails/java-0445.html

HTH.

Thanks, Maureen. But I've already tried that - both restarting the Jenkins service *and* restarting the entire machine. No go. I think it's not the DNS entry, though, but more a problem with Jenkins accessing 1.7.x repositories (the original versions were 1.6.x).

Cheers,
Daniel B.