Hi all,
As the subject says, I'm trying to enable full text indexing. I've updated
MySQL to 5.7 (on Debian 8) and ran
/opt/rt4/sbin/rt-setup-fulltext-index --dba root --dba-password pwd
However, I get a bunch of warnings about executing the SQL statements and,
after that, that attachments can't
Hello again all,
I just discovered I have a more serious problem than full-text indexing not
working. I'm getting an error when anyone tries to make a ticket, and the
ticket is never created. Here's the message:
Nov 14 11:31:03 server24 RT: [2522] DBD::mysql::st execute failed:
Incorrect integer
Hi Alex,
I think the mysql configuration be "max_allowed_packet" rather than
"max_packet_size".
Best Regards
Martin
On 2016-11-14 13:54, Alex Hall wrote:
I should also say that I've already tried setting my MySQL
max_packet_size. 500M didn't do it, so I upped it to 5000M, restarting
the
Thanks for the correction. I hate to say it, but this didn't change the
results I'm seeing at all. I just updated /etc/mysql/conf.d/mysql.cnf,
restarted MySQL, and ran the full-text index command again. I got the exact
same errors as before.
On Mon, Nov 14, 2016 at 11:50 AM, Martin Wheldon <
I had success by using Debian’s snapshot server and downgrading MySQL 5.6.27-2
and then running rt-setup-fulltext-index. That worked perfectly.
You can safely “upgrade” back to your current version after the setup script
runs – the fulltext index maintenance script will run fine.
If
Hi Alex,
You could try disabling the PriorityAsString as a test, as least it will
narrow down your problem space.
Best Regards
Martin
On 2016-11-14 21:15, Alex Hall wrote:
Update: still not working. I tried setting sql-mode to an empty
string, like it would have been in 5.5, and to all the
For future readers, my own solution was--thankfully--much simpler. Nowhere
that I found in the docs I was reading did it say you had to add the
max_allowed_packet setting under a section called [mysqld] in my.cnf. As
soon as I did that, my setting took effect, and the full text setup ran
That’s good. I was concerned that you had the same issue with MySQL 5.7 and
the implications for RT on Stretch.
Max_allowed_packet does not work with 5.6.29 or 5.6.30 (at least not the Debian
packages at those versions).
James
From: Alex Hall [mailto:ah...@autodist.com]
Sent: Monday,
Hi Alex,
On Mon, Nov 14, 2016 at 10:37 AM, Alex Hall wrote:
> Hello again all,
> I just discovered I have a more serious problem than full-text indexing not
> working. I'm getting an error when anyone tries to make a ticket, and the
> ticket is never created. Here's the
Update: still not working. I tried setting sql-mode to an empty string,
like it would have been in 5.5, and to all the 5.7 standard ones except
strict_trans_tables. Neither helped. Updating existing tickets, and all
data retrieval, seem to work fine. It's just that priority getting a string
(that
Hi all,
Ticket creation is working, now that I've finally gotten it out of strict
mode. You'd think it would check its own cnf file for errors on startup,
but nope, it doesn't notice until you try to log in using the 'mysql -u'
command. Not even an error in the log file. Anyway...
Priority is
Is there any way to access the Assets in RT over the REST API? I can't
find anything in a Google search.
Thanks!
--
Best regards,
Steve
Stephen H. Switzer
President & Chief Technical Consultant
st...@sbsroc.com
MAIN:
CELL:
+1 (585) 298-9420 EXT: 7001
+1 (585) 202-8312
Support
Adam (and all),
I just committed the first public release of code that allows RT (or
RTIR) to be used with N-Central.
https://github.com/sbsroc/RTIR_WHD_API
I welcome any testers, and invite anyone that know the markup
language for the readme file to make it look better. It's quite
13 matches
Mail list logo