Support Questions

Find answers, ask questions, and share your expertise
Announcements
Check out our newest addition to the community, the Cloudera Data Analytics (CDA) group hub.

Cloudera Manager 5.10 - Error when accessing alert screen

New Contributor

Hello,

 

I've upgraded Cloudera Manager from version 5.9 to 5.10 and the alerts admin is not working anymore.

I get the following error :

 

Chemin: http://xxxxxxxx:7180/cmf/alerts/config

Version: Cloudera Express 5.10.0 (#85 built by jenkins on 20170120-1038 git: aa0b5cd5eceaefe2f971c13ab657020d96bb842a)

java.lang.NullPointerException:
at AlertData.java line 127
in com.cloudera.server.web.cmf.AlertData isParamSpecEnabled()
41 REPLIES 41

Explorer

Problem occuring on our 5.10 install. 

 

Please advise.

Explorer
Same problem upgraded from 5.7 to 5.11. Any updates?

Explorer
Did anyone solved this problem? Can someone respond please?

Hello, 

 

It's strange how long it's taking Cloudera to fix this issue.

I repeat the post I sent on February 16.

 

"

I already found the problem and I have a version that is OK.
I can not pass the changes due to Cloudera policies.
But if Cloudera needs my collaboration contact me in the way you think is the right one.

"

 

 

Community Manager

I'm dropping in here to let everyone know I'm checking with the team for the status on this. I'll reply back when I know more.  


Cy Jervis, Manager, Community Program
Was your question answered? Make sure to mark the answer as the accepted solution.
If you find a reply useful, say thanks by clicking on the thumbs up button.

Master Collaborator

I have an information that this issue is fixed (or not present) in commercial version od CDH. So everybody here complaining about the failed alert should be using Express Edition.

Or do I have a wrong source and somebody here running into this issue in CDH Enterprise Edition?

 

Super Guru

Everyone,

 

I didn't realize that this thread had not received a progress report.

We were not able to artificially recreate the problem so we adjusted the code to ensure that the result of the problem would not prevent the page from being usable.

This fix is slated for Cloudera Manager 5.12.

 

I am working with engineering to figure out what to do in the short term for 5.10 and 5.11 to get the fix available.

We will update you soon once we know what the gameplan is.

 

Thank you for all your patience and sorry that you have been impacted by this issue.

 

Regards,

 

Ben

Super Guru

@Tomas79,

 

Please share the background of your assumption.  That shouldn't be the case, but I'd like to hear how that assumption was developed.  We have created now fix for this that is available at this time.

 

Thanks,

 

Ben

Master Collaborator
The background is simple, some users running on commercial editions proved that this is not an issue nor in 5.10 nor in 5.11. And based by Gustavo comment it seems to be true.
But good to see an update, that 5.12 will fix this.
Thanks Ben

Hi @Tomas79,

 

On 05-08-2017, exactly one month ago, I sent the change in the code to avoid the bug to @cjervis (Cloudera) by private message. With that change in the code I have the version 5.11 Express Edition working correctly.

 

According to my research the problem is related to the Express Edition, since the problem is linked to the roles REPORTSMANAGER, NAVIGATOR, NAVIGATORMETASERVER that in that version are not included.

 

While I already have all the process built to change the Java class with the problem every time I upgrade the Cloudera Manager, I think it is time for Cloudera to solve the problem, since it is so simple solution.

 

 

 

Super Guru

@GustavoVarisco,

 

Absolutely; we thank you for all the help in this.

Addressing the NPE would have solved the immediate problem, but we were going for fixing whatever was broken to lead to the NPE.  In doing so, it took much longer than we hoped to resolve.  Of course that doesn't make the fact that it is broken for you and many other users...

 

At this point, we have a proposed fix that is slated for CM 5.12 and we will update you as soon as we discuss with engineering what we can do to get the fix into 5.10 and 5.11 branches, etc.

 

Ben

Super Guru

@GustavoVarisco, You ROCK!

 

I just installed CM 5.10.1 using the Cloudera Express license and BOOM!

 

Version: Cloudera Express 5.10.1 (#6 built by jenkins on 20170319-2001 git: f226435f6fa5f545543c00245900ae43bea7a29c)

java.lang.NullPointerException:
at AlertData.java line 127
in com.cloudera.server.web.cmf.AlertData isParamSpecEnabled()
 
 
I'll convey to Cloudera engeering.
 
 
Ben
 

Super Collaborator

Is there an estimations where 5.12 will be released?

 

Is there a manual a work around for this?

Expert Contributor

This issue will be resolved in the upcoming 5.10.2 and 5.11.2 maintenance releases, in addition to the 5.12 release.

Super Collaborator
Thanks,

Do we expect when this will happen?

I'm upgrading my cluster once a year and want to know if it wait for it or
not.

Expert Contributor

C5.10.2 is supposed to be released this week. Release date for 5.11.2 is not defined yet, though.

Expert Contributor

C5.10.2 is supposed to be released this week.

C5.11.2 release date is not defined yet.

C5.12 release is planned for late July.

Explorer

Did anyone fixed this problem without upgrading CDH?

 

 

I'm using CDH 5.10.1

Expert Contributor
Just for clarification, to get the fix you need to upgrade Cloudera Manager only. CDH upgrade is not needed.

New Contributor

Same problem here. Hope a solution is available soon.

New Contributor
I've upgraded Cloudera Manager from version 5.9 to 5.10 and the alerts admin is not working anymore.HELP~
Take a Tour of the Community
Don't have an account?
Your experience may be limited. Sign in to explore more.