ambari-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Novogrodsky <david.novogrod...@gmail.com>
Subject Re: problem starting the Ambari server after running upgrade. Should I remove postgre?
Date Mon, 15 Dec 2014 19:09:58 GMT
OK, I fixed the problem.  I used yum to uninstall ambari and associated
packages, including postgre.  Then I re-installed Ambari using yum and ran
ambari-server install.  It worked.

David Novogrodsky
david.novogrodsky@gmail.com
http://www.linkedin.com/in/davidnovogrodsky

On Mon, Dec 15, 2014 at 11:53 AM, Yusaku Sako <yusaku@hortonworks.com>
wrote:
>
> Hi there,
>
> Do you mean you are running Ambari 1.6.1 and you are trying to upgrade to
> Ambari 1.7.0?  (There is no Ambari 1.7.1).
> What steps did you follow for upgrading?  Did you download the repo file
> for 1.7.0 and performed "yum upgrade ambari-server ambari-agent", etc?
>
> Yusaku
>
> On Mon, Dec 15, 2014 at 8:35 AM, David Novogrodsky <
> david.novogrodsky@gmail.com> wrote:
>>
>> I am running Ambari version 1.7.1.  I have been having some problem with
>> Ambari recognizing the nodes on the network.  I decided to try upgrading
>> using this command:
>> >>ambari-server upgrade
>>
>> When I tried to start the server, ambari-server start, I got this error:
>>   GNU nano 2.0.9                                         File:
>> /var/log/ambari-server/ambari-server.out
>>
>>
>> [EL Warning]: metadata: 2014-12-15
>> 10:28:33.117--ServerSession(335791427)--The reference column name
>> [resource_type_id] mapped on the element [field permissions] does not
>> correspond to a valid$
>> [EL Info]: 2014-12-15
>> 10:28:35.741--ServerSession(335791427)--EclipseLink, version: Eclipse
>> Persistence Services - 2.4.0.v20120608-r11652
>> [EL Info]: connection: 2014-12-15
>> 10:28:36.226--ServerSession(335791427)--file:/usr/lib/ambari-server/ambari-server-1.7.0.169.jar_ambari-server_url=jdbc:postgresql://localhost/postgres_user=am$
>> [EL Warning]: 2014-12-15 10:28:36.343--UnitOfWork(1435878060)--Exception
>> [EclipseLink-4002] (Eclipse Persistence Services - 2.4.0.v20120608-r11652):
>> org.eclipse.persistence.exceptions.Database$
>> Internal Exception: org.postgresql.util.PSQLException: ERROR: relation
>> "metainfo" does not exist
>>   Position: 46
>> Error Code: 0
>> Call: SELECT "metainfo_key", "metainfo_value" FROM metainfo WHERE
>> ("metainfo_key" = ?)
>>         bind => [1 parameter bound]
>> Query: ReadObjectQuery(name="readObject" referenceClass=MetainfoEntity
>> sql="SELECT "metainfo_key", "metainfo_value" FROM metainfo WHERE
>> ("metainfo_key" = ?)")
>>
>> I am not sure what are the next steps.
>> David Novogrodsky
>> david.novogrodsky@gmail.com
>> http://www.linkedin.com/in/davidnovogrodsky
>>
>
> 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
View raw message