Archive for the tag 'service'

SBDavid

Creating Ensim Service Plan templates

To create a Service Plan template:

In the shortcuts section of the Home page, click Add Service Plan (Sites section).
Use the Service Plan Options Information to help you complete the form.
In the Save Plan area, save the plan as a new template or overwrite an existing template.

Before creating sites, you might want to create Service Plan templates. These templates are not required to create a site; however, they can make creating multiple sites easier and faster by establishing the services and utilities you want to assign to specific sites when you create them.

To save the plan as a new plan, select the Save as a new plan option. In the adjacent text box, enter the name of the new plan.

To update or overwrite an existing plan, select the Save as an existing plan option. From the list, click the arrow and choose a name.

To save this plan as the default plan, click the arrow and choose default.

Click Save.

Service Container on a Parallels Virtuozzo Containers hardware node can be created using ‘vzsveinstall‘ utility:

# vzsveinstall -D DISTRIB_DIR -s SERVICE_CT_IP

- DISTRIB_DIR - path to Virtuozzo distribution directory hierarchy on a server.
- SERVICE_CT_IP - IP address to be assigned to Service Container;

In case you have downloaded Virtuozzo distributive already (example for 64-bit PVC 4.0) as file “virtuozzo-4.0.0-${build_version}-x86_64.sfx”, please extract it in the following way:

# mkdir -p /vz/full_distr
# bash /path/to/virtuozzo-4.0.0-${build_version}-x86_64.sfx -d /vz/full_distr –extract

Create Service Container then using this command (make sure old Service Container #1 does not exist):

# vzsveinstall -v -D /vz/full_distr -s SERVICE_CT_IP

Please refer to man page on ‘vzsveinstall‘ utility for additional information.

Reference: http://parallels.com

Stopped Parallels Plesk Panel service starts automatically

Resolution: Make sure you did not remove the Parallels Plesk Panel event handlers that are required for the proper work of the module:

Service started lowest (0) psaadm /usr/local/psa/admin/bin/php /usr/local/psa/admin/bin/modules/watchdog/wd –monit-service= –plesk-name

Service stopped lowest (0) psaadm /usr/local/psa/admin/bin/php /usr/local/psa/admin/bin/modules/watchdog/wd –unmonit-service=

Note: If you use Debian Linux or Ubuntu Linux, the path to Watchdog’s system files is /opt/psa/admin/modules/watchdog/

Source : http://parallels.com/Plesk/

If you want to change the settings for recursive domain name service:

Go to Home > DNS Settings (in the Server group) > DNS Recursion.

Select the option you need:
* To allow recursive queries from all hosts, select Allow for all requests.
* To allow recursive queries from your own server and hosts from your network, select Allow for local requests only.
* To allow recursive queries only from your own server, select Deny.
Click OK.

Preventing Accidental Denial of Service

Linux allows you to set limits on the amount of system resources that users and groups can use.

Restricting System Resources

The following example shows a practical use of setting or restricting system resources for an database user account. For a list of system resource settings, see /etc/security/limits.conf. It would be a good idea to review the default settings of system resource.

database soft nofile 4096
database hard nofile 63536

The “soft limit” in the first line defines the number of file handles or open files that the database user will have after login. If the database user gets error messages about running out of file handles, then the database user can increase the number of file handles like in this example up to 63536 (”hard limit”) by running the following command:

ulimit -n 63536

Most shells like Bash provide control over various resources like the maximum allowable number of open file descriptors or the maximum number of processes available to a user. To see all shell limits, run:

ulimit -a

# ulimit -a
core file size (blocks, -c) 0
data seg size (kbytes, -d) unlimited
scheduling priority (-e) 20
file size (blocks, -f) unlimited
pending signals (-i) 16382
max locked memory (kbytes, -l) 64
max memory size (kbytes, -m) unlimited
open files (-n) 1024
pipe size (512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
real-time priority (-r) 0
stack size (kbytes, -s) 8192
cpu time (seconds, -t) unlimited
max user processes (-u) unlimited
virtual memory (kbytes, -v) unlimited
file locks (-x) unlimited

Each line describes a limit for a user in the form:

[domain] [type] [item] [value]
#
#Where:
# can be:
# - an user name
# - a group name, with @group syntax
# - the wildcard *, for default entry
# - the wildcard %, can be also used with %group syntax,
# for maxlogin limit
# - NOTE: group and wildcard limits are not applied to root.
# To apply a limit to the root user, must be
# the literal username root.
#
# can have the two values:
# - “soft” for enforcing the soft limits
# - “hard” for enforcing hard limits
# - cpu - max CPU time (MIN)
# - nproc - max number of processes
# - core - limits the core file size (KB)

Example:

@student hard nproc 50
@faculty soft nproc 50

« Prev - Next »