Re: [opennms-discuss] Waiting for availability data. One or more categories have never been updated.

[Showers, W. <Sho...@pt...>]

I had this same issue after upgrading to 19.

Check your users.xml for an entry like this

        <user>
            <user-id>rtc</user-id>
            <full-name>RTC</full-name>
            <user-comments>RTC user, do not delete</user-comments>
            <password>68154466F81BFB532CD70F8C71426356</password>
            <role>ROLE_RTC</role>
        </user>



-----Original Message-----
From: Dan Stevenson [mailto:dan...@pr...]
Sent: Thursday, February 23, 2017 11:03 AM
To: General OpenNMS Discussion <ope...@li...>
Subject: Re: [opennms-discuss] Waiting for availability data. One or more categories have never been updated.

Don't know if it is related but I also found these entries in the web log:

2017-02-23 10:56:43,821 WARN  [qtp287382196-19503]
o.o.w.s.s.HybridOpenNMSUserAuthenticationProvider: Password auth failed for user: rtc

How would I reset the password for the RTC user? I thought this user was automatically setup by OpenNMS during the install.



Sanders Home Services
On 2/23/2017 9:28 AM, Dan Stevenson wrote:
> After working through a couple issues with the latest upgrade I was
> finally able to start OpenNMS and log in again. Now there is no data
> showing for any categories. I started reading through the log files and
> came across entries like this in the rtc.log:
>
> 2017-02-23 09:05:02,588 WARN  [DataSender-Thread-1-of-5]
> o.o.n.r.DataSender: DataSender:  Unable to send category 'Routers' to
> URL 'http://localhost:8980/opennms/rtc/post/Routers'
> java.io.IOException: Server returned HTTP response code: 401 for URL:
> http://localhost:8980/opennms/rtc/post/Routers
>       at
> sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1876)
> ~[?:1.8.0_121]
>       at
> sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1474)
> ~[?:1.8.0_121]
>       at org.opennms.netmgt.rtc.HttpUtils.post(HttpUtils.java:257)
> ~[opennms-services-19.0.1.jar:?]
>       at org.opennms.netmgt.rtc.DataSender$1.run(DataSender.java:256)
> [opennms-services-19.0.1.jar:?]
>       at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> [?:1.8.0_121]
>       at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> [?:1.8.0_121]
>       at
> org.opennms.core.concurrent.LogPreservingThreadFactory$3.run(LogPreservingThreadFactory.java:124)
> [opennms-util-19.0.1.jar:?]
>       at java.lang.Thread.run(Thread.java:745) [?:1.8.0_121]
>
> The same message is shown for every category. I'm not sure where to look
> next. Any ideas would be appreciated.
>
> Thanks,
> Dan
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
> _______________________________________________
> 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


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
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



This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, notify the sender immediately by return email and delete the message and any attachments from your system.