#113 can't delete or move sensors

closed-rejected
Nerveup
Interface (166)
5
2006-02-09
2005-10-04
Anonymous
No

Hello...
I can't delete a complete sensor or move it into the
archiv-db :-(

Error (german lang):
Es wurden keine Warnungen gewählt oder Warnung(en)
löschen war nicht erfolgreich

It's no problem to show all alerts of this sensor and then
delete...
With acid it's no problem to delete a sensor, or move it
into another db.

Discussion

1 2 > >> (Page 1 of 2)
  • Logged In: NO

    hey man. couldn't you give error in english language? i
    assume there is no german developers.

     
  • Logged In: NO

    No alerts were selected or the 'Delete alert(s) was not
    successful

     
  • Christian
    Christian
    2005-11-16

    • labels: 708744 --> Interface
    • assigned_to: nobody --> secureideas
     
  • Christian
    Christian
    2005-11-16

    Logged In: YES
    user_id=1155549

    I can confirm this on the latest CVS version.

    Reproduce:
    1. Click Sensors/Total: <nr>/
    2. Mark one sensor
    3. Action "Archive alert(s)(move)" (same issue with copy)
    4. Click Selected

    No alerts were selected or the Archive alert(s) (move) was
    not successful

    Another way of ending up with the same issue

    1. Click Most recent 30 Alerts: any protocol
    2. Click a source ip
    3. Click "Num of Sensors"
    4. Action "Delete alert(s)" (if you try to copy/move you
    get the same end result)
    5. Click All on screen

    No alerts were selected or the Delete alert(s) was not
    successful.

    /Christian

     
  • Nerveup
    Nerveup
    2006-01-22

    Logged In: YES
    user_id=1429350

    Christian, thanks for testing!
    The feature was lost in BASE-1.1 (elizabeth) (taking input
    tags out of form tag) and double lost in BASE 1.2.1 (kris)
    (after implementing sql injection fix).
    So there are two commits in base_stat_sensor.php releated to
    this bug.

    Thanks

     
  • Nerveup
    Nerveup
    2006-01-22

    • assigned_to: secureideas --> nerveup
    • status: open --> open-fixed
     
  • Nerveup
    Nerveup
    2006-01-22

    • status: open-fixed --> closed-fixed
     
  • Christian
    Christian
    2006-01-23

    • status: closed-fixed --> open-rejected
     
  • Christian
    Christian
    2006-01-23

    Logged In: YES
    user_id=1155549

    Looks like the problem is not 100% fixed.

    Reproduce:
    1. Click Sensors/Total: <nr>/
    2. Mark one sensor
    3. Action "Archive alert(s)(move)" (same issue with
    copy)
    4. Click Selected

    I hade at this time 183 alerts that i wanted to move, witch
    it also did. The odd thing is that it toke about 10min to
    move them and the report where as follow.

    Ignored 3760 duplicate alert(s)
    Successful Archive alert(s) (move) - on 11339 alert(s) (in
    3 blobs)

    So what more alerts did it move and why ?

    Happy hunting
    Christian

     
  • Nerveup
    Nerveup
    2006-01-23

    Logged In: YES
    user_id=1429350

    Hello Christian!
    Thanks for testing!
    I can't reproduce this. I tried with 24alerts on sensor.
    They copied well.
    Could you, please, try to reproduce this again befire
    rebuilding alert cache?

    p.s. excally I fixed form issue when it did nothing when
    submiting (1.2.2) and "No alerts were selected or the
    `action` was not successful" (< 1.2.2). Maybe there is bug
    in copying/moving to archivedb that needs be fixed.

    Thanks

     
1 2 > >> (Page 1 of 2)