On Fri, May 16, 2025 at 1:12 PM <[email protected]> wrote: > Moin, > > > > ich probiere mich gerade an inadyn. > > > > Per cmd-line funktioniert es, also service nicht…. > > > > inadyn -l 10 -n -1 -f /etc/inadyn.conf > > inadyn[1605265]: In-a-dyn version 2.10.0 -- Dynamic DNS update client. > > inadyn[1605265]: Cached IP# 84.165.63.18 for xxxx from previous > invocation. > > inadyn[1605265]: Last update of xxxx on Fri May 16 18:52:21 2025 > > inadyn[1605265]: Get address for custom > > inadyn[1605265]: Starting command to get my public IP#: > INADYN_PROVIDER="custom" INADYN_USER="xxx" /usr/local/sbin/getip-fritzbox > > inadyn[1605265]: Command 'INADYN_PROVIDER="custom" INADYN_USER="xxx" > /usr/local/sbin/getip-fritzbox' returns 13 bytes > > inadyn[1605265]: Command response: > > inadyn[1605265]: 84.165.63.18 > > inadyn[1605265]: Checking IPv4 address 84.165.63.18 ... > > inadyn[1605265]: IPv4 address 84.165.63.18 is valid. > > inadyn[1605265]: No IP# change detected for custom, still at 84.165.63.18 > > > > > > als service passiert das: > > > > systemctl status inadyn.service > > ● inadyn.service - LSB: DynDNS client > > Loaded: loaded (/etc/init.d/inadyn; generated) > > Active: active (exited) since Fri 2025-05-16 18:55:59 CEST; 6s ago > > Docs: man:systemd-sysv-generator(8) > > Process: 1605685 ExecStart=/etc/init.d/inadyn start (code=exited, > status=0/SUCCESS) > > CPU: 26ms > > > > Mai 16 18:55:59 mailsrv01 systemd[1]: Starting inadyn.service - LSB: > DynDNS client... > > Mai 16 18:55:59 mailsrv01 inadyn[1605690]: In-a-dyn version 2.10.0 -- > Dynamic DNS update client. > > Mai 16 18:55:59 mailsrv01 inadyn[1605685]: Starting DynDNS client : inadyn. > >
> Mai 16 18:55:59 mailsrv01 inadyn[1605690]: Cannot read configuration file > /etc/inadyn.conf > > Mai 16 18:55:59 mailsrv01 inadyn[1605690]: Error code 74: Missing .conf > file > According to the errors listed above you are missing a configuration file: /etc/inadyn.conf. This could be a permissions issue or it could be a configuration issue. Try `sudo ls -l /etc/inadyn.conf`. If the file exists then it should list the file and its permissions. Then try `sudo ls -l /etc | grep inadyn` If no file exists then it might be a configuration issue. Try checking the systemd configuration file: `sudo cat /usr/lib/systemd/system/inadyn.service` Check the `ExecStart=` settings to see what config files are referenced. If the configuration is indeed seeking a /etc/inadyn.conf file but none exists and there has not been a configuration update placing the config file into the inadyn directory then you can issue a: `sudo touch /etc/inadyn.conf` This will create a blank file which should make the error messages go away. You will have to lookup the settings commands to configure the file. Tim Mai 16 18:55:59 mailsrv01 systemd[1]: Started inadyn.service - LSB: DynDNS > client. > > > > Was mache ich falsch…. > -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/ ⠈⠳⣄⠀⠀
