sockets missing screen -ls help pls

[niwang09]

[root@localhost astguiclient]# screen -ls
There are screens on:
2659.ASTconf3way (Detached)
2653.ASTVDadapt (Detached)
2656.ASTfastlog (Detached)
2608.asterisk (Detached)
2603.astshell20150703081459 (Detached)
5 Sockets in /var/run/screen/S-root.

[striker]

Hi

Post more information like
what you have installed 1. goatuodial or 2. vicibox or 3. scratch installation of vicidial/goatuodial.
is it a production dialler or fresh installation

[williamconley]

[root@localhost astguiclient]# screen -ls
There are screens on:
2659.ASTconf3way (Detached)
2653.ASTVDadapt (Detached)
2656.ASTfastlog (Detached)
2608.asterisk (Detached)
2603.astshell20150703081459 (Detached)
5 Sockets in /var/run/screen/S-root.

You are today's lucky winner of ...

1) Welcome to the Party!

2) As you are obviously new here, I have some suggestions to help us all help you:

When you post, please post your entire configuration including (but not limited to) your installation method and vicidial version with build.

This IS a requirement for posting along with reading the stickies (at the top of each forum) and the manager's manual (available on EFLO.net, both free and paid versions)

You should also post: Asterisk version, telephony hardware (model number is helpful here), cluster information if you have one, and whether any other software is installed in the box. If your installation method is "from scratch" you must post your operating system and should also post the .iso version from which you installed your original operating system. If your installation is "Hosted" list the site name of the host.

If this is a "Cloud" or "Virtual" server, please note the technology involved along with the version of that techology (ie: VMware Server Version 2.0.2). If it is not, merely stating the Motherboard model # and CPU would be helpful.

Similar to This:

Vicibox X.X from .iso | Vicidial X.X.X-XXX Build XXXXXX-XXXX | Asterisk X.X.X | Single Server | No Digium/Sangoma Hardware | No Extra Software After Installation | Intel DG35EC | Core2Quad Q6600

3) Crashed table? Full HD? Missing sql server? Dunno. But if you identify the Missing Scripts and attempt to start them with --debugX, I bet they'll tell you what's up.

Happy Hunting!

[niwang09]

Hi striker,

thanks for the reply

its a scratch install from http://ray-solomon.com/vicidial.html
centos 6.6(final)
fresh installed
asterisk 1.8
dahdi-linux-complete-current.tar.gz
libpri-1.4-current

[striker]

did you run the below command ie the last step before the reboot.
/usr/share/astguiclient/ADMIN_update_server_ip.pl --old-server_ip=10.10.10.15


also did you disabled the firewall and selinux in centos.
if not disable both and reboot.

[niwang09]

yup i did /usr/share/astguiclient/ADMIN_update_server_ip.pl --old-server_ip=10.10.10.15 and disabled the firewall and selinux in centos. but ill try it again

[williamconley]

yup i did /usr/share/astguiclient/ADMIN_update_server_ip.pl --old-server_ip=10.10.10.15 and disabled the firewall and selinux in centos. but ill try it again

1) Have you tried starting any of the missing scripts manually? To get the error/crash?

2) Why did you install manually instead of using an .iso installer from Vicibox.com? (If you MUST have CentOS, Goautodial.org... and if you can't use an .iso, use the Goautodial repository installation from their wiki?)

3) Just so you know: It can take weeks to uncover an unusual installation problem with a Manual Installation if you're not well-versed in Linux/Vicidial. It can take 30 minutes to install from an .iso or repositories ...

[niwang09]

thanks for the reply william , ived tried goautodial but icant make it work using bootable flashdrive it always says error downloading kickstart file . i got no cdrom

[striker]

show the content of the manager.conf file
ie vi /etc/asterisk/manager.conf

[williamconley]

thanks for the reply william , ived tried goautodial but icant make it work using bootable flashdrive it always says error downloading kickstart file . i got no cdrom

Goautodial has a package installation method. you start with CentOS and then use Gardo's wiki instructions to convert your plain vanilla centos into a goautodial installation by loading his packages. It's actually pretty easy, too, from what I understand.

Goautodial may not be as recent as Vicibox, but the code IS stable. And you CAN uprade to the latest Vicidial code after your system is up and running. So it is entirely possible to have CentOS and the latest Vicidial using Gardo's installation system. When you upgrade, you dump all his customizations, of course. Some perceive that as a good thing, some Like those customizations. Up to you.

[patelsaheb]

I have face same issue.
I have installed vicidial scratch installation having asterisk version 11.25.3 dahdi 2.9.1 and centos7.

when i show screen -ls it show like below

There are screens on:
26957.ASTconf3way (Detached)
26928.ASTVDadapt (Detached)
1740.ASTfastlog (Detached)
1722.ASTupdate (Detached)
1669.asterisk (Detached)
1654.astshell20181124052128 (Detached)
6 Sockets in /var/run/screen/S-root.

how to resolved quickly...

thank you

[williamconley]

1) Always include a link to the instructions you used for installation.

2) You have not yet posted all the information to demonstrate something is wrong. You've stated screens are missing and posted the ones that are running: But "These should be running" has not been posted, so we can't be certain that the system is broken. To check which screens should be running: VARactive_keepalives in /etc/astguiclient.conf. Post the value for that field.

3) The other screens should be starting and crashing. Post the error from one of the missing screen's crashes. The logs from these are in /var/log/astguiclient IF "Admin->Servers->(your server)" has FILE for the log setting so those logs are created. A reboot may be needed.

4) Another method to check the missing screens is to start up the admin keepalive script in debug mode.

Code: Select all

perl /usr/share/astguiclient/ADMIN_keepalive_ALL.pl --debugX

This file also has the code to manually start each of these screens so you can manually fire each one up and see the crash first-hand.

5) Note that some of the screens depend upon each other, so if a screen checks for another screen, then shuts down because it's not running ... try the missing screen next. Doesn't hurt to check them all before tracing any of the crashes: Choose the one with the easiest sounding failure.

6) WHY (seriously) did you not install your system with the .iso installer from Vicibox.com or GoAutodial.com OR the wiki instructions on GoAutodial.com showing how to turn a "stock" CentOS into a Goautodial server by using repositories? There has been a huge amount of time invested in making all those available, not using them and installing line-by-line for your first server is like building your own car before learning to drive. Educational, to be sure, but ... why? Often, knowing the reasoning behind that choice is helpful so we know where you stand in the business models using Vicidial.

[patelsaheb]

Thanks for quick reply.

i have checked logs for remoteagent screen content as below

2018-11-27 07:59:13|HANGING UP||
2018-11-27 07:59:13|CLOSING DB CONNECTION||
2018-11-27 08:00:02|PROGRAM STARTED|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
2018-11-27 08:00:02|LOGGED INTO MYSQL SERVER ON 1 CONNECTION||
2018-11-27 08:00:02|HANGING UP||


is there issue in that or not?

thank you...