07-31-2015 08:00 PM - edited 03-19-2019 09:53 AM
The publisher hard drive needed to be "hot swapped" due to failure. Once completed, we powered up the Call Manager through the VM. Call Manager did not come up and stopped with the following error message: kernel panic - not syncing:attempted to kill init. I was wondering what this might mean and how we get beyond this error in order to get the publisher working again? In addition, upon reboot, Unity produced the same error.
Thank you for any insight.
Solved! Go to Solution.
07-31-2015 11:16 PM
It may be a hardware or any driver issue, I would suggest you open a TAC case for this, meanwhile you can also try running recovery disk if you want to try that.
-Terry
Please rate all helpful posts
07-31-2015 11:16 PM
It may be a hardware or any driver issue, I would suggest you open a TAC case for this, meanwhile you can also try running recovery disk if you want to try that.
-Terry
Please rate all helpful posts
08-01-2015 09:04 AM
We have contact TAC and they are performing a reinstallation. Thank you for your response!!
03-14-2021 11:46 PM
Possibly you may be hitting the following bug : https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvv33657
08-28-2023 05:50 AM
Instructions on this bugsearch solved the issue. I upgraded CUCM sub from 12.5(1) SU5 to 12.5(1) SU8 the upgrade itself was successful but when rebooting after switch version command i got the kernel panic message. Just make sure you generate the kernel version the message says it can not find.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide