A PHP Error was encountered

Severity: 8192

Message: Return type of CI_Session_null_driver::open($save_path, $name) should either be compatible with SessionHandlerInterface::open(string $path, string $name): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice

Filename: drivers/Session_null_driver.php

Line Number: 6

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: Return type of CI_Session_null_driver::close() should either be compatible with SessionHandlerInterface::close(): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice

Filename: drivers/Session_null_driver.php

Line Number: 7

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: Return type of CI_Session_null_driver::read($session_id) should either be compatible with SessionHandlerInterface::read(string $id): string|false, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice

Filename: drivers/Session_null_driver.php

Line Number: 8

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: Return type of CI_Session_null_driver::write($session_id, $session_data) should either be compatible with SessionHandlerInterface::write(string $id, string $data): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice

Filename: drivers/Session_null_driver.php

Line Number: 9

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: Return type of CI_Session_null_driver::destroy($session_id) should either be compatible with SessionHandlerInterface::destroy(string $id): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice

Filename: drivers/Session_null_driver.php

Line Number: 10

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: Return type of CI_Session_null_driver::gc($maxlifetime) should either be compatible with SessionHandlerInterface::gc(int $max_lifetime): int|false, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice

Filename: drivers/Session_null_driver.php

Line Number: 11

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 284

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: session_set_cookie_params(): Session cookie parameters cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 291

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 306

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 316

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 317

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 318

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 319

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 377

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: session_set_save_handler(): Session save handler cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 110

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: session_start(): Session cannot be started after headers have already been sent

Filename: Session/Session.php

Line Number: 143

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

NRIPage | Articles | Maha Kumbh Turns Tragic: Crowd Surge Injures 30, Authorities Scramble for Safety | Get Home & Garden improvement ideas. Transform Your Space with Style and Comfort - NRI Page
Edit

Maha Kumbh Turns Tragic: Crowd Surge Injures 30, Authorities Scramble for Safety

Maha Kumbh Turns Tragic: Crowd Surge Injures 30, Authorities Scramble for Safety
Tragedy at Maha Kumbh: Stampede Leaves Dozens Injured, Akharas Cancel Holy Dip
Prayagraj, Uttar Pradesh – A stampede-like situation unfolded at the Maha Kumbh Mela on the auspicious occasion of Mauni Amavasya, leaving around 30 women injured and prompting Akharas to cancel their sacred 'Amrit Snan.'
 
Chaos Erupts Near the Sangam
As crores of devotees gathered in Prayagraj for the holy dip at the confluence of the Ganga, Yamuna, and mythical Saraswati rivers, a surge in the crowd caused barricades to collapse nearly a kilometer away from the Sangam. Several women fainted due to suffocation, triggering panic and a stampede-like situation.
Medical teams rushed the injured to hospitals within the Maha Kumbh grounds, while those in critical condition were taken to Bailey Hospital and Swaroop Rani Medical College.
 
Akhadas Call Off Sacred Ritual
In response to the incident, the Akhil Bharatiya Akhara Parishad announced the cancellation of their scheduled 'Amrit Snan.' Parishad president Mahant Ravindra Puri said, "You must have seen what happened this morning. Our saints were prepared for the snan, but upon learning of the situation, we decided to call it off."
Similarly, Akhada Parishad General Secretary and Juna Akhara Patron Mahant Hari Giri appealed to devotees to take a holy dip in the Ganga wherever they are and return home safely.
 
Government Responds with Emergency Measures
Prime Minister Narendra Modi immediately reached out to Uttar Pradesh Chief Minister Yogi Adityanath, directing swift relief efforts. Authorities responded by shutting down pontoon bridges to prevent similar incidents and reinforcing crowd control measures.
With over 10 crore pilgrims expected for the Mauni Amavasya Snan, security measures were already stringent, including AI-powered surveillance, drone monitoring, and heightened police presence. The Prayagraj administration had earlier declared the Mela area a no-vehicle zone and urged locals to use two-wheelers only for essential travel.
 
Unprecedented Pilgrim Influx & Railway Measures
To accommodate the record-breaking influx, Indian Railways has been operating 360 trains, including 190 special services, ensuring seamless travel. Chairman and CEO of the Railway Board, Satish Kumar, highlighted, "A train is running every four minutes to facilitate pilgrims."
The Uttar Pradesh government has also deployed over 1,000 medical professionals, including 300 specialist doctors, to manage emergencies, with a super-specialty hospital in Mahakumbh Nagar equipped for major surgeries.
 
A Sacred Tradition Marked by Tragedy
The Amrit Snan on Mauni Amavasya is the most spiritually significant ritual of the Maha Kumbh, believed to transform the river waters into 'Amrit.' This year, the occasion holds even greater importance due to the rare celestial alignment known as 'Triveni Yog', occurring once every 144 years.
Despite the tragedy, over 15 crore devotees have already participated in the Maha Kumbh, with 4.80 crore pilgrims taking a dip on Tuesday alone. The government had even planned to shower 25 quintals of rose petals from helicopters to celebrate the event.
The incident raises concerns over crowd management at one of the world's largest religious gatherings, prompting urgent reviews to prevent future mishaps.

What is your response?

joyful Joyful 0%
cool Cool 0%
thrilled Thrilled 0%
upset Upset 0%
unhappy Unhappy 0%
AD
AD