Getting remove_internal_message.php to work

Squiz Matrix Support
1

Currently, I have 819254 unread messages according to the Internal Messages report. I really don't want all these messages, as I know it slows the _admin down. I have tried running the remove_internal_message.php script to remove these, but it did nothing. I used the following:

    php remove_internal_message.php -s /home/websites/mysource_matrix -p 2d


This didn't remove any of the messages according to the Internal messages report. Am I thinking that this script does something it does not?

Running 3.22.3
2

[quote]

    php remove_internal_message.php -s /home/websites/mysource_matrix -p 2d


This didn't remove any of the messages according to the Internal messages report. Am I thinking that this script does something it does not?

Running 3.22.3
[/quote]

When running on my 3.22.3 and dev systems (with --show-query-only) I am getting:

    Fatal error: Call to undefined method MatrixDAL::rowcount() in /home/mbrydon/matrix_installs/matrix_3-22/scripts/remove_internal_message.php on line 251

...and no SQL.

Please lodge a Bug Report and we'll look into this tomorrow. If it's an easy fix - from what I see here it's potentially just an invalid function call only - then I would expect it to be resolved for Monday's releases of 3.22.4 and 3.24.0.
3

[quote]
Currently, I have 819254 unread messages according to the Internal Messages report. I really don't want all these messages, as I know it slows the _admin down. I have tried running the remove_internal_message.php script to remove these, but it did nothing. I used the following:


    php remove_internal_message.php -s /home/websites/mysource_matrix -p 2d


This didn't remove any of the messages according to the Internal messages report. Am I thinking that this script does something it does not?

Running 3.22.3
[/quote]
Hey Nic, I suspect that you may be able to truncate the table (removing everything). Mark can probably confirm (or deny) it.

We don't even log stuff to the table - if we need we can get the info out of the system logs.

cheers
Richard
4

[quote]
I suspect that you may be able to truncate the table (removing everything). Mark can probably confirm (or deny) it.

[/quote]



How can I view this table to see if there is anything in it? I have some systems that are 3.18.8 which don't have the internal messages report.



Nic = Not good at psql. :slight_smile:

5

[quote]
How can I view this table to see if there is anything in it? I have some systems that are 3.18.8 which don’t have the internal messages report.



Nic = Not good at psql. :slight_smile:

[/quote]

In response to the issue I have lodged this as Bug 3889. We will get someone on this today.



An easy (non-command-line) way is to look at the “Internal Messages Report” from the System Maintenance screen (the screen icon in the toolbar).

Refreshing this report will get the latest data and show you a breakdown of message types and totals.



Please note that removing entries will cause messages shown on the “Logs” asset screen to disappear. If you are really really sure and completely happy with the content supplied in the system log, then truncating this table is fine.



This is done by running:

    psql matrix_db -U db_user

Then running the query:

[sql]TRUNCATE sq_internal_msg;[/sql]

The messages can be maintained on a schedule (when we've fixed the bug) by adding this script to your crontab. If you want to retain, say, a month's worth then using "-p 1m" should keep this tidy. Running this once a month and out-of-hours would be ideal.



Edit: Added truncation details

6

To check the rows for matrix internal messages you will need to use the command line utility I believe:

    
    psql -U postgres matrix_database_name


then..

    
    matrix_database_name=# SELECT COUNT(*) FROM sq_internal_msg;
     count
    -------
      7219
    (1 row)
7

Good news - we have a fix for the script. Please note that the script will only remove up to a certain time
period and will not remove all messages.



It was after all just an incorrect function call (Bug 3889).

The following line 251 in 3.22.3 should be changed as follows, from:


    $affected_rows = MatrixDAL::rowCount($query);

to:


    $affected_rows = $query->rowCount();

Thanks to Ben Pearson for this fix in our final steps towards release.



Please let us know whether this fixes the reported issue as it's working from our end.

8

Thanks guys, appreciate the help!