Jump to content

[Support] Fork Unraid API-RE


Recommended Posts

Posted (edited)
7 minutes ago, emilgil said:

As an environment variable when launching the container or in the GUI?

@emilgil env variable in the template. 20 000 should be 20 seconds

6 minutes ago, Puntoboy said:

 

6.12.10

I don't see that path on my server. This is my container setup.

 

image.thumb.png.ffee45be1a20dcd7a26e0c48debd46c5.png

image.png.8f594808e8c2cf56f8107ac2629b2136.png

 

 

Also you are running the tag 6.11 with unraid 6.12. They have to match

Edited by BoKKeR
  • Like 1
Link to comment
6 minutes ago, BoKKeR said:

@emilgil env variable in the template. 20 000 should be 20 seconds

image.png.8f594808e8c2cf56f8107ac2629b2136.png

 

 

Also you are running the tag 6.11 with unraid 6.12. They have to match

 

Thanks, there's nothing in the documentation I read that explains that. :)

I've made those changes, just downloading the new container.

Edited by Puntoboy
Link to comment
11 minutes ago, Puntoboy said:

 

Thanks, there's nothing in the documentation I read that explains that. :)

I've made those changes, just downloading the new container.

Its in the first post in this thread, and in the Github readme. I will add it to the template and the webpage

Link to comment
24 minutes ago, BoKKeR said:

@emilgil env variable in the template. 20 000 should be 20 seconds

 

According to the wiki the RefreshRate is in seconds and 20 s is the default value? 

 

If I omit it, I get a 30 s refresh rate. 😕

 

Edit: even if I set the RefreshRate variable to 20 or 20000, I get a 30 s poll time.

 

 

Edited by emilgil
Link to comment
2 minutes ago, BoKKeR said:

Its in the first post in this thread, and in the Github readme. I will add it to the template and the webpage

 

There is a link on the first page, you are right, it's just not very clear that the version has to match your install. I read it as the container version, not the unraid version :)

Link to comment

To see if there was a problem with the Unraid container, I deployed the one on HA. I get the same now, only seeing the single docker container in the WebUI (no other details about the Unraid server) and I've seeing these errors in the logs. When I restart the add-on the Unraid server details disappear. I assume something to do with this? 

image.png.a1249fe256de5fe50da565e7af0c9392.png

so the two issues I have are:

 

1. The Docker WebUI only shows the docker container status.
image.png.024236068e8347c40a4ddd97fb76cfd9.png
2. Home Assistant isn't getting any MQTT data (I can see the successful connection, but that's it)

Link to comment

Hi there, I'm using the 6.12 tag docker image, but i'm getting a 503. Output HTML variable shows "Browser cookie support required for Unraid OS webgui"

Also - any way to send this over WS for homeassistant as an option (not a top priority totally understand!)

Link to comment
  • 2 weeks later...

Starting a while back (not exactly sure when) my server basically DoS'es itself, logs gets filled with the line below which is the Unraid-api docker and the webgui of Unraid goes highly unstable/offline. It does work for a while when you start it up though (couple of hours or so)

 

May 10 18:16:19 TARDIS nginx: 2024/05/10 18:16:19 [error] 28398#28398: *2850557 limiting requests, excess: 20.731 by zone "authlimit", client: 172.17.0.21, server: , request: "GET /login HTTP/1.1", host: "192.168.0.20"

 

Any thoughts of why it does such an insane amount of requests?

Link to comment
  • 4 weeks later...

Hi

 

I just stumble on a small issue i cannot find the solution to so i post it here if anyone has an answer.

 

When adding my own custom template for a docker (not via gui docker browser) the docker doesnt report status after HA restart. If i turn it on or off it gets reported as it should. Also restarting the unraidapi docker fixes it. The dockers installed via "docker store" gui works fine.

 

And its actually the same for my WM.

 

Anyone has any feedback or fix for this?

 

image.png.bb0c625ca8ae1b7118b88e8f94920654.png

 

image.png.b91ebd0a65d82630addbc10e3f804cf1.png

 

Edited by ABEIDO
Link to comment
  • 1 month later...

It seems that the Unraid API RE Docker with the new Unraid 6.12.11 Version triggers a shutdown if the Dynamix System Buttons plugin is also installed.

It causes the system to simply reboot or shut down as soon as the array is running. I had to go back to 6.12.10 to get the system running normally again

Quote

Jul 17 00:36:59 Tower autofan: Highest disk temp is 40C, adjusting fan speed from: 70 (27% @ 791rpm) to: 185 (72% @ 1138rpm)
Jul 17 00:36:59 Tower autofan: Highest disk temp is 40C, adjusting fan speed from: 70 (27% @ 792rpm) to: 165 (64% @ 1076rpm)
Jul 17 00:37:00 Tower autofan: Highest disk temp is 40C, adjusting fan speed from: 70 (27% @ 1704rpm) to: OFF (0% @ 393rpm)
Jul 17 00:37:35 Tower webGUI: Successful login user root from 172.17.0.2
Jul 17 00:37:40 Tower emhttpd: cmdStart: already started
Jul 17 00:37:40 Tower kernel: mdcmd (37): check correct
Jul 17 00:37:40 Tower kernel: md: recovery thread: check P Q ...
Jul 17 00:37:42 Tower emhttpd: shcmd (180): /usr/local/sbin/mover |& logger -t move &
Jul 17 00:37:42 Tower root: Starting Mover
Jul 17 00:37:42 Tower root: Forcing turbo write on
Jul 17 00:37:42 Tower kernel: mdcmd (38): set md_write_method 1
Jul 17 00:37:42 Tower kernel: 
Jul 17 00:37:42 Tower root: ionice -c 2 -n 0 nice -n 0 /usr/local/sbin/mover.old 
Jul 17 00:37:42 Tower move: mover: started
Jul 17 00:37:42 Tower move: file: /m****
Jul 17 00:37:42 Tower move: move_object: /****.mkv File exists
Jul 17 00:37:42 Tower move: file: /****
Jul 17 00:37:44 Tower nginx: 2024/07/17 00:37:44 [error] 27399#27399: *2200 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 172.17.0.2, server: , request: "GET /plugins/dynamix.s3.sleep/include/SleepMode.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "192.168.0.***"
Jul 17 00:37:44 Tower shutdown[31572]: shutting down for system reboot
Jul 17 00:37:44 Tower shutdown[31570]: shutting down for system halt
Jul 17 00:37:44 Tower shfs: copy_file: /mnt/cache/*** /mnt/disk3/*** (28) No space left on device
Jul 17 00:37:44 Tower move: move_object: /mnt/cache/*** Connection refused
Jul 17 00:37:44 Tower move: file: /mnt/cache/***
Jul 17 00:37:45 Tower init: Switching to runlevel: 0
Jul 17 00:37:45 Tower init: Switching to runlevel: 6
Jul 17 00:37:45 Tower init: Trying to re-exec init
Jul 17 00:37:45 Tower kernel: docker0: port 1(veth3ceaf1e) entered disabled state

IP 172.17.0.2 is the Unraid-API RE Docker. 

The Error triggert on 00:37:44. 

Link to comment
  • 2 weeks later...

Hi

 

Addon seems stopped working here.

Although the addon says its connected to the server, this i see in log:

Get Main Details for ip: 192.168.1.117 Failed
Request failed with status code 503
Error: ENOENT: no such file or directory, open 'config/mqttDisabledDevices.json'
    at Object.openSync (node:fs:590:3)
    at Object.readFileSync (node:fs:458:35)
    at updateMQTT (/app/mqtt/index.ts:388:21)
    at Timeout._onTimeout (/app/mqtt/index.ts:433:5)
    at listOnTimeout (node:internal/timers:559:17)
    at processTimers (node:internal/timers:502:7) {
  errno: -2,
  syscall: 'open',
  code: 'ENOENT',
  path: 'config/mqttDisabledDevices.json'
}
<html>
<head><title>503 Service Temporarily Unavailable</title></head>
<body>
<center><h1>503 Service Temporarily Unavailable</h1></center>
<hr><center>nginx</center>
</body>
</html>

Link to comment
  • 2 weeks later...
Posted (edited)

I tested it on my test VM and it works on 6.12.11, the only thing that is broken is that the version does not report properly. Otherwise stopping array, start/stop containers and vm-s are tested.

 

@skankThe error you are getting might be related to the service overloading your server and your server returning a 503. I have plans on adding a backoff strategy in case the requests start failing but I havent had time to do it yet...

 

Edited by BoKKeR
Link to comment
  • 2 weeks later...

Hi @BoKKeR..

 

I'm experiencing an odd behaviour. Whenever the Unraid-API docker runs, it generates a lot of load on CPU and almost doubles my power consumption.

 

I already increased the mqtt update rate to 60s, but this just slightly improves the power consumption.

 

Any suggestions?

Link to comment

Okay, somehow the issue with the cpu load is gone.. but I am missing some information with unraid 7..

Is there any work in progress? RAM usage is at 0%. CPU load is enterily missing, am I correct?

Edited by giganode
Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...