Windows net client error

Hi all,

I just installed apcupsd on two Ubuntu machines and one Windows machine.
The UPS is connected via USB to a Linux PC running apcupsd 3.14.2.  The
other Linux machine has apcupsd 3.12.4, and is working as an NIS client.

On Windows, I just installed apcupsd 3.14.4 and configured it
identically to the Linux client, as a network client.  I've
double-checked the IP address and port, and the UPSTYPE setting.

The apctray icon displays a question mark, the tooltip if you hover is
"NETWORK ERROR", and double clicking brings up a window that says
"Status not available".

Any idea what this is?  Is there a compatibility issue between 3.14.2
and 3.14.4?  So far everything's gone smoothly except this Windows
client. :)

Thanks!

--
Mike Mueller
mike@...

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Apcupsd-users mailing list
Apcupsd-users@...
https://lists.sourceforge.net/lists/listinfo/apcupsd-users

On Sat, Jun 14, 2008 at 01:29:29AM -0400, Mike Mueller wrote:
> On Windows, I just installed apcupsd 3.14.4 and configured it
> identically to the Linux client, as a network client.  I've
> double-checked the IP address and port, and the UPSTYPE setting.
>
> The apctray icon displays a question mark, the tooltip if you hover is
> "NETWORK ERROR", and double clicking brings up a window that says
> "Status not available".

Followup: I may have mischaracterized the error.  The windows apcupsd
service is working perfectly.  It is logging events to the Windows event
log, and shuts down the PC after an extended power outage, just like I
configured it.

The only error seems to be that the apctray program doesn't seem to work
at all.  This is minor compared to the actual service working, so I'm
happy!

--
Mike Mueller
mike@...

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Apcupsd-users mailing list
Apcupsd-users@...
https://lists.sourceforge.net/lists/listinfo/apcupsd-users

[Adam Kropelin]

Mike Mueller wrote:

> On Sat, Jun 14, 2008 at 01:29:29AM -0400, Mike Mueller wrote:
>> On Windows, I just installed apcupsd 3.14.4 and configured it
>> identically to the Linux client, as a network client.  I've
>> double-checked the IP address and port, and the UPSTYPE setting.
>>
>> The apctray icon displays a question mark, the tooltip if you hover
>> is "NETWORK ERROR", and double clicking brings up a window that says
>> "Status not available".
>
> Followup: I may have mischaracterized the error.  The windows apcupsd
> service is working perfectly.  It is logging events to the Windows
> event log, and shuts down the PC after an extended power outage, just
> like I configured it.
>
> The only error seems to be that the apctray program doesn't seem to
> work at all.  This is minor compared to the actual service working,
> so I'm happy!

Do you have the NETSERVER (i.e. NIS) enabled on the windows client? apctray
uses NIS to read status from apcupsd, so if you have NETSERVER disabled,
apctray will be unable to connect.

Note that you can add additional monitors to apctray, so if you wanted it
to also show, for example, the status of the directly-connected Linux USB
apcupsd, you can do that as well. The command-line syntax to add additional
monitors is...

    apctray /host <hostname> /port <port> /add

To remove a monitor...

    apctray /host <hostname> /port <port> /del

'port' is usually 3551. Do "apctray /?" if you need a reminder of the
syntax.

--Adam


-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Apcupsd-users mailing list
Apcupsd-users@...
https://lists.sourceforge.net/lists/listinfo/apcupsd-users

On Sat, Jun 14, 2008 at 08:00:48AM -0400, Adam Kropelin wrote:

> Do you have the NETSERVER (i.e. NIS) enabled on the windows client? apctray
> uses NIS to read status from apcupsd, so if you have NETSERVER disabled,
> apctray will be unable to connect.
>
> Note that you can add additional monitors to apctray, so if you wanted it
> to also show, for example, the status of the directly-connected Linux USB
> apcupsd, you can do that as well. The command-line syntax to add additional
> monitors is...
>
>     apctray /host <hostname> /port <port> /add
>
> To remove a monitor...
>
>     apctray /host <hostname> /port <port> /del
>
> 'port' is usually 3551. Do "apctray /?" if you need a reminder of the
> syntax.
>
> --Adam

Thanks for the helpful response.  I assumed the apctray app would look
at the apcupsd configuration and connect to the master automatically.  I
see now that that doesn't make as much sense.

First I tried the apctray /host /add trick, which worked, but only for
my user account.  All the other users still had the default localhost
setting.  So I ended up turning on the netserver on the Windows slaves
and the apctray default behavior works for everyone now.

Thanks again,
Mike

--
Mike Mueller
mike@...

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Apcupsd-users mailing list
Apcupsd-users@...
https://lists.sourceforge.net/lists/listinfo/apcupsd-users

[Adam Kropelin]

Mike Mueller wrote:

> On Sat, Jun 14, 2008 at 08:00:48AM -0400, Adam Kropelin wrote:
>> Do you have the NETSERVER (i.e. NIS) enabled on the windows client?
>> apctray uses NIS to read status from apcupsd, so if you have
>> NETSERVER disabled, apctray will be unable to connect.
>>
>> Note that you can add additional monitors to apctray, so if you
>> wanted it to also show, for example, the status of the
>> directly-connected Linux USB apcupsd, you can do that as well. The
>> command-line syntax to add additional monitors is...
>>
>>     apctray /host <hostname> /port <port> /add
>>
>> To remove a monitor...
>>
>>     apctray /host <hostname> /port <port> /del
>>
>> 'port' is usually 3551. Do "apctray /?" if you need a reminder of the
>> syntax.
>>
>> --Adam
>
> Thanks for the helpful response.  I assumed the apctray app would look
> at the apcupsd configuration and connect to the master automatically.
> I see now that that doesn't make as much sense.

I considered that feature once upon a time, but monitoring the remote
apcupsd instead of the local one has some pretty big disadvantages. Chiefly
that the local apcupsd could be dead or in an error state and you'd never
know it since apctray would be showing the status of the remote apcupsd. So
I did not want that to be the default configuration.

> First I tried the apctray /host /add trick, which worked, but only for
> my user account.  All the other users still had the default localhost
> setting.  So I ended up turning on the netserver on the Windows slaves
> and the apctray default behavior works for everyone now.

Were these "other users" already logged in (on other terminal services
sessions, for example) and running apctray already? The apctray config is
system-wide, so it will affect all users equally. However if the users were
already logged in and running apctray those other apctracy instances would
not have received the 'refresh' signal. You should just need to exit and
restart them and they will all honor the new hosts.

On a side note, I find it incredibly frustrating how difficult Windows
makes it for a process running in one session to send window messages (or
any type of IPC, really) to a process in another session. I've been
fighting with the installer to find a way for it to ensure all apcupsd and
all apctray processes are exited (cleanly!) before going on to perform the
install. But Windows' baroque security infrastructure prevents it. The same
problem is true of the apctray refresh signal. If there are any win32 api
gurus out there..help!?

--Adam


-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Apcupsd-users mailing list
Apcupsd-users@...
https://lists.sourceforge.net/lists/listinfo/apcupsd-users