Summary
Error when trying to execute a cli command due to a corrupt config file in memoryOverview
When user tries to execute a command in the cli mode, they get an internal error 1001 or 1002 or 1003Cause
A corrupt config in the system can cause this. It can happen when a binary file from one Exinda is transferred to another Exinda, hence corrupting the config on the latter. This bad corruption will not allow any CLI or web UI configurationResolution
User needs to go to Single User Mode during boot and delete all the files under config/db directory. This is a detailed internal mode that is not easy to access. This deletes all the config files in memory and restores the system to a good default state with no configuration on it.In order to obtain steps to perform this, please contact Exinda TAC.
Internal Notes
Steps for an x60 DeviceFirst, the system must be rebooted or power cycled. It is assumed the person following this procedure is able to access the system's console and can see the entire boot process (this is either over a serial console or the system's direct console).
Step1: Press the down key when it says "Boot loading stage 2"and select the image to boot into. Once the image is selected (in this case 0) then press ÒeÓ to enter the edit command mode. This will give the user the ability to change the commands options that are part of the boot process.
Boot Menu
---------------------------------------
0: exinda-6.0.2.16348 (i386) 2010/03/31
1: exinda-6.0.2.16348 (i386) 2010/03/31
2: memtest86+ v1.70
---------------------------------------
Step2: Now use the arrow key and select 1 (for kernel.......) and type ÒeÓ again
Boot Menu
---------------------------------------
0: root (hd0,1)
1: kernel /vmlinuz ro root=/dev/sda5 img_id=1 quiet loglevel=4 panic=10 console=tty0
console=ttyS0.9600n8
---------------------------------------
Step3: On the next screen after entering 'e' go to the end of the line and the text 'single' should be appended to the end of this line. Hit Enter.
Note: The '<' indicates that a portion of the command line is not seen. The arrow keys allow the user to navigate the command line to the very end so that above step 2 can be done as below:
<el=4 panic=10 console=tty0 console=ttyS0, 9600n8 single
Step4: On the next screen select option 1 (kernel.....) and type "b" to resume booting the selected image.
Boot Menu
---------------------------------------
0: root (hd0,1)
1: kernel /vmlinuz ro root=/dev/sda5 img_id=1 quiet loglevel=4 panic=10 console=tty0
console=ttyS0.9600n8 single
---------------------------------------
Step5: After more boot messages a 'root' user prompt should be displayed as below:
resh-3.2#
Now here run the below:
cd /config/db
Now here remove the configs listed including any .bak files. This will basically load the default config. This can be done as below
rm <filename>
Now just Reload the box.
resh-3.2# reboot
------------------
FOR x62 devices:
When editing the command line, which looks something like this:
ro root=/dev/vda6 crashkernel=128M img_id=2 quiet loglevel=4 panic=10 console=tty0 console=ttyS0,115200
1.- Append the word "single" like this: ro root=/dev/vda6 crashkernel=128M img_id=2 quiet loglevel=4 panic=10 console=tty0 console=ttyS0,115200 single
2.- Remove the 'quite' - that tells it to log very little. If something is going wrong it is useful to see all the mesasges.
3.- Change the 'loglevel=4' to 'loglevel=7'. That changes the messages that are shown from ERR and above to INFO and above. It may show something else of use.
4.- If using the VGA console and a keyboard remove the 'console=ttyS0,9600' - that'll stop it talking out the serial point.
5.- If using the serial port remove the 'console=tty0' - that will stop it talking to the VGA output/local keyboard.
6(Optional).- If that did not work try changing 115200 to 9600
1.- Append the word "single" like this: ro root=/dev/vda6 crashkernel=128M img_id=2 quiet loglevel=4 panic=10 console=tty0 console=ttyS0,115200 single
2.- Remove the 'quite' - that tells it to log very little. If something is going wrong it is useful to see all the mesasges.
3.- Change the 'loglevel=4' to 'loglevel=7'. That changes the messages that are shown from ERR and above to INFO and above. It may show something else of use.
4.- If using the VGA console and a keyboard remove the 'console=ttyS0,9600' - that'll stop it talking out the serial point.
5.- If using the serial port remove the 'console=tty0' - that will stop it talking to the VGA output/local keyboard.
6(Optional).- If that did not work try changing 115200 to 9600