search for: omvs

Hello, Replaced UPS Kstar Micropower Micro 1200 (managed via blazer_usb) with https://www.njoy.ro/UPS/horus-plus-2000. The latter doesn't seem to be supported. 1. I tried blazer_usb and usbhid-ups. Any other suggestions? 2. What would be needed to get it supported by NUT? ======== HW ======== HP Microserver Gen 8 ======== UPS ======== Working:Kstar Micropower Micro

Hello, No ttyUSB* device under /dev however the new driver has detected the UPS, the nut services are able to start, just "upsc -l ups" sais unknown error and doesn't return any information. Could be due to the driver unable to detect number of battery packs as reported by the nut-driver.service startup? How can I fix that? root at omv:~# systemctl status nut-driver.service●

Hi Virtualizers, I just setup a CentOS 6 box (at home) to run as a KVM host. It's replacing an absolutely ancient CentOS 5 server that's running Xen. I have one OS drive, and two drives in RAID 1 with LVM on top which is being used as the KVM storage pool. I created a KVM that will run OpenMediaVault (OMV). OMV requires an OS drive (which is really a LVM), and a separate drive(s) to

Hello list. I'm doing nightly syncs over SSH with rsnapshot, and now rsync gives me strange errors, like: rsync: failed to connect to localhost: Connection refused (111) rsync error: error in socket IO (code 10) at clientserver.c(122) [receiver=3.0.3] ------------------------------------------------------------------------ ---- rsnapshot encountered an error! The program was invoked with

On 20/05/2019 19:47, Hendrik Friedel wrote: > Hello, > >>>> You posted this: >>>> I am using Openmediavault (debian based NAS distribution), which is >>>> not actively supporting btrfs >>>> It is this that I was referring to. >>> Ah, yes. >>> OMV intended to move to btrfs as the only choice with the next >>>

On 20/05/2019 18:54, Hendrik Friedel wrote: > Hello, > >> Is btrfs becoming more common ? > In my impression: Yes. Also, this problem seems to affect also zfs and > thus all (?) file systems that support checksums and scrubbing in > linux; consequently all filesystems that are the choice of users who > need this for ensuring data consistency. Not from my experience, but,

Hi, I'm working hard to setup winbind and openLDAP work together with TLS My networks contains: - a windows server 2008 R2 domain controller - a debian 6 based file server (openmediavault v0.4) running OpenLDAP 2.4.23 and Samba v3.5.6 - a debian 7 computer running winbind 3.6.6 I want to let OpenLDAP store SID <=> uig/gid mapping to ensure constant uid and gid for users on all linux

By side effect, lack of "killpower" touch file works to not-tell the OS shutdown integration on OMV to turn off the UPS. A more proper way about this is generally to change MONITOR back-ups 1 monmaster 4L[p9<0Vi|Z>xKgK master (see my earlier message or docs about primary/master vs. secondary/slave clients), to MONITOR back-ups 1 monmaster 4L[p9<0Vi|Z>xKgK slave and it

Hello, I am try to get my "new" UPS running with NUT on my OpenMediaVault device but only receive error meassages on several configurations I try. Your support is really appreciated for getting it solved. Best Regards, Olaf *lsusb* Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID

Hello, We are running OS/390 version 1.3 with samba 1.9.15p8. We would like to add security to our current release, But when I put 'security = user ' in the config file and trying to enter I don't get an existing user-id although my PC user-id is the same as my MVS one. HELP !!! Any advice Or a simple config file working with Samba security Vs. Racf it would be highly appreciated.

Hello, >> In my impression: Yes. Also, this problem seems to affect also zfs and > > I'm mostly interested in the claim that ZFS is affected. > I haven't followed this thread carefully, but what exactly is the problem we're > talking about, and how do we know it impacts ZFS? > [Something more than a single one-liner in that bug report?] Indeed, I only find

This PowerCOM device (0d9f:0004) is not (or perhaps not yet) supported by usbhid-ups. Please make sure you have an up-to-date version of NUT. If this does not fix the problem, try running the driver with the '-x productid=0004' option. Please report your results to the NUT user's mailing list <nut-upsuser at lists.alioth.debian.org>. No matching HID UPS found Driver failed to

Hello, >>>You posted this: >>>I am using Openmediavault (debian based NAS distribution), which is not actively supporting btrfs >>>It is this that I was referring to. >>Ah, yes. >>OMV intended to move to btrfs as the only choice with the next version. In order to pave the way, I intended to be an early adopter. The problem I report here, that there is good

On 18/05/2019 14:19, Hendrik Friedel wrote: > Hello > >> No, probably a lack of users using your combination of Samba, btrfs >> and quotas. > I would have thought that btrfs is becoming more mainstream now. And > then, Samba and Quotas should be rather common... >> Is btrfs becoming more common ? > >> Of course, more info may help, what is in your smb.conf

Hi there, I tried all the driver on the list for this UPS, but they don?t work. Could you help me please? INFO: OMV 2.2.14 (Stone burner) Debian Release 7.11 - Linux nas01 3.2.0-4-amd64 Debian 3.2.93-1 x86_64 GNU/Linux HPE ProLiant Gen8 G1610T 819185-421 4GB RAM MicroServer NUT 2.0 installed from the Plugin Panel of OMV APC Back-UPS 390 Watts / 700 VA, 230V, AVR, IEC Sockets Best regards mikael

THIS IS systemctl list-units | grep UPS nut-driver at back-ups.service

This is the first time that i had to use E-mail like forums i'm only hitting reply to mail NOT replay to all mails THIS IS upssched.conf # This file is auto-generated by openmediavault (https://www.openmediavault.org) # WARNING: Do not edit this file, your changes will get lost. CMDSCRIPT /usr/bin/upssched-cmd PIPEFN /run/nut/upssched.pipe LOCKFN /run/nut/upssched.lock AT COMMOK * EXECUTE

On Jun 17, 2013, at 5:32 AM, Yuriy Yurev wrote: > This PowerCOM device (0d9f:0004) is not (or perhaps not yet) supported > by usbhid-ups. Please make sure you have an up-to-date version of NUT. If > this does not fix the problem, try running the driver with the > '-x productid=0004' option. Please report your results to the NUT user's > mailing list <nut-upsuser at

device -Powercom model: BNT-800A 17 ???? 2013, ? 14:55, Charles Lepple <clepple at gmail.com> ???????(?): > On Jun 17, 2013, at 5:32 AM, Yuriy Yurev wrote: > >> This PowerCOM device (0d9f:0004) is not (or perhaps not yet) supported >> by usbhid-ups. Please make sure you have an up-to-date version of NUT. If >> this does not fix the problem, try running the driver

Hi Stuart, I am using OpenMedaVault and purchased the Tripp-Lite SMART1300LCDT. I can't get it to work with OMV. Any ideas for me? I posted a request on the OMV community but no answers. Any direction would be appreciated. Thanks, Roman -------------- next part -------------- An HTML attachment was scrubbed... URL: