unRAID OS Version: 6.0.1

 

Description: UPS communication can't be established over the network when authentication phrase contains spaces

 

How to reproduce:

1. Set up a APC Smart UPS on the network with authentication phrase containing spaces, for example: This is a test phrase.

2. Set up UPS communication like this:

UPS cable: Ether

UPS type: PCnet

Device: ip-of-the-UPS:Username:This is a test phrase

 

Expected results: Established communication with the UPS

 

Actual results:

Communication can't be established.

On console window you will see the following messages:

sed: can't read is: No such file or directory

sed: can't read a: No such file or directory

sed: can't read test: No such file or directory

sed: can't read phrase: No such file or directory

 

 

Bump?

MODERATORS: Please move it to the Defect Reports, as this is definitely a bug:

 

When UPS authentication phrase contains spaces (it's a phrase, duh!), unRAID doesn't deal with it properly. In fact, it tries to execute each word from the phrase. It can only be visible from the console messages:

sed: can't read (2nd word from the phrase): No such file or directory

sed: can't read (3rd word from the phrase): No such file or directory

sed: can't read (4th word from the phrase): No such file or directory

Mines working fine.  In fact I got it running yesterday just in time for our first blackout which lasted for 3 hours!  I was happy to see the 2 servers stayed up and then realised that my modem wasn't on the UPS so they couldn't communicate!  Lucky for me I had a UPS cable that I could plug it into and away they went, and shutdown safely!

 

Anyway back to your issue.

 

I have my master running V5 set to

UPS Cable:USB

UPS Type:USB

Battery Level 30

Minutes 10

 

My Slave running V6 set to

UPS Cable:Ether

UPS Type:Net

Device: IP Address of my master ie 192.168.0.100

Battery Level 50

Minutes 10

 

It works, it communicates and well tested last night.  Just make sure as I have done that your slave is set to shutdown before your master or your slave won't be able to communicate and will keep running.

 

Hope that helps.

I don't think you read carefully. Mine is communicating over the network - it's a totally different ballgame.

The device in this case is set as such:

Device: ip-of-the-UPS:Username:authentication phrase

 

When the authentication phrase contains spaces, it doesn't work properly.

Was the version of apcupsd 3.14.13 in the v6 version that PCnet was working with the passphrase?

 

Maybe your thread should be moved to Defect Reports.

Please see my post above where I asked it to be moved to the defect reports 

I have moved the thread to Defect Reports, but please see Guidelines for Defect Reports and edit your first post in the thread to include the requested information.

 

Thanks

 

Edited per the guidelines.