Re: [influxdb] run: parse config: toml: cannot load TOML value of type string into a Go boolean

[Konstantin Kulikov]

Remove quotes around "true" in:

[[collectd]]
  enabled = "true"

On Fri, Sep 16, 2016 at 11:42 AM  wrote:

> Hi,
>
> I am seeing the below issue while starting InfluxDB version
> influxdb-1.0.0-1.x86_64 on
> CentOS Linux release 7.2.1511 (Core)
>
> cat /etc/influxdb/influxdb.conf
> ### Welcome to the InfluxDB configuration file.
>
> # Once every 24 hours InfluxDB will report usage data to
> usage.influxdata.com
> # The data includes a random ID, os, arch, version, the number of series
> and other
> # usage data. No data from user databases is ever transmitted.
> # Change this option to true to disable reporting.
> reporting-disabled = false
>
> # we'll try to get the hostname automatically, but if it the os returns
> something
> # that isn't resolvable by other servers in the cluster, use this option to
> # manually set the hostname
> # hostname = "localhost"
>
> ###
> ### [meta]
> ###
> ### Controls the parameters for the Raft consensus group that stores
> metadata
> ### about the InfluxDB cluster.
> ###
>
> [meta]
>   # Where the metadata/raft database is stored
>   dir = "/var/lib/influxdb/meta"
>
>   retention-autocreate = true
>
>   # If log messages are printed for the meta service
>   logging-enabled = true
>   pprof-enabled = false
>
>   # The default duration for leases.
>   lease-duration = "1m0s"
>
> ###
> ### [data]
> ###
> ### Controls where the actual shard data for InfluxDB lives and how it is
> ### flushed from the WAL. "dir" may need to be changed to a suitable place
> ### for your system, but the WAL settings are an advanced configuration.
> The
> ### defaults should work for most systems.
> ###
>
> [data]
>   # Controls if this node holds time series data shards in the cluster
>   enabled = true
>
>   dir = "/var/lib/influxdb/data"
>
>   # These are the WAL settings for the storage engine >= 0.9.3
>   wal-dir = "/var/lib/influxdb/wal"
>   wal-logging-enabled = true
>
>   # Trace logging provides more verbose output around the tsm engine.
> Turning
>   # this on can provide more useful output for debugging tsm engine issues.
>   # trace-logging-enabled = false
>
>   # Whether queries should be logged before execution. Very useful for
> troubleshooting, but will
>   # log any sensitive data contained within a query.
>   # query-log-enabled = true
>
>   # Settings for the TSM engine
>
>   # CacheMaxMemorySize is the maximum size a shard's cache can
>   # reach before it starts rejecting writes.
>   # cache-max-memory-size = 524288000
>
>   # CacheSnapshotMemorySize is the size at which the engine will
>   # snapshot the cache and write it to a TSM file, freeing up memory
>   # cache-snapshot-memory-size = 26214400
>
>   # CacheSnapshotWriteColdDuration is the length of time at
>   # which the engine will snapshot the cache and write it to
>   # a new TSM file if the shard hasn't received writes or deletes
>   # cache-snapshot-write-cold-duration = "1h"
>
>   # MinCompactionFileCount is the minimum number of TSM files
>   # that need to exist before a compaction cycle will run
>   # compact-min-file-count = 3
>
>   # CompactFullWriteColdDuration is the duration at which the engine
>   # will compact all TSM files in a shard if it hasn't received a
>   # write or delete
>   # compact-full-write-cold-duration = "24h"
>
>   # MaxPointsPerBlock is the maximum number of points in an encoded
>   # block in a TSM file. Larger numbers may yield better compression
>   # but could incur a performance penalty when querying
>   # max-points-per-block = 1000
>
> ###
> ### [coordinator]
> ###
> ### Controls the clustering service configuration.
> ###
>
> [coordinator]
>   write-timeout = "10s"
>   max-concurrent-queries = 0
>   query-timeout = "0"
>   log-queries-after = "0"
>   max-select-point = 0
>   max-select-series = 0
>   max-select-buckets = 0
>
> ###
> ### [retention]
> ###
> ### Controls the enforcement of retention policies for evicting old data.
> ###
>
> [retention]
>   enabled = true
>   check-interval = "30m"
>
> ###
> ### [shard-precreation]
> ###
> ### Controls the precreation of shards, so they are available before data
> arrives.
> ### Only shards that, after creation, will have both a start- and end-time
> in the
> ### future, will ever be created. Shards are never precreated that would
> be wholly
> ### or partially in the past.
>
> [shard-precreation]
>   enabled = true
>   check-interval = "10m"
>   advance-period = "30m"
>
> ###
> ### Controls the system self-monitoring, statistics and diagnostics.
> ###
> ### The internal database for monitoring data is created automatically if
> ### if it does not already exist. The target retention within this database
> ### is called 'monitor' and is also created with a retention period of 7
> days
> ### and a replication factor of 1, if it does not exist. In all cases the
> ### this retention policy is configured as the default for the database.
>
> [monitor]
>   store-enabled = true # Whether to record statistics internally.
>   store-databa

Re: [influxdb] run: parse config: toml: cannot load TOML value of type string into a Go boolean

[Sean Beckett]

We don't have a separate validation process or script, no.

If InfluxDB launches, the config file is valid ;)



On Fri, Sep 16, 2016 at 12:47 PM, Kaushal Shriyan 
wrote:

>
>
> On Fri, Sep 16, 2016 at 8:50 PM, Sean Beckett  wrote:
>
>> Kaushal,
>>
>> The key line in the logs is "parse config: toml: cannot load TOML value
>> of type string into a Go boolean"
>>
>> The [[collecd]] section has enabled = "true". Booleans are not strings,
>> and should not be surrounded by double-quotes. Change that instead to this
>> and everything should load fine.
>>
>> [[collectd]]
>>   enabled = true
>>
>
> Thanks Sean for the reply and it fixed the issue. Is there a way to
> validate the influxdb.conf file for any syntax related issues?
>
> Regards,
>
> Kaushal
>
> --
> Remember to include the InfluxDB version number with all issue reports
> ---
> You received this message because you are subscribed to the Google Groups
> "InfluxDB" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to influxdb+unsubscr...@googlegroups.com.
> To post to this group, send email to influxdb@googlegroups.com.
> Visit this group at https://groups.google.com/group/influxdb.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/influxdb/CAD7Ssm9uXFJOD1R_Zyuor2jiEjb1jd_5i25fPnPksUufZMKXFQ%40mail.
> gmail.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Sean Beckett
Director of Support and Professional Services
InfluxDB

-- 
Remember to include the InfluxDB version number with all issue reports
--- 
You received this message because you are subscribed to the Google Groups 
"InfluxDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to influxdb+unsubscr...@googlegroups.com.
To post to this group, send email to influxdb@googlegroups.com.
Visit this group at https://groups.google.com/group/influxdb.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/influxdb/CALGqCvMy1kTnUdwMfj362jErw4J0uvRYycmM5SaAYtXA2kOnLQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [influxdb] run: parse config: toml: cannot load TOML value of type string into a Go boolean

[Kaushal Shriyan]

On Fri, Sep 16, 2016 at 8:50 PM, Sean Beckett  wrote:

> Kaushal,
>
> The key line in the logs is "parse config: toml: cannot load TOML value
> of type string into a Go boolean"
>
> The [[collecd]] section has enabled = "true". Booleans are not strings,
> and should not be surrounded by double-quotes. Change that instead to this
> and everything should load fine.
>
> [[collectd]]
>   enabled = true
>

Thanks Sean for the reply and it fixed the issue. Is there a way to
validate the influxdb.conf file for any syntax related issues?

Regards,

Kaushal

-- 
Remember to include the InfluxDB version number with all issue reports
--- 
You received this message because you are subscribed to the Google Groups 
"InfluxDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to influxdb+unsubscr...@googlegroups.com.
To post to this group, send email to influxdb@googlegroups.com.
Visit this group at https://groups.google.com/group/influxdb.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/influxdb/CAD7Ssm9uXFJOD1R_Zyuor2jiEjb1jd_5i25fPnPksUufZMKXFQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [influxdb] run: parse config: toml: cannot load TOML value of type string into a Go boolean

[Sean Beckett]

Kaushal,

The key line in the logs is "parse config: toml: cannot load TOML value of
type string into a Go boolean"

The [[collecd]] section has enabled = "true". Booleans are not strings, and
should not be surrounded by double-quotes. Change that instead to this and
everything should load fine.

[[collectd]]
  enabled = true

On Fri, Sep 16, 2016 at 2:42 AM,  wrote:

> Hi,
>
> I am seeing the below issue while starting InfluxDB version
> influxdb-1.0.0-1.x86_64 on
> CentOS Linux release 7.2.1511 (Core)
>
> cat /etc/influxdb/influxdb.conf
> ### Welcome to the InfluxDB configuration file.
>
> # Once every 24 hours InfluxDB will report usage data to
> usage.influxdata.com
> # The data includes a random ID, os, arch, version, the number of series
> and other
> # usage data. No data from user databases is ever transmitted.
> # Change this option to true to disable reporting.
> reporting-disabled = false
>
> # we'll try to get the hostname automatically, but if it the os returns
> something
> # that isn't resolvable by other servers in the cluster, use this option to
> # manually set the hostname
> # hostname = "localhost"
>
> ###
> ### [meta]
> ###
> ### Controls the parameters for the Raft consensus group that stores
> metadata
> ### about the InfluxDB cluster.
> ###
>
> [meta]
>   # Where the metadata/raft database is stored
>   dir = "/var/lib/influxdb/meta"
>
>   retention-autocreate = true
>
>   # If log messages are printed for the meta service
>   logging-enabled = true
>   pprof-enabled = false
>
>   # The default duration for leases.
>   lease-duration = "1m0s"
>
> ###
> ### [data]
> ###
> ### Controls where the actual shard data for InfluxDB lives and how it is
> ### flushed from the WAL. "dir" may need to be changed to a suitable place
> ### for your system, but the WAL settings are an advanced configuration.
> The
> ### defaults should work for most systems.
> ###
>
> [data]
>   # Controls if this node holds time series data shards in the cluster
>   enabled = true
>
>   dir = "/var/lib/influxdb/data"
>
>   # These are the WAL settings for the storage engine >= 0.9.3
>   wal-dir = "/var/lib/influxdb/wal"
>   wal-logging-enabled = true
>
>   # Trace logging provides more verbose output around the tsm engine.
> Turning
>   # this on can provide more useful output for debugging tsm engine issues.
>   # trace-logging-enabled = false
>
>   # Whether queries should be logged before execution. Very useful for
> troubleshooting, but will
>   # log any sensitive data contained within a query.
>   # query-log-enabled = true
>
>   # Settings for the TSM engine
>
>   # CacheMaxMemorySize is the maximum size a shard's cache can
>   # reach before it starts rejecting writes.
>   # cache-max-memory-size = 524288000
>
>   # CacheSnapshotMemorySize is the size at which the engine will
>   # snapshot the cache and write it to a TSM file, freeing up memory
>   # cache-snapshot-memory-size = 26214400
>
>   # CacheSnapshotWriteColdDuration is the length of time at
>   # which the engine will snapshot the cache and write it to
>   # a new TSM file if the shard hasn't received writes or deletes
>   # cache-snapshot-write-cold-duration = "1h"
>
>   # MinCompactionFileCount is the minimum number of TSM files
>   # that need to exist before a compaction cycle will run
>   # compact-min-file-count = 3
>
>   # CompactFullWriteColdDuration is the duration at which the engine
>   # will compact all TSM files in a shard if it hasn't received a
>   # write or delete
>   # compact-full-write-cold-duration = "24h"
>
>   # MaxPointsPerBlock is the maximum number of points in an encoded
>   # block in a TSM file. Larger numbers may yield better compression
>   # but could incur a performance penalty when querying
>   # max-points-per-block = 1000
>
> ###
> ### [coordinator]
> ###
> ### Controls the clustering service configuration.
> ###
>
> [coordinator]
>   write-timeout = "10s"
>   max-concurrent-queries = 0
>   query-timeout = "0"
>   log-queries-after = "0"
>   max-select-point = 0
>   max-select-series = 0
>   max-select-buckets = 0
>
> ###
> ### [retention]
> ###
> ### Controls the enforcement of retention policies for evicting old data.
> ###
>
> [retention]
>   enabled = true
>   check-interval = "30m"
>
> ###
> ### [shard-precreation]
> ###
> ### Controls the precreation of shards, so they are available before data
> arrives.
> ### Only shards that, after creation, will have both a start- and end-time
> in the
> ### future, will ever be created. Shards are never precreated that would
> be wholly
> ### or partially in the past.
>
> [shard-precreation]
>   enabled = true
>   check-interval = "10m"
>   advance-period = "30m"
>
> ###
> ### Controls the system self-monitoring, statistics and diagnostics.
> ###
> ### The internal database for monitoring data is created automatically if
> ### if it does not already exist. The target retention within this database
> ### is called 'monitor' and is also created with a retention perio