Upgrade Opendj from 2.6.4 to 3.5.3 for replication server - ldap

I'm trying to perform an upgrade on an environments 2 OpenDJ directory servers with 1 standalone replication server between them referring to the 3.5 Upgrade doc. However, I could not find information on the order of upgrade for replication topology with standalone replication server. Should we go with upgrade of Directory servers first followed by replication, or vice versa. Can upgrade script identify between replication and directory servers.

It doesn't matter, replication is compatible between versions.

Related

Data Replication failed between OpenDJ 2.6.4 and 4.4.11

We plan to upgrade our OpenDJ server(currently on 2.6.4) to 4.4.11. We decided to do the data migration by enabling replication between old and new servers. We were able to enable the replication between servers and the replication process got susccessfully completed. But the we checked the replication status, it is showing as 0 entries in the new OpenDJ server.
We found below error in the error log file,
Also when we check the data from Apache Directory studio we can see the data. But some records does not have values.
We followed this https://backstage.forgerock.com/knowledge/kb/article/a19631732 but it didnt fix the issue.

Are there any possibilities of upgrading OpenDJ LDAP with minimalistic downtime?

I am planning to update LDAP OpenDJ 2.6.4 version to OpenDJ 4.4.11 version. Is there any recommended way to migrate the data to the new OpenDJ 4.4.11 LDAP server with minimalistic downtime?
The expectation is to migrate the data records to OpenDJ 4.4.11 version, with minimum downtime.
OpenDJ supports replication of data between servers of different versions.
And it also supports easy upgrade from version 2 to version 4.
If you have setup high availability through replicated servers, you should be able to upgrade with no downtime of the service.

WHM/CPanel update on a Linux, Apache server

I currently have a dedicated server running the following:
Apache/2.2.32
WHM/CPanel 11.44.3 (build 5)
MySQL Server version: 5.5.40-cll
Because of a security with the version of Cpanel I am told by my hosting company that Cpanel requires an update. The issue they have is because the current Cpanel is version 11.44.3 they can not update to the latest version.
Question, has anyone else had this issue and if so what was if any the resolution.
Many thanks in advance for your time
The hosting company are telling me that the only way around this issue is to have a completely new server configured with all the latest Apache, WHM/CPanel.
This of course would require all the scripts for our web site been transferred to the new server.
You have too old version and to avoid possible issues and downtime, it is recommended to setup and new server with CentOS 7 and latest cPanel and then migrate account one by one. This will allow you to check your websites one by one as you migrate. You should be able to generate full account backup and then you can restore it on a new server.
There is possibility to upgrade the version on your existing server but it is possible that it may cause other issues and you may face lots of issues and downtime.

Visual SVN Server compression and cpu peak

I have a Visual SVN Server 3.2 x64 installed in Windows 2008 R2 Server x64.
I have less or more 50 projects with some huge binary files (eg.: 500 MB). After a commit with large change (difference/delta) on those huge binary files i have notice a cpu peak. The server has a bit of traffic (400 clients/hour) and is fully dedicated to Visual SVN Server (AWS EC2 large instance)
After a little investigation i think the problem is in the default compression of the default settings of Visual SVN Server.
Increase cache on delta doesn't help.
Visual SVN Server/subversion has a problem with compression large delta?
Disable it, when the delta between the commits is huge, is a best practice?
Other good suggestion is appreciated. Thanks.
Please, upgrade the server to the most recent version and see whether it helps. I'm pretty sure that the issue you've encountered has been already fixed. If the upgrade won't help, please drop us a line at support#visualsvn.com.
Upgrading from VisualSVN Server 3.2 to the latest 3.5 version should complete in less than 5 minutes. Please read KB95: Upgrading to VisualSVN Server 3.5 guide before beginning the upgrade.
You can get the latest VisualSVN Server installer at the main download page.
VisualSVN Server 3.2.x has reached End of Support in September, 2015. VisualSVN Server 3.2.x is not supported anymore and does not receive security and patch updates.
Please, keep your server instance up-to-date. We timely release maintenance updates for VisualSVN Server with security and bugfixes, and we strongly recommend our users to keep VisualSVN Server at the latest version. The list of fixed vulnerabilities is available for every release in VisualSVN Server changelog and on our release announcements page.

how to restart a subsystem in alfresco 4 community?

i'm working in installing and configuring Alfresco community edition 4 (alfresco-community-4.0.d-installer-linux-x64.bin) on a 64bit ubuntu server (10.04.4 LTS). I'm trying to authenticate and syncronize users and group with out OpenLDAP server but as long as we make changes to
$TOMCAT_HOME/shared/classes/alfresco/extension/subsystems/Authentication/ldap/ldap1/ldap-authentication.properties
i have to restart tomcat or the whole server.
Is there a way to restart only a single subsytem in alfresco community edition?
Thanks
Unfortunately, not. The reason is that JMX, which allows you to restart subsystems without a restart, is only available in Enterprise Edition.