search for: afs1

Displaying 5 results from an estimated 5 matches for "afs1".

Did you mean: afs
2013 Dec 07
2
APC Smart-UPS 1500; system shutdown is not initiated.
Dear list, I have an APC Smart-UPS 1500 hooked up via the USB port. Recently, when we had a power outage, the only entry in the logs was: Dec 3 14:43:43 afs1 upsmon[3035]: UPS apc at localhost on battery and then the machine seems to have run until the battery was empty. It only notices the "battery low" after I turn the system back on: Dec 3 16:01:39 afs1 usbhid-ups[21973]: Startup successful Dec 3 16:01:39 afs1 upsd[21975]: listening on...
2013 Dec 09
0
APC Smart-UPS 1500; system shutdown is not initiated.
On Dec 7, 2013, at 2:38 PM, Christian wrote: > Dear list, > > I have an APC Smart-UPS 1500 hooked up via the USB port. Recently, when > we had a power outage, the only entry in the logs was: > > Dec 3 14:43:43 afs1 upsmon[3035]: UPS apc at localhost on battery > > and then the machine seems to have run until the battery was empty. It > only notices the "battery low" after I turn the system back on: [...] > Occasionally, i get these in daemon.log: > Dec 4 03:11:54 afs1 usbhid-ups[21...
2020 Feb 09
0
wbinfo -r reports strange gids on AD member
...t;>>>> net cache flush >>>>> systemctl stop samba winbind >>>>> systemctl start samba winbind >>>>> >>>>> id some_user >>>>> getent passwd some_user >>>>> >>>>> [..] >>>> afs1:~# net cache flush >>>> afs1:~# systemctl stop smbd winbind >>>> afs1:~# net cache flush >>>> afs1:~# systemctl start smbd winbind >>>> afs1:~# id some_user >>>> uid=10586(some_user) gid=10206(group1) >>> groups=10206(group2),105...
2013 Dec 09
2
APC Smart-UPS 1500; system shutdown is not initiated.
Charles, thanks for your detailed answer. >> Occasionally, i get these in daemon.log: Dec 4 03:11:54 afs1 >> usbhid-ups[21973]: libusb_get_interrupt: could not claim interface >> 0: Device or resource busy > > This isn't great, but I don't think it's related. > > It is normal to get a "could not claim interface 0" error once after > the USB cable is...
2010 Mar 26
1
Winbind eventually locks "forever" if one of ActiveDirectory refuses all connections
...So it seems that when one ad server is restarted, winbind does not like it and errors, and stops listening on that pipe, and when any communication happens (sid-uid lookups), since no one is responding on that pipe/socket, it hangs. This is with samba 3.4.5 our samba config: netbios name = nimdev-afs1 workgroup = <redacted> security = ads realm = <redacted> kerberos method = system keytab idmap backend = hash idmap uid = 4000-100000000 idmap gid = 4000-100000000 winbind enum users = yes winbind enum groups = yes auth methods = w...