backup mail report says INTERRUPTED but it's not ?
-
@Pilow said in backup mail report says INTERRUPTED but it's not ?:
@florent not really, it is activated and I tried to fiddle a bit with it, why ?
the smaller the changes, the more we can focus on the right component(s). And december release was quite massive ( a good consequence of the team growing)
can you disable it to be sure ?again, thank you for your help here
-
@florent okay disabled.
We have quite an extensive use of API calls too, all over the place
and websockets (to get VM console in in-house web app)I don't know if this could have an impact
-
@Pilow I think I remember that you have a xoa ? would it be ok to open a support tunnel a give me the number by the chat ( or by a support ticket ) ?
are you querying on of the dashboard or only the individual CRUD api ? rest api or xo cli ?
We could add some debug
-
@florent I am also experiencing this on XOA and can send you a support tunnel number if you'd like. I rebooted it Sunday night after sharing the screenshot of memory usage above in this thread but it is slowly growing again. It used to crash and restart every 3 days but with --max-old-space-size=12288 i get around 7-8 day now before its an issue.
-
@flakpyro yes, with pleasure
do you also use the rest api / xo6 ?
do you use proxies ? -
@florent Not using the API but we have two Proxies.
-
@florent rest and xo-cli
tunnel ID sent by message -
thanks guy, I will connect in a few hours, and we will investigate tomorrow all day with @mathieura
-
From my XOA
One of my pools have been offline for 24hrs due to power outage.
Standard XOA can open support tunnel if needed.
-
On tomorrow 's release we will:
- reduce the polling for the patches list
- add more debug to know exactly what request go through the xo6 api (rest api)
following this we will add core xo metrics to the openmetrics ( prometheus) export to allow users and support to dig through real world data when needed
-
@florent thanks for working on this!
-
@florent since your early patch of my XOA (xo-server restart at the disk activity peak)
noticing vif0 transmitting a bit on the network and different ram activity on a timespan of 2 hours
something has changed, is it for the better ?
let the night decide
