You are viewing a plain text version of this content. The canonical link for it is here.

Posted to users@nifi.apache.org by Bob Mroczka <Ro...@bcbsil.com> on 2018/01/03 23:16:53 UTC

Getting 404 from Nifi UI on new installation

I've installed a standalone Nifi 1.4.0 instance on a Windows 2012 R2 server.   The instance starts successfully and there are no errors in either the bootstrap or app logs but when I attempt to access the UI I get the following 404 page.  I've attempted to enable debugging in the logback.xml file but nothing stands out.  Any suggestions on troubleshooting this issue?

HTTP ERROR 404

Problem accessing /nifi/. Reason:

    Not Found

________________________________
Powered by Jetty:// 9.4.3.v20170317<http://eclipse.org/jetty>

HCSC Company Disclaimer

The information contained in this communication is confidential, private,
proprietary, or otherwise privileged and is intended only for the use of
the addressee.  Unauthorized use, disclosure, distribution or copying is
strictly prohibited and may be unlawful.  If you have received this
communication in error, please notify the sender immediately at
(312)653-6000 in Illinois; (800) 447-7828 in Montana;
(800)835-8699 in New Mexico; (918)560-3500 in Oklahoma; 
or (972)766-6900 in Texas.

RE: Getting 404 from Nifi UI on new installation

Posted by Joe Witt <jo...@gmail.com>.

should go to nifi-bootstrap.log by default

On Jan 3, 2018 7:07 PM, "Bob Mroczka" <Ro...@bcbsil.com> wrote:

> I’ve sanitized the user log a bit but everything else is there.  Since
> this is Windows I ran dump-nifi.bat but it doesn’t show where the output
> file was stored.
>
> HCSC Company Disclaimer
>
> The information contained in this communication is confidential, private,
> proprietary, or otherwise privileged and is intended only for the use of
> the addressee.  Unauthorized use, disclosure, distribution or copying is
> strictly prohibited and may be unlawful.  If you have received this
> communication in error, please notify the sender immediately at
> (312) 653-6000 in Illinois; (800) 447-7828 in Montana;
> (800)835-8699 <(800)%20835-8699> in New Mexico; (918)560-3500
> <(918)%20560-3500> in Oklahoma;
> or (972)766-6900 <(972)%20766-6900> in Texas.
>

Re: Getting 404 from Nifi UI on new installation

Posted by Joe Witt <jo...@gmail.com>.

Bob

In the latests thread dumps things look good now with the archive
thread.  So it seems like it should be running now (please send latest
app log if not) and it seems like what mark suggested is the issue
(slowwww archive review on startup).

Thanks

On Thu, Jan 4, 2018 at 9:38 AM, Mark Payne <ma...@hotmail.com> wrote:
> Bob,
>
> I believe what you're running into is NIFI-4737 [1]. When NiFi starts up, it
> is scanning the content repository
> to see which files should be aged off from the archive first. Unfortunately
> it does not log the fact that it is
> doing this, so everything seems okay... I think the first step is to add in
> some logging to at least make it obvious
> what is happening. Then we can look at ways to make it faster on startup.
>
> Thanks
> -Mark
>
>
> [1] https://issues.apache.org/jira/browse/NIFI-4737
>
>
> On Jan 3, 2018, at 9:39 PM, Joe Witt <jo...@gmail.com> wrote:
>
> Bob,
>
> There should be more in the app log after that controller
> initialization line and of course there should be things in the user
> log for when you're attempting access.  Looking at the stack dump I'm
> thinking there is an issue with archive cleanup/management.  It is
> either stuck on a native call or it is just taking a long time.
>
> Can you please grab a couple more stack dumps at about 60 second
> intervals.  Then send the bootstrap log (and any rollovered bootstrap
> logs) again.  What i'm keying in on is this
>
> "Cleanup Archive for default" Id=47 RUNNABLE
> at sun.nio.fs.WindowsNativeDispatcher.CreateFile0(Native Method)
> at
> sun.nio.fs.WindowsNativeDispatcher.CreateFile(WindowsNativeDispatcher.java:71)
> at sun.nio.fs.WindowsChannelFactory.open(WindowsChannelFactory.java:302)
> at
> sun.nio.fs.WindowsChannelFactory.newFileChannel(WindowsChannelFactory.java:162)
> at
> sun.nio.fs.WindowsFileSystemProvider.checkReadAccess(WindowsFileSystemProvider.java:325)
> at
> sun.nio.fs.WindowsFileSystemProvider.checkAccess(WindowsFileSystemProvider.java:362)
> at java.nio.file.Files.exists(Files.java:2385)
> at
> org.apache.nifi.controller.repository.FileSystemRepository.destroyExpiredArchives(FileSystemRepository.java:1335)
> at
> org.apache.nifi.controller.repository.FileSystemRepository.access$1700(FileSystemRepository.java:84)
> at
> org.apache.nifi.controller.repository.FileSystemRepository$DestroyExpiredArchiveClaims.run(FileSystemRepository.java:1572)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> Number of Locked Synchronizers: 1
> - java.util.concurrent.ThreadPoolExecutor$Worker@43a72f0f
>
> Thanks
> Joe
>
> On Wed, Jan 3, 2018 at 7:10 PM, Bob Mroczka <Ro...@bcbsil.com>
> wrote:
>
> Looks like the thread dump went to the bootstrap log.  See attached.
>
>
>
>
>
> HCSC Company Disclaimer
>
> The information contained in this communication is confidential, private,
> proprietary, or otherwise privileged and is intended only for the use of
> the addressee.  Unauthorized use, disclosure, distribution or copying is
> strictly prohibited and may be unlawful.  If you have received this
> communication in error, please notify the sender immediately at
> (312) 653-6000 in Illinois; (800) 447-7828 in Montana;
> (800)835-8699 in New Mexico; (918)560-3500 in Oklahoma;
> or (972)766-6900 in Texas.
>
>