0
votes

This is an odd problem;

  • I have TeamCity on Ubuntu 12.04 Virtual Machine; Network is Bridged.
  • I have an Agent on my Windows 7 Machine running as my domain account.
  • I have an Agent on a Windows 8.1 Virtual Machine, running under a domain account.
  • Its all running on domain with a proxy (automatically picks up domain user).

When I run a build via my windows 7 agent, it all works fine.

When I run a build via the Windows 8.1 Virtual Machine. Nuget Complains it isn't able to access the TeamCity feed. Now the odd thing is I know the domain login and proxy is okay because NuGet is able to access the main online nuget feed!

Apart from the Windows version, there is effectively no difference between the agents; just the VM agent can't access the TeamCity Feed (running as separate VM).

If I remote into the VM build agent and access the feed url, it works fine (no packages listed, but I thought this was normal).

I even tried formatting the VM and not messing with NuGet config; no luck.

So, I'm really stuck now. Any help welcome. I'm sure its something to do with proxy settings and Active Domain on Windows Server 2013, but that is all working as far as I can see.

Here is the log:

[09:57:06][Step 1/4] restore: Restoring NuGet packages for Data.sln (3s)
[09:57:06]NuGet command: C:\BuildAgent\plugins\nuget-agent\bin\JetBrains.TeamCity.NuGetRunner.exe C:\BuildAgent\tools\NuGet.CommandLine.DEFAULT.nupkg\tools\NuGet.exe restore C:\BuildAgent\work\8eb62dff1e11de78\Data.sln -Source http://anwyn/guestAuth/app/nuget/v1/FeedService.svc/ -Source https://www.nuget.org/api/v2/
[09:57:06]Starting: C:\BuildAgent\temp\agentTmp\custom_script2003394465901551489.cmd
[09:57:06]in directory: C:\BuildAgent\work\8eb62dff1e11de78
[09:57:06]JetBrains TeamCity NuGet Runner 8.0.30168.9
[09:57:06]Registered additional extensions from paths: C:\BuildAgent\plugins\nuget-agent\bin\plugins-2.8
[09:57:06]Starting NuGet.exe 2.8.50506.491 from C:\BuildAgent\tools\NuGet.CommandLine.DEFAULT.nupkg\tools\NuGet.exe
[09:57:07]Installing 'AutoMapper 3.2.1'.
[09:57:07]Successfully installed 'AutoMapper 3.2.1'.
[09:57:07]Installing 'protobuf-net 2.0.0.668'.
[09:57:08]Successfully installed 'protobuf-net 2.0.0.668'.
[09:57:08]WARNING: The remote server returned an error: (503) Server Unavailable.
[09:57:08]WARNING: The remote server returned an error: (503) Server Unavailable.
[09:57:09]Installing 'NUnit 2.6.3'.
[09:57:09]Successfully installed 'NUnit 2.6.3'.
[09:57:09]Installing 'RhinoMocks 3.6.1'.
[09:57:09]Successfully installed 'RhinoMocks 3.6.1'.
[09:57:10]Unable to find version '0.1.3' of package 'RobGeoLtd.Core'.
[09:57:10]Unable to find version '0.1.22' of package 'RobGeoLtd.Measurement'.
[09:57:10]Process exited with code 1
[09:57:10][Step 1/4] Step Restore (NuGet Installer) failed

Update #1: Logged in as Domain account via Console:

Console

Going to ask our IT support to check the proxy/firewall to see what its doing... :/

Update #2: He was at a loss too; the Log:

[04/Sep/2014:11:57:46 +0100] "GET
http://anwyn/guestAuth/app/nuget/v1/FeedService.svc HTTP/1.0" 407 2167
TCP_DENIED:NONE 192.168.1.11 - local\devserver 

[04/Sep/2014:11:57:46 +0100] "GET
http://anwyn/guestAuth/app/nuget/v1/FeedService.svc HTTP/1.0" 503 2668
TCP_MISS:DEFAULT_PARENT

However, accessing the feed via IP rather than DNS name worked!

2

2 Answers

0
votes

I'm not expert in linux administration so i have no clue how (and if its posibile) to set-up linux server into active directory domain. Can you please describe how did you configure Authentication section in your teamcity ? (login as administrator then under settings in Server Administrator => Authentication)

Can you access your teamcity feed via browser from this agents? Feed URI should be http://SERVERNAME:PORT/httpAuth/app/nuget/v1/FeedService.svc or if you're using public url (no authentication) http://SERVERNAME:PORT/guestAuth/app/nuget/v1/FeedService.svc ?

0
votes

I had our virtual machine (Agent) set up to have a bridged network connection. Prior to our server upgrade, this worked fine. After the upgrade, I had the above problem. I tried setting the VM connection to be NAT and that inexplicably fixed everything. Still think there is more going on here with the Proxy (I think its a Symantec Web Gateway proxy), AD and DNS alias as domain name.