Problem using HTTP file manager

Notes, tips, and other usefull things on how to use LogMX

Moderator: admin

Post Reply
flequi.dph
Posts: 5
Joined: Mon Jan 08, 2018 12:15 pm

Problem using HTTP file manager

Post by flequi.dph » Mon Jan 08, 2018 12:38 pm

Hi.

I'm tried to use the Http file Manager to view how works this application, but I can't configure to work fine, these are the steps i did it:

1. Click on Open Log(s) and configure the Host and File fields (data isn't real but it's equivalent):
Host: logs01.dev.mydomain.local
File: folder/file.log

2. Obtained:
Error while reading "
http://logs01.dev.mydomain.local/folder/file.log".
[IOException] - Server returned HTTP response code: 401 for URL:
http://logs01.dev.mydomain.local:80/folder/file.log

3. I configured the network account with my user/pass thats works fine in all the browsers:
logMXError.png
logMXError.png (28.42 KiB) Viewed 840 times
4. I configured the Proxy Settings with no proxy, like I have in my browsers settings for the URLs of mydomain.local.
proxiesLogMx.png
proxiesLogMx.png (34.67 KiB) Viewed 840 times
5. I push "Apply" and "Accept" to the Options Window.

6. I click on Open Logs with the same options of Host and File, and obtain the same error.

I don't know if the problem is for the Network configuration, the LogMX application that doesn't works like a browser, the http file manager or what???

This is the logMX information of the logMx log file:

08/01/18 12:57:15.886 [INFO] (com.lightysoft.logmx.MF) Opening "http://logs01.dev.mydomain.local/folder/file.log"...
08/01/18 12:57:15.890 [FINE] (com.lightysoft.logmx.ProxyManager) ProxySelector.select(http://logs01.dev.mydomain.local:80/folder/file.log) => use [DIRECT]
08/01/18 12:57:15.892 [FINE] (com.lightysoft.logmx.ProxyManager) ProxySelector.select(socket://logs01.dev.mydomain.local:80) => use [DIRECT]
08/01/18 12:57:15.963 [FINE] (com.lightysoft.logmx.ProxyManager) ProxySelector.select(http://logs01.dev.mydomain.local:80/folder/file.log) => use [DIRECT]
08/01/18 12:57:15.964 [FINE] (com.lightysoft.logmx.ProxyManager) ProxySelector.select(socket://logs01.dev.mydomain.local:80) => use [DIRECT]
08/01/18 12:57:16.037 [WARNING] (com.lightysoft.logmx._STDERR) java.io.IOException: Server returned HTTP response code: 401 for URL: http://logs01.dev.mydomain.local:80/folder/file.log
08/01/18 12:57:16.038 [WARNING] (com.lightysoft.logmx._STDERR) at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1839)
08/01/18 12:57:16.038 [WARNING] (com.lightysoft.logmx._STDERR) at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1440)
08/01/18 12:57:16.038 [WARNING] (com.lightysoft.logmx._STDERR) at java.net.URL.openStream(URL.java:1038)
08/01/18 12:57:16.038 [WARNING] (com.lightysoft.logmx._STDERR) at com.lightysoft.logmx.mgr.managers.HTTPFileManager.prepareForReading(X:179)
08/01/18 12:57:16.038 [WARNING] (com.lightysoft.logmx._STDERR) at com.lightysoft.logmx.mgr.l.a(X:110)
08/01/18 12:57:16.038 [WARNING] (com.lightysoft.logmx._STDERR) at ff.a(X:1501)
08/01/18 12:57:16.038 [WARNING] (com.lightysoft.logmx._STDERR) at fn.run(X:1434)

admin
Site Admin
Posts: 437
Joined: Sun Dec 17, 2006 10:30 pm

Re: Problem using HTTP file manager

Post by admin » Tue Jan 09, 2018 3:15 am

Hello,

You're right, and you just discovered a bug. Sorry about that.

Thank you for your (detailed!) feedback, I think it should be fixed in the next release, that should be available in a couple of weeks. Please let me know if you don't want to wait for the release, I will send you just the new HttpFileManager as soon as it is fixed. Otherwise, I will post a message in this thread to let you know when the next release is available.

Thank you.
Xavier

flequi.dph
Posts: 5
Joined: Mon Jan 08, 2018 12:15 pm

Re: Problem using HTTP file manager

Post by flequi.dph » Wed Jan 10, 2018 8:36 am

Ok, thanks for the quick response, sendme the new HTTP File Manager to test it.

Bye

admin
Site Admin
Posts: 437
Joined: Sun Dec 17, 2006 10:30 pm

Re: Problem using HTTP file manager

Post by admin » Tue Jan 16, 2018 4:18 am

Hi,

In the end, we had to slightly adjust the LogMX code in order to allow Authentication in HTTP[S] Log File Managers, so instead of sending you the new Log Manager only, I sent you (via Private Message on this forum) the links to nightly builds so you can try the new Log Manager.

Please let me know if you have any question or issue.

Xavier

flequi.dph
Posts: 5
Joined: Mon Jan 08, 2018 12:15 pm

Re: Problem using HTTP file manager

Post by flequi.dph » Tue Jan 16, 2018 10:06 am

Hi Xavier.

Now it works fine, I can connect and merge many files, I'm very surprised with this tool, good job.

Thanks

flequi.dph
Posts: 5
Joined: Mon Jan 08, 2018 12:15 pm

Re: Problem using HTTP file manager

Post by flequi.dph » Tue Jan 16, 2018 3:54 pm

Hi again.

Working with more files I've founded several errors:

With connection reset in 15 or 20 seconds.
ConnectionReset.png
ConnectionReset.png (13.47 KiB) Viewed 814 times
With parser error
NoSuitableParser.png
NoSuitableParser.png (29.01 KiB) Viewed 814 times
This is an error of my file, but does't works fine because if I push "SI/Yes" to parse now the tool don't lets me to parse it and it excludes the file automatically with no option for me.
SkippedForMerge.png
SkippedForMerge.png (27.77 KiB) Viewed 814 times
Bye

admin
Site Admin
Posts: 437
Joined: Sun Dec 17, 2006 10:30 pm

Re: Problem using HTTP file manager

Post by admin » Wed Jan 17, 2018 2:34 am

Hi,
  • About the first message: it seems that a network issue happened. When did this message show up? What is the file size? You said "With connection reset in 15 or 20 seconds". What does it mean?
  • About the second message: it means the log file you are trying to read is using a log format that none of your current Log Parser understands. If you click "Yes"/"SI", you will be able to create a new Log Parser for this log format.
  • About the third message: I'm not sure to understand your point. Do you mean that even if you choose "Yes"/"SI", LogMX doesn't try to parse the other files? If that's the case, maybe there is a real problem with these files (e.g. file doesn't exist, unknown log file format, network issue while reading the file, ...)
If you still have problems, please use the bug report feature in LogMX: menu "Help" > item "Report bug or enhancement...".
We will then analyze the problems you had.
Or, of course, you can reply to this message by giving more details, but at some point I may need some logs or information about your environment to find the cause of some issues.

Xavier

flequi.dph
Posts: 5
Joined: Mon Jan 08, 2018 12:15 pm

Re: Problem using HTTP file manager

Post by flequi.dph » Wed Jan 17, 2018 9:04 am

Hi.

The first point means that there is a connection reset like you say because a network connection, it's posible to be an error of my net.
The second point and the third point goes together, the first step it's a parse problem, thats wright, the error it's if you say "Yes" for create a New Parser, the app doesn't open the Parser's edition window, opens the third window and I can't create a new parser for this file can't be parsed. I think that could be a bug of this beta version, but I's possible that was a bug of the actual release version. I put you a message in a new post.

Thanks

admin
Site Admin
Posts: 437
Joined: Sun Dec 17, 2006 10:30 pm

Re: Problem using HTTP file manager

Post by admin » Wed Jan 17, 2018 10:55 am

OK thanks we will investigate that. In the meantime, you can always create Parsers at anytime by going to menu "Tools" > "Options" > tab "Parsers" > green "+" button at the right.

admin
Site Admin
Posts: 437
Joined: Sun Dec 17, 2006 10:30 pm

Re: Problem using HTTP file manager

Post by admin » Sat Mar 24, 2018 4:16 am

Hello,
flequi.dph wrote:
Wed Jan 17, 2018 9:04 am
the first step it's a parse problem, that's right, the error is if you say "Yes" to create a New Parser, the app doesn't open the Parser's edition window, opens the third window and I can't create a new parser for this file can't be parsed.
LogMX v6.2.0 has just been released and it includes a fix for this bug (when no suitable Parser is found for a file included in a merge, answering "Yes" to the question "Do you want to create a Parser now?" now opens the Parser creation dialog)

Xavier

Post Reply