Homepage v0.8.11 is slower and uses a lot of CPU

[deimjons]

Description

Hello.
After updating the Homepage to v0.8.11 it started to work slower and used a lot of CPU.

The logs do not show anything suspicious. All errors are about turned off services.
Do you know where there could be a problem?

homepage version

v0.8.11

Installation method

Docker

Configuration

No response

Container Logs

}
]
[2024-04-16T15:58:14.745Z] error: Error calling http://librephotos-proxy/...
[2024-04-16T15:58:14.745Z] error: [
500,
Error: getaddrinfo ENOTFOUND librephotos-proxy
at GetAddrInfoReqWrap.onlookupall [as oncomplete] (node:dns:118:26) {
errno: -3008,
code: 'ENOTFOUND',
syscall: 'getaddrinfo',
hostname: 'librephotos-proxy'
}
]
[2024-04-16T15:58:14.745Z] error: Error calling http://prometheus:9090/...
[2024-04-16T15:58:14.746Z] error: [
500,
Error: getaddrinfo ENOTFOUND prometheus
at GetAddrInfoReqWrap.onlookupall [as oncomplete] (node:dns:118:26) {
errno: -3008,
code: 'ENOTFOUND',
syscall: 'getaddrinfo',
hostname: 'prometheus'
}
]
[2024-04-16T15:58:14.755Z] error: Error calling http://lemmy/...
[2024-04-16T15:58:14.755Z] error: [
500,
Error: getaddrinfo ENOTFOUND lemmy
at GetAddrInfoReqWrap.onlookupall [as oncomplete] (node:dns:118:26) {
errno: -3008,
code: 'ENOTFOUND',
syscall: 'getaddrinfo',
hostname: 'lemmy'
}
]
[2024-04-16T15:58:14.795Z] error: Error calling http://calibre-web:8083/...
[2024-04-16T15:58:14.795Z] error: [
500,
Error: getaddrinfo ENOTFOUND calibre-web
at GetAddrInfoReqWrap.onlookupall [as oncomplete] (node:dns:118:26) {
errno: -3008,
code: 'ENOTFOUND',
syscall: 'getaddrinfo',
hostname: 'calibre-web'
}
]
[2024-04-16T15:58:14.796Z] error: Error calling http://lazylibrarian:5299/...
[2024-04-16T15:58:14.797Z] error: [
500,
Error: getaddrinfo ENOTFOUND lazylibrarian
at GetAddrInfoReqWrap.onlookupall [as oncomplete] (node:dns:118:26) {
errno: -3008,
code: 'ENOTFOUND',
syscall: 'getaddrinfo',
hostname: 'lazylibrarian'

Browser Logs

Failed to load resource: the server responded with a status of 500 ()
/api/services/proxy?type=sonarr&group=Multimedia&service=Sonarr&endpoint=queue:1 Failed to load resource: the server responded with a status of 500 ()
/api/services/proxy?type=jellyfin&group=Multimedia&service=Jellyfin&endpoint=Count&query=%7B%22refreshInterval%22%3A60000%7D:1 Failed to load resource: the server responded with a status of 500 ()
/api/services/proxy?type=sonarr&group=Multimedia&service=Sonarr&endpoint=wanted%2Fmissing:1 Failed to load resource: the server responded with a status of 500 ()
/api/services/proxy?type=sonarr&group=Multimedia&service=Sonarr&endpoint=queue%2Fdetails:1 Failed to load resource: the server responded with a status of 500 ()
/api/services/proxy?type=readarr&group=Books+%26+Documents&service=Readarr&endpoint=book:1 Failed to load resource: the server responded with a status of 500 ()
/api/services/proxy?type=radarr&group=Multimedia&service=Radarr&endpoint=movie:1 Failed to load resource: the server responded with a status of 500 ()
/api/services/proxy?type=sonarr&group=Multimedia&service=Sonarr&endpoint=series:1 Failed to load resource: the server responded with a status of 500 ()
/api/services/proxy?type=radarr&group=Multimedia&service=Radarr&endpoint=queue%2Fdetails:1 Failed to load resource: the server responded with a status of 500 ()

Troubleshooting

do not know how to troubleshoot it.

[glime-ai[bot]]

Thanks for posting a discussion about homepage here on GitHub. Homepage now uses a fancy new AI tool thanks to our friends at Glime, so the answer below is the AI bot's attempt to answer your question. If you feel it's sufficient you can mark the answer and close this post, otherwise feel free to leave it open of course!

Thanks for using Homepage! ❤️

---

Based on the information provided, it seems that the Homepage instance is experiencing a high number of HTTP 500 errors when attempting to call various services (e.g., librephotos-proxy, prometheus, lemmy, calibre-web, lazylibrarian, sonarr, jellyfin, readarr, radarr). These errors indicate that the services cannot be found (ENOTFOUND), which suggests a DNS resolution issue or a misconfiguration in the service URLs.

Here are some steps you can take to troubleshoot the issue:

1. Check Service URLs: Ensure that the URLs configured for each service in your Homepage setup are correct. According to the documentation, URLs should not end with a slash or other API path unless otherwise noted. Each widget will handle the path on its own.

2. Verify Network Connectivity: Make sure that the Homepage installation can connect to the IP address or host you are using for each widget's url. You can do this by pinging the server from the Homepage machine. If you're using Docker, you should ping from inside the container.

3. Check Logs: Review the homepage.log file for any additional information that might indicate what is causing the high CPU usage. You can access the logs by using the command docker logs homepage if you're running Homepage in a Docker container.

4. Browser Console: Check the browser error console for any client-side issues that might be contributing to the problem.

5. Update Configuration: If you have recently updated Homepage, ensure that your configuration files are compatible with the new version. Sometimes updates can introduce changes that require updates to the configuration.

6. Resource Limits: Check if there are any resource limits set on the Docker container that might be causing the high CPU usage. You can adjust these limits if necessary.

7. Ask for Help: If you're unable to resolve the issue, consider using the 'Ask AI' button on any page in the Homepage docs, opening a GitHub discussion, or checking out the #ai-support channel on Discord for more assistance.

8. Recreate Container: If all else fails, you might want to try recreating the Docker container to see if that resolves the issue.

Remember to back up your configuration before making any changes. If you need further assistance, please provide more details about your setup, such as the configuration files for Homepage and any customizations you have made.

This comment was generated by Glime.

[str8edgedave]

I have also noticed this after updating to 8.11. I also noticed that a lot of the services i am using siteMonitor with are giving 500 errors. I'm using Fedora 40 with Podman 5.0.2.

My homepage container logs are filled with network errors:

[2024-04-24T17:52:10.984Z] error: <httpProxy> Error calling https://netbox.example.ca/...
[2024-04-24T17:52:10.984Z] error: <httpProxy> [
  500,
  AggregateError
      at internalConnectMultiple (node:net:1114:18)
      at internalConnectMultiple (node:net:1173:5)
      at afterConnectMultiple (node:net:1601:5) {
    code: 'ECONNREFUSED',
    [errors]: [ [Error], [Error] ]
  }
]
[2024-04-24T17:52:10.985Z] error: <httpProxy> Error calling http://guacamole.example.ca/...
[2024-04-24T17:52:10.985Z] error: <httpProxy> [
  500,
  AggregateError
      at internalConnectMultiple (node:net:1114:18)
      at internalConnectMultiple (node:net:1173:5)
      at afterConnectMultiple (node:net:1601:5) {
    code: 'ECONNREFUSED',
    [errors]: [ [Error], [Error] ]
  }
]
[2024-04-24T17:52:11.225Z] error: <httpProxy> Error calling http://apps-02.example.ca/...
[2024-04-24T17:52:11.225Z] error: <httpProxy> [
  500,
  AggregateError
      at internalConnectMultiple (node:net:1114:18)
      at internalConnectMultiple (node:net:1173:5)
      at Timeout.internalConnectMultipleTimeout (node:net:1632:3)
      at listOnTimeout (node:internal/timers:571:11)
      at process.processTimers (node:internal/timers:512:7) {
    code: 'ENETUNREACH',
    [errors]: [ [Error] ]
  }
]

Pinging from inside the container works. After 8.11, I am unable to use wget to get any data, I get "Connection Refused" error messages.

$ podman exec -it systemd-homepage sh
/app # ping netbox.example.ca
PING netbox.example.ca (10.0.0.11): 56 data bytes
64 bytes from 10.0.0.11: seq=0 ttl=42 time=0.079 ms
64 bytes from 10.0.0.11: seq=1 ttl=42 time=0.128 ms
^C
--- netbox.example.ca ping statistics ---
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max = 0.079/0.103/0.128 ms
/app # wget https://netbox.example.ca
Connecting to netbox.example.ca (10.0.0.11:443)
wget: can't connect to remote host (10.0.0.11): Connection refused
/app #

[github-actions[bot]]

This discussion has been automatically closed due to inactivity. See our contributing guidelines for more details.

[github-actions[bot]]

This discussion has been automatically locked since there has not been any recent activity after it was closed. Please open a new discussion for related concerns. See our contributing guidelines for more details.