> Error 400007: `ccdb_postgres/0' is not running after update
-- cheers,
/Martin
-- Martin Englund, Staff Engineer, Cloud Foundry, VMware Inc.
"The question is not if you are paranoid, it is if you are paranoid enough."
>> Error 400007: `ccdb_postgres/0' is not running after update
-- cheers,
/Martin
-- Martin Englund, Staff Engineer, Cloud Foundry, VMware Inc.
"The question is not if you are paranoid, it is if you are paranoid enough."
> >> Error 400007: `ccdb_postgres/0' is not running after update
> -- > cheers, > /Martin > -- > Martin Englund, Staff Engineer, Cloud Foundry, VMware Inc. > "The question is not if you are paranoid, it is if you are paranoid > enough."
>> >> Error 400007: `ccdb_postgres/0' is not running after update
>> --
>> cheers,
>> /Martin
>> --
>> Martin Englund, Staff Engineer, Cloud Foundry, VMware Inc.
>> "The question is not if you are paranoid, it is if you are paranoid
>> enough."
-- cheers,
/Martin
-- Martin Englund, Staff Engineer, Cloud Foundry, VMware Inc.
"The question is not if you are paranoid, it is if you are paranoid enough."
ah okay i understand but what do i need to provide in the resource pool for the openstack cpi is there a list of properties specific for the bosh/openstack cpi?
Op vrijdag 5 oktober 2012 16:13:48 UTC+2 schreef ramonm...@gmail.com het volgende:
On Mon, Oct 8, 2012 at 11:47 AM, <ramonmakke...@gmail.com> wrote:
> ah okay i understand
> but what do i need to provide in the resource pool for the openstack cpi
> is there a list of properties specific for the bosh/openstack cpi?
> Op vrijdag 5 oktober 2012 16:13:48 UTC+2 schreef ramonm...@gmail.com het
> volgende:
>> finally after some network difficulties
>> all vm's are starting
>> and now i get the following error
>> and i really don't know where to look
>> this is a small part ofmy template.yml
>> Jobs:
>> - name: ccdb_postgres
>> template: postgres
>> instances: 1
>> resource_pool: infrastructure
>> networks:
>> - name: default
>> default: [dns, gateway]
>> - name: static
>> static_ips:
>> - 172.24.4.231
>> properties:
>> db: ccdb
>> Error 400007: `ccdb_postgres/0' is not running after update
-- cheers,
/Martin
-- Martin Englund, Staff Engineer, Cloud Foundry, VMware Inc.
"The question is not if you are paranoid, it is if you are paranoid enough."
> You'll have to ask Ferdy for OpenStack specific stuff - I've just been
> working on vSphere & AWS...
> /M
> On Mon, Oct 8, 2012 at 11:47 AM, <ramonmakke...@gmail.com> wrote:
> > ah okay i understand
> > but what do i need to provide in the resource pool for the openstack cpi
> > is there a list of properties specific for the bosh/openstack cpi?
> > Op vrijdag 5 oktober 2012 16:13:48 UTC+2 schreef ramonm...@gmail.com het
> > volgende:
> >> finally after some network difficulties
> >> all vm's are starting
> >> and now i get the following error
> >> and i really don't know where to look
> >> Error 400007: `ccdb_postgres/0' is not running after update
> --
> cheers,
> /Martin
> --
> Martin Englund, Staff Engineer, Cloud Foundry, VMware Inc.
> "The question is not if you are paranoid, it is if you are paranoid
> enough."
>> You'll have to ask Ferdy for OpenStack specific stuff - I've just been >> working on vSphere & AWS...
>> /M
>> On Mon, Oct 8, 2012 at 11:47 AM, <ramonm...@gmail.com <javascript:>> >> wrote: >> > ah okay i understand >> > but what do i need to provide in the resource pool for the openstack cpi >> > is there a list of properties specific for the bosh/openstack cpi?
>> > Op vrijdag 5 oktober 2012 16:13:48 UTC+2 schreef ramonm...@gmail.comhet >> > volgende:
>> >> finally after some network difficulties
>> >> all vm's are starting
>> >> and now i get the following error >> >> and i really don't know where to look
>> >> Error 400007: `ccdb_postgres/0' is not running after update
>> -- >> cheers, >> /Martin >> -- >> Martin Englund, Staff Engineer, Cloud Foundry, VMware Inc. >> "The question is not if you are paranoid, it is if you are paranoid >> enough."
No, the ephemeral disk is always attached to the vm when is started (it's
part of the vm image: /dev/vda is the root device and /dev/vdb is the
ephemeral (free) space you configured at the OpenStack flavor spec), but it
will be destroyed whenever the vm is stopped. The persistent disk is
optional (only required by some packages), and it attaches an OpenStack
volume to the vm (usually /dev/vdc).
So when you specify a persistent_disk option, the CPI will create an
OpenStack volume and attach it to the vm. If for some reason the vm is
stopped (i.e. redeploy a new release version), the director will start a
new vm and attach to it the old persistent disk, so you won't lost any data.
An example could be a release that contains mysql: the mysql instance is
deployed in a vm, all the binaries and configuration data are stored in the
ephemeral disk, but the DB data can be configured to be stored in the
persistent disk. If you redeploy the release (i.e. changing some mysql conf
files), director will destroy the vm and create a new one, then it'll
deploy the mysql server with the new configuration on the new vm (in the
ephemeral disk), and it will attach the old persistent disk, so any data
you had previously it won't be destroyed.
>>> You'll have to ask Ferdy for OpenStack specific stuff - I've just been
>>> working on vSphere & AWS...
>>> /M
>>> On Mon, Oct 8, 2012 at 11:47 AM, <ramonm...@gmail.com> wrote:
>>> > ah okay i understand
>>> > but what do i need to provide in the resource pool for the openstack
>>> cpi
>>> > is there a list of properties specific for the bosh/openstack cpi?
>>> > Op vrijdag 5 oktober 2012 16:13:48 UTC+2 schreef ramonm...@gmail.comhet
>>> > volgende:
>>> >> finally after some network difficulties
>>> >> all vm's are starting
>>> >> and now i get the following error
>>> >> and i really don't know where to look
>>> >> Error 400007: `ccdb_postgres/0' is not running after update
>>> --
>>> cheers,
>>> /Martin
>>> --
>>> Martin Englund, Staff Engineer, Cloud Foundry, VMware Inc.
>>> "The question is not if you are paranoid, it is if you are paranoid
>>> enough."
> No, the ephemeral disk is always attached to the vm when is started (it's > part of the vm image: /dev/vda is the root device and /dev/vdb is the > ephemeral (free) space you configured at the OpenStack flavor spec), but it > will be destroyed whenever the vm is stopped. The persistent disk is > optional (only required by some packages), and it attaches an OpenStack > volume to the vm (usually /dev/vdc).
> So when you specify a persistent_disk option, the CPI will create an > OpenStack volume and attach it to the vm. If for some reason the vm is > stopped (i.e. redeploy a new release version), the director will start a > new vm and attach to it the old persistent disk, so you won't lost any data.
> An example could be a release that contains mysql: the mysql instance is > deployed in a vm, all the binaries and configuration data are stored in the > ephemeral disk, but the DB data can be configured to be stored in the > persistent disk. If you redeploy the release (i.e. changing some mysql conf > files), director will destroy the vm and create a new one, then it'll > deploy the mysql server with the new configuration on the new vm (in the > ephemeral disk), and it will attach the old persistent disk, so any data > you had previously it won't be destroyed.
>>>> You'll have to ask Ferdy for OpenStack specific stuff - I've just been >>>> working on vSphere & AWS...
>>>> /M
>>>> On Mon, Oct 8, 2012 at 11:47 AM, <ramonm...@gmail.com> wrote: >>>> > ah okay i understand >>>> > but what do i need to provide in the resource pool for the openstack >>>> cpi >>>> > is there a list of properties specific for the bosh/openstack cpi?
>>>> > Op vrijdag 5 oktober 2012 16:13:48 UTC+2 schreef ramonm...@gmail.comhet >>>> > volgende:
>>>> >> finally after some network difficulties
>>>> >> all vm's are starting
>>>> >> and now i get the following error >>>> >> and i really don't know where to look
>>>> >> Error 400007: `ccdb_postgres/0' is not running after update
>>>> -- >>>> cheers, >>>> /Martin >>>> -- >>>> Martin Englund, Staff Engineer, Cloud Foundry, VMware Inc. >>>> "The question is not if you are paranoid, it is if you are paranoid >>>> enough."
On Wednesday, October 10, 2012 7:42:39 AM UTC-7, ramonm...@gmail.com wrote:
> oka thanks after some trial and error i know how it works now with the > persistent disk part
> but still can't get ccdb_postgress running > /var/vcap/sys/log/monit/postgres_ctl.err.log show
> pg_ctl: could not start server > Examine the log output.
> but there are no more log files in this directory
> Op dinsdag 9 oktober 2012 15:04:09 UTC+2 schreef ferdy het volgende:
>> No, the ephemeral disk is always attached to the vm when is started (it's >> part of the vm image: /dev/vda is the root device and /dev/vdb is the >> ephemeral (free) space you configured at the OpenStack flavor spec), but it >> will be destroyed whenever the vm is stopped. The persistent disk is >> optional (only required by some packages), and it attaches an OpenStack >> volume to the vm (usually /dev/vdc).
>> So when you specify a persistent_disk option, the CPI will create an >> OpenStack volume and attach it to the vm. If for some reason the vm is >> stopped (i.e. redeploy a new release version), the director will start a >> new vm and attach to it the old persistent disk, so you won't lost any data.
>> An example could be a release that contains mysql: the mysql instance is >> deployed in a vm, all the binaries and configuration data are stored in the >> ephemeral disk, but the DB data can be configured to be stored in the >> persistent disk. If you redeploy the release (i.e. changing some mysql conf >> files), director will destroy the vm and create a new one, then it'll >> deploy the mysql server with the new configuration on the new vm (in the >> ephemeral disk), and it will attach the old persistent disk, so any data >> you had previously it won't be destroyed.
>>>>> You'll have to ask Ferdy for OpenStack specific stuff - I've just been >>>>> working on vSphere & AWS...
>>>>> /M
>>>>> On Mon, Oct 8, 2012 at 11:47 AM, <ramonm...@gmail.com> wrote: >>>>> > ah okay i understand >>>>> > but what do i need to provide in the resource pool for the openstack >>>>> cpi >>>>> > is there a list of properties specific for the bosh/openstack cpi?
>>>>> > Op vrijdag 5 oktober 2012 16:13:48 UTC+2 schreef ramonm...@gmail.comhet >>>>> > volgende:
>>>>> >> finally after some network difficulties
>>>>> >> all vm's are starting
>>>>> >> and now i get the following error >>>>> >> and i really don't know where to look
>>>>> >> Error 400007: `ccdb_postgres/0' is not running after update
>>>>> -- >>>>> cheers, >>>>> /Martin >>>>> -- >>>>> Martin Englund, Staff Engineer, Cloud Foundry, VMware Inc. >>>>> "The question is not if you are paranoid, it is if you are paranoid >>>>> enough."
> oka thanks after some trial and error i know how it works now with the
> persistent disk part
> but still can't get ccdb_postgress running
> /var/vcap/sys/log/monit/postgres_ctl.err.log show
> pg_ctl: could not start server
> Examine the log output.
> but there are no more log files in this directory
> Op dinsdag 9 oktober 2012 15:04:09 UTC+2 schreef ferdy het volgende:
>> No, the ephemeral disk is always attached to the vm when is started (it's
>> part of the vm image: /dev/vda is the root device and /dev/vdb is the
>> ephemeral (free) space you configured at the OpenStack flavor spec), but it
>> will be destroyed whenever the vm is stopped. The persistent disk is
>> optional (only required by some packages), and it attaches an OpenStack
>> volume to the vm (usually /dev/vdc).
>> So when you specify a persistent_disk option, the CPI will create an
>> OpenStack volume and attach it to the vm. If for some reason the vm is
>> stopped (i.e. redeploy a new release version), the director will start a
>> new vm and attach to it the old persistent disk, so you won't lost any data.
>> An example could be a release that contains mysql: the mysql instance is
>> deployed in a vm, all the binaries and configuration data are stored in the
>> ephemeral disk, but the DB data can be configured to be stored in the
>> persistent disk. If you redeploy the release (i.e. changing some mysql conf
>> files), director will destroy the vm and create a new one, then it'll
>> deploy the mysql server with the new configuration on the new vm (in the
>> ephemeral disk), and it will attach the old persistent disk, so any data
>> you had previously it won't be destroyed.
>>>>> You'll have to ask Ferdy for OpenStack specific stuff - I've just been
>>>>> working on vSphere & AWS...
>>>>> /M
>>>>> On Mon, Oct 8, 2012 at 11:47 AM, <ramonm...@gmail.com> wrote:
>>>>> > ah okay i understand
>>>>> > but what do i need to provide in the resource pool for the openstack
>>>>> cpi
>>>>> > is there a list of properties specific for the bosh/openstack cpi?
>>>>> > Op vrijdag 5 oktober 2012 16:13:48 UTC+2 schreef ramonm...@gmail.comhet
>>>>> > volgende:
>>>>> >> finally after some network difficulties
>>>>> >> all vm's are starting
>>>>> >> and now i get the following error
>>>>> >> and i really don't know where to look
>>>>> >> Error 400007: `ccdb_postgres/0' is not running after update
>>>>> --
>>>>> cheers,
>>>>> /Martin
>>>>> --
>>>>> Martin Englund, Staff Engineer, Cloud Foundry, VMware Inc.
>>>>> "The question is not if you are paranoid, it is if you are paranoid
>>>>> enough."
can ping to WWW and works fine.. so i think BOSH is doing something but not on the vm it self as it seems because on the vm the resolv.conf / route -n etc etc are all the same
Op woensdag 10 oktober 2012 21:02:04 UTC+2 schreef ferdy het volgende:
>> oka thanks after some trial and error i know how it works now with the >> persistent disk part
>> but still can't get ccdb_postgress running >> /var/vcap/sys/log/monit/postgres_ctl.err.log show
>> pg_ctl: could not start server >> Examine the log output.
>> but there are no more log files in this directory
>> Op dinsdag 9 oktober 2012 15:04:09 UTC+2 schreef ferdy het volgende:
>>> No, the ephemeral disk is always attached to the vm when is started >>> (it's part of the vm image: /dev/vda is the root device and /dev/vdb is the >>> ephemeral (free) space you configured at the OpenStack flavor spec), but it >>> will be destroyed whenever the vm is stopped. The persistent disk is >>> optional (only required by some packages), and it attaches an OpenStack >>> volume to the vm (usually /dev/vdc).
>>> So when you specify a persistent_disk option, the CPI will create an >>> OpenStack volume and attach it to the vm. If for some reason the vm is >>> stopped (i.e. redeploy a new release version), the director will start a >>> new vm and attach to it the old persistent disk, so you won't lost any data.
>>> An example could be a release that contains mysql: the mysql instance is >>> deployed in a vm, all the binaries and configuration data are stored in the >>> ephemeral disk, but the DB data can be configured to be stored in the >>> persistent disk. If you redeploy the release (i.e. changing some mysql conf >>> files), director will destroy the vm and create a new one, then it'll >>> deploy the mysql server with the new configuration on the new vm (in the >>> ephemeral disk), and it will attach the old persistent disk, so any data >>> you had previously it won't be destroyed.
>>>>>> You'll have to ask Ferdy for OpenStack specific stuff - I've just been >>>>>> working on vSphere & AWS...
>>>>>> /M
>>>>>> On Mon, Oct 8, 2012 at 11:47 AM, <ramonm...@gmail.com> wrote: >>>>>> > ah okay i understand >>>>>> > but what do i need to provide in the resource pool for the >>>>>> openstack cpi >>>>>> > is there a list of properties specific for the bosh/openstack cpi?
>>>>>> > Op vrijdag 5 oktober 2012 16:13:48 UTC+2 schreef >>>>>> ramonm...@gmail.com het >>>>>> > volgende:
>>>>>> >> finally after some network difficulties
>>>>>> >> all vm's are starting
>>>>>> >> and now i get the following error >>>>>> >> and i really don't know where to look
>>>>>> >> Error 400007: `ccdb_postgres/0' is not running after update
>>>>>> -- >>>>>> cheers, >>>>>> /Martin >>>>>> -- >>>>>> Martin Englund, Staff Engineer, Cloud Foundry, VMware Inc. >>>>>> "The question is not if you are paranoid, it is if you are paranoid >>>>>> enough."
> i' have some seriously strange problems > the postgresql can't listen on the vip adres it was assigned to > 172.24.4.227 (default devstack gives away)
> i can ping the ip adres > nslookup results in > Server: 10.0.0.1 > Address: 10.0.0.1#53
> ** server can't find 227.4.24.172.in-addr.arpa.: NXDOMAIN
> and there is another strange problem > on every vm where there are 2 networks assigned > the default one and the static
> can ping to WWW and works fine.. > so i think BOSH is doing something but not on the vm it self as it seems > because on the vm the resolv.conf / route -n etc etc are all the same
> Op woensdag 10 oktober 2012 21:02:04 UTC+2 schreef ferdy het volgende:
>> Check /var/vcap/store/postgres/pg_log/startup.log to see if there's any >> error.
>>> oka thanks after some trial and error i know how it works now with the >>> persistent disk part
>>> but still can't get ccdb_postgress running >>> /var/vcap/sys/log/monit/postgres_ctl.err.log show
>>> pg_ctl: could not start server >>> Examine the log output.
>>> but there are no more log files in this directory
>>> Op dinsdag 9 oktober 2012 15:04:09 UTC+2 schreef ferdy het volgende:
>>>> No, the ephemeral disk is always attached to the vm when is started >>>> (it's part of the vm image: /dev/vda is the root device and /dev/vdb is the >>>> ephemeral (free) space you configured at the OpenStack flavor spec), but it >>>> will be destroyed whenever the vm is stopped. The persistent disk is >>>> optional (only required by some packages), and it attaches an OpenStack >>>> volume to the vm (usually /dev/vdc).
>>>> So when you specify a persistent_disk option, the CPI will create an >>>> OpenStack volume and attach it to the vm. If for some reason the vm is >>>> stopped (i.e. redeploy a new release version), the director will start a >>>> new vm and attach to it the old persistent disk, so you won't lost any data.
>>>> An example could be a release that contains mysql: the mysql instance >>>> is deployed in a vm, all the binaries and configuration data are stored in >>>> the ephemeral disk, but the DB data can be configured to be stored in the >>>> persistent disk. If you redeploy the release (i.e. changing some mysql conf >>>> files), director will destroy the vm and create a new one, then it'll >>>> deploy the mysql server with the new configuration on the new vm (in the >>>> ephemeral disk), and it will attach the old persistent disk, so any data >>>> you had previously it won't be destroyed.
>>>>>>> You'll have to ask Ferdy for OpenStack specific stuff - I've just >>>>>>> been >>>>>>> working on vSphere & AWS...
>>>>>>> /M
>>>>>>> On Mon, Oct 8, 2012 at 11:47 AM, <ramonm...@gmail.com> wrote: >>>>>>> > ah okay i understand >>>>>>> > but what do i need to provide in the resource pool for the >>>>>>> openstack cpi >>>>>>> > is there a list of properties specific for the bosh/openstack cpi?
>>>>>>> > Op vrijdag 5 oktober 2012 16:13:48 UTC+2 schreef >>>>>>> ramonm...@gmail.com het >>>>>>> > volgende:
>>>>>>> >> finally after some network difficulties
>>>>>>> >> all vm's are starting
>>>>>>> >> and now i get the following error >>>>>>> >> and i really don't know where to look
>>>>>>> >> Error 400007: `ccdb_postgres/0' is not running after update
>>>>>>> -- >>>>>>> cheers, >>>>>>> /Martin >>>>>>> -- >>>>>>> Martin Englund, Staff Engineer, Cloud Foundry, VMware Inc. >>>>>>> "The question is not if you are paranoid, it is if you are paranoid >>>>>>> enough."
