Want more timely Centmin Mod News Updates?
Become a Member

VPS Lockup

Discussion in 'Install & Upgrades or Pre-Install Questions' started by GASTAN, Feb 19, 2018.

  1. GASTAN

    GASTAN New Member

    24
    3
    3
    Jun 28, 2017
    Ratings:
    +5
    Local Time:
    3:46 PM
    I have a problem with my server locking up.
    this is the second time and I had a chance to look into logs now.


    here is messages log:
    Code:
    Feb 18 11:50:01 ram02 systemd: Started Session 16112314 of user root.
    Feb 18 11:50:01 ram02 systemd: Starting Session 16112314 of user root.
    Feb 18 11:50:01 ram02 systemd: Removed slice User Slice of root.
    Feb 18 11:50:01 ram02 systemd: Stopping User Slice of root.
    Feb 18 11:55:02 ram02 systemd: Created slice User Slice of root.
    Feb 18 11:55:02 ram02 systemd: Starting User Slice of root.
    Feb 18 11:55:02 ram02 systemd: Started Session 16113667 of user root.
    Feb 18 11:55:02 ram02 systemd: Starting Session 16113667 of user root.
    Feb 18 11:55:02 ram02 systemd: Removed slice User Slice of root.
    Feb 18 11:55:02 ram02 systemd: Stopping User Slice of root.
    ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@Feb 18 12:00:01 ram02 systemd: Starting Session 16114825 of user root.
    Feb 18 12:00:01 ram02 systemd: Started Session 16114823 of user root.
    Feb 18 12:00:01 ram02 systemd: Starting Session 16114823 of user root.
    Feb 18 12:17:49 ram02 journal: Runtime journal is using 8.0M (max allowed 204.8M, trying to leave 307.2M free of 1.9G available <E2><86><92> current limit 204.8M).
    
    and here is cron:
    Code:
    Feb 18 11:50:01 ram02 CROND[11840]: (root) CMD (/usr/lib64/sa/sa1 1 1)
    Feb 18 11:55:02 ram02 CROND[11878]: (root) CMD (/usr/lib64/sa/sa1 1 1)
    ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
    ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
    ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@Feb 18 12:00:01 ram02 CROND[11915]: (root) CMD (/usr/lib64/sa/sa1
    1 1)
    Feb 18 12:00:01 ram02 CROND[11918]: (root) CMD (/usr/bin/cminfo_updater 2>/dev/null)
    Feb 18 12:17:52 ram02 crond[128]: (CRON) INFO (RANDOM_DELAY will be scaled with factor 26% if used.)
    Feb 18 12:17:53 ram02 crond[128]: (CRON) INFO (running with inotify support)
    Feb 18 12:20:01 ram02 CROND[1043]: (root) CMD (/usr/lib64/sa/sa1 1 1)
    Feb 18 12:25:01 ram02 CROND[1077]: (root) CMD (/usr/lib64/sa/sa1 1 1)
    
    same ^@ again as in messages.
    Interestingly enough most of the other log files are zero length, with timestamp of Nov 24 2017, when I installed Centmin:

    Code:
    ls -la php-fpm/
    total 8
    drwxr-xr-x 2 root root 4096 Nov 24 01:57 .
    drwxr-xr-x 6 root root 4096 Feb 18 03:50 ..
    -rw-rw---- 1 root root    0 Nov 24 01:57 www-error.log
    -rw-rw-rw- 1 root root    0 Nov 24 01:57 www-php.error.log
    
    Code:
    sar -u
    00:00:00        CPU     %user     %nice   %system   %iowait    %steal     %idle
    00:00:00        all      0.00      0.00      0.00      0.00      0.00      0.00
    00:00:00        all      0.00      0.00      0.00      0.00      0.00      0.00
    00:00:00        all      0.00      0.00      0.00      0.00      0.00      0.00
    00:00:00        all      0.00      0.00      0.00      0.00      0.00      0.00
    00:00:00        all      0.00      0.00      0.00      0.00      0.00      0.00
    00:00:00        all      0.00      0.00      0.00      0.00      0.00      0.00
    00:00:00        all      0.00      0.00      0.00      0.00      0.00      0.00
    00:00:00        all      0.00      0.00      0.00      0.00      0.00      0.00
    00:00:00        all      0.00      0.00      0.00      0.00      0.00      0.00
    00:00:00        all      0.00      0.00      0.00      0.00      0.00      0.00
    00:00:00        all      0.00      0.00      0.00      0.00      0.00      0.00
    00:00:00        all      0.00      0.00      0.00      0.00      0.00      0.00
    00:00:00        all      0.00      0.00      0.00      0.00      0.00      0.00
    00:00:00        all      0.00      0.00      0.00      0.00      0.00      0.00
    00:00:00        all      0.00      0.00      0.00      0.00      0.00      0.00
    00:00:00        all      0.00      0.00      0.00      0.00      0.00      0.00
    00:00:00        all      0.00      0.00      0.00      0.00      0.00      0.00
    00:00:00        all      0.00      0.00      0.00      0.00      0.00      0.00
    00:00:00        all      0.00      0.00      0.00      0.00      0.00      0.00
    00:00:00        all      0.00      0.00      0.00      0.00      0.00      0.00
    00:00:00        all      0.00      0.00      0.00      0.00      0.00      0.00
    00:00:00        all      0.00      0.00      0.00      0.00      0.00      0.00
    End of system activity file unexpected
    
    Server is running only one WP install and I must admit it used to lock up on older 1GB RAMnode, that's why I moved to 4GB.
    Any help will be appreciate on how to track down the problem.

    CentOS Linux release 7.4.1708 (Core) 64bit, 4GB RAM, ramnode
    123.09beta01
    nginx/1.13.7
    PHP 5.6.32 (cli)
    mysqld Ver 10.1.31-MariaDB for Linux on x86_64
     
  2. eva2000

    eva2000 Administrator Staff Member

    36,054
    7,910
    113
    May 24, 2014
    Brisbane, Australia
    Ratings:
    +12,192
    Local Time:
    11:46 PM
    Nginx 1.15.x
    MariaDB 5.5/10.x
    could you elaborate on the symptoms, what exact happens, any particular time of day or after specific activity/action i.e. yum updates etc ?

    probably need to start with initial install log inspection

    To troubleshoot initial installation, you need to check the initial install log at /root/centminlogs and instructions under Sharing logs and errors heading for using Pastebin.com or Gists to share a sanitised version of the contents of the initial install log. You can see full details at How to troubleshoot Centmin Mod initial install issues

    Example list /root/centminlogs files in date ascending order and grep for install.log
    Code (Text):
    ls -lahrt /root/centminlogs | grep install.log
    

    example output returns install log at /root/centminlogs/centminmod_1.2.3-eva2000.09.001_111016-112321_install.log
    Code (Text):
    ls -lahrt /root/centminlogs | grep install.log
    -rw-r--r--  1 root root 2.2M Oct 11 01:40 centminmod_1.2.3-eva2000.09.001_111016-112321_install.log
    

    in SSH use cat to ouput contents of /root/centminlogs/centminmod_1.2.3-eva2000.09.001_111016-112321_install.log. Clear your SSH client window/buffer so only output is the contents of the file
    Code (Text):
    cat /root/centminlogs/centminmod_1.2.3-eva2000.09.001_111016-112321_install.log
    

    Then copy and paste into Pastebin.com or Gists entry. If your SSH window scroll buffer isn't that large to get the whole contents of the install log, you can download file manually and copy and paste contents. But makes sure it's sanitised version of the contents of the initial install log as outlined at How to troubleshoot Centmin Mod initial install issues

    For 1Gb adn 4GB Ramnode plans, what specific VPS plan you using openvz ? kvm ? ssd or non-ssd cached disk ?

    Definitely overdue for updates to at least 1.13.8 and 5.6.33. Have you rebooted servers or done yum updates since initial centmin mod install ? Judging by your old versions used, have you updated for zlib workaround outlined at 123.09beta01 Updated Nginx zlib routine with optional Cloudflare zlib support ?

    I'd update Centmin Mod 123.09beta01. Getting Started Guide step 19 outlines also how to keep Centmin Mod code updated or how to switch version branches or you can run cmupdate command that was recently added.

    Centmin Mod LEMP stack's script code is constantly updated for improvements, bug fixes and security fixes so keeping the Centmin Mod code up to date is important. With Centmin Mod 1.2.3-eva2000.08) (123.08stable) and higher releases, a newly added centmin.sh menu option 23 allows much easier code updates and version branch swicthing via Git backed environment you can setup. For full details read the following links:
    Upgrading Centmin Mod involves 2 parts.
    1. Upgrading the actual Centmin Mod code outlined at Upgrade Centmin Mod. This is heart of Centmin Mod where the code is the engine that runs centmin.sh shell based menu and all the automation you're accustomed to. You can easily update within a Centmin Mod version branch or switch version branches via centmin.sh menu option 23 outlined here.
    2. Upgrade software that Centmin Mod installed or manages. For this part following outline at How to upgrade Centmin Mod software installed on your server.
    So essentially, you can upgrade from one version branch to another i.e. 123.08stable to 123.09beta01 or higher in place, but not everything is upgraded as some things like server initial environment setup isn't changed i.e. how swap, tmp setup and allocation are created etc. The main parts from part 2 above are what in place upgrades do i.e. Nginx and PHP-FPM compilation and config/settings parameters and MariaDB version from 5.5 to 10.0.x. If you want the full environment changed including tmp and swap setup to .08's configuration, then you would need a fresh OS install and fresh .08 initial install. You can think of it like upgrading Windows 7 to Windows 8. An in place upgrade will upgrade code but won't change your computer environment from when you installed Windows 7 i.e. disk configuration and partition sizes won't change from when you initially installed Windows 7. Only way to change that would be fresh Windows 8 install.
     
  3. eva2000

    eva2000 Administrator Staff Member

    36,054
    7,910
    113
    May 24, 2014
    Brisbane, Australia
    Ratings:
    +12,192
    Local Time:
    11:46 PM
    Nginx 1.15.x
    MariaDB 5.5/10.x
    Also simple things have you checked disk space ?
    Code (Text):
    df -hT
    
     
..