Re: [Nut-upsuser] ordered shutdown

2009-02-09 Thread Lars Täuber
Hi Arjen,

Arjen de Korte  schrieb:
> Citeren Lars Täuber :
> In that case, I probably don't understand what you're trying to do.

sorry for my english.

> So you want the servers to keep running as long as possible and the  
> clients should go down after a power outage of (say) five minutes?  
> That's possible too.

Let's assume we have a lot of servers and each should start it's shutdown 
sequence at a different level of time left of the ups running on batteries.
 
Could you give an example of a configuration for two different servers then?

Thanks
Lars

___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] ordered shutdown

2009-02-09 Thread Lars Täuber
Hallo Arjen,

Arjen de Korte  schrieb:
> Citeren Lars Täuber :
> 
> [...]
> The above values would be an extremely bad idea and this is also not  
> how NUT works. See the FAQ.
> 
[...] 
> What you describe is not how NUT works. Until the UPS signals that the  
> battery is low, it is business as usual (see the FAQ for the reasons  
> behind this). Once the UPS signals battery low, all timers are started  
> at the same time and there is no way to stop the following sequence of  
> events. The systems *will* go down. If the power returns during the  
> shutdown sequence, the shutdown sequence will be completed and NUT  
> will power-cycle the UPS to make sure the connected systems are  
> restarted.

it seems I understood how NUT works now. But then it is not the solution for 
us. The reason simply is we have one big ups for so many servers. And it's a 
bad idea to have one point in time to shutdown all servers. So one »battery 
low« signal for all servers is not what we need.
There are some servers that should  work as long as possible and shut down 
shortly (2 minutes) before the ups shuts off. But these server also should try 
to shut down and that's why they need the connection to the ups too.
Is it possible with NUT to tell upsd to initiate a shutdown by the means of 
upssched? As long as I understood upssched doesn't run as root. So it can't be 
used to initiate a shutdown directly.

Thanks
Lars

___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] ordered shutdown

2009-02-06 Thread Lars Täuber
Hallo Arjen,

Arjen de Korte  schrieb:
> Citeren Charles Lepple :
> 
> Basically, this needs to be dealt with in the client application.  
> Since we don't provide Windows clients (which Lars apparently is  
> using), I have no idea if this is possible with those.

yes, we have a mixed enviroment with mostly Linux boxes but also some Windows 
and MacOS servers.


>  FINALDELAY 0 (for the clients)
>  FINALDELAY X (for the SQL servers)
>  FINALDELAY X+Y (for the NFS servers)
> 
> The values of X and Y depend on how long the clients need for  
> finishing their business with the SQL servers (X) and how long the SQL  
> servers needs for doing their thing on the NFS servers (Y).

This seems dangerous to me. Just think of the following situation:

The ups has a normally 60 minutes of time left before shutdown after power loss.
In this case I would use 40 mins for X and 5 mins for Y.

Lets assume a power outage of 38 min has happend before it power gets back. The 
servers still run and the shutdown sequences get canceled. The batteries now 
can bridge only 22 mins on a second outage. This would lead to an unexpected 
shutoff for those servers.
The battery charge status has to get into account additionally to manage such 
situations.

Thanks anyway
Lars

___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser


Re: [Nut-upsuser] ordered shutdown

2009-02-06 Thread Lars Täuber
Hi there again,

because nobody replied I decided to enhance apcupsd with the knowlegde of the 
snmp communication to our UPS. It works for me.
I'm unsubscribing some time soon.

Regards
Lars

Lars Täuber  schrieb:
> Hallo there.
> 
> I'm new to this list and also to NUT.
> Our previous ups-system was APC based and apcupsd was serving the ordered 
> shutdowns in our network.
> 
> Our new ups is made by MGE and that's why we can't use apcupsd anymore. This 
> led us into trouble.
> Our network system is quite complex and we need shutdown sequence levels. The 
> servers depend on each other because of NFS and SQL connections and the like.
> We have one 60kVA UPS and more than 20 servers/routers/SANs supplied with 
> energy by it.
> 
> With apcupsd we could confiure the servers to shutdown on a specified battery 
> level or the remaining time. Is there a way to do this with NUT anyhow?
> I thought about using the schedule mechanism with own bash scripts but this 
> won't work on windows. In the docs is nothing written about such a feature.
> BTW, is there a feature request website for NUT somewhere?
> 
> Thanks
> Lars
> 
> ___
> Nut-upsuser mailing list
> Nut-upsuser@lists.alioth.debian.org
> http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser


-- 
Informationstechnologie
Berlin-Brandenburgische Akademie der Wissenschaften
Jägerstrasse 22-23 10117 Berlin
Tel.: +49 30 20370-352   http://www.bbaw.de

___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser

[Nut-upsuser] ordered shutdown

2009-01-30 Thread Lars Täuber
Hallo there.

I'm new to this list and also to NUT.
Our previous ups-system was APC based and apcupsd was serving the ordered 
shutdowns in our network.

Our new ups is made by MGE and that's why we can't use apcupsd anymore. This 
led us into trouble.
Our network system is quite complex and we need shutdown sequence levels. The 
servers depend on each other because of NFS and SQL connections and the like.
We have one 60kVA UPS and more than 20 servers/routers/SANs supplied with 
energy by it.

With apcupsd we could confiure the servers to shutdown on a specified battery 
level or the remaining time. Is there a way to do this with NUT anyhow?
I thought about using the schedule mechanism with own bash scripts but this 
won't work on windows. In the docs is nothing written about such a feature.
BTW, is there a feature request website for NUT somewhere?

Thanks
Lars

___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser