Forum Discussion
ray1234_166092
Nimbostratus
NimbostratusZoneRunner error
Hello,
There were some records added in the ZoneRunner when suddenly the issue happened with the error message for each menu as below: Global Traffice -> ZoneRunner -> Resource Record List -> Error: "01020005:3: The requested operation is not implemented yet" Global Traffice -> ZoneRunner -> Zone List -> Error: "General Error" Global Traffice -> ZoneRunner -> View List -> Error: "General Error" Global Traffice -> ZoneRunner -> Named Configuration -> Error: "Error trying to access the database."
Login to the box showed that it keeps trying to re-starting zrd daemon.
Checking the system log, I found this information (some names are changed): Aug 7 05:30:10 local/usf5-01 err zrd[2030]: 01150403:3: Server failure during update Aug 7 05:30:11 local/usf5-01 err zrd[2030]: 0115020b:3: Errors in config file server reload successful. zone internal.abcd.com/IN: journal rollforward failed: journal out of sync with zone. internal/internal.abcd.com./IN: out of range. zone 148.24.10.in-addr.arpa/IN: loaded serial 4. zone 140.24.10.in-addr.arpa/IN: loaded serial 10.
I found this document in the KB that looks match with the issue: sol10066 (http://support.f5.com/kb/en-us/solutions/public/10000/000/sol10066.html). The recommended workaround is to delete the corresponding journal file. Questions: 1. I assume the corresponding journal file that need to be deleted is db.internal.abcd.com..jnl, correct? 2. Will there be a negative impact (service disruption) by deleting that file? Currently this box is still functioning well in answering DNS queries. 3. This box is part of the synchronization group, which consists of three boxes. Only this box which has ZoneRunner error, the other two are accessible from the GUI. Do I need to delete the same journal file in two other boxes? Again, will there be any service disruption caused by deleting the file?
Thank you Raymond.
ray1234_166092Additional questions: 4. Does this message: "internal/internal.abcd.com./IN: out of range." relates to the same issue or it's another problem that need to be looked into? 5. I guess this message "zone 148.24.10.in-addr.arpa/IN: loaded serial 4. zone 140.24.10.in-addr.arpa/IN: loaded serial 10." means it's working normally and should not be worried about, right?
OTS02Cirrus
You may get this one resolved faster/better/easier by opening an f5 Support case. I had a similar problem (zrd constantly restarting) and it had to do with a Zonerunner bug in 11.2.1 HF9. If this is a sync pair, be sure you have taken .ucs backups.
kridsanaCirrocumulus
How is the problem? I have experience this right now and don't know how to work around this.
Thank you
cagdasyiThis is an old thread but it may be beneficial for someone in the future. We had a very similar problem in our environment recently. Following the solution article https://support.f5.com/csp/article/K10066 resolved the problem. You need to stop the zrd and the named processes and then remove the relevant journal file(s). And then start the named and the zrd processes again. Stopping the zrd is harmless in regards to dns resolution. Stopping the named process will make your BIND unresponsive so you may want to do that in a maintenance window.