Bug #1427
Cannot connect after 0.10 -> 0.12.4 upgrade
0%
Description
I upgraded my core and OSX client to the latest version.
Connecting to the core (SQLite backend) is very slow and spews a lot of errors like this when run with --debug. Not sure what I should do about this, or is it harmful or harmless or is there something else preventing successful connections.
017-01-26 21:38:24 Error: last Query:
SELECT messageid, time, type, flags, sender, message
FROM backlog
JOIN sender ON backlog.senderid = sender.senderid
WHERE bufferid = :bufferid
ORDER BY messageid DESC
LIMIT :limit
2017-01-26 21:38:24 Error: executed Query:
SELECT messageid, time, type, flags, sender, message
FROM backlog
JOIN sender ON backlog.senderid = sender.senderid
WHERE bufferid = ?
ORDER BY messageid DESC
LIMIT ?
2017-01-26 21:38:24 Error: bound Values: :bufferid=6, :limit=50
2017-01-26 21:38:24 Error: Error Number: -1
2017-01-26 21:38:24 Error: Error Message:
2017-01-26 21:38:24 Error: Driver Message:
2017-01-26 21:38:24 Error: DB Message:
2017-01-26 21:38:24 Error: last Query:
SELECT bufferid, networkid, buffertype, groupid, buffername
FROM buffer
WHERE bufferid = :bufferid AND userid = :userid
2017-01-26 21:38:24 Error: executed Query:
SELECT bufferid, networkid, buffertype, groupid, buffername
FROM buffer
WHERE bufferid = ? AND userid = ?
2017-01-26 21:38:24 Error: bound Values: :bufferid=1086, :userid=1
2017-01-26 21:38:24 Error: Error Number: -1
2017-01-26 21:38:24 Error: Error Message:
2017-01-26 21:38:24 Error: Driver Message:
2017-01-26 21:38:24 Error: DB Message:
2017-01-26 21:38:24 Error: last Query:
SELECT messageid, time, type, flags, sender, message
FROM backlog
JOIN sender ON backlog.senderid = sender.senderid
WHERE bufferid = :bufferid
ORDER BY messageid DESC
LIMIT :limit
2017-01-26 21:38:24 Error: executed Query:
SELECT messageid, time, type, flags, sender, message
FROM backlog
JOIN sender ON backlog.senderid = sender.senderid
WHERE bufferid = ?
ORDER BY messageid DESC
LIMIT ?
2017-01-26 21:38:24 Error: bound Values: :bufferid=1086, :limit=50
2017-01-26 21:38:24 Error: Error Number: -1
2017-01-26 21:38:24 Error: Error Message:
2017-01-26 21:38:24 Error: Driver Message:
2017-01-26 21:38:24 Error: DB Message:
2017-01-26 21:38:24 Error: last Query:
SELECT bufferid, networkid, buffertype, groupid, buffername
FROM buffer
WHERE bufferid = :bufferid AND userid = :userid
2017-01-26 21:38:24 Error: executed Query:
SELECT bufferid, networkid, buffertype, groupid, buffername
FROM buffer
WHERE bufferid = ? AND userid = ?
2017-01-26 21:38:24 Error: bound Values: :bufferid=5, :userid=1
2017-01-26 21:38:24 Error: Error Number: -1
2017-01-26 21:38:24 Error: Error Message:
2017-01-26 21:38:24 Error: Driver Message:
2017-01-26 21:38:24 Error: DB Message:
History
#1 Updated by miohtama almost 8 years ago
Further information.
If I set Backlog fetching to 0 it manages to connect. If I set Initial backlog amount to 5 it fails in Receiving session state or Receiving backlog.
#2 Updated by genius3000 over 7 years ago
As far as the "Errors" in that log snippet go, they aren't actual errors. The '--debug' or '-d' command line argument enables full on developer debug output. The argument you may want to try is '--loglevel Debug' or '-L Debug'.
Though in this case you might actually want/need the former to debug this issue. The supplied logs appear to be normal, as in no actual errors are apparent. How long does it take for the connection to succeed at 0 backlog and to fail at 5 backlog? When it fails, and running the core in debug mode, are all the SQL queries done in a second or two time frame or is it taking a long time/hanging in that area?