Has anyone seen this error and how do i resolve it? Happened after running a restore to migrate lms 3.2 data into lms 4.2 in which the database user or password got corrupted.
Info: Starting database engine UPMDbEngine
Error: Failed to become a daemon
Error: Failed to start database 'upm' because: Could not connect to engine 'EPMDbEngine" on 'upm' in bulk mode. Check user id and passwords.
Ran the dbpasswd.pl script to change all the database passwords. Got the same error as above, a long with:
Error:Failed to connect to the database upm with current password.
Info: Trying factory password for upm database.
Error: Failed to update new userinfo into database.
lms 4.2 was installed on a new solaris zone. Verified that it was working and discovering the network before running a restore to migrate lms 3.2 data. After the restore it appeared to be working until i tried to run a backup of lms 4.2. or the dbpasswd.pl script. Password change worked on all other databases.
Question We run asr9001 with XR 6.1.3, and we have a very long delay to
login w/ SSH 1 or 2 to the device compare to IOS device. After
investigation, the there is 1s delay between the client KEXDH_INIT and
the server (XR) KEXDH_REPLY. After debug ssh serv...
Introduction The purpose of this document is to demonstrate the Open
Shortest Path First (OSPF) behavior when the V-bit (Virtual-link bit) is
present in a non-backbone area. The V-bit is signaled in Type-1 LSA only
if the router is the endpoint of one or ...
Hi, I am seeing quite a few issues with patch install and wanted to
share my experience and workaround to this. Login to admin via CLI, then
access root with the “shell” command Issue “df –h” and you’ll probably
see the following directory full or nearly ...