Displaying 20 results from an estimated 4000 matches similar to: "[Nut-upsdev] Shutdown by battery.remaining or battery.runtime?"
2008 Jul 17
1
Shutdown by battery.remaining or battery.runtime?
On a test shutdown of an APC Back-UPS RS1500 upsc was run periodically
to follow the UPS discharge, it showed these values:
battery.low 120
battery.charge.low 10
As it turned out, the battery.charge.low was encountered first and the
system shut down there. However, considering the rate at which the
charge was falling at the end I would much rather have had it shutdown
sooner than it did. Is
2008 Jul 11
1
upsmon issue: user monuser not found
Short description: when upsmon starts it logs this to /var/log/messages:
Jul 11 12:35:55 sorcerer upsmon[23902]: Startup successful
Jul 11 12:35:55 sorcerer upsmon[23902]: user monuser not found
Near as I can tell upsd is running properly.
Long description:
Centos 5 system (x86_64), built nut 2.2.2 from stable source with
./configure --with-usb --with-user=nut --with-group-nut
make
2008 May 08
0
Tripplite SU1500RTXL2Ua and nut versions, battery line state fluctuates
I am trying to get a TrippLite SU1500RTXL2Ua working with nut on
Mandriva 2007.1, is there a particular version of nut needed to get this
to work? At first I tried nut 2.0.5 (which came with 2007.1) but it
wouldn't work, and then research showed it was an older version of nut.
So nut-2.2.1-2 src rpm was pulled from Mandriva 2008.1, the binary rpm
built, and nut and nut-server installed from
2020 May 04
2
Fwd: [EXTERNAL] SNMP shutdown timing out
I meant to send this to the list but evidently only sent it to David.
Since sending it I've done a second test which shows what a successful
snmpset looks like.
First attachment, from the forwarded email, is nutout.txt. Second
attachment is snmpout.txt.
nomad
-------- Forwarded Message --------
Subject: Re: [Nut-upsuser] [EXTERNAL] SNMP shutdown timing out
Date: Mon, 4 May 2020 09:28:57
2008 Jul 11
3
mdadm --readonly which device in halt?
Setting up nut on a system where an LVM volume holds the root
filesystem.. What is the appropriate device form to use with "mdadm
--readonly" in halt? This is on a CentOS 5 system. So far I have found
three possibilities, but I do not know which one (if any) will still be
valid that late in the halt procedure:
1. /dev/md0 (from posts on the net)
2.
2008 Sep 04
1
method to simulate domain logon from a node?
I recently ran into a situation where a Samba upgrade apparently broke
the machine records in the smbpasswd file, with the resulting symptom
that domain logons on those computers would fail about 95% of the time.
(A very strange symptom, how it worked sometimes is still a mystery to
me.) Similarly, this would fail:
% smbclient -L saf01 -U 'saf/mathog%(password)'
session setup failed:
2006 Sep 12
1
Re: netlogon initially fails after moving samba server to new machine.
Well this is even more interesting. Parts of the profile are
not being saved back to the server, at least for existing
users. For instance,
1. login
2. change the start menu to "classic view"
3. rearrange the desktop
4. logout
5. login again
start menu is back as it was and it isn't classic view any more.
Very strange. Wipe the test profile on the server and the copy
on the
2023 Nov 27
1
APC Modbus support is finally here!
Jim Klimov <jimklimov+nut at gmail.com>
>
> I believe some fixes were applied to the branch since your report (most visibly, about battery time settings), are you in position to test how it behaves now? :)
Hi:
I got another ups for testing. so I test the new commit for both
APC SRT3000XL and SMT2200RM2U. the results below:
1. I get the new attribute "ups.test.result" for
2023 Nov 27
1
APC Modbus support is finally here!
Jim Klimov <jimklimov+nut at gmail.com>
>
> I believe some fixes were applied to the branch since your report (most visibly, about battery time settings), are you in position to test how it behaves now? :)
Hi:
I got another ups for testing. so I test the new commit for both
APC SRT3000XL and SMT2200RM2U. the results below:
1. I get the new attribute "ups.test.result" for
2006 Sep 12
2
netlogon initially fails after moving samba server to new machine.
Yesterday I migrated a Samba server from one machine running
Samba 3.0.13 (on Mandrake 10.0) to another running 3.0.20-3
(on Mandriva 2006). The contents of:
/etc/samba/* (all the .conf files)
/usr/local/samba/private/* (secrets.pdb, smbpasswd)
were moved intact from one machine to the other, as was all
of the user data. I even checked md5sums - no changes to any
of the samba files. Then
2010 May 12
1
upgraded 3.0.28a-2 to 3.4.7-0.2, profile desktop configuration no longer saved
Upgraded a Samba server from 3.0.28a-2 to 3.4.7-0.2. Initially the XP
workstations could not log on (not finding machine account) then
discovered a new "passdb" variable, so added to smb.conf:
passdb backend = smbpasswd
and also changed all browseable -> browsable. Restarted the server.
Domain logins worked. Test files saved to desktop are retained between
logins (are stored in
2008 Sep 02
3
upgrade broke XP workstation logins, variably
Help please, a file server was upgraded from:
Mandriva 2007.1, Samba 3.0.24-2.7mdv2007.1
to
Mandriva 2008.1, Samba 3.0.28a-2.1mdv2008.1
and it broke something badly.
After the upgrade logins from all XP workstations broke - some of the
time. For an existing account (one with a profile already in the home
directory) sometimes it will login normally. Well, almost normally, it
never seems
2010 May 27
4
fixed delay logging onto Samba3.3 from Vista Business
> The domain user does login eventually. Mostly. Roaming Profiles are
> very broken on W7: the top level "Vista.V2" directory is created, but
> nothing is stored back into it on the server, and the logged in domain
> user ends up with a C:\Users\Temp profile.
Thanks to Drew Vonada-Smith the roaming profiles are working again. The
problem was that information stored in
2010 May 18
0
Samba 3.4.7-0.2, Windows 7, roaming profile issues
After update from 3.0 to 3.4.7 roaming profiles were not being saved
on XP. Disabled ipv6 on our Samba server (some update must have
re-enabled it) and rebooted. Now profiles on XP seem to be working OK
again.
Not so for Windows 7. This is a newly set up Windows 7 machine,
registry fixes were applied as indicated here:
http://wiki.samba.org/index.php/Windows7
was able to join domain, and
2008 Sep 17
2
Slow "run as ...", firewall issues.
After doing some system work, including upgrading the Samba server to
3.0.28a from 3.0.24, upgrading the kernel to 2.6.24, and changing the
firewall rulesk, the XP workstations which belong to that domain, the
right click "run as ..." option is slow to bring up a dialog. The
phenotype is this:
right click some program (for instance, a shortcut to the
"command prompt")
2010 Sep 07
0
Semi-automated cloning using powershell scripts
Just in case anybody else ever needs these, here are my semi-automated
powershell cloning scripts for Windows domain clients for Samba domain
servers.
ftp://saf.bio.caltech.edu/pub/software/windows/Cloning.zip
They are not very polished, but do what I need, and could serve as a
starting point for other sites. These have been tested only on XP SP3.
These scripts do not use sysprep, so the
2008 Oct 16
2
usbhid-ups works, upsc doesn't - help?
Hi, Folks,
I'm new to this admin game, and one of the hardest parts for me is
figuring out where files/programs/data are stored in the file system.
I think this is one of these situations.
I've installed NUT on my Mac OS X 10.5 server, using the macports
build. The machine is a dual processor G4 tower, connected to an APC
UPS via USB.
usbhid-ups seems to be working, see output
1998 Dec 02
2
W95/98 connect to any SMB share as another user? (SAMBA dige
> Date: 30 Nov 1998 20:22:27 GMT
> From: mathog@seqaxp.bio.caltech.edu
> To: mlist-samba@nntp-server.caltech.edu
> Subject: W95/98 connect to any SMB share as another user?
> Message-ID: <73uuq3$s7j@gap.cco.caltech.edu>
>
> map H: as \\machine1\share1 as username=John, password=JohnsPassword map
> M: as \\machine2\share2 as username=Jane, password=JanesPassword
>
2024 Apr 24
1
CyberPower CST150UC: Question re: battery.runtime.low configuration settings
> Unfortunately, the SUCCESS response is just saying that upsrw was able to send that request to upsd (i.e. the username/password were correct). As you saw, the real proof is in what you read back from upsc.
Ah, gotcha.
> Have you tried any other values? 3600 is hex 0xe10, and 16 is 0x10, so it is quite possible the UPS is using an 8-bit field to store battery.runtime.low. I'm guessing
2024 Apr 23
1
CyberPower CST150UC: Question re: battery.runtime.low configuration settings
I would like to solicit some feedback re: the
battery.runtime.lowconfiguration settings through NUT. I was able to set
the value using the 'upsrw' command but when I did a 'upsc' the
configuration seems incorrect. Please see below for details. Thank you
OS name and version:
?? ?Description:??? Debian GNU/Linux 12 (bookworm)
?? ?Release:??????? 12
?? ?Codename:?????? bookworm