Opened 20 months ago
Closed 17 months ago
#815 closed defect (fixed)
DDNS (inadyn) unable to start
| Reported by: | bbowers | Owned by: | |
|---|---|---|---|
| Priority: | minor | Milestone: | |
| Component: | Backend | Version: | 8.0.2-RELEASE |
| Keywords: | inadyn, ddns | Cc: |
Description
Was working for me on i386 with RC1, just upgraded to RC2 and this is no longer working.
Sep 22 18:10:34 freenas freenas[1811]: Popen()ing: sysctl -b kern.geom.confxml
Sep 22 18:10:34 freenas freenas[1811]: Popen()ing: sysctl -b kern.geom.confxml
Sep 22 18:10:34 freenas freenas[1811]: Executing: /usr/sbin/service ix-inadyn quietstart
Sep 22 18:10:35 freenas freenas[1811]: Executing: /usr/sbin/service inadyn restart
Sep 22 18:10:35 freenas freenas: inadyn not running?
Sep 22 18:10:35 freenas freenas: Starting inadyn.
Sep 22 18:10:35 freenas freenas: /usr/local/bin/inadyn: 1: Syntax error: "(" unexpected
Sep 22 18:10:35 freenas root: /usr/local/etc/rc.d/inadyn: WARNING: failed to start inadyn
Sep 22 18:10:35 freenas freenas: /usr/local/etc/rc.d/inadyn: WARNING: failed to start inadyn
Sep 22 18:10:35 freenas freenas[1811]: Executing: /bin/pgrep inadyn
Change History (6)
comment:1 Changed 20 months ago by william
- Resolution set to duplicate
- Status changed from new to closed
comment:2 Changed 19 months ago by bbowers
- Keywords inadyn ddns added
- Resolution duplicate deleted
- Status changed from closed to reopened
- Summary changed from DDNS unable to start to DDNS (inadyn) unable to start
- Version changed from 8.0.1-RC2 to 8.0.2-RELEASE
Still receiving errors when using Dyndns or others on 8.0.2 release.
Oct 20 09:23:38 freenas freenas[1832]: Executing: /usr/sbin/service ix-inadyn quietstart
Oct 20 09:23:39 freenas freenas[1832]: Executing: /usr/sbin/service inadyn restart
Oct 20 09:23:39 freenas freenas: inadyn not running?
Oct 20 09:23:39 freenas freenas: Starting inadyn.
Oct 20 09:23:39 freenas freenas: /usr/local/bin/inadyn: 1: Syntax error: "(" unexpected
Oct 20 09:23:39 freenas root: /usr/local/etc/rc.d/inadyn: WARNING: failed to start inadyn
Oct 20 09:23:39 freenas freenas: /usr/local/etc/rc.d/inadyn: WARNING: failed to start inadyn
Oct 20 09:23:39 freenas freenas[1832]: Executing: /bin/pgrep inadyn
comment:3 Changed 19 months ago by dogfish
The problem appears to be that /usr/local/bin/inadyn is a SYSV binary not a FreeBSD binary, which fails to run (at least on my machine).
atg-tm# uname -a
FreeBSD atg-tm 8.2-RELEASE-p3 FreeBSD 8.2-RELEASE-p3 #5: Fri Sep 30 13:20:55 PDT 2011 jpaetzel@…:/b/sf_freenas_build/obj.i386/i386/b/sf_freenas_build/FreeBSD/src/sys/FREENAS.i386 i386
atg-tm# file /usr/local/bin/inadyn
/usr/local/bin/inadyn: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), stripped
atg-tm# /usr/local/etc/rc.d/inadyn start
Starting inadyn.
ELF binary type "0" not known.
/usr/local/bin/inadyn: 1: Syntax error: "(" unexpected
/usr/local/etc/rc.d/inadyn: WARNING: failed to start inadyn
comment:4 Changed 19 months ago by gcooper
Huh?
# cat /etc/version FreeNAS-8.2-r8607-amd64 # file /usr/local/bin/inadyn /usr/local/bin/inadyn: ELF 64-bit LSB executable, x86-64, version 1 (FreeBSD), dynamically linked (uses shared libs), for FreeBSD 8.2, stripped
# cat /etc/version TrueNAS-8.2-r3958M-amd64 # file /usr/local/bin/inadyn /usr/local/bin/inadyn: ELF 64-bit LSB executable, x86-64, version 1 (FreeBSD), dynamically linked (uses shared libs), for FreeBSD 8.2, stripped
comment:5 Changed 19 months ago by dogfish
This is a i386 machine not an x64 machine (see uname -a output).
[atg-tm ~]$ cat /etc/version.freenas
FreeNAS-8.0.2-RELEASE-i386 (8288)
[atg-tm ~]$ file /usr/local/bin/inadyn
/usr/local/bin/inadyn: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), stripped
comment:6 Changed 17 months ago by gcooper
- Resolution set to fixed
- Status changed from reopened to closed
Someone on the forums [1] claimed that DDNS works in '8.0.3-RC1', so it was most likely build environment tainting that was causing issues here.
Marking fixed.

Just wondering, you had already commented on #737 which has the same issue described here, why did you open another ticket for it?
Closing it, marking duplicated of #737.