Estou tentando recuperar uma senha de root em um MX80, mas estou recebendo alguns erros e não tenho idéia do que eles significam (não é ao vivo, portanto, etapas sugestivas de "interrupção" são aceitáveis);
Os passos que tomei são os seguintes;
Reinicie o roteador, no prompt
Hit [Enter] to boot immediately, or space bar for command prompt- eu acertei espaçoEntro
boot -spara inicializar no modo de usuário únicoNo prompt
Enter full pathname of shell or 'recovery' for root password recovery or RETURN for /bin/sh:, insirorecoveryUma vez na CLI, entro no modo de configuração e tento redefinir a senha root e confirmar a configuração;
Aqui é onde eu experimento os erros; O que eles significam e como posso corrigir isso? Ele ainda precisa ser corrigido (eu diria que sim!):
[edit]
root# set system root-authentication plain-text-password
New password:
Retype new password:
[edit]
root# commit
error: could not open database: /var/run/db/juniper.data: No such file or directory
error: Database open failed for file '/var/run/db/juniper.data': No such file or directory
error: commit failed: daemon file propagation failed
[edit]
root# WATCHDOG_TIMER : Loss of soft watchdog
panic: Loss of soft watchdog
Entering boot mastership relinquish phase
KDB: enter: panic
[thread pid 11 tid 100005 ]
Stopped at kdb_enter+0x1a4: addis r3, r0, -0x5f7a
db>
O MX80 está executando o JunOS 11.4R1.14. Reiniciei e a senha não foi redefinida. Devo tentar novamente ou há algo de errado com este roteador que devo abordar primeiro? Eu não quero danificar nada.
ATUALIZAR
Como uma atualização para isso; Hoje eu iniciei novamente no modo de recuperação e não fiz nada, estava no telefone com o roteador sentado na "raiz>". Enquanto estava no telefone por alguns minutos, o roteador entrou em pânico;
Enter full pathname of shell or 'recovery' for root password recovery or RETURN for /bin/sh: recovery
Performing filesystem consistency checks ...
/dev/da0s1a: 1466 files, 91908 used, 361032 free (56 frags, 45122 blocks, 0.0% fragmentation)
/dev/da0s1e: 9 files, 8 used, 50273 free (17 frags, 6282 blocks, 0.0% fragmentation)
Performing mount of main filesystems ...
Performing filesystem consistency of secondary filesystems ...
/dev/da1s1f: 232 files, 362550 used, 1105677 free (125 frags, 138194 blocks, 0.0% fragmentation)
Performing mount of secondary filesystems ...
Verified manifest signed by PackageProduction_11_4_0
Verified jboot signed by PackageProduction_11_4_0
Verified jbase-ppc-11.4R1.14 signed by PackageProduction_11_4_0
Mounted jkernel package on /dev/md1...
Verified manifest signed by PackageProduction_11_4_0
veriexec: fingerprint for dev 73, file 49356 f743694d46ccdfd6bc72f0793c1cc0e8e5bdf80e != b3dfc26ab4c595f569e86791aa3dcfa4a277892c
Verified jkernel-ppc-11.4R1.14 signed by PackageProduction_11_4_0
Mounted jpfe package on /dev/md2...
Mounted jdocs package on /dev/md3...
Verified manifest signed by PackageProduction_11_4_0
Verified jdocs-11.4R1.14 signed by PackageProduction_11_4_0
Mounted jroute package on /dev/md4...
Verified manifest signed by PackageProduction_11_4_0
Verified jroute-ppc-11.4R1.14 signed by PackageProduction_11_4_0
Mounted jcrypto package on /dev/md5...
Verified manifest signed by PackageProduction_11_4_0
Verified jcrypto-ppc-11.4R1.14 signed by PackageProduction_11_4_0
machdep.bootsuccess: 1 -> 1
Performing initialization of management services ...
mgd: error: could not open database: /var/run/db/schema.db: No such file or directory
mgd: error: Database open failed for file '/var/run/db/schema.db': No such file or directory
mgd: error: could not open database schema: /var/run/db/schema.db
mgd: error: could not open database schema
mgd: error: database schema is out of date, rebuilding it
mgd: error: could not open database: /var/run/db/juniper.data: No such file or directory
mgd: error: Database open failed for file '/var/run/db/juniper.data': No such file or directory
mgd: error: Cannot read configuration: Could not open configuration database
Performing checkout of management services ...
NOTE: Once in the CLI, you will need to enter configuration mode using
NOTE: the 'configure' command to make any required changes. For example,
NOTE: to reset the root password, type:
NOTE: configure
NOTE: set system root-authentication plain-text-password
NOTE: (enter the new password when asked)
NOTE: commit
NOTE: exit
NOTE: exit
NOTE: When you exit the CLI, you will be asked if you want to reboot
NOTE: the system
Starting CLI ...
root> WATCHDOG_TIMER : Loss of soft watchdog
panic: Loss of soft watchdog
###Entering boot mastership relinquish phase
KDB: enter: panic
[thread pid 11 tid 100005 ]
Stopped at kdb_enter+0x1a4: addis r3, r0, -0x5f7a
db>
Vou reinstalar e ver o que acontece.
fonte
Respostas:
Poderia ser um sistema de arquivos corrompido - o roteador foi reiniciado sem o desligamento adequado? Se for o caso, tente inicializar a partir do pendrive e reinstale (com a nova partição) o cartão CF:
solicitar mídia de partição de instantâneo do sistema compact-flash (ou similar, consulte o manual para obter o nome exato do dispositivo)
fonte