Illegal instruction

[baka-na]

Hi All,

I have installed Vicibox v.4.0.3 on an HP Proliant DL 380 G4 with Dual Intel Xeon Processor @ 3.40Ghz. Installation went well but asterisk won't start. Everytime I issue asterisk -rvvvvv it wil give me an Illegal instruction. Doing a safe_asterisk will give me:

Asterisk ended with exit status 132
Asterisk exited on signal 4.
cat: /var/run/asterisk.pid: No such file or directory
Automatically restarting Asterisk.
mpg123: no process found
/usr/sbin/safe_asterisk: line 118: 4912 Illegal instruction (core dumped) nice -n $PRIORITY ${ASTSBINDIR}/asterisk -f ${CLIARGS} ${ASTARGS} &>/dev/${TTY} < /dev/${TTY}

and dmesg produce:

[ 3630.672388] asterisk[4976] trap invalid opcode ip:44f21e sp:7fff197455c0 error:0 in asterisk[400000+123000]

Has someone encountered this? I tried googling it and saw some recompile asterisk suggestions.

Please kindly advise. Thanks in advance!

[williamconley]

I have encountered this a few times. It usually has to do with a bad CD (MD5 shows it burned wrong) or a bad download .iso (once again, MD5 shows the .iso is not valid). I've resolved this a few times with a recompile of asterisk ... but that is usually just the start of the battle. Then there invariable turns out to be other problems which also need to be chased down.

If you are extremely unlucky it will be a driver issue with the proliant (if it is too new and cool, the drivers may not be properly debugged yet!).

So: Check your .iso download against the MD5 (google will acquire you an app with which to do this, the MD5 can be acquired by clicking on the link that gave you the .iso file and removing the filename, you will then find the MD5 right next to the .iso with the same name). After verifying the .iso, be sure you tell the .iso burner to verify the disk after burning.

If you do this with 4.0.3 and still cannot get a good install, consider 32bit instead of 64 bit (drivers will be different) and then even consider GoAutoDial as a last resort (you can upgrade via SVN after the install to get the same Vicidial version).

Of course, you can recompile asterisk/libpri/dahdi and see if your problem goes away ... but you may end up fighting a fairly long battle that way. There are several locations with instructions for recompiling, because if you upgrade your kernel after installation a recompile of these apps is necessary.

[baka-na]

Thanks William!

Actually I have tried installing GoAutodial v 2.1 and it install fine and no issue whatsoever. I want this server to be a part of a cluster with the DB server the one on my sig.

The HP server is fairly old, I think it is 3-4 years old. Haven't checked the MD5 sum yet, will try to do that. Right now I'm trying to reinstall asterisk itself but, as you said, it is not pretty.

Thanks again william.

[baka-na]

Hi William,

md5sum seems not the issue as I had the same with the link provided.

Also I tried installing the 32bit version, however, the installer did not detect the array on my server.

[williamconley]

I had the same with the link provided

does this mean you checked the .iso (before burning the cd) or the cd with "verify cd after burning" or both? And what MD5 value did you use to check the .iso value against? the MD5 value downloaded from the vicidial group?

[baka-na]

Yes on both. Md5 checked against the value provided by the Vicidial group.

[williamconley]

Did you re-try the original install again (just for the sake of argument?) Perhaps with a new CD drive?

Of course, you can always install GoAutoDial (or scratch) or an older Vicibox version (3.1.15 is good ...). If you use 3.1.15, it will still cluster for you. If you use scratch or goautodial, there is always the PoundTeam Multi-Server manual

[baka-na]

Hi William,

Thanks for replying and sorry if i am taking a bit off of your time. Appreciated,

Will probably try that tomorrow. If I remember it right, I also did an install of older Vicibox. There were some issues too but can't remember it. I think it has only few screens when doing screen -list. On clustering, I want to cluster this server to the running server I did. Will the older version allow it?

Again, thanks much!

[williamconley]

Yes, the older version will cluster to an existing system. But remember that they must all have the same code-base. So be sure to select SVN and update to the latest SVN code and OS during installation. And of course, be sure your installation is also at the latest SVN code (or you have to manually modify the SVN revision to the desired level before vicibox-install).

[baka-na]

Ok. Noted on that.

Done installation of Vicibox Redux 3.1 to this server. Will try to cluster it to an existing Vicibox 4.0.1.

Thanks for the assistance.

[williamconley]

"svn info" in the /usr/src/asterisk/trunk folder will give the revision level. Be sure they match!

[baka-na]

Yep. They're match.

Would there be any conflict or problem if I'll be connecting this to an already-running Vicidial?

[williamconley]

As long as you are adding a dialer or web, and not a DB (which obviously causes conflict! LOL). We've added while clients were using their dialers many times without any interruption in services.

But DO A BACKUP FIRST. As Always. (The backup, of course, will cause interruption ...)

[baka-na]

Ok. Thanks a lot William. Appreciated. I think I'll try to do some trial run on how to properly connect a dialer then I'll be adding this one to our existing server.

[williamconley]

VMware and vSphere are excellent free tools to allow you to practice these things.