Posts Tagged ‘Nothing’

Find when cron.daily cron.weekly and cron.monthly run on Redhat / CentOS / Debian Linux and systemd-timers

Wednesday, March 25th, 2020

Find-when-cron.daily-cron.monthly-cron.weekly-run-on-Redhat-CentOS-Debian-SuSE-SLES-Linux-cron-logo

The problem – Apache restart at random times


I've noticed today something that is occuring for quite some time but was out of my scope for quite long as I'm not directly involved in our Alert monitoring at my daily job as sys admin. Interestingly an Apache HTTPD webserver is triggering alarm twice a day for a short downtime that lasts for 9 seconds.

I've decided to investigate what is triggering WebServer restart in such random time and investigated on the system for any background running scripts as well as reviewed the system logs. As I couldn't find nothing there the only logical place to check was cron jobs.
The usual
 

crontab -u root -l


Had no configured cron jobbed scripts so I digged further to check whether there isn't cron jobs records for a script that is triggering the reload of Apache in /etc/crontab /var/spool/cron/root and /var/spool/cron/httpd.
Nothing was found there and hence as there was no anacron service running but /usr/sbin/crond the other expected place to look up for a trigger even was /etc/cron*

1. Configured default cron execution times, every day, every hour every month

# ls -ld /etc/cron.*
drwxr-xr-x 2 root root 4096 feb 27 10:54 /etc/cron.d/
drwxr-xr-x 2 root root 4096 dec 27 10:55 /etc/cron.daily/
drwxr-xr-x 2 root root 4096 dec  7 23:04 /etc/cron.hourly/
drwxr-xr-x 2 root root 4096 dec  7 23:04 /etc/cron.monthly/
drwxr-xr-x 2 root root 4096 dec  7 23:04 /etc/cron.weekly/

After a look up to each of above directories, finally I found the very expected logrorate shell script set to execute from /etc/cron.daily/logrotate and inside it I've found after the log files were set to be gzipped and moved to execute WebServer restart with:

systemctl reload httpd 

My first reaction was to ponder seriously why the script is invoking systemctl reload httpd instead of the good oldschool

apachectl -k graceful

But it seems on Redhat and CentOS since RHEL / CentOS version 6.X onwards systemctl reload httpd is supposed to be identical and a substitute for apachectl -k graceful.
Okay the craziness of innovation continued as obviously the reload was causing a Downtime to be visible in the Zabbix HTTPD port Monitoring graph …
Now as the problem was identified the other logical question poped up how to find out what is the exact timing scheduled to run the script in that unusual random times each time ??
 

2. Find out cron scripts timing Redhat / CentOS / Fedora / SLES

/etc/cron.{daily,monthly,weekly} placed scripts's execution method has changed over the years, causing a chaos just like many Linux standard things we know due to the inclusion of systemd and some other additional weird OS design changes. The result is the result explained above scripts are running at a strange unexpeted times … one thing that was intruduced was anacron – which is also executing commands periodically with a different preset frequency. However it is considered more thrustworhty by crond daemon, because anacron does not assume the machine is continuosly running and if the machine is down due to a shutdown or a failure (if it is a Virtual Machine) or simply a crond dies out, some cronjob necessery for overall set environment or application might not run, what anacron guarantees is even though that and even if crond is in unworking defunct state, the preset scheduled scripts will still be served.
anacron's default file location is in /etc/anacrontab.

A standard /etc/anacrontab looks like so:
 

[root@centos ~]:# cat /etc/anacrontab
# /etc/anacrontab: configuration file for anacron
 
# See anacron(8) and anacrontab(5) for details.
 
SHELL=/bin/sh
PATH=/sbin:/bin:/usr/sbin:/usr/bin
MAILTO=root
# the maximal random delay added to the base delay of the jobs
RANDOM_DELAY=45
# the jobs will be started during the following hours only
START_HOURS_RANGE=3-22
 
#period in days   delay in minutes   job-identifier   command
1    5    cron.daily        nice run-parts /etc/cron.daily
7    25    cron.weekly        nice run-parts /etc/cron.weekly
@monthly 45    cron.monthly        nice run-parts /etc/cron.monthly

START_HOURS_RANGE : The START_HOURS_RANGE variable sets the time frame, when the job could started. 
The jobs will start during the 3-22 (3AM-10PM) hours only.

  • cron.daily will run at 3:05 (After Midnight) A.M. i.e. run once a day at 3:05AM.
  • cron.weekly will run at 3:25 AM i.e. run once a week at 3:25AM.
  • cron.monthly will run at 3:45 AM i.e. run once a month at 3:45AM.

If the RANDOM_DELAY env var. is set, a random value between 0 and RANDOM_DELAY minutes will be added to the start up delay of anacron served jobs. 
For instance RANDOM_DELAY equels 45 would therefore add, randomly, between 0 and 45 minutes to the user defined delay. 

Delay will be 5 minutes + RANDOM_DELAY for cron.daily for above cron.daily, cron.weekly, cron.monthly config records, i.e. 05:01 + 0-45 minutes

A full detailed explanation on automating system tasks on Redhat Enterprise Linux is worthy reading here.

!!! Note !!! that listed jobs will be running in queue. After one finish, then next will start.
 

3. SuSE Enterprise Linux cron jobs not running at desired times why?


in SuSE it is much more complicated to have a right timing for standard default cron jobs that comes preinstalled with a service 

In older SLES release /etc/crontab looked like so:

SHELL=/bin/bash
PATH=/sbin:/bin:/usr/sbin:/usr/bin
MAILTO=root
HOME=/

# run-parts
01 * * * * root run-parts /etc/cron.hourly
02 4 * * * root run-parts /etc/cron.daily
22 4 * * 0 root run-parts /etc/cron.weekly
42 4 1 * * root run-parts /etc/cron.monthly


As time of writting article it looks like:

SHELL=/bin/sh
PATH=/usr/bin:/usr/sbin:/sbin:/bin:/usr/lib/news/bin
MAILTO=root
#
# check scripts in cron.hourly, cron.daily, cron.weekly, and cron.monthly
#
-*/15 * * * *   root  test -x /usr/lib/cron/run-crons && /usr/lib/cron/run-crons >/dev/null 2>&1


This runs any scripts placed in /etc/cron.{hourly, daily, weekly, monthly} but it may not run them when you expect them to run. 
/usr/lib/cron/run-crons compares the current time to the /var/spool/cron/lastrun/cron.{time} file to determine if those jobs need to be run.

For hourly, it checks if the current time is greater than (or exactly) 60 minutes past the timestamp of the /var/spool/cron/lastrun/cron.hourly file.

For weekly, it checks if the current time is greater than (or exactly) 10080 minutes past the timestamp of the /var/spool/cron/lastrun/cron.weekly file.

Monthly uses a caclucation to check the time difference, but is the same type of check to see if it has been one month after the last run.

Daily has a couple variations available – By default it checks if it is more than or exactly 1440 minutes since lastrun.
If DAILY_TIME is set in the /etc/sysconfig/cron file (again a suse specific innovation), then that is the time (within 15minutes) when daily will run.

For systems that are powered off at DAILY_TIME, daily tasks will run at the DAILY_TIME, unless it has been more than x days, if it is, they run at the next running of run-crons. (default 7days, can set shorter time in /etc/sysconfig/cron.)
Because of these changes, the first time you place a job in one of the /etc/cron.{time} directories, it will run the next time run-crons runs, which is at every 15mins (xx:00, xx:15, xx:30, xx:45) and that time will be the lastrun, and become the normal schedule for future runs. Note that there is the potential that your schedules will begin drift by 15minute increments.

As you see this is very complicated stuff and since God is in the simplicity it is much better to just not use /etc/cron.* for whatever scripts and manually schedule each of the system cron jobs and custom scripts with cron at specific times.


4. Debian Linux time start schedule for cron.daily / cron.monthly / cron.weekly timing

As the last many years many of the servers I've managed were running Debian GNU / Linux, my first place to check was /etc/crontab which is the standard cronjobs file that is setting the { daily , monthly , weekly crons } 

 debian:~# ls -ld /etc/cron.*
drwxr-xr-x 2 root root 4096 фев 27 10:54 /etc/cron.d/
drwxr-xr-x 2 root root 4096 фев 27 10:55 /etc/cron.daily/
drwxr-xr-x 2 root root 4096 дек  7 23:04 /etc/cron.hourly/
drwxr-xr-x 2 root root 4096 дек  7 23:04 /etc/cron.monthly/
drwxr-xr-x 2 root root 4096 дек  7 23:04 /etc/cron.weekly/

debian:~# cat /etc/crontab 
# /etc/crontab: system-wide crontab
# Unlike any other crontab you don't have to run the `crontab'
# command to install the new version when you edit this file
# and files in /etc/cron.d. These files also have username fields,
# that none of the other crontabs do.

SHELL=/bin/sh
PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin# Example of job definition:
# .—————- minute (0 – 59)
# |  .————- hour (0 – 23)
# |  |  .———- day of month (1 – 31)
# |  |  |  .——- month (1 – 12) OR jan,feb,mar,apr …
# |  |  |  |  .—- day of week (0 – 6) (Sunday=0 or 7) OR sun,mon,tue,wed,thu,fri,sat
# |  |  |  |  |
# *  *  *  *  * user-name command to be executed
17 *    * * *    root    cd / && run-parts –report /etc/cron.hourly
25 6    * * *    root    test -x /usr/sbin/anacron || ( cd / && run-parts –report /etc/cron.daily )
47 6    * * 7    root    test -x /usr/sbin/anacron || ( cd / && run-parts –report /etc/cron.weekly )
52 6    1 * *    root    test -x /usr/sbin/anacron || ( cd / && run-parts –report /etc/cron.monthly )

What above does is:

– Run cron.hourly once at every hour at 1:17 am
– Run cron.daily once at every day at 6:25 am.
– Run cron.weekly once at every day at 6:47 am.
– Run cron.monthly once at every day at 6:42 am.

As you can see if anacron is present on the system it is run via it otherwise it is run via run-parts binary command which is reading and executing one by one all scripts insude /etc/cron.hourly, /etc/cron.weekly , /etc/cron.mothly

anacron – few more words

Anacron is the canonical way to run at least the jobs from /etc/cron.{daily,weekly,monthly) after startup, even when their execution was missed because the system was not running at the given time. Anacron does not handle any cron jobs from /etc/cron.d, so any package that wants its /etc/cron.d cronjob being executed by anacron needs to take special measures.

If anacron is installed, regular processing of the /etc/cron.d{daily,weekly,monthly} is omitted by code in /etc/crontab but handled by anacron via /etc/anacrontab. Anacron's execution of these job lists has changed multiple times in the past:

debian:~# cat /etc/anacrontab 
# /etc/anacrontab: configuration file for anacron

# See anacron(8) and anacrontab(5) for details.

SHELL=/bin/sh
PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
HOME=/root
LOGNAME=root

# These replace cron's entries
1    5    cron.daily    run-parts –report /etc/cron.daily
7    10    cron.weekly    run-parts –report /etc/cron.weekly
@monthly    15    cron.monthly    run-parts –report /etc/cron.monthly

In wheezy and earlier, anacron is executed via init script on startup and via /etc/cron.d at 07:30. This causes the jobs to be run in order, if scheduled, beginning at 07:35. If the system is rebooted between midnight and 07:35, the jobs run after five minutes of uptime.
In stretch, anacron is executed via a systemd timer every hour, including the night hours. This causes the jobs to be run in order, if scheduled, beween midnight and 01:00, which is a significant change to the previous behavior.
In buster, anacron is executed via a systemd timer every hour with the exception of midnight to 07:00 where anacron is not invoked. This brings back a bit of the old timing, with the jobs to be run in order, if scheduled, beween 07:00 and 08:00. Since anacron is also invoked once at system startup, a reboot between midnight and 08:00 also causes the jobs to be scheduled after five minutes of uptime.
anacron also didn't have an upstream release in nearly two decades and is also currently orphaned in Debian.

As of 2019-07 (right after buster's release) it is planned to have cron and anacron replaced by cronie.

cronie – Cronie was forked by Red Hat from ISC Cron 4.1 in 2007, is the default cron implementation in Fedora and Red Hat Enterprise Linux at least since Version 6. cronie seems to have an acive upstream, but is currently missing some of the things that Debian has added to vixie cron over the years. With the finishing of cron's conversion to quilt (3.0), effort can begin to add the Debian extensions to Vixie cron to cronie.

Because cronie doesn't have all the Debian extensions yet, it is not yet suitable as a cron replacement, so it is not in Debian.
 

5. systemd-timers – The new crazy systemd stuff for script system job scheduling


Timers are systemd unit files with a suffix of .timer. systemd-timers was introduced with systemd so older Linux OS-es does not have it.
 Timers are like other unit configuration files and are loaded from the same paths but include a [Timer] section which defines when and how the timer activates. Timers are defined as one of two types:

 

  • Realtime timers (a.k.a. wallclock timers) activate on a calendar event, the same way that cronjobs do. The option OnCalendar= is used to define them.
  • Monotonic timers activate after a time span relative to a varying starting point. They stop if the computer is temporarily suspended or shut down. There are number of different monotonic timers but all have the form: OnTypeSec=. Common monotonic timers include OnBootSec and OnActiveSec.

    For each .timer file, a matching .service file exists (e.g. foo.timer and foo.service). The .timer file activates and controls the .service file. The .service does not require an [Install] section as it is the timer units that are enabled. If necessary, it is possible to control a differently-named unit using the Unit= option in the timer’s [Timer] section.

    systemd-timers is a complex stuff and I'll not get into much details but the idea was to give awareness of its existence for more info check its manual man systemd.timer

Its most basic use is to list all configured systemd.timers, below is from my home Debian laptop
 

debian:~# systemctl list-timers –all
NEXT                         LEFT         LAST                         PASSED       UNIT                         ACTIVATES
Tue 2020-03-24 23:33:58 EET  18s left     Tue 2020-03-24 23:31:28 EET  2min 11s ago laptop-mode.timer            lmt-poll.service
Tue 2020-03-24 23:39:00 EET  5min left    Tue 2020-03-24 23:09:01 EET  24min ago    phpsessionclean.timer        phpsessionclean.service
Wed 2020-03-25 00:00:00 EET  26min left   Tue 2020-03-24 00:00:01 EET  23h ago      logrotate.timer              logrotate.service
Wed 2020-03-25 00:00:00 EET  26min left   Tue 2020-03-24 00:00:01 EET  23h ago      man-db.timer                 man-db.service
Wed 2020-03-25 02:38:42 EET  3h 5min left Tue 2020-03-24 13:02:01 EET  10h ago      apt-daily.timer              apt-daily.service
Wed 2020-03-25 06:13:02 EET  6h left      Tue 2020-03-24 08:48:20 EET  14h ago      apt-daily-upgrade.timer      apt-daily-upgrade.service
Wed 2020-03-25 07:31:57 EET  7h left      Tue 2020-03-24 23:30:28 EET  3min 11s ago anacron.timer                anacron.service
Wed 2020-03-25 17:56:01 EET  18h left     Tue 2020-03-24 17:56:01 EET  5h 37min ago systemd-tmpfiles-clean.timer systemd-tmpfiles-clean.service

8 timers listed.


N ! B! If a timer gets out of sync, it may help to delete its stamp-* file in /var/lib/systemd/timers (or ~/.local/share/systemd/ in case of user timers). These are zero length files which mark the last time each timer was run. If deleted, they will be reconstructed on the next start of their timer.

Summary

In this article, I've shortly explain logic behind debugging weird restart events etc. of Linux configured services such as Apache due to configured scripts set to run with a predefined scheduled job timing. I shortly explained on how to figure out why the preset default install configured cron jobs such as logrorate – the service that is doing system logs archiving and nulling run at a certain time. I shortly explained the mechanism behind cron.{daily, monthy, weekly} and its execution via anacron – runner program similar to crond that never misses to run a scheduled job even if a system downtime occurs due to a crashed Docker container etc. run-parts command's use was shortly explained. A short look at systemd.timers was made which is now essential part of almost every new Linux release and often used by system scripts for scheduling time based maintainance tasks.

Saint George’s day in an Elder – Spiritual father Georgi (91 years old Priest) in Jeglarci’s Village Bulgaria

Friday, May 9th, 2014

https://pc-freak.net/images/otec-father-Georgi-Jeglarci-village-spiritual-elder-in-Bulgaria

This year on 6th of May – saint George's day Church feast and army celebration in Bulgaria I had the blessing to be in a small village with 868 citizens – Jiglarci (Jeglarci).
Jeglarci is situated about 40 km from Dobrich. Father Georgi from Jiglarci is a well known priest in Dobrich region. He is spiritual father of many priests, monks and nuns here in Bulgaria. This is the 3rd time I'm visiting Jiglarci one time I was on Great and Holy Friday – the day on which the Lord Jesus Christ was crucified and one time I was a few months ago with some brothers and sisters from Holy Trinity Church in Dobrich. This time I had the blessing to go fr. Georgi with my wife Svetlana with Russian family from moscow Mihail and Mariana, and Denica (a sister from Church in Dobrich).

Jiglarci-Cyrkva-Church-building-where-father-Georgi-from-Jiglarci-serves

The Church saint George in Jeglarci village

Each time I visit father Georgi I have the blessing to see and hear a living proof of God's existence. Father's Georgi from Jeglarci is famous all around Bulgaria for being one of the spiritual elders of Bulgaria. He is now 91 years old but even though his age  continues his service for God (serves Holy Liturgy every day during great Lent!), continue to preach and accept dozens of people almost daily looking for spiritual advice, spiritual help, confession, or questions on how to deal with life hardship situations.
Father Georgi is known in the world under the secular name Georgi Stoyanov Peev his life is full of miracles, interesting events and wondrous facts. In communism times of atheism and Orthodox Christian faith persecutions, father Georgi was one of the many priests who underwent tortures and persecutions for his faith in Christ. Because of his firm faith of zealous priest, the Lord endowed the fr. with great spiritual gifts. In short I will mention some facts about fr. Georgi From Jeglarci life as the father is an example of a living saint, very much like another Bulgarian Church Elder (Dijado) Dobri from Baylovo.

Father Georgi has been nurtured with Christian virtues since his childhood – his aunt (sister of his father) was a nun. By his own words, "Since a child, the joy of my life was in faith". Since his youth years his faith was strong and because of that God has helped him in numerous times. Fr. Georgi had 6 children 3 sons and 3 daughters. All of his sons choose the way of priesthood and are now priests in the Bulgarian Orthodox Church. His nephew fr. Stoyan is also a priest in Holy Trinity Orthodox Church in Dobrich. The father become priest while being 43 years old, by studying in seminary after feeing the call of God and need for firm believers and mass disbelieve in atheistic communist times. In seminary father Georgi studied together with his son. To be able to support himself and his family financially, he worked all kind of hard labour  (sand mining near his village). His all life was labor and prayer in all his free time during studing he learned the church services, readhing the living of saints and holy bible.

Thanks to the house whom he turned into a small chapel almost 20 people become priests later in Bulgarian Orthodox Church. In his priesthood fr. Georgi was among the minority which opposed the ungodly communistic regime, he rejected to comply with communist desires to close the Church in Jeglarci and as a responce to their closure opened as a Church his own house. He was questioned and asked for reports being increminated from local Communist authorities, threatened with death and called in police stations many times because of his refusal to stop his service in Church and preaching the Gospel.

Here is a story of fr. Georgi's youth:

"Our Lord as a Good Father, not only listens our prayers but also reads in the hearts. In 1953 my brother Atanas was a soldier. We received a letter, that soldiers will be dismissed in January next year, this was a very long time. It was st. Dimiter's feast and I wanted my brother to be home for Christmas. At night I prayed the Lord, simple and by all my heart: "Lord for you nothing is hard or impossible. I beg you – in one way or another make it possible, that my brother Atanas to come home earlier.

I had a strong faith in God. My faith in God was so strong that I was feeling like being able to fly. In 3 days later only, when I saw my brother Atanas on the front door, my legs started shaking and I sat down, started crying and in my thoughts started giving thanks to the Lord, "Lord, Lord I'm a big sinner and what you've done for me the sinner …
In a short while, my brother told me how in a human way everything ordered in a way that he was able to come home, 3 days after my prayer. When I received the letter on St. Dimiter's day I've prayed, the prayer was heard and God moved. The human mind is a spiritual substance connected with God. God orders things and we in a human way receive them. On the next day after st. Dimiter's feast the coy was gathered and the commander said, "Atanas Stoyanov Peichev, make 5 steps forward and start Marching!". Together with another man commander sent them in hospital, where a doctor had to inspect their health. The two soldiers took their luggate, foreseeing that they might be kept in hospital. The health check prooved they're healthy. There were 4 months until service completion but in hospital the doctor told them – "Come on go home. Your service is over". – Do you see how in a human way the things ordered. Disbelievers would say it was a coincidence but believers knows the Lord hears our prayers, when they're prayed by our whole being and with pure heart."

fr-Georgi-Jeglarci-elder-of-Dobrich-Bulgaria-3

Saint George Church in Jeglarci – Altar and Dveri

Another of his stories is connected with fasting:

"The fasting of the body is a big power. It does clean up the body and draws us near God. The fasting gives a big power. I was hindered in many ways, disbelieving authorities in the village has done me many attempts to do me evil but the Lord has saved me. Didn't allowed them nothing bad to happen to me. He grant me powers, spirit to speak the truth and to not resign from righteousness. But I leave fasting …

Fasting and Prayer are lights leading to God. I was warned 3 times by our Lord about fasting significance. When we were living in North Dobrudja, following thing happened to me: " I was 15 years old. Near our village Karamankyoij a river rich of fish was flowing. One day my bigger brother cought a lot of fish from the white one. My father and all of us was tempted, we wanted eating and it was during the Great Lent. My father said, "Okay prepare the fish and let us eat, God will forgive us?" Notice he said that in faith! apostol Paul writes, 'who eat eats for the Lord and who doesn't eat- also doesn't eat for the Lord'". We have done so as well, we were big family 7-8 children,  grandma, grandpa, my father, mother. Some eat others doesn't. I was in the group of those who ate. We ate and we went to bed. A sudden pain in stomach came … hard to explain. Nothing helps, a thought came to my mind: "Lord forgive me, I will no longer eat fish during fasting". The pain immediately disappeared I immediately got well.

But unfortunately I was weak. On the other day my brother prepared fish again and invited me.

– Genyo, come lets eat.
– I suffered yesterday – I don't want.
– Don't worry your pains was from something else not from the fish, come eat I beg you.

I was tempted and ate. We played until night time and all was well with me. In night, I fall asleep, but suddenly the pain come again, 3 times more painful. I thought I am dying, I was all sweating. My mother and grandma tried to heal me but nothing helped. Then I turned with a prayer to the Lord: "Please Lord forgive me this time also." And out of a sudden I hear a noise like from many waters coming like from heaven. Something went through me and took away the pain. There was a flash in front of my eyes. Do you see how merciful is the Lord!"

Among the many spiritual gifts of fr. Georgi is the gift of "foreseeing" (thoughts and deeds, and future). Many people who visited him later narrated the father told them things which helped them improve their spiritual life. During my first visit of the father I had the possibility to raise few questions on my spiritual life, his answers was a proove for myself that the fr. has truly the gift of sagacity.
Father Georgi had many dreams during his life and many of his dreams were prophetic about future events to come. By his own words often God spoke to him in "dreams and visions". A very notable gift he has is the gift of humility and pure Godly love. He speaks in his stories about everyone including of many who tried to do him evil with profound love and forgiveness.

fr-Georgi-Jeglarci-elder-of-Dobrich-Bulgaria-2

By prayers of father Georgi many miracles has happened, he openly speaks of this miracles, believing that through this the weak in faith are strengthened. The father says "Even if the whole earth is convincing me to deny what I saw and experienced with my spiritual eyes I will not forsake.

His humility is sincere, he says about himself: "I am just negligible mot and the miracle is not in human deed but in God's. God uses a lot simple people and through them creates miracle to edify "the smart", those which is of God is being remembered like it happened today.  Wondrous are God's deeds!"

fr-Georgi-Jeglarci-elder-of-Dobrich-Bulgaria-1
 

"The Spiritual deed is very hard. I have worked many kind of works, when you get tired you take a rest, and for the spirit there is no rest.
What to say, how to behave, how to determine the spiritual in you, to be vigilant for your food and for body pureness for pureness of your thoughts and your heart … And of course the Prayer! This is a hard labour. The devil is trying to hit us exactly there, because in all those is the direct relationship with God. Your thought is careless, you remember "important" things, you get tired to be concentrated … And it is most harder to collect your mind and feelings and enter the heart with pure infinite faith that the Lord is with you and he hears you and then pray from all your heart and soul … So is this all easy?! And there is no end and there is no station. But once you live like this there is delight and you can't live no longer in another way …"

 

What’s going around Lately

Saturday, April 19th, 2008

Nothing special. Last week went just fine thanks to the Lord ! Of Course :). It was mostly peaceful. What was interesting was a method our teacher at management choose to use to make us better understand ourselves. She said I want all of you to draw me a picture of how do you foresee yourself ten years from now :). We all was surprised but just as she requested we did draw the pictures. My picture had 4 possibly futures. In one of them I was with my wife and a kid in front of our house, on the other I was owning and leading an IT company. On one of them I was helping to get out of the terrible pit of depression, addiction to drug, alcoholism, telling them “Stop there is a reason to live, God Loves you!”. In the other case I was a Senior SysAdmin in a middle size/big company managing servers/clusters. Now we had to make a report explaining our picture. I just did make my report hope the teacher would like it. Yesterday, Bino came home and proposed to go out, we went out we saw Stoyan (who btw is a Brother in Christ). Later we saw Dancho a friend of mine (a communist). First we started a normal talk later the talk just transformed into a terrible and useless argue I did a mistake not stopping whenever I had to. And in the end we decided not to see each other because it’s bad for both of us. Later Alex (an ex class-mate) called me and we went we had a walk in the central park and talked ’bout if I can say it like this “the life, the universe, and everything else” :). The next few weeks outline to be a tough one. We are going to have a lot of exams 8 or 9 ! We had a lot of projects and assignments but still I trust on the Holy one to help me make all of them and do just fine on the exams just like he helped me the last semester and the previous year.END—–

People Just Pretend

Sunday, January 28th, 2007

I’m starting to realize that there is no actually friendship in life. I’m starting realize, ppl use you time after time. I’m sick of existence. I want to go out of this Hell. Why I’m Here Why? What makes the difference with or without me? Nobody cares in general. I’m so disappointed of this miserable existence here on earth even. My life is not so bad but with or without God it’s so meaningless. I want out of this body and this universe. I want Freedom in the END. I want real things I’m sick of all this. As Buddha says everything is chaning nothing seems to be static, he is right about this! I never imagined I’ll be the person which I’m now. I hate my life. Please take my life Lord. Let me out of this miserable Place Please! Body My holding Cell …