Project

General

Profile

Bug #44947

Add --continue-on-error for inadyn to prevent it from exiting on error

Added by Bug Clerk 8 months ago. Updated 3 months ago.

Status:
Done
Priority:
No priority
Assignee:
Vladimir Vinogradenko
Category:
Middleware
Target version:
Severity:
New
Reason for Closing:
Reason for Blocked:
Needs QA:
No
Needs Doc:
No
Needs Merging:
No
Needs Automation:
No
Support Suite Ticket:
n/a
Hardware Configuration:
ChangeLog Required:
No

Description

While working ticket 41395, changed password for DDNS service, the inadyn.conf file is not updating after 1st set-up.


Related issues

Related to FreeNAS - Bug #41395: Properly encode passwords in inadyn configDone
Related to FreeNAS - Bug #44958: Fix bug that prevented update to DDNS configurationDone
Copied from FreeNAS - Bug #44900: Add --continue-on-error for inadyn to prevent it from exiting on errorDone

History

#1 Updated by Bug Clerk 8 months ago

  • Copied from Bug #44900: Add --continue-on-error for inadyn to prevent it from exiting on error added

#2 Updated by Bug Clerk 8 months ago

  • Target version changed from Master - FreeNAS Nightlies to TrueNAS 11.1-U6.2

#3 Updated by Bug Clerk 8 months ago

  • Status changed from Unscreened to In Progress

#4 Updated by Bug Clerk 7 months ago

  • Status changed from In Progress to Ready for Testing

#5 Updated by Dru Lavigne 6 months ago

  • Subject changed from inadyn.conf File Not Updating to Add --continue-on-error for inadyn to prevent it from exiting on error
  • Needs Doc changed from Yes to No
  • Needs Merging changed from Yes to No

#6 Updated by Dru Lavigne 6 months ago

  • Related to Bug #41395: Properly encode passwords in inadyn config added

#7 Updated by Dru Lavigne 6 months ago

  • Related to Bug #44958: Fix bug that prevented update to DDNS configuration added

#8 Updated by Dru Lavigne 5 months ago

  • Target version changed from TrueNAS 11.1-U6.2 to 11.1-U7

#11 Updated by Jeff Ervin 4 months ago

  • Status changed from Ready for Testing to Failed Testing

Test Failed FreeNAS-11.1-U7-INTERNAL1

Test case followed. Used No-IP.com for Dynamic DNS Service. Under Dynamic DNS services, info entered and password entered/confirmed. Service started. Re-entered service settings, put in a different password, service stopped.

#12 Updated by Bonnie Follweiler 4 months ago

Test failed in FreeNAS-11.1-U7-INTERNAL1

#13 Updated by Vladimir Vinogradenko 4 months ago

  • Status changed from Failed Testing to Blocked
  • Reason for Blocked set to Waiting for feedback

Jeff, please attach a debug, I am not able to repeat this

#14 Updated by Jeff Ervin 4 months ago

  • File debug-freenas-20190109093715.tgz added

#15 Updated by Jeff Ervin 4 months ago

  • Private changed from No to Yes

#16 Updated by Jeff Ervin 4 months ago

  • File debug-fn01-20190109075158.tgz added

Different system...new debug file for you Vlad.

#17 Updated by Vladimir Vinogradenko 4 months ago

  • Status changed from Blocked to Ready for Testing
  • Reason for Blocked deleted (Waiting for feedback)

Note: please do the testing on 11.1 when DynamicDNS service is enabled for auto-start. It's a known bug in 11.1 that some services are stopping when they are not enabled and we update their configuration (this also happens with e.g. SNMP)

In 11.2 or 11.3 everything should work as expected when both service is enabled or disabled

#18 Updated by Jeff Ervin 3 months ago

  • Status changed from Ready for Testing to Passed Testing
  • Needs QA changed from Yes to No

Test Passed FreeNAS-11.1-U7-INTERNAL2

Enabled "Start on Boot" and followed test case and instructions laid out by Vlad. Service remains on.

#19 Updated by Dru Lavigne 3 months ago

  • File deleted (debug-freenas-20190109093715.tgz)

#20 Updated by Dru Lavigne 3 months ago

  • File deleted (debug-fn01-20190109075158.tgz)

#21 Updated by Dru Lavigne 3 months ago

  • Status changed from Passed Testing to Done
  • Private changed from Yes to No

Also available in: Atom PDF