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 logs are not pushed to syslog despite option being enabled on Ubuntu 14.04 #2056

Closed
ghost opened this issue May 16, 2016 · 4 comments
Closed
Labels
waiting-reply Waiting on response from Original Poster or another individual in the thread

Comments

@ghost
Copy link

ghost commented May 16, 2016

consul version for both Client and Server

Client: 0.6.4
Server: 0.6.4

consul info for both Client and Server

Client:

agent:
    check_monitors = 0
    check_ttls = 0
    checks = 1
    services = 2
build:
    prerelease =
    revision = 26a0ef8c
    version = 0.6.4
consul:
    known_servers = 3
    server = false
runtime:
    arch = amd64
    cpu_count = 2
    goroutines = 37
    max_procs = 2
    os = linux
    version = go1.6
serf_lan:
    encrypted = false
    event_queue = 0
    event_time = 959
    failed = 1
    intent_queue = 0
    left = 1
    member_time = 2903
    members = 113
    query_queue = 0
    query_time = 79

Server:

agent:
    check_monitors = 0
    check_ttls = 0
    checks = 0
    services = 1
build:
    prerelease =
    revision = 26a0ef8c
    version = 0.6.4
consul:
    bootstrap = false
    known_datacenters = 1
    leader = false
    server = true
raft:
    applied_index = 7278490
    commit_index = 7278490
    fsm_pending = 0
    last_contact = 55.448544ms
    last_log_index = 7278490
    last_log_term = 1638
    last_snapshot_index = 7277475
    last_snapshot_term = 1638
    num_peers = 2
    state = Follower
    term = 1638
runtime:
    arch = amd64
    cpu_count = 2
    goroutines = 202
    max_procs = 2
    os = linux
    version = go1.6
serf_lan:
    encrypted = false
    event_queue = 0
    event_time = 959
    failed = 3
    intent_queue = 0
    left = 6
    member_time = 2903
    members = 120
    query_queue = 0
    query_time = 79
serf_wan:
    encrypted = false
    event_queue = 0
    event_time = 1
    failed = 0
    intent_queue = 0
    left = 0
    member_time = 13
    members = 1
    query_queue = 0
    query_time = 1

Operating system and Environment details

Ubuntu 14.04

configuration:

{
  "data_dir": "/var/lib/consul",
  "retry_join": [
    "SANITIZED"
  ],
  "datacenter": "SANITIZED",
  "domain": "SANITIZED",
  "node_name": "SANITIZED",
  "ports": {
    "dns": 8600,
    "http": 8500,
    "rpc": 8400,
    "serf_lan": 8301,
    "serf_wan": 8302,
    "server": 8300
  },
  "enable_syslog": true
}

Description of the Issue (and unexpected/desired result)

Consul logs are not written to syslog, regardless if enable_syslog is set via command line or in configuration. This is only true of agents that are run as clients. On server nodes with a similar setup, I did not see any issues.

Reproduction steps

I have been able to write to syslog as a server and as a OS X client, but not as a client on Ubuntu 14.04.

Log Fragments

Not sure how to trace or determine where issue might exist.

@slackpad
Copy link
Contributor

Hi @mjcdiggity this looks possibly related - #1610. Do you see any errors in your stderr log when starting?

@ghost
Copy link
Author

ghost commented Aug 11, 2016

@slackpad Nope. Just checked again and did not see anything in stderr log when starting. I also tried restarting rsyslog before starting consul with syslog enabled, but that did not seem to work or showed anything in stderr log.

@slackpad
Copy link
Contributor

slackpad commented May 3, 2017

@carkmorwin did you ever figure this one out?

@slackpad slackpad added the waiting-reply Waiting on response from Original Poster or another individual in the thread label May 3, 2017
@ghost
Copy link
Author

ghost commented May 7, 2017

@slackpad No I never got to the bottom of the issue, and have since moved on.

@ghost ghost closed this as completed May 7, 2017
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
waiting-reply Waiting on response from Original Poster or another individual in the thread
Projects
None yet
Development

No branches or pull requests

1 participant