Security

When I try to upload new content to use in our customized captive portal I run into the following error.

System has low free memory and/or low free disk space. Please delete unwanted files by accessing WebUI Maintenance > File > Delete Files, reload the controller to recover free memory and try uploading the image again. If it fails again, try other upgrade options.

This error is pretty self-explanatory.. you'd say :)

What command can I use to determine wether dispace and/or memory is the issue?

Please try the following commands.

(3600) #show memory

Memory (Kb):

total: 1541408, used: 285068, free: 1256340

(3600) #show storage

Filesystem Size Used Available Use% Mounted on

none 300.0M 3.2M 296.8M 1% /tmp

/dev/hda3 392.7M 111.7M 260.7M 30% /flash

(3600) # dir 

(ZMARUBA01) #show memory

Memory (Kb): total: 354376, used: 297832, free: 56544

(ZMARUBA01) #show storage
Filesystem                Size      Used Available Use% Mounted on
none                    300.0M      3.8M    296.2M   1% /tmp
/dev/hda3               392.7M    145.6M    226.8M  39% /flash

(ZMARUBA01) #

Seems to be enough mem/storage.. right?

Monday mornin' bump

- What controller platform is this?

- What verson of ArubaOS?

- How big is the content you are trying to upload?

Can you try typing "tar crash" at the commandline and copying off and deleting the crash.tar file and trying again?

Can you type "dir" to see if you have any file that you might not be using there?

Creating and deleting the crash tar did the trick, tnx.

Seems to be a temp fix.

Same problem again, cant upload any custom content (html files)..

Any ideas?

Bump

Please open a support case to get to the bottom of this.  I can say that I have not seen your issue, but others might have.

hey,

please enveekaa have you found any solution to this issue, i got the same probleme with a 7030 controller

hay any update :)

for the reference

according to the TAC the issue was resolved in the version 6.4.2.3 , indeed we found in the release note of the version 6.4.2.3 that the  bug was resolved.