FreePBX Yellow Warnings

[jrglass]

On my server status page I have Yellow Warn lights for Op Panel and SSH Server. What do I need to do to correct this?

Thanks,

Jeff

 

[jroper]

Hi

Hover your mouse over them, and see if it gives you a clue to the error.

Do they stay there when you do a page refresh.

Joe

 

[wardmundy]

Try refreshing the browser page, too. Sometimes the FreePBX page is generated before all of the modules come on line.

 

[jrglass]

Refresh does not change them.

Mouse over states the panel and ssh server s are not running but I can access panel and putty in to the server.

Thanks,

Jeff

 

[wardmundy]

Better open a FreePBX bug ticket. It's theirs, not ours. Sorry.

 

[lonen]

HI JR,

Did you ever get this issue resolved? I have the same exact issue on a fresh install. Both FOP and SSH are functional yet I get yellow "Warn" Lights on the FreePBX status page. FreePBX forums weren't much help either...

Thanks.

 

[Hat]

I have the same issue. I posted a bug with FPBX.

Tom

 

[ronw]

I have the same problem with SSH Server status. I know what is causing the yellow warning, but I am not sure of the proper way to solve.

The dashboard code is checking the port status of ssh on the localhost. In file sshd_config, I have ListenAddress set to 192.168.1.200. Since ssh is not listening on 127.0.0.1, the status check performed by the dashboard in class.procinfo.php fails.

The code in class.procinfo.php that performs the status check is:

function check_port($port, $server = "localhost") {
$timeout = 5;
if ($sock = @fsockopen($server, $port, $errno, $errstr, $timeout)) {
fclose($sock);
return true;
}
return false;

If I change the ListenAddress in sshd_config to 127.0.0.1, the status will go to "ok" green. But then I cannot establish a remote ssh connection.

Is there a way to associate "localhost" to my systems IP address (192.168.1.200). All documentation that I have read states localhost should refference IP address 127.0.0.1.

 

[ronw]

I found that multiple ListenAddress options are allowed in /etc/sshd_config. Make sure you have an entry for localhost as well as the ip of your pbx.

ListenAddress 127.0.0.1
ListenAddress 192.168.1.200

Also, if you have changed your ssh port from 22, set the port number in /etc/amportal.conf.

SSHPORT=9022

That fixed my issue with SSH SERVER. I do not have the FOP status issue.

 

[Hat]

Here is an update from FreePBX:

If I read the piaf thread correctly, it sounds like piaf is not enabling (or somehow blocking) ssh and port 4445 from localhost causing the warning. If that understanding is correct, it would be useful to hear from the piaf team if there is a good reason why they are doing that or if it is an oversight. (or maybe I misunderstood the thread). We need to depend on seeing if those ports are open and being listened to and generally localhost is not blocked.

I'll wait on hearing feedback from and/or suggestions from the piaf team to determine if something needs changing here or not as I would like to understand their reasoning.

Ward, Joe, Tom, sounds like your input is requested with this issue. I think I'm in a little over my head at this point.

 

[wardmundy]

TCP/4445 is not blocked by the default firewall. Nor is the SSH port. You can verify these by reviewing /etc/sysconfig/iptables. The firewall design is to only open ports that are absolutely essential. You, of course, can reconfigure it to meet your own requirements if you know what you're doing.

To see if some problem is truly a firewall issue, turn off the firewall momentarily: disable-iptables. Then try your application and see if it works. If it doesn't, it's not a firewall issue. If it does work, then the firewall needs to be adjusted. Don't forget to turn the firewall back on: enable-iptables. If you make changes to the firewall, restart it:

service iptables stop
service iptables start

My strongest recommendation to new users is not to screw around changing ports in PBX in a Flash. Instead, buy a cheap dLink WBR-2310 router, and change the public Internet ports for the services that you believe are vulnerable and then map those port numbers to the standard ports in PBX in a Flash on the inside of your hardware-based firewall. It eliminates many, many configuration problems. More than half of the problems we see with PBX in a Flash are issues caused by needlessly messing with passwords (that don't matter) and ports. My apologies if my frustration is showing through in this post. :tazb:

 

[jroper]

Hi

Could you also check that ping localhost resolves to 127.0.0.1

Joe

 

[Hat]

My strongest recommendation to new users is not to screw around changing ports in PBX in a Flash

More than half of the problems we see with PBX in a Flash are issues caused by needlessly messing with passwords (that don't matter) and ports

I can certainly understand your frustration with these issues. However, I didn't change any ports, or the passwords referenced, that's why this issue has me .

Joe,
I did ping pbx.local and it resolved to 127.0.0.1

 

[jroper]

I did ping pbx.local and it resolved to 127.0.0.1

Hi

I really wanted you to

ping localhost

Joe

 

[Hat]

Joe,

I did try ping localhost later on and it did not resolve to anything.

root@pbx:~ $ ping localhost
ping: unknown host localhost

 

[jroper]

Hi

That would be your problem.

your /etc/hosts file should look something like this:-

# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1    pbx.local    pbx    localhost.localdomain    localhost
::1    localhost6.localdomain6    localhost6

Can you post yours.

Joe

 

[wardmundy]

I can certainly understand your frustration with these issues. However, I didn't change any ports, or the passwords referenced, that's why this issue has me .

But you did change the /etc/hosts file and take something out.

I've got two questions:

1. Why did you make the change?
2. Why didn't you mention it when seeking help?

Here's a really important TIP for everyone. If you make changes to the stock install, write them down and keep the list. When you have a problem down the road, share the list. More often than not, this gives someone a clue why your system mysteriously came unglued. opsb:

 

[Hat]

Resolved

Joe,

Here is the contents of my /etc/host file:

# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1    myFDQN.dyndns.org pbx.local pbx 
localhost.localdomain 
localhost
::1        localhost6.localdomain6 localhost6

I found the entry like this. I must have screwed it up when I nano'd the file to add myFDQN.dyndns.org for sendmail. Though I don't recall tapping enter to change the line.

I fixed it to show this:

# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1    [I]myFDQN[/I].dyndns.org pbx.local pbx localhost.localdomain localhost
::1        localhost6.localdomain6 localhost6

Thanks for your help and patience, everything is now working.

 

[jroper]

http://www.pbxinaflash.com/forum/showpost.php?p=16835&postcount=10

Would you mind letting FreePBX know, or pointing in the direction of these posts and the resolution.

JOe

 

[Hat]

Joe,

I have asked the FreePBX team to close the bug on the fact that this issue is not a bug but my own error. My apologies to you, Ward and the PIAF community for the inconvenience my ignorance has caused. Thanks for your help.

Tom