Bob
That is really interesting and thanks for following up. It was
particularly confusing because from a logs and thread dump pov all
looked ready to roll. I dont understand what the deal was there.
Thanks
Joe
On Thu, Jan 11, 2018 at 12:51 PM, Bob Mroczka wrote:
>
For what its worth I found the root cause of this issue to be that I was
invoking run-nifi.bat through a junctioned path. Apparently java or possibly
jetty does not work through either symlinked or junctioned paths on Windows. I
had originally created a junctioned path to facilitate future
I thought that might be the issue as well. I installed Firefox on the server
and attempted to access the UI on localhost but still the same issue. I even
installed wget and it returns the same 404 error:
D:\>wget -O- -S http://localhost:8080/nifi
--2018-01-10 08:44:14--
Bob
The logs you sent are for an up and running and good to go looking
Apache NiFi 1.4.0 install.
I'm wondering if your browser has some sort of proxy settings or
something that is preventing web requests from getting to NiFi.
Please try to validate the browser settings and/or bypass the browser
I'm still having an issue getting to the Nifi UI on Windows using Nifi 1.4.0.
I've tried a number of different things. I've tried both java 8 and 9 jvm's.
I've tried a default configuration with no security. I've tried setting it up
on different Windows servers. I was able to use Nifi on
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
(slo archive review on startup).
Thanks
On Thu, Jan 4, 2018 at 9:38 AM, Mark Payne
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
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
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
ok yeah the user log is what i was curious about.
that is interesting. can you please run
bin/nifi.sh dump
then share the bootstrap.log.
one log at a time we will get there
On Jan 3, 2018 6:57 PM, "Bob Mroczka" wrote:
> The only log files I see being written to
The only log files I see being written to are the nifi-app.log,
nifi-bootstrap.log, and the nifi-user.log. None of these files show any access
attempts.
HCSC Company Disclaimer
The information contained in this communication is confidential, private,
proprietary, or otherwise privileged and is
hmm..ill have to get to a computer to compare logs. nothing obvious to me
there yet.
do your access logs show the requests?
please share those too.
On Jan 3, 2018 6:41 PM, "Bob Mroczka" wrote:
> The URL I’m trying to access is listed in the app-log, third line
The URL I’m trying to access is listed in the app-log, third line from the
bottom:
https://dchiswifss01.adhcscdev.net:9091/nifi
HCSC Company Disclaimer
The information contained in this communication is confidential, private,
proprietary, or otherwise privileged and is intended only for the use
can you show what url you are trying to access?
On Jan 3, 2018 6:28 PM, "Bob Mroczka" wrote:
>
>
> HCSC Company Disclaimer
>
> The information contained in this communication is confidential, private,
> proprietary, or otherwise privileged and is intended only for the
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
hello
please share the contents of the nifi app log. might need to creat a jira
and attach or something similar.
thanks
joe
On Jan 3, 2018 6:16 PM, "Bob Mroczka" wrote:
> I’ve installed a standalone Nifi 1.4.0 instance on a Windows 2012 R2
> server. The instance
16 matches
Mail list logo