Skip to main content

Thoughtworks Go - dreaded 404 on artifact fetching

I've run into this more than I'd care to admit, so figured I should post it up.

Often when chaining Go pipelines I run into a message like:
19:40:33.412 [go] Could not fetch artifact Pausing 15 seconds to retry. Error was : Unsuccessful response '404' from the server

I've found there are two reasons for this message to come up.

  1. Artifact path specified incorrectly
  2. Go server purging accidentally removed the file
An example bad artifact path is visible in the example above.  If you check the pipeline details, you see: 
  • Pipeline Name: #{fetchPipeline}
  • Stage Name: ExtractCIcomponents
  • Job Name: ExtractZIP
  • Source Directory: components/WebPortal
  • Destination: components

What you SHOULD see is:
  • Pipeline Name: #{fetchPipeline}
  • Stage Name: ExtractCIcomponents
  • Job Name: ExtractZIP
  • Source Directory: components/web/WebPortal
  • Destination: components

A subtle but important difference. The source dir MUST match your build artifact location.  In this example, the build artifact looks like:
Source: components/web/WebPortal
Destination: components/web

For the latter example, it's pretty obvious wha happen.
Check here on your Go server:

If you no see files n's been purged.  But there is a way out!!

To regen the files, simply re-run the build from that original pipeline run - the files will re-appear, and any call to 'latest' for that pipeline run will be re-populated.  (although the one time this came up, the code piece built, but the tests piece did not)  It was enough to get us past the production deployment - we could then say 'hay hay hay give Go more disk!'.


Popular posts from this blog

DFSR - eventid 4312 - replication just won't work

This warning isn't documented that well on the googles, so here's some google fodder:

You are trying to set up replication for a DFS folder (no existing replication)Source server is 2008R2, 'branch office' server is 2012R2 (I'm moving all our infra to 2012R2)You have no issues getting replication configuredYou see the DFSR folders get created on the other end, but nothing stagesFinally you get EventID 4312:
The DFS Replication service failed to get folder information when walking the file system on a journal wrap or loss recovery due to repeated sharing violations encountered on a folder. The service cannot replicate the folder and files in that folder until the sharing violation is resolved.  Additional Information:  Folder: F:\Users$\\Desktop\Random Folder Name\  Replicated Folder Root: F:\Users$  File ID: {00000000-0000-0000-0000-000000000000}-v0  Replicated Folder Name: Users  Replicated Folder ID: 33F0449D-5E67-4DA1-99AC-681B5BACC7E5  Replication Group…

Fixing duplicate SPNs (service principal name)

This is a pretty handy thing to know:

SPNs are used when a specific service/daemon uses Kerberos to authenticate against AD. They map a specific service, port, and object together with this convention: class/host:port/name

If you use a computer object to auth (such as local service):

If you use a user object to auth (such as a service account, or admin account):

Why do we care about duplicate SPNs? If you have two entries trying to auth using the same Kerberos ticket (I think that's right...), they will conflict, and cause errors and service failures.

To check for duplicate SPNs:
The command "setspn.exe -X

C:\Windows\system32>setspn -X
Processing entry 7
MSSQLSvc/ is registered on these accounts:
CN=SQL Admin,OU=service accounts,OU=resources,DC=company,DC=local

found 1 groups of duplicate SPNs. (truncated/sanitized)

Note that y…

Logstash to Nagios - alerting based on Windows Event ID

This took way longer than it should have to get here's a config and brain dump...

You want to have a central place to analyze Windows Event/IIS/local application logs, alert off specific events, alert off specific situations.  You don't have the budget for a boxed solution.  You want pretty graphs.  You don't particularly care about individual server states.  (see rationale below - although you certainly have all the tools here to care, I haven't provided that configuration)

ELK stack, OMD, NXlog agent, and Rsyslog.  The premise here is as follows:

Event generated on server into EventLogNXlog ships to Logstash inputLogstash filter adds fields and tags to specified eventsLogstash output sends to a passive Nagios service via the Nagios NSCA outputThe passive service on Nagios (Check_MK c/o OMD) does its thing w. alerting
Open Monitoring Distribution, but the real point here is Check_MK (IIRC Icinga uses this...).  It makes Nagios easy to use and main…