Why do I need to keep restarting Berks API


#1

I FINALLY got my Berks API server working, and am able to do a berks install/upload. However, it seems like I have to restart it every now and then for it to respond. I assume this is NOT normal?

Chris


#2

Is this restart needed for it to respond or serve your latest cookbook
versions.
On 24 Apr 2015 15:19, “Fouts, Chris” Chris.Fouts@sensus.com wrote:

I FINALLY got my Berks API server working, and am able to do a berks
install/upload. However, it seems like I have to restart it every now and
then for it to respond. I assume this is NOT normal?

Chris


#3

Whenever I upload new cookbooks/cookbook versions to my Berks API server, I have to rerun ‘berks api’ for subsequent berks install/upload to work.

Chris

From: Damien Roche [mailto:dcroche@gmail.com]
Sent: Friday, April 24, 2015 10:34 AM
To: chef@lists.opscode.com
Subject: [chef] Re: Why do I need to keep restarting Berks API

Is this restart needed for it to respond or serve your latest cookbook versions.
On 24 Apr 2015 15:19, “Fouts, Chris” <Chris.Fouts@sensus.commailto:Chris.Fouts@sensus.com> wrote:
I FINALLY got my Berks API server working, and am able to do a berks install/upload. However, it seems like I have to restart it every now and then for it to respond. I assume this is NOT normal?

Chris


#4

There is a build_interval option for berks-api config.json it should not
require a service restart.
On 24 Apr 2015 16:23, “Fouts, Chris” Chris.Fouts@sensus.com wrote:

Whenever I upload new cookbooks/cookbook versions to my Berks API
server, I have to rerun ‘berks api’ for subsequent berks install/upload to
work.

Chris

From: Damien Roche [mailto:dcroche@gmail.com]
Sent: Friday, April 24, 2015 10:34 AM
To: chef@lists.opscode.com
Subject: [chef] Re: Why do I need to keep restarting Berks API

Is this restart needed for it to respond or serve your latest cookbook
versions.

On 24 Apr 2015 15:19, “Fouts, Chris” Chris.Fouts@sensus.com wrote:

I FINALLY got my Berks API server working, and am able to do a berks
install/upload. However, it seems like I have to restart it every now and
then for it to respond. I assume this is NOT normal?

Chris


#5

Ok thanks, I’ll look into that.

I think my problem was the way I was running it which as

/opt/opscode/embedded/bin/ruby /opt/opscode/embedded/bin/berks-api –c .berkshhelf/api-server/config.json &

I did this instead and it seems to be running fine now

nohup /opt/opscode/embedded/bin/ruby /opt/opscode/embedded/bin/berks-api –c .berkshhelf/api-server/config.json &

Chris

From: Damien Roche [mailto:dcroche@gmail.com]
Sent: Saturday, April 25, 2015 7:39 AM
To: chef@lists.opscode.com
Subject: [chef] Re: RE: Re: Why do I need to keep restarting Berks API

There is a build_interval option for berks-api config.json it should not require a service restart.
On 24 Apr 2015 16:23, “Fouts, Chris” <Chris.Fouts@sensus.commailto:Chris.Fouts@sensus.com> wrote:
Whenever I upload new cookbooks/cookbook versions to my Berks API server, I have to rerun ‘berks api’ for subsequent berks install/upload to work.

Chris

From: Damien Roche [mailto:dcroche@gmail.commailto:dcroche@gmail.com]
Sent: Friday, April 24, 2015 10:34 AM
To: chef@lists.opscode.commailto:chef@lists.opscode.com
Subject: [chef] Re: Why do I need to keep restarting Berks API

Is this restart needed for it to respond or serve your latest cookbook versions.
On 24 Apr 2015 15:19, “Fouts, Chris” <Chris.Fouts@sensus.commailto:Chris.Fouts@sensus.com> wrote:
I FINALLY got my Berks API server working, and am able to do a berks install/upload. However, it seems like I have to restart it every now and then for it to respond. I assume this is NOT normal?

Chris


#6

There’s a cookbook on the supermarket to help you do all this, if you
didn’t know.

https://supermarket.chef.io/cookbooks/berkshelf-api-server

The config json file is managed via attributes.

On Sat, Apr 25, 2015 at 10:13 AM, Fouts, Chris Chris.Fouts@sensus.com
wrote:

Ok thanks, I’ll look into that.

I think my problem was the way I was running it which as

/opt/opscode/embedded/bin/ruby /opt/opscode/embedded/bin/berks-api –c

.berkshhelf/api-server/config.json &

I did this instead and it seems to be running fine now

nohup /opt/opscode/embedded/bin/ruby

/opt/opscode/embedded/bin/berks-api –c .berkshhelf/api-server/config.json &

Chris

From: Damien Roche [mailto:dcroche@gmail.com]
Sent: Saturday, April 25, 2015 7:39 AM
To: chef@lists.opscode.com
Subject: [chef] Re: RE: Re: Why do I need to keep restarting Berks API

There is a build_interval option for berks-api config.json it should not
require a service restart.

On 24 Apr 2015 16:23, “Fouts, Chris” Chris.Fouts@sensus.com wrote:

Whenever I upload new cookbooks/cookbook versions to my Berks API server,
I have to rerun ‘berks api’ for subsequent berks install/upload to work.

Chris

From: Damien Roche [mailto:dcroche@gmail.com]
Sent: Friday, April 24, 2015 10:34 AM
To: chef@lists.opscode.com
Subject: [chef] Re: Why do I need to keep restarting Berks API

Is this restart needed for it to respond or serve your latest cookbook
versions.

On 24 Apr 2015 15:19, “Fouts, Chris” Chris.Fouts@sensus.com wrote:

I FINALLY got my Berks API server working, and am able to do a berks
install/upload. However, it seems like I have to restart it every now and
then for it to respond. I assume this is NOT normal?

Chris


Yoshi Spendiff
Ops Engineer
Indochino
Mobile: +1 778 952 2025
Email: yoshi.spendiff@indochino.com


#7

Thanks. The nohup trick was simple enough.

Chris

From: Yoshi Spendiff [mailto:yoshi.spendiff@indochino.com]
Sent: Monday, April 27, 2015 11:48 AM
To: chef@lists.opscode.com
Subject: [chef] Re: RE: Re: RE: Re: Why do I need to keep restarting Berks API

There’s a cookbook on the supermarket to help you do all this, if you didn’t know.

https://supermarket.chef.io/cookbooks/berkshelf-api-server


The config json file is managed via attributes.

On Sat, Apr 25, 2015 at 10:13 AM, Fouts, Chris <Chris.Fouts@sensus.commailto:Chris.Fouts@sensus.com> wrote:
Ok thanks, I’ll look into that.

I think my problem was the way I was running it which as

/opt/opscode/embedded/bin/ruby /opt/opscode/embedded/bin/berks-api –c .berkshhelf/api-server/config.json &

I did this instead and it seems to be running fine now

nohup /opt/opscode/embedded/bin/ruby /opt/opscode/embedded/bin/berks-api –c .berkshhelf/api-server/config.json &

Chris

From: Damien Roche [mailto:dcroche@gmail.commailto:dcroche@gmail.com]
Sent: Saturday, April 25, 2015 7:39 AM
To: chef@lists.opscode.commailto:chef@lists.opscode.com
Subject: [chef] Re: RE: Re: Why do I need to keep restarting Berks API

There is a build_interval option for berks-api config.json it should not require a service restart.
On 24 Apr 2015 16:23, “Fouts, Chris” <Chris.Fouts@sensus.commailto:Chris.Fouts@sensus.com> wrote:
Whenever I upload new cookbooks/cookbook versions to my Berks API server, I have to rerun ‘berks api’ for subsequent berks install/upload to work.

Chris

From: Damien Roche [mailto:dcroche@gmail.commailto:dcroche@gmail.com]
Sent: Friday, April 24, 2015 10:34 AM
To: chef@lists.opscode.commailto:chef@lists.opscode.com
Subject: [chef] Re: Why do I need to keep restarting Berks API

Is this restart needed for it to respond or serve your latest cookbook versions.
On 24 Apr 2015 15:19, “Fouts, Chris” <Chris.Fouts@sensus.commailto:Chris.Fouts@sensus.com> wrote:
I FINALLY got my Berks API server working, and am able to do a berks install/upload. However, it seems like I have to restart it every now and then for it to respond. I assume this is NOT normal?

Chris


Yoshi Spendiff
Ops Engineer
Indochino
Mobile: +1 778 952 2025
Email: yoshi.spendiff@indochino.commailto:yoshi.spendiff@indochino.com