vicidial.org

Hi again!

I am a little confused, today i got a major issue after a reboot

i described the problem here:

viewtopic.php?f=4&t=33404

At the end seems like the database was broken.

Before, a few weeks ago i had another issue with the recordings, and it also was the database.


viewtopic.php?f=4&t=33208

And that is why i am here seeking for advice, what could be causing the database to get broken?


Vicibox 6.0 | HARDWARE HP DL360E-G8 w/ Raid 5 (only 3 SAS disks) | VERSION: 2.10-450a BUILD: 140822-1034 | MySQL Server version: 5.5.33-MariaDB-log openSUSE package | Asterisk 1.8.29.0-vici

BTW mysqlcheck does not detect any problem, but the only way to fix the problems i describe in the links was to re-install with no-db :/

Given that you've reinstalled. I would suspect a hardware problem. In paticular the disk(s) and the memory.

1) Title says broken DB, but you theoretically resolved the issue by reinstalling without a DB? Wouldn't that indicate that the db is NOT the problem?

2) What do you mean by "reinstall with no db", exactly?

3) While you refer to the problem in another post, I've often found that the present problem must be documented and posted (from the present system experiencing the problem) to avoid "oops, I just thought it was the same problem, because the symptom appeared to be similar". Please post a precise description of the problem along with any CLI output to demonstrate the symptom, from This System

4) At this point, I am not sure how this system was assembled, but I get the impression that this system's DB originated on another system and has since been "brought over" and possibly upgraded (more than once?). Please enlighten us on this as upgrades have been known to cause issues.

5) Please verify that your asterisk version in admin->servers matches the asterisk version returned by asterisk -V

Sorry for this really confusing post, i was really in a hurry and i realize that i said a lot of non-sense

williamconley wrote:1) Title says broken DB, but you theoretically resolved the issue by reinstalling without a DB? Wouldn't that indicate that the db is NOT the problem?

If i do fresh install it works, if i restore the backup database it wont, so the only difference is the database.

williamconley wrote:2) What do you mean by "reinstall with no db", exactly?

I meant i reinstall without restoring up the database. i just re-run the vicibox-install script.

williamconley wrote:3) While you refer to the problem in another post, I've often found that the present problem must be documented and posted (from the present system experiencing the problem) to avoid "oops, I just thought it was the same problem, because the symptom appeared to be similar". Please post a precise description of the problem along with any CLI output to demonstrate the symptom, from This System

each post had their own examples.

williamconley wrote:4) At this point, I am not sure how this system was assembled, but I get the impression that this system's DB originated on another system and has since been "brought over" and possibly upgraded (more than once?). Please enlighten us on this as upgrades have been known to cause issues.

You are right, at first i was a Vicibox 5.0, the the recordings stop stop working and we re-install with Vicibox 6.0 and restore the database, but the problem persist.
We had to perform a fresh install and create again users, phones, campaigns and everything, so at this point it was like a fresh install.
We made an upgrade via zypper only asterisk and dahdi were upgraded, but we didnt reboot
After we reboot, i start having the NO ONE IS IN YOUR SESSION problem i tried everything to solve it, then i made a backup and re-install (yes, again) before restoring the backup i made a test and it worked, after i restore the backup i got the same error again.

The only way i got it working without losing all my info, was to create a backup without creating the table --no-create-info and with --insert-ignore, this way, i got the fresh install and only INSERT my data, i got it working this way.

williamconley wrote:5) Please verify that your asterisk version in admin->servers matches the asterisk version returned by asterisk -V

Yes, i doubled check that.

covarrubiasgg wrote:Sorry for this really confusing post, i was really in a hurry and i realize that i said a lot of non-sense

williamconley wrote:1) Title says broken DB, but you theoretically resolved the issue by reinstalling without a DB? Wouldn't that indicate that the db is NOT the problem?

If i do fresh install it works, if i restore the backup database it wont, so the only difference is the database.

This tells me that the problem is your "restore of the DB". After you perform this "restore", do you upgrade the DB to match the vicidial software?

williamconley wrote:This tells me that the problem is your "restore of the DB". After you perform this "restore", do you upgrade the DB to match the vicidial software?

Yes, i always verify that the DB schema is in the same version, actually i always upgrade to match svn versions.

You were very close, but you said it in a way that still makes me nervous.

You said you "verify" the db schema, but you should be "upgrading" the db to make it match, not just verifying.

You should enter the commands you issues to perform your DB upgrade. Just to be sure.