David Saint wrote:
>> >> -----Original Message-----
>> >> From: [email protected]
>> >> [mailto:[email protected]] On Behalf Of Gmb
>> >> Sent: Wednesday, April 22, 2009 6:25 AM
>> >> To: [email protected]
>> >> Subject: [sipX-dev] Problem adding new server
>> >>
>> >> Hi,
>> >> I'm trying sipx 4.1.0-015219, I've encountered a problem
>> when I was
>> >> trying to add a new server as HA configuration:
>> >>
>> >> â
>> >>
>> https://tst-sipxm.tstcsi.it:8443/sipxconfig/initial-config/ â â
>> >> â tst-sipxs.tstcsi.it
>> >> â
>> >> â exception tarfile.ReadError
>> >> â
>> >> â file could not be opened successfully
>> >> â
>> >> â headers
>> >> â
>> >> â Date: Wed, 22 Apr 2009 12:21:00 GMT^M
>> >> â
>> >> â Server: Jetty/5.1.4 (Linux/2.6.18-92.el5 i386
>> >> java/1.6.0_07^M â
>> >> â Expires: Thu, 01 Jan 1970 00:00:00 GMT^M
>> >> â
>> >> â Cache-Control: must-revalidate, post-check=0,
>> >> pre-check=0^M â
>> >> â Pragma: public^M
>> >> â
>> >> â Content-Disposition: attachment;
>> >> â
>> >> â filename="tst-sipxs.tstcsi.it.tar.gz"^M
>> >> â
>> >> â Content-Type: text/html^M
>> >> â
>> >> â Set-Cookie:
>> >> JSESSIONID=30r4rgfvl82d9;Path=/sipxconfig^M â
>> >> â Content-Length: 1282^M
>> >> â
>> >> â Connection: close^M
>> >>
>> >> What's wrong?
>> >> Thanks
>> >>
>> >
>> > Should check the file ownership under the primary server directory
>> > /var/sipxdata/certdb, the files should owned by
>> sipxchange:sipxchange
>> > (or whatever your sipx user is).
>> >
>> > Dave.
>>
>>
>> It's tracked as this issue:
>> http://track.sipfoundry.org/browse/XCF-3639
>>
>> For some reason initial-config script returns error to sipXconfig.
>> Dave - do you think it's because of the permission problems?
>> D.
>>
>
>I've seen this issue several times, the most recent time it
>happened to me the certdb/*.der files were found to be set to
>root:root instead of sipxchange:sipxchange. However main
>stream rev15235 works fine.
>
Another issue with this script is it returns an exit code of 1 for all of the
possible errors. It makes it a little difficult to pinpoint exactly what
failed but the issue that I saw in the recent past was because of permission
issues either in the actual "certdb" directory or in the setup.log file in the
logging directory.
Fortunately, as of a recent submission by Carolyn, we no longer log to the
setup.log file.
_______________________________________________
sipx-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
