Topic: UPS connection failure

[uniqsys]

I have 2 servers both with Tripplite SmartPro upses.  One server is still on 7.0 with patches and the other is up to 7.1 with the latest patches.  The 7.0 server communicates fine with the tripplite using the tripplite driver.  The 7.1 server retruns an error:connection failure, connection refused.  The 7.1 server-ups communication was previously working before I ran the updates.

When I now do a

Code: [Select]

config show nut it now returns
2 new parameters

MasterPass

and

SlavePass

that were not there before.

Is there some kind of encrytion that is now a part of nut that I am unaware of? I have searched the forum and haven't found anything referencing this.

I am leery of updating the 7.0 server in case that breaks too for it is at a customer site before I can resolve this in house issue on the 7.1 server.

Can anyone help?

PS I configured the ups nut communication as directed in other postings here at the forum which worked for me before I ran the update.

[CharlieBrady]

I have 2 servers both with Tripplite SmartPro upses.  One server is still on 7.0 with patches and the other is up to 7.1 with the latest patches.  The 7.0 server communicates fine with the tripplite using the tripplite driver.  The 7.1 server retruns an error:connection failure, connection refused.

Please report all problems only via the Bug Tracker. Thanks.

[uniqsys]

OK.

But I have been verbally spanked twice after posting directly to the bug tracker.  I was strongly told to start here first which I did.

I need some help and don't want to upset anyone.

Upon further investigation on my problem, it seems Nut won't even start so bug tracker here we come!

[CharlieBrady]

But I have been verbally spanked twice after posting directly to the bug tracker.  I was strongly told to start here first which I did.

You were never told, and nobody ever gets told, to report bugs via the forums.

Perhaps you are referring to here:

http://bugs.contribs.org/show_bug.cgi?id=1664

where we inform you that we cannot assist you in getting your customisations to work.

Or here:

http://bugs.contribs.org/show_bug.cgi?id=1287

where we tell you that we are unable to fix bugs in the Evolution mail client.

In neither case were you told that you shouldn't have used the bug tracker. On the contrary, you were encouraged to use the bug tracker:

> Sorry I bothered you with this issue. I will try to be more diligent
> in "proving" the bug before I report any other possible ones.

No, we'd rather have advance warnings of possible bugs. Raise the bug, and then
continue to investigate.

Please help us to make our software as reliable as possible. Your role in that is to report possible bugs only via the bug tracker, and to encourage others to do the same. Thanks.

[uniqsys]

My goal is to make the software better too and I want to help in that way as much as possible without being a bother.
 
So how do I know it is a bug?  I thought the forum would be the place to start to see if someone else has a similar problem.  Then if the combined knowledge (not just mine) points to a bug, we would report it as a bug.

I guess I am frustrated as to how to determine if it is a bug.  On this particular issue I was assuming the software worked because it had worked before and I suspected my ignorance regarding 2 new NUT properties (MasterPass and SlavePass) was causing the problem.

In hind site (always 20/20) I should have looked at the bug tracker first before posting my issue.  Sorry.  It never dawned on me because, well, as I explained before, the software was working and I would suspect my ignorance before I would suspect the prior working software.

In any case, I have taken this issue to the bug tracker and hopefully it can be resolved soon. If I can do anything to help in that way, please let me know.  As I said before, I support SME wholeheartedly and want to help in any way I can.  Thanks Charlie for your patience with me.

[CharlieBrady]

So how do I know it is a bug?

You don't need to. If there's any chance that it is a bug, please report to the bug tracker. It doesn't matter whether anyone else has seen it. It doesn't matter whether anyone else has a theory as to what is happening. You have noticed something that doesn't seem to work right, so just report it. Please.

[uniqsys]

OK, will do.

This issue was moved to Bug 2268.