基于PHPSecLib的多服务器Exim邮件队列统计仪表盘显示异常问题

Hey there! Let's walk through simple, actionable checks to figure out why only Web1's queue stats are showing up—no fancy dev jargon required.

Step 1: Test Each Server File Independently #

First, set index.php aside for a minute. Open your browser and visit web2.php and web3.php directly (like http://your-domain.com/web2.php).

• If these pages don’t display a queue number (or show an error), the problem lies with the individual server files, not how index.php includes them.
• If they work on their own, the issue is likely with how index.php pulls them in (though this is less likely since Web1 works).

Step 2: Turn On Error Messages #

Most issues are silent errors you can’t see. Add these two lines at the very top of web2.php and web3.php to force PHP to show errors:

<?php
error_reporting(E_ALL);
ini_set('display_errors', 1);
// Rest of your PHPSecLib code below...
?>

Reload those files, and you’ll probably get a clear message like "Login Failed" or "Command not found" that points directly to the problem.

Step 3: Double-Check SSH Connection Details #

Typos here are super common—verify these in web2.php and web3.php:

• Server hostname/IP: Is web2.example.com (or your actual server address) spelled correctly?
• SSH port: Most servers use port 22, but if yours uses a custom port, did you set it with $ssh->setPort(XX);?
• Credentials: Username, password, or SSH key path—are they accurate? If using keys, make sure the web server user has access to the key file.

Step 4: Verify Exim Command Permissions #

The SSH user you’re using needs permission to run the Exim queue command (usually exim -bpc). Try running that command manually via SSH on Web2/Web3 to confirm:

• If it works there, great. If not, you might need to add the user to a group with access, or configure sudo so the user can run sudo exim -bpc without entering a password (set this up in the sudoers file).

Step 5: Check File Permissions & Paths #

Make sure web2.php and web3.php exist in the same folder as index.php, and that your web server (Apache/Nginx) can read them. Set file permissions to 644 with this command:

chmod 644 web2.php web3.php

Step 6: Rule Out Connection Timeouts #

Remote server connections can take longer than PHP expects. Add a timeout setting to your PHPSecLib code in web2.php/web3.php to give it more time:

$ssh = new Net_SSH2('web2.example.com');
$ssh->setTimeout(15); // Wait up to 15 seconds for the connection
if (!$ssh->login('username', 'password')) {
    exit('Login failed or timed out');
}

Quick Check: Inspect Page Source #

If index.php still doesn’t show Web2/Web3, right-click the page and select "View Page Source". Look at the cells for Web2 and Web3—you might find hidden error messages there that aren’t visible in the browser.

内容的提问来源于stack exchange，提问作者Cylon