Scott,

The ownership and permissions look ok.  I changed them anyway, but still
no help.

I'm still getting the read error running sipxecs-setup on the secondary
server.

The files appear to be there (but if the tar file should be here as
well, I don't see it):

[r...@hyipt1 tmp]# ls -la initial-config/hyipt2.hyoung.voice/etc/*
-rw-r--r-- 1 sipxchange sipxchange  703 Nov 30 18:28
initial-config/hyipt2.hyoung.voice/etc/named.conf
-rw-r--r-- 1 sipxchange sipxchange  719 Nov 30 18:28
initial-config/hyipt2.hyoung.voice/etc/ntp.conf
-rw-r--r-- 1 sipxchange sipxchange   61 Nov 30 18:28
initial-config/hyipt2.hyoung.voice/etc/resolv.conf

initial-config/hyipt2.hyoung.voice/etc/ntp:
total 12
drwxr-xr-x 2 sipxchange sipxchange 4096 Nov 30 18:28 .
drwxr-xr-x 4 sipxchange sipxchange 4096 Nov 30 18:28 ..
-rw-r--r-- 1 sipxchange sipxchange   21 Nov 30 18:28 step-tickers

initial-config/hyipt2.hyoung.voice/etc/sipxpbx:
total 16
drwxr-xr-x 2 sipxchange sipxchange 4096 Nov 30 18:28 .
drwxr-xr-x 4 sipxchange sipxchange 4096 Nov 30 18:28 ..
-rw-r--r-- 1 sipxchange sipxchange  250 Nov 30 18:28 domain-config
-rw-r--r-- 1 sipxchange sipxchange   65 Nov 30 18:28
sipxsupervisor-config

Thanks,

jim





> On Sun, 2009-11-29 at 12:18 -0800, jnolen wrote:
> > Greetings,
> > 
> > I just upgraded a system from 10.0.3 to 4.0.4 (4.0.4-017289
> > 2009-11-19T18:15:29 ecs-centos5).  Upgrade of primary (master) system
> > was uneventful.  Upgrade was done incrementally passing through 4.0.1,
> > 4.0.2, and finally 4.0.4.
> > 
> > Attempted to deploy a secondary server:
> > 
> > Added secondary server to Primary.
> > Secondary server installed using an iso install, and got the following
> > error:
> > 
> > Invalid configuration returned from                          รข
> > 
> > https://hyipt1.hyoung.voice:8443/sipxconfig/initial-config/hyipt2.hyoung.voice
> > exception tarfile.ReadError
> > file could not be opened successfully
> 
> Check the permissions on the directory
> 
>   /var/sipxdata/tmp/initial-config
> 
> it should be owned and writeable by the user 'sipxchange'; if it is not,
> then fix it (as root):
> 
>   chown -R sipxchange:sipxchange /var/sipxdata/tmp/initial-config
>   chmod -R ug+w /var/sipxdata/tmp/initial-config
> 
> (I've seen this on upgrades before and have not been able to figure out
> where this gets messed up)
> 

_______________________________________________
sipx-users mailing list [email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
sipXecs IP PBX -- http://www.sipfoundry.org/

Reply via email to