What's new

Memory allocation error / write error

  • 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!

geko53

Regular Contributor
After an uptime of about 15 days my syslog suddenly is flooded with write errors:

Nov 10 15:23:28 dnsmasq-dhcp[596]: failed to write /var/lib/misc/dnsmasq.leases: No space left on device (retry in 60s)
Nov 10 15:24:19 smbd[28522]: [2012/11/10 15:24:19, 0] lib/util.c:Realloc(1073)
Nov 10 15:24:19 smbd[28522]: Memory allocation error: failed to expand to 7760 bytes
Nov 10 15:24:19 smbd[28522]: [2012/11/10 15:24:19, 0] smbd/lanman.c:get_server_info(1136)
Nov 10 15:24:19 smbd[28522]: get_server_info: failed to enlarge servers info struct!
Nov 10 15:24:19 smbd[28522]: [2012/11/10 15:24:19, 0] lib/util.c:Realloc(1073)
Nov 10 15:24:19 smbd[28522]: Memory allocation error: failed to expand to 4096 bytes
Nov 10 15:24:19 smbd[28522]: [2012/11/10 15:24:19, 0] lib/util.c:Realloc(1073)
Nov 10 15:24:19 smbd[28522]: Memory allocation error: failed to expand to 4096 bytes
Nov 10 15:24:28 dnsmasq-dhcp[596]: failed to write /var/lib/misc/dnsmasq.leases: No space left on device (retry in 60s)
What did happen here? I'm running an USB drive with 500 GB space mounted on USB1, on USB2 a GSM Modem (HUAWEI E372) is mounted. Firmware: 3.0.0.4.246.19b (Merlin build) (RT-N66U).

Any explanation? After rebooting the device the issue doesn't show any longer, but I would prefer to understand what had happened... :)

Ciao
Gerald
 
After an uptime of about 15 days my syslog suddenly is flooded with write errors:

What did happen here? I'm running an USB drive with 500 GB space mounted on USB1, on USB2 a GSM Modem (HUAWEI E372) is mounted. Firmware: 3.0.0.4.246.19b (Merlin build) (RT-N66U).

Any explanation? After rebooting the device the issue doesn't show any longer, but I would prefer to understand what had happened... :)

Ciao
Gerald

Something was leaking memory, until your router eventually ran out of it.

I suspect the leak is in AiCloud, I noticed myself that the lighttpd-arpping process was eating 99 MB of RAM on my router a few days ago, which isn't normal.
 
I suspect the leak is in AiCloud, I noticed myself that the lighttpd-arpping process was eating 99 MB of RAM on my router a few days ago, which isn't normal.

Tx for your quick response, Merlin. Do you know any remedy against that leak? It would be very annoying if I would have to shut down AICloud as I'm using that feature in daily work...

Tot kijk
Gerald
 
I guess you could configure your router to reboot itself in the middle of the night. Creating a services-start script with this command would do that:

#!/bin/sh
cru a reboot 0 3 * * * reboot
 
Good idea - I'll give it a try!

Bye
Gerald
 
I guess you could configure your router to reboot itself in the middle of the night. Creating a services-start script with this command would do that:

#!/bin/sh
cru a reboot 0 3 * * * reboot

Note.. I followed this and got errors. I had to use quotes:

#!/bin/sh
cru a reboot "0 3 * * * reboot"
 

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