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: " target="_blank"> ]
Sent: Saturday, April 25, 2015 7:39 AM
To: " target="_blank">
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" < " target="_blank"> > 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: " target="_blank"> ]
Sent: Friday, April 24, 2015 10:34 AM
To: " target="_blank">
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" < " target="_blank"> > 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
Archive powered by MHonArc 2.6.16.