Oxidized init.d script for Centos 6

Oxidized init.d script for Centos 6

 

To run oxidized as service


1. copy init script from oxidized/extra

 cp /usr/local/rvm/gems/ruby-2.3.0/gems/oxidized-0.24.0/extra/oxidized.init.d /etc/init.d/<br />

2. if you installed oxidized using manual (added system user oxidized) and rvm you need to modify script

#cmd=oxidized
cmd="sudo -u oxidized /usr/local/rvm/gems/ruby-2.3.0/wrappers/oxidized"
args="--daemonize"

#pidfile=/etc/oxidized/pid
pidfile=/home/oxidized/.config/oxidized/pid


#export OXIDIZED_HOME=/etc/oxidized
export OXIDIZED_HOME=/home/oxidized/

3. after that start as normal service

# /etc/rc.d/init.d/oxidized start

# /etc/rc.d/init.d/oxidized status
sudo (pid  9987) is running...


# ps aux | grep oxi
oxidized  9987  1.2  0.6 861488 97496 ?        Sl   08:52   0:25 puma 3.12.0 (tcp://127.0.0.1:8888) [/]

#netstat -tulpn   | grep 88
tcp        0      0 127.0.0.1:8888              0.0.0.0:*                   LISTEN      9987/puma 3.12.0 (t

Comments

Post a Comment

Popular posts from this blog

Securing the Pi-hole with fail2ban to prevent DNS Amplification attacks

Securing the Pi-hole with fail2ban to prevent DNS Amplification attacks   1. Install fail2ban  sudo apt-get update ; sudo apt-get install fail2ban 2. create jail file vi /etc/fail2ban/jail.d/pihole-dns.conf [pihole-dns] enabled = true port     = 53 action   = %(banaction)s[name=%(__name__)s-tcp, port="%(port)s", protocol="tcp", chain="%(chain)s", actname=%(banaction)s-tcp]            %(banaction)s[name=%(__name__)s-udp, port="%(port)s", protocol="udp", chain="%(chain)s", actname=%(banaction)s-udp] logpath = /var/log/pihole.log findtime = 60 maxretry = 5 bantime = 3600   3. create filter file vi /etc/fail2ban/filter.d/pihole-dns.conf # Fail2Ban configuration file # # script from www.marek.tokyo # [INCLUDES] # Read common prefixes. If any customizations available -- read them from # common.local before = common.conf [Definition] _daemon = dnsmasq #...
Read more

Reduce (shrink) and resize raw disk at Proxmox

 Reduce (shrink) and resize raw disk at Proxmox 1. Check the status of raw disk:   #e2fsck -fy /hdd-img/images/111/vm-111-disk-1.raw e2fsck 1.46.5 (30-Dec-2021) Pass 1: Checking inodes, blocks, and sizes Pass 2: Checking directory structure Pass 3: Checking directory connectivity Pass 4: Checking reference counts Pass 5: Checking group summary information /hdd-img/images/111/vm-111-disk-1.raw: 135279/327680000 files (1.8% non-contiguous), 857599886/1310720000 blocks  2. At first, check raw disk size:   #qemu-img info /hdd-img/images/111/vm-111-disk-1.raw image: /hdd-img/images/111/vm-111-disk-1.raw file format: raw virtual size: 4.88 TiB (5368709120000 bytes) disk size: 3.59 TiB  3. Resize filesystem: -M - will resize to the minimum size based on saved files -p - will display progress bar #resize2fs -M -p /hdd-img/images/111/vm-111-disk-1.raw resize2fs 1.46.5 (30-Dec-2021) Resizing the filesystem on /hdd-img/images/111/vm-111-disk-1.raw to 852166716 (4k) blocks....
Read more

How to clean DB from old logs in Magento 1.x

How to clean DB from old logs in Magento 1.x Using MySQL truncate log_customer ; truncate log_quote ; truncate log_summary ; truncate log_summary_type ; truncate log_url ; truncate log_url_info ; truncate log_visitor ; truncate log_visitor_info ; truncate log_visitor_online ;     login to shell(SSH)  go with root/shell folder. execute the below command inside the shell folder   php - f log . php clean   enter this command to view the log data's size php -f log.php status This method will help you to clean the log data's very easy way.  
Read more