Re: centos update and opennms run fails after update

JohnD Blackburn <[email protected]> Mon, 17 Sep 2018 00:17:14 +0000
Newsgroups gmane.network.opennms.general
Message-ID <AM6PR0602MB3381EAAFE01C6F47F6E4BBDDCB1E0@AM6PR0602MB3381.eurprd06.prod.outlook.com>
If your OpenNMS installation has been updated, you would also need to run $OPENNMS_HOME/bin/install -dis









From: Chuck harpham [mailto:[email protected]]
Sent: Friday, 14 September 2018 10:00 AM
To: General OpenNMS Discussion <[email protected]>
Subject: Re: [opennms-discuss] centos update and opennms run fails after update

CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.

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
[linkedin icon]
linkedin.com/in/charpham411<https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Flinkedin.com%2Fin%2Fcharpham411&data=02%7C01%7Cjohnd.blackburn%40au.abb.com%7Ca1594074993241cbd8a908d619d5342a%7C372ee9e09ce04033a64ac07073a91ecd%7C0%7C0%7C636724800842179474&sdata=Stevm7uNuI3Mw1y6Qj5iBUeCF5s7YL9lUJTDYWaoJ3k%3D&reserved=0>

On Thu, Sep 13, 2018 at 4:42 PM, <[email protected]<mailto:[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]<mailto:[email protected]>
300 S. Hamilton Pl.
Gilbert, AZ 85233
Phone: (480) 610-3500
Fax: (480) 610-3501
www.PerformAir.com<https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.PerformAir.com&data=02%7C01%7Cjohnd.blackburn%40au.abb.com%7Ca1594074993241cbd8a908d619d5342a%7C372ee9e09ce04033a64ac07073a91ecd%7C0%7C0%7C636724800842189478&sdata=On7pqNAYvUS%2BbLGQaluUEX1nWdZnArTmyxeFYG8BGSU%3D&reserved=0>


From: Chuck harpham [mailto:[email protected]<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<https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.freedesktop.org%2Fmailman%2Flistinfo%2Fsystemd-devel&data=02%7C01%7Cjohnd.blackburn%40au.abb.com%7Ca1594074993241cbd8a908d619d5342a%7C372ee9e09ce04033a64ac07073a91ecd%7C0%7C0%7C636724800842189478&sdata=dtZwJul3p3Hc7k0S%2F9HOJj5kJOPAmiGpUbw%2BytfrAQI%3D&reserved=0>
--
-- 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<https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Flinkedin.com%2Fin%2Fcharpham411&data=02%7C01%7Cjohnd.blackburn%40au.abb.com%7Ca1594074993241cbd8a908d619d5342a%7C372ee9e09ce04033a64ac07073a91ecd%7C0%7C0%7C636724800842199497&sdata=sr7aDnScdMiulV%2F5EXetOr68cGurZqe2MWEBuenuM7w%3D&reserved=0>

_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ<https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.opennms.org%2Findex.php%2FMailing_List_FAQ&data=02%7C01%7Cjohnd.blackburn%40au.abb.com%7Ca1594074993241cbd8a908d619d5342a%7C372ee9e09ce04033a64ac07073a91ecd%7C0%7C0%7C636724800842199497&sdata=eFJQA3UFUVNPPaFmG2AwMOEJxJOx2J0KmksYQAyzX3Q%3D&reserved=0>

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<https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.sourceforge.net%2Flists%2Flistinfo%2Fopennms-discuss&data=02%7C01%7Cjohnd.blackburn%40au.abb.com%7Ca1594074993241cbd8a908d619d5342a%7C372ee9e09ce04033a64ac07073a91ecd%7C0%7C0%7C636724800842209497&sdata=jnSpllr2Nrz26BZFZYmnbuHwHHUPoiPlCPbQMS1g2AE%3D&reserved=0>

_______________________________________________
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
image001.png (image/png, 604 B) - not displayed