Support Questions

Find answers, ask questions, and share your expertise
Announcements
Celebrating as our community reaches 100,000 members! Thank you!

Apache NiFi Canvas loading issue

avatar
New Contributor

NiFi canvas (Version 1.14) is  failing to load when launched with the loading indicator being indefinitely shown on the screen . The console has the following two  errors:

Uncaught Error: SlickGrid requires a valid container, #controlle-service-types-table does not exist in the DOM.

Uncaught TypeError : can not read properties of undefined (reading 'get')

Uncaught TypeError : can not read properties of undefined (reading 'top')

 

This issue is observed intermittently  on a particular environment while it works fine in other environments.

 

Thanks,

Pratyush

 

 

 

2 REPLIES 2

avatar
New Contributor

@Pratyush1MaryKayInTouch wrote:

NiFi canvas (Version 1.14) is  failing to load when launched with the loading indicator being indefinitely shown on the screen . The console has the following two  errors:

Uncaught Error: SlickGrid requires a valid container, #controlle-service-types-table does not exist in the DOM.

Uncaught TypeError : can not read properties of undefined (reading 'get')

Uncaught TypeError : can not read properties of undefined (reading 'top')

 

This issue is observed intermittently  on a particular environment while it works fine in other environments.

 

Thanks,

Pratyush

 

 

 


Hello,

The errors you're encountering suggest an issue with the NiFi canvas initialization process. Here's a breakdown and potential solutions:

Errors:

Uncaught Error: SlickGrid requires a valid container, #controlle-service-types-table does not exist in the DOM.

This means the HTML element with the ID "controlle-service-types-table" is missing when the canvas tries to interact with it using the SlickGrid library (used for tables).

Uncaught TypeError : can not read properties of undefined (reading 'get') & (reading 'top')
These errors indicate NiFi tries to access properties (like "get" or "top") on an element that doesn't exist or hasn't loaded yet.
Possible Causes (Since it's intermittent):

JavaScript Errors: There might be other JavaScript errors on the page preventing the DOM from loading correctly. Check browser developer console for additional errors.
Network Issues: Temporary network delays during canvas initialization could cause some elements to load after the script tries to access them.

Browser Caching: Cached browser data might be causing conflicts. Try clearing your browser cache and reloading NiFi.

Troubleshooting Steps:

Check Browser Console: Open the developer console in your browser (usually by pressing F12) and look for any additional errors besides the ones mentioned. These might provide more specific clues.

Clear Browser Cache: Clear your browser cache and hard reload the NiFi canvas (Ctrl+Shift+R).

Network Monitoring: If network issues are suspected, monitor network activity during canvas load using developer tools. Look for slow loading resources.

NiFi Logs: Check the NiFi logs for any additional error messages related to canvas initialization.

I hope the information may help you. 

 

avatar
Super Mentor

@Pratyush1 

The more detail you can provide, the better here.

In addition to what @cassie2698bratt suggested:

Apache NiFi 1.14 was released 3 years ago and has had many important bug fixed, security fixes, and improvements since then,  The latest 1.x release is Apache NiFi 1.26 as of writing this response.  I strongly recommend upgrading to the latest release.

What Java vendor and version are you using with your NiFi.  NIFi supports Java 8 (and 11 in newer releases).  Java 8 update 252 or newer is required minimum.  All nodes consistently on same version?

What OS is being used on server where NiFi is having issue?

Is this a NiFi multi-node cluster?  Does UI of every node in same cluster present same issue while loading the UI or is it specific to just one node in the cluster?

Any custom code add-ons?

Are the other systems using the same Java and NiFi versions?

Any observations in the NiFi logs when accessing the UI?

Thank you,
Matt