Kernel panic - not syncing: Attempted to kill init!

General and Support topics relating to ViciDialNow and GoAutoDial ISO installers

Moderators: enjay, williamconley, Op3r, Staydog, gardo, mflorell, MJCoate, mcargile, Kumba, s0lid

Kernel panic - not syncing: Attempted to kill init!

Postby gmcust3 » Fri Jan 15, 2010 2:15 pm

exec of init (/sbin/init) failed!!! : 2
umount /initrd/dev failed: 2
Kernel panic - not syncing: Attempted to kill init!

I tried installing VNow 1.3

1) Server was working.

2) Kernel Version 2.6.18-164.el5.vnow (SMP)

3) CentOS release 5.4 (Final)

4) Person available but he is not a tech person.

5) Just restarted the server and seen the Error.

6) Didnt update anything.

Server got Installed today itself.

Any solutions ?

My server is at remote end which I access through Public IP.
GoAutoDial CE
VERSION: 2.4-309a
BUILD: 110430-1642
No other software installed on the box.
I've read the manager manual.
gmcust3
 
Posts: 1148
Joined: Sat Oct 24, 2009 1:15 pm

thanks

Postby brett05 » Fri Jan 15, 2010 2:24 pm

you have a critical panic in your kernel
have you edit same thing
or try to install again
Jasperreports & Queuemetrics & SugarCRM integration - Customization and Add-ons
Freepbx||Billing||Centos||Opensuse||Debian||Centos||Fedora||Sangoma||Diguim
brett05
 
Posts: 571
Joined: Sun May 24, 2009 5:48 pm
Location: tunisia

Postby callcentersolutions » Sat Jan 16, 2010 3:09 pm

It's not related to vicidialnow rather than linux kernel with filesystem issues. So better you reinstall and check.
Best Regards,
callcentersolns
------------------------------------------------------------------------------------
Free vicidial installation. Email when needed any kind of solutions regards vicidial/vicidialnow
callcentersolutions
 
Posts: 25
Joined: Tue Dec 08, 2009 9:28 am

Postby Janky » Sat Jan 16, 2010 11:40 pm

yes a kernel panic is going to be something typically related to your hardware and os version or vise versa and not related to vicidial.

were any of the drive labels changed or fstab edited? was the drive loaded on one channel and then booted from another? are there any cpu isssues or memory issues? are you running the right kernel version for the amount of ram you have in the system?

many possibilities almost like a BSOD in windows but usually more detailed anyway i still believe this is an issue solved by a general linux tech and not the developers of vicidial.

just my 2 cents
Vicibox 5 from standard.iso | Vicidial 2.8-409a Build 130809-1410 | SVN Rev 2015 | Asterisk 1.8.23.0-vici | Cluster | No Digium/Sangoma Hardware | No Extra Software After Installation | Supermicro | 2x QuadCore XEON 3.2Ghz
Janky
 
Posts: 85
Joined: Wed Jan 06, 2010 10:03 pm
Location: Tampa


Return to ViciDialNow - GoAutoDial

Who is online

Users browsing this forum: No registered users and 37 guests

cron