Closed GoogleCodeExporter closed 9 years ago
This sound as a error in event parser of waf-fle OR an bad formed event.
To accelerate the fix and once that you use tshark, could you please send a
full dump of a event (with request too)? This will make clear the reason for
the problem.
Best regard,
Klaubert
Original comment by klaub...@gmail.com
on 17 May 2013 at 5:58
Hi
I have the mlogc file from the server which I have attached, perhaps that might
be enough?
The tshark file will contain the sensor password, so I'd rather send that
directly to you!
Dave
Original comment by dave.hil...@displaylink.com
on 20 May 2013 at 11:05
Attachments:
Here is the tshark trace, I did "follow tcp stream" then edited out the
password and server names.
Dave
Original comment by dave.hil...@displaylink.com
on 21 May 2013 at 10:43
Attachments:
Hi
Anything happening about this - other people are seeing similar things.
Dave
Original comment by dave.hil...@displaylink.com
on 29 Oct 2013 at 10:49
Yes, in few days you will have a patch.
sorry for delay.
Klaubert
Original comment by klaub...@gmail.com
on 29 Oct 2013 at 10:56
Thanks.
Dave
Original comment by dave.hil...@displaylink.com
on 29 Oct 2013 at 3:31
Users,
While an update version is not available, you can make a little change in
database schema as noted below:
use mysql command line, logging as database administrator (my admin user is
root, yours can be different)
# mysql -u root -p
mysql> use waffle;
mysql> ALTER TABLE `events`
CHANGE `f_protocol` `f_protocol` CHAR( 8 ) NULL ,
CHANGE `f_status` `f_status` SMALLINT( 3 ) UNSIGNED NULL ,
CHANGE `f_msg` `f_msg` VARCHAR( 300 ) NULL ,
CHANGE `f_content_length` `f_content_length` INT( 10 ) UNSIGNED NULL ,
CHANGE `f_connection` `f_connection` VARCHAR( 16 ) NULL ,
CHANGE `f_content_type` `f_content_type` VARCHAR( 30 ) NULL;
mysql> quit
This should solve the problem, by now, of an incomplete request that don't
produce a response header.
Klaubert
Original comment by klaub...@gmail.com
on 31 Oct 2013 at 2:49
Thanks, I have done this and will see what happens!
Dave
Original comment by dave.hil...@displaylink.com
on 31 Oct 2013 at 9:25
The code in development was changed to address this issue, so the schema will
not change anymore to solve this.
Best regards,
Klaubert
Original comment by klaub...@gmail.com
on 21 Jan 2014 at 9:59
Original issue reported on code.google.com by
dave.hil...@displaylink.com
on 13 May 2013 at 1:14