Jump to content

Leaderboard


Popular Content

Showing content with the highest reputation since 08/22/20 in all areas

  1. 1 point
    Prophet731

    Procon server connection problem

    There shouldn't be a limit of how many clients can be connected.
  2. 1 point
    Prophet731

    procon crash

    [12:40 AM] Prophet: How's the procon performance? It's now on the new server. [12:40 AM] Prophet: @OneManArmy [12:41 AM] OneManArmy: i have the layer open with adkats to all servers, looks :ok_hand: [12:45 AM] Prophet: Ok cool [12:45 AM] Prophet: I'm going to leave it like this overnight [12:45 AM] Prophet: and see how well it preforms [1:03 AM] Prophet: Alright, EU pool is now enabled. Let's see how this goes [1:12 AM] Prophet: How's the performance now @OneManArmy [1:13 AM] OneManArmy: stable, all green and connected without disconnonecting / connecting [1:15 AM] Prophet: perfect. All I did was increase the php-fpm pool [1:15 AM] Prophet: Don't know how that fix it lol [1:15 AM] Prophet: other server was running fine without those changes [1:19 AM] OneManArmy: okay. i can monitor it a bit from work, see if it stay's connected [1:20 AM] Prophet: Awesome. Doing about 2500 queries per second from the API alone. [1:21 AM] Prophet: So let me know if procon lags for more than 5 mins continuously and at what time it started [1:22 AM] Prophet: UTC time Just for context of what I did and what I would like to know.
  3. 1 point
    Prophet731

    procon crash

    Give it a restart. Maybe it glitched out. I've migrated over the API to two web hosts now so now it's failover supported. That could be the cause too as I was just working on it. The two hosts are located in the US and in EU and the requests are routed based on where the layer is at (georegion)
×
×
  • Create New...

Important Information

Please review our Terms of Use and Privacy Policy. We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.