I'm trying to decide if I need to open an issue for this or if it's just a misconfiguration issue of some sort. Here's the situation - yesterday morning, I downloaded asterisk 1.8.19.1 and installed it on a fresh CentOS 5.8 installation and got a shell of a basic asterisk install setup (minimum required configuration files, etc, with no dialplan or sip peers setup yet). In the afternoon, I got the notification that asterisk 1.8.20.0 had been released, so today, I downloaded the latest 1.8-current.tar.gz and compiled and installed it (./configure, make menuselect and choose all the same options as my previous install, make, make install).
Now, when I start the asterisk service using "service asterisk start" from the command line, this is the output: [root@pbx ~]# service asterisk start Unable to connect to remote asterisk (does /var/run/asterisk/asterisk.ctl exist?) Starting asterisk: However, the /var/run/asterisk/asterisk.ctl file is being created and the process is starting: [root@pbx ~]# ls -lh /var/run/asterisk/ total 4.0K srwxr-xr-x 1 root root 0 Jan 16 12:07 asterisk.ctl -rw-r--r-- 1 root root 6 Jan 16 12:07 asterisk.pid However, I'm no longer getting the usual splash message when I connect to the asterisk console...this is what I get: [root@pbx ~]# asterisk -r Verbosity is at least 3 pbx*CLI> I don't have any peers setup yet, or even any dialplan configured to test, but when I go through the logs, I don't find any errors or warnings that I'm not expecting. I've gone back to the asterisk 1.8.19.1 install and everything works as expected (no error messages, full splash about license / version on connection to console, etc). I performed make clean in my 1.8.20 source directory, then ./configure, make menuselect, make, make install, and even make config, and I'm still seeing this message pop up when restarting / starting the service. I went through the CHANGELOG.TXT for 1.8.20.0 and it appears there are some items talking about changing the way the process starts up (commit r376428), but I'm not enough of a coder to understand if those would cause what I'm seeing. Is anyone else seeing this issue? Should I open an issue on the tracker? Anyone see something obvious I missed? -- Thanks, --Warren Selby, dCAP http://www.SelbyTech.com <http://www.selbytech.com>
-- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
