11-22-2024 10:04 PM
Hi, Support team
I got a zone director 1100 with version of 9.5. 0.0 build156, this unit always goes into the setup wizard mode when powering up/powering cycle, which means that I need to finish the setup wizard for each powering up. Is there any config to set to prevent this happen.
btw, I tried to ugprade to newer version via GUI and CLI. However, it always failed, is there any restricton on the upgrade?
Thanks.
Solved! Go to Solution.
11-27-2024 06:52 PM
Hi,
Yes, this seems like a hardware issue, you will have to raise an RMA on this.
Please contact support on this and share this discussion link so that they can initiate the RMA.
11-23-2024 12:38 AM
Hi,
more debug info.
I tried to connect with serial port with CLI interface. it always pops with below:
mv: cannot create '/etc/airespider/custom.bak.xml': Read-only file system
mv: cannot create '/etc/airespider/license-list.bak.xml': Read-only file system
mv: cannot create '/etc/airespider/mesh-list.xml': Read-only file system
mv: cannot remove '/etc/airespider/system.bak.xml': Read-only file system
mv: cannot remove '/etc/airespider/system.xml': Read-only file system
mv: cannot remove '/etc/airespider/ap-list.bak.xml': Read-only file system
mv: cannot remove '/etc/airespider/apgroup-list.bak.xml': Read-only file system
is the issue related to this?
Thanks.
11-23-2024 04:54 PM
Hi,
Once the controller comes up after power cycle, login to the CLI and finish the setup process.
Then check if you are still facing the issue.
Are you getting any error while doing the upgrade?
11-24-2024 02:34 AM
Hi, Sanjay
Thanks a lot for your prompt reply on this.
Yes, I do have issue for the upgrade, please help to check it below
------------------------------------------------------------------------
** Upgrading the system **
------------------------------------------------------------------------
ZoneDirector is being upgraded, DO NOT disconnect ZoneDirector
from the power source or the wired network. Wait a few minutes
after the automatic system restart.
........................................Out of memory: kill process 5099 (ruckus_cli2) score 149 or a child
Killed process 6546 (sh)
Out of memory: kill process 5099 (ruckus_cli2) score 140 or a child
Killed process 5099 (ruckus_cli2)
Please login: Out of memory: kill process 5058 (webs) score 84 or a child
Killed process 5058 (webs)
Out of memory: kill process 5073 (webs) score 84 or a child
Killed process 5073 (webs)
Out of memory: kill process 5074 (webs) score 84 or a child
Killed process 5074 (webs)
Out of memory: kill process 5075 (webs) score 84 or a child
Killed process 5075 (webs)
Out of memory: kill process 5076 (webs) score 84 or a child
Killed process 5076 (webs)
Out of memory: kill process 5077 (webs) score 84 or a child
Killed process 5077 (webs)
Out of memory: kill process 5078 (webs) score 84 or a child
Killed process 5078 (webs)
Out of memory: kill process 4924 (vsftpd) score 47 or a child
Killed process 4924 (vsftpd)
Out of memory: kill process 6547 (fw_upgrade) score 38 or a child
Killed process 7233 (sys_wrapper.sh)
Out of memory: kill process 7523 (login.sh) score 37 or a child
Killed process 7524 (login)
Killed
Out of memory: kill process 5087 (tacmon.sh) score 31 or a child
Killed process 5092 (tacmon)
Out of memory: kill process 5089 (rhttpd) score 31 or a child
Killed process 5089 (rhttpd)
Out of memory: kill process 5090 (zapd) score 20 or a child
Killed process 5090 (zapd)
Out of memory: kill process 7526 (rhttpd) score 31 or a child
Killed process 7526 (rhttpd)
Out of memory: kill process 7527 (zapd) score 20 or a child
Killed process 7527 (zapd)
Out of memory: kill process 7522 (gunzip) score 19 or a child
Killed process 7522 (gunzip)
/bin/zapd version 1.83.16, Copyright (C) 2004-2006 Ruckus Wireless, Inc. All Rights Reserved.
Built Dec 26 2012 at 01:04:57
Please login:
Seems it prompts with out of memory, is it a hardware failure?
Thanks.
regards,
11-27-2024 06:52 PM
Hi,
Yes, this seems like a hardware issue, you will have to raise an RMA on this.
Please contact support on this and share this discussion link so that they can initiate the RMA.