really long load times #1653

danktankk · 2023-07-02T13:40:21Z

danktankk
Jul 2, 2023

Recently,

I have been having an issue with extremely long load times for my homepage. Im not sure where to begin on troubleshooting this. I was hoping that this has already been an issue, but I didnt see anything when I looked. It takes close to a minute for the page to load now. If I click refresh, it will load much more quickly.

When I made an addition or a change to the homepage, it will autoreload as expected, but it takes forever for it to load back up. The only way to get it to load faster is to refresh it after it refreshes itself. Any help would be greatly appreciated. This is the best homepage WebUI I have ever used!

shamoon · 2023-07-02T14:35:19Z

shamoon
Jul 2, 2023
Maintainer

Yea I haven’t seen this much. I’m assuming you’re running a docker install? One thing is that some of the APIs used by widgets can return huge amounts of data, you may want to try commenting out some services and see if that helps. You can also try completely removing and recreating the container. There are probably other possibilities though.

0 replies

danktankk · 2023-07-03T12:46:35Z

danktankk
Jul 3, 2023
Author

Yeah this is running in ubuntu-server 22.04 in docker compose. I did find that my qbittorrent container was over the limit of 4mb for the API, but that did not fix the error. I have tried removing entries and so on, but that has not helped. I also recreated the container. The log file did show several containers that it had issues with and I have fixed all of them or removed them completely.

This is the only error I am seeing in the log and it appears twice after a change is made to the services.yaml file. Once at initial attempt to refresh the page and again once the page actually loads almost 2 minutes later.:

`[2023-07-03T12:41:07.193Z] error: TypeError: Cannot read properties of null (reading 'conn')
at handler (/app/.next/server/pages/api/docker/status/[...service].js:89:86)
at Object.apiResolver (/app/node_modules/.pnpm/[email protected][email protected][email protected]/node_modules/next/dist/server/api-utils/node.js:366:15)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async NextNodeServer.runApi (/app/node_modules/.pnpm/[email protected][email protected][email protected]/node_modules/next/dist/server/next-server.js:481:9)
at async Object.fn (/app/node_modules/.pnpm/[email protected][email protected][email protected]/node_modules/next/dist/server/next-server.js:741:37)
at async Router.execute (/app/node_modules/.pnpm/[email protected][email protected][email protected]/node_modules/next/dist/server/router.js:252:36)
at async NextNodeServer.run (/app/node_modules/.pnpm/[email protected][email protected][email protected]/node_modules/next/dist/server/base-server.js:365:29)
at async NextNodeServer.handleRequest (/app/node_modules/.pnpm/[email protected][email protected][email protected]/node_modules/next/dist/server/base-server.js:303:20)
at async Server. (/app/server.js:19:5)

[2023-07-03T12:43:20.974Z] error: TypeError: Cannot read properties of null (reading 'conn')
at handler (/app/.next/server/pages/api/docker/status/[...service].js:89:86)
at Object.apiResolver (/app/node_modules/.pnpm/[email protected][email protected][email protected]/node_modules/next/dist/server/api-utils/node.js:366:15)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async NextNodeServer.runApi (/app/node_modules/.pnpm/[email protected][email protected][email protected]/node_modules/next/dist/server/next-server.js:481:9)
at async Object.fn (/app/node_modules/.pnpm/[email protected][email protected][email protected]/node_modules/next/dist/server/next-server.js:741:37)
at async Router.execute (/app/node_modules/.pnpm/[email protected][email protected][email protected]/node_modules/next/dist/server/router.js:252:36)
at async NextNodeServer.run (/app/node_modules/.pnpm/[email protected][email protected][email protected]/node_modules/next/dist/server/base-server.js:365:29)
at async NextNodeServer.handleRequest (/app/node_modules/.pnpm/[email protected][email protected][email protected]/node_modules/next/dist/server/base-server.js:303:20)
at async Server. (/app/server.js:19:5)`

The timestamp of the error entries is the time it takes to load the page currently if I do nothing and allow the app the refresh on its own.

1 reply

shamoon Jul 3, 2023
Maintainer

Perhaps something with file permissions, that function reads from the docker.yaml file

But really no obvious reason why that would take 2 minutes (or for the error itself)

danktankk · 2023-07-04T21:49:48Z

danktankk
Jul 4, 2023
Author

hm ok... welp... thanks anyway

2 replies

danktankk Jul 5, 2023
Author

is there a way to maybe get more granular logs? I really dont want to toss this homepage for another one.

danktankk Jul 5, 2023
Author

before you answer, I will remove a section at a time to see if I can at least narrow the search to help someone else later. I will report back what I find

benphelps · 2023-07-05T06:42:14Z

benphelps
Jul 5, 2023
Maintainer

If you have docker stats open by default, this can cause the load times to slow dramatically, perhaps that's it.

3 replies

danktankk Nov 19, 2023
Author

I was able to finally determine that it was docker.sock that was causing the insane load times.

StancuFlorin Mar 3, 2024

How did you determined that? Did you fixed?

ptrsconsulting Mar 21, 2024

@danktankk can you share how did you determine that and fixed it?

danktankk · 2023-07-06T00:44:10Z

danktankk
Jul 6, 2023
Author

it does not appear that docker stats is running. I have no idea why this is happening. I have completely removed everything from the yaml files, deleted the container, did a docker system prune & docker system prune -a --volumes and it still, even empty is taking forever to load..... unless of course I hit refresh. Same behavior in Edge, Opera, and Chrome.

0 replies

henkiewie · 2023-07-20T14:14:02Z

henkiewie
Jul 20, 2023

I seem to have the same kind of error. In my case it's only azuracast. AL other containers work normal. It uses its own docker.sh script that installs in /var/azuracast. So there must be something homepage can not reach or maube times out? There are no docker specific files there except for the docker-compose.yml and an .env file. The containername is correct.
The homepage log spits out an error like this;

2023-07-20T13:57:49.645Z] error: <dockerStatsService> TypeError: Cannot read properties of null (reading 'conn')
    at handler (/app/.next/server/pages/api/docker/stats/[...service].js:89:86)
    at Object.apiResolver (/app/node_modules/.pnpm/[email protected][email protected][email protected]/node_modules/next/dist/server/api-utils/node.js:366:15)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async NextNodeServer.runApi (/app/node_modules/.pnpm/[email protected][email protected][email protected]/node_modules/next/dist/server/next-server.js:481:9)
    at async Object.fn (/app/node_modules/.pnpm/[email protected][email protected][email protected]/node_modules/next/dist/server/next-server.js:741:37)
    at async Router.execute (/app/node_modules/.pnpm/[email protected][email protected][email protected]/node_modules/next/dist/server/router.js:252:36)
    at async NextNodeServer.run (/app/node_modules/.pnpm/[email protected][email protected][email protected]/node_modules/next/dist/server/base-server.js:365:29)
    at async NextNodeServer.handleRequest (/app/node_modules/.pnpm/[email protected][email protected][email protected]/node_modules/next/dist/server/base-server.js:303:20)
    at async Server.<anonymous> (/app/server.js:19:5)

By the way there was a request some time ago to make a widget for this very nice radio streamer.

regards,
Henk

1 reply

henkiewie Jul 20, 2023

When I run docker stats the info is provided.

CONTAINER ID   NAME                         CPU %     MEM USAGE / LIMIT     MEM %     NET I/O           BLOCK I/O         PIDS
9c29f6532a04   homepage                     4.16%     110.6MiB / 15.48GiB   0.70%     46.4MB / 38.3MB   5.09MB / 864kB    13
99f03093ef86   azuracast                    40.46%    2.286GiB / 15.48GiB   14.77%    186MB / 6.3GB     4.39GB / 583MB    122

2024-09-18T03:06:29Z

github-actions[bot]
bot Sep 18, 2024

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

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

really long load times #1653

{{title}}

Replies: 7 comments 7 replies

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

Select a reply

really long load times #1653

danktankk Jul 2, 2023

Replies: 7 comments · 7 replies

shamoon Jul 2, 2023 Maintainer

danktankk Jul 3, 2023 Author

shamoon Jul 3, 2023 Maintainer

danktankk Jul 4, 2023 Author

danktankk Jul 5, 2023 Author

danktankk Jul 5, 2023 Author

benphelps Jul 5, 2023 Maintainer

danktankk Nov 19, 2023 Author

StancuFlorin Mar 3, 2024

ptrsconsulting Mar 21, 2024

danktankk Jul 6, 2023 Author

henkiewie Jul 20, 2023

henkiewie Jul 20, 2023

github-actions[bot] bot Sep 18, 2024

danktankk
Jul 2, 2023

Replies: 7 comments 7 replies

shamoon
Jul 2, 2023
Maintainer

danktankk
Jul 3, 2023
Author

shamoon Jul 3, 2023
Maintainer

danktankk
Jul 4, 2023
Author

danktankk Jul 5, 2023
Author

danktankk Jul 5, 2023
Author

benphelps
Jul 5, 2023
Maintainer

danktankk Nov 19, 2023
Author

danktankk
Jul 6, 2023
Author

henkiewie
Jul 20, 2023

github-actions[bot]
bot Sep 18, 2024