Currently I am using mirth connect 3.0 in 3.0. It is not possible to prune the error messages.
I have a plan for upgrading to 3.5.
My question is, in mirth connect 3.5 is it possible to prune error messages?
Errored messages are still not included in pruning, but that's something we're planning on adding in the near future.
Related
I am trying to upgrade Aurora RDS Postgres cluster db.r5.xlarge from version 12.7 to 13.3.
I choose Engine version 13.3, default DB cluster parameter group and DB parameter group default.aurora-postgresql13 and choose 'Apply immediately'.
Received error message:
We're sorry, your request to modify DB cluster clone-cluster has failed.
Cannot modify engine version because instance clone-cluster is running on an old configuration.
Apply any pending maintenance actions on the instance before proceeding with the upgrade
There are no any pending maintenance actions showing in AWS RDS console and I have no idea what configuration they mean.
We are on a free basic support plan no so we cannot get help from AWS. Can anyone please suggest if there's a way to upgrade the whole cluster at once?
I had this issue and contacted AWS support. They said it is a known issue for (some, or all) db.t3 instance types. In my case I was using db.t3.medium.
So the workaround is as follows:
Change instance type on the cluster to r5.xlarge or db.r6g.large.
Upgrade to PostgreSQL 13.3
Change instance type back to db.t3.medium.
Just to add to the other great answers, another possible reason for "old configuration" errors is attempting to upgrade from an old minor version.
I was trying to upgrade from Postgres 12.6 directly to 13.3, which is not supported.
Instead, I had to upgrade to 12.7 first and then upgrade to 13.3.
It's written in the docs, but I didn't notice the minor version requirement.
Hit the same issue with upgrade to a major version and here's the undocumented solution I found:
Select an instance from the cluster, and in the actions menu you should see Upgrade Now.
Do this for each instance that is part of the cluster.
Modify the cluster and you should be able to upgrade to any available 13.x version.
Even though it is shown as the same version as the Cluster, the Upgrade now action will run configuration update on the instance itself putting it in maintenance and rebooting it.
This is not correctly documented at the moment, but it is possible to check and resolve (for those of us automating the upgrade process.) The CLI aws rds describe-pending-maintenance-actions sometimes reports the status. If you know ARNs, you can filter on them, or if just a name, this seems to work:
aws rds describe-pending-maintenance-actions --query 'PendingMaintenanceActions[?contains(ResourceIdentifier, `test`)`
The maintenance can be applied programmatically using apply-pending-maintenance-action.
However...
This message also appears to occur when something about the upgrade path is invalid. In my case, I believe the case is as follows:
Source is 9.6.19 Aurora PostgreSQL
Target is 10.18. This fails.
Set target to 10.14 and upgrade occurs
In short, the UI, and other information about what versions of what are compatible is incomplete. I have reported this to AWS and they mostly shrugged, telling me to look at the doc. Pffft.
This one worked for me. In rds, select the server highlighted in the error message, go to "Configuration" and make sure that the "Recommendations" area is empty, otherwise, "Apply Now" the recommendation/s. Once all completed, "Modify" from the Global/Regional Cluster and try to upgrade again.
This question may sound absurd as I am totally new to XMPP & Openfire. I have a setup of Openfire 4.2.3 in Ubuntu 18.0.4 LTS that being used in my android chat app. During testing I received a Timeout error. While investigating the issue I found the solution rely on the XMPP updated version, check this link for more info.
Well I tried my best to find out my XMPP version and how to update it. Unfortunately I didn't find anything on it. So, I have two obvious questions here:
How to check XMPP version my Openfire is running on?
How to update XMPP version on my existing Openfire setup?
Since you are able to use the web-interface, just log in. On the start page look for the server properties. Theres the version.
For upgrading follow these steps:
To stop openfire on ubuntu: /etc/init.d/openfire stop;
Backup copy of the openfire installation directory: /usr/share/openfire;
Backup Openfire Base in Postgres: If you use the pgAdmin application, right-click on openfire base and click “Backup”. To run backup, it can be with own postgres as user. I recommend tar format, and encoding “SQL_ASCII”.
To install the new version: you can actually use the “dpkg -i” command, you will be asked if you want to keep your current version (choose this one), but you will still upgrade (option N or O - keep your currently -installed version).
On the java, has a statement informing that from version 4.3 will be necessary Java 8 installed.
Source: https://discourse.igniterealtime.org/t/update-openfire-4-1-6-to-4-2-1-in-ubuntu-server/80336
And if you really meant the "XMPP-Version". There is not really such a thing. XMPP is implemented to a different extend on different server-providers. Some have more extensions, some less.
To see which ones you have, refer to the wikipedia site:
https://en.wikipedia.org/wiki/Comparison_of_XMPP_server_software
I am looking for a Version Control tool for SQLite database. So on exploring I came to know about Fossil which is recommended by SQLite also.
I am using latest version 2.7 for Windows and the problem I am facing is on using it in server mode and committing few files, it gets crashed frequently giving 'database is locked' error.
At first instance I thought that I am using the server and cloned copy on same system so it might be crashing due to this reason. But when I have started server on another system and even committing to it from a different system the result is same, It got crashed again.
Here's the screenshot of the crashed fossil server
Can anyone point me to the right direction that what I am doing wrong here?
Indeed, version 2.7 still had some wrinkles with a newly added backoffice functionality.
In general, the backoffice processing can be turned off via setting 'fossil set backoffice-disable true', see help on backoffice-disable
This would most likely resolve the issue you experienced.
Meanwhile, the recently released version 2.8 has those wrinkles resolved.
I am running offline compaction to reduce aem repository size. but it is throwing error [05:28:37.939 [main] ERROR o.a.j.o.p.segment.SegmentTracker - Segment not found:
3ff5d2ae-2b7f-412b-bfff-1dcdf0613315. Creation date delta is 15 ms.
org.apache.jackrabbit.oak.plugins.segment.SegmentNotFoundException: Segment 3ff5
d2ae-2b7f-412b-bfff-1dcdf0613315 not found].
Compaction was working fine earlier, when we were using AEM 6.1 only with communities FP4 and have oak version 1.2.7.
Problem occurred after installation of communities FP5, FP6, service pack 2 and CFP3 in AEM 6.1, now oak version upgraded to 1.2.18 and we are using oak jar version 1.2.18 to perform the compaction.
When I Google this error then found that our segments have been corrupted and we have to restore our segment with last good condition.
Then we have found a command this [java -jar D:\aem\oakfile\oak-run-1.2.18.jar check -d1 --bin=-1 -p D:\aem\crx-quickstart\repository\segmentstore] to find the last good condition segment where we can restore. But when we are running this command to find the previous good segment then this command is keep running to infinite without end.
Can anyone let me know how I can fix this?
There are many posts here and all over the web about getting the message:
Connection using old (pre-4.1.1) authentication protocol refused (client option 'secure_auth' enabled)
when trying to connect a a MySQL database. In my case, it's coming from MySQLWorkbench version 6.3 newly installed on a almost as newly install Ubuntu 15.10 system.
The advice is always to update the password on the database to use the new authentication.
However, that is not my problem, and that's not what the message says. It says that the OLD authentication is being used when the database wants the NEW authentication.
This version of MySQLWorkbench has a checkbox that tells it to use the OLD authentication, which is unchecked, but, from the message, it appears to be using the OLD authentication all the time.
I can connect to the database easily from version 5.2 of MySQLWorkbench running on Mac OS X.
I tried installing an older version of MySQLWorkbench on my Ubuntu system, but there were numerous errors with the package, which is intended for an earlier version of Ubuntu.
Any ideas about how I can force MySQLWorkbench to use the NEW authentication? I tried setting:
useLegacyAuth=0
but that did nothing.
OK, got the answer. The hosting outfit (Siteground) sets up MySQL passwords to work with EITHER the legacy or the new protocol. I don't know if this is homegrown, some sort of plugin that's generally available, or a standard MySQL feature. With this option, MySQLWorkbench fails to connect and erroneously reports the problem as the server not supporting the old protocol. Probably it's just confused by the error response which its programmers didn't anticipate.
Siteground very quickly set my password to use the new authentication ONLY upon my request, and then MySQLWorkbench connected with no problem.