Question about Trend Micro Signature "update failed"

  • ATTENTION! As of November 1, 2020, you are not able to reply to threads 6 months after the thread is opened if there are more than 500 posts in the thread.
    Threads will not be locked, so posts may still be edited by their authors.
    Just start a new thread on the topic to post if you get an error message when trying to reply to a thread.

Wayne Hutchinson

Occasional Visitor
upload_2020-6-21_7-51-39.png


I am using latest stable release RT-5300_384-17 but have noticed the following error about Trend Micro.

I like to enable AiProtection and the last update is 11/28/2019 and if I try to update I get this error.

How to update??

Rew
 

dave14305

Part of the Furniture
Try logging in over SSH and running these commands to see if any hints are there (post the output):
Code:
cat /tmp/sig_upgrade.log
ls -l /jffs/signature/
df /jffs
date
nslookup dlcdnets.asus.com
 

Wayne Hutchinson

Occasional Visitor
OK, I tried this but I got this "ssh: connect to host 192.168.1.1 port 22: Connection refused"
I used my IP and login name for the Asus, what about password?

Thanks
 

dave14305

Part of the Furniture
OK, I tried this but I got this "ssh: connect to host 192.168.1.1 port 22: Connection refused"
I used my IP and login name for the Asus, what about password?

Thanks
It’s the same User/Password as when you login via a browser. But first you have to enable SSH on the Administration / System tab in the webui.
 

dave14305

Part of the Furniture
Does this look right
Download sig info Failure, return_code : 2
[email protected]:/tmp/home/root# ls -l /jffs/signature/
-rw-rw-rw- 1 Rew452 root 992139 Nov 27 2019 rule.trf
[email protected]:/tmp/home/root# df /jffs
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/mtdblock4 65536 3436 62100 5% /jffs
[email protected]:/tmp/home/root# date
Sun Jun 21 09:53:37 DST 2020
How about the last command?
nslookup dlcdnets.asus.com
 

EmeraldDeer

Very Senior Member
The important part of an nslookup is the reply
Code:
# nslookup dlcdnets.asus.com
Server:    127.0.0.1
Address 1: 127.0.0.1 localhost.localdomain

Name:      dlcdnets.asus.com
Address 1: 152.199.24.41
Here is how dnsmasq responded to the nslookup
Code:
Jun 21 10:21:19 dnsmasq[25138]: 86796 127.0.0.1/52277 query[A] dlcdnets.asus.com from 127.0.0.1
Jun 21 10:21:19 dnsmasq[25138]: 86796 127.0.0.1/52277 forwarded dlcdnets.asus.com to 127.0.1.1
Jun 21 10:21:19 dnsmasq[25138]: 86797 127.0.0.1/52277 query[AAAA] dlcdnets.asus.com from 127.0.0.1
Jun 21 10:21:19 dnsmasq[25138]: 86797 127.0.0.1/52277 forwarded dlcdnets.asus.com to 127.0.1.1
Jun 21 10:21:19 dnsmasq[25138]: 86796 127.0.0.1/52277 reply dlcdnets.asus.com is <CNAME>
Jun 21 10:21:19 dnsmasq[25138]: 86796 127.0.0.1/52277 reply wideip-dlcdnets.isoi.asia is <CNAME>
Jun 21 10:21:19 dnsmasq[25138]: 86796 127.0.0.1/52277 reply cs956197766.wpc.psicdn.net is 152.199.24.41
Jun 21 10:21:19 dnsmasq[25138]: 86797 127.0.0.1/52277 reply dlcdnets.asus.com is <CNAME>
Jun 21 10:21:19 dnsmasq[25138]: 86797 127.0.0.1/52277 reply wideip-dlcdnets.isoi.asia is <CNAME>
Jun 21 10:21:19 dnsmasq[25138]: 86797 127.0.0.1/52277 reply cs956197766.wpc.psicdn.net is NODATA-IPv6
Here is the same lookup but direct to Comcast DNS
Code:
# nslookup dlcdnets.asus.com 75.75.75.75
Server:    75.75.75.75
Address 1: 75.75.75.75 cdns01.comcast.net

Name:      dlcdnets.asus.com
Address 1: 152.199.24.41
 

dave14305

Part of the Furniture
[email protected]:/tmp/home/root# nslookup dlcdnets.asus.com
Server: 75.75.75.75
Address 1: 75.75.75.75 cdns01.comcast.net
I run the same command (also Xfinity) and get this:
Code:
# nslookup dlcdnets.asus.com
Server:    75.75.75.75
Address 1: 75.75.75.75 cdns01.comcast.net

Name:      dlcdnets.asus.com
Address 1: 152.199.24.41
So why doesn’t Comcast let you resolve the name?

Test a different name:
Code:
nslookup www.snbforums.com
Server:    75.75.75.75
Address 1: 75.75.75.75 cdns01.comcast.net

Name:      www.snbforums.com
Address 1: 2606:4700:20::681a:942
Address 2: 172.67.69.81
Address 3: 104.26.8.66
Address 4: 104.26.9.66
Also test a different server:
Code:
nslookup dlcdnets.asus.com 9.9.9.9
 

dave14305

Part of the Furniture
Ok. How about running this?
Code:
wget https://dlcdnets.asus.com/pub/ASUS/LiveUpdate/Release/Wireless/sig2nd_update.zip -O -
So are you saying Comcast is not letting me access because it is not resolving Asus dns
Well the original output you provided didn’t show the response. The last output did, so maybe not the issue.
 
Last edited:

dave14305

Part of the Furniture
this is what I get
--2020-06-21 10:52:40-- https://dlcdnets.asus.com/pub/ASUS/LiveUpdate/Release/Wireless/sig2nd_update.zip
Resolving dlcdnets.asus.com... 152.199.24.41
Connecting to dlcdnets.asus.com|152.199.24.41|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 41 [application/zip]
Saving to: 'STDOUT'
I get more output than you.
Code:
wget https://dlcdnets.asus.com/pub/ASUS/LiveUpdate/Release/Wireless/sig2nd_update.zip -O -
--2020-06-21 10:54:20--  https://dlcdnets.asus.com/pub/ASUS/LiveUpdate/Release/Wireless/sig2nd_update.zip
Resolving dlcdnets.asus.com... 152.199.24.41
Connecting to dlcdnets.asus.com|152.199.24.41|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 41 [application/zip]
Saving to: 'STDOUT'

-                            0%[                                       ]       0  --.-KB/s               WW_FULL#2.182
WW_PART#2.182
WW_WRS#2.182
-                          100%[======================================>]      41  --.-KB/s    in 0s     

2020-06-21 10:54:21 (133 KB/s) - written to stdout [41/41]
 

Wayne Hutchinson

Occasional Visitor
sorry, I missed some
[email protected]:/tmp/home/root# wget https://dlcdnets.asus.com/pub/ASUS/LiveUpdate/Release/Wireless/sig2nd_update.
zip -O -
--2020-06-21 10:59:21-- https://dlcdnets.asus.com/pub/ASUS/LiveUpdate/Release/Wireless/sig2nd_update.zip
Resolving dlcdnets.asus.com... 152.199.24.41
Connecting to dlcdnets.asus.com|152.199.24.41|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 41 [application/zip]
Saving to: 'STDOUT'
- 0%[ ] 0 --.-KB/s WW_FULL#2.182
WW_PART#2.182
WW_WRS#2.182
- 100%[=================================================>] 41 --.-KB/s in 0s
 

dave14305

Part of the Furniture
Seems all the pieces are there.
Try running:
Code:
sh -x /usr/sbin/sig_update.sh
Edit: got confused on the file name after looking at github.
 
Last edited:

Wayne Hutchinson

Occasional Visitor
OK this is what I got
[email protected]:/tmp/home/root# sh -x /usr/sbin/sig_update.sh
+ nvram get apps_wget_timeout
+ wget_timeout=3O
+ wget_options=-q -t 2 -T 3O
+ nvram set sig_state_update=0
+ nvram set sig_state_flag=0
+ nvram set sig_state_error=0
+ nvram get rc_support
+ grep -i nt_center
+ IS_SUPPORT_NOTIFICATION_CENTER=
+ [ != ]
+ nvram get bwdpi_sig_ver
+ current_sig_ver=2.152
+ echo 2.152
+ sed s/\.//g
+ current_sig_ver=2152
+ echo 2152
2152
+ echo 2152
+ nvram get sig_type
+ sig_type=FULL
+ [ FULL == ]
+ nvram get apps_sq
+ forsq=
+ nvram get territory_code
+ tcode=US/06
+ [ US/06 == ]
+ territory_type=US/06_FULL
+ [ == 1 ]
+ echo ---- sig update real normal----
+ wget -q -t 2 -T 3O https://dlcdnets.asus.com/pub/ASUS/LiveUpdate/Release/Wireless/sig2nd_update.zip -O /tmp/sig_update.txt
wget: --timeout: Invalid time period '3O'
+ r=2
+ [ 2 != 0 ]
+ echo Download sig info Failure, return_code : 2
Download sig info Failure, return_code : 2
+ echo Download sig info Failure, return_code : 2
+ nvram set sig_state_error=1
+ nvram get sig_state_info
+ update_sig_state_info=2152
+ nvram get sig_last_info
+ last_sig_state_info=
+ [ == ]
+ nvram set sig_state_error=1
+ nvram set sig_state_update=1
 

Similar threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top