tickets #64953
closeddatabase error on connect platform.
100%
Description
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I'm on https://connect.opensuse.org//pg/members/all/. I click login, and
I get this error:
+++------------------------
Welcome to Elgg.
Field 'id' doesn't have a default value
QUERY: INSERT into elgg_system_log (object_id, object_class, object_type,
object_subtype, event, performed_by_guid, owner_guid, access_id, enabled,
time_created) VALUES ('8035','ElggUser','user', '', 'update',8035, 0, 2,
'yes', '1585434719')
- ------------------------++-
Blue background. Can send a photo if you wish.
I hit "reload" and get to the correct page. I think you were adding index
fields to the databases, may be related.
Cheers / Saludos,
Carlos E. R.
(from 15.1 x86_64 at Legolas)
-----BEGIN PGP SIGNATURE-----
iHYEARECADYWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCXn/R1BgcY2FybG9zLmUu
ckBvcGVuc3VzZS5vcmcACgkQtTMYHG2NR9W7pgCfXT4c4qkxZPiV7EsYdXV/8rh3
U3YAn3a0tPAYyBAv6JO1vqXjAKOqFBaZ
=c5kl
-----END PGP SIGNATURE-----
Updated by lrupp about 4 years ago
- Category set to Servers hosted in NBG
- Private changed from Yes to No
Thanks for the information: https://status.opensuse.org is updated.
This problem needs someone with "egg knowledge"...
Updated by lrupp about 4 years ago
- Status changed from New to Closed
- Assignee set to lrupp
- % Done changed from 0 to 100
Closing: application is back.
Some parts are still kind of broken - but the analysis of the logs showed that this is the case since years.
Updated by jensm about 4 years ago
lrupp wrote:
Closing: application is back.
Some parts are still kind of broken - but the analysis of the logs showed that this is the case since years.
"Elgg couldn't connect to the database using the given credentials. " with a blue background
Updated by robin_listas about 4 years ago
The connect platform at https://connect.opensuse.org/ is effectively down, contrary to what https://status.opensuse.org/ shows. It just displays an elgg error:
+++--------------
Welcome to Elgg.
Elgg couldn't connect to the database using the given credentials.
--------------++-
Please reopen.
Updated by cboltz about 4 years ago
- Status changed from Closed to New
A manual attempt to access the database says ERROR 1226 (42000): User 'boosters_elgg' has exceeded the 'max_connections_per_hour' resource (current value: 50)
- interesting[tm]... (Lars, any idea?)
I marked connect as down on status.o.o.
As a sidenote - the error message gets delivered with a 200 OK
http status code so that the monitoring doesn't notice the error...
Updated by lrupp about 4 years ago
- Status changed from New to Closed
cboltz wrote:
A manual attempt to access the database says
ERROR 1226 (42000): User 'boosters_elgg' has exceeded the 'max_connections_per_hour' resource (current value: 50)
- interesting[tm]... (Lars, any idea?)
Yes, sorry: this was a temporary workaround a couple of days ago to not allow connect.o.o to DoS the database cluster itself. I removed the limit now again. Sorry for forgetting this...
I marked connect as down on status.o.o.
...and I marked it as ok now, as the limitation is gone.
As a sidenote - the error message gets delivered with a
200 OK
http status code so that the monitoring doesn't notice the error...
I don't want to comment on that, old, crappy, application and OS state...
Regards,
Lars