-
Notifications
You must be signed in to change notification settings - Fork 352
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
树莓派上运行很难保持登录状态 #413
Comments
开debug日志看看哪里报错。同时确认下配置文件权限是否有问题 |
` goroutine 1 [running]: |
"https://openapi.alipan.com/adrive/v1.0/user/getDriveInfo": dial tcp 47.88.74.38:443: connect: connection refused 你这是阿里官网都连不上了,可以先确认一下树莓派系统所在的环境的网络情况是否ok的。例如网络权限配置之类的。 |
尝试在在树莓派上运行24小时监控和下载脚本,上传一次后只过了2分钟再次执行上传就跳出下面这个提示了:
`
尝试登录失败,请使用 login 命令进行重新登录
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x390 pc=0x5faf0c]
goroutine 1 [running]:
github.com/tickstep/aliyunpan/internal/command.parseDriveId(0x40001f0580)
/Users/tickstep/Documents/Workspace/go/projects/aliyunpan/internal/command/command.go:57 +0x2c
github.com/tickstep/aliyunpan/internal/command.CmdDownload.func1(0x40001f0580)
/Users/tickstep/Documents/Workspace/go/projects/aliyunpan/internal/command/download.go:136 +0x168
github.com/urfave/cli.HandleAction({0x688c20?, 0x8e4af8?}, 0x8?)
/Users/tickstep/Applications/go/pkg/mod/github.com/urfave/cli@v1.21.1-0.20190817182405-23c83030263f/app.go:523 +0x58
github.com/urfave/cli.Command.Run({{0x7734f0, 0x8}, {0x0, 0x0}, {0x4000217c30, 0x1, 0x1}, {0x77bdc6, 0x13}, {0x40001e80a0, ...}, ...}, ...)
/Users/tickstep/Applications/go/pkg/mod/github.com/urfave/cli@v1.21.1-0.20190817182405-23c83030263f/command.go:174 +0x500
github.com/urfave/cli.(*App).Run(0x400022c000, {0x40000b6000, 0x7, 0x7})
/Users/tickstep/Applications/go/pkg/mod/github.com/urfave/cli@v1.21.1-0.20190817182405-23c83030263f/app.go:276 +0x820
main.main()
/Users/tickstep/Documents/Workspace/go/projects/aliyunpan/main.go:681 +0x1470
`
然后得再次登录,并且还要登录好几次才行
The text was updated successfully, but these errors were encountered: