What killed WHT?

Admittedly, I don’t come here frequently, but it was always a fantastic resource.

Now, it’s hard to see where the good content is, the N… | Read the rest of https://www.webhostingtalk.com/showthread.php?t=1829656&goto=newpost

dnd 5e – What happens to the rider when their summoned mount is killed?

The rider should follow the rules of the mount getting knocked prone

There isn’t anything in the core rules that covers this exact situation, but a common-sense approach should be enough to make a ruling.

The Find Steed spell says:

When the steed drops to 0 hit points, it disappears, leaving behind no physical form.

The rules on mounting and dismounting state:

If your mount is knocked prone, you can use your reaction to dismount it as it falls and land on your feet. Otherwise, you are dismounted and fall prone in a space within 5 feet it.

If you combine the two, and consider that instead of going prone the mount has simply disappeared, allowing the rider to make the reaction dismount seems reasonable. If they chose not to use their reaction, then they fall prone.

A reasonable DM may decide to just call for a Dexterity saving throw from the rider as well, landing on their feet on a success, or falling prone in the dirt on a failure. But I think the rules lean more towards the dismount using a reaction. The rules on mounting and dismounting mention this:

If an effect moves your mount against its will while you’re on it, you must succeed on a DC 10 Dexterity saving throw or fall off the mount, landing prone in a space within 5 feet of it.

But in this case, the situation is not the same. The save is to fall off or stay on the mount, which clearly isn’t an option in this case where the mount doesn’t exist any more.

dnd 5e – Does a fiend drop any items carried when it is killed and returned to Avernus?

It’s up to the DM.

It is not explicitly stated that a slain devil drops what it is wearing or carrying. The only guidance we have is found in the Monster Manual:

If it dies outside the Nine Hells, a devil disappears in a cloud of sulfurous smoke or dissolves into a pool of ichor, instantly returning to its home layer, where it reforms at full strength.

I take this to mean that the devil itself, which does not include things it is carrying disappears, leaving behind what it was carrying.

But there are good reasons to rule differently.

If you rule that the devil drops its stuff, then a consistent application of that ruling to the spell banishment makes things very interesting. The effect of banishment would look something like this:

If the target is native to the plane of existence you’re on, you banish the target to a harmless demiplane. While there, the target is incapacitated. The target remains there until the spell ends, at which point the target reappears [completely naked] in the space it left or in the nearest unoccupied space if that space is occupied.

Banishment doesn’t mention the targeted creature taking its stuff. So this one could go either way in my estimation.

Why did the spellplague happen after Cyric killed Mystra?

From what I understand when a god kills another god he gets his portfolio. Wouldn’t this mean that when Cyric killed Mystra he should have just got her portfolio over magic, spells, and the weave?

ubuntu – nginx sometimes gets killed after reloading it using systemd

After upgrading my Ubuntu server to 20.04 from 18.04 the nginx started with strange behaviour. It dies randomly on systemctl reload nginx and complains that there is already process listening on given ports. Before I’m able to run portmap or something similar I’m already able to start nginx using systemctl start nginx with no problems so I think the problem is nginx is trying to bind to ports which are already taken by the old nginx being reloaded.

I haven’t tried much because I’m lost. I’ve checked that the /run/nginx.pid contains correct pid. There is docker on my server so I thought maybe some container starts trying to bind 80 or 443 but no. The only mapped port for docker is 8090.

Versions:

nginx -v
nginx version: nginx/1.18.0 (Ubuntu)

cat /etc/os-release 
VERSION="20.04.1 LTS (Focal Fossa)"
PRETTY_NAME="Ubuntu 20.04.1 LTS"
VERSION_ID="20.04"
...

Configuration files are valid:

nginx -t
nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
nginx: configuration file /etc/nginx/nginx.conf test is successful

All ports nginx binds to are the same it complains about in the journal log:

cat /etc/nginx/sites-enabled/* | grep listen | uniq
listen 80 default_server;
listen 127.0.0.1:8080;
listen 443 ssl http2;
listen (::):443 ssl http2;

Do you have any idea why nginx would die on reload? What more can I check?

Logs produced

Journal

Oct 28 01:32:24 fooServer systemd(1): Starting A high performance web server and a reverse proxy server...
Oct 28 01:32:25 fooServer systemd(1): Started A high performance web server and a reverse proxy server.
Oct 28 01:35:05 fooServer systemd(1): nginx.service: Main process exited, code=killed, status=11/SEGV
Oct 28 01:35:05 fooServer systemd(1): nginx.service: Killing process 587 (nginx) with signal SIGKILL.
Oct 28 01:35:05 fooServer systemd(1): nginx.service: Killing process 2048 (nginx) with signal SIGKILL.
Oct 28 01:35:05 fooServer systemd(1): nginx.service: Killing process 2049 (nginx) with signal SIGKILL.
Oct 28 01:35:05 fooServer systemd(1): nginx.service: Killing process 2050 (nginx) with signal SIGKILL.
Oct 28 01:35:05 fooServer systemd(1): nginx.service: Killing process 2051 (nginx) with signal SIGKILL.
Oct 28 01:35:05 fooServer systemd(1): nginx.service: Killing process 2052 (nginx) with signal SIGKILL.
Oct 28 01:35:05 fooServer systemd(1): nginx.service: Killing process 2053 (nginx) with signal SIGKILL.
Oct 28 01:35:05 fooServer systemd(1): nginx.service: Killing process 2054 (nginx) with signal SIGKILL.
Oct 28 01:35:05 fooServer systemd(1): nginx.service: Killing process 2055 (nginx) with signal SIGKILL.
Oct 28 01:35:05 fooServer systemd(1): nginx.service: Killing process 587 (nginx) with signal SIGKILL.
Oct 28 01:35:05 fooServer systemd(1): nginx.service: Killing process 2048 (nginx) with signal SIGKILL.
Oct 28 01:35:05 fooServer systemd(1): nginx.service: Killing process 2049 (nginx) with signal SIGKILL.
Oct 28 01:35:05 fooServer systemd(1): nginx.service: Killing process 2050 (nginx) with signal SIGKILL.
Oct 28 01:35:05 fooServer systemd(1): nginx.service: Killing process 2051 (nginx) with signal SIGKILL.
Oct 28 01:35:05 fooServer systemd(1): nginx.service: Killing process 2052 (nginx) with signal SIGKILL.
Oct 28 01:35:05 fooServer systemd(1): nginx.service: Killing process 2053 (nginx) with signal SIGKILL.
Oct 28 01:35:05 fooServer systemd(1): nginx.service: Killing process 2054 (nginx) with signal SIGKILL.
Oct 28 01:35:05 fooServer systemd(1): nginx.service: Killing process 2055 (nginx) with signal SIGKILL.
Oct 28 01:35:05 fooServer systemd(1): nginx.service: Failed with result 'signal'.
Nov 02 05:32:05 fooServer systemd(1): Starting A high performance web server and a reverse proxy server...
Nov 02 05:32:05 fooServer nginx(415078): nginx: (emerg) bind() to 0.0.0.0:80 failed (98: Address already in use)
Nov 02 05:32:05 fooServer nginx(415078): nginx: (emerg) bind() to 0.0.0.0:443 failed (98: Address already in use)
Nov 02 05:32:05 fooServer nginx(415078): nginx: (emerg) bind() to (::):80 failed (98: Address already in use)
Nov 02 05:32:05 fooServer nginx(415078): nginx: (emerg) bind() to (::):443 failed (98: Address already in use)
Nov 02 05:32:05 fooServer nginx(415078): nginx: (emerg) bind() to 127.0.0.1:8080 failed (98: Address already in use)
Nov 02 05:32:06 fooServer nginx(415078): nginx: (emerg) bind() to 0.0.0.0:80 failed (98: Address already in use)
Nov 02 05:32:06 fooServer nginx(415078): nginx: (emerg) bind() to 0.0.0.0:443 failed (98: Address already in use)
Nov 02 05:32:06 fooServer nginx(415078): nginx: (emerg) bind() to (::):80 failed (98: Address already in use)
Nov 02 05:32:06 fooServer nginx(415078): nginx: (emerg) bind() to (::):443 failed (98: Address already in use)
Nov 02 05:32:06 fooServer nginx(415078): nginx: (emerg) bind() to 127.0.0.1:8080 failed (98: Address already in use)
Nov 02 05:32:06 fooServer nginx(415078): nginx: (emerg) bind() to 0.0.0.0:80 failed (98: Address already in use)
Nov 02 05:32:06 fooServer nginx(415078): nginx: (emerg) bind() to 0.0.0.0:443 failed (98: Address already in use)
Nov 02 05:32:06 fooServer nginx(415078): nginx: (emerg) bind() to (::):80 failed (98: Address already in use)
Nov 02 05:32:06 fooServer nginx(415078): nginx: (emerg) bind() to (::):443 failed (98: Address already in use)
Nov 02 05:32:06 fooServer nginx(415078): nginx: (emerg) bind() to 127.0.0.1:8080 failed (98: Address already in use)
Nov 02 05:32:07 fooServer nginx(415078): nginx: (emerg) bind() to 0.0.0.0:80 failed (98: Address already in use)
Nov 02 05:32:07 fooServer nginx(415078): nginx: (emerg) bind() to 0.0.0.0:443 failed (98: Address already in use)
Nov 02 05:32:07 fooServer nginx(415078): nginx: (emerg) bind() to (::):80 failed (98: Address already in use)
Nov 02 05:32:07 fooServer nginx(415078): nginx: (emerg) bind() to (::):443 failed (98: Address already in use)
Nov 02 05:32:07 fooServer nginx(415078): nginx: (emerg) bind() to 127.0.0.1:8080 failed (98: Address already in use)
Nov 02 05:32:07 fooServer nginx(415078): nginx: (emerg) bind() to 0.0.0.0:80 failed (98: Address already in use)
Nov 02 05:32:07 fooServer nginx(415078): nginx: (emerg) bind() to 0.0.0.0:443 failed (98: Address already in use)
Nov 02 05:32:07 fooServer nginx(415078): nginx: (emerg) bind() to (::):80 failed (98: Address already in use)
Nov 02 05:32:07 fooServer nginx(415078): nginx: (emerg) bind() to (::):443 failed (98: Address already in use)
Nov 02 05:32:07 fooServer nginx(415078): nginx: (emerg) bind() to 127.0.0.1:8080 failed (98: Address already in use)
Nov 02 05:32:08 fooServer nginx(415078): nginx: (emerg) still could not bind()
Nov 02 05:32:08 fooServer systemd(1): nginx.service: Control process exited, code=exited, status=1/FAILURE
Nov 02 05:32:08 fooServer systemd(1): nginx.service: Failed with result 'exit-code'.
Nov 02 05:32:08 fooServer systemd(1): Failed to start A high performance web server and a reverse proxy server.
Nov 02 05:32:17 fooServer systemd(1): Starting A high performance web server and a reverse proxy server...
Nov 02 05:32:17 fooServer nginx(415100): nginx: (emerg) bind() to 0.0.0.0:80 failed (98: Address already in use)
Nov 02 05:32:17 fooServer nginx(415100): nginx: (emerg) bind() to 0.0.0.0:443 failed (98: Address already in use)
Nov 02 05:32:17 fooServer nginx(415100): nginx: (emerg) bind() to (::):80 failed (98: Address already in use)
Nov 02 05:32:17 fooServer nginx(415100): nginx: (emerg) bind() to (::):443 failed (98: Address already in use)
Nov 02 05:32:17 fooServer nginx(415100): nginx: (emerg) bind() to 127.0.0.1:8080 failed (98: Address already in use)
Nov 02 05:32:17 fooServer nginx(415100): nginx: (emerg) bind() to 0.0.0.0:80 failed (98: Address already in use)
Nov 02 05:32:17 fooServer nginx(415100): nginx: (emerg) bind() to 0.0.0.0:443 failed (98: Address already in use)
Nov 02 05:32:17 fooServer nginx(415100): nginx: (emerg) bind() to (::):80 failed (98: Address already in use)
Nov 02 05:32:17 fooServer nginx(415100): nginx: (emerg) bind() to (::):443 failed (98: Address already in use)
Nov 02 05:32:17 fooServer nginx(415100): nginx: (emerg) bind() to 127.0.0.1:8080 failed (98: Address already in use)
Nov 02 05:32:18 fooServer nginx(415100): nginx: (emerg) bind() to 0.0.0.0:80 failed (98: Address already in use)
Nov 02 05:32:18 fooServer nginx(415100): nginx: (emerg) bind() to 0.0.0.0:443 failed (98: Address already in use)
Nov 02 05:32:18 fooServer nginx(415100): nginx: (emerg) bind() to (::):80 failed (98: Address already in use)
Nov 02 05:32:18 fooServer nginx(415100): nginx: (emerg) bind() to (::):443 failed (98: Address already in use)
Nov 02 05:32:18 fooServer nginx(415100): nginx: (emerg) bind() to 127.0.0.1:8080 failed (98: Address already in use)
Nov 02 05:32:18 fooServer nginx(415100): nginx: (emerg) bind() to 0.0.0.0:80 failed (98: Address already in use)
Nov 02 05:32:18 fooServer nginx(415100): nginx: (emerg) bind() to 0.0.0.0:443 failed (98: Address already in use)
Nov 02 05:32:18 fooServer nginx(415100): nginx: (emerg) bind() to (::):80 failed (98: Address already in use)
Nov 02 05:32:18 fooServer nginx(415100): nginx: (emerg) bind() to (::):443 failed (98: Address already in use)
Nov 02 05:32:18 fooServer nginx(415100): nginx: (emerg) bind() to 127.0.0.1:8080 failed (98: Address already in use)
Nov 02 05:32:19 fooServer nginx(415100): nginx: (emerg) bind() to 0.0.0.0:80 failed (98: Address already in use)
Nov 02 05:32:19 fooServer nginx(415100): nginx: (emerg) bind() to 0.0.0.0:443 failed (98: Address already in use)
Nov 02 05:32:19 fooServer nginx(415100): nginx: (emerg) bind() to (::):80 failed (98: Address already in use)
Nov 02 05:32:19 fooServer nginx(415100): nginx: (emerg) bind() to (::):443 failed (98: Address already in use)
Nov 02 05:32:19 fooServer nginx(415100): nginx: (emerg) bind() to 127.0.0.1:8080 failed (98: Address already in use)
Nov 02 05:32:19 fooServer nginx(415100): nginx: (emerg) still could not bind()
Nov 02 05:32:19 fooServer systemd(1): nginx.service: Control process exited, code=exited, status=1/FAILURE
Nov 02 05:32:19 fooServer systemd(1): nginx.service: Failed with result 'exit-code'.
Nov 02 05:32:19 fooServer systemd(1): Failed to start A high performance web server and a reverse proxy server.

/var/log/nginx/error.log:

2020/11/02 21:49:38 (info) 25842#25842: Using 32768KiB of shared memory for nchan in /etc/nginx/nginx.conf:74
2020/11/02 21:49:40 (notice) 25846#25846: signal process started
2020/11/02 21:51:09 (notice) 26353#26353: signal process started
2020/11/02 21:51:19 (info) 26357#26357: Using 32768KiB of shared memory for nchan in /etc/nginx/nginx.conf:74
2020/11/02 21:51:28 (info) 26364#26364: Using 32768KiB of shared memory for nchan in /etc/nginx/nginx.conf:74
2020/11/02 21:52:31 (notice) 26406#26406: signal process started
2020/11/02 21:52:31 (notice) 26418#26418: signal process started
2020/11/02 21:52:38 (info) 26431#26431: Using 32768KiB of shared memory for nchan in /etc/nginx/nginx.conf:74
2020/11/02 21:58:54 (info) 26584#26584: Using 32768KiB of shared memory for nchan in /etc/nginx/nginx.conf:74
2020/11/02 21:58:57 (notice) 26589#26589: signal process started
2020/11/02 22:04:04 (info) 31847#31847: Using 32768KiB of shared memory for nchan in /etc/nginx/nginx.conf:74
2020/11/02 22:04:06 (notice) 31855#31855: signal process started
2020/11/02 22:06:05 (info) 31925#31925: Using 32768KiB of shared memory for nchan in /etc/nginx/nginx.conf:74
2020/11/02 22:12:39 (notice) 32321#32321: signal process started
2020/11/02 22:13:40 (notice) 32392#32392: signal process started
2020/11/02 22:13:53 (info) 32413#32413: Using 32768KiB of shared memory for nchan in /etc/nginx/nginx.conf:74
2020/11/02 22:24:13 (notice) 39657#39657: signal process started
2020/11/02 22:24:40 (notice) 39837#39837: signal process started
2020/11/02 22:24:45 (info) 39870#39870: Using 32768KiB of shared memory for nchan in /etc/nginx/nginx.conf:74

Configuration

/etc/nginx/nginx.conf:

user www-data;
worker_processes auto;
pid /run/nginx.pid;
include /etc/nginx/modules-enabled/*.conf;

events {
    worker_connections 768;
    # multi_accept on;
}

http {
    ##
    # Basic Settings
    ##

    sendfile on;
    tcp_nopush on;
    tcp_nodelay on;
    keepalive_timeout 65;
    types_hash_max_size 2048;
    server_tokens off;
    client_max_body_size 1G;

    # server_names_hash_bucket_size 64;
    # server_name_in_redirect off;

    include /etc/nginx/mime.types;
    default_type application/octet-stream;

    ##
    # SSL Settings
    ##

    ssl_session_timeout 1d;
    ssl_session_cache shared:MozSSL:10m;  # about 40000 sessions
    ssl_session_tickets off;

    # curl https://ssl-config.mozilla.org/ffdhe2048.txt > /path/to/dhparam.pem
    ssl_dhparam /etc/nginx/ssl/dhparam.pem;

    # intermediate configuration
    ssl_protocols TLSv1.2 TLSv1.3;
    ssl_ciphers ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384;
    ssl_prefer_server_ciphers off;

    # HSTS (ngx_http_headers_module is required) (63072000 seconds)
    add_header Strict-Transport-Security "max-age=63072000" always;

    ##
    # Logging Settings
    ##

    access_log /var/log/nginx/access.log;
    error_log /var/log/nginx/error.log;

    ##
    # Gzip Settings
    ##

    gzip on;
    gzip_vary on;
    gzip_proxied any;
    gzip_comp_level 6;
    gzip_buffers 16 8k;
    gzip_http_version 1.1;
    gzip_types text/plain text/css application/json application/javascript text/xml application/xml application/xml+rss text/javascript;

    ##
    # Virtual Host Configs
    ##

    include /etc/nginx/conf.d/*.conf;
    include /etc/nginx/sites-enabled/*;
}

most of my /etc/nginx/sites-enabled/*.conf looks like this one:

  listen 443 ssl http2;
  server_name example.com;

  root /var/www/public;

  include fpm7.3.conf; # includes fastcgi_pass to php-fpm for *.php files

  ssl_certificate /etc/letsencrypt/live/example.com/fullchain.pem;
  ssl_certificate_key /etc/letsencrypt/live/example.com/privkey.pem;
  ssl_trusted_certificate /etc/letsencrypt/live/example.com/fullchain.pem;

  error_log /var/log/nginx/example.com.error.log;
  access_log /var/log/nginx/example.com.access.log;
}

Spam email king killed

Father of missing spam email king killed in Squamish offers $10K reward to help solve son’s homicide

[url]https://www.cbc.ca/amp/1.578469… | Read the rest of https://www.webhostingtalk.com/showthread.php?t=1827592&goto=newpost

dnd 5e – Will revivify work on a creature killed by Extract Brain?

So there are a couple of interesting things going on here.

One, while Raise Dead says the spell automatically fails if the creature is missing vital parts or organs, Revivify lacks this clause. It is an open question, therefore, whether the spell actually functions on such a target or not.

Two, Revivify also lacks several other clauses. It lacks the clause in Raise Dead that resurrecting a creature causes that creature to take penalties because of strain. It can be cast on any creature that died in the last minute, willing or no, and it allows no saving throw! It is cast in a single action, instead of 1 hour. These are very odd, because Revivify is lower level than Raise Dead. One might say that this is counterbalanced by Revivify only working on those who have died in the very immediate past, but this is not balanced.

When I want to rez somebody, there’s a very good chance it’s because the party is currently getting its ass handed to it. In this scenario, all the other resurrection magic is useless; you can’t rez someone until the fighting is over. But Revivify will get them back into the fight with no ill effects for the cost of one action, able to take actions immediately. This is beyond even the power of True Resurrection, a ninth level spell!

Finally, interestingly enough, by RAW, it doesn’t actually matter whether it works or not. If it doesn’t work, well, it doesn’t work. But there is the absurd possibility that it does work, but the resurrected creature immediately dies a second time.

In other words, Revivify probably needs to be errata’ed. It’s a third level spell in many ways more powerful than a 9th level spell. And in this specific case, it doesn’t matter whether the spell works (unless some other game effect triggers as a result of the target coming back to life momentarily) – technically, the target is still dead after the spell is cast, although it may briefly have come back to life in the interim.

The most reasonable interpretation is the spell is supposed to include those restrictions, but the designers cut too much out of the description.

Composer killed when installing a module

  • I am actually running Drupal on a LAMP (XUbuntu 20-04 with 4 GB RAM in VirtualBox)
  • At the beginning of the installation I had no problem with installing dependencies using composer
  • But since yesterday every composer command gets killed like in the following code (entity print installation):
igpde@igpde-VirtualBox:/var/www/html/d8igpde2$ composer require dompdf/dompdf
Using version ^0.8.6 for dompdf/dompdf
./composer.json has been updated
Loading composer repositories with package information
Updating dependencies (including require-dev)
Killed

  • I thought it could be a memory problem but in the php 7.4 client installation:
    • I read -1 should mean no limit
; Maximum amount of memory a script may consume (128MB)
; http://php.net/memory-limit
memory_limit = -1
  • Any Id how I could solve this problem?

Thanks in advance for you suggestions

  • Running with the vvv flag:
igpde@igpde-VirtualBox:/var/www/html/d8igpde2$ composer -vvv require dompdf/dompdf | tee composer.log
Reading ./composer.json
Loading config file ./composer.json
Checked CA file /etc/ssl/certs/ca-certificates.crt: valid
Executing command (/var/www/html/d8igpde2): git branch --no-color --no-abbrev -v
Executing command (/var/www/html/d8igpde2): git describe --exact-match --tags
Executing command (CWD): git --version
Executing command (/var/www/html/d8igpde2): git log --pretty="%H" -n1 HEAD --no-show-signature
Executing command (/var/www/html/d8igpde2): hg branch
Executing command (/var/www/html/d8igpde2): fossil branch list
Executing command (/var/www/html/d8igpde2): fossil tag list
Executing command (/var/www/html/d8igpde2): svn info --xml
Failed to initialize global composer: Composer could not find the config file: /home/igpde/.config/composer/composer.json
To initialize a project, please create a composer.json file as described in the https://getcomposer.org/ "Getting Started" section
Reading /var/www/html/d8igpde2/vendor/composer/installed.json
Loading plugin DrupalComposerPluginProjectMessageMessagePlugin
Loading plugin DrupalComposerPluginScaffoldPlugin
Loading plugin DrupalConsoleComposerPluginExtender
Loading plugin ComposerInstallersPlugin
Running 1.10.9 (2020-07-16 12:57:00) with PHP 7.4.3 on Linux / 5.4.0-42-generic
Downloading https://packages.drupal.org/8/packages.json
Writing /home/igpde/.cache/composer/repo/https---packages.drupal.org-8/packages.json into cache
Downloading https://repo.packagist.org/packages.json
Writing /home/igpde/.cache/composer/repo/https---repo.packagist.org/packages.json into cache
Reading /home/igpde/.cache/composer/repo/https---packages.drupal.org-8/drupal-provider-2020-3.json from cache
Reading /home/igpde/.cache/composer/repo/https---packages.drupal.org-8/drupal-provider-2020-2.json from cache
Reading /home/igpde/.cache/composer/repo/https---packages.drupal.org-8/drupal-provider-2020-1.json from cache
...............................................
Reading /home/igpde/.cache/composer/repo/https---repo.packagist.org/provider-sabberworm$php-css-parser.json from cache
Killed

  • the preceding output is very long
  • It waits a lot of time before declaring Killed. looks like a time out!
  • except for the last reading every Reading … happens fast

MySQL 5.7 High Memory usage Killed by OOM

i upgrade my WHM server / Cent-OS 7 from MySQL 5.6 to 5.7. after that upgrade every few hours my server memory full by MySQL which after hours of MySQL restart it exceed 80% of whole memory. i increase my server ram from 13GB to 17.5GB and still get same problem also i create swap for 3GB and still same problem. i change in MySQL configuration without any luck. so if anyone can help with that.

i try also mysqltuner but the problem that MySQL restarting every few hours and they said that MySQL must be running more than 24 hour at lease for recommendation to be accurate.

this is the configuration of the etc/my.cnf file:

(mysqld)
default-storage-engine=INNODB
innodb_file_per_table=1
max_allowed_packet=268435456
open_files_limit=80000


collation_server=utf8_unicode_ci
character_set_server=utf8
slow_query_log=1
long_query_time=3
max_connections = 200
sort_buffer_size=16M
join_buffer_size=1M
innodb_sort_buffer_size=16M
read_buffer_size=1M
read_rnd_buffer_size=2M
max_heap_table_size=64M
tmp_table_size=64M
key_buffer_size=128M
#event_scheduler=on

innodb_log_file_size=384M
query_cache_type=0
query_cache_size=0
table_open_cache=78000
table_definition_cache=39400
innodb_buffer_pool_instances=3
innodb_buffer_pool_size=3G

and the result of mysql tuner i don’t know if it can help as MySQL not running from a long time:

>>  MySQLTuner 1.7.19 - Major Hayden <major@mhtx.net>
 >>  Bug reports, feature requests, and downloads at http://mysqltuner.com/
 >>  Run with '--help' for additional options and output filtering

(--) Skipped version check for MySQLTuner script
(OK) Currently running supported MySQL version 5.7.31-log
(OK) Operating on 64-bit architecture

-------- Log file Recommendations ------------------------------------------------------------------
(OK) Log file /var/lib/mysql/bilal.hosting.err exists
(--) Log file: /var/lib/mysql/bilal.hosting.err(10K)
(OK) Log file /var/lib/mysql/bilal.hosting.err is readable.
(OK) Log file /var/lib/mysql/bilal.hosting.err is not empty
(OK) Log file /var/lib/mysql/bilal.hosting.err is smaller than 32 Mb
(!!) /var/lib/mysql/bilal.hosting.err contains 16 warning(s).
(!!) /var/lib/mysql/bilal.hosting.err contains 2 error(s).
(--) 2 start(s) detected in /var/lib/mysql/bilal.hosting.err
(--) 1) 2020-09-12T11:38:30.571913Z 0 (Note) /usr/sbin/mysqld: ready for connections.
(--) 2) 2020-09-12T05:40:13.253650Z 0 (Note) /usr/sbin/mysqld: ready for connections.
(--) 0 shutdown(s) detected in /var/lib/mysql/bilal.hosting.err

-------- Storage Engine Statistics -----------------------------------------------------------------
(--) Status: +ARCHIVE +BLACKHOLE +CSV -FEDERATED +InnoDB +MEMORY +MRG_MYISAM +MyISAM +PERFORMANCE_SCHEMA
(--) Data in MyISAM tables: 10.0M (Tables: 51)
(--) Data in InnoDB tables: 5.4G (Tables: 30538)
(OK) Total fragmented tables: 0

-------- Analysis Performance Metrics --------------------------------------------------------------
(--) innodb_stats_on_metadata: OFF
(OK) No stat updates during querying INFORMATION_SCHEMA.

-------- Security Recommendations ------------------------------------------------------------------
(OK) There are no anonymous accounts for any database users
(OK) All database users have passwords assigned
(--) There are 620 basic passwords in the list.

-------- CVE Security Recommendations --------------------------------------------------------------
(OK) NO SECURITY CVE FOUND FOR YOUR VERSION

-------- Performance Metrics -----------------------------------------------------------------------
(--) Up for: 1h 20m 30s (407K q (84.438 qps), 8K conn, TX: 248M, RX: 48M)
(--) Reads / Writes: 98% / 2%
(--) Binary logging is disabled
(--) Physical Memory     : 17.0G
(--) Max MySQL memory    : 57.2G
(--) Other process memory: 0B
(--) Total buffers: 3.2G global + 276.2M per thread (200 max threads)
(--) P_S Max memory usage: 72B
(--) Galera GCache Max memory usage: 0B
(OK) Maximum reached memory usage: 5.1G (29.97% of installed RAM)
(!!) Maximum possible memory usage: 57.2G (336.45% of installed RAM)
(!!) Overall possible memory usage with other process exceeded memory
(OK) Slow queries: 0% (21/407K)
(OK) Highest usage of available connections: 3% (7/200)
(OK) Aborted connections: 0.01%  (1/8243)
(!!) name resolution is active : a reverse name resolution is made for each new connection and can reduce performance
(OK) Query cache is disabled by default due to mutex contention on multiprocessor machines.
(OK) Sorts requiring temporary tables: 3% (872 temp sorts / 25K sorts)
(!!) Joins performed without indexes: 2920
(OK) Temporary tables created on disk: 1% (4K on disk / 414K total)
(OK) Thread cache hit rate: 99% (7 created / 8K connections)
(!!) Table cache hit rate: 4% (39K open / 851K opened)
(!!) table_definition_cache(39400) is lower than number of tables(44053)
(OK) Open file limit used: 0% (312/80K)
(OK) Table locks acquired immediately: 99% (1K immediate / 1K locks)

-------- Performance schema ------------------------------------------------------------------------
(--) Memory used by P_S: 72B
(--) Sys schema is installed.

-------- ThreadPool Metrics ------------------------------------------------------------------------
(--) ThreadPool stat is disabled.

-------- MyISAM Metrics ----------------------------------------------------------------------------
(!!) Key buffer used: 18.3% (24M used / 134M cache)
(OK) Key buffer size / total MyISAM indexes: 128.0M/1.1M
(OK) Read Key buffer hit rate: 98.8% (4K cached / 55 reads)
(!!) Write Key buffer hit rate: 92.5% (40 cached / 37 writes)

-------- InnoDB Metrics ----------------------------------------------------------------------------
(--) InnoDB is enabled.
(--) InnoDB Thread Concurrency: 0
(OK) InnoDB File per table is activated
(!!) InnoDB buffer pool / data size: 3.0G/5.4G
(OK) Ratio InnoDB log file size / InnoDB Buffer pool size: 384.0M * 2/3.0G should be equal to 25%
(OK) InnoDB buffer pool instances: 3
(--) Number of InnoDB Buffer Pool Chunk : 24 for 3 Buffer Pool Instance(s)
(OK) Innodb_buffer_pool_size aligned with Innodb_buffer_pool_chunk_size & Innodb_buffer_pool_instances
(OK) InnoDB Read buffer efficiency: 99.95% (216374723 hits/ 216488054 total)
(!!) InnoDB Write Log efficiency: 86.23% (10420 hits/ 12084 total)
(OK) InnoDB log waits: 0.00% (0 waits / 1664 writes)

-------- AriaDB Metrics ----------------------------------------------------------------------------
(--) AriaDB is disabled.

-------- TokuDB Metrics ----------------------------------------------------------------------------
(--) TokuDB is disabled.

-------- XtraDB Metrics ----------------------------------------------------------------------------
(--) XtraDB is disabled.

-------- Galera Metrics ----------------------------------------------------------------------------
(--) Galera is disabled.

-------- Replication Metrics -----------------------------------------------------------------------
(--) Galera Synchronous replication: NO
(--) No replication slave(s) for this server.
(--) Binlog format: ROW
(--) XA support enabled: ON
(--) Semi synchronous replication Master: Not Activated
(--) Semi synchronous replication Slave: Not Activated
(--) This is a standalone server

-------- Recommendations ---------------------------------------------------------------------------
General recommendations:
    Control warning line(s) into /var/lib/mysql/bilal.hosting.err file
    Control error line(s) into /var/lib/mysql/bilal.hosting.err file
    MySQL was started within the last 24 hours - recommendations may be inaccurate
    Reduce your overall MySQL memory footprint for system stability
    Dedicate this server to your database for highest performance.
    Configure your accounts with ip or subnets only, then update your configuration with skip-name-resolve=1
    We will suggest raising the 'join_buffer_size' until JOINs not using indexes are found.
             See https://dev.mysql.com/doc/internals/en/join-buffer-size.html
             (specially the conclusions at the bottom of the page).
    Increase table_open_cache gradually to avoid file descriptor limits
    Read this before increasing table_open_cache over 64: https://bit.ly/2Fulv7r
    Read this before increasing for MariaDB https://mariadb.com/kb/en/library/optimizing-table_open_cache/
    This is MyISAM only table_cache scalability problem, InnoDB not affected.
    See more details here: https://bugs.mysql.com/bug.php?id=49177
    This bug already fixed in MySQL 5.7.9 and newer MySQL versions.
    Beware that open_files_limit (80000) variable
    should be greater than table_open_cache (39895)
Variables to adjust:
  *** MySQL's maximum memory usage is dangerously high ***
  *** Add RAM before increasing MySQL buffer variables ***
    join_buffer_size (> 1.0M, or always use indexes with JOINs)
    table_open_cache (> 39895)
    table_definition_cache(39400) > 44053 or -1 (autosizing if supported)
    innodb_buffer_pool_size (>= 5.4G) if possible.

note i try to put innodb_buffer_pool_size to 6G as recommended but still the same memory load.

also no load on the server or mysql. and on top just the mysql is taking the memory above 70% of it

and this the output of free:

              total        used        free      shared  buff/cache   available
Mem:            16G         13G        323M         14M        3.6G        3.6G
Swap:          3.0G        2.1G        933M
Total:          19G         15G        1.2G

Thanks,

Drupal 9.0.5 composer killed when installing a module

  • I am actually running Drupal on a LAMP (XUbuntu 20-04 with 4 GB RAM in VirtualBox)
  • At the beginning of the installation I had no problem with installing dependencies using composer
  • But since yesterday every composer command gets killed like in the following code (entity print installation):
igpde@igpde-VirtualBox:/var/www/html/d8igpde2$ composer require dompdf/dompdf
Using version ^0.8.6 for dompdf/dompdf
./composer.json has been updated
Loading composer repositories with package information
Updating dependencies (including require-dev)
Killed

  • I thought it could be a memory problem but in the php 7.4 client installation:
    • I read -1 should mean no limit
; Maximum amount of memory a script may consume (128MB)
; http://php.net/memory-limit
memory_limit = -1
  • Any Id how I could solve this problem?

Thanks in advance for you suggestions

  • Running with the vvv flag:
igpde@igpde-VirtualBox:/var/www/html/d8igpde2$ composer -vvv require dompdf/dompdf | tee composer.log
Reading ./composer.json
Loading config file ./composer.json
Checked CA file /etc/ssl/certs/ca-certificates.crt: valid
Executing command (/var/www/html/d8igpde2): git branch --no-color --no-abbrev -v
Executing command (/var/www/html/d8igpde2): git describe --exact-match --tags
Executing command (CWD): git --version
Executing command (/var/www/html/d8igpde2): git log --pretty="%H" -n1 HEAD --no-show-signature
Executing command (/var/www/html/d8igpde2): hg branch
Executing command (/var/www/html/d8igpde2): fossil branch list
Executing command (/var/www/html/d8igpde2): fossil tag list
Executing command (/var/www/html/d8igpde2): svn info --xml
Failed to initialize global composer: Composer could not find the config file: /home/igpde/.config/composer/composer.json
To initialize a project, please create a composer.json file as described in the https://getcomposer.org/ "Getting Started" section
Reading /var/www/html/d8igpde2/vendor/composer/installed.json
Loading plugin DrupalComposerPluginProjectMessageMessagePlugin
Loading plugin DrupalComposerPluginScaffoldPlugin
Loading plugin DrupalConsoleComposerPluginExtender
Loading plugin ComposerInstallersPlugin
Running 1.10.9 (2020-07-16 12:57:00) with PHP 7.4.3 on Linux / 5.4.0-42-generic
Downloading https://packages.drupal.org/8/packages.json
Writing /home/igpde/.cache/composer/repo/https---packages.drupal.org-8/packages.json into cache
Downloading https://repo.packagist.org/packages.json
Writing /home/igpde/.cache/composer/repo/https---repo.packagist.org/packages.json into cache
Reading /home/igpde/.cache/composer/repo/https---packages.drupal.org-8/drupal-provider-2020-3.json from cache
Reading /home/igpde/.cache/composer/repo/https---packages.drupal.org-8/drupal-provider-2020-2.json from cache
Reading /home/igpde/.cache/composer/repo/https---packages.drupal.org-8/drupal-provider-2020-1.json from cache
...............................................
Reading /home/igpde/.cache/composer/repo/https---repo.packagist.org/provider-sabberworm$php-css-parser.json from cache
Killed

  • the preceding output is very long
  • It waits a lot of time before declaring Killed. looks like a time out!
  • except for the last reading every Reading … happens fast