What's new

Let's Encrypt stuck on updating on my AC86U

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

J.T.

Occasional Visitor
Hi, per the subject, any ideas on how to fix? Let me know what you all need to help troubleshoot. :)

upload_2020-3-28_17-54-46.png
 
Mar 28 18:01:38 rc_service: httpd 975:notify_rc restart_ddns_le
Mar 28 18:01:38 start_ddns: update WWW.ASUS.COM dyndns, wan_unit 0
Mar 28 18:01:38 ddns update: ez-ipupdate: starting...
Mar 28 18:01:38 ddns update: asus_private() interface =eth0
Mar 28 18:01:38 ddns update: g_asus_ddns_mode == 2
Mar 28 18:01:39 ddns update: connected to nwsrv-ns1.asus.com (103.10.4.108) on port 443.
Mar 28 18:01:39 ddns update: Asus update entry:: return: HTTP/1.1 200 OK^M Date: Sat, 28 Mar 2020 22:01:39 GMT^M Server: Apache^M X-Powered-By: PHP/5.6.30^M Content-Length: 0^M Connection: close^M Content-Type: text/html; charset=UTF-8^M ^M
Mar 28 18:01:39 ddns update: retval= 0, ddns_return_code (,200)
Mar 28 18:01:39 ddns update: asusddns_update: 0
Mar 28 18:01:39 ddns: ddns update ok
Mar 28 18:01:39 ddns update: exit_main
Mar 28 18:01:39 kernel: /usr/sbin/acme.sh: line 1: can't create /jffs/.le/account.conf: No space left on device
Mar 28 18:01:39 kernel: mkdir: can't create directory '/jffs/.le/xxxxxxxxxxx.asuscomm.com': No space left on device
Mar 28 18:01:40 kernel: touch: /jffs/.le/xxxxxxxxxxx.asuscomm.com/xxxxxxxxxxx.asuscomm.com.conf: No such file or directory
Mar 28 18:01:40 kernel: grep: /jffs/.le/xxxxxxxxxxx.asuscomm.com/xxxxxxxxxxx.asuscomm.com.conf: No such file or directory
Mar 28 18:01:40 kernel: grep: /jffs/.le/xxxxxxxxxxx.asuscomm.com/xxxxxxxxxxx.asuscomm.com.conf: No such file or directory
Mar 28 18:01:40 kernel: /usr/sbin/acme.sh: line 3: can't create /jffs/.le/xxxxxxxxxxx.asuscomm.com/xxxxxxxxxxx.asuscomm.com.conf: nonexistent directory
Mar 28 18:01:40 kernel: grep: /jffs/.le/xxxxxxxxxxx.asuscomm.com/xxxxxxxxxxx.asuscomm.com.conf: No such file or directory
Mar 28 18:01:40 kernel: touch: /jffs/.le/xxxxxxxxxxx.asuscomm.com/xxxxxxxxxxx.asuscomm.com.conf: No such file or directory
Mar 28 18:01:40 kernel: grep: /jffs/.le/xxxxxxxxxxx.asuscomm.com/xxxxxxxxxxx.asuscomm.com.conf: No such file or directory
Mar 28 18:01:40 kernel: grep: /jffs/.le/xxxxxxxxxxx.asuscomm.com/xxxxxxxxxxx.asuscomm.com.conf: No such file or directory
Mar 28 18:01:40 kernel: /usr/sbin/acme.sh: line 3: can't create /jffs/.le/xxxxxxxxxxx.asuscomm.com/xxxxxxxxxxx.asuscomm.com.conf: nonexistent directory
Mar 28 18:01:40 kernel: grep: /jffs/.le/xxxxxxxxxxx.asuscomm.com/xxxxxxxxxxx.asuscomm.com.conf: No such file or directory
Mar 28 18:01:40 kernel: touch: /jffs/.le/xxxxxxxxxxx.asuscomm.com/xxxxxxxxxxx.asuscomm.com.conf: No such file or directory
Mar 28 18:01:40 kernel: grep: /jffs/.le/xxxxxxxxxxx.asuscomm.com/xxxxxxxxxxx.asuscomm.com.conf: No such file or directory
Mar 28 18:01:40 kernel: grep: /jffs/.le/xxxxxxxxxxx.asuscomm.com/xxxxxxxxxxx.asuscomm.com.conf: No such file or directory
Mar 28 18:01:40 kernel: /usr/sbin/acme.sh: line 3: can't create /jffs/.le/xxxxxxxxxxx.asuscomm.com/xxxxxxxxxxx.asuscomm.com.conf: nonexistent directory
Mar 28 18:01:40 kernel: grep: /jffs/.le/xxxxxxxxxxx.asuscomm.com/xxxxxxxxxxx.asuscomm.com.conf: No such file or directory
Mar 28 18:01:40 kernel: touch: /jffs/.le/xxxxxxxxxxx.asuscomm.com/xxxxxxxxxxx.asuscomm.com.conf: No such file or directory
Mar 28 18:01:40 kernel: grep: /jffs/.le/xxxxxxxxxxx.asuscomm.com/xxxxxxxxxxx.asuscomm.com.conf: No such file or directory
Mar 28 18:01:40 kernel: grep: /jffs/.le/xxxxxxxxxxx.asuscomm.com/xxxxxxxxxxx.asuscomm.com.conf: No such file or directory
Mar 28 18:01:40 kernel: /usr/sbin/acme.sh: line 3: can't create /jffs/.le/xxxxxxxxxxx.asuscomm.com/xxxxxxxxxxx.asuscomm.com.conf: nonexistent directory
Mar 28 18:01:40 kernel: grep: /jffs/.le/xxxxxxxxxxx.asuscomm.com/xxxxxxxxxxx.asuscomm.com.conf: No such file or directory
Mar 28 18:01:40 kernel: touch: /jffs/.le/xxxxxxxxxxx.asuscomm.com/xxxxxxxxxxx.asuscomm.com.conf: No such file or directory
Mar 28 18:01:40 kernel: grep: /jffs/.le/xxxxxxxxxxx.asuscomm.com/xxxxxxxxxxx.asuscomm.com.conf: No such file or directory
Mar 28 18:01:40 kernel: grep: /jffs/.le/xxxxxxxxxxx.asuscomm.com/xxxxxxxxxxx.asuscomm.com.conf: No such file or directory
Mar 28 18:01:40 kernel: /usr/sbin/acme.sh: line 3: can't create /jffs/.le/xxxxxxxxxxx.asuscomm.com/xxxxxxxxxxx.asuscomm.com.conf: nonexistent directory
Mar 28 18:01:40 kernel: grep: /jffs/.le/xxxxxxxxxxx.asuscomm.com/xxxxxxxxxxx.asuscomm.com.conf: No such file or directory
Mar 28 18:01:40 kernel: touch: /jffs/.le/xxxxxxxxxxx.asuscomm.com/xxxxxxxxxxx.asuscomm.com.conf: No such file or directory
Mar 28 18:01:40 kernel: grep: /jffs/.le/xxxxxxxxxxx.asuscomm.com/xxxxxxxxxxx.asuscomm.com.conf: No such file or directory
Mar 28 18:01:40 kernel: grep: /jffs/.le/xxxxxxxxxxx.asuscomm.com/xxxxxxxxxxx.asuscomm.com.conf: No such file or directory
Mar 28 18:01:40 kernel: /usr/sbin/acme.sh: line 3: can't create /jffs/.le/xxxxxxxxxxx.asuscomm.com/xxxxxxxxxxx.asuscomm.com.conf: nonexistent directory
Mar 28 18:01:40 kernel: grep: /jffs/.le/xxxxxxxxxxx.asuscomm.com/xxxxxxxxxxx.asuscomm.com.conf: No such file or directory
Mar 28 18:01:40 kernel: cat: can't open '/jffs/.le/xxxxxxxxxxx.asuscomm.com/xxxxxxxxxxx.asuscomm.com.conf': No such file or directory
Mar 28 18:01:40 kernel: /usr/sbin/acme.sh: line 3: can't create /jffs/.le/xxxxxxxxxxx.asuscomm.com/xxxxxxxxxxx.asuscomm.com.conf: nonexistent directory
Mar 28 18:01:40 kernel: cat: can't open '/jffs/.le/xxxxxxxxxxx.asuscomm.com/xxxxxxxxxxx.asuscomm.com.conf': No such file or directory
Mar 28 18:01:40 kernel: /usr/sbin/acme.sh: line 3: can't create /jffs/.le/xxxxxxxxxxx.asuscomm.com/xxxxxxxxxxx.asuscomm.com.conf: nonexistent directory
Mar 28 18:01:40 kernel: cat: can't open '/jffs/.le/xxxxxxxxxxx.asuscomm.com/xxxxxxxxxxx.asuscomm.com.conf': No such file or directory
Mar 28 18:01:40 kernel: /usr/sbin/acme.sh: line 3: can't create /jffs/.le/xxxxxxxxxxx.asuscomm.com/xxxxxxxxxxx.asuscomm.com.conf: nonexistent directory
Mar 28 18:01:41 kernel: [Sat Mar 28 18:01:41 DST 2020]
Mar 28 18:01:41 kernel: Registering account
Mar 28 18:01:42 kernel: [Sat Mar 28 18:01:42 DST 2020]
Mar 28 18:01:42 kernel: Already registered
Mar 28 18:01:42 kernel: [Sat Mar 28 18:01:42 DST 2020]
Mar 28 18:01:42 kernel: ACCOUNT_THUMBPRINT='mv2xvCriLyrUzBnYaexW7o1tmavY6B5d3HUm3_A_mZY'
Mar 28 18:01:42 kernel: [Sat Mar 28 18:01:42 DST 2020]
Mar 28 18:01:42 kernel: Creating domain key
Mar 28 18:01:42 kernel: mkdir: can't create directory '/jffs/.le/xxxxxxxxxxx.asuscomm.com': No space left on device
Mar 28 18:01:42 kernel: [Sat Mar 28 18:01:42 DST 2020]
Mar 28 18:01:42 kernel: Can not create path: /jffs/.le/xxxxxxxxxxx.asuscomm.com
Mar 28 18:01:42 kernel: [Sat Mar 28 18:01:42 DST 2020]
Mar 28 18:01:42 kernel: Can not create domain key
Mar 28 18:01:42 kernel: [Sat Mar 28 18:01:42 DST 2020]
Mar 28 18:01:42 kernel: Create domain key error.
Mar 28 18:01:43 kernel: [Sat Mar 28 18:01:43 DST 2020]
Mar 28 18:01:43 kernel: Please add '--debug' or '--log' to check more details.
Mar 28 18:01:43 kernel: [Sat Mar 28 18:01:43 DST 2020]
Mar 28 18:01:43 kernel: See: https://github.com/Neilpang/acme.sh/wiki/How-to-debug-acme.sh
 
Mar 28 18:01:39 kernel: /usr/sbin/acme.sh: line 1: can't create /jffs/.le/account.conf: No space left on device
Mar 28 18:01:39 kernel: mkdir: can't create directory '/jffs/.le/xxxxxxxxxxx.asuscomm.com': No space left on device

Your /jffs/ partition is full.
 
Silly question, how do you fix that? I haven't done anything advanced with this router to fill it up or anything...
 
The two most common reasons are either the traffic analyzer database growing out of control (it normally should get trimmed at 30 MB), or the client database growing out of control (seems to mostly happen when people use a repeater on their network).

I would recommend clearing the traffic analyzer database. First stop it on the web interface, then over SSH delete the database:

Code:
rm -rf /jffs/.sys/TrafficAnalyzer/*

Then re-enable Traffic Analyzer.
 
The two most common reasons are either the traffic analyzer database growing out of control (it normally should get trimmed at 30 MB), or the client database growing out of control (seems to mostly happen when people use a repeater on their network).

I would recommend clearing the traffic analyzer database. First stop it on the web interface, then over SSH delete the database:

Code:
rm -rf /jffs/.sys/TrafficAnalyzer/*

Then re-enable Traffic Analyzer.
I just joined the SNB Forums to say thanks for this info. I also had exactly the same issue (Lets Encrypt not working) and creating some more space on the jffs partition (by deleting the traffic analyzer database) worked a treat. On further inspection afterwards, for some reason, I have a 248MB .ico file in a /jffs/usericon folder so that was why it was running out of space. Reading another post on here about this usericon file/folder, I think I'll keep a copy just in case then delete it.

Thanks, Peter
 
I just joined the SNB Forums to say thanks for this info. I also had exactly the same issue (Lets Encrypt not working) and creating some more space on the jffs partition (by deleting the traffic analyzer database) worked a treat. On further inspection afterwards, for some reason, I have a 248MB .ico file in a /jffs/usericon folder so that was why it was running out of space. Reading another post on here about this usericon file/folder, I think I'll keep a copy just in case then delete it.

Thanks, Peter

I confirm that; None of the solutions given above worked for me, cause i had this error message saying "no space left on the device". I deleted that huge .ico file and it enabled creation of files again. Thus, i could renew the let's encrypt certificate... That's very strange though.
 

Latest threads

Sign Up For SNBForums Daily Digest

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