Project

General

Profile

Bug #122

prewikka internal error (connection error)

Added by over 13 years ago. Updated about 10 years ago.

Status:
Closed
Priority:
Normal
Target version:
Start date:
Due date:
% Done:

0%

Resolution:
invalid

Description

Hi there,

I am using prewikka 0.9.2 with Cheetah-2.0b1, prelude-manager-0.9.1, libpreludedb-0.9.2, libprelude-0.9.1 and mysql 5.0.17 under [[SuSE]] Linux 10.

I got the following error message this morning when I tried to login to prewikka. Also, the failed query _login=<user>&_password=<mypassword> showed up in plaintext (?!?).

Browser-Refresh of the login window did'nt solve the problem.
After clicking "Retry"-button, login was executed and the management overview appeared.
I got this strange behaviour twice now.
Any ideas?
Thanks for helping!


Traceback (most recent call last):
File "/usr/lib/python2.4/site-packages/prewikka/Core.py", line 268, in process
user = self.checkAuth(request)
File "/usr/lib/python2.4/site-packages/prewikka/Core.py", line 255, in checkAuth
return self._env.auth.getUser(request)
File "/usr/lib/python2.4/site-packages/prewikka/Auth.py", line 139, in getUser
self.checkPassword(login, password)
File "/usr/lib/python2.4/site-packages/prewikka/modules/auth/loginpassword/loginpassword.py", line 39, in checkPassword
real_password = self.db.getPassword(login)
File "/usr/lib/python2.4/site-packages/prewikka/Database.py", line 191, in getPassword
rows = self.query("SELECT login, password FROM Prewikka_User WHERE login = %s" % (self.escape(login)))
File "/usr/lib/python2.4/site-packages/prewikka/Database.py", line 122, in query
raise [[PreludeDBError]](e.errno, preludedb_sql_get_plugin_error(self._sql))
[[PreludeDBError]]: Connection error

History

#1 Updated by Yoann VANDOORSELAERE over 13 years ago

The error seem to indicate that your [[MySQL]] server has gone away.
You could also see the _login and _password variable in the exception since it happened on login.

#2 Updated by over 13 years ago

I checked the [[MySQL]] process as well as login to [[MySQL]] via mysql-u <user> -p right after the error occured. Everything was fine, [[MySQL]] is up and running.

After clicking on "Retry", then logging out and logging in again, everything seems normal.
I had the error after a "session expired" message (I left the management window in browser open overnight).

Is there a separate logfile of prewikka/ libpreludedb that may have logged these events so that I can post it here?

Thanks and Regards.

#3 Updated by Yoann VANDOORSELAERE over 13 years ago

The connection might has been broken for any reason, including network or local problem. Or you might have hit an instance of the following [[MySQL]] bug:
http://bugs.mysql.com/bug.php?id=14747

When clicking "Retry" after getting the Connection error problem, Prewikka attempted to reconnect the [[MySQL]] server and sorted out the issue since the reconnection was successful.

If you got the "log" configuration option in your configuration file, then the query might be found in this place. But I doubt it will permit to learn anything about this specific issue.

#4 Updated by over 13 years ago

Ok, although the patch to fix that bug should have been applied to the version I am currently using (5.0.17), there's a new one available for download. I'll check this out. If the problem occurs again, I'll post it on this thread.

Thanks and regards.

#5 Updated by Yoann VANDOORSELAERE over 13 years ago

  • Status changed from New to Closed
  • Resolution set to invalid

Marking as invalid. Connection Error problem are out of the scope of Prewikka.
Please re-open if needed.

#6 Updated by over 13 years ago

  • Status changed from Closed to Feedback
  • Resolution deleted (invalid)

Hi there,

same problem with [[MySQL]]-5.0.18. [[MySQL]] is up and running.

There's a new error message (because the first "Retry"-Action failed).


_login=<user>&_password=<password>&_error_back=%7B%27analyzerid
%27%3A+%5B%272462743973851376%27%5D%2C+%27view%27%3A+%5B%27
heartbeat_analyze%27%5D%7D

Traceback (most recent call last):
File "/usr/lib/python2.4/site-packages/prewikka/Core.py", line 277, in process
getattr(view[[object"] view["handler]])()
File "/usr/lib/python2.4/site-packages/prewikka/views/messagelisting.py", line 1125, in render
total = self._setMessages(criteria)
File "/usr/lib/python2.4/site-packages/prewikka/views/messagelisting.py", line 1072, in _setMessages
return self._setAggregatedMessagesNoValues(criteria, aggregated_on)
File "/usr/lib/python2.4/site-packages/prewikka/views/messagelisting.py", line 864, in _setAggregatedMessagesNoValues
for values in results[self.parameters[[offset"]selfparameters["offset"]+selfparameters["limit]]:
[[PreludeDBError]]: Connection error

#7 Updated by Yoann VANDOORSELAERE over 13 years ago

  • Status changed from Feedback to Closed
  • Resolution set to invalid

As stated previously, I don't think this is a Prelude issue. The connection might has been broken for any reason, including network problem, or a [[MySQL]] crash/restart. I'd suggest running [[MySQL]] under GDB to see if there is any problem with it.

#8 Updated by Yoann VANDOORSELAERE about 10 years ago

  • Project changed from PRELUDE SIEM to Prewikka
  • Category deleted (5)
  • Target version deleted (0.9.3)

Also available in: Atom PDF