$ plague-client list Error: an error ocurred communicating with the server. '<Fault 1: 'pg.DatabaseError:error 'ERROR: expression too complex\nDETAIL: Nesting depth exceeds maximum expression depth 10000.\nHINT: Increase the configuration parameter "max_expr_depth".\n' in 'SELECT jobid, parent_uid, starttime, endtime, arch, builder_addr, status, builder_status FROM archjobs WHERE parent_uid=5 ---snip--- (400K of parent_uid=...)
$ plague-client list status needsign (same here)
$ plague-client list result success (same here)
$ plague-client list status failed Error: connection to the server timed out. '(110, 'Operation timed out.')'
$ plague-client list status building (same here)
$ plague-client list email myemailaddress (works)
On Sat, 2006-11-25 at 18:28 +0100, Michael Schwendt wrote:
$ plague-client list Error: an error ocurred communicating with the server. '<Fault 1: 'pg.DatabaseError:error 'ERROR: expression too complex\nDETAIL: Nesting depth exceeds maximum expression depth 10000.\nHINT: Increase the configuration parameter "max_expr_depth".\n' in 'SELECT jobid, parent_uid, starttime, endtime, arch, builder_addr, status, builder_status FROM archjobs WHERE parent_uid=5 ---snip--- (400K of parent_uid=...)
Don't list all jobs :) In any case, the server needs to limit the CLI clients request size.
dan
$ plague-client list status needsign (same here)
$ plague-client list result success (same here)
$ plague-client list status failed Error: connection to the server timed out. '(110, 'Operation timed out.')'
$ plague-client list status building (same here)
$ plague-client list email myemailaddress (works)
-- Fedora-buildsys-list mailing list Fedora-buildsys-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-buildsys-list
On 11/26/06, Dan Williams dcbw@redhat.com wrote:
On Sat, 2006-11-25 at 18:28 +0100, Michael Schwendt wrote:
$ plague-client list Error: an error ocurred communicating with the server. '<Fault 1: 'pg.DatabaseError:error 'ERROR: expression too complex\nDETAIL: Nesting depth exceeds maximum expression depth 10000.\nHINT: Increase the configuration parameter "max_expr_depth".\n' in 'SELECT jobid, parent_uid, starttime, endtime, arch, builder_addr, status, builder_status FROM archjobs WHERE parent_uid=5 ---snip--- (400K of parent_uid=...)
Don't list all jobs :) In any case, the server needs to limit the CLI clients request size.
this is the same I hit the very first time I tried plague... Now a probably naive question: is there a reason why "plague-client list" builds a full list of parent_uid's in the WHERE clause instead of just stopping the query at "archjobs"?
try plague-client list status needsign uid_gt 22000 the problem is the command is returning too much data.
On Saturday 25 November 2006 11:28 am, Michael Schwendt wrote:
$ plague-client list Error: an error ocurred communicating with the server. '<Fault 1: 'pg.DatabaseError:error 'ERROR: expression too complex\nDETAIL: Nesting depth exceeds maximum expression depth 10000.\nHINT: Increase the configuration parameter "max_expr_depth".\n' in 'SELECT jobid, parent_uid, starttime, endtime, arch, builder_addr, status, builder_status FROM archjobs WHERE parent_uid=5 ---snip--- (400K of parent_uid=...)
$ plague-client list status needsign (same here)
$ plague-client list result success (same here)
$ plague-client list status failed Error: connection to the server timed out. '(110, 'Operation timed out.')'
$ plague-client list status building (same here)
$ plague-client list email myemailaddress (works)
-- Fedora-buildsys-list mailing list Fedora-buildsys-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-buildsys-list
buildsys@lists.fedoraproject.org