如何解决恐慌:没有可达的服务器

时间:2016-05-25 07:30:26

标签: linux raspberry-pi3

我正在尝试使用Raspberry pi来托管一个leanote,当我尝试运行leanote二进制文件时,它一直给我这个错误,其中没有可达的主机,可能是什么原因?

Panic: no reachable servers

goroutine 1 [running]:
github.com/leanote/leanote/app/db.Init(0x111a4ab0, 0x21, 0x1103c46a, 0x7)
        /Users/life/Documents/Go/package_base/src/github.com/leanote/leanote/app/db/Mgo.go:104 +0x500
github.com/leanote/leanote/app.init.1.func27()
        /Users/life/Documents/Go/package_base/src/github.com/leanote/leanote/app/init.go:413 +0x2c
github.com/revel/revel.runStartupHooks()
        /Users/life/Documents/Go/package_base/src/github.com/revel/revel/server.go:135 +0x70
github.com/revel/revel.Run(0x1f90)
        /Users/life/Documents/Go/package_base/src/github.com/revel/revel/server.go:92 +0x20c
main.main()
        /Users/life/leanote2/app/tmp/main.go:2294 +0x4f3c4

goroutine 9 [sleep]:
time.Sleep(0x1dcd6500, 0x0)
        /Users/life/app/go1.5.1/src/runtime/time.go:59 +0x104
gopkg.in/mgo%2ev2.(*mongoCluster).syncServersLoop(0x110c50e0)
        /Users/life/Documents/Go/package_base/src/gopkg.in/mgo.v2/cluster.go:383 +0x410
created by gopkg.in/mgo%2ev2.newCluster
        /Users/life/Documents/Go/package_base/src/gopkg.in/mgo.v2/cluster.go:76 +0x1c4

goroutine 49 [sleep]:
time.Sleep(0x2a05f200, 0x1)
        /Users/life/app/go1.5.1/src/runtime/time.go:59 +0x104
gopkg.in/mgo%2ev2.(*mongoServer).pinger(0x111de0a0, 0x1)
        /Users/life/Documents/Go/package_base/src/gopkg.in/mgo.v2/server.go:297 +0x180
created by gopkg.in/mgo%2ev2.newServer
        /Users/life/Documents/Go/package_base/src/gopkg.in/mgo.v2/server.go:90 +0x140

goroutine 52 [sleep]:
time.Sleep(0x2a05f200, 0x1)
        /Users/life/app/go1.5.1/src/runtime/time.go:59 +0x104
gopkg.in/mgo%2ev2.(*mongoServer).pinger(0x10f0c460, 0x1)
        /Users/life/Documents/Go/package_base/src/gopkg.in/mgo.v2/server.go:297 +0x180
created by gopkg.in/mgo%2ev2.newServer
        /Users/life/Documents/Go/package_base/src/gopkg.in/mgo.v2/server.go:90 +0x140

抱歉,我是这个XD的新手

1 个答案:

答案 0 :(得分:0)

您的mongoDB服务器很可能没有运行,请尝试检查psnetstat以确定mongod是否正在运行并连接到IP和端口。