how to schedule simple command to be executed every 12h on Gaia R81 bash?

[Jerry]

hi folks, happy new year btw.

got a simple questions from one of my customers who wants to run simple command each 12h every day of the year, that command is just killall wsdnsd but the important stuff is that it need to run every 12h precisely. I did try to use cron for it but seems it does not reoccur in the way what customer really wants. can you give me a simple hint on how to make it more reliable as well as how to avoid playing with this topic every time machine reboots (it occurs every few months anyway).

Cheers

[G_W_Albrecht]

sk77300: How to create a scheduled job (cron job) in Gaia with frequency of less than a day

[Jerry]

Cheers, I'll give them an option to try and come back to you with the outcome.

Thanks!

[G_W_Albrecht]

I tried in Lab - you can just paste killall wsdnsd in WebGUI ! You do not need sk77300 at all, look here:

So GAiA calls killall wsdnsd all 12 hours...

[Jerry]

done. Let's see if that works every time 🙂

[Wolfgang]

@Jerry would you please explain why to „kill“ the WSDNS daemon. I’m asking because we had an actual case with some problems with this daemon. And I‘m not really sure if these is needed if not using the gateway as proxy.

[Jerry]

sure I'm happy to explain.

my customer's R81 ClusterXL is running multistack ipv4/ipv6.

I used to rise that concerns with R&D some year ago or so but killall wsdnsd is the only way to bring the name-resolution on multistack back to normal. otherwise you end up with Alerts all over the logs (CLM logging) and in terms of a need - well I'm well aware we've had such cases in the past but apparently it wasn't fixed nor DNS resolution due to the complexity of the design changed hence that process 2 time per day is the really a "work around" at the moment. That's all 🙂

That Gateway isn't used as proxy at all. It is a SG which uses both FWD DNS resolutions - IPv4 & IPv6 at the very same time but DNS servers supporting both back to the SG gives such errors (alerts) every day when only killing the wsdnsd helps for literally the period of 8h no more. 3 times a day killing that process (restarting effectively) helps to eliminate such huge hunger for logging saving a lot of space on the CLM.

Hope it clears up the situation mate.

J.

[G_W_Albrecht]

Use cpwd_admin list; ps aux | grep -v grep | grep wsdnsd shortly before and after the scheduled time to verify.

[Jerry]

certainly a good option to verify the "workaround" solution. I only wonder why R81 still has issues with dual-stack networks ...

[_Val_]

What does support say about this?

[Jerry]

mostly blaming DNS server configuration and DNS setup of the SG but we've made a peace with that considering above workaround as the one viable option at the moment.

[_Val_]

Could you please PM me with the SR#?

[Jerry]

topic was that one Val

https://community.checkpoint.com/t5/General-Topics/Domain-resolving-error-Check-DNS-configuration-on...

SR No. I'm searching for so bear with me on that.

[Jerry]

when the killall wsdnsd is done, 1 min. afterwards you've got to see below in the logs. That says a lot about how DNSv6 processing works on Gaia 3.x R81. I've made that scheduler for every 2h as it seems that the daemon does not cope well and every 2h demands restart of its processes. This seems to me like a workaround anyway and I wonder what R&D could do in order to fix that finally in such old build like R81 😛 

[the_rock]

Good point, also tried it myself and it does work.