| *** a__pi has quit IRC | 03:51 | |
| *** a__pi has joined #ara | 03:58 | |
| tolland | when running `ara-manage runserver` with a mysql backend - mysql-community 5.7 I am seeing loads of errors like `InternalError: (pymysql.err.InternalError) Packet sequence number wrong - got 191 expected 1 ` and `MySQL server has gone away (error(32, 'Broken pipe')` | 04:39 |
|---|---|---|
| tolland | ara itself seems to be working... the database contains entres for playbooks etc, at the expected time, so the connection string is at least working in that respect | 04:40 |
| tolland | ah. so if I set processes = 1 it seems to not happen. | 04:54 |
| *** sshnaidm|off has quit IRC | 06:33 | |
| *** sshnaidm|off has joined #ara | 12:26 | |
| *** sshnaidm|off is now known as sshnaidm | 12:50 | |
| *** jparrill has joined #ara | 15:31 | |
| dmsimard | tolland: hmm, are we defaulting to one process ? Or more ? | 16:22 |
| dmsimard | logan-: I'm late -- looks like it's the unhashable type list thing | 16:23 |
| dmsimard | Perhaps the django_manage module returns non-standard things ? Dunno. I'll have to look | 16:25 |
| dmsimard | Also TIL about a django_manage module, thanks :p | 16:25 |
| logan- | :) yeah. it seems like 2 problems.. 1) the django_manage module returns some data ara cannot accept 2) ara handles the failure to log that task ungracefully and never issues a session rollback so the rest of the tasks in the playbook fail to log | 16:29 |
| dmsimard | I'll look at 1, likely not going to spend too much time on 2 because everything is so different with ara 1.0 | 16:31 |
| logan- | gotcha | 16:31 |
| logan- | thanks! | 16:31 |
| logan- | hows 1.0 coming along? | 16:32 |
| logan- | i could run a job with ara from git master and see how it handles the same returns if that feedback would help | 16:34 |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!