Ask the Community
Groups
The appliance's storage is being initialized. Please wait a few minutes, then try logging in again. - Connect IT Community | Kaseya
<main> <article class="userContent"> <h2 data-id="issue"><strong>ISSUE</strong></h2> <p><b>ISSUE: </b>You have updated the Unitrends system or made modifications to the storage. You receive the following message when logging into the Web Administrative Interface. </p> <div><i>The appliance's storage is being initialized. Please wait a few minutes, then try logging in again.</i></div> <br><br>As presented in the HTML Web Administrative Interface:<br> <div><img alt="User-added image" height="112" src="https://us.v-cdn.net/6032361/uploads/migrated/77ZTWC97FLGX/eid-ka81w0000004cqm-feoid-00n40000003czoc-refid-0em40000000am1v." width="500" class="embedImage-img importedEmbed-img"></img></div> <h2 data-id="resolution"><strong>RESOLUTION</strong></h2> <p></p> <ol><li>Connect to the Unitrends system using an SSH capable client (e.g.: <a rel="nofollow" href="/home/leaving?allowTrusted=1&target=http%3A%2F%2Fwww.chiark.greenend.org.uk%2F%7Esgtatham%2Fputty%2Flatest.html">putty.exe</a>) and authenticate as the user <b>root</b>.</li> <li>Verify that the storage allocated (below in dark red) is what you expect by executing this command: <pre class="code codeBlock" spellcheck="false" tabindex="0"> [root@UB1 ~]# df -hP Filesystem Size Used Avail Use% Mounted on /dev/sda2 976M 262M 664M 29% / tmpfs 7.8G 0 7.8G 0% /dev/shm /dev/sda1 239M 25M 201M 11% /boot /dev/sda5 5.8G 1.1G 4.5G 20% /usr /dev/sda3 50G 4.8G 42G 11% /usr/bp /dev/sda6 3.9G 211M 3.5G 6% /var /dev/mapper/vg_state-lv_backup <b>12T</b><b> </b> 8.4T 3.7T 70% /_Stateless</pre> </li> <li>If it looks normal, then it is possible a hidden stop file is to blame. Execute this command to see if it exists: <b> ls -rlasth /usr/bp/lists.dir/.disable_rrc</b> </li> <li> <pre class="code codeBlock" spellcheck="false" tabindex="0"> [root@UB1 ~]# rm /usr/bp/lists.dir/.disable_rrc 4.0K -rw-r--r-- 1 root root 100 Apr 18 12:36 /usr/bp/lists.dir/<b>.disable_rrc</b></pre> </li> <li>If the results include details of the file, then it exists and must be removed. Execute this command to remove it: <b>rm /usr/bp/lists.dir/.disable_rrc</b><br> Confirm that you want to file deleted by typing <b>y</b> and pressing the Enter key.</li> <li> <pre class="code codeBlock" spellcheck="false" tabindex="0"> [root@UB1 ~]# rm /usr/bp/lists.dir/.disable_rrc rm: remove regular file `/usr/bp/lists.dir/.disable_rrc'? <b>y</b></pre> </li> <li>Restart the Unitrends Database... <ul><li>Stop the database by executing this command: /etc/init.d/bp_rcscript stop </li> <li> <pre class="code codeBlock" spellcheck="false" tabindex="0"> [root@UB1 ~]# /etc/init.d/bp_rcscript stop Stopping Unitrends Agent...Success.</pre> </li> <li>Start the database by executing this command: /etc/init.d/bp_rcscript start </li> <li> <pre class="code codeBlock" spellcheck="false" tabindex="0"> [root@UEBackup-01 ~]# /etc/init.d/bp_rcscript start Starting Unitrends Agent... Success.</pre> </li> </ul></li> </ol> You should be able to access the Web Administrative Interface now.<h2 data-id="tasks"><strong>TASKS</strong></h2> <p><b>CAUSE:</b> The file is placed in order to ensure a that a consistent state is maintained on the system. In some cases, when a disconnect in communications occur (latency or network disruption for example), the call to remove the file is not received/processed and the file remains.<br><br>The file can be removed if you see that the system is functioning from the command line interface.</p> </article> </main>