Michelle Sullivan wrote:
Michelle Sullivan wrote:
Alex Vandiver wrote:
On 05/13/2014 05:39 AM, Michelle Sullivan via RT wrote:
[snip]
This message was rejected from rt-users because it was over 1M of
logfiles. Please don't send large
Alex Vandiver wrote:
On Thu, 2014-01-30 at 10:57 +0100, Michelle Sullivan wrote:
Jan 28 02:11:09 to Jan 28 02:18:31 ... a full 7 minutes of being in
ShowCustomFields there are just 100's (like more than 1900 of them) of
statements like this: [snip]
.. and no other queries... The start
Michelle Sullivan wrote:
Alex Vandiver wrote:
On 05/13/2014 05:39 AM, Michelle Sullivan via RT wrote:
[snip]
This message was rejected from rt-users because it was over 1M of
logfiles. Please don't send large messages to the list; you're welcome
to provide a link
Alex Vandiver wrote:
On 05/13/2014 05:39 AM, Michelle Sullivan via RT wrote:
[snip]
This message was rejected from rt-users because it was over 1M of
logfiles. Please don't send large messages to the list; you're welcome
to provide a link to complete logs for those interested
Alex Vandiver wrote:
On Thu, 2014-01-30 at 10:57 +0100, Michelle Sullivan wrote:
My frontends are on completely different networks (and indeed different
data centers) from the database servers for security (mainly DDoS type)
reasons
[snip discussion of optimization of column_info
Alex Vandiver wrote:
On Tue, 2014-01-28 at 03:30 +0100, Michelle Sullivan wrote:
Ok so temporarily I set min_duration to 0 and logged everything, the log
is here:
The situation can be made much clearer by limiting to the postgres
process IDs which are responding to queries from RT
}}} 3.5403
/Ticket/Display.html }}} 458.0237
/Ticket/autohandler }}} 458.0245
/Elements/Footer {{{
/l_unsafe {{{
/l_unsafe }}} 0.0009
/Elements/Footer }}} 0.0026
/autohandler }}} 459.6573
/Ticket/Display.html }}} ENDS
--
Michelle
Alex Vandiver wrote:
On Mon, 2014-01-27 at 10:06 +0100, Michelle Sullivan wrote:
After upgrade to v4.0.17 from 3.x loading tickets is extremely slow..
can anyone give me any clues please...?
What version were you upgrading from? What database backend are you
using?
3.6.3
Michelle Sullivan wrote:
Alex Vandiver wrote:
The fact that even cookie setup takes a quarter of a second is
problematic, and suggests that your database badly needs tuning.
I doubt it, it's probably because it's busy.
Oh I should also point out in lulls between
Michelle Sullivan wrote:
Michelle Sullivan wrote:
Alex Vandiver wrote:
The fact that even cookie setup takes a quarter of a second is
problematic, and suggests that your database badly needs tuning.
I doubt it, it's probably because it's
|public.objectcustomfieldvalues_id_s|public.objectcustomfields_id_s|_seq)'
) you can see the times involved.
Any clues would be very much appreciated.
Michelle
--
Michelle Sullivan
http://www.mhix.org/
that it is not possible without
extensive work... can anyone confirm or deny?
Thanks,
--
Michelle Sullivan
http://www.mhix.org/
Alberto Villanueva wrote:
Got it working a treat, but I need to be able to disable accounts and
re-enable them, is this possible with RT::Client::REST?
If we look at next page [1], it is not possible. I tried to several
actions in a custom program for working with users, and I was not able
Is there and API available in 3.6 or 3.8 so that I can create a ticket
and get the ticket number (and create a user if necessary).
Currently I have a web interface that collects data, sets up an email
with the required support information and sends it to a Queue Input address.
I'd like to get
14 matches
Mail list logo
