Solving linux partition /run out of inode space

 
The inode (index node) is a data structure in a Unix-style file system that describes a file-system object such as a file or a directory. Each inode stores the attributes and disk block locations of the object's data. What will happen if you inode full ?
 
root@darkstar:/run/test# df -hi
Filesystem Inodes IUsed IFree IUse% Mounted on
/dev/root 448K 237K 212K 53% /
devtmpfs 178K 577 177K 1% /dev
tmpfs 179K 179K 0 100% /run
tmpfs 179K 1 179K 1% /dev/shm
cgroup_root 179K 14 179K 1% /sys/fs/cgroup
none 179K 1 179K 1% /run/user/1000



mount -o remount,nr_inodes=<bignum> /run

Generate https self signed OKD Openshift



[root@master-b01 ~]# vi /etc/ssl/req.conf
[req]
distinguished_name = Abimayu
x509_extensions = v3_req
prompt = no
[Abimayu]
C = ID
ST = DKI Jakarta
L = Jakarta
O = PT. Abimayu Indonesia
OU = IT Operation
CN = 192.168.123.1
[v3_req]
keyUsage = keyEncipherment, dataEncipherment
extendedKeyUsage = serverAuth
subjectAltName = @alt_names
[alt_names]
DNS.1 = www.abimayu.com
DNS.2 = api.upg.apps.abimayu.com

Restore PostgreSQL 10.6 from crash server



Prepare the new machine with the same version PostgreSQL, ( in this case , we use 10.6 , On Slackware machine ).

PostgreSQL session : 
- Install PostgreSQL using this link  http://slackbuilds.org/repository/14.2/system/postgresql/
- Change version download source into :
  https://ftp.postgresql.org/pub/source/v10.6/postgresql-10.6.tar.gz
- Change version postgresql.SlackBuild ( 10.6 ) , edit line :
     VERSION=${VERSION:-10.6}
     PG_VERSION=${PG_VERSION:-10.6}
- Build  using script :

Install kali linux 2020.1




download https://cdimage.kali.org/kali-2020.1/

install offline kali linux 2020.1 ( make usb bootable first )

then boot your computer using this usb bootable media

In my thinkpad edge 330 ( laptop ) , there was a problem with the wifi & desktop manager,
so i use this step :

1. add the repository list :
add /etc/apt/sources.list
 deb http://http.kali.org/kali kali-rolling main non-free contrib

vacuum systemd journal logs




On this morning ( 02:10 AM ) on my server send alert that was disk usage was critical. We realize that size of folder /var/log/journal/ was not normal. The logs can start to add more and take considerable amount of disk space.

Use cloudfuse for access bizznet GIO Storage





yum install gcc make fuse-devel curl-devel libxml2-devel openssl-devel json-c-devel json-c json_simple json_diff
mkdir app/
cd app/
git clone https://github.com/redbo/cloudfuse.git

cd cloudfuse/
./configure
make
make install
export PKG_CONFIG_PATH=/lib64/pkgconfig/