Cpanel is user friendly, we can easily update squirrel mail and horde as follows.
sh /usr/local/cpanel/bin/update-squirrelmail
sh /usr/local/cpanel/bin/update-horde
Cpanel is user friendly, we can easily update squirrel mail and horde as follows.
sh /usr/local/cpanel/bin/update-squirrelmail
sh /usr/local/cpanel/bin/update-horde
Setting your timezone
The timezone under Linux is set by a symbolic link from /etc/localtime[1] to a file in the /usr/share/zoneinfo[2] directory that corresponds with what timezone you are in. For example, since I’m in South Australia, /etc/localtime is a symlink to /usr/share/zoneinfo/Australia/South. To set this link, type:
ln -sf ../usr/share/zoneinfo/yourzone /etc/localtime
Replace your/zone with something like Australia/NSW or Australia/Perth. Have a look in the directories under /usr/share/zoneinfo to see what timezones are available.
This assumes that /usr/share/zoneinfo is linked to /etc/localtime as it is under Red Hat Linux.
MYSQL:
The server load had been high due to increased MySQL activity by one of the users database in the server. We have optimized the database and restarted the MySQL service.
The MySQL has been tweaked for excellent performance.
We have confirmed that all the services are running perfectly in the server. The server load has been brought to the normal level.
Swap memory :
The swap memory being used in the server is high.
This means that the physical memory on the server is not available. When the server uses the Swap or the Disk Memory, the processes slows down.
We would recommend upgrading the RAM in the server to at least 2GB, which will satisfy the current workload.
Monitor:
There was a heavy load on the server which contributed to the issues you had been facing. Currently the load is very stable and all services are up.
The server has remained stable. Have you noticed any issues on your end ? Please advise so that we can further trouble shoot any lasting problems.
We have confirmed that all the services are running perfectly in the server. The server load has been brought to the normal level.
Monitoring :
Thank you for your patience. This is an update as we have continued to monitor the services on your server and all has remained calm and the load low.
Have you experienced any issues on your end in the past 10 hours? If so please let us know in detail what issues occurred and we can do our best to resolve them . We will await your reply.
As stated earlier, we have been monitoring the server very closely and there has not been any reported issues by any other clients and we are not seeing any issues at this time.
top – 07:44:42 up 29 days, 19:19, 2 users, load average: 3.65, 3.75, 3.49
If you notice any issues on your end, please let us know.
We have taken as much precaution as possible to minimize this downtime.
The server has remained stable. Have you noticed any issues on your end?
Please advise so that we can further trouble shoot any lasting problems. We will leave this ticket open to continue monitoring the sites.
Reboot:
We will continue to monitor the server for progress on this situation and if you notice any issues, please do not hesitate to let us know.
Just to update you, the server was rebooted about 10 minutes ago as there was a heavy load on there which contributed to the issues you had been facing. Currently the load is very stable and all services should resume very shortly:
Shared Server Restriction
We are really sorry to say that we cannot install “FFMPEG” in a shared server. The main concerns of shared servers are performance and security.
It is a resource intensive program which may lead to high server load and hence affect all accounts hosted in the server.
We are not forcing you with shared server rules. We are ensuring more security for the server. Kindly understand the situation regarding this matter.
In such cases, you need to move to a dedicated server or VPS. If you wish, we can forward your request to our sales department.
Thanks a lot for your patience.
The mod security rules are usually put in a single file and Include that file in httpd.conf. So, the rules will be applicable to all virtualhost entries. But we can disable it for a particular domain by turning it off in the virtualhost entry.
Put the following entries in the corresponding virtualhost.
SecFilterEngine Off
SecAuditEngine Off