Dynamic DNS (inadyn) fails to start after update to 12.0 U5

[invar]

******** The U6 update is out with the fix. Woohoo ********



Updated from TrueNAS Core 12.0-U4.1 to U5 and dynamic DNS service now fails to start. The following error is logged to /var/log/messages:

"inadyn 6689 - - Error code 31: System has no trusted CA store"

Reverted my boot back to 12.0-U4.1 and it starts right up again.

Inadyn.conf as follows:

Code:

period = 300

custom customProvider {

    ddns-server = "MYCUSTOMDDNSSERVICE.com"

    ddns-path = "/myddnspath?domain="

    ssl = true

    checkip-server = "checkip.dyndns.com"

    checkip-ssl = "false"

    username = "MYUSER"

    password = 'MYPASS'

    hostname = { "myhost.mydomain.com" }

    ddns-response = "ipv4:"

}

Seems like inadyn 2.5 is failing to detect the correct location of the file (/etc/ssl/cert.pem?)

Inadyn v2.8.1 has support for a "ca-trust-file" configuration option but we are only on v2.5 unfortunately.

Inadyn: man/inadyn.conf.5 | Fossies

inadyn.conf manual page - inadyn DDNS client configuration file

fossies.org

Anyone else experiencing this?

 

[juhny]

Yes, I have same error. So reverting back to U4.1 is the only way to fix error?

 

[invar]

Yes, I have same error. So reverting back to U4.1 is the only way to fix error?

I haven't explored any other options yet, reverting was the quickest solution for me.

 

[cobrakiller58]

same problem here reported the bug.

https://jira.ixsystems.com/browse/NAS-111704

looks like filing the report crashed my server lmao

EDIT: yup filing the bug report caused
had an unscheduled system reboot. The operating system successfully came back online at Fri Aug 6 10:55:26 2021

 

[muaijaz]

Same issue here.
15637 - - Error code 31: System has no trusted CA store
Aug 8 15:03:15 truenas 1 2021-08-08T15:03:15.306660-05:00 truenas.local inadyn

 

[muaijaz]

Bump because same issue. Submitted my debug file as well.

 

[cobrakiller58]

Problem appears to have been fixed https://jira.ixsystems.com/browse/NAS-111735 to release with U6

 

[invar]

Thanks for the update. Didn't feel like waiting for U6 to drop, so I compiled a port of inadyn 2.8.1 in one of my test jails with the correct options and have a startup script on my TrueNAS server replace the inadyn executable during startup. Not the prettiest or recommended, but DDNS works for me now on U5.

 

[albertredneck]

Is there any simple workaround for this (like rollback version or modifying the /usr/local/etc/rc.d/inadyn)? I have no experience with FreeBSD, I'd appreciate any help.

I'm out in vacations and I managed to fix my access checking my last IP from google devices registry :D, but if my IP changes again while I'm out I'm toast!

 

[hax0rjax]

+1 on albertredneck's post
Anyone have any docs or guides to have a work around? I'm also a FreeBSD newbie, as well as a TrueNas newb.

 

[invar]

Might want to just go back to U4 unless you need the bug fixes or enhancements that U5 or U5.1 offer.

I don't think my workaround is the recommended method

 

[BloP]

For who can't wait fo the next update. This is what i did.
Created a default jail with NAT. named it inadyn
ssh to TrueNAS

jls

look for the jailnumber with the new created jail

jexec [jailnumber] tcsh

now you are in the jail shell and need to install pkg

pkg

accept it, same for the next (https://www.freebsd.org/cgi/man.cgi...tion=8&manpath=FreeBSD+11-current&format=html)

pkg install dns/inadyn

now we need to config the service, we need to edit inadyn.conf located in /usr/local/etc.
There for you can compare the old config on truenas and with (ee use [ESC] for exit and save)

ee /usr/local/etc/inadyn.conf

and past it in the inadyn.conf in the new created jail. check the brackets, on my first run i missed one ;)
Inadyn comes also with rc.d script, to enable it we need to edit rc.conf and add inady_enable="YES"

ee /etc/rc.conf

inady_enable="YES"

now, inadyn will start with the system but is still not running, to start it

service inadyn start

with

service inadyn status

you can verify it or restart the jail with [shutdown -r now]

cat /var/log/messages

to see if inadyn is working properly

 

[YeahThatsTrue]

Just wanted to confirm that this problem still exists as of version 12.0-U5.1 and that @BloP's solution works perfectly. I think the only thing worth mentioning is I added inadyn_enable="YES" (note the n) to /etc/rc.conf, not inady_enable="YES".

Also, to the other beginners out there, you can check the version of TrueNAS you're running by going to System > Support.

 

[invar]

U6 is out with the fix, woohoo.

 

[Frog]

U6 is out with the fix, woohoo.

I'm running U6 and am encountering this same issue. :(