On Sat, Jul 22, 2017 at 7:48 AM, Charles Lepple <clepple at gmail.com> wrote:> > I also have not used a Synology device, but as I recall, they generally > expect to be the NUT master system. This may cause problems if you need to > do something fancy with upssched. >The Synology boxes work fine as NUT clients, *however* they provide very little ability to configure NUT options. Specifically, the UPS name, username and password are all hard-coded (at least on DSM 6.x last time I looked at it), so the main NUT configuration on the NUT master must use these values for slaves: UPS - ups Username - monuser Password - secret Therefore protect the NUT network segment appropriately. --Larry -- Larry Fahnoe, Fahnoe Technology Consulting, fahnoe at FahnoeTech.com Minneapolis, Minnesota FahnoeTech.com -------------- next part -------------- An HTML attachment was scrubbed... URL: <lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20170722/c2b0410b/attachment.html>
Now I have some access problems. This is what ends up un messages Hosts.allow is set to accept anyone on the local net. Username and passwords are the same Upsc gives proper output. System is Centos 6.8 Jul 22 17:20:06 BIFROST upscode2[10113]: Startup successful Jul 22 17:20:06 BIFROST upsd[10116]: listening on ::1 port 3493 Jul 22 17:20:06 BIFROST upsd[10116]: listening on 192.168.0.1 port 3493 Jul 22 17:20:06 BIFROST upsd[10116]: listening on 127.0.0.1 port 3493 Jul 22 17:20:06 BIFROST upsd[10116]: Connected to UPS [R3000]: upscode2-R3000 Jul 22 17:20:06 BIFROST upsd[10117]: Startup successful Jul 22 17:20:06 BIFROST upsmon[10121]: Startup successful Jul 22 17:20:06 BIFROST upsmon[10122]: Login on UPS [R3000 at localhost] failed - got [ERR ACCESS-DENIED] With best regards [Beskrivning: ENRAD_logo_20K.bmp] Tomas Larsson CTO Enrad AB Verkstadsgatan 10 504 62 Bor?s Office: +46 33 297 550 Direct: +46 33 297 553 enrad.se<enrad.se> youtu.be/Dq9duakIjMU Enrad AB ing?r i Cleantech inn. Kluster f?r h?llbar global utveckling [Beskrivning: Clean Tech Inn]<cleantechinn.se> This e-mail message is confidential intended only for use of the addressees. If you have received this e-mail in error, please notify us immediately and delete it thereafter from your system. Any dissemination, distribution or copying of this e-mail is strictly prohibited. P T?nk p? milj?n innan du skriver ut. [cid:image003.jpg at 01D30310.A4A62BB0] Fr?n: Larry Fahnoe [mailto:fahnoe at fahnoetech.com] Skickat: den 22 juli 2017 15:10 Till: Charles Lepple Kopia: Tomas Larsson; nut-upsuser at lists.alioth.debian.org ?mne: Re: [Nut-upsuser] Compaq R3000h support On Sat, Jul 22, 2017 at 7:48 AM, Charles Lepple <clepple at gmail.com<mailto:clepple at gmail.com>> wrote: I also have not used a Synology device, but as I recall, they generally expect to be the NUT master system. This may cause problems if you need to do something fancy with upssched. The Synology boxes work fine as NUT clients, *however* they provide very little ability to configure NUT options. Specifically, the UPS name, username and password are all hard-coded (at least on DSM 6.x last time I looked at it), so the main NUT configuration on the NUT master must use these values for slaves: UPS - ups Username - monuser Password - secret Therefore protect the NUT network segment appropriately. --Larry -- Larry Fahnoe, Fahnoe Technology Consulting, fahnoe at FahnoeTech.com<mailto:fahnoe at FahnoeTech.com> Minneapolis, Minnesota FahnoeTech.com<FahnoeTech.com> -------------- next part -------------- An HTML attachment was scrubbed... URL: <lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20170722/9d0eeefe/attachment-0001.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 2725 bytes Desc: image001.png URL: <lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20170722/9d0eeefe/attachment-0001.png> -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 1427 bytes Desc: image002.jpg URL: <lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20170722/9d0eeefe/attachment-0002.jpg> -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 10122 bytes Desc: image003.jpg URL: <lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20170722/9d0eeefe/attachment-0003.jpg> -------------- next part -------------- A non-text attachment was scrubbed... Name: Tomas Larsson.vcf Type: text/x-vcard Size: 24120 bytes Desc: Tomas Larsson.vcf URL: <lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20170722/9d0eeefe/attachment-0001.vcf>
[please don't use HTML email unless needed.] sorry for the delay.> On Jul 22, 2017, at 11:33 AM, Tomas Larsson <tomas.larsson at enrad.se> wrote: > > Now I have some access problems. > This is what ends up un messages > Hosts.allow is set to accept anyone on the local net. > Username and passwords are the same > Upsc gives proper output. > System is Centos 6.8 > > Jul 22 17:20:06 BIFROST upscode2[10113]: Startup successful > Jul 22 17:20:06 BIFROST upsd[10116]: listening on ::1 port 3493 > Jul 22 17:20:06 BIFROST upsd[10116]: listening on 192.168.0.1 port 3493 > Jul 22 17:20:06 BIFROST upsd[10116]: listening on 127.0.0.1 port 3493 > Jul 22 17:20:06 BIFROST upsd[10116]: Connected to UPS [R3000]: upscode2-R3000 > Jul 22 17:20:06 BIFROST upsd[10117]: Startup successful > Jul 22 17:20:06 BIFROST upsmon[10121]: Startup successful > Jul 22 17:20:06 BIFROST upsmon[10122]: Login on UPS [R3000 at localhost] failed - got [ERR ACCESS-DENIED] >for upsmon-to-upsd access issues, you should to check that upsmon.conf is using a NUT login/password that is listed in upsd.users as having either "upsmon master" or "upsmon slave" privileges, as appropriate. If you change upsd.users, reload or restart upsd. networkupstools.org/docs/man/upsd.html networkupstools.org/docs/man/upsd.users.html