Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.

Close

#315 2.10.9 - Logging problem using sessions file with MySQL

closed-fixed
nobody
None
5
2006-08-21
2006-07-19
pir0k4
No

When I use mysql to save the sessions, every time I
enter the wrong password to the list administration,
it inserts multiple records to the dada_sessions
table. With every time I input a wrong password it
seems to increase the number of records that inserts
into the table. This cause the logging page to get
slower and slower every time.

BTW, not everything is bad, I love the script, besides
this problems it seems to work great, i will love to
buy the PRO version, but I will need these problems
fixed.

I'm using the v.2.10.9 in a RHEL 4.

Thanks.

Discussion

1 2 > >> (Page 1 of 2)
  • Justin J
    Justin J
    2006-07-21

    Logged In: YES
    user_id=90833

    Expired session *should* remove themselves after about 3
    days. You must have thousands of session entries for
    slowdown, I would presume (I may be presuming wrong)

    Does the number ever go down?

     
  • Justin J
    Justin J
    2006-07-21

    • summary: Logging problem using sessions file with MySQL --> 2.10.9 - Logging problem using sessions file with MySQL
     
  • Justin J
    Justin J
    2006-07-21

    Logged In: YES
    user_id=90833

    Changed Summary Subject thingy...

     
  • Justin J
    Justin J
    2006-07-21

    Logged In: YES
    user_id=90833

    Changed the, remove_old_session_files method in
    DADA::App::Session to use CGI::Session::ExpireSessions

     
  • pir0k4
    pir0k4
    2006-07-21

    Logged In: YES
    user_id=1558485

    Hi, the problem is not that is not deleting the sessions,
    the problem is that once I click submit on the login
    screens creates thousands of sessions for every time I type
    the wrong password. It happens exponentially, i.e. the
    first time I enter an incorrect password it adds 10 records
    to the session table, the second time adds 100 records, the
    third adds 1000 records. In five minutes the login screens
    gets really slow.
    I hope this helps.

     
  • Justin J
    Justin J
    2006-07-22

    Logged In: YES
    user_id=90833

    oh my - THOUSANDS?!

    OK, thanks for the clarification!

     
  • Justin J
    Justin J
    2006-07-22

    Logged In: YES
    user_id=90833

    Hmm, don't have an MySQL backed Dada handy, but this doesn't
    seem to be a problem with the Postgres flavor. Will
    investigate more...

     
  • pir0k4
    pir0k4
    2006-07-24

    Logged In: YES
    user_id=1558485

    Please let me know if you want me to send you more data to
    debug the problem.

     
  • Justin J
    Justin J
    2006-07-31

    Logged In: YES
    user_id=90833

    If you can, drop the session table you have currently and
    replace it with this:

    CREATE TABLE dada_sessions (
    id CHAR(32) NOT NULL PRIMARY KEY,
    a_session TEXT NOT NULL
    );

    I've done a lot of work in the code itself, but changing out
    the table to what's above will help you immensely. You may
    (still) get random sessions that are meaningless (these have
    been fixed in code), but your problem with getting thousands
    of copies should be fixed.

    Thanks for the report - if it checks out with you, I'm going
    to close this out soon.

     
  • Justin J
    Justin J
    2006-08-13

    Logged In: YES
    user_id=90833

    Closing bug soon unless the problem is persisting... :)

     
1 2 > >> (Page 1 of 2)