Jump to content

Jajunk88

Members
  • Posts

    4
  • Joined

  • Last visited

Posts posted by Jajunk88

  1. On 8/26/2022 at 8:59 AM, Ludditus said:

    There are a couple ways to get the UPS data - USB connection or over the network.  Sounds like your UPS only has the network option.  You may need to connect the UPS directly to the network (router or switch) instead of to your server, then the server would point to the IP address of the UPS.  You can read about the different kind of connections at http://www.apcupsd.org/manual/#supported-upses-and-cables  -- sounds like you will be using SNMP.  The UNRAID UPS menu has options for ethernet/SNMP as well as the USB connection.

     

    Once you have the UPS data connected to UNRAID, telegraf should report it regardless of whether you are using a network or USB connection.

    So I tried all 3 ports on the UPS end plugged into my UDM router. I kept checking my UDM settings under "Wired" devices and never saw the UPS pop up in the menu, thus not getting on the internet. Not really sure how to get the UPS online. If this is an easy fix I'd love to go down this route, if it's a cumbersome process then it's not something I'll explore (it's a luxury). Thanks for your help here.

  2. 8 minutes ago, Ludditus said:

    Are you getting the UPS stats on the dashboard of your UNRAID server, like this?  image.png.2fb64fd3ce861d311eb3f63ac855d7e7.png

     

    If not, then you probably have some additional configuration to make sure that data is being received in UNRAID, if your UPS is capable of reporting and already connected to your UNRAID server via USB.  That's done on the Settings page under Systems Settings | UPS Settings.

     

    My recommendation would be to comment out that line until you have telegraf up and running - then you can experiment with changes to telegraf.conf and adding back in additional plugins by un-commenting those lines.

     

    Don't be afraid of editing the telegraf.conf file, it's pretty simple.  Most of it is just un-commenting sections that you want to add and changing default values/addresses to match your system. Just make sure you make a backup copy of a known working config file before you start editing, in case you need to roll back.  And, after each change you will either need to restart the telegraf service from the terminal, or restart the docker, to incorporate the change.

     

    Depending on your level of interest in Grafana/Influx, I found it very helpful to use InfluxDB Studio running on a Windows PC to see all of the measurements that were being stored in the database.  That let me see what was being recorded by telegraf in the database, which helped troubleshoot areas where I wanted to customize the UUD and other dashboards in Grafana.

    Hey thanks for the response. What you're saying makes sense. I think my UPS is limited in this capability though. I say that because there is no USB port to be found on the UPS. There are 3 ethernet ports - 1 reads Network In, 2 reads Network Out, and the 3rd reads Data Port. My thinking is that the Data Port ethernet connected to the server would give me this connection, however, there is only 1 ethernet port on my server (which is connected to my UDM). Seems like my setup is limited. Oh well. Again, thanks for the insight.

  3. 1 hour ago, Jajunk88 said:

    Hi - 

    I have meticulously gone through all of the documentation to set up the UUD. I have an issue with the Telegraf container not starting properly. After installing (with documentation steps implemented correctly) the container starts, and then it stops. When manually starting again, it stops. 

     

    I looked at the logs, and I notice this part sticking out - 

     

    [telegraf] Error running agent: Error loading config file /etc/telegraf/telegraf.conf: plugin inputs.cpu: line 3218: configuration specified the fields ["core_tags"], but they weren't used

     

    Another thing I noticed - Upon installation no Telegraph folder is created in the InfluxDB folder.

     

    I am a noob in this environment, so I don't want to start editing the telegraf config file and potentially breaking something. Does anyone have any advice or insight as to what I may be able to do here?

    Well, I commented out the ["core tags"] = false line in the [[inputs.cpu]] section in the telegraph config file. Now I'm getting a new error on the telegraf log. It reads:

     

    [inputs.apcupsd] Error in plugin: dial tcp 127.0.0.1:3551: connect: connection refused


    Has anyone run into this problem? Does the UPS have to be a "Smart UPS"? I'm not sure if my APC UPS 1000VA is capable of connecting to the internet...

  4. Hi - 

    I have meticulously gone through all of the documentation to set up the UUD. I have an issue with the Telegraf container not starting properly. After installing (with documentation steps implemented correctly) the container starts, and then it stops. When manually starting again, it stops. 

     

    I looked at the logs, and I notice this part sticking out - 

     

    [telegraf] Error running agent: Error loading config file /etc/telegraf/telegraf.conf: plugin inputs.cpu: line 3218: configuration specified the fields ["core_tags"], but they weren't used

     

    Another thing I noticed - Upon installation no Telegraph folder is created in the InfluxDB folder.

     

    I am a noob in this environment, so I don't want to start editing the telegraf config file and potentially breaking something. Does anyone have any advice or insight as to what I may be able to do here?

×
×
  • Create New...