Please follow this fixes listed below :-
1) Solution What are frozen messages?
Ans:-Frozen messages are messages that Exim will no longer attempt to deliver, You can thaw the message with.
exim -Mt <message-id> [ <message-id> ... ]
2) To remove all frozen messages:-
exiqgrep -z -i | xargs exim -Mrm
3) To show frozen messages:-
exim -bp | grep frozen
4) Freeze all queued messages from local user:-
exiqgrep -i -f luser@localhost | xargs exim -Mf
Saturday, October 23, 2010
FrontPage Error fix
Error message on the screen will be like this:-
Error: The server extensions were unable to access the file "..htaccess.tmp". Please check the file permissions.
Setting Password
Frontpage passthough auth enabled!
To solve this follow this commands:-
cd /usr/local/frontpage/version5.0/bin/
./owsadm.exe -o install -u username -p 80 -m www.domain.com -servconf /usr/local/apache/conf/httpd.conf -xuser username
Note:-( Even if you still receive some errors on .htacess files under the domain rename those .htaccess files, This will resolve the permission issues and .htaccess problems.)
Once the above is done- Try to reinstall Frontpage extensions on the domain.
Error: The server extensions were unable to access the file "..htaccess.tmp". Please check the file permissions.
Setting Password
Frontpage passthough auth enabled!
To solve this follow this commands:-
cd /usr/local/frontpage/version5.0/bin/
./owsadm.exe -o install -u username -p 80 -m www.domain.com -servconf /usr/local/apache/conf/httpd.conf -xuser username
Note:-( Even if you still receive some errors on .htacess files under the domain rename those .htaccess files, This will resolve the permission issues and .htaccess problems.)
Once the above is done- Try to reinstall Frontpage extensions on the domain.
Some Important Exim Commands
Queues information along with commands :-
1)**USE** Print a count of the messages in the queue- Quote:-
root@localhost# exim -bpc
2)**USE** Print a listing of the messages in the queue (time queued, size, message-id, sender, recipient):
Quote:-
root@localhost# exim -bp
3)**USE** Print a summary of messages in the queue (count, volume, oldest, newest, domain, and totals)
Quote:-
exim -bp | exiqsumm
4) **USE**Generate and display Exim stats from a logfile Quote:-
eximstats /path/to/exim_mainlog
5)**USE** Generate and display Exim stats from a logfile, with less verbose output Quote:-
eximstats -ne -nr -nt /path/to/exim_mainlog
6) **USE**Generate and display Exim stats from a logfile, for one particular day Quote:-
fgrep 2007-02-16 /path/to/exim_mainlog | eximstats
7)**USE** Print what Exim is doing right now Quote:-
exiwhat
8)**USE** How many Frozen mails on the queue :-
exim -bpr | grep frozen | wc -l
9) **USE**To delete frozen emails Quote:-
exim -bpr | grep frozen | awk {'print $3'} | xargs exim -Mrm
10) **USE** To deliver emails forcefully Quote:-
exim -qff -v -C /etc/exim.conf &
11) **USE**To Flush all mail in queue :-
exim -qff
1)**USE** Print a count of the messages in the queue- Quote:-
root@localhost# exim -bpc
2)**USE** Print a listing of the messages in the queue (time queued, size, message-id, sender, recipient):
Quote:-
root@localhost# exim -bp
3)**USE** Print a summary of messages in the queue (count, volume, oldest, newest, domain, and totals)
Quote:-
exim -bp | exiqsumm
4) **USE**Generate and display Exim stats from a logfile Quote:-
eximstats /path/to/exim_mainlog
5)**USE** Generate and display Exim stats from a logfile, with less verbose output Quote:-
eximstats -ne -nr -nt /path/to/exim_mainlog
6) **USE**Generate and display Exim stats from a logfile, for one particular day Quote:-
fgrep 2007-02-16 /path/to/exim_mainlog | eximstats
7)**USE** Print what Exim is doing right now Quote:-
exiwhat
8)**USE** How many Frozen mails on the queue :-
exim -bpr | grep frozen | wc -l
9) **USE**To delete frozen emails Quote:-
exim -bpr | grep frozen | awk {'print $3'} | xargs exim -Mrm
10) **USE** To deliver emails forcefully Quote:-
exim -qff -v -C /etc/exim.conf &
11) **USE**To Flush all mail in queue :-
exim -qff
To clear Domlogs
Fire the following command :-
cd /usr/local/apache/domlogs/
for x in `ls`;
do
echo "" > $x;
done;
cd /usr/local/apache/domlogs/
for x in `ls`;
do
echo "" > $x;
done;
Thursday, October 21, 2010
Using cron to run programs on a schedule
Using cron to run programs on a schedule is very useful feature :-
Cron is a Linux system process that will execute a program at a preset time, To use cron you must prepare a text file that describes the program that you want executed & the times that cron should execute them, Then you use the crontab program to load the text file that describes the cron jobs into cron.
Here is the format of a cron job file:
[min] [hour] [day of month] [month] [day of week] [program to be run]
where each field is defined as
[min] Minutes that program should be executed on. 0-59. Do not set as * or the program will be run once a minute.
[hour] Hour that program should be executed on. 0-23. * for every hour.
[day of month] Day of the month that process should be executed on. 1-31. * for every day.
[month] Month that program whould be executed on. 1-12 * for every month.
[day of week] Day of the week. 0-6 where Sunday = 0, Monday = 1, ...., Saturday = 6. * for every day of the week.
[program] Program to be executed, Include full path information.
Here are some examples below:-
0,15,30,45 * * * * /usr/bin/foo
Will run /usr/bin/foo every 15 minutes on every hour, day-of-month, month, and day-of-week. In other words, it will run every 15 minutes for as long as the machine it running.
10 3 * * * /usr/bin/foo
Will run /usr/bin/foo at 3:10am on every day.
10 * 1 * * /usr/bin/foo
Will run /usr/bin/foo at 12:10am on the first day of the month.
10 * * 1 * /usr/bin/foo
Will run /usr/bin/foo at 12:10am on the first month of the year.
10 14 * * 1 /usr/bin/foo
Will run /usr/bin/foo at 2:10pm on every Monday.
You must use crontab to load cron jobs into cron. First create a text file that uses the above rule to describe the cron job that you want to load into cron. But before you load it, type crontab -l to list any jobs that are currently loaded in crontab.
If none are listed, then it is safe to load your job,Example. If you wanted to run /usr/local/bin/foo once a day at 3:10am, then create a text file
10 3 * * * /usr/bin/foo
Save it as foo.cron. Then type crontab foo.cron. Check to see if it was loaded by typing crontab -l. It should display something like this:
# DO NOT EDIT THIS FILE - edit the master & reinstall.
# (ipwatch.cron installed on Thu Nov 18 11:48:02 2009)
# (Cron version -- $Id: crontab.c,v 2.13 2004/01/17 03:20:37 vixie Exp $)
10 3 * * * /usr/bin/foo
If you want to edit the cron job, then edit foo.cron and then remove the existing cron job (crontab -r) and load it again (crontab foo.cron). You can have multiple jobs. Just put each different one on a seperate line in foo.cron.
contab jobs will run under the user that was in effect when you loaded the job in crontab.
Cron is a Linux system process that will execute a program at a preset time, To use cron you must prepare a text file that describes the program that you want executed & the times that cron should execute them, Then you use the crontab program to load the text file that describes the cron jobs into cron.
Here is the format of a cron job file:
[min] [hour] [day of month] [month] [day of week] [program to be run]
where each field is defined as
[min] Minutes that program should be executed on. 0-59. Do not set as * or the program will be run once a minute.
[hour] Hour that program should be executed on. 0-23. * for every hour.
[day of month] Day of the month that process should be executed on. 1-31. * for every day.
[month] Month that program whould be executed on. 1-12 * for every month.
[day of week] Day of the week. 0-6 where Sunday = 0, Monday = 1, ...., Saturday = 6. * for every day of the week.
[program] Program to be executed, Include full path information.
Here are some examples below:-
0,15,30,45 * * * * /usr/bin/foo
Will run /usr/bin/foo every 15 minutes on every hour, day-of-month, month, and day-of-week. In other words, it will run every 15 minutes for as long as the machine it running.
10 3 * * * /usr/bin/foo
Will run /usr/bin/foo at 3:10am on every day.
10 * 1 * * /usr/bin/foo
Will run /usr/bin/foo at 12:10am on the first day of the month.
10 * * 1 * /usr/bin/foo
Will run /usr/bin/foo at 12:10am on the first month of the year.
10 14 * * 1 /usr/bin/foo
Will run /usr/bin/foo at 2:10pm on every Monday.
You must use crontab to load cron jobs into cron. First create a text file that uses the above rule to describe the cron job that you want to load into cron. But before you load it, type crontab -l to list any jobs that are currently loaded in crontab.
If none are listed, then it is safe to load your job,Example. If you wanted to run /usr/local/bin/foo once a day at 3:10am, then create a text file
10 3 * * * /usr/bin/foo
Save it as foo.cron. Then type crontab foo.cron. Check to see if it was loaded by typing crontab -l. It should display something like this:
# DO NOT EDIT THIS FILE - edit the master & reinstall.
# (ipwatch.cron installed on Thu Nov 18 11:48:02 2009)
# (Cron version -- $Id: crontab.c,v 2.13 2004/01/17 03:20:37 vixie Exp $)
10 3 * * * /usr/bin/foo
If you want to edit the cron job, then edit foo.cron and then remove the existing cron job (crontab -r) and load it again (crontab foo.cron). You can have multiple jobs. Just put each different one on a seperate line in foo.cron.
contab jobs will run under the user that was in effect when you loaded the job in crontab.
Close connection in response to STARTTLS
---*If you get the following error (tail -F /var/log/messages)---*:-
.----------------------++++++++++++------------------.
T=remote_smtp defer (-18): Remote host mail.domain.com [111.111.111.111] closed connection in response to STARTTLS
2007-10-01 17:15:28 Start queue run: pid=13647
2007-10-01 17:15:28 1IcMzG-0003XG-1f == test@domain.com R=dnslookup
.-----------------------++++++++++++------------------.
Then you can fix this issue by editing your /etc/exim.conf, and changing the following code:-
remote_smtp:
driver = smtp
To be:-
remote_smtp:
driver = smtp
hosts_avoid_tls=* (This line should be present if not then add the line.)
Save, exit, then restart exim.
If the issue is for incoming email, you can comment out this section of your exim.conf:
tls_advertise_hosts = *
.----------------------++++++++++++------------------.
T=remote_smtp defer (-18): Remote host mail.domain.com [111.111.111.111] closed connection in response to STARTTLS
2007-10-01 17:15:28 Start queue run: pid=13647
2007-10-01 17:15:28 1IcMzG-0003XG-1f == test@domain.com R=dnslookup
.-----------------------++++++++++++------------------.
Then you can fix this issue by editing your /etc/exim.conf, and changing the following code:-
remote_smtp:
driver = smtp
To be:-
remote_smtp:
driver = smtp
hosts_avoid_tls=* (This line should be present if not then add the line.)
Save, exit, then restart exim.
If the issue is for incoming email, you can comment out this section of your exim.conf:
tls_advertise_hosts = *
When Server is not responding
When PhpMyAdmin in your domain control panel gives following error:-
#2002 - The server is not responding (or the local MySQL server's socket is not correctly configured")
link : http://forums.cpanel.net/showpost.php?p=33...mp;postcount=11
Here is what worked for me:-
pico /usr/local/cpanel/base/3rdparty/phpMyAdmin/config.inc.php
find
$cfg['Servers'][$i]['socket'] = '';
change to
$cfg['Servers'][$i]['socket'] = '/var/lib/mysql/mysql.sock';
next line
$cfg['Servers'][$i]['connect_type'] = 'tcp';
change to
$cfg['Servers'][$i]['connect_type'] = 'socket';
/** I am sure you like this just like me **/
#2002 - The server is not responding (or the local MySQL server's socket is not correctly configured")
link : http://forums.cpanel.net/showpost.php?p=33...mp;postcount=11
Here is what worked for me:-
pico /usr/local/cpanel/base/3rdparty/phpMyAdmin/config.inc.php
find
$cfg['Servers'][$i]['socket'] = '';
change to
$cfg['Servers'][$i]['socket'] = '/var/lib/mysql/mysql.sock';
next line
$cfg['Servers'][$i]['connect_type'] = 'tcp';
change to
$cfg['Servers'][$i]['connect_type'] = 'socket';
/** I am sure you like this just like me **/
Subscribe to:
Posts (Atom)