ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ed Kohlwey <ekohl...@gmail.com>
Subject Re: Malformed package list in generated pp files
Date Thu, 19 Dec 2013 15:38:05 GMT
The Ambari agent reports parse errors from the site-xx.pp files during
install of any service except HDFS. Could it be that the error message is
being generated incorrectly?
On Dec 19, 2013 10:33 AM, "Nate Cole" <ncole@hortonworks.com> wrote:

> The 2.0._ stack does not use site-XX.pp files, it uses command-XX.json
> files.
>
> Thanks,
> Nate
>
> On 12/19/13 10:28 AM, Ed Kohlwey wrote:
>
>> What about cleanup of the site-xx.pp files? Can that be turned off? It did
>> not occur in older versions.
>> On Dec 19, 2013 10:11 AM, "Sumit Mohanty" <smohanty@hortonworks.com>
>> wrote:
>>
>>  You can enable debug level by editing ambari-agent.ini file.
>>>
>>> [agent]
>>> loglevel=DEBUGINFO
>>>
>>> -Sumit
>>> On 12/19/13 12:08 AM, "Ed Kohlwey" <ekohlwey@gmail.com> wrote:
>>>
>>>  Thanks. Is anyone aware if there is a way to get better debugging output
>>>> from the agent?
>>>>
>>>>
>>>> On Wed, Dec 18, 2013 at 11:41 PM, Sumit Mohanty
>>>> <smohanty@hortonworks.com>wrote:
>>>>
>>>>    You are right. The 2.0._ stack is the one that has support for
>>>>> dynamic
>>>>>   stack. However, that code is under active development and thus there
>>>>>
>>>> may
>>>
>>>>   be intermittent issues like you are seeing. I will ensure that the
>>>>>   developers working on this capability take a look into this issue.
>>>>>
>>>>>   -Sumit
>>>>>
>>>>>   On 12/18/13 8:20 PM, "Ed Kohlwey" <ekohlwey@gmail.com> wrote:
>>>>>
>>>>>    >I'm deploying 2.0._ - and looking to work on the dynamic stack
>>>>>>
>>>>> changes
>>>
>>>>   >(which I understand from Nate Cole are only available within that
>>>>>>
>>>>> stack).
>>>
>>>>   >
>>>>>>   >It looks like the issue may be within manifestGenerator.py
on lines
>>>>>>
>>>>> 167
>>>
>>>>   >and
>>>>>>   >172 (earlier trunk check out today, assume it hasn't changed)
-
>>>>>>
>>>>> there's no
>>>
>>>>   >input validation so I assume thats how the un-escaped strings are
>>>>>>
>>>>> getting
>>>
>>>>   >in.
>>>>>>   >
>>>>>>   >I'm currently trying to test a patch but the agent keeps cleaning
>>>>>> up
>>>>>>
>>>>> the
>>>
>>>>   >generated site-xx.pp files before I can get to them. Is there a way
>>>>>>
>>>>> to
>>>
>>>>   >turn
>>>>>>   >off this behavior?
>>>>>>   >
>>>>>>   >
>>>>>>   >On Wed, Dec 18, 2013 at 10:13 PM, Sumit Mohanty
>>>>>>   ><smohanty@hortonworks.com>wrote:
>>>>>>   >
>>>>>>
>>>>>>>   >> What version of the stack are you deploying? Try deploying
2.0.6
>>>>>>>
>>>>>> and
>>> see
>>>
>>>>   >> if the issue reproduces. I had deployed the same a few days back.
>>>>>>>   >>
>>>>>>>   >> -Sumit
>>>>>>>   >>
>>>>>>>   >> On 12/18/13 6:19 PM, "Ed Kohlwey" <ekohlwey@gmail.com>
wrote:
>>>>>>>   >>
>>>>>>>
>>>>>>>>   >> >I'm attempting to get started with ambari
development, and
>>>>>>>> while
>>>>>>>>
>>>>>>>   >>setting
>>>>>>>
>>>>>>>>   >> >up
>>>>>>>>   >> >an environment based on a trunk checkout I
noticed that my
>>>>>>>> agent
>>>>>>>>
>>>>>>>   >>scripts
>>>>>>>
>>>>>>>>   >> >appear the be producing malformed package_list
strings. Here's
>>>>>>>>
>>>>>>> an
>>>
>>>>   >>example:
>>>>>>>
>>>>>>>>   >> >
>>>>>>>>
>>>>>>>   >>
>>>>>>>
>>>>>>>>
>>>>>>>>  $package_list="[{"type":"rpm","name":"libganglia-3.5.0-99"},
>>>>>> {"type":"rpm
>>>>>>
>>>>>>>   >>>",
>>>>>>>>
>>>>>>>   >>
>>>>>>>
>>>>>>>>
>>>>>>>>  "name":"ganglia-devel-3.5.0-99"},{"type":"rpm","name":"
>>>>>> ganglia-gmetad-3.
>>>>>>
>>>>>>>   >>>5.
>>>>>>>>
>>>>>>>   >>
>>>>>>>
>>>>>>>>
>>>>>>>>  0-99"},{"type":"rpm","name":"ganglia-web-3.5.7-99.noarch"},
>>>>>> {"type":"rpm"
>>>>>>
>>>>>>>   >>>,"
>>>>>>>>
>>>>>>>   >>
>>>>>>>
>>>>>>>>
>>>>>>>>  name":"python-rrdtool.x86_64"},{"type":"rpm","name":"
>>>>>> ganglia-gmond-3.5.0
>>>>>>
>>>>>>>   >>>-9
>>>>>>>>   >>
>>>>>>>>
>>>>>>> 9"},{"type":"rpm","name":"ganglia-gmond-modules-python-3.5.0-99"}]"
>>>>
>>>>>   >> >
>>>>>>>>   >> >The inner quotes are not escaped so puppet
fails to parse the
>>>>>>>>
>>>>>>> .pp
>>>
>>>>   >>files.
>>>>>>>
>>>>>>>>   >> >
>>>>>>>>   >> >Has anyone encountered this issue? Does anyone
have any ideas
>>>>>>>>
>>>>>>> about
>>>
>>>>   >>what
>>>>>>>
>>>>>>>>   >> >to
>>>>>>>>   >> >do about it?
>>>>>>>>
>>>>>>>   >>
>>>>>>>   >>
>>>>>>>   >>
>>>>>>>   >> --
>>>>>>>   >> CONFIDENTIALITY NOTICE
>>>>>>>   >> NOTICE: This message is intended for the use of the
individual
>>>>>>> or
>>>>>>>   >>entity to
>>>>>>>   >> which it is addressed and may contain information
that is
>>>>>>>
>>>>>> confidential,
>>>
>>>>   >> privileged and exempt from disclosure under applicable law. If
the
>>>>>>>   >>reader
>>>>>>>   >> of this message is not the intended recipient, you
are hereby
>>>>>>>
>>>>>> notified
>>>
>>>>   >>that
>>>>>>>   >> any printing, copying, dissemination, distribution,
disclosure
>>>>>>> or
>>>>>>>   >> forwarding of this communication is strictly prohibited.
If you
>>>>>>>
>>>>>> have
>>>
>>>>   >> received this communication in error, please contact the sender
>>>>>>>   >>immediately
>>>>>>>   >> and delete it from your system. Thank You.
>>>>>>>   >>
>>>>>>>
>>>>>>
>>>>>
>>>>>   --
>>>>>   CONFIDENTIALITY NOTICE
>>>>>   NOTICE: This message is intended for the use of the individual or
>>>>>
>>>> entity to
>>>
>>>>   which it is addressed and may contain information that is
>>>>> confidential,
>>>>>   privileged and exempt from disclosure under applicable law. If the
>>>>>
>>>> reader
>>>
>>>>   of this message is not the intended recipient, you are hereby notified
>>>>>
>>>> that
>>>
>>>>   any printing, copying, dissemination, distribution, disclosure or
>>>>>   forwarding of this communication is strictly prohibited. If you have
>>>>>   received this communication in error, please contact the sender
>>>>>
>>>> immediately
>>>
>>>>   and delete it from your system. Thank You.
>>>>>
>>>>>
>>>
>>> --
>>> CONFIDENTIALITY NOTICE
>>> NOTICE: This message is intended for the use of the individual or entity
>>> to
>>> which it is addressed and may contain information that is confidential,
>>> privileged and exempt from disclosure under applicable law. If the reader
>>> of this message is not the intended recipient, you are hereby notified
>>> that
>>> any printing, copying, dissemination, distribution, disclosure or
>>> forwarding of this communication is strictly prohibited. If you have
>>> received this communication in error, please contact the sender
>>> immediately
>>> and delete it from your system. Thank You.
>>>
>>>
>
> --
> CONFIDENTIALITY NOTICE
> NOTICE: This message is intended for the use of the individual or entity
> to which it is addressed and may contain information that is confidential,
> privileged and exempt from disclosure under applicable law. If the reader
> of this message is not the intended recipient, you are hereby notified that
> any printing, copying, dissemination, distribution, disclosure or
> forwarding of this communication is strictly prohibited. If you have
> received this communication in error, please contact the sender immediately
> and delete it from your system. Thank You.
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message