Build cache error - Could not store entry - 404: Not Found


(Jonathan Ackerman) #1

Hi there

I’m trying to set up a build cache node. The node appears to start up fine but when my build tries to cache something it fails with:

Could not store entry e7e26be0cea9a15ad6ef501cdf43431e for task ':compileJava' in remote build cache: Storing entry at 'http://localhost/e7e26be0cea9a15ad6ef501cdf43431e' response status 404: Not Found

Loooking at the nodes logs (node.log). I can see the following:

2018-04-23 00:43:35,199 INFO r.s.RatpackServer {} Server stopped. 
2018-04-23 00:43:35,969 INFO r.s.RatpackServer {} Starting server... 
2018-04-23 00:43:36,513 INFO r.s.RatpackServer {} Building registry... 
2018-04-23 00:43:37,933 INFO r.s.RatpackServer {} Initializing 13 services... 
2018-04-23 00:43:38,004 INFO c.g.b.n.c.a {executionId=5exjc4lmjdyvmsccc33w6ewd3i} Loading NodeSettings_2 from /data/system/config/system.v2.bin 
2018-04-23 00:43:38,223 INFO c.g.b.c.s.d.d {executionId=5exjc4lmjdyvmsccc33w6ewd3i} Target size set to 10000000000 
2018-04-23 00:43:38,223 INFO c.g.b.c.a.j {executionId=5exjc4lmjdyvmsccc33w6ewd3i} Max artifact size set to 100000000 
2018-04-23 00:43:38,291 INFO c.g.b.c.s.b.b {executionId=czz3x5q2crrsz3y7vu66yscigy} Listing store files took PT0.0039791S 
2018-04-23 00:43:38,297 INFO c.g.b.c.s.b.b {executionId=bubjw7qk2i6f66cliwy2xiw6lm} Reading LRU index took PT0.0086605S 
2018-04-23 00:43:38,299 INFO c.g.b.c.s.b.b {executionId=bubjw7qk2i6f66cliwy2xiw6lm} Store backing initialized 0 items in PT0.0481241S 
2018-04-23 00:43:38,303 INFO c.g.b.n.c.a {executionId=agb6aascrgpmwdbrgfi3cf3imu} Loading NodeRegistrationSettings from /data/system/config/registration.v1.bin 
2018-04-23 00:43:38,351 INFO r.s.RatpackServer {} Ratpack started for http://localhost:5000 
2018-04-23 00:44:29,383 WARN r.e.i.DefaultProductionErrorHandler {executionId=4gvfhnaavf5cgrtvywestgs6ke, requestId=b80018cf-d196-56c1-88ab-86a3c11a3356} Default production error handler used to render client error, please add a ratpack.error.ClientErrorHandler instance to your application (method: GET, uri: /196d7f5bdba18053b63d9e7211e03f25) 
2018-04-23 00:44:29,455 WARN r.e.i.DefaultProductionErrorHandler {executionId=62jobfukha2scsrtnq4d2sikfe, requestId=beaa77dc-4d88-f20f-b478-c9aab4b88b53} Default production error handler used to render client error, please add a ratpack.error.ClientErrorHandler instance to your application (method: PUT, uri: /196d7f5bdba18053b63d9e7211e03f25) 
2018-04-23 00:46:59,042 WARN r.e.i.DefaultProductionErrorHandler {executionId=5zlaemlp5temoq3yrjjpxn5fci, requestId=8a9b5934-09c5-bed0-f69e-ecef4e32dc06} Default production error handler used to render client error, please add a ratpack.error.ClientErrorHandler instance to your application (method: GET, uri: /e7e26be0cea9a15ad6ef501cdf43431e) 
2018-04-23 00:46:59,091 WARN r.e.i.DefaultProductionErrorHandler {executionId=pcx5ea7u4o4z7axuk5s5kvmshi, requestId=d0f7062c-07b7-2e97-0fff-f5546d8e9778} Default production error handler used to render client error, please add a ratpack.error.ClientErrorHandler instance to your application (method: PUT, uri: /e7e26be0cea9a15ad6ef501cdf43431e) 

However there isn’t any obvious reason for the 404… Anyone have any ideas ?


(James Justinic) #2

Check the configured remote URL for the cache. The build cache node serves an interface at /, but the actual cache is located at /cache/.


(Jonathan Ackerman) #3

Ahhh, yes that appears to be the problem!

Thanks