Nonexistent config path and cur cannot be blank

I was looking through my server logs and I noticed a couple of entries that make me wonder if I should be doing something about them. Here is a snippet of the log:

2022-02-19T01:40:30.647Z [INFO]  waypoint: waypoint version: full_string="v0.7.1 (062857d16)" version=v0.7.1 prerelease="" metadata="" revision=062857d16
2022-02-19T01:40:30.647Z [TRACE] waypoint: starting interrupt listener for context cancellation
2022-02-19T01:40:30.648Z [TRACE] waypoint: interrupt listener goroutine started
2022-02-19T01:40:30.648Z [DEBUG] waypoint: home configuration directory: path=/nonexistent/.config/waypoint
2022-02-19T01:40:30.648Z [INFO]  waypoint.server: opening DB: path=/alloc/data/data.db
2022-02-19T01:40:30.661Z [DEBUG] waypoint.server.singleprocess: checking if DB restore is requested
2022-02-19T01:40:30.661Z [TRACE] waypoint.server.singleprocess: acquiring file lock for restore: path=/alloc/data/waypoint-restore.db.lock
2022-02-19T01:40:30.661Z [DEBUG] waypoint.server.singleprocess: no restore file found, no DB restore requested
2022-02-19T01:40:30.661Z [TRACE] waypoint.server.singleprocess: releasing file lock for restore: path=/alloc/data/waypoint-restore.db.lock
2022-02-19T01:40:30.676Z [DEBUG] waypoint.server.singleprocess.url_service: API token not set in config, initializing guest account
2022-02-19T01:40:30.676Z [DEBUG] waypoint.server.singleprocess.url_service: connecting to URL service to retrieve guest token: addr=api.waypoint.run:443 tls=true
2022-02-19T01:40:30.676Z [DEBUG] waypoint.server.singleprocess.url_service: waiting on server connection state to become ready
2022-02-19T01:40:30.676Z [TRACE] waypoint.server.singleprocess.url_service: connection state: state=IDLE
2022-02-19T01:40:30.677Z [TRACE] waypoint.server.singleprocess.url_service: connection state: state=CONNECTING
2022-02-19T01:40:30.772Z [TRACE] waypoint.server.singleprocess.url_service: connection state: state=READY
2022-02-19T01:40:30.772Z [DEBUG] waypoint.server.singleprocess.url_service: connection is ready
2022-02-19T01:40:30.835Z [TRACE] waypoint.server.singleprocess.url_service: connection state: state=IDLE
2022-02-19T01:40:30.835Z [TRACE] waypoint.server.singleprocess.url_service: connection state: state=CONNECTING
2022-02-19T01:40:30.904Z [TRACE] waypoint.server.singleprocess.url_service: connection state: state=READY
2022-02-19T01:40:30.904Z [DEBUG] waypoint.server.singleprocess.url_service: connection is ready
2022-02-19T01:40:30.904Z [INFO]  waypoint.server.singleprocess.url_service: URL service client successfully initialized
2022-02-19T01:40:30.915Z [DEBUG] waypoint.server.grpc: starting listener: addr=:9701
2022-02-19T01:40:30.915Z [INFO]  waypoint.server.singleprocess.poll_queuer.project: starting
2022-02-19T01:40:30.915Z [TRACE] waypoint.server.singleprocess.poll_queuer.project: waiting on watchset and contexts
2022-02-19T01:40:30.915Z [INFO]  waypoint.server.singleprocess.poll_queuer.application_statusreport: starting
2022-02-19T01:40:30.915Z [TRACE] waypoint.server.singleprocess.poll_queuer.application_statusreport: no application returned from peek
2022-02-19T01:40:30.915Z [TRACE] waypoint.server.singleprocess.poll_queuer.application_statusreport: waiting on watchset and contexts
2022-02-19T01:40:30.915Z [INFO]  waypoint.server.singleprocess.prune: starting
...
2022-02-19T01:50:30.916Z [ERROR] waypoint.server.singleprocess.prune: error pruning data: error="cur: cannot be blank."
2022-02-19T02:00:30.916Z [ERROR] waypoint.server.singleprocess.prune: error pruning data: error="cur: cannot be blank."

The lines that concern me are these two:

  • waypoint: home configuration directory: path=/nonexistent/.config/waypoint
  • waypoint.server.singleprocess.prune: error pruning data: error="cur: cannot be blank."

Should I be worried about either of those?

1 Like