@[email protected]: thanks a lot for sharing this insight. I just had stumbled
in a similar problem (see
https://github.com/vegasbrianc/docker-monitoring/issues/9), and it was very
helpful to know that this is cause by a VirtualBox mmap issue.
I am using Vagrant 1.8.6 on Windows 10. My workaround was to switch from vboxsf
synced folders to smb synced folders. Since creation of an SMB share requires
Administrator rights, this requires following steps:
- add the line
config.vm.synced_folder ".", "/vagrant", type: "smb"
to the Vagrantfile inside the configure section
- start CMD as Administrator. E.g. run
runas.exe /savecred /user:Administrator "cmd"
in a non-priviledged CMD
- run "vagrant up" in the privideged CMD session
Then InfluxDB is starting with no problem:
root@bef79b5b982e:/# exec influxd -config=/config/config.toml
8888888 .d888 888 8888888b. 888888b.
888 d88P" 888 888 "Y88b 888 "88b
888 888 888 888 888 888 .88P
888 88888b. 888888 888 888 888 888 888 888 888 8888888K.
888 888 "88b 888 888 888 888 Y8bd8P' 888 888 888 "Y88b
888 888 888 888 888 888 888 X88K 888 888 888 888
888 888 888 888 888 Y88b 888 .d8""8b. 888 .d88P 888 d88P
8888888 888 888 888 888 "Y88888 888 888 8888888P" 8888888P"
2016/10/28 08:55:28 InfluxDB starting, version 0.9.6.1, branch 0.9.6, commit
6d3a8603cfdaf1a141779ed88b093dcc5c528e5e, built 2015-12-10T23:40:23+0000
2016/10/28 08:55:28 Go version go1.4.2, GOMAXPROCS set to 2
2016/10/28 08:55:29 Using configuration at: /config/config.toml
[metastore] 2016/10/28 08:55:29 Using data dir: /data/meta
[retention] 2016/10/28 08:55:29 retention policy enforcement terminating
[monitor] 2016/10/28 08:55:29 shutting down monitor system
[handoff] 2016/10/28 08:55:29 shutting down hh service
[subscriber] 2016/10/28 08:55:29 closed service
run: open server: open meta store: raft: new bolt store: invalid argument
If I work in a non-synced folder, InfluxDB starts without any problems.
...
influxdb_1 | [admin] 2016/10/28 08:58:58 Listening on HTTP: [::]:8083
influxdb_1 | [continuous_querier] 2016/10/28 08:58:58 Starting continuous
query service
influxdb_1 | [httpd] 2016/10/28 08:58:58 Starting HTTP service
influxdb_1 | [httpd] 2016/10/28 08:58:58 Authentication enabled: false
influxdb_1 | [httpd] 2016/10/28 08:58:58 Listening on HTTP: [::]:8086
influxdb_1 | [retention] 2016/10/28 08:58:58 Starting retention policy
enforcement service with check interval of 10m0s
influxdb_1 | [run] 2016/10/28 08:58:58 Listening for signals
Interestingly, upgrading InfluxDB from 0.9 to 0.13 also has solved the problem,
even if I keep using synced folders of the vboxsf type. However, I guess that
upgrading InfluxDB is not solving the root cause.
--
Remember to include the version number!
---
You received this message because you are subscribed to the Google Groups
"InfluxData" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
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/51354f8d-d018-4e17-b745-60c9b0ca5eb9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
