我正在尝试恢复MX80上的root密码,但是我收到一些错误,并且不知道它们的含义(它不存在,因此建议性的“破坏性”步骤是可以接受的);
我已采取的步骤如下:
在提示时重新启动路由器
Hit [Enter] to boot immediately, or space bar for command prompt
-我碰到空格我进入
boot -s
引导进入单用户模式在提示符下,
Enter full pathname of shell or 'recovery' for root password recovery or RETURN for /bin/sh:
我输入recovery
进入CLI后,我进入配置模式,然后尝试重置root密码并提交配置。
这是我遇到的错误;它们是什么意思,我该如何纠正?它是否甚至需要更正(我认为是!):
[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>
MX80正在运行JunOS 11.4R1.14。我已重新启动,密码尚未重置。我应该再试一次,还是该路由器出现问题,我应该首先解决?我不想破坏任何东西。
更新
作为对此的更新;今天,我再次进入恢复模式,却什么也没做,我在电话中,路由器位于“ root>”。在电话上通话了几分钟后,路由器突然出现了恐慌。
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>
我将重新安装,看看会发生什么。
2
我感觉操作系统可能有问题,导致您无法更改密码。我会尝试升级或降级操作系统,以查看是否可行。但是,当然,在这样做之前,请务必备份您的配置和操作系统。
—
ponsfonze 2013年
我同意这听起来像路由器正在从备份映像启动,并且无法将配置写回到永久存储,我也建议您进行软件更新,如果仍无法解决,那么我将使用TAC查看硬件
—
DrBru