WannabeMKII

Members
  • Posts

    204
  • Joined

Posts posted by WannabeMKII

  1. Fix common problems is reporting that my parity drive is reporting read errors - Drive log attached.

     

    I've been an UNRAID user for 4 years now and love it, but this is the first time I've had a potential disk error. Would someone be able to check the log file for the drive please? If more info is needed, please let me know. If it is a potential drive failure, what are the correct steps to take to resolve?

     

    Many thanks.

    WDC_WD40EFRX-68WT0N0_WD-WCC4E2ND35EL-20201201-1729 parity (sdd).txt

  2. 8 minutes ago, axipher said:

    I believe its because your new UPS is reporting LOADPCT as "16.0 percent" instead of just "16.0".

     

    So your UPS is actually providing a String Value to the formula when it needs just an Integer or a Float number.  You might have to dig in the Grafana Dashboard code and help files to figure out how to strip that string value of the " percent" from the end of it in that formula.  Or maybe someone here can help with that.

     

    I had to do a custom User Script using CA User Scripts Plugin and the NUT-Settings Plugin instead of the built-in UPS Settings for my Eaton Rack-mount UPS because it was not providing any of the normally named tags and I had to modify all the Grafana charts to look for the new variables, but I didn't have to do any string manipulation like your new UPS would require.

     

     

    Hopefully I can at least point you in the right direction.

    Ouch, that sounds complicated. I'm hoping there's a more 'straightforward' solution...

  3. 9 hours ago, Frank1940 said:

    Why don't you ask for support in the support thread for this Docker?  (You left click on the Docker icon and select 'Support' from there.)

    Sorry, didn't think to post across there. I've done that now, so please feel to delete this thread. Many thanks.

  4. I've just replaced my UPS and the new UPS provides information that the old one didn't so Grafana should be more accurate. For example, nompower, loadpct, timeleft etc.

     

    However, something isn't quite right, as Grafana is actually reporting less and I'm thinking it's something to do with apcupsd still reporting the old information from the old UPS and not updating Influx with the new information?

     

    I've added a number of screenshots from what apcupsd shows, Grafana, Influx set up, Influx data sources and if I remove the nompower from the apcupsd-influx-exporter (this UPS reports nompower, the old on didn't), the log file.


    Can anyone assist please?

     

    Many thanks and stay safe!

    Screenshot 2020-04-10 at 17.35.34.png

    Screenshot 2020-04-10 at 17.36.07.png

    Screenshot 2020-04-10 at 17.42.07.png

    Screenshot 2020-04-10 at 17.44.17.png

    Screenshot 2020-04-10 at 17.47.20.png

  5. I've just replaced my UPS and the new UPS provides information that the old one didn't so Grafana should be more accurate. For example, nompower, loadpct, timeleft etc.

     

    However, something isn't quite right, as Grafana is actually reporting less and I'm thinking it's something to do with apcupsd still reporting the old information from the old UPS and not updating Influx with the new information?

     

    I've added a number of screenshots from what apcupsd shows, Grafana, Influx set up, Influx data sources and if I remove the nompower from the apcupsd-influx-exporter (this UPS reports nompower, the old on didn't), the log file.


    Can anyone assist please?

     

    Many thanks and stay safe!

     

     

    Screenshot 2020-04-10 at 17.35.34.png

    Screenshot 2020-04-10 at 17.36.07.png

    Screenshot 2020-04-10 at 17.42.07.png

    Screenshot 2020-04-10 at 17.44.17.png

    Screenshot 2020-04-10 at 17.47.20.png

  6. On 11/8/2019 at 5:33 PM, WannabeMKII said:

    Thanks for coming back. I've just deleted one of the SSL certificates and tried to re-create it and it came back with an 'internal error'?

     

    What else can I try?

    Quick update as I've managed to get it back up and running.

     

    Basically, I removed the container along with the appdata folder and started again. On starting again from scratch, everything is now back up and running!


    Many thanks for the help offered, appreciated!

  7. 21 hours ago, WannabeMKII said:

    Stupid question, but how would I test I can read it?

     

    Krusader is reporting the file as 0 bytes in size?

     

    Also, if I go into the webgui and try to edit one of the hosts and hit save, it comes back with a 'Internal Error'? 

     

    Does any of that help?

    Alternatively, is there a way I can create a new one?

  8. 9 hours ago, Djoss said:

    Looks like a certificate is corrupted.... You can check if you can read the certificate at /mnt/user/appdata/NginxProxyManager/letsencrypt/live/npm-1/fullchain.pem.

    Stupid question, but how would I test I can read it?

     

    Krusader is reporting the file as 0 bytes in size?

     

    Also, if I go into the webgui and try to edit one of the hosts and hit save, it comes back with a 'Internal Error'? 

     

    Does any of that help?

  9. I had an issue with another Docker image, so carried out a restore and I'm now seeing the following error in the logs;

     

    [nginx] starting...
    nginx: [emerg] PEM_read_bio_X509_AUX("/etc/letsencrypt/live/npm-1/fullchain.pem") failed (SSL: error:0909006C:PEM routines:get_name:no start line:Expecting: TRUSTED CERTIFICATE)

     

    Any ideas?

  10. Well, I was feeling brave and thought I'd turn the UPS off at the wall and hey presto, an alert from unraid that it was running on UPS. Perfect.

     

    Perhaps I'll hold fire on a new UPS as I left it off for about 13 mins when it hit about 50% before turning it back on. Also, as I've never seen an alert before in nearly 3 years of running unraid, I'm guessing things are pretty stable around here.

     

    I just like the nice UPS load reports etc in Grafana, but mind appear very static compared to everyone else.

     

    The fluctuations this evening are when it was running on battery. So it went onto battery about 6:30 for 1 min, then onto mains, then battery at 7:05 until about 7:15, then back to main.

     

    bXzR9re.png

  11. I'm based in the UK, so it looks like the model numbers vary slightly. For APC, this looks similar to what you have?

     

    With the CyberPower (minor typo in your footer of Cyperpower (unless it's a cheap Chinese knockoff)), it doesn't look like we have a UK equivalent, but this look nearest?

     

    Decisions decisions...

     

    Talking of which, is there a way that unraid can send me notifications whenever the UPS is triggered? My Synology NAS does in the showroom, but it would be great to have my unraid server in the office notify too as it's at a different location (about 5 miles away). Or is this also down to the UPS reporting it to unraid for the alert?

  12. Thanks for the feedback. I'll have to do some more research and try to find some real world feedback, as I don't fancy the trial and error approach at the moment.

     

    I think it would be really useful if either here, or somewhere else, there was a list of UPSs that people have used and has worked successfully? Perhaps a Google Sheet or something?

  13. My ageing (5 year old) UPS needs to be replaced before it stops working and now I have Grafana etc working along with apcupsd, it makes sense to make sure my new UPS provides this information as my current one doesn't.

     

    Is there a list or way to find which UPSs' are supported? For example, particular manufacturers or model ranges within a manufacturer to enjoy I get a UPS with full reporting?

     

    Many thanks.

  14. 7 hours ago, Djoss said:

    Looks like the file is not a valid certificate chain.  You can verify the file content at /mnt/user/appdata/NginxProxyManager/letsencrypt/live/npm-22/fullchain.pem

    Sorry, beginner question, but how do I verify it?

     

    Ignore this - I started again from scratch and all is now working fine.

  15. I needed to carry out an AppData restore last night, but since then, I'm seeing the following in the nginx logs;

    [nginx] starting...
    nginx: [emerg] PEM_read_bio_X509_AUX("/etc/letsencrypt/live/npm-22/fullchain.pem") failed (SSL: error:********:PEM routines:CRYPTO_internal:no start line:Expecting: TRUSTED CERTIFICATE)

    Any ideas what's caused this and how to resolve it, as I can't access remotely at the moment?

     

    Thanks.