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.
Related
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.
Previously I had a different version of WAS (8.5.5.3) this morning I installed WAS (8.5.5.6) on my laptop. Also I reinstalled MFP Server to point to new WAS
I started using 'Server configuration tool' then but somehow the tool remembers the old path '/opt/ibm/Websphere/Liberty' and all other old settings
Even I tried removing 'runtime' and 'application' and recreated but still 'tool' picks up the same old details by default
Is there any way to clear the old details (or cache) of 'Server configuration tool' ?
Thanks
Sathish kumar
In the current versions of MFP, there is no link between the application server you selected in Install Manager to deploy Application Center, and the application server that is presented first by the Server Configuration Tool when you deploy an MFP Server. The Server Configuration Tool looks at the list of application servers installed with Install Manager and presents them in the order in which it did find them.
I am trying to deploy the Phpscheduleit(http://sourceforge.net/projects/phpscheduleit/) open source software on a WAMP Server version 2.4.
One of the instructions states "The web server must have write access (0755) to /your-booked/tpl_c and /your-booked/tpl" Does anyone have any idea where I could change the write access to 0755?
Thanks.
I had a SharePoint server, now i want to move this from one machine to another machine.
This is what i did for the migration.
I have just installed sharepoint server in my new machine and i have removed the Sharepoint_config and wss_content databased from the new server. and i have restored both the databases from the old server. Then i tried to run the Central Admin and i got Unable to connect to content database error.
Is replacing the DB is wrong. is there any other way to migrate SP server from one machine to another. I have tried my taking Farm backup and restore i had many problem with that. so i feel replacing DB would be better for me. any suggestions please?
Move SharePoint between servers is a huge effort.
Data in databases are very depends on the SharePoint install and its environments. So, I suggest just re-install the SharePoint on the new server, and then restore site collection backups to the new install.
Install SharePoint Server on the new server machine
Backup site collections from the old server, follow this guide: http://technet.microsoft.com/en-us/library/cc263441(v=office.12).aspx
Create Web Applications on the new server
Restore site collections from the prev. backups, follow this guide: http://technet.microsoft.com/en-us/library/cc262087(v=office.12).aspx
Be aware, if you have farm level customize solutions (developed by Visual Studio) or css files deployed in the LAYOUT folder, don't forget to re-deploy them on the new server.
I guess this question is too old and my answer will not help topicstarter... However, I was looking to refresh my own knowledge on this topic and I feel it will be useful to share it here.
This solution is not good for every SharePoint deployments, of course, it's just a general idea.
And I don't think it suits production environments well... but if you are brave and foolish as myself, you can do it there as well, with some additional precautions like backups and so on.
Here are prerequisites:
SharePoint was initially installed in Farm mode (not in Single Server mode)
Both old and new servers are in the same domain
You know Farm Passphrase used for initial installation
Old server is still intact and accessible from the new server
Steps to do
Skip steps 2-6 if you don't want to move databases to new location
Install SharePoint on the new server and join to existing farm. See
https://technet.microsoft.com/en-us/library/cc261752.aspx for details on joining procedure.
Ensure that the SharePoint is read-only. You can just shut down MS SQL DBEngine service if it's ok for your users.
Install MSSQL Server on the new server or other location you want. Remember, that it's not a good idea to keep SharePoint and MSSQL on the same server if it's not a demo/dev environment
Move all SharePoint databases to the new MSSQL Server. You can simply copy all DB files and attach it to the new SQL, or go full backup and restore way.
Important: Create an SQL client alias on the new server with cliconfg tool. See blogs.msdn.com/b/priyo/archive/2013/09/13/sql-alias-for-sharepoint.aspx for details.
Use your old SQL instance name as alias name. E.g. if your old server had SQL installed alongside with SharePoint on SharePoint.mydomain.com, alias name should be "SharePoint.mydomain.com"
Set Server name for alias to the new SQL location. Something like "NewServer.mydomain.com"
Ensure that you specify correct port number for SQL connection or configure network for default dynamic port. It is not necessary only if you have local SQL server on the same machine.
Create identical SQL client alias on the old server (this is needed to correctly remove old server from farm)
Remove old server from the farm. See this technet article for details
Update DNS settings or whatever you use to point users to the new server.
That's it. Hope it will help someone
I can see that there is a key called "TfsUrl" in the appSettings part of the Web.config file for SVNBridge. Is this possible? Can I install the SVNBridge on a different machine to the TFS server? We are a big company and the admin people don't want to install svnbridge on their server.
Thanks
Yes you can. However, I have found it to be very slow depending on where the SVNBridge server is. In my testing I installed the SVNBridge server locally and pointed it at my production server over a VPN. With this setup it would take up to 3 minutes to just open the repository in TortoiseSVN. With the SVNBrige server installed on the same machine as TFS the load time is almost unnoticeable.