Shani does not trouble the devotees of Hanumanji, know why?
Religion Spirituality
lekhaka-gajendra sharma
New Delhi, May 25. It is well known that Shani Dev never gives trouble to the devotees of Hanumanji. What is the reason behind this, why Shani Dev does not hurt the devotees of Hanuman, let us know.
In the Treta Yuga, the great mighty, erudite scholar, the great scholar of the six scriptures and the eighteen Puranas, the power and knowledge of Pandit Ravana used to ring in the whole universe. Ravana had kept all the planets under his control. But when the condition of Shani came on Ravana, he was terrified. To protect himself, Ravana attacked Shani. He injured Shani with a trident received from Shiva and hanged him upside down in his prison. While burning Lanka, Hanumanji saw Kishnidev hanging upside down in Ravana’s prison, so he freed Shani. Expressing his gratitude towards Hanumanji, Shani asked him to tell him the service. Then Hanumanji said that you do not trouble my devotees. Shani immediately accepted this and since then he does not trouble the devotees of Hanumanji. Worshiping and serving Hanumanji at the time of Shani’s pain gives immediate freedom from Shani’s pain. In the Ram-Ravana war, Shani used his evil vision to destroy Ravana along with his family. As a result Ravana was defeated.
exile to the Pandavas
When Shani’s condition came on the Pandavas in Dwapar Yuga, Shani Dev first confused Draupadi’s intellect. Because of which he spoke bitter words towards the Kauravas. As a result of this the Pandavas had to undergo exile and it culminated in the Mahabharata war.
Vikramaditya’s plight
When the condition of Shani came on Maharaja Vikramaditya, only the picture of the peacock swallowed the necklace. Because of this Vikramaditya was accused of theft and he had to run a crusher at Teli’s house.
King Harishchandra suffered
Due to Shani, King Harishchandra had to suffer from door to door. The family is away. Had to work with the Chandal in the crematorium.
Story first published: Wednesday, May 25, 2022, 7:00 [IST]
