Trouble with PCNS 2.2.3 configuration/webgui on linux

Anonymous user · ‎2021-06-30

First and foremost, I'm not a linux expert, I hunt and peck for answers as I need them so bear with me if I'm not following your help.

I've got a CentOS 5.3 64bit box (command line only) that I'm able to install just fine (using all the defaults). The problem comes in when running PCNSConfig. According to the config output, the management card is not responding; however when I check the client list on the UPS, the IP for this box is listed and I've deleted the entry since and reinstalled/reconfigured on the box only to have it show back up in the UPS client list. So that's oddity #1. The second issue is I cannot access the webgui on 3052. I know the service is running but that's about it.

I've installed 2.2.1 on 32bit CentOS 5.2 with no problem as well as some ESX 3.0 servers with no problems so I'm not sure what the issue here is. The only thing that's different here is I'm unsure if the firewall is impeding anything.

iptables shows:
Chain INPUT (policy ACCEPT)
target prot opt source destination
RH-Firewall-1-INPUT all -- anywhere anywhere

selinux was enabled so I set that to disabled in the config file and rebooted, same thing.

According to the about, my NMC is: Firmware Revision: 477.17.W
Why it shows that instead of 3.5.8 (which I even re-flashed with this morning) I'm not sure.

So what am I missing?

Thanks

ETA: A little more info, not sure if it's relevant. netstat on the 5.2 box comes back with:
tcp 0 0 0.0.0.0:3052 0.0.0.0:* LISTEN
udp 0 0 0.0.0.0:3052 0.0.0.0:*

While on the bad 5.3 box it shows:
tcp 0 0 :::3052 :::* LISTEN
udp 0 0 :::3052 :::*

Not sure if the IP values being empty is bad. Not sure what config file they might be in to fix that.

Message was edited by: TomBodet

voidstar_apc · ‎2021-06-30

iptables -L only shows you a single table, but there are multiple tables that the packet goes through. You can use the -t option to select a particular table, such as INPUT, PREROUTING, POSTROUTING, OUTPUT, etc

See Answer In Context

Anonymous user · ‎2021-06-30

Okay, turned off iptables and magically everything works now. So I'm obviously interpreting the result of iptables -L incorrectly.

Just need to figure out how to add the entries and I think I'm all set.

voidstar_apc · ‎2021-06-30

iptables -L only shows you a single table, but there are multiple tables that the packet goes through. You can use the -t option to select a particular table, such as INPUT, PREROUTING, POSTROUTING, OUTPUT, etc