Skip to content
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

Consul server reports agent.rpc error whenever CLI commands are run #2356

Closed
godefroi opened this issue Sep 23, 2016 · 2 comments
Closed

Consul server reports agent.rpc error whenever CLI commands are run #2356

godefroi opened this issue Sep 23, 2016 · 2 comments

Comments

@godefroi
Copy link

godefroi commented Sep 23, 2016

consul version for both Client and Server

Client: Consul v0.7.0
Server: Consul v0.7.0

consul info for both Client and Server

Client:

agent:
        check_monitors = 0
        check_ttls = 0
        checks = 0
        services = 1
build:
        prerelease =
        revision = 'a189091
        version = 0.7.0
consul:
        bootstrap = false
        known_datacenters = 1
        leader = false
        leader_addr = 10.8.16.200:8300
        server = true
raft:
        applied_index = 756034
        commit_index = 756034
        fsm_pending = 0
        last_contact = 42.9613ms
        last_log_index = 756034
        last_log_term = 109
        last_snapshot_index = 755547
        last_snapshot_term = 109
        latest_configuration = [{Suffrage:Voter ID:10.8.16.201:8300 Address:10.8.16.201:8300} {Suffrage:Voter ID:10.8.16.200:8300 Address:10.8.16.200:8300} {Suffrage:Voter ID:10.8.16.195:8300 Address:10.8.16.195:8300} {Suffrage:Voter ID:10.8.16.202:8300 Address:10.8.16.202:8300}]
        latest_configuration_index = 744666
        num_peers = 3
        protocol_version = 1
        protocol_version_max = 3
        protocol_version_min = 0
        snapshot_version_max = 1
        snapshot_version_min = 0
        state = Follower
        term = 109
runtime:
        arch = amd64
        cpu_count = 2
        goroutines = 58
        max_procs = 2
        os = windows
        version = go1.6.3
serf_lan:
        encrypted = false
        event_queue = 0
        event_time = 66
        failed = 0
        health_score = 0
        intent_queue = 0
        left = 1
        member_time = 97
        members = 6
        query_queue = 0
        query_time = 1
serf_wan:
        encrypted = false
        event_queue = 0
        event_time = 1
        failed = 0
        health_score = 0
        intent_queue = 0
        left = 0
        member_time = 3
        members = 1
        query_queue = 0
        query_time = 1

Server:

(same as client, it's on the same machine)

Operating system and Environment details

Windows Server 2012 R2, both client and server (in this case, they're on the same machine).

Description of the Issue (and unexpected/desired result)

Each time I run a CLI command, the server log spits out an error indicating some sort of network oddity between the client and server.

Reproduction steps

Run any CLI command (for example, consul info) and check the server's log

Log Fragments or Link to gist

2016/09/23 10:59:43 [INFO] agent.rpc: Accepted client: 127.0.0.1:64239
2016/09/23 10:59:43 [ERR] agent.rpc: failed to decode request header: read tcp 127.0.0.1:8400->127.0.0.1:64239: wsarecv: An existing connection was forcibly closed by the remote host.
2016/09/23 11:19:23 [INFO] agent.rpc: Accepted client: 127.0.0.1:49848
2016/09/23 11:19:23 [ERR] agent.rpc: failed to decode request header: read tcp 127.0.0.1:8400->127.0.0.1:49848: wsarecv: An existing connection was forcibly closed by the remote host.
@slackpad
Copy link
Contributor

Hi @godefroi does the command succeed but you see this error in the log? It looks like there's an old check for this error to try to mask it, and we might need to make the string compare case insensitive - bae3c16.

@godefroi
Copy link
Author

Yes, the commands always succeed; you'd never know anything was wrong if you didn't check the server's log.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants