[root@server ~]# sh /script/sysinfo
A. Control Panel:
- Kloxo-MR: 7.0.0.c-2017081502
- Web: hiawatha-10.6.0-f.1.mr.el7.x86_64
- PHP: php56s - 5.6.30-2.ius.centos7 (fpm mode)
B. Plateform:
- OS: CentOS Linux release 7.3.1611 (Core) x86_64
- Hostname: server.vXXXXX.com
C. Services:
1. MySQL: MariaDB-server-10.0.32-1.el7.centos.x86_64
2. PHP:
- Installed:
- Branch: php56u-cli-5.6.32-1.ius.centos7.x86_64
- Multiple:
* php56m - 5.6.30-2.ius.centos7
- Used: php56m-fpm
- Multiple: disable
3. Web Used: lighttpd
- Hiawatha: hiawatha-10.6.0-f.1.mr.el7.x86_64
- Lighttpd: lighttpd-1.4.45-1.el7.x86_64
- Nginx: nginx-1.13.4-1.el7.ngx.x86_64
- Apache: httpd24u-2.4.27-1.ius.centos7.x86_64
- PHP Type: php-fpm_event
- Secondary PHP: off
4. WebCache: none
- ATS: --uninstalled--
- Squid: --uninstalled--
- Varnish: --uninstalled--
5. Dns: bind
- Bind: bind-9.9.9-1.mr.el7.x86_64
- DJBDns: djbdns-1.05-17.4.mr.el7.x86_64
- NSD: nsd-4.1.16-1.el7.x86_64
- PowerDNS: pdns-4.0.3-1.el7.MIND.x86_64
- Yadifa: yadifa-2.2.5-1.mr.el7.x86_64
6. Mail: qmail-toaster-1.03-1.3.57.mr.el7.x86_64
- pop3/imap4: courier-imap-toaster-4.1.2-1.3.20.mr.el7.x86_64
- smtp: qmail-toaster-1.03-1.3.57.mr.el7.x86_64
- spam: bogofilter-1.2.3-6.el7.x86_64
7. FTP: pure-ftpd
- pure-ftpd: pure-ftpd-1.0.42-3.el7.x86_64
8. Stats: awstats
- awstats: kloxomr-stats-awstats-7.6-1.mr.noarch
D. Memory:
total used free shared buff/cache available
Mem: 7877 467 6384 378 1025 6935
Swap: 1021 18 1003
E. Disk Space:
Filesystem Size Used Avail Use% Mounted on
/dev/root 39G 3.4G 33G 10% /
*** Process Time: 00:00:00:20.20824 (dd:hh:mm:ss:xxxxxx) ***
* Note: run 'sh /script/sysinfo -y' if you want run 'fix-service-list' also
(importance after Kloxo-MR update)
Above is sysinfo, I have just use the fix all permission from the kloxomr admin panel. After that my all website went down. I have used all old tricks switch program,
The website is working under lighthttpd only. When i switch back to apache again website went down.
[root@server ~]# sh /script/restart-web
Redirecting to /bin/systemctl restart php-fpm.service
-------------------------------------------------------------------
*** Process for HTTPD service ***
- Process: restart
Redirecting to /bin/systemctl stop httpd.service
Redirecting to /bin/systemctl start httpd.service
Job for httpd.service failed because the control process exited with error code. See "systemctl status httpd.service" and "journalctl -xe" for details.
-------------------------------------------------------------------
- For help, type '/script/restart-web [--help|-h]'
[root@server ~]# yum update -y
Loaded plugins: fastestmirror, priorities, protectbase, replace
auto-ffmpeg | 3.0 kB 00:00
base | 3.6 kB 00:00
extras | 3.4 kB 00:00
mratwork-epel/7/x86_64/metalink | 13 kB 00:00
mratwork-epel | 4.7 kB 00:00
mratwork-google-mod-pagespeed | 951 B 00:00
mratwork-ius-archive | 2.4 kB 00:00
mratwork-ius-stable | 2.3 kB 00:00
mratwork-mariadb | 2.9 kB 00:00
mratwork-nginx | 2.9 kB 00:00
mratwork-nginx-stable | 2.9 kB 00:00
mratwork-release-neutral-noarch | 1.3 kB 00:00
mratwork-release-version-arch | 1.2 kB 00:00
http://repo.varnish-cache.org/redhat/varnish-3.0/el7/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 410 - Gone
Trying other mirror.
One of the configured repositories failed (MRatWork - Varnish 3.0 for EL 7 - arch),
and yum doesn't have enough cached data to continue. At this point the only
safe thing yum can do is fail. There are a few ways to work "fix" this:
1. Contact the upstream for the repository and get them to fix the problem.
2. Reconfigure the baseurl/etc. for the repository, to point to a working
upstream. This is most often useful if you are using a newer
distribution release than is supported by the repository (and the
packages for the previous distribution release still work).
3. Run the command with the repository temporarily disabled
yum --disablerepo=mratwork-varnish-3.0 ...
4. Disable the repository permanently, so yum won't use it by default. Yum
will then just ignore the repository until you permanently enable it
again or use --enablerepo for temporary usage:
yum-config-manager --disable mratwork-varnish-3.0
or
subscription-manager repos --disable=mratwork-varnish-3.0
5. Configure the failing repository to be skipped, if it is unavailable.
Note that yum will try to contact the repo. when it runs most commands,
so will have to try and fail each time (and thus. yum will be be much
slower). If it is a very temporary problem though, this is often a nice
compromise:
yum-config-manager --save --setopt=mratwork-varnish-3.0.skip_if_unavailable=true
failure: repodata/repomd.xml from mratwork-varnish-3.0: [Errno 256] No more mirrors to try.
http://repo.varnish-cache.org/redhat/varnish-3.0/el7/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 410 - Gone
[root@server ~]#