lw-eventlog-cli sql filters fail with error code 36882
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
likewise-open (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: likewise-open
Attempting to troubleshoot likewise-open bug 572271, I discovered a problem with using sql_filter arguments with lw-eventlog-cli.
$ sudo lw-eventlog-cli -c "(EventRecordId < 1000) AND (EventType = 'Warning')" 127.0.0.1
Error: An invalid event record range [(EventRecordId < 1000) AND (EventType = 'Warning')] was specified.
20100511092630:
The example above was take from lw-eventlog-cli -h output.
Using the same command with the "all records" - character does not error.
$ sudo lw-eventlog-cli -c - 127.0.0.1
107 records found in database
I checked to make sure it was not a problem with there being no 'Warning' events in my likewise-open log.
$ sudo lw-eventlog-cli -t - 127.0.0.1
Id: | Type | Date | Time | Source | Category | Event | User
1 | Information | 2010-04-30 | 03:41:19 PM | Likewise LSASS | Service | 1004 | SYSTEM
2 | Information | 2010-04-30 | 03:41:19 PM | Likewise LSASS | Service | 1000 | SYSTEM
3 | Information | 2010-04-30 | 03:50:04 PM | Likewise LSASS | Service | 1004 | SYSTEM
4 | Information | 2010-04-30 | 03:50:04 PM | Likewise LSASS | Service | 1000 | SYSTEM
5 | Information | 2010-04-30 | 04:32:07 PM | Likewise LSASS | Service | 1004 | SYSTEM
...
104 | Information | 2010-05-10 | 09:03:13 AM | Likewise LSASS | Service | 1000 | SYSTEM
105 | Information | 2010-05-10 | 09:05:09 AM | Likewise LSASS | Service | 1002 | SYSTEM
106 | Information | 2010-05-10 | 09:05:09 AM | Likewise LSASS | Service | 1004 | SYSTEM
107 | Information | 2010-05-10 | 09:05:09 AM | Likewise LSASS | Service | 1000 | SYSTEM
$ sudo lw-eventlog-cli -c "(EventRecordId < 1000) AND (EventType = 'Information')" 127.0.0.1
Error: An invalid event record range [(EventRecordId < 1000) AND (EventType = 'Information')] was specified.
20100511093550:
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on the most recent Ubuntu LTS version, 12.04. When you test it and it is still an issue, kindly upload the updated logs by running apport-collect <bug #> and any other logs that are relevant for this particular issue.