server troubleshooting Archives - Michael Helm's Technology Blog

server troubleshooting

Essential Exim Mail Server Commands for System Administrators

July 19, 2009 By Michael Helm in Blog Tags: command line, email, email delivery, Exim, Linux, mail server, queue management, server management, server troubleshooting, System Administration

If you’re managing an Exim mail server, you’ll inevitably need to perform various maintenance and troubleshooting tasks. Over my nine years of server administration, I’ve found certain commands particularly useful. This guide shares those essential Exim commands that have consistently proven their value in managing mail servers effectively.

Monitoring Current Activity

To get a real-time snapshot of what Exim is currently doing:

exiwhat

This command provides an immediate overview of Exim’s current processes, showing you what the mail server is handling at that precise moment.

Analyzing the Mail Queue

Count Messages in the Queue

One of the first indicators of potential problems is an unusually large mail queue. To get a simple count of messages currently in the queue:

exim -bpc

For effective monitoring, run this command several times over a few hours to establish whether the queue is growing, which could indicate a delivery issue.

Detailed Queue Analysis

For a more comprehensive analysis of your mail queue, including size and age statistics:

exim -bp | exiqsumm

This powerful combination displays:

Total message count
Queue volume
Age of oldest and newest messages
Destination domains
Summary statistics

The “oldest message” and “volume” metrics are particularly useful for identifying problematic domains or persistent delivery issues.

Managing the Mail Queue

Process the Entire Queue

To trigger an immediate delivery attempt for all queued messages with verbose output:

exim -q -v

This instructs Exim to process the entire queue according to its standard delivery rules, with the -v flag providing detailed information about each delivery attempt.

Process Only Local Mail

If external mail is causing blockages, you can prioritize the delivery of local mail (such as system notifications):

exim -ql -v

This command attempts to deliver only messages addressed to local recipients, which can help clear important internal communications when external delivery is experiencing issues.

Clean Up Old Messages

To remove messages that have been stuck in the queue for extended periods (potentially spam or bounces):

exiqgrep -o 604800 -i | xargs exim -Mrm

This command finds and removes all messages older than 7 days (604,800 seconds). Adjust the time value as needed—it’s calculated as seconds per day (86,400) multiplied by the number of days.

Final Thoughts

While Exim offers many more specialized commands, these are the ones I’ve found most useful in day-to-day server administration. They provide a solid foundation for monitoring, troubleshooting, and maintaining your Exim mail server.

For specific issues or advanced configurations, Exim’s comprehensive documentation is an excellent resource. However, these commands should handle the vast majority of routine mail server management tasks you’re likely to encounter.

Adding Swap Space Without a Partition in Linux: A Quick Emergency Fix

July 1, 2009 By Michael Helm in Blog Tags: Linux, Linux commands, memory management, server management, server stability, server troubleshooting, swap file, swap space, System Administration, system resources

Recently, we encountered a challenging issue on one of the servers I help administer. The server would occasionally max out its RAM usage, forcing it to rely on swap space. When both RAM and swap space were exhausted, the server would grind to a halt, requiring a manual restart.

The Problem: Growing Needs, Limited Resources

The server in question had been in operation for several years, starting with modest traffic but gradually growing as the websites it hosted gained popularity and their databases expanded. Despite this growth, it was still running with only 512MB of RAM—a limitation we’ve since addressed with an upgrade.

However, we needed an immediate solution before the hardware upgrade could be implemented. The server already had a swap partition, but creating another one wasn’t feasible without significant downtime, as all available hard drives were in active use.

The Solution: Adding a Swap File

The answer turned out to be creating a swap file rather than a swap partition. This approach allows you to add additional swap space without reconfiguring your disk partitions—perfect for an emergency fix. Here’s how to do it:

Navigate to a directory with plenty of available space:
```
cd /home
```
Create a swap file using /dev/zero:
```
bash
dd if=/dev/zero of=swapfile bs=1024 count=4194304
```
This creates an empty file called “swapfile” with a block size of 1024 bytes and 4,194,304 blocks, resulting in a 4GB file. (To calculate the size in GB: 4,194,304 ÷ 1024 ÷ 1024 = 4GB)
Set appropriate permissions on the file:
```
chmod 600 swapfile
```
Format the file as swap space:
```
mkswap swapfile
```
Activate the swap file:
```
swapon swapfile
```

To verify that your new swap space is active, you can run:

cat /proc/swaps

This command displays all active swap spaces on your system, and you should now see your newly created swap file listed alongside any existing swap partitions.

Important Considerations

This solution doesn’t automatically activate on system boot, which was fine for our purposes since we planned to upgrade the RAM soon. If you need a more permanent solution, you would need to add an entry to your /etc/fstab file.

Remember that while this approach can prevent system crashes, it’s only a temporary workaround. Swap space, especially on a traditional hard drive, is significantly slower than RAM. For optimal performance, it’s always better to address the root cause by:

Upgrading physical RAM
Optimizing your application configurations
Considering server upgrades if necessary

That said, when you need a quick fix to keep a server stable until more permanent solutions can be implemented, adding a swap file is a valuable technique to have in your system administration toolkit.