Cannot get a stable working version running

I have a new box that I’ve commandeered. This is an Acer Veriton i3 L4618 small form factor CPU. I have stable versions of older distros running on similar boxes in other offices.

Here’s my problem. I’ve burned a cd for the 64bit and the 32bit version of the install for the 1.810.210.57.iso. The 32bit iso would get the kickstart message. The 64bit version would get through the installation, Id do a full configuration and then 72 hours later the dialing would fall apart. (This is on the same exact hardware that I mentioned above) I get a short period of time where everything is fine, then everything starts falling apart and outbound calls start failing. To reinforce the network stability concerns, I have another office right next door running the same firewall, the same ISP, the same POE Switch, practically identical that has been up for almost 4 months with zero issues.

This is happening on the last 2 boxes I tried to install with the latest and greatest flavor (Thursday of last week I downloaded and installed) literally right out of the box. Same configuration. Literally 6 phones, 4 right groups, an IVR, 1 conference line, 3 extensions with voicemail. Simple configuration. Nothing to brag about.

These are the lines that are show up as red, orange or blue in order… I left out the rest of the stuff because it wouldn’t post with all that info.

Again, keep in mind that I’ve done this installation with older flavors of the distro on near identical hardware and those installations are stable and problem free. Those distros are no longer supported and my older cd will not let me install them as they are off the freepbx radar.

please help me. I’m loosing my mind. (doesn’t help that I’m currently on a 10 day fast… yes I’m serious) Thank you guys!

[2012-04-23 20:01:50] DEBUG[3051] xmldoc.c: Cannot find variable ‘description’ in tree ‘MEETME_INFO’
[2012-04-23 20:01:50] VERBOSE[3051] pbx.c: == Registered custom function ‘MEETME_INFO’
[2012-04-23 20:01:50] VERBOSE[3051] loader.c: app_meetme.so => (MeetMe conference bridge)
[2012-04-23 20:01:50] VERBOSE[3051] pbx.c: == Registered custom function ‘DEVICE_STATE’
[2012-04-23 20:01:50] VERBOSE[3051] pbx.c: == Registered custom function ‘HINT’
[2012-04-23 20:01:50] VERBOSE[3051] loader.c: func_devstate.so => (Gets or sets a device state in the dialplan)
[2012-04-23 20:01:50] VERBOSE[3051] config.c: == Parsing ‘/etc/asterisk/cdr.conf’: [2012-04-23 20:01:50] VERBOSE[3051] config.c: == Found
[2012-04-23 20:01:50] WARNING[3051] cel_manager.c: Failed to load configuration file. CEL manager Module not activated.
[2012-04-23 20:01:50] WARNING[3051] cdr_manager.c: Failed to load configuration file. Module not activated.
[2012-04-23 20:01:50] ERROR[3051] cdr_custom.c: Unable to load cdr_custom.conf. Not logging custom CSV CDRs.
[2012-04-23 20:01:50] VERBOSE[3051] loader.c: cdr_custom.so => (Customizable Comma Separated Values CDR Backend)
[2012-04-23 20:01:50] ERROR[3051] cdr_syslog.c: Unable to load cdr_syslog.conf. Not logging custom CSV CDRs to syslog.
[2012-04-23 20:01:50] ERROR[3051] cel_custom.c: Unable to load cel_custom.conf. Not logging CEL to custom CSVs.

[2012-04-23 20:01:50] ERROR[3051] pbx_dundi.c: Unable to load config dundi.conf

[2012-04-23 20:01:50] NOTICE[3051] chan_ooh323.c: Unable to load config ooh323.conf, OOH323 disabled

[2012-04-23 20:01:50] NOTICE[3051] pbx_ael.c: Starting AEL load process.
[2012-04-23 20:01:50] NOTICE[3051] pbx_ael.c: File /etc/asterisk/extensions.ael not found; AEL declining load

[2012-04-23 20:01:50] ERROR[3051] res_clialiases.c: res_clialiases configuration file ‘cli_aliases.conf’ not found

[2012-04-23 20:01:50] ERROR[3051] ais/clm.c: Could not initialize cluster membership service: Try Again

[2012-04-23 20:01:50] WARNING[3051] res_phoneprov.c: Unable to load users.conf

[2012-04-23 20:01:50] ERROR[3051] app_amd.c: Configuration file amd.conf missing.

[2012-04-23 20:01:50] WARNING[3051] app_followme.c: No follow me config file (followme.conf), so no follow me

[2012-04-23 20:01:50] WARNING[3051] app_minivm.c: Failed to load configuration file. Module activated with default settings.

[2012-04-23 20:01:50] WARNING[3051] app_festival.c: No such configuration file festival.conf

[2012-04-23 20:01:51] ERROR[3051] chan_unistim.c: Unable to load config unistim.conf

[2012-04-23 20:01:51] NOTICE[3051] app_queue.c: No queuerules.conf file found, queues will not follow penalty rules

[2012-04-23 20:02:02] NOTICE[3447] manager.c: 127.0.0.1 tried to authenticate with nonexistent user ‘manager’
[2012-04-23 20:02:02] NOTICE[3447] manager.c: 127.0.0.1 failed to authenticate as ‘manager’
[2012-04-23 20:02:10] NOTICE[3461] manager.c: 127.0.0.1 tried to authenticate with nonexistent user ‘manager’
[2012-04-23 20:02:10] NOTICE[3461] manager.c: 127.0.0.1 failed to authenticate as ‘manager’
[2012-04-23 20:02:17] NOTICE[3464] manager.c: 127.0.0.1 tried to authenticate with nonexistent user ‘manager’
[2012-04-23 20:02:17] NOTICE[3464] manager.c: 127.0.0.1 failed to authenticate as ‘manager’
[2012-04-23 20:02:24] NOTICE[3467] manager.c: 127.0.0.1 tried to authenticate with nonexistent user ‘manager’
[2012-04-23 20:02:24] NOTICE[3467] manager.c: 127.0.0.1 failed to authenticate as ‘manager’

Everything you see is either a warning or notice and would not effect call processing.

The distro by default does not load a user called manager.

Please note below a distro I checked for reference I added the FOP2 and queuereport users.

Have you done anything non-stock to this box?


[[email protected] ~]$ su -
Password:
[[email protected] ~]# asterisk -r
Asterisk 1.8.4.2, Copyright (C) 1999 - 2010 Digium, Inc. and others.
Created by Mark Spencer <[email protected]>
Asterisk comes with ABSOLUTELY NO WARRANTY; type 'core show warranty' for details.
This is free software, with components licensed under the GNU General Public
License version 2 and other licenses; you are welcome to redistribute it under
certain conditions. Type 'core show license' for details.
=========================================================================
Connected to Asterisk 1.8.4.2 currently running on pioneer (pid = 13909)
Verbosity is at least 3
pioneer*CLI> manager show users

username
--------
admin
fop2
queuereport
aastra-xml
-------------------
4 manager users configured.
pioneer*CLI>
127 sip peers [Monitored: 84 online, 42 offline Unmonitored: 1 online, 0 offline]
pioneer*CLI>

Literally pulled it out of the packaging and installed the distro.

This also happened to an older enano microcomputer that I installed the same version distro on.

What happens is at a random time mayhem ensues. The log files show the call flow failing. I can try to get this back up and try to break it and pull the log files I guess.

Just so confused as to why the older versions worked without issue and this distro is giving me so much of a problem. The GUI is different too…

[2012-04-23 21:00:26] WARNING[3873] pbx.c: Unable to register extension ‘s’, priority 1 in ‘macro-outisbusy’, already in use
[2012-04-23 21:00:26] WARNING[3873] pbx.c: Unable to register extension ‘s’, priority 2 in ‘macro-outisbusy’, already in use
[2012-04-23 21:00:26] WARNING[3873] pbx.c: Unable to register extension ‘s’, priority 3 in ‘macro-outisbusy’, already in use
[2012-04-23 21:00:26] WARNING[3873] pbx.c: Unable to register extension ‘s’, priority 4 in ‘macro-outisbusy’, already in use

What does this mean? I’ve created no extension ‘s’

Several items, please stop posting these little one sentence comments. Focus and organize your thoughts. “Mayhem ensues” is a meaningless statement.

I told you in your other thread commands that will let us know if Asterisk is running. You also need to define what is happening. Are the phones loosing registration etc.

Also the warning messages are not important. Asterisk is very verbose. ‘s’ just means start and is the beginning of many functions.

Lastly, the GUI was updated in 2.10. I know you have been around in the last year. Is this your first time seeing the new version? I suggest you go back and read the last years blogs and news.

You will have to reproduce the issues if you want assistance.