similar to: NUT under NAS4Free config issue

On Aug 21, 2013, at 10:41 AM, Incze Andras wrote: > Having the next problem, manually adding via WinSCP in the upsd.users file the user for remote monitoring, saving the file, WinNUT client connects after "upsd -c reload" in NAS4Free console, but if I restart the NAS4Free system, the slave user disappears from upsd.users and remains only the master user. > NAS4Free is version

Thanks, the strange is that I could set in this way the master user. At NAS4Free forum cannot get help, I presented the problem there too, but no real help. On Thu, Aug 22, 2013 at 2:19 AM, Charles Lepple <clepple at gmail.com> wrote: > On Aug 21, 2013, at 10:41 AM, Incze Andras wrote: > > > Having the next problem, manually adding via WinSCP in the upsd.users > file the

On Aug 22, 2013, at 5:15 AM, Incze Andras wrote: > Thanks, the strange is that I could set in this way the master user. That is odd. The development version of NAS4Free seems to be regenerating the entire upsd.users file: http://sourceforge.net/p/nas4free/code/848/tree/trunk/build/ports/nut/files/nut.sh.in To address your original concern (adding remote users for monitoring), I would

[forgot to include the list] Begin forwarded message: > From: Charles Lepple <clepple at gmail.com> > Subject: Re: [Nut-upsuser] NUT under NAS4Free config issue > Date: August 26, 2013 9:03:35 AM EDT > To: Incze Andras <andrisgazda at gmail.com> > > On Aug 26, 2013, at 8:08 AM, Incze Andras wrote: > >> Here is the result with the code inserted into script

Thank You very much !!! Now I see how was entered the master password in the file : "-v "concat(' password = ',//system/password)" -n \" I will test the proposed solution. Two questions - Do I need separate users for each WinNUT client or they can use the same user for monitoring&shutdown client machines ? - This is maybe a newbie question,

There is some problem with formatting :( If I paste how was written, the structure is wrong formatted, is putted somewhere right after the end of 1st part with master in the generated file. On Thu, Aug 22, 2013 at 3:32 PM, Charles Lepple <clepple at gmail.com> wrote: > On Aug 22, 2013, at 5:15 AM, Incze Andras wrote: > > > Thanks, the strange is that I could set in this way

On Aug 23, 2013, at 12:49 PM, Incze Andras wrote: > There is some problem with formatting :( > > If I paste how was written, the structure is wrong formatted, is putted somewhere right after the end of 1st part with master in the generated file. Can you be more specific? You can attach text files if needed. > On Thu, Aug 22, 2013 at 3:32 PM, Charles Lepple <clepple at

I'm trying to use a Nas4Free storage system. This same hardware worked fine on Freenas 0.7.2. O/S: Nas4Free 9.0.0.1.148 which comes with nut 2.6.4. UPS is an APC Back UPS RS 800. USB interface. Driver : usbhid-ups Port: auto my NAS is communicating with the UPS, but in testing power failures, I'm not getting the shutdown to be handled properly. When I pull the AC plug on the UPS,

Hello, I'm trying to integrate HAST to NAS4Free (FreeBSD 9.1-RC3). Now I have created version 9.1.0.1.531. http://sourceforge.net/projects/nas4free/files/NAS4Free-9.1.0.1/9.1.0.1.531/ Basic CARP + HAST + iSCSI target setup can be done, but very frequently I get hastctl hang when called: /sbin/hastctl status /sbin/hastctl dump Is it better for this method not to call from a script? or

I'm using Nas4Free, and I'm getting the following message all the time in the Daemon log: usbhid-ups[42466]: libusb_get_report: Unknown Error I'm running Nas4Free 9.2.0.1 Shigawire Driver usbhid-ups Nut Version is 2.7.1 Internal verion 0.38 UPS Info from Nas4Free Manufacturer:CP1500PFCLCD Model:CRCA102*AF1 The model UPS I'm running is a Cyber Power CP1500PFCLCD, other

I've setup nas4free (latest version 11.0.0.4, which has NUT 2.7.4) in a VM and configured it via webinterface to my APC UPS and set "shutdown mode" to "UPS goes on battery" with a timer of 30s. Then I started runtime calibration on the UPS and after 30s nas4free has shut down! I think this is not the correct behavior, since the status was "OB CAL". The system

I have gotten the links to the ./configure for NUT for NAS4Free see nas4free build makefile http://sourceforge.net/p/nas4free/code/ ... t/Makefile config files: http://sourceforge.net/p/nas4free/code/ ... nut/files/ I hope this give some insights On Wednesday, August 19, 2015 6:00 AM, Charles Lepple <clepple at gmail.com> wrote: On Aug 19, 2015, at 12:08 AM, Johnny Wong

OS = NAS4Free (FreeBSD Revision: 199506) NUT Version = 2.7.3 for other parts of NUT version is listed below NUT is part of the NAS4Free distribution Device = Tripp Lite SMART1300LCDT URL http://www.tripplite.com/line-interactive-ups-system-desktop-tower-1300va-120v-usb-port-lcd-screen~SMART1300LCDT/ PROBLEM: NUT is ABLE to see the UPS BUT it is not getting the right(?) descriptor? I am using

> What does that revision number correspond to in FreeBSD release numbers? (e.g. 9.3, 10.0) FreeBSD 10.2-RELEASE #0 r286738M the last person probably wasn't able to give the ./configure probably because most people uses the precompiled iso to install NAS4Free.? if you need the ./configure I might have to look for their source on GitHub or something. /usr/local/libexec/nut/usbhid-ups -a

>> >> I need some help here with getting this thing running. Every time I enable NUT on the server, I get a "on battery" status when I know that it is running on house power. This only occurs when I am monitoring it with FreeBSD(NAS4Free) > >Which version of FreeBSD is this based on? I also included the Motherboard and processor so if there is anything those

Hello, I would like to use nas4free under xcp 1.6. I install it under full HVM using "other install media". Now I am attaching 4 hdds as external disks. The vm sees at most two hdds, I suppose because of bios support (1 boot + 1 cdrom + 2 hdds= 4 hdds). I need to use more disks, is it possible? If not, it seems to me a serious limit. Mario

I need some help here with getting this thing running. Every time I enable NUT on the server, I get a "on battery" status when I know that it is running on house power. This only occurs when I am monitoring it with FreeBSD(NAS4Free) When i plug the same UPS into CentOS 6.7, It works as expected. I am not sure what the difference between the NUT versions other than the base OS would be.

I am trying to allow users with permissions in one group (DEV) to have full access to a folder that is owned by (QA). I have not been able to figure this out. Its running samba 4.2 in WORKGROUP mode (I can find everything for domain but I am not ready for that). Its running on freebsd on the latest nas4free build NAS with a ZFS file system.. Thanks in advance Frank Kahle FileCatalyst |

Hello all, I am looking to setup a Samba AD on my NAS. I am currently using the latest version of NAS4Free which has Samba bundled into it already. However, I am getting a very nasty error when I go in to setup the samba service: Initializing... Looking up IPv4 addresses Looking up IPv6 addresses No IPv6 address will be assigned Setting up share.ldb Setting up secrets.ldb Setting up the

But if Samba AD does not work on the ZFS filesystem, then why bundle it with the NAS4Free OS? What filesystems does the Samba AD support? On Thu, Jul 6, 2017 at 10:54 AM, Andrew Walker via samba < samba at lists.samba.org> wrote: > Yes. I imagine that's why Andrew Bartlett commented: "There may be some > good news in the future, as I've had one of the developers at