What's new

Unbound unbound-control reload errors

  • Thread starter Deleted member 62525
  • Start date
  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

D

Deleted member 62525

Guest
I remember that unbound-control reload command used to work on previous versions. Can someone confirm that it is still working? When I try manually run unbound-control -c /opt/var/lib/unbound/unbound.conf reload it is reporting "ok" but
it is crushing with "error: can't bind socket: Address already in use for 127.0.0.1 port 953".
Checking netstat and there is nothing running on port 953 but Unbound, however in the unbound log I see this message when unbound is trying to reload:
fatal error: Could not read config file: /unbound/unbound.conf. Maybe try unbound -dd

It seems that even if I supply -c flag to unbound-control, unbound is trying to load wrong file.
FYI, unbound-control start|stop even if I done without specify -c works just fine.
 

Similar threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top