similar to: Shutdown when both (all) UPS on battery / low battery

Displaying 20 results from an estimated 1000 matches similar to: "Shutdown when both (all) UPS on battery / low battery"

2014 Jan 21
0
Shutdown when both (all) UPS on battery / low battery
I would like to mention that MINSUPPLIES manipulation doesn't work. My nut version is : 2.2.2-4 (RHEL 5) -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2274 bytes Desc: Kryptograficzna sygnatura S/MIME URL:
2014 Jan 21
3
Shutdown when both (all) UPS on battery / low battery
On Jan 21, 2014, at 3:16 AM, Rafa? Oleszek wrote: > I would like to mention that MINSUPPLIES manipulation doesn't work. My nut version is : 2.2.2-4 (RHEL 5) What do your configuration files look like? Setting MINSUPPLIES to 2 should work. You can run upsmon with a debug level of 3 or greater, and it will print the current and minimum "power value", which is what determines
2014 Jan 21
0
Shutdown when both (all) UPS on battery / low battery
> What do your configuration files look like? Setting MINSUPPLIES to 2 should work. You can run upsmon with a debug level of 3 or greater, and it will print the current and minimum "power value", which is what determines when to shut down. > > Also, if you don't want to wait for both UPSes to drain to the low battery state, you can set up a pair of dummy-ups drivers. I'm
2014 Jan 23
2
Shutdown when both (all) UPS on battery / low battery
On Jan 21, 2014, at 9:27 AM, Rafal Oleszek wrote: > So it's impossible to configure upssched to start timer only if all ups > are in status: OB or LB ? Not impossible, just not possible inside a single configuration file. You can always put that logic into an external script called by upssched. -- Charles Lepple clepple at gmail
2014 Feb 03
0
Shutdown when both (all) UPS on battery / low battery
> On Jan 21, 2014, at 9:27 AM, Rafal Oleszek wrote: > >> So it's impossible to configure upssched to start timer only if all ups >> are in status: OB or LB ? > Not impossible, just not possible inside a single configuration file. You can always put that logic into an external script called by upssched. > Thank for your help Charles. I checked it and it works like you
2014 Jan 23
2
Shutdown when both (all) UPS on battery / low battery
On Jan 21, 2014, at 9:24 AM, Rafal Oleszek wrote: > I tried all options: > 1,2 > and in MINSUPPLIES: 1,2,3,4 > still didn't work. My mistake - I gave you the wrong advice before. For MINSUPPLIES, I'm used to either a 1:1 UPS-to-server ratio, or 2:1 where the server can run with either power supply unpowered. I just tried this in upsmon.conf: MONITOR dummy1 1 monuser
2014 Jan 21
2
Shutdown when both (all) UPS on battery / low battery
On Jan 21, 2014, at 8:05 AM, Rafa? Oleszek wrote: > MONITOR UPS_251 at localhost 2 monmaster password master > MONITOR UPS_252 at localhost 2 monmaster password master I think the "2"s here should be "1". "powervalue is an integer representing the number of power supplies that the UPS feeds *on this system*." So if UPS_251 is connected to one power supply on
2014 Jan 23
0
Shutdown when both (all) UPS on battery / low battery
> On Jan 21, 2014, at 9:24 AM, Rafal Oleszek wrote: > >> I tried all options: >> 1,2 >> and in MINSUPPLIES: 1,2,3,4 >> still didn't work. > > My mistake - I gave you the wrong advice before. For MINSUPPLIES, I'm used > to either a 1:1 UPS-to-server ratio, or 2:1 where the server can run with > either power supply unpowered. > > I just tried
2014 Jan 21
0
Shutdown when both (all) UPS on battery / low battery
I tried all options: 1,2 and in MINSUPPLIES: 1,2,3,4 still didn't work. UPS_251 and UPS_252 feeds all environment and it's not feed directly one server, but many of them. > On Jan 21, 2014, at 8:05 AM, Rafa? Oleszek wrote: > >> MONITOR UPS_251 at localhost 2 monmaster password master >> MONITOR UPS_252 at localhost 2 monmaster password master > > I think the
2014 Jan 21
2
Shutdown when both (all) UPS on battery / low battery
On Jan 21, 2014, at 8:05 AM, Rafa? Oleszek wrote: > It does not matter what value I'll put in MONITOR and MINSUPPLIES line. NUT not waiting for both UPS to start timer. Correct. You can think of upssched as operating on raw UPS status, rather than the calculated powervalue that upsmon uses to decide when to shut down. -- Charles Lepple clepple at gmail
2014 May 08
3
v2.2.13.rc1 released
http://dovecot.org/releases/2.2/rc/dovecot-2.2.13.rc1.tar.gz http://dovecot.org/releases/2.2/rc/dovecot-2.2.13.rc1.tar.gz.sig There have been a ton of smaller and some larger changes since v2.2.12, so I thought I'd first make a RC release and the final v2.2.13 tomorrow. Please try it out! BTW. I've read most of the mails again in Dovecot mailing list, but there are still a few reported
2014 May 08
3
v2.2.13.rc1 released
http://dovecot.org/releases/2.2/rc/dovecot-2.2.13.rc1.tar.gz http://dovecot.org/releases/2.2/rc/dovecot-2.2.13.rc1.tar.gz.sig There have been a ton of smaller and some larger changes since v2.2.12, so I thought I'd first make a RC release and the final v2.2.13 tomorrow. Please try it out! BTW. I've read most of the mails again in Dovecot mailing list, but there are still a few reported
2014 Jan 21
0
Shutdown when both (all) UPS on battery / low battery
So it's impossible to configure upssched to start timer only if all ups are in status: OB or LB ? > On Jan 21, 2014, at 8:05 AM, Rafa? Oleszek wrote: > >> It does not matter what value I'll put in MONITOR and MINSUPPLIES line. >> NUT not waiting for both UPS to start timer. > > Correct. You can think of upssched as operating on raw UPS status, rather > than the
2012 Sep 26
2
mail size needed in dovecot sieve log line
This is a dovecot sieve log line: 2012-09-26T13:47:52+02:00 host/192.168.1.1 dovecot: [ID 583609 mail.info] lmtp(7565, user at domain): vTtJDTrrYlCNHQAAs1WjhA: sieve: msgid=<MSGID>: stored mail into mailbox 'INBOX' Would it be possible to have mail size logged here? MU -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type:
2014 May 21
1
dovecot auth ldap attributes - unused?
Please explain the following dovecot (2.2.13) behaviour: I run dovecot in ldap auth debug mode and log file excerpt follows: 2014-05-21T08:22:01+02:00 dovecot/ip dovecot: auth: Debug: ldap(user at domain,pcip,<bdKvA+P5HQCbnmFI>): bind search: base=o=tree,dc=do,dc=ma,dc=in filter=(&(objectClass=MailAccount)(accountActive=TRUE)(mail=user at domain)) 2014-05-21T08:22:01+02:00 dovecot/ip
2014 May 13
2
RFE: please add mail queue id to 'sent vacation response' log line
May I ask to add receiving smtp server mail queue id to sieve 'sent vacation response' log line? Now: 2014-05-09T15:04:32+02:00 name/ip dovecot: lmtp(8164, user1 at domain): YvJFLVbSbFPkHwAASpgOhg: sieve: msgid=<000301cf6b87$36be4570$a43ad050$@us.edu.pl> size=46850: sent vacation response to <user2 at domain> Asked for something like this: 2014-05-09T15:04:32+02:00 name/ip
2014 Jan 13
0
Fatal: master: service(imap): child n killed with signal 11 (core dumped) - in mail_cache_header_fields_read
This is log from dovecot 2.2.10: 2014-01-13T15:34:39+01:00 server/a.b.c.d dovecot: imap(user at domain): Fatal: master: service(imap): child 6290 killed with signal 11 (core dumped) (gdb) bt full #0 0x00007fe78683aba5 in mail_cache_header_fields_read () from /usr/local/dovecot-2.2.10/lib/dovecot/libdovecot-storage.so.0 No symbol table info available. #1 0x00007fe78683890a in
2014 Jan 11
0
Panic: file buffer.c: line 307 (buffer_set_used_size): assertion failed: (used_size <= buf->alloc)
This is log from dovecot 2.2.10: 2014-01-11T09:55:14+01:00 server/a.b.c.d dovecot: imap(user at domain): Error: Corrupted transaction log file /pracmail/domain/user/mail/.sent-mail/dovecot.index.log seq 16777216: log file shrank (868 < 6144) (sync_offset=6144) 2014-01-11T09:55:14+01:00 server/a.b.c.d dovecot: imap(user at domain): Panic: file buffer.c: line 307 (buffer_set_used_size):
2014 May 13
3
RFE: please add Return-Path: to sieve sent mail headers
May I ask to add Return-Path: some meaningful header line to sieve sent mail headers in vacation message? Now the header line isn't generated at all and the effect is as follows: on receiving MTA: 2014-05-09T15:04:32+02:00 host/ip postfix/qmgr[2408]: 41F2F6024E: from=<>, size=900, nrcpt=1 (queue active) in received mail body: Return-Path: <> Would be nice to get: Return-Path:
2014 Jan 14
0
Fatal: master: service(lmtp): child n killed with signal 11 (core dumped) - in mail_cache_header_fields_read
This is log from dovecot 2.1.17 (I had to downgrade from 2.2.10 because lot of problems) on CentOS 6.5: 2014-01-14T18:36:03+01:00 server/a.b.c.d dovecot: lmtp(5927): Fatal: master: service(lmtp): child 5927 killed with signal 11 (core dumped) # uname -a Linux server 2.6.32-431.1.2.0.1.el6.x86_64 #1 SMP Fri Dec 13 13:06:13 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux (gdb) bt full #0