Deprecated: Optional parameter $shortcode declared before required parameter $args is implicitly treated as a required parameter in /home/ashishka/public_html/wp-content/plugins/wp-cirrus/wp-cirrus.php on line 331

Warning: Cannot modify header information - headers already sent by (output started at /home/ashishka/public_html/wp-content/plugins/wp-cirrus/wp-cirrus.php:331) in /home/ashishka/public_html/wp-content/plugins/all-in-one-seo-pack/app/Common/Meta/Robots.php on line 89

Warning: Cannot modify header information - headers already sent by (output started at /home/ashishka/public_html/wp-content/plugins/wp-cirrus/wp-cirrus.php:331) in /home/ashishka/public_html/wp-includes/feed-rss2.php on line 8
Exim corrupted | Web Hosting Stuff https://www.ashishkale.in Get solutions under one roof Thu, 30 Apr 2015 18:57:31 +0000 en-US hourly 1 Exim : retry time not reached for any host after a long failure period https://www.ashishkale.in/exim-retry-time-not-reached-for-any-host-after-a-long-failure-period/ https://www.ashishkale.in/exim-retry-time-not-reached-for-any-host-after-a-long-failure-period/#respond Thu, 30 Apr 2015 18:57:31 +0000 http://www.ashishkale.in/?p=127 Exim : retry time not reached for any host after a long failure period. The issue is because of the corrupted exim db files. Go to /var/spool/exim/db and delete files: retry , retry.lockfile , wait-remote_smtp, wait-remote_smtp.lockfile #cd /var/spool/exim/ #rm retry retry.lockfile wait-remote_smtp wait-remote_smtp.lockfile After that restart the exim service. #/etc/init.d/exim restart

The post Exim : retry time not reached for any host after a long failure period first appeared on Web Hosting Stuff.

]]> exim

Exim : retry time not reached for any host after a long failure period.

The issue is because of the corrupted exim db files.

Go to /var/spool/exim/db and delete files: retry , retry.lockfile , wait-remote_smtp, wait-remote_smtp.lockfile

#cd /var/spool/exim/

#rm retry retry.lockfile wait-remote_smtp wait-remote_smtp.lockfile

After that restart the exim service.

#/etc/init.d/exim restart

The post Exim : retry time not reached for any host after a long failure period first appeared on Web Hosting Stuff.

]]> https://www.ashishkale.in/exim-retry-time-not-reached-for-any-host-after-a-long-failure-period/feed/ 0