vServer Resourcen

RauchenwaldC

New Member
Hab nen vServer bei server4you mit folgender zugesicherter Leistung:

OS: Debian 5.0

Main Features
Type virtual dedicated
Web Space 25,000 MB
CPU Power 3,000 MHz
Guaranteed RAM 1,024 MB
Guaranteed FlexRAM* 2,048 MB

Leider bekomm ich im Plesk des öfteren Internal Server Error. Laut support weil ich angeblich Resourcentechnisch am Limit unterwegs bin, was ich mir eigentlich nicht vorstellen kann... Hier mal ein paar Infos, vl kann mir ja jemand helfen...

top
top - 12:37:43 up 11:58, 3 users, load average: 0.06, 0.06, 0.07
Tasks: 41 total, 1 running, 40 sleeping, 0 stopped, 0 zombie
Cpu(s): 0.0%us, 0.0%sy, 0.0%ni,100.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Mem: 2097152k total, 293868k used, 1803284k free, 0k buffers
Swap: 0k total, 0k used, 0k free, 0k cached

PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
11695 root 15 0 76788 3576 2832 S 0 0.2 0:00.10 sshd
11733 root 15 0 19204 1280 984 S 0 0.1 0:04.68 htop
1 root 18 0 10304 740 620 S 0 0.0 0:02.22 init
1544 sw-cp-se 18 0 48876 3268 1564 S 0 0.2 0:00.31 sw-cp-serverd
11687 root 18 0 76788 3556 2816 S 0 0.2 0:00.01 sshd
11689 root 15 0 42076 1816 1396 S 0 0.1 0:00.00 sftp-server
11720 root 15 0 17512 1788 1272 S 0 0.1 0:00.00 bash
11741 root 18 0 76788 3580 2836 S 0 0.2 0:00.05 sshd
11743 root 15 0 76788 3584 2836 S 0 0.2 0:00.06 sshd
11921 root 15 0 17512 1796 1272 S 0 0.1 0:00.00 bash
12122 root 18 0 17512 1792 1276 S 0 0.1 0:00.01 bash
13983 root 15 0 18540 932 712 S 0 0.0 0:00.07 cron
17655 root 18 0 218m 14m 7288 S 0 0.7 0:00.18 apache2
17656 www-data 15 0 154m 5608 476 S 0 0.3 0:00.00 apache2
18032 popuser 18 0 105m 42m 900 S 0 2.1 0:00.00 spamd
18242 postgres 18 0 99368 1504 696 S 0 0.1 0:00.20 postgres
18341 postgres 18 0 99368 1316 508 S 0 0.1 0:00.15 postgres

proc/user_beancounters
Version: 2.5
uid resource held maxheld barrier limit failcnt
10001564: kmemsize 13973472 46978510 49029120 54476800 0
lockedpages 0 104 344 344 26
privvmpages 84435 204962 524288 550502 0
shmpages 9732 19562 19567 19567 629
dummy 0 0 9223372036854775807 9223372036854775807 0
numproc 58 112 256 256 0
physpages 43799 72009 0 9223372036854775807 0
vmguarpages 0 0 262144 9223372036854775807 0
oomguarpages 43799 72009 9223372036854775807 9223372036854775807 0
numtcpsock 23 80 288 288 0
numflock 9 17 224 246 0
numpty 3 4 32 32 0
numsiginfo 0 32 512 512 0
tcpsndbuf 312376 1545288 2449232 3598712 0
tcprcvbuf 291656 3608600 2449232 3598712 144
othersockbuf 15504 288320 744366 1481926 0
dgramrcvbuf 0 25416 844366 844366 0
numothersock 14 48 288 288 0
dcachesize 1323990 1464181 7299072 8110080 0
numfile 2239 3108 6000 6000 0
dummy 0 0 0 0 0
dummy 0 0 0 0 0
dummy 0 0 0 0 0
numiptent 10 10 96 96 0

ps uax
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
root 1 0.0 0.0 10304 740 ? Ss 00:39 0:02 init [2]
1000 1544 0.0 0.1 48876 3268 ? S 00:39 0:00 /usr/sbin/sw-cp
root 11687 0.0 0.1 76788 3556 ? Ss 12:16 0:00 sshd: root@nott
root 11689 0.0 0.0 42076 1816 ? Ss 12:16 0:00 /usr/lib/openss
root 11695 0.0 0.1 76788 3576 ? Ss 12:16 0:00 sshd: root@pts/
root 11720 0.0 0.0 17512 1788 pts/0 Ss 12:16 0:00 -bash
root 11733 0.3 0.0 19204 1280 pts/0 S+ 12:16 0:03 htop
root 11741 0.0 0.1 76788 3580 ? Ss 12:16 0:00 sshd: root@pts/
root 11743 0.0 0.1 76788 3584 ? Ss 12:16 0:00 sshd: root@pts/
root 11921 0.0 0.0 17512 1796 pts/1 Ss+ 12:17 0:00 -bash
root 12122 0.0 0.0 17512 1792 pts/2 Ss 12:18 0:00 -bash
root 13983 0.0 0.0 18540 932 ? Ss 00:40 0:00 /usr/sbin/cron
root 17655 0.0 0.7 224200 14772 ? Ss 12:24 0:00 /usr/sbin/apach
www-data 17656 0.0 0.2 158592 5608 ? S 12:24 0:00 /usr/sbin/apach
popuser 18032 0.0 2.0 107612 43316 ? S 00:44 0:00 spamd child
postgres 18242 0.0 0.0 99368 1504 ? Ss 00:44 0:00 postgres: write
postgres 18341 0.0 0.0 99368 1316 ? Ss 00:44 0:00 postgres: wal w
root 19547 0.0 0.0 5896 660 ? Ss 00:39 0:00 /sbin/syslogd
root 19645 0.0 0.0 17312 1440 ? S 00:39 0:00 /bin/sh /usr/bi
mysql 19694 0.1 1.5 223992 32308 ? Sl 00:39 1:11 /usr/sbin/mysql
root 19695 0.0 0.0 3772 596 ? S 00:39 0:00 logger -p daemo
postgres 20014 0.0 0.2 99368 5736 ? S 00:39 0:01 /usr/lib/postgr
root 22354 0.0 0.0 21712 864 ? S 00:39 0:00 /usr/lib/courie
root 22373 0.0 0.0 21712 860 ? S 00:39 0:00 /usr/lib/courie
root 22387 0.0 0.0 21712 872 ? S 00:39 0:00 /usr/lib/courie
root 22402 0.0 0.0 21712 872 ? S 00:39 0:00 /usr/lib/courie
root 22406 0.0 0.0 14048 1300 ? S 00:39 0:00 /usr/sbin/couri
www-data 24505 0.1 1.2 237616 26908 ? S 12:31 0:00 /usr/sbin/apach
www-data 25766 0.7 0.8 229472 18060 ? S 12:32 0:01 /usr/sbin/apach
www-data 25782 0.2 1.2 236032 25192 ? S 12:32 0:00 /usr/sbin/apach
www-data 25921 0.2 1.2 238224 26168 ? S 12:33 0:00 /usr/sbin/apach
www-data 25956 0.0 0.4 224336 9068 ? S 12:33 0:00 /usr/sbin/apach
www-data 26204 0.0 0.5 224568 10544 ? S 12:34 0:00 /usr/sbin/apach
www-data 26221 0.0 0.3 224200 8272 ? S 12:34 0:00 /usr/sbin/apach
www-data 26222 0.0 0.3 224200 8268 ? S 12:34 0:00 /usr/sbin/apach
www-data 26223 0.0 0.3 224200 8268 ? S 12:34 0:00 /usr/sbin/apach
www-data 26225 0.0 0.3 224200 8268 ? S 12:34 0:00 /usr/sbin/apach
root 26226 0.0 0.0 14720 980 pts/2 R+ 12:34 0:00 ps aux
root 29991 0.0 0.0 48856 1192 ? Ss 00:39 0:00 /usr/sbin/sshd
root 30015 0.0 0.0 19256 920 ? Ss 00:39 0:00 /usr/sbin/xinet
root 30194 0.0 2.1 107612 45076 ? Ss 00:39 0:01 /usr/sbin/spamd
qmails 32199 0.0 0.0 3840 576 ? S 00:39 0:00 qmail-send
qmaill 32201 0.0 0.0 3784 544 ? S 00:39 0:00 splogger qmail
root 32202 0.0 0.0 3824 464 ? S 00:39 0:00 qmail-lspawn |
qmailr 32203 0.0 0.0 3824 448 ? S 00:39 0:00 qmail-rspawn
qmailq 32204 0.0 0.0 3780 436 ? S 00:39 0:00 qmail-clean

Wäre echt toll wenn mir jemand verraten könnte wo ich hier ansetzen kann um das ganze stabil laufen zu lassen....
 
selbe problem wie bei mir... hab das auch schon hier gepostet bin noch am warten^^ hab auch schon mindestens 20 mal bei deren support angerufen die sagen immer dasselbe ich glaub auch nicht das das an uns liegt sondern an dem hostsystem wo unsere server drauf sind...
 
@RauchenwaldC: Dein Server hat schön mehrmals die ihm zugewiesenen Limits erreicht (letzte Spalte der user_beancounters): lockedpages, shmpages, tcprcvbuf. Hier gibts die Infos was das zu bedeuten hat: http://wiki.openvz.org/UBC_secondary_parameters

Es scheint so, als würde Dein Apache recht viel RAM verbrauchen. Da würde ich zunächst mal ansetzen.

Übrigens: Server4You ist nicht für die Einhaltung der Grenzwerte verantwortlich, darum müsst ihr Euch schon selbst kümmern. S4Y wird Euch wahrscheinlich Raten auf ein teureres Produkt zu wechseln. Zunächst würde ich aber erst einmal versuchen den Ressourcenverbrauch zu optimieren. Erst wenn das nichts helfen sollte, dann wäre ein Server-Upgrade angebracht. Bei einem älteren VServer wäre auch ein Upgrade innerhalb der Preisklasse auf ein neueres Modell möglich. Das würde aber auch einen neuen Vertrag bedeuten.

Die Ressourcen der S4Y-VServer lassen sich übrigens ermitteln, in dem man einen Testserver bestellt.

Anfang des Jahres bin ich übrigens von S4Y weg, da die bei ihren Limits recht knausrig sind. In die engere Auswahl kam damals HostEurope, da die ihre Parameter/Limits veröffentlichen (http://faq.hosteurope.de/index.php?cpid=13281) sowie Strato, da die keine Limits haben (irgendwelche Grenzen wird es dort sicher auch geben, aber ich habe sie bisher noch nicht erreicht).

Leider übersehen viele, dass es bei einem VServer unter Vituozzo/OpenVZ nicht nur um RAM/CPU/Festplatte geht. Zum Beispiel ist die Auslastung meines VServers eher gering, selbst bei vielen Zugriffen maximal 800MB RAM-Verbrauch bei 2GB zugesichertem RAM (4GB maximal). Bei einem Server von S4Y in der gleichen Preisklasse hätte ich aber schon längst z. B. die numfiles-Grenze erreicht.
 
Erstmal danke für die Antwort. Hab mir die Erklärungen der einzelnen Begriffe angesehen, werde daraus aber nicht schlau...

- Welche Möglichkeiten hab ich um Apache2 zu optimieren?

Hier mein Apache2.conf
#
# Based upon the NCSA server configuration files originally by Rob McCool.
#
# This is the main Apache server configuration file. It contains the
# configuration directives that give the server its instructions.
# See http://httpd.apache.org/docs/2.2/ for detailed information about
# the directives.
#
# Do NOT simply read the instructions in here without understanding
# what they do. They're here only as hints or reminders. If you are unsure
# consult the online docs. You have been warned.
#
# The configuration directives are grouped into three basic sections:
# 1. Directives that control the operation of the Apache server process as a
# whole (the 'global environment').
# 2. Directives that define the parameters of the 'main' or 'default' server,
# which responds to requests that aren't handled by a virtual host.
# These directives also provide default values for the settings
# of all virtual hosts.
# 3. Settings for virtual hosts, which allow Web requests to be sent to
# different IP addresses or hostnames and have them handled by the
# same Apache server process.
#
# Configuration and logfile names: If the filenames you specify for many
# of the server's control files begin with "/" (or "drive:/" for Win32), the
# server will use that explicit path. If the filenames do *not* begin
# with "/", the value of ServerRoot is prepended -- so "/var/log/apache2/foo.log"
# with ServerRoot set to "" will be interpreted by the
# server as "//var/log/apache2/foo.log".
#

### Section 1: Global Environment
#
# The directives in this section affect the overall operation of Apache,
# such as the number of concurrent requests it can handle or where it
# can find its configuration files.
#

#
# ServerRoot: The top of the directory tree under which the server's
# configuration, error, and log files are kept.
#
# NOTE! If you intend to place this on an NFS (or otherwise network)
# mounted filesystem then please read the LockFile documentation (available
# at <URL:http://httpd.apache.org/docs-2.1/mod/mpm_common.html#lockfile>);
# you will save yourself a lot of trouble.
#
# Do NOT add a slash at the end of the directory path.
#
ServerRoot "/etc/apache2"

#
# The accept serialization lock file MUST BE STORED ON A LOCAL DISK.
#
#<IfModule !mpm_winnt.c>
#<IfModule !mpm_netware.c>
LockFile /var/lock/apache2/accept.lock
#</IfModule>
#</IfModule>

#
# PidFile: The file in which the server should record its process
# identification number when it starts.
# This needs to be set in /etc/apache2/envvars
#
PidFile ${APACHE_PID_FILE}

#
# Timeout: The number of seconds before receives and sends time out.
#
Timeout 180

#
# KeepAlive: Whether or not to allow persistent connections (more than
# one request per connection). Set to "Off" to deactivate.
#
KeepAlive On

#
# MaxKeepAliveRequests: The maximum number of requests to allow
# during a persistent connection. Set to 0 to allow an unlimited amount.
# We recommend you leave this number high, for maximum performance.
#
MaxKeepAliveRequests 50

#
# KeepAliveTimeout: Number of seconds to wait for the next request from the
# same client on the same connection.
#
KeepAliveTimeout 15

##
## Server-Pool Size Regulation (MPM specific)
##

# prefork MPM
# StartServers: number of server processes to start
# MinSpareServers: minimum number of server processes which are kept spare
# MaxSpareServers: maximum number of server processes which are kept spare
# MaxClients: maximum number of server processes allowed to start
# MaxRequestsPerChild: maximum number of requests a server process serves
<IfModule mpm_prefork_module>
StartServers 4
MinSpareServers 4
MaxSpareServers 5
MaxClients 50
MaxRequestsPerChild 0
</IfModule>

# worker MPM
# StartServers: initial number of server processes to start
# MaxClients: maximum number of simultaneous client connections
# MinSpareThreads: minimum number of worker threads which are kept spare
# MaxSpareThreads: maximum number of worker threads which are kept spare
# ThreadsPerChild: constant number of worker threads in each server process
# MaxRequestsPerChild: maximum number of requests a server process serves
<IfModule mpm_worker_module>
StartServers 4
MaxClients 50
MinSpareThreads 4
MaxSpareThreads 5
ThreadsPerChild 15
MaxRequestsPerChild 0
</IfModule>

# These need to be set in /etc/apache2/envvars
User ${APACHE_RUN_USER}
Group ${APACHE_RUN_GROUP}

#
# AccessFileName: The name of the file to look for in each directory
# for additional configuration directives. See also the AllowOverride
# directive.
#

AccessFileName .htaccess

#
# The following lines prevent .htaccess and .htpasswd files from being
# viewed by Web clients.
#
<Files ~ "^\.ht">
Order allow,deny
Deny from all
</Files>

#
# DefaultType is the default MIME type the server will use for a document
# if it cannot otherwise determine one, such as from filename extensions.
# If your server contains mostly text or HTML documents, "text/plain" is
# a good value. If most of your content is binary, such as applications
# or images, you may want to use "application/octet-stream" instead to
# keep browsers from trying to display binary files as though they are
# text.
#
DefaultType text/plain


#
# HostnameLookups: Log the names of clients or just their IP addresses
# e.g., www.apache.org (on) or 204.62.129.132 (off).
# The default is off because it'd be overall better for the net if people
# had to knowingly turn this feature on, since enabling it means that
# each client request will result in AT LEAST one lookup request to the
# nameserver.
#
HostnameLookups Off

# ErrorLog: The location of the error log file.
# If you do not specify an ErrorLog directive within a <VirtualHost>
# container, error messages relating to that virtual host will be
# logged here. If you *do* define an error logfile for a <VirtualHost>
# container, that host's errors will be logged there and not here.
#
ErrorLog /var/log/apache2/error.log

#
# LogLevel: Control the number of messages logged to the error_log.
# Possible values include: debug, info, notice, warn, error, crit,
# alert, emerg.
#
LogLevel warn

# Include module configuration:
Include /etc/apache2/mods-enabled/*.load
Include /etc/apache2/mods-enabled/*.conf

# Include all the user configurations:
Include /etc/apache2/httpd.conf

# Include ports listing
Include /etc/apache2/ports.conf

#
# The following directives define some format nicknames for use with
# a CustomLog directive (see below).
# If you are behind a reverse proxy, you might want to change %h into %{X-Forwarded-For}i
#
LogFormat "%v:%p %h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\"" vhost_combined
LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\"" combined
LogFormat "%h %l %u %t \"%r\" %>s %b" common
LogFormat "%{Referer}i -> %U" referer
LogFormat "%{User-agent}i" agent

#
# Define an access log for VirtualHosts that don't define their own logfile
CustomLog /var/log/apache2/other_vhosts_access.log vhost_combined

#
# Customizable error responses come in three flavors:
# 1) plain text 2) local redirects 3) external redirects
#
# Some examples:
#ErrorDocument 500 "The server made a boo boo."
#ErrorDocument 404 /missing.html
#ErrorDocument 404 "/cgi-bin/missing_handler.pl"
#ErrorDocument 402 http://www.example.com/subscription_info.html
#

#
# Putting this all together, we can internationalize error responses.
#
# We use Alias to redirect any /error/HTTP_<error>.html.var response to
# our collection of by-error message multi-language collections. We use
# includes to substitute the appropriate text.
#
# You can modify the messages' appearance without changing any of the
# default HTTP_<error>.html.var files by adding the line:
#
# Alias /error/include/ "/your/include/path/"
#
# which allows you to create your own set of files by starting with the
# /usr/share/apache2/error/include/ files and copying them to /your/include/path/,
# even on a per-VirtualHost basis. The default include files will display
# your Apache version number and your ServerAdmin email address regardless
# of the setting of ServerSignature.
#
# The internationalized error documents require mod_alias, mod_include
# and mod_negotiation. To activate them, uncomment the following 30 lines.

# Alias /error/ "/usr/share/apache2/error/"
#
# <Directory "/usr/share/apache2/error">
# AllowOverride None
# Options IncludesNoExec
# AddOutputFilter Includes html
# AddHandler type-map var
# Order allow,deny
# Allow from all
# LanguagePriority en cs de es fr it nl sv pt-br ro
# ForceLanguagePriority Prefer Fallback
# </Directory>
#
# ErrorDocument 400 /error/HTTP_BAD_REQUEST.html.var
# ErrorDocument 401 /error/HTTP_UNAUTHORIZED.html.var
# ErrorDocument 403 /error/HTTP_FORBIDDEN.html.var
# ErrorDocument 404 /error/HTTP_NOT_FOUND.html.var
# ErrorDocument 405 /error/HTTP_METHOD_NOT_ALLOWED.html.var
# ErrorDocument 408 /error/HTTP_REQUEST_TIME_OUT.html.var
# ErrorDocument 410 /error/HTTP_GONE.html.var
# ErrorDocument 411 /error/HTTP_LENGTH_REQUIRED.html.var
# ErrorDocument 412 /error/HTTP_PRECONDITION_FAILED.html.var
# ErrorDocument 413 /error/HTTP_REQUEST_ENTITY_TOO_LARGE.html.var
# ErrorDocument 414 /error/HTTP_REQUEST_URI_TOO_LARGE.html.var
# ErrorDocument 415 /error/HTTP_UNSUPPORTED_MEDIA_TYPE.html.var
# ErrorDocument 500 /error/HTTP_INTERNAL_SERVER_ERROR.html.var
# ErrorDocument 501 /error/HTTP_NOT_IMPLEMENTED.html.var
# ErrorDocument 502 /error/HTTP_BAD_GATEWAY.html.var
# ErrorDocument 503 /error/HTTP_SERVICE_UNAVAILABLE.html.var
# ErrorDocument 506 /error/HTTP_VARIANT_ALSO_VARIES.html.var



# Include of directories ignores editors' and dpkg's backup files,
# see README.Debian for details.

# Include generic snippets of statements
Include /etc/apache2/conf.d/

# Include the virtual host configurations:
Include /etc/apache2/sites-enabled/
AddOutputFilter INCLUDES .shtml
AddType text/html .shtml
AddType application/x-httpd-php .php
AddType application/x-httpd-php-source .phps
 
HostEurope, da die ihre Parameter/Limits veröffentlichen (http://faq.hosteurope.de/index.php?cpid=13281)

Wenn ich das mit meinen Werten vergleiche... :mad:
... dann werd ich mich wohl von S4Y auch verabschieden müssen...

Wohl dem, der keine langen Vertragslaufzeiten hat!

Inzwischen sind mache VServer ähnlich leistungsfähig wie Root-Server.
Nur kann man sie nicht wirklich nutzen, da irgendeine andere Ressource vorher am Ende ist.:mad:
 
Server MPM: Prefork

Server version: Apache/2.2.9 (Debian)
Server built: Apr 20 2010 15:40:17
Server's Module Magic Number: 20051115:15
Server loaded: APR 1.2.12, APR-Util 1.2.12
Compiled using: APR 1.2.12, APR-Util 1.2.12
Architecture: 64-bit
Server MPM: Prefork
threaded: no
forked: yes (variable process count)
Server compiled with....
-D APACHE_MPM_DIR="server/mpm/prefork"
-D APR_HAS_SENDFILE
-D APR_HAS_MMAP
-D APR_HAVE_IPV6 (IPv4-mapped addresses enabled)
-D APR_USE_SYSVSEM_SERIALIZE
-D APR_USE_PTHREAD_SERIALIZE
-D SINGLE_LISTEN_UNSERIALIZED_ACCEPT
-D APR_HAS_OTHER_CHILD
-D AP_HAVE_RELIABLE_PIPED_LOGS
-D DYNAMIC_MODULE_LIMIT=128
-D HTTPD_ROOT=""
-D SUEXEC_BIN="/usr/lib/apache2/suexec"
-D DEFAULT_PIDLOG="/var/run/apache2.pid"
-D DEFAULT_SCOREBOARD="logs/apache_runtime_status"
-D DEFAULT_LOCKFILE="/var/run/apache2/accept.lock"
-D DEFAULT_ERRORLOG="logs/error_log"
-D AP_TYPES_CONFIG_FILE="/etc/apache2/mime.types"
-D SERVER_CONFIG_FILE="/etc/apache2/apache2.conf"
 
Die Failcounts sind eigentlich untypisch. Lockedpages wird kaum genutzt und tcprcvbuf deutet erstmal darauf, dass die Daten von außen schneller ankommen, als Web- oder sonstige Serverdienste diese verarbeiten können.

Zum shmpages: kann es sein, dass Plesk /dev/shm als RAM-Disk nutzt? Das geht nämlich direkt auf diesen Parameter (wie auch die shared_buffers von PostgreSQL). Mit nichtmal 20000 Pages Limit hast du da nichtmal 80MB zur Verfügung und PostgreSQL nimmt sich davon auch noch was. Was sagt denn df -k zum Füllgrad von /dev/shm?

Kannst du die Situation in Plesk nachstellen und dann schauen, was sich an den Zählern verändert hat?
 
Meine andere Frage wird nicht beantwortet?
Welche? Was der Apache macht? Kümmert sich darum die Anfragen zu verarbeiten, sind alles PHP Seiten.. (hoffe das ist das was du wissen wolltest)

Was sagt denn df -k zum Füllgrad von /dev/shm?

Filesystem 1K-blocks Used Available Use% Mounted on
/dev/vzfs 26214400 2078220 24136180 8% /
tmpfs 1048576 0 1048576 0% /lib/init/rw
tmpfs 1048576 0 1048576 0% /dev/shm
tmpfs 1048576 0 1048576 0% /opt/psa/handlers/before-local
tmpfs 1048576 0 1048576 0% /opt/psa/handlers/before-queue
tmpfs 1048576 0 1048576 0% /opt/psa/handlers/before-remote
tmpfs 1048576 636 1047940 1% /opt/psa/handlers/info
tmpfs 1048576 0 1048576 0% /opt/psa/handlers/spool

Kannst du die Situation in Plesk nachstellen und dann schauen, was sich an den Zählern verändert hat?

In wiefern in Plesk nachstellen?

Im Augenblick sehen die Werte so aus...
Version: 2.5
uid resource held maxheld barrier limit failcnt
10001564: kmemsize 16944975 46978510 49029120 54476800 0
lockedpages 0 104 344 344 26
privvmpages 90671 204962 524288 550502 0
shmpages 10100 19562 19567 19567 629
dummy 0 0 9223372036854775807 9223372036854775807 0
numproc 66 112 256 256 0
physpages 46179 72009 0 9223372036854775807 0
vmguarpages 0 0 262144 9223372036854775807 0
oomguarpages 46329 72009 9223372036854775807 9223372036854775807 0
numtcpsock 30 96 288 288 0
numflock 9 17 224 246 0
numpty 1 4 32 32 0
numsiginfo 0 32 512 512 0
tcpsndbuf 308000 1545288 2449232 3598712 0
tcprcvbuf 304784 3608600 2449232 3598712 144
othersockbuf 15504 288320 744366 1481926 0
dgramrcvbuf 0 25416 844366 844366 0
numothersock 24 49 288 288 0
dcachesize 1342770 1485498 7299072 8110080 0
numfile 2441 3108 6000 6000 0
dummy 0 0 0 0 0
dummy 0 0 0 0 0
dummy 0 0 0 0 0
numiptent 10 10 96 96 0
 
Back
Top