[opensuse] Recent update to bind-9.9.9P1-36.1 seems to have broken named on Leap 42.1
After my most recent "zypper up" on Leap 42.1 the named (daemon) would not start. There weren't any error messages in the system log, it just said named was starting, but it didn't start. There were also updates to procps in the same update. Fortunately for me my backup name server runs 13.2 which didn't receive the update. I used snapper to roll the change back. I will research the problem further on Tuesday if somebody else hasn't figured it out. Bill -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Fri, Jul 01, 2016 at 04:57:56PM -0400, Bill Merriam wrote:
After my most recent "zypper up" on Leap 42.1 the named (daemon) would not start. There weren't any error messages in the system log, it just said named was starting, but it didn't start. There were also updates to procps in the same update.
Fortunately for me my backup name server runs 13.2 which didn't receive the update. I used snapper to roll the change back. I will research the problem further on Tuesday if somebody else hasn't figured it out.
can you check the named.log and systemctl status named.service Ciao, Marcus -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Fri, 2016-07-01 at 23:06 +0200, Marcus Meissner wrote:
On Fri, Jul 01, 2016 at 04:57:56PM -0400, Bill Merriam wrote:
After my most recent "zypper up" on Leap 42.1 the named (daemon) would not start. There weren't any error messages in the system log, it just said named was starting, but it didn't start. There were also updates to procps in the same update.
Fortunately for me my backup name server runs 13.2 which didn't receive the update. I used snapper to roll the change back. I will research the problem further on Tuesday if somebody else hasn't figured it out.
can you check the named.log and systemctl status named.service
Ciao, Marcus
Here in America we are supposed to be eating and drinking beer this weekend. I decided to fix this problem. I moved my bind installation to another VM with Leap 42.1 that already had bind-9.9.9P1-36.1 installed and IT WORKS FINE. It still doesn't work on the first VM so there is something strange about that system. I will do a clean install of that system and forget about the problem. So there is nothing wrong with the bind package, please disregard my post. Bill -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (2)
-
Bill Merriam -
Marcus Meissner