Description

This article explains an issue observed on JuniperACX/MX/EX routers where the device boots but fails to enter CLI mode.

Symptoms

When the device is affected, it displays boot messages and fails to reach the CLI prompt. The following messages may be observed on the console:

root@% 01:51:03 authd[3452]: UI_CONFIGURATION_ERROR: Process: authd, path: <none>, statement: <none>, Opening configuration database: Could not open configuration database

root@% 01:51:46 alarmd[2566]: conn_connect 144: conn_who 3, connecton fails, retried 420 times, error: No such file or directory.

root@% 01:51:49 authd[3453]: UI_DBASE_OPEN_FAILED: Database open failed for file '/var/run/db/juniper.data': No such file or directory

May 9 01:51:49 authd[3453]: UI_CONFIGURATION_ERROR: Process: authd, path: <none>, statement: <none>, Opening configuration database: Could not open configuration database

root@% 01:52:24 pfed: UI_DBASE_OPEN_FAILED: Database open failed for file '/var/run/db/juniper.data': No such file or directory

root@% 01:52:24 pfed: LIBCOS_CONFIG_DB_FAILURE: Configuration database open failure: Could not open configuration database

root@% 01:52:24 pfed: UI_DBASE_OPEN_FAILED: Database open failed for file '/var/run/db/juniper.data': No such file or directory

root@% 01:52:24 pfed: LIBCOS_CONFIG_DB_FAILURE: Configuration database open failure: Could not open configuration database

root@% 01:52:24 pfed: UI_DBASE_OPEN_FAILED: Database open failed for file '/var/run/db/juniper.data': No such file or directory

root@% 01:52:24 pfed: LIBCOS_CONFIG_DB_FAILURE: Configuration database open failure: Could not open configuration database

root@% 01:52:34 authd[3454]: UI_DBASE_OPEN_FAILED: Database open failed for file '/var/run/db/juniper.data': No such file or directory

root@% 01:52:34 authd[3454]: UI_CONFIGURATION_ERROR: Process: authd, path: <none>, statement: <none>, Opening configuration database: Could not open configuration database

root@% 01:52:46 alarmd[2566]: conn_connect 144: conn_who 3, connecton fails, retried 480 times, error: No such file or directory.

root@%

root@% 01:53:00 login: login_getclass: unknown class 'junos-login-defaults'

root@% ncorrect

root@%

root@% login: ^C^HClient aborted login

root@%

root@% c (ttyu0)

root@%

root@% root

root@% OS 21.2R3-S9.20 built 2025-03-31 19:11:39 UTC

root@% cli

May 9 01:53:09 login: login_getclass: unknown class 'junos-login-defaults'

May 9 01:53:18 cli: login_getclass: unknown class 'j-idle-timeout'

May 9 01:53:20 authd[3455]: UI_DBASE_OPEN_FAILED: Database open failed for file '/var/run/db/juniper.data': No such file or directory

May 9 01:53:20 authd[3455]: UI_CONFIGURATION_ERROR: Process: authd, path: <none>, statement: <none>, Opening configuration database: Could not open configuration database

could not open user interface connection: management daemon not responding

Retry connection attempts ? [yes,no] (yes) yes

could not open user interface connection: management daemon not responding

Retry connection attempts ? [yes,no] (yes)

Solution

The logs shown below typically indicate a memory error, likely due to a bad sector on the flash storage. In such cases, using the USB recovery method can help clear the error state and allow the router to boot successfully.

 

root@% 01:52:24 pfed: UI_DBASE_OPEN_FAILED: Database open failed for file '/var/run/db/juniper.data': No such file or directory

root@% 01:52:24 pfed: LIBCOS_CONFIG_DB_FAILURE: Configuration database open failure: Could not open configuration database

root@% 01:52:24 pfed: UI_DBASE_OPEN_FAILED: Database open failed for file '/var/run/db/juniper.data': No such file or directory

root@% 01:52:24 pfed: LIBCOS_CONFIG_DB_FAILURE: Configuration database open failure: Could not open configuration database

root@% 01:52:34 authd[3454]: UI_DBASE_OPEN_FAILED: Database open failed for file '/var/run/db/juniper.data': No such file or directory

Please refer the below documents for the USB recovery procedure.

Modification History

2025-06-21 : Article Created