vicidial.org

Today i installed Vicibox 7.0.4, after installation when i rebooted server and tried to open asterisk i am getting following error

Unable to connect to remote asterisk (does /run/asterisk/asterisk.ctl exist?)

I am not able to open asterisk , please update how can i fix it, Thanks.

Version: 2.14b0.5
SVN Version: 3114
DB Schema Version: 1571
DB Schema Update Date: 2019-06-27 13:03:36
Password Encryption: DISABLED - S1 - C1
Auto User-add Value: 101
Recording Prompt Count: 0
Install Date: 2019-06-27

This is error when i try to start asterisk

/etc/init.d/asterisk status
Checking for asterisk unused
asterisk.service - Asterisk PBX
Loaded: loaded (/usr/lib/systemd/system/asterisk.service; disabled)
Active: failed (Result: exit-code) since Thu 2019-06-27 14:32:12 EDT; 1min 17s ago
Process: 3689 ExecStart=/usr/sbin/asterisk -fn (code=exited, status=1/FAILURE)
Main PID: 3689 (code=exited, status=1/FAILURE)

1) I can see you're trying, you posted your full Vicibox Installer version, and you posted MOST of your "Vicidial Version with build", the only thing missing is ... "with build". Please be sure to include that build information. It matters.

2) WHY did you install with Vicibox 7.0.4 instead of 8.1.2 if you installed today? (Not saying it's a bad thing, but if you chose an old version on purpose, often the reason for that choice will provide information that assists me with helping you and will expose a situation that contributes to your problem.)

3) During installation, you first use the PDF from Vicibox.com. After successful installation you would switch to the Vicidial Manager's Manual. But since this is part of the installation process (asterisk running is a pre-requisite, install is not complete ...), I have to ask if there were any errors during your installation? Or anything outside the realm of the installer (like ... restoring an old DB?)

4) Are the screens running?

Code: Select all

cat /etc/astguiclient.conf | grep VARactive_keepalives
screen -list


5) Will asterisk actually run if you ask it to? (Note that this is merely a test)

Code: Select all

/usr/sbin/asterisk -vvvvvvvvvvvvvvvvvvvvvgcT

6) Asterisk is NOT a service in a Vicidial system. Getting the asterisk service's status is of no value. Vicidial runs asterisk in a "screen". Attaching to that screen will provide you with "the asterisk console" that is inaccessible if asterisk is run as a service. If asterisk is run as a service you can "attach to remote asterisk", but that remote console does not show errors from perl and php agi scripting. Scripting errors are ONLY visible on the "non-remote" console.

Got the mentioned error when i run this command: /usr/sbin/asterisk -vvvvvvvvvvvvvvvvvvvvvgcT

/usr/sbin/asterisk -vvvvvvvvvvvvvvvvvvvvvgcT
[Jun 27 14:52:32] Asterisk 11.25.1-vici, Copyright (C) 1999 - 2013 Digium, Inc. and others.
[Jun 27 14:52:32] Created by Mark Spencer <markster@digium.com>
[Jun 27 14:52:32] Asterisk comes with ABSOLUTELY NO WARRANTY; type 'core show warranty' for details.
[Jun 27 14:52:32] This is free software, with components licensed under the GNU General Public
[Jun 27 14:52:32] License version 2 and other licenses; you are welcome to redistribute it under
[Jun 27 14:52:32] certain conditions. Type 'core show license' for details.
[Jun 27 14:52:32] =========================================================================
[Jun 27 14:52:32] [ Initializing Custom Configuration Options ]
[Jun 27 14:52:32] ERROR[1968]: logger.c:1327 init_logger: Errors detected in logger.conf. Default console logging is being used.
ASTdb initialization failed.

This error:

/usr/sbin/asterisk -vvvvvvvvvvvvvvvvvvvvvgcT
[Jun 27 14:54:16] Asterisk 11.25.1-vici, Copyright (C) 1999 - 2013 Digium, Inc. and others.
[Jun 27 14:54:16] Created by Mark Spencer <markster@digium.com>
[Jun 27 14:54:16] Asterisk comes with ABSOLUTELY NO WARRANTY; type 'core show warranty' for details.
[Jun 27 14:54:16] This is free software, with components licensed under the GNU General Public
[Jun 27 14:54:16] License version 2 and other licenses; you are welcome to redistribute it under
[Jun 27 14:54:16] certain conditions. Type 'core show license' for details.
[Jun 27 14:54:16] =========================================================================
[Jun 27 14:54:16] [ Initializing Custom Configuration Options ]
[Jun 27 14:54:16] ERROR[2156]: logger.c:1327 init_logger: Errors detected in logger.conf. Default console logging is being used.
ASTdb initialization failed.
[Jun 27 14:54:16] WARNING[2156]: db.c:255 db_open: Unable to open Asterisk database '/var/lib/asterisk/astdb.sqlite3': unable to open database file

looks like a bad install. Neither of those errors is serious, of course, but the fact that your fresh install has any errors is an indication that your install did not go as planned.

You can fight each of those errors one at a time, but there may be hundreds of them. I'd start over if this were my install.

For clarity: What instructions were you using during your installation? Did you make any adjustments to your system outside the PDF from Vicibox.com? If so, when you re-install ... DON'T make any adjustments. After you finish with the PDF from Vicibox.com, switch to The Vicidial Manager's Manual (free on EFLO.net, but I recommend the paid version if you intend to make a living with this server! lol). Start at page one. Do not skip anything. Do not venture outside the manual. Once the system is verified fully operational, make a backup. THEN you can play with customizations (assuming you know how to restore from your backup in case you break anything).

Note that reinstalling several times is not a bad thing. Every time you run through, it'll make more sense. If you install a dozen times, it'll be downright simple.

ok i will reinstall Vicidial 8.1.2 in this case, Thanks.

If you have a virtualized system (virtualbox, vmware, vsphere) available, that's excellent for practice installs. Don't use it in production (at load, it'll fail), but it's great for a single agent for sandbox/development/testing. And perfect for re-installing a bunch of times to become familiar with the product.