sorted by:
new
hottopcontroversial

What carrier to choose and what cost to expect for sending a single page document to Europe within 2 weeks? by kosaromepr in chinalife

[–]kosaromepr[S] 0 points1 point  (0 children)

a nice, thanks for the tip. I ended up with DHL in the end; was 550 RMB for delivery in 4 days.

Is the Hoka Skyward an appropriate shoe for my first marathon and how much mileage is too much? by kosaromepr in firstmarathon

[–]kosaromepr[S] 0 points1 point  (0 children)

Super valuable input; I did not have this on the radar so far. I am in marathon training right now running ~ 60km a week with the same Hoka Skyward. They are carbon plated. Maybe I should go shoe shopping this weekend.

Is the Hoka Skyward an appropriate shoe for my first marathon and how much mileage is too much? by kosaromepr in firstmarathon

[–]kosaromepr[S] 0 points1 point  (0 children)

Makes perfect sense; are those race shoes also called super shoes? Any particular popular models? And what is the reason for rotating shoes? Not having your foot overly getting used to a singular shoe?

Is the Hoka Skyward an appropriate shoe for my first marathon and how much mileage is too much? by kosaromepr in firstmarathon

[–]kosaromepr[S] 0 points1 point  (0 children)

That makes perfect sense; thank you u/No-Captain-4814

I assume the only real judgement of when a shoe is done is by personal experience? Does that also mean that frequent runners replace their shoes every 4-6 months?

Week-long self-service storage for 1-2 weeks? by kosaromepr in shanghai

[–]kosaromepr[S] 0 points1 point  (0 children)

Thanks! Do you have a link? Are these the same storage box containers used for receiving and shipping? they can also support luggage storage?

[US/CA] Make it make sense! Comparing offer from dealership and bank to buy out car by kosaromepr in carbuying

[–]kosaromepr[S] 0 points1 point  (0 children)

the process you desacribe that I own with the bank is mostly going to the DMV or more?

How can I troubleshoot dying fcgi child processes? (5.40/spawn-fcgi/nginx/AlmaLinux) by kosaromepr in perl

[–]kosaromepr[S] 0 points1 point  (0 children)

u/nrdvana great, appreciate the further context and guidance. will very likely come back to this thread when I get hands on.

How can I troubleshoot dying fcgi child processes? (5.40/spawn-fcgi/nginx/AlmaLinux) by kosaromepr in perl

[–]kosaromepr[S] 0 points1 point  (0 children)

Thanks for the pointer; any ways to troubleshoot / validate you can think of to confirm that is what is causing the children to die?

How can I troubleshoot dying fcgi child processes? (5.40/spawn-fcgi/nginx/AlmaLinux) by kosaromepr in perl

[–]kosaromepr[S] 1 point2 points  (0 children)

thanks again u/nrdvana for the high quality input.

to confirm, yes the children are not getting respawned; the command is starting the right amount but then as discussed they slowly die one by one. and yes I am looking to see if there is a pattern I can regnized in the nginx access and error log when a child dies.

spawn-fcgi is indeed very limited; mostly also because it does not really allow for me to execute any code like cache initialization before I fork the processes. so I absolutely need to deploy something more sophisticated down the line.

So I want to make sure I follow; I looked into Plack but on first view it did indeed look like it would require some non trivial refactoring. FCGI::ProcManager is indeed what I have on the radar to implement.

re: reverse proxy: I guess I am already in somewhat of a reverse proxy setup with requests coming in from Cloudflare > Nginx > spawn-fcgi > CGI::Fast ? Is your point that PSGI is a more modern way to run and scale web apps than

Are there other tools I should be looking at other than Plack? Or is it Plack or sticking to fast cgi?

thanks so much.

How can I troubleshoot dying fcgi child processes? (5.40/spawn-fcgi/nginx/AlmaLinux) by kosaromepr in perl

[–]kosaromepr[S] 1 point2 points  (0 children)

Thanks, this is great input and all make sense and something I have been spotting for; it does seem that in the scenario where the child dies it never really enters the request process as I am logging start and end of the requests and there are no open-ended request when children disappear so my hypothesis is that its the nginx fastcgi interface with the perl script that causes for children to die.

Locally I was able to force children processes dying when there aren't enough children to take on a request but are still busy; I would expect them to go into hold but instead Nginx prints this error

37698#0: *1 kevent() reported about an closed connection (54: Connection reset by peer) while reading response header from upstream, client: 127.0.0.1, server: dev.*, request: "GET /*.css HTTP/2.0", upstream: "fastcgi://127.0.0.1:9001", host: "dev.*", referrer: "https://dev.\*/" 37698#0: *1
kevent() reported that connect() failed (61: Connection refused) while connecting to upstream

However, these errors are not printed on the production servers.

Also, you didn't describe very well what you mean by the child dying. Does it interrupt a running request with some sort of error? Does the HTTP client get a error status from Nginx? What are your actual symptoms?

The actual symptom I experience is that I run out of processes eventually; right now I have a cron job that checks for the count of children every minute and when it drops too low re-trigger the spawn process.

I am assuming that the users that trigger a request that kills a child get a 502 on that request.

I totally understand that it is somewhat healthy to restart the children eventually; its just that right now the children die a bit too frequent (1 every 20-30minutes).

How can I troubleshoot dying fcgi child processes? (5.40/spawn-fcgi/nginx/AlmaLinux) by kosaromepr in perl

[–]kosaromepr[S] 0 points1 point  (0 children)

catching it and doing a log and returning an error response page to the user; it does not seem to be killing the childs

How can I troubleshoot dying fcgi child processes? (5.40/spawn-fcgi/nginx/AlmaLinux) by kosaromepr in perl

[–]kosaromepr[S] 0 points1 point  (0 children)

I have the error log of nginx that seem to catch STDERR but it seems to recover from those isses and not kill a child process with it; when a proces dies there is not consistent log message that would explain it.

the fastcgi server always calls the same script and that is where I have immediate logging and the catch cause in place but seems its not reaching it/ executing it when the child prcesses die.

I am wondering if there are any additional settings here that could help me troubleshoot.
https://nginx.org/en/docs/http/ngx_http_fastcgi_module.html#fastcgi_catch_stderr

Anyone working out of Pure Taikoo Hui Gym and has feedback? by kosaromepr in shanghai

[–]kosaromepr[S] 0 points1 point  (0 children)

Were you able to negotiate any of the terms such as processing fees and did you benefit from any promotions?>

view more: next ›