Shivratri 2025: Why did Rishi Kashyap give this terrible curse to Lord Shiva? Know how Ganesha had to suffer result

;

Lord Shiva is considered an angry god as well as a liberal deity. All of them get protection in their shelter. Similarly, once the monk gardeners and Sumali also reached their shelter with their call. He was tried with severe physical pain because the Sun God was not blessing him.

According to the Brahmavaivarta Purana, when Lord Shiva heard his agony, he became very angry and in anger he hit Suryadev with his trident. Suryadev could not bear the attack of Bholenath and fell down from the chariot and died. As soon as he fell, the entire creation drowned in darkness. Seeing his son in this condition, Pita Kashyap sage furious in anger and reached Lord Shiva and came in a rage and cursed Shiva. He said that the way he is crying on his son’s condition today, he will have to be sad like his son’s death.

When the anger of Lord Shiva calmed down, he saw that there is darkness throughout the creation. Then he decided to donate life to Surya Dev. But when he came to know about the curse of sage Kashyap, he decided to abandon his family. At the very request of Brahma ji, the sage Kashyapa reconsidered his curse. He said that Shiva’s son will definitely be killed by him, but he will definitely get life like my son.

How the curse of Rishi Kashyapa was the effect of the curse of sage Kashyapa, that Lord Shiva came in anger and separated his son Ganesha from the torso. When Goddess Parvati saw this, she became very angry. Even when Ganesha was not insulting him, Lord Shiva was not insulting him, but was obeying his mother, he started feeling very sad to kill his own son. Then all the gods together requested Shiva to revive the child because due to the wrath of Goddess Parvati, there was an outcry in the entire creation. Then at the behest of Lord Shankar, Vishnu brought the head of an elephant and put that head on the torso of that child and made him alive. Since then, Lord Ganesha’s name became Gajanan.

Share this story

Exit mobile version