DHCP: No space left on device message error

[Kristapor]

Hi,

i just face some latencies issues and when i looked in the Asus router logs, i found a strange message:
DHCP: no space left on device (see attachement)

Is there any link?
Should i reboot my router (uptime is 27d)?
Is it a bug?

Thanks for your feedback

Christophe

 

[joegreat]

i just face some latencies issues and when i looked in the Asus router logs, i found a strange message:
DHCP: no space left on device (see attachement)

Hi Christophe,

This was already discussed here - a small forum search would give you the instant answer...

 

[Kristapor]

Arf, true ... lazy me ;-)

Thanks for the info.

However, the root cause for this message doesn't look clear for me. And i also have Parental Control enabled but no special scripts activated.

Anyway, i think i will reboot my router tonight to clear the log.

 

[RMerlin]

Arf, true ... lazy me ;-)

Thanks for the info.

However, the root cause for this message doesn't look clear for me. And i also have Parental Control enabled but no special scripts activated.

Anyway, i think i will reboot my router tonight to clear the log.

Already fixed in 378.56_2, please upgrade to the latest version.

 

[FlyByWire]

Already fixed in 378.56_2, please upgrade to the latest version.

Is it? In my case this occured under 378.56_2?!

 

[L&LD]

Is it? In my case this occured under 378.56_2?!

You may need to do a reset to factory defaults and a minimal and manual configuration of the router then.

http://www.snbforums.com/threads/no...l-and-manual-configuration.27115/#post-205573

 

[RMerlin]

Is it? In my case this occured under 378.56_2?!

There are a number of things recently causing RAM to fill up. 378.56 (which the OP uses) was generating a mDNSNetMonitor.log file that was filling up RAM for many users, which was resolved in 378.56_2. It's a common cause, so there's a good chance it will resolve his specific issue. In your case, it's probably the (far less common) smb.log that gets filled up by more debug output. That one is fixed in the current development code, and will be part of the 380.57 release.

 

[unsynaps]

Already fixed in 378.56_2, please upgrade to the latest version.

The thing is for me this problem did not start till I upgraded to 378.56_2. Factory defaulted and everything after upgrade. The only things re-imported was the reserved DHCP list. The unit is a RT-AC87R.

Just had to power off restart my router cause I could not log in via web or SSH. I will see if I can dig up some logs or output other than the system log spamming "Dec 10 17:31:10 dnsmasq-dhcp[441]: failed to write /var/lib/misc/dnsmasq.leases: No space left on device (retry in 7s)".

 

[RMerlin]

The thing is for me this problem did not start till I upgraded to 378.56_2. Factory defaulted and everything after upgrade. The only things re-imported was the reserved DHCP list. The unit is a RT-AC87R.

Just had to power off restart my router cause I could not log in via web or SSH. I will see if I can dig up some logs or output other than the system log spamming "Dec 10 17:31:10 dnsmasq-dhcp[441]: failed to write /var/lib/misc/dnsmasq.leases: No space left on device (retry in 7s)".

Then your problem is probably with the samba debug log, which was also added by Asus in the 9xxx firmware code on which 378.56 and 378.56_2 are based. You can try the 380.57 alpha builds posted in these forums, which resolved the Samba log issue. 378.56_2 resolved the mDNSMonitor log issue, which was also filling up RAM.

There's one more log I haven't removed yet that can take a fair amount of RAM, because I don't know if it's used by the new mobile application or not.

 

[RMerlin]

Essentially, in 9177, Asus added a bunch of debug log that are stored in RAM, and which can potentially fill up your RAM. 378.56 has all of these logs, 378.56_2 removed the mDNS log, and 380.57 removes also the samba log.

 

[sfx2000]

DHCP: no space left on device (see attachement)

Perhaps expand your DHCP scope?

Otherwise - do a reset and see what happens, and expand the scope from there...

 

[unsynaps]

Then your problem is probably with the samba debug log, which was also added by Asus in the 9xxx firmware code on which 378.56 and 378.56_2 are based. You can try the 380.57 alpha builds posted in these forums, which resolved the Samba log issue. 378.56_2 resolved the mDNSMonitor log issue, which was also filling up RAM.

There's one more log I haven't removed yet that can take a fair amount of RAM, because I don't know if it's used by the new mobile application or not.

Yeah looks like its samba. I made my last post within 5-10 min of that restart. Should have saved ls -la I did on /tmp then but at the time of this posting:

admin@mpu:/tmp# ls -la
drwxrwxrwx   13 admin    root           940 Dec 10 17:39 .
drwxr-xr-x   18 admin    root           337 Nov  2 10:48 ..
-rwxr--r--    1 admin    root             0 Dec 10 17:34 .bwdpi.appdb.lck
-rwxr--r--    1 admin    root             0 Dec 10 17:34 .bwdpi.rule.lck
-rwxr--r--    1 admin    root             0 Dec 10 17:34 .qosd.conf.lock
drwxrwxrwx    3 admin    root            80 Jul 31 20:00 avahi
drw-rw-rw-    3 admin    root           360 Dec 10 17:35 bwdpi
-rw-rw-rw-    1 admin    root            25 Dec 10 17:34 ddns.cache
lrwxrwxrwx    1 admin    root             8 Jul 31 20:00 dhcp6c -> /sbin/rc
drwxr-xr-x    6 admin    root           860 Dec 10 17:34 etc
-rw-rw-rw-    1 admin    root           702 Dec 10 17:34 filter.default
-rw-rw-rw-    1 admin    root           702 Dec 10 17:34 filter_ipv6.default
-rw-rw-rw-    1 admin    root          1419 Dec 10 17:34 filter_rules
-rw-rw-rw-    1 admin    root          2512 Dec 10 17:34 filter_rules_ipv6
drwxr-xr-x    3 admin    root            60 Dec 31  1969 home
-rw-rw-rw-    1 admin    root           374 Dec 10 17:34 miniupnpc.log
drwxrwxrwx    3 admin    root            60 Jul 31 20:00 mnt
lrwxrwxrwx    1 admin    root            24 Dec 10 17:34 nat_rules -> /tmp/nat_rules_eth0_eth0
-rw-rw-rw-    1 admin    root           784 Dec 10 17:34 nat_rules_eth0_eth0
drwxr-xr-x    3 admin    root            60 Dec 31  1969 notify
drwxrwxrwx    3 admin    root           260 Jul 31 20:00 ppp
drwxr--r--    2 admin    root           140 Jul 31 20:00 pptpd
-rwxr-xr-x    1 admin    root           617 Nov  2 10:48 qtn_dbg.sh
-rw-rw-rw-    1 admin    root           965 Dec 10 17:34 redirect_rules
-rw-rw-rw-    1 admin    root            46 Dec 10 17:34 resolv.conf
-rw-rw-rw-    1 admin    root           130 Dec 10 17:34 resolv.dnsmasq
-rwxr-xr-x    1 admin    root          3263 Nov  2 10:48 router_command.sh
-rw-r--r--    1 admin    root             0 Dec 31  1969 settings
drwxr-xr-x    2 admin    root            40 Dec 31  1969 share
-rw-rw-rw-    1 admin    root            46 Dec 10 17:36 sig_upgrade.log
-rw-rw-rw-    1 admin    root      32791158 Dec 11 00:01 smb.log
-rwxr-xr-x    1 admin    root          5802 Nov  2 10:48 start-stateless-slave
-rw-rw-rw-    1 admin    root           463 Jul 31 20:00 stateless_slave_config
-rw-rw-rw-    1 admin    root         69252 Dec 11 00:14 syslog.log
-rw-rw-rw-    1 admin    root        262177 Jul 31 20:00 syslog.log-1
-rwxr-xr-x    1 admin    root       4769651 Nov  2 10:48 topaz-linux.lzma.img
-rwxr-xr-x    1 admin    root            68 Nov  2 10:48 tweak_qcomm
-rwxr-xr-x    1 admin    root         68816 Nov  2 10:48 u-boot.bin
lrwxrwxrwx    1 admin    root             8 Jul 31 20:00 udhcpc -> /sbin/rc
-rw-rw-rw-    1 admin    root            10 Jul 31 20:00 udhcpc0.expires
-rw-rw-rw-    1 admin    root         30327 Dec 10 17:34 upnpc_xml.log
drwxrwxrwx    2 admin    root            40 Jul 31 20:00 upnpicon
-rw-rw-rw-    1 admin    root          2524 Dec 10 17:34 usb.log
-rw-rw-rw-    1 admin    root            32 Dec 10 17:34 usb_err
drwxr-xr-x   14 admin    root           380 Dec 10 17:34 var
lrwxrwxrwx    1 admin    root             8 Jul 31 20:00 wpa_cli -> /sbin/rc
lrwxrwxrwx    1 admin    root             8 Jul 31 20:00 zcip -> /sbin/rc

32MB already. Least I know what the issue is. Now to decide if I want to run the beta or just set the router to restart more often than once a week and wait for the final.

 

[RMerlin]

Yeah looks like its samba. I made my last post within 5-10 min of that restart. Should have saved ls -la I did on /tmp then but at the time of this posting:
32MB already. Least I know what the issue is. Now to decide if I want to run the beta or just set the router to restart more often than once a week and wait for the final.

You could just delete that file instead of rebooting your router. It's just a logfile.

The alpha builds have been quite stable so far. I don't expect many more changes to happen before the final release, I'm just lacking the time to wrap everything up for an actual release at this time.