Re: centos update and opennms run fails after update

You can learn which rps were installed, removed, or upgraded in
/var/log/yum.log.


Sincerely,
Mike
--
Mike Diehn
Enfield, NH

On Thu, Sep 13, 2018, 8:01 PM Chuck harpham <[email protected]> wrote:

> Thanks for your prompt response.. I ran into some other problems where I
> could not get it to run after modifying the rpmnew files... My installation
> is a home installation, so I think I am going to start fresh. I can afford
> to lose my current configuration as  I only have about 20 devices to
> monitor...
>
> thanks again
>
>
>
>
>
>
> *Notice of Confidentiality:*
> *This transmission constitutes an electronic communication within the
> meaning of the Electronic Commissions Privacy Act, 18 U.S.C. 2510, and its
> disclosure is strictly limited to the recipient intended by the sender of
> this message, together with any attachments.  This communication, including
> any attachments, may contain confidential and privileged material for the
> sole use of the intended individual or entity, and receipt by any party
> other than the intended recipient does not constitute a loss of the
> confidential or privileged nature of the communication. *
>
> *Any review or distribution by others is prohibited:*  *If you are not
> the intended recipient, you are hereby notified that any dissemination,
> distribution, or copying of this message, or any attachment, is strictly
> prohibited.  If you have received this message in error, please notify the
> original sender immediately by telephone or by return E-mail and delete
> this message, along with any attachments, from your computer.*
> .
>
> Thank you kindly
>
> chuck harpham
> _____
> |__/__|
> (0||||0)
>
> Sit vis vobiscum
>
> [image: linkedin icon]
> linkedin.com/in/charpham411
>
> On Thu, Sep 13, 2018 at 4:42 PM, <[email protected]> wrote:
>
>> Chuck;
>>
>> When Yum installs updates, it recognizes when a file has been modified
>> from the previously installed version.  One of the options for dealing with
>> this (I believe it prompts if run interactively) is to save the new file
>> with .rpmnew added to the end.
>>
>> Apparently OpenNMS, or one of its enabling technologies, looks for this
>> files, and if present, treats them as an error.
>>
>> The first step is to identify which files it might have a problem with.
>> find $OPENNMS_HOME/ -name *.rpmnew
>> should show you the files the OpenNMS has a problem with.
>>
>> Then open each of those .rpmnew files, and mentally compare it to the
>> file without .rpmnew, or use a diff tool.  In particular you need to look
>> for changed configuration syntax.
>>
>> When your happy with where you're at, move the .rpmnew files (or change
>> the .rpmnew to .default or something), and OpenNMS should be happy (unless
>> you left old syntax in one or more files).
>>
>> Thank you,
>>
>> Dominic L. Hilsbos, MBA
>> Director – Information Technology
>> Perform Air International Inc.
>> [email protected]
>> 300 S. Hamilton Pl.
>> Gilbert, AZ 85233
>> Phone: (480) 610-3500
>> Fax: (480) 610-3501
>> www.PerformAir.com
>>
>>
>> From: Chuck harpham [mailto:[email protected]]
>> Sent: Thursday, September 13, 2018 3:48 PM
>> To: General OpenNMS Discussion
>> Subject: [opennms-discuss] centos update and opennms run fails after
>> update
>>
>> Hi
>>
>> I am having some problems running Opennms Horizon (I think ver 21.x) on
>> centos 7x. I ran an update for Centos which I think included some updates
>> for opennms (wish I could find the log file for this update to figure out
>> what updated)...  Now when I launch opennms services it fails to load.
>> looking at "journalctl -xe" I noticed it has failed and not sure what this
>> means.. wondering if someone can help me troubleshoot this thanks
>>
>> "-- Unit opennms.service has begun starting up.
>> Sep 13 20:04:22 .local opennms[6165]: Starting OpenNMS:
>> Sep 13 20:04:22 .local opennms[6165]: WARNING!  You have files that end
>> in .rpmnew in your
>> Sep 13 20:04:22 .local opennms[6165]: OPENNMS_HOME (/opt/opennms)
>> directory.
>> Sep 13 20:04:22 .local opennms[6165]: The format of the original files
>> may have changed since
>> Sep 13 20:04:22 .local opennms[6165]: you modified them before installing
>> a new version.
>> Sep 13 20:04:22 .local opennms[6165]: Please double-check that your
>> configuration files are
>> Sep 13 20:04:22 .local opennms[6165]: up-to-date and delete any leftover
>> .rpmnew files or
>> Sep 13 20:04:22 .local opennms[6165]: OpenNMS will not start.
>> Sep 13 20:04:22 .local opennms[6165]: [FAILED]
>> Sep 13 20:04:22 .local systemd[1]: opennms.service: control process
>> exited, code=exited status=6
>> Sep 13 20:04:22 .local systemd[1]: Failed to start OpenNMS server.
>> -- Subject: Unit opennms.service has failed
>> -- Defined-By: systemd
>> -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
>> --
>> -- Unit opennms.service has failed.
>> --
>> -- The result is failed.
>> Sep 13 20:04:22 .local systemd[1]: Unit opennms.service entered failed
>> state.
>> Sep 13 20:04:22 .local systemd[1]: opennms.service failed.
>> Sep 13 20:04:22 .local polkitd[775]: Unregistered Authentication Agent
>> for unix-process:6159:452393 (system bus name :1.154, object path
>> /org/freede
>> lines 2577-2617/2617 (END)
>>
>>
>>
>>
>> Notice of Confidentiality:
>> This transmission constitutes an electronic communication within the
>> meaning of the Electronic Commissions Privacy Act, 18 U.S.C. 2510, and its
>> disclosure is strictly limited to the recipient intended by the sender of
>> this message, together with any attachments.  This communication, including
>> any attachments, may contain confidential and privileged material for the
>> sole use of the intended individual or entity, and receipt by any party
>> other than the intended recipient does not constitute a loss of the
>> confidential or privileged nature of the communication.
>>
>> Any review or distribution by others is prohibited:  If you are not the
>> intended recipient, you are hereby notified that any dissemination,
>> distribution, or copying of this message, or any attachment, is strictly
>> prohibited.  If you have received this message in error, please notify the
>> original sender immediately by telephone or by return E-mail and delete
>> this message, along with any attachments, from your computer.
>> .
>>
>> Thank you kindly
>>
>> chuck harpham
>> _____
>> |__/__|
>> (0||||0)
>>
>> Sit vis vobiscum
>>
>> linkedin.com/in/charpham411
>>
>> _______________________________________________
>> Please read the OpenNMS Mailing List FAQ:
>> http://www.opennms.org/index.php/Mailing_List_FAQ
>>
>> opennms-discuss mailing list
>>
>> To *unsubscribe* or change your subscription options, see the bottom of
>> this page:
>> https://lists.sourceforge.net/lists/listinfo/opennms-discuss
>
>
> _______________________________________________
> Please read the OpenNMS Mailing List FAQ:
> http://www.opennms.org/index.php/Mailing_List_FAQ
>
> opennms-discuss mailing list
>
> To *unsubscribe* or change your subscription options, see the bottom of
> this page:
> https://lists.sourceforge.net/lists/listinfo/opennms-discuss

_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss