Skip to content

Upgrade client and connect: apparent errors #13

@DiagonalArg

Description

@DiagonalArg

I upgraded after two years:

$ /usr/lib/go-1.10/bin/go get -u vuvuzela.io/vuvuzela/cmd/vuvuzela-client
package crypto/ed25519: unrecognized import path "crypto/ed25519" (import path does not begin with hostname)
package github.com/godbus/dbus/v5: cannot find package "github.com/godbus/dbus/v5" in any of:
        /usr/lib/go-1.10/src/github.com/godbus/dbus/v5 (from $GOROOT)
        /home/dev/go/src/github.com/godbus/dbus/v5 (from $GOPATH)
package google.golang.org/genproto/googleapis/rpc/status: google.golang.org/genproto is a custom import path for https://github.com/googleapis/go-genproto, but /home/dev/go/src/google.golang.org/genproto is checked out from https://github.com/google/go-genproto

I was curious if the md5 of the client would change, so I checked it before and after. It did not:

901cb30ede47e5b7d5d19bdd68422b69 vuvuzela-client

Then I ran the client and /connect:

 -!- Connection error: inconsistent PKG status for "XXXXXXX":
  ·  PKG pkg1.vuvuzela.io:8443: Post https://pkg1.vuvuzela.io:8443/status: read tcp 10.18.0.3:56142->128.52.176.147:8443: read: connection reset by peer
  ·  PKG nickolai.srv.vuvuzela.io:54331: Post https://nickolai.srv.vuvuzela.io:54331/status: read tcp 10.18.0.3:54780->50.202.194.198:54331: read: connection reset by peer
  ·  PKG pkg2.vuvuzela.io:8443: Post https://pkg2.vuvuzela.io:8443/status: read tcp 10.18.0.3:39762->128.31.25.215:8443: read: connection reset by peer
 -!- Type /connect after resolving the issue to try again.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions