"Sorry, you are not allowed to login to this campaign"...

[ScissorHill]

Hello all,

System configuration:

• Vicidial VERSION: 2.11-476a
• BUILD: 150302-0945
• Asterisk 1.8.32.3
• CentOS 6.6
• Linux Kernel 2.6.32-642.1.1.el6.x86_64

(That's all the info I have access to at the moment - apologies if I've missed something pertinent, and please let me know how to get that from CLI!)

The system was working fine until a while ago. Suddenly, newly added users are seeing the

Sorry, you are not allowed to login to this campaign: <campaign id>

error message. Searching the forum reveals that this is most commonly encountered after an upgrade, but no upgrade has happened of late.

Any kind of help in resolving this issue, and suggestions how to avoid it, would be much appreciated. Thanks in advance...!

[mflorell]

Could be a crashed table or just a permission change in their User Groups setting.

[ScissorHill]

Thanks! I should have mentioned earlier: users are being added through the add_user API call. So it's unlikely to be something to do with User Group settings.

If it's a crashed table, any pointers on how it could be diagnosed and repaired - safely?

[mflorell]

try running this script:

# /usr/share/astguiclient/AST_DB_check_tables.pl --help
allowed run time options:
[--quick] = run test in QUICK mode, may not catch all issues
[--email-list=test.com:test2.com] = send email results to these addresses
[--email-sender=vicidial] = sender for the email results
[--test] = test
[--quiet] = quiet
[--debug] = verbose debug messages
[--debugX] = extra verbose debug messages

[BoydSmith]

Thanks for the script mflorell, worked perfectly.

[ScissorHill]

Sorry for the delay in responding, mflorell...!

I can't find the AST_DB_check_tables.pl script under /usr/share/astguiclient. Is this something that's available in a later version (as mentioned above, this server has Vicidial VERSION: 2.11-476a, BUILD: 150302-0945).

If so, would it suffice to download just this one script and run it?

I've been trying to reproduce this issue. It seems to be intermittent, and thus tricky.
Thanks once again.

[mflorell]

Just upgrade to the most recent svn/trunk version and it will be there.

[ScissorHill]

Just upgrade to the most recent svn/trunk version and it will be there.

I understand it makes sense to upgrade to the latest version, but this might take a while, as it's a production server right now. Question: if I were to just copy this script from the SVN checkout and run it on the server, would it be a bad idea?

Also, I find that the error occurs every time a new user is created. It disappears as soon as I go to the newly created user's user group, and just hit 'submit' without actually changing anything...! Which is actually a bit concerning.

Any help in this regard would be appreciated.

[williamconley]

Code: Select all

mysql asterisk -e "show table status where comment like '%crashed%'" --user=cron -p1234

If it identifies a crashed table, substitute that table for this one:

Code: Select all

mysqlcheck --auto-repair  --user=cron -p1234 asterisk vicidial_log_extended

Check ALL tables (after hours):

Code: Select all

mysqlcheck --all-databases --auto-repair --user=cron -p1234