Signature version reverted back to 2.066 again - this time factory resets are not resolving it

[Ceejus]

Was on signature version 2.274 from 1/20/22. Went to go check for a signature update today, was updating to what I'm guessing is either 2.276 or 2.278, said the update completed, but is now showing the version at 2.066. This happened once before and a factory reset got the signature updating properly again. This time that is not the case.

The logs read the same as they did last time this happened:

Feb 8 01:42:52 rc_service: httpd 1349:notify_rc start_sig_check
Feb 8 01:42:54 rc_service: rc 7064:notify_rc restart_wrs
Feb 8 01:42:54 rc_service: waitting "start_sig_check" via httpd ...
Feb 8 01:43:09 rc_service: skip the event: restart_wrs.
Feb 8 01:43:11 kernel: *** ERROR: [tdts_shell_ioctl_sig_op_load:95] tdts_core_rule_parsing_trf_load() fail!
Feb 8 01:43:11 BWDPI: fun bitmap = 4ff

Am using a GT-AC2900 with official ASUSWRT firmware. Am I pretty much SOL with signature updates moving forward? A couple of threads seemed to indicate there may be some things that can be done if using Merlin. I suppose I would be willing to make the switch if that is really necessary.

 

[saleanddeki]

Same situation, AX56U, Merlin 386.4 and 386.5 alpha 1. Latest version is 2.278.

 

[emizzle]

Noticed the same, RT-AX88U, factory firmware 3.0.0.4.386_46065-ge51f2dc, showing signature version at 2.066, seeing the same issue in the logs:

Feb  8 22:35:50 rc_service: httpds 1596:notify_rc start_sig_check
Feb  8 22:35:53 rc_service: rc 9895:notify_rc restart_wrs
Feb  8 22:35:53 rc_service: waitting "start_sig_check" via httpds ...
Feb  8 22:36:08 rc_service: skip the event: restart_wrs.
Feb  8 22:36:09 kernel:  *** ERROR: [tdts_shell_ioctl_sig_op_load:95] tdts_core_rule_parsing_trf_load() fail!
Feb  8 22:36:09 BWDPI: fun bitmap = 5ff
Feb  8 22:36:09 A.QoS: qos_count=0, qos_check=0

Forcing a signature check (via the "check" button) triggers the above in the syslog.

 

[bbunge]

System problem. Nothing you did to your router. We all will have to wait for it to be fixed.

 

[bbunge]

Signature version updated successfully overnight. 2.274 reported.

 

[Ceejus]

Thanks all. Was just able to manually update to 2.280. I figured based on these comments the next version would be 2.280.

 

[Wallace_n_Gromit]

2.280 Updated : 2022/02/09 11:04
2.274 Updated : 2022/02/08 02:01
2.274 Updated : 2022/01/20 02:00

dunno why my router "updated" to the same version of the signature, but when I tried a manual update, updated to 2.280

Regarding apparent signature reversion to 2.066. I seem to recall (in some prior posts -- possibly/typically by @ColinTaylor ) that even though the GUI seems to indicate what signature you are on, a [certain] command in ssh can actually reveal the signature version that is actually on the router.

Spent a very short time looking for post(s) mentioning this, but haven't found anything. Maybe, someone actually knows the command prompt command?

 

[L&LD]

This is an issue on Asus' end (or, Trend Micro).

When they finally put the correct files in the links that they were supposed to be at, everything works.

 

[Clark Griswald]

I rarely check the TM signature date.
All of the Trend Micro stuff is "closed", so when there has been an issue in the past, best to wait until TM/Asus fix the issues.