Monthly Archives: October 2018

Failed to start LSB: Bring up/down networking

Leave a reply

systemctl status network.service
● network.service - LSB: Bring up/down networking
Loaded: loaded (/etc/rc.d/init.d/network; bad; vendor preset: disabled)
Active: failed (Result: exit-code) since Tue 2018-10-16 14:53:33 EEST; 39s ago
Docs: man:systemd-sysv-generator(8)
Process: 19847 ExecStop=/etc/rc.d/init.d/network stop (code=exited, status=0/SUCCESS)
Process: 20735 ExecStart=/etc/rc.d/init.d/network start (code=exited, status=1/FAILURE)

Oct 16 14:53:33 xxx.xxx.lt network[20735]: RTNETLINK answers: File exists
Oct 16 14:53:33 xxx.xxx.lt network[20735]: RTNETLINK answers: File exists
Oct 16 14:53:33 xxx.xxx.lt network[20735]: RTNETLINK answers: File exists
Oct 16 14:53:33 xxx.xxx.lt network[20735]: RTNETLINK answers: File exists
Oct 16 14:53:33 xxx.xxx.lt network[20735]: RTNETLINK answers: File exists
Oct 16 14:53:33 xxx.xxx.lt network[20735]: RTNETLINK answers: File exists
Oct 16 14:53:33 xxx.xxx.lt systemd[1]: network.service: control process exited, code=exited status=1
Oct 16 14:53:33 xxx.xxx.lt systemd[1]: Failed to start LSB: Bring up/down networking.
Oct 16 14:53:33 xxxx.xxx.lt systemd[1]: Unit network.service entered failed state.
Oct 16 14:53:33 xxx.xxx.lt systemd[1]: network.service failed.

systemctl stop NetworkManager
systemctl disable NetworkManager
systemctl restart network

linux find disk usage grow

Leave a reply

lsof / > lsof_1.txt; sleep 15; lsof / > lsof_2.txt; sdiff -w250 lsof_1.txt lsof_2.txt > lsof_difference.txt; cat lsof_difference.txt | egrep '\||<|>'

This can take long:
touch new_file
find / -newer new_file -not -path "/proc/*" -exec ls -lh {} \;

Or just using iotop this way, monitor online:
iotop -Pbktoqqq -d 3

linux find nvme model

Leave a reply

yum install nvme-cli
nvme list

Node SN Model Namespace Usage Format FW Rev
—————- ——————– —————————————- ——— ————————– —————- ——–
/dev/nvme0n1 18IB50NWKT7S KXG50ZNV512G TOSHIBA 1 512.11 GB / 512.11 GB 512 B + 0 B AAGA4102
/dev/nvme1n1 18IB50L6KT7S KXG50ZNV512G TOSHIBA 1 512.11 GB / 512.11 GB 512 B + 0 B AAGA4102

YumRepo Error: All mirror URLs are not using ftp, http[s] or file.

Leave a reply


If you still have Centos 5 running:

yum install openssh-clients
YumRepo Error: All mirror URLs are not using ftp, http[s] or file.
Eg. Invalid release/repo/arch combination/
removing mirrorlist with no valid mirrors: /var/cache/yum/base/mirrorlist.txt
Error: Cannot retrieve repository metadata (repomd.xml) for repository: base. Please verify its path and try again

uname -a
... i686 i686 i386 GNU/Linux
echo "http://vault.centos.org/5.11/os/i386/" > /var/cache/yum/base/mirrorlist.txt

if 64x
echo "http://vault.centos.org/5.11/os/x86_64/" > /var/cache/yum/base/mirrorlist.txt
Then you can yum install openssh-clients

Failed to load resource: the server responded with a status of 405 (Method Not Allowed)

Leave a reply

[allowmethods:error] [pid 688212:tid 139871391713024] [client xx.xx.xx.xx:41682] AH01623: client method denied by server configuration: ‘PATCH’

this means server do not support PATCH, if this id directadmin server:

cd /usr/local/directadmin/custombuild
./build set http_methods GET:HEAD:POST:PUT:DELETE:PATCH
./build rewrite_confs