Hi Matt,

I add "-e to at the top file bash: #!/bin/bash -e" for all shell scripts
under hooks.
I will test it and talk with my manager before I check-in today.

For unused hook hpcc-relation-changed, if I remove it 'juju charm proof'
will report an info massage: "I: relation hpcc has no hooks". And I must
keep 'hpcc' in "provider" field in metadata.yaml otherwise will get a
warning.

Thanks


On Wed, Mar 5, 2014 at 2:55 PM, Xiaoming Wang <email address hidden> wrote:

> the /proc/sys/net/core show the same problem on my system.
> It miss the network resource settings.
> Maybe you can help me open a bug against juju-local
> Here is discussion thread on Ubuntu one (Actually you help me correct the
> spelling and formatting. Thanks).
>
>
> http://askubuntu.com/questions/404969/error-net-core-wmem-default-is-an-unknown-key-on-juju-local-provider
>
>
> I will try to see how much efforts I need to replace "set -e" and
> necessary hook code changes.
>
>
> Thanks
>
>
> On Wed, Mar 5, 2014 at 2:34 PM, Matt Bruzek <email address hidden>wrote:
>
>> Xiaoming,
>>
>> The last tar file included the file listing from /proc/sys/net/core/ for
>> each system including cluster1/2 which was not in error state.
>>
>> Here is cluster1/0 output:
>> $ ls /proc/sys/net/core/
>> somaxconn  xfrm_acq_expires  xfrm_aevent_etime  xfrm_aevent_rseqth
>>  xfrm_larval_drop
>>
>> I have attached a new tar file that has the logs from the
>> /var/log/HPCCSystems/myroxie on each system.
>>
>> It is important that the scripts end on the first error (set -e) so that
>> the script does not continue in an error state.  The error of one
>> command could cause problems for following commands.  For instance if
>> the script was unable to write the LOCAL_IP_FILE and did not halt
>> execution, a different hook could fail to read that file later and cause
>> different problems.
>>
>>
>>
>> ** Attachment added: "Log files from the hpcc units myroxie directories."
>>
>> https://bugs.launchpad.net/charms/+bug/1272083/+attachment/4008744/+files/hpcc_logs.tar.gz
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https://bugs.launchpad.net/bugs/1272083
>>
>> Title:
>>   HPCC Charm initial check-in for review
>>
>> Status in Juju Charms:
>>   Incomplete
>>
>> Bug description:
>>   A new Juju Charm - hpcc is submitted for review.
>>   The README.md has the information for how to use the charm.
>>
>>   For charm code:
>>     config.yaml:   there are parameters to control which HPCCSystems use
>> can install. There are other parameters for how to configure
>>                                the cluster.
>>     bin/  : There are some help scripts we put here mainly for
>> re-configure HPCC cluster. Default configuration may not meet user need.
>>                 We understand it probably not recommend way for juju
>> charm. But we want to give user convenient  way to access the tools.
>>                 We are open for discuss these during the review process.
>>     icon.svg: We haven't gotten which icon we should use. It is in our
>> internal process.
>>
>>     Currently HPCC charm doesn't have related to any other charms.
>>
>> To manage notifications about this bug go to:
>> https://bugs.launchpad.net/charms/+bug/1272083/+subscriptions
>>
>
>