search for: filesrv01

On Mon, 25 Mar 2024 07:39:21 +0100 Kai via samba <samba at lists.samba.org> wrote: > Hello everyone, > > I have a Samba setup with an AD controller (DC01) and set up a second > system which should work as file share (filesrv01). > I was setting it up using this manual: > https://wiki.samba.org/index.php/Setting_up_a_Share_Using_Windows_ACLs > > Somehow, I broke the administrator's account. No, I doubt if you have. > After I set up a test > share, I got RPC server unavailable errors. I started...

...se tests... Yes, I've tried this as well with worse results unfortunately. This driver seems to be even more unstable. When it gets able to set communication with the UPS (which is not always the case), it usually lost it again after a while. ~# /usr/local/libexec/nut/oldmge-shut -DD -a ups-filesrv01 Network UPS Tools - Eaton / SHUT driver 0.70 (2.7.2) 0.000000 debug level is '2' 0.000882 entering upsdrv_initups() 0.001019 entering shut_ups_start() 0.028445 Communication with UPS established 0.028457 entering shut_get_descriptor(n 21, 9) 0.11...

Hello everyone, I have a Samba setup with an AD controller (DC01) and set up a second system which should work as file share (filesrv01). I was setting it up using this manual: https://wiki.samba.org/index.php/Setting_up_a_Share_Using_Windows_ACLs Somehow, I broke the administrator's account. After I set up a test share, I got RPC server unavailable errors. I started investigating and found test commands like this: rpcclien...

...schrieb Rowland Penny via samba: > On Mon, 25 Mar 2024 07:39:21 +0100 > Kai via samba<samba at lists.samba.org> wrote: > >> Hello everyone, >> >> I have a Samba setup with an AD controller (DC01) and set up a second >> system which should work as file share (filesrv01). >> I was setting it up using this manual: >> https://wiki.samba.org/index.php/Setting_up_a_Share_Using_Windows_ACLs >> >> Somehow, I broke the administrator's account. > No, I doubt if you have. > >> After I set up a test >> share, I got RPC server un...

...5 5SC Serial with mge-shut driver) is working initially, almost after every reboot, the driver is failing with the message "UPS failed - Driver not connected". This was not the case with FreeNAS 9.2 and NUT 2.7.1. Additional information: ~# /usr/local/libexec/nut/mge-shut -DD -a ups-filesrv01 Network UPS Tools - Generic HID driver 0.38 (2.7.2) SHUT communication driver 0.84 Warning: This is an experimental driver. Some features may not function correctly. 0.000000 debug level is '2' 0.000901 upsdrv_initups... 0.000911 libshut_open: using port /dev/cuau0...

...as well with worse results unfortunately. > This driver seems to be even more unstable. When it gets able to > set communication with the UPS (which is not always the case), it > usually lost it again after a while. > > ~# /usr/local/libexec/nut/oldmge-shut -DD -a ups-filesrv01 > Network UPS Tools - Eaton / SHUT driver 0.70 (2.7.2) > 0.000000 debug level is '2' > 0.000882 entering upsdrv_initups() > 0.001019 entering shut_ups_start() > > 0.028445 Communication with UPS established > 0.0284...

...rking initially, almost after every reboot, > the driver is failing with the message "UPS failed - Driver not > connected". This was not the case with FreeNAS 9.2 and NUT 2.7.1. > > Additional information: > > ~# /usr/local/libexec/nut/mge-shut -DD -a ups-filesrv01 > Network UPS Tools - Generic HID driver 0.38 (2.7.2) > SHUT communication driver 0.84 > Warning: This is an experimental driver. > Some features may not function correctly. > > 0.000000 debug level is '2' > 0.000901 upsdrv_initups....

...9;ve tried this as well with worse results unfortunately. This driver > seems to be even more unstable. When it gets able to set communication with > the UPS (which is not always the case), it usually lost it again after a > while. > > ~# /usr/local/libexec/nut/oldmge-shut -DD -a ups-filesrv01 > Network UPS Tools - Eaton / SHUT driver 0.70 (2.7.2) > 0.000000 debug level is '2' > 0.000882 entering upsdrv_initups() > 0.001019 entering shut_ups_start() > > 0.028445 Communication with UPS established > 0.028457 entering shut_get...

...iver) is > working initially, almost after every reboot, the driver is failing with > the message "UPS failed - Driver not connected". This was not the case with > FreeNAS 9.2 and NUT 2.7.1. > > Additional information: > > ~# /usr/local/libexec/nut/mge-shut -DD -a ups-filesrv01 > Network UPS Tools - Generic HID driver 0.38 (2.7.2) > SHUT communication driver 0.84 > Warning: This is an experimental driver. > Some features may not function correctly. > > 0.000000 debug level is '2' > 0.000901 upsdrv_initups... > 0.000911...

...ell with worse results unfortunately. This >> driver seems to be even more unstable. When it gets able to set >> communication with the UPS (which is not always the case), it usually lost >> it again after a while. >> >> ~# /usr/local/libexec/nut/oldmge-shut -DD -a ups-filesrv01 >> Network UPS Tools - Eaton / SHUT driver 0.70 (2.7.2) >> 0.000000 debug level is '2' >> 0.000882 entering upsdrv_initups() >> 0.001019 entering shut_ups_start() >> >> 0.028445 Communication with UPS established >> 0...

...unfortunately. This driver seems to be even more unstable. >> When it gets able to set communication with the UPS (which is >> not always the case), it usually lost it again after a while. >> >> ~# /usr/local/libexec/nut/oldmge-shut -DD -a ups-filesrv01 >> Network UPS Tools - Eaton / SHUT driver 0.70 (2.7.2) >> 0.000000 debug level is '2' >> 0.000882 entering upsdrv_initups() >> 0.001019 entering shut_ups_start() >> >> 0.028445 Communica...