On Mon, Aug 20, 2012 at 6:06 PM,  <[email protected]> wrote:
>
>
> I had a look into the initialconfig directory and there I found the archive:
> [root@gssipx02 initial-config]# ls -al /var/sipxdata/tmp/initial-config/
> total 44
> drwxr-xr-x  4 root       root        4096 Aug 20 16:37 .
> drwxr-xr-x 15 sipxchange sipxchange 20480 Aug 20 16:37 ..
> drwxr-xr-x  4 root       root        4096 Aug 20 16:37 etc
> -rw-r--r--  1 root       root        3973 Aug 20 16:37 .tar.gz
> drwxr-xr-x  3 root       root        4096 Aug 20 16:37 th.internal.epo.org
> -rw-r--r--  1 root       root        3952 Aug 20 16:37
> th.internal.epo.org.tar.gz

Ah, right Sorry about, that should be the proper directory
/var/sipxdata/tmp/initial-config/

> [root@gssipx02 initial-config]#
>
> So with a manual run it is being created.
> I then tried to add a server (at around 16:40, so 14:40 in the logfile
> (GMT+2) through the GUI, nothing in the sipxconfig.log relating to "initial"
> or the servername.

The entry regarding initial-config will appear after sipxecs-setup
performed on secondary (that is not registered, check UI before)

>
> Looking through the files a bit more I found it a bit strange that
>     /etc/sipxpbx/ssl/th/ca.gssipx02.internal.epo.org.crt
>      [root@gssipx02 ssl]# ls -al
> /etc/sipxpbx/ssl/th/ca.gssipx02.internal.epo.org.crt
>      -rw-r--r-- 1 root root 2377 Aug 16 20:02
> /etc/sipxpbx/ssl/th/ca.gssipx02.internal.epo.org.crt
> is different from
>
> /var/sipxdata/tmp/initial-config/etc/sipxpbx/ssl/authorities/ca.gssipx02.internal.epo.org.crt
>      [root@gssipx02 ssl]# ls -al
> /var/sipxdata/tmp/initial-config/etc/sipxpbx/ssl/authorities/
>      total 12
>      drwx------ 2 sipxchange root 4096 Aug 20 16:37 .
>      drwx------ 3 sipxchange root 4096 Aug 20 16:37 ..
>      lrwxrwxrwx 1 root       root   32 Aug 20 16:37 c6310ad2.0 ->
> ca.gssipx02.internal.epo.org.crt
>      -rw-r--r-- 1 sipxchange root 2377 Aug 20 16:37
> ca.gssipx02.internal.epo.org.crt
>
> I don't know whether that is important, but it looked suspicious to me, why
> would there be a different ca certificate?.
>
>

That's the way it generates afaik, related to machine hostname

>
> Paul
>
> [email protected] wrote on 20-08-2012 15:29:14:
>
>> From:
>>
>> George Niculae <[email protected]>
>>
>> To:
>>
>> Discussion list for users of sipXecs software
>> <[email protected]>
>>
>> Date:
>>
>> 20-08-2012 15:29
>>
>> Subject:
>>
>> Re: [sipx-users] SipX not starting anymore.
>>
>> Sent by:
>>
>> [email protected]
>>
>> On Mon, Aug 20, 2012 at 3:34 PM,  <[email protected]> wrote:
>> > Hi George,
>> >
>> > Back at work, trying to solve the initialconfig problem.
>> > I started with a restart this morning with all the files in the
>> > /var/sipxdata/tmp/ in place (restored them friday).
>> > Then added a server through the GUI
>> > This resulted in a run of initialconfig with an exit code 1.
>> > (09:55:44.821
>> > in log file)
>> > I then deleted all the tar.gz's in /var/sipxdata/tmp (or should I delete
>> > something else?)
>> > Restarted services again.
>> > Added a server again through the GUI.
>> > Then the initial-config did not run anymore, in the log file I see a
>> > "Connection refused" around that time, 10:14:14.754
>>
>> I think you see this because there is another server configured, can
>> you start from the beginning one more time and leave only master? that
>> is gssipx02.internal.epo.org I assume. Then add slave in UI, run
>> sipxecs-setup on slave and see if still same error. If you get the
>> error try to manually run intial-config script and see if archive gets
>> generated inside /var/sipxdata/tmp/
>> No need to manually delete any archive from /var/sipxdata/tmp/
>>
>> > I put all the tar.gz's back in place, restarted services, but still
>> > initialconfig won't run.
>> > All I see is a replicationBean error around 10:29:44.211
>> > After some time this will probably work again because of some
>> > synchronisation (because it also worked this morning).
>> > But then I will run into the exit code 1 problem again.
>> > Any clue how to solve this, because if I am not mistaken I am otherwise
>> > looking at a complete rebuild of all the servers.
>>
>> Let's give it one more try before doing this
>>
>> George
>> _______________________________________________
>> sipx-users mailing list
>> [email protected]
>> List Archive:
> http://list.sipfoundry.org/archive/sipx-users/
>
> _______________________________________________
> sipx-users mailing list
> [email protected]
> List Archive: http://list.sipfoundry.org/archive/sipx-users/
_______________________________________________
sipx-users mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users/

Reply via email to