Issue with v 1.1

Users Dgraph
1

Hi all,

I got error while trying to start new dgrah instance (no old version database, just a new launch with version 1.1).

Here’s what i got, when run dgraph zero:

[Decoder]: Using assembly version of decoder
I1018 13:12:21.964166    3184 init.go:98]

Dgraph version   : v1.1.0
Dgraph SHA-256   : da23a00e333176e5e7ef5dcc1280d09193b1eb5a72450e0cc34e7ddd1cee463f
Commit SHA-1     : ef7cdb28
Commit timestamp : 2019-09-04 00:12:51 -0700
Branch           : HEAD
Go version       : go1.12.7

For Dgraph official documentation, visit https://docs.dgraph.io.
For discussions about Dgraph     , visit http://discuss.dgraph.io.
To say hi to the community       , visit https://dgraph.slack.com.

Licensed variously under the Apache Public License 2.0 and Dgraph Community License.
Copyright 2015-2018 Dgraph Labs, Inc.


I1018 13:12:21.989071    3184 run.go:102] Setting up grpc listener at: 0.0.0.0:5080
I1018 13:12:21.991066    3184 run.go:102] Setting up http listener at: 0.0.0.0:6080
badger 2019/10/18 13:12:22 INFO: All 0 tables opened in 0s
2019/10/18 13:12:22 truncate zw\000000.vlog: The requested operation cannot be performed on a file with a user-mapped section open.
During db.vlog.open
github.com/dgraph-io/dgraph/vendor/github.com/dgraph-io/badger/y.Wrapf
        /tmp/go/src/github.com/dgraph-io/dgraph/vendor/github.com/dgraph-io/badger/y/error.go:82
github.com/dgraph-io/dgraph/vendor/github.com/dgraph-io/badger.Open
        /tmp/go/src/github.com/dgraph-io/dgraph/vendor/github.com/dgraph-io/badger/db.go:323
github.com/dgraph-io/dgraph/dgraph/cmd/zero.run
        /tmp/go/src/github.com/dgraph-io/dgraph/dgraph/cmd/zero/run.go:208
github.com/dgraph-io/dgraph/dgraph/cmd/zero.init.0.func1
        /tmp/go/src/github.com/dgraph-io/dgraph/dgraph/cmd/zero/run.go:73
github.com/dgraph-io/dgraph/vendor/github.com/spf13/cobra.(*Command).execute
        /tmp/go/src/github.com/dgraph-io/dgraph/vendor/github.com/spf13/cobra/command.go:702
github.com/dgraph-io/dgraph/vendor/github.com/spf13/cobra.(*Command).ExecuteC
        /tmp/go/src/github.com/dgraph-io/dgraph/vendor/github.com/spf13/cobra/command.go:783
github.com/dgraph-io/dgraph/vendor/github.com/spf13/cobra.(*Command).Execute
        /tmp/go/src/github.com/dgraph-io/dgraph/vendor/github.com/spf13/cobra/command.go:736
github.com/dgraph-io/dgraph/dgraph/cmd.Execute
        /tmp/go/src/github.com/dgraph-io/dgraph/dgraph/cmd/root.go:68
main.main
        /tmp/go/src/github.com/dgraph-io/dgraph/dgraph/main.go:33
runtime.main
        /usr/local/go/src/runtime/proc.go:200
runtime.goexit
        /usr/local/go/src/runtime/asm_amd64.s:1337
Error while opening WAL store
github.com/dgraph-io/dgraph/x.Checkf
        /tmp/go/src/github.com/dgraph-io/dgraph/x/error.go:49
github.com/dgraph-io/dgraph/dgraph/cmd/zero.run
        /tmp/go/src/github.com/dgraph-io/dgraph/dgraph/cmd/zero/run.go:209
github.com/dgraph-io/dgraph/dgraph/cmd/zero.init.0.func1
        /tmp/go/src/github.com/dgraph-io/dgraph/dgraph/cmd/zero/run.go:73
github.com/dgraph-io/dgraph/vendor/github.com/spf13/cobra.(*Command).execute
        /tmp/go/src/github.com/dgraph-io/dgraph/vendor/github.com/spf13/cobra/command.go:702
github.com/dgraph-io/dgraph/vendor/github.com/spf13/cobra.(*Command).ExecuteC
        /tmp/go/src/github.com/dgraph-io/dgraph/vendor/github.com/spf13/cobra/command.go:783
github.com/dgraph-io/dgraph/vendor/github.com/spf13/cobra.(*Command).Execute
        /tmp/go/src/github.com/dgraph-io/dgraph/vendor/github.com/spf13/cobra/command.go:736
github.com/dgraph-io/dgraph/dgraph/cmd.Execute
        /tmp/go/src/github.com/dgraph-io/dgraph/dgraph/cmd/root.go:68
main.main
        /tmp/go/src/github.com/dgraph-io/dgraph/dgraph/main.go:33
runtime.main
        /usr/local/go/src/runtime/proc.go:200
runtime.goexit
        /usr/local/go/src/runtime/asm_amd64.s:1337

My system is Windows 10 Pro build 17134.
As I find out problem can be related with Visual Studio tools. But I don’t know how to cure this. Be very appreciated for any help.

2

As far as I know, this issue is fixed on master. You can try running the master branch and see if you still observe the same issue.

1 Like