Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

'|' (pipe character) causes error during analyze #16

Open
Leftium opened this issue May 12, 2016 · 2 comments
Open

'|' (pipe character) causes error during analyze #16

Leftium opened this issue May 12, 2016 · 2 comments

Comments

@Leftium
Copy link

Leftium commented May 12, 2016

Steps to Reproduce:

  1. echo "t=|" > input.txt
  2. go run sequence.go analyze --input input.txt

Expected Results:

2016/05/12 13:13:56 Analyzed 1 messages, found 1 unique patterns, 1 are new.

(No error and message is analyzed.)

Actual Results:

2016/05/12 13:13:56 Error analyzing: t=|
2016/05/12 13:13:56 Analyzed 1 messages, found 0 unique patterns, 0 are new.

Comments:
I think something is going wrong with the heuristics for key=value pairs. I found this bug while processing an actual log file. One of the log events in question:

81.181.146.13 - - [15/Mar/2005:05:06:49 -0500] "GET //cgi-bin/awstats/awstats.pl?configdir=|%20id%20| HTTP/1.1" 404 1050 "-" "Mozilla/4.0 (compatible; MSIE 6.0; Windows 98)"
@antham antham mentioned this issue May 21, 2016
@jobordu
Copy link

jobordu commented Apr 18, 2017

Might be related, but I found an error and it might be caused be the '|' caracter:

2017/04/18 12:13:32 Error analyzing:
2017-04-11T16:49:28.551 Something is wrong with Attachment Browser Plugin, no working directory found: QDir( "C:/SpecifX_stateFiles/V2/femoralUnWrapNoManageLink3_pv_attachments" , nameFilters = { "*" }, QDir::SortFlags( Name | IgnoreCase ) , QDir::Filters( Dirs|Files|Drives|AllEntries ) ) (:0, )

@leolee192
Copy link

Since I tried and couldn't contact the original author for weeks, I decided to migrate the project to leolee192/sequencer. Please visit leolee192/sequencer#11 for further activity, or to subscribe to receive notifications.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants