trino: node.environment: may not be null

when I try bin/launcher run I get this error Invalid configuration property node.environment: may not be null (for class io.airlift.node.NodeConfig.environment) my node.environment is set to “test” so I don’t see what is the issue.

bin/launcher run
OpenJDK 64-Bit Server VM warning: Option UseBiasedLocking was deprecated in version 15.0 and will likely be removed in a future release.
Jan 04, 2022 10:35:00 AM io.airlift.log.Logger info
INFO: Java version: 16.0.1
2022-01-04T10:35:00.653Z	INFO	main	io.airlift.log.Logging	Logging to stderr
2022-01-04T10:35:00.655Z	INFO	main	Bootstrap	Loading configuration
2022-01-04T10:35:00.944Z	INFO	main	Bootstrap	Initializing logging
2022-01-04T10:35:03.608Z	ERROR	main	io.trino.server.Server	Configuration is invalid
==========

Errors:

1) Invalid configuration property node.environment: may not be null (for class io.airlift.node.NodeConfig.environment)

and this is my node.properties

node.environment=production
node.id=ffffffff-ffff-ffff-ffff-ffffffffffff
node.data-dir=/home/accidf/Desktop/Trino/data

another thing worth mentioning, if I rename node.environment such that it contains invalid characters (‘-’ and uppercase letters) I still get the same error.

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Comments: 19 (7 by maintainers)

Most upvoted comments

As we talked in Slack, the node.proporties file name was wrong. It was node.porperties in your environment.