Skip to content
This repository has been archived by the owner on May 15, 2020. It is now read-only.

503 status when serving many concurrent files #553

Open
magnusdahlstrand opened this issue Jan 12, 2018 · 0 comments
Open

503 status when serving many concurrent files #553

magnusdahlstrand opened this issue Jan 12, 2018 · 0 comments

Comments

@magnusdahlstrand
Copy link

Thanks for making pow, it's been a great developer helper for me for many years.

I originally posted this issue in basecamp/powprox#12, but have since noticed the issue when running pow directly.

I've configured the domain to proxy a node.js app (running koa with koa-static serving the files). When I load the page, about a third of the resources (~6) fail when running through powprox (https), and about 1/20 fail when not running through pow. None fail when running directly. The requests fail with 503 status errors and a x-pow-template:application_not_found, even though the application is there and working for the other requests.

I originally did a lot of digging in powprox's setup to figure out why to no avail. Since observing the issue with pow directly I tried looking at the error log, but can only find access.log in the Log directory (as per the User Manual). The manual mentions error logs can be found in the "apps directory", but I can't find a mention of where this is. Reading through the code is seems it should be next to the access.log, but isn't. This makes me think either writing error logs is broken, or pow isn't aware of the error.

In the end I tried updating the pow config to use more workers, which resolved the issue. I returned it to 2 workers & restarted pow, and the issue is still gone. It seems restarting pow was all that was needed.

I will report back if the issue reappears and I'm able to find a solution. In the meantime, where can I find the error logs?

Thanks,
Magnus

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant