i am working as a newbie in CUCM side, i have a CUCM (Business Edition) in our office lab an previously it was working on
7.1.3 version but 3 days ago when i turned it on for some testing then at was not taking me to the admin login prompt (console)
and was just giving me this message:
*** An error occured during the file system check. *** Dropping you to a shell; the system will reboot *** when you leave the shell. Give root password for maintenance (or type Control-D to continue):
then i tried to recover this issue with ( 126.96.36.199000-1 recovery.iso) just because of this statement
(regardless of product version. New recovery disks generally work with older releases.)
as described in this link:
Right now i can access the CUCM BE from the console, i can get the admin login from the console
but i can't access this CUCM BE via GUI and when i check utils system list , all the services in that
list are showing [STOPPED]
How can i get the Admin page access again ??
Any of your prompt response regarding this will be really appreciated.
Go to Consol and start all the below service by utils service start command.
A Cisco DB
Cisco DRF Local
Cisco DRF Master
Cisco Database Layer Monitor
Cisco CallManager Serviceability
Cisco CAR DB
Please rate helpful posts.
Thanks for your reply, but i have already tried to start of these services, Cisco Tomcat keeps giving me the message
Cisco Tomcat [STARTING] ........
and to stop this message i need to press Crtl - C , also when i checked via :
utils diagnose test
one of the test which got fail gave me this message:
test - tomcat _connectors : Failed - The HTTP and HTTPS ports are not responding
to local . Please collect all of the tomcat logs for root cause analysis: file get
Please let me know what should i suppose to do next !!
Do you still get following message during CUCM boots ?
*** An error occured during the file system check.
*** Dropping you to a shell; the system will reboot
*** when you leave the shell.
Give root password for maintenance
(or type Control-D to continue):
If yes, why not try using the matching recovery software this time, dowload it from here ?
Pls rate helpful posts !!
No i am not getting that error message again, as i mentioned already i got the access of admin
via cli but the only issue is that i can't access the BE via GUI.
Restarting the server will not kill, as this is LAB server. This may happen some times due to high memory utilization by other process. Not sure if restarting will help but it is worth of try.
Hi Ali Jaffry, how are you?
This is a memory issue.
If you're using VMWARE to do your lab, please allocate 2 GB of memory at least.
Please try and let us know the results
Can you provide the log from the diagnostic test?
From the CLI, pull up the active log by run the following command:
file list activelog tomcat/logs
See if you can find a file titled something along the lines of:
to view the file, type the following command in the CLI:
file view activelog tomcat/logs/