Diversion not starting after reboot

[BSOD2600]

RT-AC87U on 384.9.
Diversion 4.0.7

I've got weekly reboots of the router enabled. Ever since updating to 384.9, Diversion+pixelserv will not start up after the reboot. If I ssh to the router, launch diversion, and then enable it, it works just fine for another week. already tried a force reinstall of diversion.

Ideas?

syslog has these bits about the services

Feb 24 04:02:50 192.168.1.1 Feb 24 04:02:49 Diversion: pixelserv-tls or Diversion disabled, not starting pixelserv-tls, from /opt/etc/init.d/S80pixelserv-tls
Feb 24 04:02:50 192.168.1.1 Feb 24 04:02:49 Diversion: started Entware services, from /jffs/scripts/post-mount
Feb 24 04:02:56 192.168.1.1 Feb 24 04:02:54 Diversion: is disabled, no services enabled, from /jffs/scripts/dnsmasq.postconf
<manual start>
Feb 24 07:07:17 192.168.1.1 Feb 24 07:07:15 Diversion: created br0:pixelserv-tls 192.168.1.11, from /opt/etc/init.d/S80pixelserv-tls
Feb 24 07:07:17 192.168.1.1 Feb 24 07:07:15 pixelserv-tls[8340]: pixelserv-tls 2.1.2 (compiled: Sep  8 2018 20:33:38) options: 192.168.1.11
Feb 24 07:07:17 192.168.1.1 Feb 24 07:07:15 Entware (armv7sf-k2.6): Started pixelserv-tls (Diversion) from /opt/bin/diversion
Feb 24 07:07:20 192.168.1.1 Feb 24 07:07:18 pixelserv-tls[8340]: Listening on :192.168.1.11:443
Feb 24 07:07:20 192.168.1.1 Feb 24 07:07:18 pixelserv-tls[8340]: Listening on :192.168.1.11:80
Feb 24 07:07:20 192.168.1.1 Feb 24 07:07:18 Diversion: restarted Dnsmasq to apply settings, from /jffs/scripts/dnsmasq.postconf

admin@RT-AC87U:/tmp/home/root# cat /jffs/scripts/dnsmasq.postconf
#!/bin/sh

. /opt/share/diversion/file/post-conf.div # Added by Diversion

 

[L&LD]

Is your USB drive corrupted by any chance? Are you using amtm? Do you have the disk checker installed? After a reboot, what is it reporting on the drive? Do you have a swapfile installed (not a swap partition)?

Have you any other customizations on your router? Did you let Diversion install Entware and pixelserv-tls?

When updating to 384.9, what version were you coming from? When was the last time you did a full reset to factory defaults after flashing to a new firmware followed by a minimal and manual install?

 

[BSOD2600]

USB drive I dont think is corrupt.. at least the built in disk checking tool doesnt state there are any errors.
No amtm.
Swap file is installed on USB.
No other customization. Yes, let entware and pixelserv be installed.
Came from 384.7_2 to 384.9. hmm, full factory rest I had to do before could successfully upgrade to 384.9... and then used the forum's nvram-save to put back the settings.

 

[L&LD]

USB drive I dont think is corrupt.. at least the built in disk checking tool doesnt state there are any errors.
No amtm.
Swap file is installed on USB.
No other customization. Yes, let entware and pixelserv be installed.
Came from 384.7_2 to 384.9. hmm, full factory rest I had to do before could successfully upgrade to 384.9... and then used the forum's nvram-save to put back the settings.

That is your issue right there, I think. If you used john9527's old NVRAM save/restore utility...

That stopped working on the 380 branch if I'm not mistaken. For sure it doesn't work with the latest firmware.

And you need to do a full restore to factory defaults after flashing the firmware you want to use.

See the links below to get your router working again.

 

[BSOD2600]

That is your issue right there, I think. If you used john9527's old NVRAM save/restore utility...

Correct.

So those of us who have custom settings on nearly every page, what is the efficient way of saving and restoring those? Taking screenshots and manually setting them is super inconvenient. My static DHCP table has at least 30 entries alone. I'm more inclined to waste an hour with a full reset if there are clear signs of corruption vs a hypothesis.



Back to the root of the problem, on how to further troubleshoot why Diversion is not starting on boot?

 

[L&LD]

I'm more inclined to waste an hour with a full reset if there are clear signs of corruption vs a hypothesis.

Back to the root of the problem, on how to further troubleshoot why Diversion is not starting on boot?

The fact that Diversion is not starting is your clear sign. Nobody else has reported a similar issue, afaik.

By using the NVRAM save/restore utility you have effectively trashed your router's firmware. Only a clean reset and manual configuration will fix what you did now.

If by any chance you get Diversion to boot up, it doesn't discount anything I've stated above. It is simply another glitch that may have further implications down the road.

Save your time and the time of other posters here and simply reset the router to a known/good state. As that is the main and biggest issue you have right now.