23.01.r.20230202.1645 re-sends e-mail notification for DynDNS WAN IP change every 15 seconds

[mfld]

23.01.r.20230202.1645 with DynDNS package.

WAN interface has uptime since boot. WAN IPv6 address is unchanged the entire time since boot.

DynDNS Package has verbose logging enabled. Log shows no repeated DynDNS updates.

Telegram and Pushover notifications are also enabled alongside SMTP - These are NOT replicated. They fire once when appropriate and do not repeat.

System log shows every 15 seconds:

<11>1 2023-02-06T18:00:12.886665+00:00 pfsense.home.arpa php-cgi 3431 - - notify_monitor.php: Message sent to hostmaster@mfld.net OK
<11>1 2023-02-06T18:00:27.294581+00:00 pfsense.home.arpa php-cgi 3431 - - notify_monitor.php: Message sent to hostmaster@mfld.net OK
<11>1 2023-02-06T18:00:42.005435+00:00 pfsense.home.arpa php-cgi 3431 - - notify_monitor.php: Message sent to hostmaster@mfld.net OK

RIP Inbox :

login-to-view

You can see in the e-mail subject line that it's referring to the same event, the only timestamp showing there is 15:11:38 so it seems to not be related to the dyndns package doing too many updates or a false positive on WAN IP change. Seems to be whatever fires the SMTP notification thinks it did not work out and needs to be re-done. But the system log clearly shows "Message sent to hostmaster@mfld.net OK"

[mfld]

@mfld I disabled SMTP notifications and applied the change.

login-to-view

But it still keeps emailing every 15 seconds!

I will reboot to end this lunacy

[jimp]

That would seem to indicate that it's having a problem removing or emptying the message file /var/db/notices_lastmsg.txt. Maybe something is holding that open.

First, go to a console menu and use options 16 and 11 to reset PHP and the GUI, then rm /var/db/notices_lastmsg.txt and see if it stops.

[dennypage]

@jimp Just ran into this myself with a watchdog report.

I took the following steps:

• console option 16
• console option 11
• rm /var/db/notices_lastmsg.txt

This did not stop the emails. I had to reboot to get it to stop.

I did receive a PHP error report:

[08-Feb-2023 10:00:04 PST8PDT] PHP Fatal error:  Uncaught TypeError: fwrite(): Argument #1 ($stream) must be of type resource, bool given in /etc/inc/config.lib.inc:172
Stack trace:
#0 /etc/inc/config.lib.inc(172): fwrite(false, 'a:47:{s:7:"vers...')
#1 /etc/inc/config.lib.inc(147): generate_config_cache(Array)
#2 /etc/inc/config.inc(141): parse_config()
#3 /etc/inc/gwlb.inc(25): require_once('/etc/inc/config...')
#4 /etc/inc/functions.inc(35): require_once('/etc/inc/gwlb.i...')
#5 /etc/inc/notices.inc(26): require_once('/etc/inc/functi...')
#6 /usr/local/pkg/nut/nut_email.php(24): require_once('/etc/inc/notice...')
#7 {main}
  thrown in /etc/inc/config.lib.inc on line 172
[08-Feb-2023 10:00:04 PST8PDT] PHP Fatal error:  Uncaught ValueError: Path cannot be empty in /etc/inc/notices.inc:101
Stack trace:
#0 /etc/inc/notices.inc(101): fopen('', 'w')
#1 /etc/inc/config.lib.inc(1162): file_notice('phperror', 'PHP ERROR: Type...', 'PHP errors')
#2 [internal function]: pfSense_clear_globals()
#3 {main}
  thrown in /etc/inc/notices.inc on line 101