Fixed in latest 4.6.0-233 CentOS RPMs.
thanks~
On Jul 30, 2012, at 14:11 , Kurt Albershardt wrote:
Created http://track.sipfoundry.org/browse/XX-10340
Quite likely a release blocker, but not my call.
___
sipx-users mailing list
mongo doesn't look right...
try:
bash -x /usr/bin/mongodb-repair
/etc/init.d/mongod start
On Mon, Jul 30, 2012 at 2:27 PM, Kurt Albershardt k...@nv.net wrote:
sipxconfig.log and tail of sipxagent.log (which was 2 MB) attached.
Updated via yum this morning and invoked 'sipxecs-setup
Somehow you might have double quotes around your host name. When
running sipxecs-setup, did you put double quotes around your host
name? Can you send me /etc/sipxpbx/sipxconfig.properties?
On Mon, Jul 30, 2012 at 2:27 PM, Kurt Albershardt k...@nv.net wrote:
sipxconfig.log and tail of
Attached, and shows double quotes. I'm guessing this is also the cause of what
I reported earlier:
One more minor glitch at the end of the script - looks like extra quotes in
the URL:
In a few more minutes you will be able to access the administration
interface from your web browser at
did not add quotes -- and the URL at the end still has them:
[root@sipx ~]# sipxecs-setup --reset-all
This will wipe all configuration data from this server. Are you sure? [ enter
'y' or 'n' ] : y
Network settings:
IP address : 192.168.X.26
Would you like to configure your system's network
perhaps re-run the script and manually input the host and sipdomain
(instead of hitting enter) to see if it removes the quotes.
On Mon, Jul 30, 2012 at 2:59 PM, Kurt Albershardt k...@nv.net wrote:
did not add quotes -- and the URL at the end still has them:
[root@sipx ~]# sipxecs-setup
Just tried a couple variants of that - first one left the host and domain at
default and then I manually typed everything else -- that produced the same
result at the end:
https://sipx.domain.com;
Note spurious double quotes show in the proposed defaults:
Enter just the host name of this
On Mon, Jul 30, 2012 at 3:11 PM, Kurt Albershardt k...@nv.net wrote:
thanks~
We scrape host and domain from
/etc/sysconfig/network
so it probably *was* wrong there too. That value comes from using the
network config tool we launch from the setup-setup script. I say was
because we in turn
i might venture a guess that re-running the script and taking the defaults
are doing this. if so, it would be incorrect and unwanted behavior. i think
in order to open a jira, it needs to be tried against a fresh install and
all patched up prior to running, then re-running the script. if it
On Jul 30, 2012, at 13:22 , Douglas Hubler wrote:
We scrape host and domain from
/etc/sysconfig/network
so it probably *was* wrong there too. That value comes from using the
network config tool we launch from the setup-setup script. I say was
because we in turn write it back if
Happened the first time I ran the script, FWIW.
Install was updated 2-3x before I ran setup (due to dependency glitches) so
it's not a good test case.
I'll re-install on a clean VM and try again.
On Jul 30, 2012, at 13:26 , Tony Graziano wrote:
i might venture a guess that re-running the
First time running setup script on a freshly built Centos 6 VM:
[root@sipx ~]# cat /etc/sysconfig/network
NETWORKING=yes
GATEWAYDEV=venet0
NETWORKING_IPV6=yes
IPV6_DEFAULTDEV=venet0
HOSTNAME=sipx.domain.com
[root@sipx ~]# sipxecs-setup
Network settings:
IP address : 192.168.X.26
Would you
Created http://track.sipfoundry.org/browse/XX-10340
Quite likely a release a blocker, but not my call.
On Jul 30, 2012, at 14:05 , Kurt Albershardt wrote:
First time running setup script on a freshly built Centos 6 VM:
[root@sipx ~]# cat /etc/sysconfig/network
NETWORKING=yes
check/send along sipxagent.log and sipxconfig.log
On Sat, Jul 28, 2012 at 4:07 PM, Kurt Albershardt k...@nv.net wrote:
Ran a 'yum update' on an unconfigured 4.6 (installed on 7/25, the one with
the unmet Homer dependency) and got only a couple of OS updates.
Running 'yum groupupgrade
Ran a 'yum update' on an unconfigured 4.6 (installed on 7/25, the one with the
unmet Homer dependency) and got only a couple of OS updates.
Running 'yum groupupgrade sipxecs' yielded 271 updates (now at 4.6.0.233)
Did a 'yum clean all' and restarted, then ran sipxecs-setup.
Five minutes later,
15 matches
Mail list logo
