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

cron is already configured, can not start scheduler #1111

Closed
xcw0754 opened this issue May 16, 2022 · 1 comment
Closed

cron is already configured, can not start scheduler #1111

xcw0754 opened this issue May 16, 2022 · 1 comment

Comments

@xcw0754
Copy link

xcw0754 commented May 16, 2022

I have 3 nodes:

  • vbox1: 192.168.56.103
  • vbox2: 192.168.56.104
  • vbox3: 192.168.56.105

After bootstrap, vbox3 was become a leader in this cluster. Then I restart vbox3, a new leader vbox1 was elected. When I restart vbox1, leadership was turn back to vbox3. This is the ouput below:

xxx@vbox3:~/dkron$ ./dkron agent --config=config.yml
INFO[2022-05-16T21:18:20+08:00] agent: Dkron agent starting                   node=vbox3
INFO[2022-05-16T21:18:20+08:00] agent: joining: [192.168.56.103 192.168.56.104 192.168.56.105] replay: true  node=vbox3
INFO[2022-05-16T21:18:20+08:00] agent: joined: 3 nodes                        node=vbox3
INFO[2022-05-16T21:18:20+08:00] api: Running HTTP server                      address=":8080" node=vbox3
INFO[2022-05-16T21:18:20+08:00] dkron: monitoring leadership                  node=vbox3
INFO[2022-05-16T21:18:20+08:00] agent: registering usage stats for cluster ID '9xcWVuPZKGLuJx0VJKroc4qphQhm/jUv1FEceqEPWRQ='  node=vbox3
WARN[2022-05-16T21:18:20+08:00] agent: unable to create the usage report client:Post "https://stats.dkron.io/session": dial tcp: lookup stats.dkron.io on 127.0.0.53:53: server misbehaving  node=vbox3
INFO[2022-05-16T21:18:20+08:00] agent: Listen for events                      node=vbox3
INFO[2022-05-16T21:18:21+08:00] agent: Received event                         event=member-join node=vbox3
INFO[2022-05-16T21:18:21+08:00] adding server                                 node=vbox3 server=vbox2
INFO[2022-05-16T21:18:21+08:00] adding server                                 node=vbox3 server=vbox1
INFO[2022-05-16T21:18:21+08:00] agent: Received event                         event=member-update node=vbox3
ERRO[2022-05-16T21:18:23+08:00] no member leader found in member list         node=vbox3
INFO[2022-05-16T21:18:57+08:00] dkron: cluster leadership acquired            node=vbox3
INFO[2022-05-16T21:18:57+08:00] dkron: monitoring leadership                  node=vbox3
INFO[2022-05-16T21:18:57+08:00] agent: Starting scheduler                     node=vbox3
INFO[2022-05-16T21:19:01+08:00] agent: Received event                         event=member-failed node=vbox3
INFO[2022-05-16T21:19:01+08:00] removing server vbox1 (Addr: 192.168.56.103:6868) (DC: dc1)  node=vbox3
INFO[2022-05-16T21:19:01+08:00] agent: Received event                         event=member-update node=vbox3
INFO[2022-05-16T21:19:13+08:00] agent: Received event                         event=member-update node=vbox3
INFO[2022-05-16T21:19:18+08:00] dkron: cluster leadership lost                node=vbox3
INFO[2022-05-16T21:19:18+08:00] dkron: monitoring leadership                  node=vbox3
ERRO[2022-05-16T21:19:19+08:00] no member leader found in member list         node=vbox3
INFO[2022-05-16T21:19:21+08:00] dkron: cluster leadership acquired            node=vbox3
INFO[2022-05-16T21:19:21+08:00] dkron: monitoring leadership                  node=vbox3
INFO[2022-05-16T21:19:21+08:00] agent: Starting scheduler                     node=vbox3
ERRO[2022-05-16T21:19:21+08:00] dkron: failed to establish leadership         error="cron is already configured, can not start scheduler" node=vbox3
INFO[2022-05-16T21:20:21+08:00] agent: Starting scheduler                     node=vbox3
ERRO[2022-05-16T21:20:21+08:00] dkron: failed to establish leadership         error="cron is already configured, can not start scheduler" node=vbox3
INFO[2022-05-16T21:21:21+08:00] agent: Starting scheduler                     node=vbox3
ERRO[2022-05-16T21:21:21+08:00] dkron: failed to establish leadership         error="cron is already configured, can not start scheduler" node=vbox3
INFO[2022-05-16T21:22:21+08:00] agent: Starting scheduler                     node=vbox3
ERRO[2022-05-16T21:22:21+08:00] dkron: failed to establish leadership         error="cron is already configured, can not start scheduler" node=vbox3
INFO[2022-05-16T21:23:21+08:00] agent: Starting scheduler                     node=vbox3
ERRO[2022-05-16T21:23:21+08:00] dkron: failed to establish leadership         error="cron is already configured, can not start scheduler" node=vbox3
INFO[2022-05-16T21:24:21+08:00] agent: Starting scheduler                     node=vbox3
ERRO[2022-05-16T21:24:21+08:00] dkron: failed to establish leadership         error="cron is already configured, can not start scheduler" node=vbox3

version

xxx@vbox1:~/dkron$ ./dkron version
INFO[0000] No valid config found: Applying default values.  error="Config File \"dkron\" Not Found in \"[/etc/dkron /home/xiao/.dkron /home/xiao/dkron/config]\""
Name: Dkron
Version: 3.1.11
Codename: merichuas
Agent Protocol: 5 (Understands back to: 2)

config.yml

server: true
bootstrap-expect: 3
data-dir: dkron.data
log-level: info
join:
  - 192.168.56.103
  - 192.168.56.104
  - 192.168.56.105
@vcastellm
Copy link
Member

Fixed in #1119

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

Successfully merging a pull request may close this issue.

2 participants