CentOS disable SELinux permanently or one time on grub Linux kernel boot time

July 24th, 2021



1. Office 365 cloud connected computer and a VirtualBox hosted machine with SELINUX preventing it to boot

At my job we're in process of migrating my old Lenovo Laptop Thinkpad model L560 Laptop to Dell Latitude 5510 wiith Intel Core i5 vPro CPU and 256 Gb SSD Hard Drive.  The new laptops are generally fiine though they're not even a middle class computers and generally I prefer thinkpads. The sad thing out of this is our employee decided to migrate to Office 365 (again perhaps another stupid managerial decision out of an excel sheet wtih a balance to save some money … 

As you can imagine Office 365 is not really PCI Standards compliant and not secure since our data is stored in Microsoft cloud and theoretically Microsoft has and owns our data or could wipe loose the data if they want to. The other obvious security downside I've noticed with the new "Secure PCI complaint laptop" is the initial PC login screen which by default offers fingerprint authentication or the even worse  and even less secure face recognition, but obviosly everyhing becomes more and more crazy and people become less and less cautious for security if that would save money or centralize the data … In the name of security we completely waste security that is very dubious paradox I don't really understand but anyways, enough rant back to the main topic of this article is how to and I had to disable selinux?

As part of Migration I've used Microsoft OneDrive to copy old files from the Thinkpad to the Latitude (as on the old machine USB's are forbidden and I cannot copy over wiith a siimple USB driive, as well as II have no right to open the laptop and copy data from the Hard driive, and even if we had this right without breaking up some crazy company policy that will not be possible as the hard drive data on old laptop is encrypted, the funny thing is that the new laptop data comes encrypted and there is no something out of the box as BitDefender or McAffee incryption (once again, obviously our data security is a victim of some managarial decisions) …

2. OneDrive copy problems unable to sync some of the copied files to Onedrive

Anyways as the Old Laptop's security is quite paranoid and we're like Fort Nox, only port 80 and port 443 connections to the internet can be initiated to get around this harsh restrictions it was as simple to use a Virtualbox Virtual Machine. So on old laptop I've installed a CentOS 7 image which I used so far and I used one drive to copy my vbox .vdi image on the new laptop work machine.

The first head buml was the .vdi which seems to be prohibited to be copied to OneDrive, so to work around this I had to rename the origianl CentOS7.vdi to CentOS7.vdi-renamed on old laptop and once the data is in one drive copy my Vitualbox VM/ directory from one drive to the Dell Latitude machine and rename the .vdi-named towards .vdi as well as import it from the latest installed VirtualBox on the new machine.

3. Disable SELINUX from initial grub boot

So far so good but as usual happens with miigrations I've struck towards another blocker, the VM image once initiated to boot from Virtualbox badly crashed with some complains that selinux cannot be loaded.
Realizing CentOS 7 has the more or less meaningless Selinux, I've took the opportunity to disable SeLinux.

To do so I've booted the Kernel with Selinux disabled from GRUB2 loader prompt before Kernel and OS Userland boots.



I thought I need to type the information on the source in grub. What I did is very simple, on the Linux GRUB boot screen I've pressed

'e' keyboard letter

that brought the grub boot loader into edit mode.

Then I had to add selinux=0 on the edited selected kernel version, as shown in below screenshot:


Next to boot the Linux VM without Selinux enabled one time,  just had to press together

Ctrl+X then add selinux=0 on the edited selected kernel version, that should be added as shown in the screenshot somewhere after the line of

4. Permanently Disable Selinux on CentOS 7

Once I managed to boot Virtual Machine properly with Oracle Virtualbox, to permanently disabled selinux I had to:


Once booted into CentOS, to check the status of selinux run:


# sestatus
SELinux status:                 enabled
SELinuxfs mount:                /sys/fs/selinux
SELinux root directory:         /etc/selinux
Loaded policy name:             targeted
Current mode:                   enforcing
Mode from config file:          enforcing
Policy MLS status:              enabled
Policy deny_unknown status:     allowed
Max kernel policy version:      31


5. Disable SELinux one time with setenforce command

You can temporarily change the SELinux mode from targeted to permissive with the following command:


# setenforce 0

Next o permanently disable SELinux on your CentOS 7 next time the system boots, Open the /etc/selinux/config file and set the SELINUX mod parameter to disabled.

On CentOS 7 you can  edit the kernel parameters in /etc/default/grub (in the GRUB_CMDLINE_LINUX= key) and set selinux=0 so on next VM / PC boot we boot with a SELINUX disabled for example add   RUB_CMDLINE_LINUX=selinux=0 to the file then you have to regenerate your Grub config like this:

# grub2-mkconfig -o /etc/grub2.cfg
# grub2-mkconfig -o /etc/grub2-efi.cfg

Further on to disable SeLinux on OS level edit /etc/selinux

Default /etc/selinux/config with selinux enabled should look like so:

# This file controls the state of SELinux on the system.
# SELINUX= can take one of these three values:
#       enforcing – SELinux security policy is enforced.
#       permissive – SELinux prints warnings instead of enforcing.
#       disabled – No SELinux policy is loaded.
# SELINUXTYPE= can take one of these two values:
#       targeted – Targeted processes are protected,
#       mls – Multi Level Security protection.

To disable SeLinux modify the file to be something like:

# This file controls the state of SELinux on the system.
# SELINUX= can take one of these three values:
#       enforcing – SELinux security policy is enforced.
#       permissive – SELinux prints warnings instead of enforcing.
#       disabled – No SELinux policy is loaded.
# SELINUXTYPE= can take one of these two values:
#       targeted – Targeted processes are protected,
#       mls – Multi Level Security protection.

6. Check SELINUX status is disabled

# sestatus

SELinux status:                 disabled

So in this article shottly was explained shortly the fake security adopted by using Microsoft Cloud environment Offiice 365, my faced OneDrive copy issues (which prevented even my old laptop Virtual Machine to boot properly and the handy trick to rename the file that is unwilling to get copied from old PC towards m$ OneDrive as well as the grub trick to disable Selinux permanently from grub2.

Linux: How to set KVM Virtual Machine to autostart on system boot

July 15th, 2021


Recently I've written a short article on how to make auto boot OpenVZ container Virtual Machine if system gets rebooted as I had the task to do so in daily job as sysadmin.
Few days ago after some power outage in one of Frankfurt based Data Centers, some Rack tech equipment has been temporary powered of and once the electricity was up again, some Linux servers  running Kernel Based Virtualization ( KVM ) some of the virtual machines did not managed to automatically start up and we had to manually start them one by one.
To manually start each of the machines that did not start up had to do the trivial:

[root@hypervisor ~]# virsh list
 Id    Name                           State
 3     VM500                   running

[root@hypervisor ~]# virsh dominfo VM500
Id:             3
Name:           VM500
UUID:           82075903-a4ce-5ec0-a3d8-9ee83d85fc75
OS Type:        hvm
State:          running
CPU(s):         2
CPU time:       247407.9s
Max memory:     2097152 KiB
Used memory:    2097152 KiB
Persistent:     yes
Autostart:      disable
Managed save:   no
Security model: selinux
Security DOI:   0
Security label: system_u:system_r:svirt_t:s0:c447,c723 (permissive)

[root@hypervisor ~]# virsh start VM_domain_Name

Of course logcally to prevent future issues in case if Linux server gets suddenly rebooted due to whatever reason, we had to configure the machines in questions to automatically boot on OS system boot.

In some rare cases if above start command does not help you might want to check what is the status of libvirtd and investigate the logs in /var/log/libvirt/ i.e. /var/log/libvirt/libvirt.log

An alternative but more complicated way to set virtual machine to automatically start on boot is by using default location for automatic VM start just like OpenXEn has its /etc/xen/auto/ dirtory from where each soft symlinked VM configuration from /etc/xen/VM_name.cfg is started in KVM Hypervisor hosts to auto boot a certain vm you have to link /etc/libvirt/qemu/VM-to-autoboot-name.xml to /etc/libvirt/qemu/autostart/VM-to-autoboot-name.xml

[root@hypervisor ~]# systemctl status libvirtd
● libvirtd.service – Virtualization daemon
   Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; enabled; vendor preset: enabled)
   Active: active (running) since Tue 2021-06-29 10:21:30 CEST; 2 weeks 2 days ago
     Docs: man:libvirtd(8)
 Main PID: 1809 (libvirtd)
    Tasks: 22 (limit: 32768)
   CGroup: /system.slice/libvirtd.service
           ├─1809 /usr/sbin/libvirtd
           ├─2335 /usr/sbin/dnsmasq –conf-file=/var/lib/libvirt/dnsmasq/default.conf –leasefile-ro –dhcp-script=/us…
           ├─2336 /usr/sbin/dnsmasq –conf-file=/var/lib/libvirt/dnsmasq/default.conf –leasefile-ro –dhcp-script=/us…
           ├─2386 /usr/sbin/dnsmasq –conf-file=/var/lib/libvirt/dnsmasq/Host-Only.conf –leasefile-ro –dhcp-script=/…
           └─2387 /usr/sbin/dnsmasq –conf-file=/var/lib/libvirt/dnsmasq/Host-Only.conf –leasefile-ro –dhcp-script=/…

If for some reason libvirtd is not running or disabled state you will have to enable it with:

[root@hypervisor ~]# systemctl enable libvirtd

If the virtualization is running on some RPM based distribtuion OpenSuse whatever and libvirtd is controlled via chkconfig (redhat runlevel alternative system), you will have to :

[root@hypervisor ~]# chkconfig libvirtd on

Disabling KVM Virtual Machine from auto start on server boot

[root@hypervisor ~]# virsh autostart Debian10 –disable
Domain Debian10 unmarked as autostarted

7th of July The Feast of Saint Nedelya Kyriakia one of the most honored woman saints in Bulgarian Orthodox Church and few words of the history of Sofia Second biggest Cathedral Church St. Nedelya

July 8th, 2021


Saint Nedelya is a major Cathedral in Sofia Bulgaria dedicated to an early Christian saint Kyriaki (martyred year 289 AD). It is is a second biggest Cathedral Church in Bulgaria and a place where they serve the Holy Liturgy daily. The Patriarch and most notable spiritual leaders of the Bulgarian orthodox church do hold services there regularly.


Coffin with Holy Relics of Saint Stephan Urosh II Milutin in the St Nedelya Sofia Church right corner near alter wall

Saint Nedelya Church  is a beautiful peace of Christian art the Church is also known in XX-th century as Holy King (because the incorruptable Holy Relics of Sebian King Saint Stephan Urosh II ( Milutin ) are found in the Church).

Saint Nedelya Icon Arapovski Monastery Bulgaria

The fact that Saint Nedelya is the second Church by spiritual importance for Bulgaria is not a coincidence and this is related to the high veneration of saint martyr Nedelya (Kyriakia) Bulgarians had for the saint through the years especially in the Second Bulgarian kingdom during the reigh of King Asen's Dynasty (12-th 13-th century). The incorruptable Holy relics of the saint Kyriakia has been transferred to Trnovo (Tarnovo) the capital of Bulgaria at that time by saint Patriarch Euthymius (Evtimij) of Tarnovo (who was the last patriarch head of Bulgarian Orthodox Church during the Second Bulgarian Kingdom, right  before the fall of Bulgaria under the Turkish slavery (Yoke).

Saint Martyr Nedelya ( Kyriakia) died in July 7th 289 A.D.


Saint Nedelya Debrene Church iconographer Dicho Zograph from year 1844

Inspired by the great deed and the great grace received by receiving the incorruptable relics of the saint, saint Euthymius wrote a glorofication called "Praise to the Holy Great Martyr (Nedelya)". The Nedelya word meaning in Bulgarian Language is Sunday and is a literal translation from Greek's Kyriaky.


Saint Kyriaky dedicated Church, Istanbul Turkey

The veneration for saint Kyriaky has been quite common in medieval times one of the major Churches in Constantinople (today Istanbul) is dedicated also to saint Kyriaki.

According to Church tradition described by patriarch Evtimij, we know saint Nedelya has been born in Asia Minor and has been a child who has been long awaited kid that was gifted by God. Saint Kyriaki's was born in responce to her parents Dorotheus and Eusebia many fervent beseach prayers begging for a kid that will help Christ's salvation plan for the mankind.

 She was brought up in the truths of Christ from an early age.

At a very young age, she decided to dedicate her life to God. She happened to live at the time before Saint Constantine The Great when still the ligth of Christianity did not yet overcome the false believes of paganism in the time of the peresuction by emperor Diocletian. This was the time of persecution against Christian confessors and brutal violence against Christians – they were persecuted, imprisoned, exiled or forced to renounce their faith. Nedelya was thrown into prison and tortured, and her parents were exiled to the town of Miletin. The miraculous healing of her wounds, as well as her refusal to worship pagan idols, led the authorities to sentence her to death as they believed she is doing her wonderful healing by some strange whichcraft.

Kyriaki was tortured again by Apollonius, the successor of Hilarion. She was thrown into a fire, but the flames were extinguished, and then to wild beasts, but they became tame and gentle. Apollonius then sentenced her to death by the sword. As she was given a little time to pray, she asked God to receive her soul and to remember those who honoured her martyrdom. Upon completing her prayer, she rendered her soul to God before the sword was lowered on her head. Pious Christians took her relics and buried them. At the time of her death, she was 21 years old.[

At her place of death, after prayer, Sunday surrendered her spirit to God before the sentence is carried out exactly on her feast date (July 7, 289). For early Christians the day of death or martyrdom was considered the date of the real birthday for eternal life in heve. Nedelya died at the age of 22, as saint Patriarch Euthymius of Trnovo writes, "Dying in a short time, she fulfilled long years, because her Lord's soul was satisfied, purity – great enough, feats enough …"

The Second Biggest Bulgarian Cathedral is dedicated to saint Nedelya


Saint Nedelya Church, Sofia – Capital of Bulgaria

As many of the Churches in Bulgaria the history of Saint Nedelya's Church in Capital of Bulgaria, Sofia  goes back to distant X-th century and as many of the Churches of the time was most lilely laying on a stones and built of wood as Churches used to be built of that time. Today's architecture of the Church is of the XIX century.


The church became famous during the assassination attempt by Bulgarian Communist Party (BCP / BKP) on April 16, 1925 during the funeral of General Konstantin Georgiev, when it was destroyed. Then on this sad date for the Bulgarian history, 193 people mainly from the country's political and military elite were killed and about 500  bystander believers, who attended the liturgy were injured. The assault was perhaps the worst terrorist act in the history of Bulgaria, and at that time in the world. The aim of the temple blowing assault was to kill King Boris III, who was not in the Church at the time because he was slightly late for the service by the providence.

After this bloody terrorist act of the Bulgarian Communist Party, the church board of trustees assigned the architectural bureau "Vasilyov – Tsolov" (architect Ivan Vasilyov and architect Dimitar Tsolov) the restoration of the church. Renovation began in June 1927. By the spring of 1933, an almost new, huge central-domed temple was built with a length of 30 meters, a width of 15.50 meters and a height of the dome of 31 meters. The surviving two-row gilded iconostasis has been returned to the temple.

The church was solemnly consecrated again on April 7, 1933. The fresco decoration was made from 1971 to 1973 by an artistic team led by Nikolai Rostovtsev. Around 2015, the Church iconography has been fully restored and is amazingly beautiful worthy to see, if you happen to visit Bulgaria.

OpenVZ enable or disable auto start on Linux Hypervisor host boot for Virtual Machine containers

July 7th, 2021


To make OpenVZ / Virtuozzo Hypervisor servers and you are not sure whether your configured container virtual machines are configured to automatically boot on Linux Physical OS host boot in case of restart after patch update set or after unexpected shutdown due to Kernel / OS bug a hang or due to some electricity Power outage.

To check what is your current configuration for Virtual Environment on CentOS Linux you need to check inside /etc/sysconfig/vz-scripts/VEID.conf
You need to check the value for inside the file


To get the exact ID of "VEID.conf of the current openvz guest VM containers exec:

[root@openvz vz-scripts]# vzlist -a
       300         23 running     VirtualMachine1
       301         25 running     VirtualMachine2

[root@openvz ~]# cd /etc/sysconfig/vz-scripts
[root@gbapp2 vz-scripts]# pwd

[root@openvz vz-scripts]# grep -i ONBOOT 300.conf 301.conf

If you happen to have configured ONBOOT="no" you will need to the change to respective VEID.conf:

vi /etc/sysconfig/vz-scripts/VEID.conf

search for


and change to



OpenVZ server process tree. The colors of the virtual severs are indicated by colors.

OpenVZ Quick cheat sheet commands

This change will auto-start the VPS container next time the host Hypervisor node is rebooted.
If you happen to have daily work with OpenVZ legacy systems like I do you might find also useful the following OpenVZ Cheatsheet pdf document.

A miniature quick cheatsheet for OpenVZ Virtualion, in case if you are like me and you have to use various virtualization technologies and tend to forget is as below:

vzlist                               # List running instances
vzlist -a                            # List all instances


vzctl stop <instance>
vzctl start <instance>
vzctl status <instance>

vzctl exec <instance> <command>      # Run a command

vzctl enter <instance>               # Get console

vzyum <instance> install <package>   # Install a package

# Change properties
vzctl set <instance> –hostname <hostname> –save
vzctl set <instance> –ipadd <IP> –save
vzctl set <instance> –userpasswd root:<password> –save

If need to get more insight on how OpenVZ Virtualization does work on a low level and stretch out its possibilities, an old but useful document you might want to check is OpenVZ-Users-Guide PDF.

If you need it to hava e copy of it openvz_cheat_sheet.txt.

Fix Zabbix selinux caused permission issues on CentOS 7 Linux / cannot set resource limit: [13] Permission denied error solution

July 6th, 2021


If you have to install Zabbix client that has to communicate towards Zabbix server via a Zabbix Proxy you might be unpleasently surprised that it cannot cannot be start if the selinux mode is set to Enforcing.
Error message like on below screenshot will be displayed when starting proxy client with systemctl.


In the zabbix logs you will see error  messages such as:

"cannot set resource limit: [13] Permission denied, CentOS 7"


29085:20160730:062959.263 Starting Zabbix Agent [Test host]. Zabbix 3.0.4 (revision 61185).
29085:20160730:062959.263 **** Enabled features ****
29085:20160730:062959.263 IPv6 support: YES
29085:20160730:062959.263 TLS support: YES
29085:20160730:062959.263 **************************
29085:20160730:062959.263 using configuration file: /etc/zabbix/zabbix_agentd.conf
29085:20160730:062959.263 cannot set resource limit: [13] Permission denied
29085:20160730:062959.263 cannot disable core dump, exiting…



Next step to do is to check whether zabbix is listed in selinux's enabled modules to do so run:

[root@centos ~ ]# semodules -l

vhostmd    1.1.0
virt    1.5.0
vlock    1.2.0
vmtools    1.0.0
vmware    2.7.0
vnstatd    1.1.0
vpn    1.16.0
w3c    1.1.0
watchdog    1.8.0
wdmd    1.1.0
webadm    1.2.0
webalizer    1.13.0
wine    1.11.0
wireshark    2.4.0
xen    1.13.0
xguest    1.2.0
xserver    3.9.4
zabbix    1.6.0
zarafa    1.2.0
zebra    1.13.0
zoneminder    1.0.0
zosremote    1.2.0


[root@centos ~ ]# sestatus
# sestatusSELinux status:                 enabled
SELinuxfs mount:                /sys/fs/selinux
SELinux root directory:         /etc/selinux
Loaded policy name:             targeted
Current mode:                   enforcing
Mode from config file:          enforcing
Policy MLS status:              enabled

Policy deny_unknown status:     allowed
Max kernel policy version:      28

To get exact zabbix IDs that needs to be added as permissive for Selinux you can use ps -eZ like so:

[root@centos ~ ]# ps -eZ |grep -i zabbix
system_u:system_r:zabbix_agent_t:s0 1149 ?     00:00:00 zabbix_agentd
system_u:system_r:zabbix_agent_t:s0 1150 ?     00:04:28 zabbix_agentd
system_u:system_r:zabbix_agent_t:s0 1151 ?     00:00:00 zabbix_agentd
system_u:system_r:zabbix_agent_t:s0 1152 ?     00:00:00 zabbix_agentd
system_u:system_r:zabbix_agent_t:s0 1153 ?     00:00:00 zabbix_agentd
system_u:system_r:zabbix_agent_t:s0 1154 ?     02:21:46 zabbix_agentd

As you can see zabbix is enabled and hence selinux enforcing mode is preventing zabbix client / server to operate and communicate normally, hence to make it work we need to change zabbix agent and zabbix proxy to permissive mode.

Setting selinux for zabbix agent and zabbix proxy to permissive mode

If you don't have them installed you might neet the setroubleshoot setools, setools-console and policycoreutils-python rpms packs (if you have them installed skip this step).

[root@centos ~ ]# yum install setroubleshoot.x86_64 setools.x86_64 setools-console.x86_64 policycoreutils-python.x86_64

Then to add zabbix service to become permissive either run

[root@centos ~ ]# semanage permissive –add zabbix_t

[root@centos ~ ]# semanage permissive -a zabbix_agent_t

In some cases you might also need in case if just adding the permissive for zabbix_agent_t try also :

setsebool -P zabbix_can_network=1

Next try to start zabbox-proxy and zabbix-agent systemd services 

[root@centos ~ ]# systemctl start zabbix-proxy.service

[root@centos ~ ]# systemctl start zabbix-agent.service

Hopefully all should report fine with the service checking the status should show you something like:

[root@centos ~ ]# systemctl status zabbix-agent
● zabbix-agent.service – Zabbix Agent
   Loaded: loaded (/usr/lib/systemd/system/zabbix-agent.service; enabled; vendor preset: disabled)
   Active: active (running) since Thu 2021-06-24 07:47:42 CEST; 1 weeks 5 days ago
 Main PID: 1149 (zabbix_agentd)
   CGroup: /system.slice/zabbix-agent.service
           ├─1149 /usr/sbin/zabbix_agentd -c /etc/zabbix/zabbix_agentd.conf
           ├─1150 /usr/sbin/zabbix_agentd: collector [idle 1 sec]
           ├─1151 /usr/sbin/zabbix_agentd: listener #1 [waiting for connection]
           ├─1152 /usr/sbin/zabbix_agentd: listener #2 [waiting for connection]
           ├─1153 /usr/sbin/zabbix_agentd: listener #3 [waiting for connection]
           └─1154 /usr/sbin/zabbix_agentd: active checks #1 [idle 1 sec]

Check the Logs finally to make sure all is fine with zabbix being allowed by selinux.

[root@centos ~ ]# grep zabbix_proxy /var/log/audit/audit.log

[root@centos ~ ]# tail -n 100 /var/log/zabbix/zabbix_agentd.log

If no errors are in and you receive and you can visualize the usual zabbix collected CPU / Memory / Disk etc. values you're good, Enjoy ! 🙂

Linux: logrotate fix log file permissions on newly created logs after rotation

July 5th, 2021

fix logrotate permission issues of newly logrotated files, howto chown chmod logrotate linux logo

If you have to administer a bunch of Web or Application servers you will definetely end up with some machines that has some logrotate misconfiguration.

Perhaps the most common one sysadmin faces is when you have rotated webserver, proxy, mail server logs that gets gzipped with a date timestamp of the rotation and a brand new files is created by logrotate. Such a thing could be seen on various Linux distributions and even a more corporate prodcution ready Linux – es like CentOS and Fedora occasionally end up with issues caused by improperly created user / group permissions (usually root:root) of logrotate. 

The wrong permissions of usually normally logging to file by a service, happens when the log file will get filled (or matches some thresholds) configured by logrotate respective config, the log rotate mechanism will rename this file gzip / bzip it depending on how it is prepared to behave and opens a new one, however the newly produced log file will not have the read write permission which are necessery for the respective service because the service is not running as administrator (root), lets say there is a haproxy daemon running with user / group haproxy, haproxy, like it happeed today on one of our legacy CentOS 6.5 servers.

The sad result is /var/log/haproxy.log or whatever log file stays empty forever even though the service is normally working and you end up blind not seeing what's going on …

To solve the empty file due to logrotate dumping the original file permissions to a wrong one due to misconfiguration or a lack of special configuration it is as easy as setting up the logrotated file to write down the new rotated file to a specic user, this is done with a one line addition of code with a syntax like:

create mode owner group

Below is extract from logrotate man page (man logrotate)

Immediately after rotation (before the postrotate script is run) the log file is created (with the same name as the log file just rotated). mode specifies the mode for the log file in octal (the same as chmod(2)), owner specifies the user name who will own the log file, and group specifies the group the log file will belong to. Any of the log file attributes may be omitted, in which case those attributes for the new file will use the same values as the original log file for the omitted attributes. This option can be disabled using the nocreate option.

 Lets say you have following /etc/logrotate.d/haproxy configuration that is instructing logrotate to do the rotation and this will create empty file with root:root after rotate:

root@haproxy2:/etc/logrotate.d# cat haproxy

/var/log/haproxy.log {
    rotate 52

To make /var/log/haproxy.log be owned by haproxy user and group and chmod to certain owner permissions hence, do add inside the block something like: 


/var/log/haproxy.log {
        create 664 user group

i.e. :

/var/log/haproxy.log {
        create 644 haproxy hapoxy

To test the configuration do a logrotate config dry run do:

root@haproxy2:/etc/logrotate.d# logrotate -v -d -f /etc/logrotate.d/haproxy
WARNING: logrotate in debug mode does nothing except printing debug messages!  Consider using verbose mode (-v) instead if this is not what you want.

reading config file /etc/logrotate.d/haproxy
Reading state from file: /var/lib/logrotate/status
Allocating hash table for state file, size 64 entries
Creating new state
Creating new state
Creating new state
Creating new state
Creating new state
Creating new state
Creating new state
Creating new state
Creating new state
Creating new state
Creating new state
Creating new state


Handling 1 logs

rotating pattern: /var/log/haproxy.log  forced from command line (52 rotations)
empty log files are not rotated, old logs are removed
considering log /var/log/haproxy.log
  Now: 2021-07-05 21:51
  Last rotated at 2021-07-05 00:00
  log needs rotating
rotating log /var/log/haproxy.log, log->rotateCount is 52
dateext suffix '-20210705'
glob pattern '-[0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9]'
compressing log with: /bin/gzip

renaming /var/log/haproxy.log.8.gz to /var/log/haproxy.log.9.gz (rotatecount 52, logstart 1, i 8),
renaming /var/log/haproxy.log.7.gz to /var/log/haproxy.log.8.gz (rotatecount 52, logstart 1, i 7),
renaming /var/log/haproxy.log.6.gz to /var/log/haproxy.log.7.gz (rotatecount 52, logstart 1, i 6),
renaming /var/log/haproxy.log.5.gz to /var/log/haproxy.log.6.gz (rotatecount 52, logstart 1, i 5),
renaming /var/log/haproxy.log.4.gz to /var/log/haproxy.log.5.gz (rotatecount 52, logstart 1, i 4),
renaming /var/log/haproxy.log.3.gz to /var/log/haproxy.log.4.gz (rotatecount 52, logstart 1, i 3),
renaming /var/log/haproxy.log.2.gz to /var/log/haproxy.log.3.gz (rotatecount 52, logstart 1, i 2),
renaming /var/log/haproxy.log.1.gz to /var/log/haproxy.log.2.gz (rotatecount 52, logstart 1, i 1),
renaming /var/log/haproxy.log.0.gz to /var/log/haproxy.log.1.gz (rotatecount 52, logstart 1, i 0),
log /var/log/haproxy.log.53.gz doesn't exist — won't try to dispose of it
renaming /var/log/haproxy.log to /var/log/haproxy.log.1
creating new /var/log/haproxy.log mode = 0644 uid = 106 gid = 112
running postrotate script
running script with arg /var/log/haproxy.log: "



root@haproxy2:/etc/logrotate.d# grep -Ei '106|112' /etc/passwd

You do it for any other service respectively by editting whatever /etc/logrotate.d/file, lets say postfix's /var/log/maillog should be owned with 644 by postfix:postfix.

# cat /etc/logrotate/postfix
/var/log/maillog {
        create 664 postfix postfix

The names of the Twelve apostles of Christ – Feast of the Twelve Glorious and Primal Apostles in Eastern Orthodox Church (30th of June)

June 30th, 2021

Jesus and his Twelve Apostles, fresco with the Chi-Rho symbol ☧, Catacombs of Domitilla, Rome

One day after the June 29 the Feast of The Glorious and First among Apostles Peter and Paul  on 30th of June according to so called new calendar in the Eastern Orthodox Church comes, the remembrace of Feast of the gathering of 12 Glorious apostles (Σύναξη των Αγίων Δώδεκα Αποστόλων).


The Secret Supper (Christ and the 12 Apostles iconographer Simon Ushakov y. 1685 (Jude the Iscariot the traitor without a halo)

"The names of the 12 Holy Apostles are: Simon (called Peter), Andrew his brother, Jacob the Zabedee and John his brother, Philip and Bartholomew, Thomas and Mathew (tax collectors), James, son of Alphaeus and Levi called (Thadeus), Simon The Canonite and Jude the Iscariot who has betrayed Christ"

(Gospel of Mathew 10:2-4)


13 When morning came, he called his disciples to him and chose twelve of them, whom he also designated apostles: 14 Simon (whom he named Peter), his brother Andrew, James, John, Philip, Bartholomew, 15 Matthew, Thomas, James son of Alphaeus, Simon who was called the Zealot, 16 Judas son of James, and Judas Iscariot, who became a traitor.

(Luke 6:13-16)

15 And in those days Peter stood up in the midst of the disciples, and said, (the number of names together were about an hundred and twenty,)

16 Men and brethren, this scripture must needs have been fulfilled, which the Holy Ghost by the mouth of David spake before concerning Judas, which was guide to them that took Jesus.

17 For he was numbered with us, and had obtained part of this ministry.

18 Now this man purchased a field with the reward of iniquity; and falling headlong, he burst asunder in the midst, and all his bowels gushed out.

19 And it was known unto all the dwellers at Jerusalem; insomuch as that field is called in their proper tongue, Aceldama, that is to say, The field of blood.

20 For it is written in the book of Psalms, Let his habitation be desolate, and let no man dwell therein: and his bishoprick let another take.

21 Wherefore of these men which have companied with us all the time that the Lord Jesus went in and out among us, (Acts 1:15-26)


The Synaxis of the Twelve Apostles. Russian, 14th century, Moscow Museum.

"Jesus had other desciples as well that were seventeen and other circles of desciples around each of the pupils, however they have alwasys been considered less venerable as they did not been so close to Christ and did not understand so well the mysterios of Christ's teaching and did not persevere as mcuh as the twelve and the seventeen of desciples. Those had been been distinguished among the King, those who have been the closest people to the Teacher" (Saint John Chrysostomos)

In Constantinople Saint King Constantine ( y. 274 – 337 ), has built a famous Church dedicated to the 12 Apostles. In historian documents there is data for a first time the feast is celebrated in the V-th century.

While the memory of each apostle has a separate day in the Church calendar yearly circle, they 12 apostles are sharing the same honor, because the Holy Scriptures and the Tradition glorifious their high efforts for building the Church on top of the corner stone that is Jesus Christ himsef and for their perseverance to accept martyrdom for Christ, thus to accent this they're is this special feast the Gathering of the 12 Glorious Apostles on 30th of June. As the Holy Scriptures says they're a friends of God (John 15:14), and when the Son of Man (Jesus) sits on the glory of his power, they all are to sit on 12 thrones, to judge the 12 Hebrew tribes (Mathew 19:28). 

In first centuries the Church has been feasting all the apostles together, Later she has included saint Apostle Paul, again the full list of names of the apostles are as follows:

1. Saint Apostle Peter the First Called (commemorated 29 June and 16 of January)

2. Saint apostle Andrew the First Called – as has been called by Christ together with Peter (30 November)

3.  Saint Jacob the Zebedee (30 April)

4. Saint Apostle John the Zebedee – the evangelist (26 September and 8 May)

5. Saint Apostle Philip (14 November)

6. Saint apostle Bartholomew or Nathanael (11 June and 25 August)

7. Saint apostle Thomas (6 October)

8. Saint apostle Mathew – evangelist (16 November)

9. Saint Apostle Jacob – son of Alpheus 9 October)

10. Saint Apostle Jude – fleshly brother of Christ (son of Joseph), called also Thadeus and Levi (19 June)

11. Saint Apostle Mathew (Mathias) (9 August)

12. Saint Apostle Paul  (Paul of Tarsus) (29 June)

The Church books define the feast day as the "Gathering of the Twelve", because this number of 12 apostles is initial and depics Christ essence of Completeness (as he is All in everything) Mathew (10:1-5)


ASCII Art studio – A powerful ASCII art editor for Windows / Playscii a cool looking text editor for Linux

June 28th, 2021

This post is just informative for Text Geeks who are in love with ASCII Art, it is a bit of rant as I will say nothing new, but I thought it might be of interest to some console maniac out there 🙂

ascii art studio aas program windows xp professional drawing program screenshot

While checking stuff on Internet I've stumbled on interesting ASCII arts freak software – >ASCII Art Studio. ASCII Art Studio is unfortunately needs licensing is not Free Software. But anyways, for anyone willing to draw pro ASCII art pictures it is a must see. Check it out;

Isn't it like a Plain Text pro Photoshop ? 🙂 Its a pity we don't have a Linux / BSD Release of this wonderful piece of software. I've tried with WINE (Windows Emulator) on Linux to make the Ascii Art Studio work but that was a fail. It seems only way to make it work is have Windows as a worst case install a Virtual Machine with VirtualBox / Vmware and run it inside if you don't have a Windows PC at hand.

Of course there are stuff on Linux to ascii art edit you can use if you want to have a native software to edit ASCIIs such as Playscii. Unfortunately Playscii is not an easy one to install and the software doesn't have a prepared rpm or deb binary you can easily roll on the OS and you have to manually build all required python modules and have a working version of python3 to be able to make it work.

I did not have much time to test to install it and since I faced issues with plascii install I just abandoned it. If some geek has some more time anyways I guess it is worse to give it a try below is 2 screenshots from PLAYSCII official download page. 


As you see authors of the open source playscii whose source is available via github choose to have an amazing looking ascii art text menus, though for daily ASCII art editing it is perhaps much more complicated to use than the simlistic ASCII Art Studio


There is other stuff for Linux to do ASCII Art files text edit like:
JaVE (this one I don't personally like because it is Java Based),  Ascii Art Maker or Pablow Draw Linux (unfortunately this 2 ones are proprietary).

Stop haproxy log requests to /var/log/messages / Disable haproxy double logging

June 25th, 2021


On a CentOS Linux release 7.9.2009 (Core) I've running haproxies on two KVM virtual machines that are configured in a High Avaialability cluster with Corosync and Pacemaker, the machines are inherited from another admin (I did not install the servers hardware) and OS but have been received the system for support.
The old sysadmins seems to not care much about the system so they've left the haprxoy with Double logging one time under separate configured log in /var/log/haproxy/haproxyprod.log and each Haproxy TCP mode flown request has been double logged to /var/log/messages as well. As you can guess this shouldn't be so because we're wasting Hard drive space so to fix that I had to stop haproxy doble logging to /var/log/messages.

The logging is done under a separate local pointer local6 the /etc/haproxy/haproxyprod.cfg goes as follows:

[root@haproxy01 ~]# cat /etc/haproxy/haproxyprod.cfg

    # log <address> [len ] [max level [min level]]
    log local6 debug


The logging is handled by rsyslog via the local6, so obviously to keep out the logging from /var/log/messages
The logging to the separate log file configuration in rsyslog is as follows:

local6.*                                                /var/log/haproxy/haproxyprod.log

It turned to be really easy to prevent haproxy get its requests log to /var/log/messages all I had to change is under /etc/rsyslogd.conf

local6.none config has to be placed for /var/log/messages the full line configuration in /etc/rsyslog.conf that stopped double logging is:

# Don't log private authentication messages!
*.info;mail.none;authpriv.none;cron.none;local5.none;local6.none                /var/log/messages