node.environment: may not be null
See original GitHub issuewhen 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.
Issue Analytics
- State:
- Created 2 years ago
- Comments:19 (7 by maintainers)
Top Results From Across the Web
com.facebook.presto.server.PrestoServer Guice creation errors
1) Error: Constraint violation with property prefix '': environment may not be null (for class io.airlift.node.
Read more >Using AWS Lambda environment variables
Environment variables are not evaluated prior to the function invocation. Any value you define is considered a literal string and not expanded.
Read more >Deploying Presto — Presto 0.278 Documentation
All Presto nodes in a cluster must have the same environment name. node.id : The unique identifier for this installation of Presto. This...
Read more >Node.js v19.2.0 Documentation
Usage; Node-API version matrix; Environment life cycle APIs ... WARNING: This does not throw an AssertionError in legacy assertion mode! assert.
Read more >Configuration | NestJS - A progressive Node.js framework
Disable env variables loading#. If you don't want to load the .env file, but instead would like to simply access environment variables from...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
As we talked in Slack, the
node.proportiesfile name was wrong. It wasnode.porpertiesin your environment.ok