#known 2016-03-23

2016-03-23 UTC
tantek, j12t and benborges joined the channel
#
benborges getting a 502 gateway when trying to export my Known Data admin/export/generate/
#
benborges 502 Bad Gateway
#
benborges nginx/1.6.2
#
benborges wondering what i can do on my side to fix that
j12t, Madgod and jfred joined the channel
#
kylewm benborges: I was seeing 504 Gateway Timeout using nginx https://github.com/idno/Known/issues/1296
#
kylewm wonder if it's the same issue
#
kylewm (which is, I think, that nginx doesn't allow background processing the same way apache does)
#
benborges hmmm it ended up my making the backup archive kylewm
#
benborges and i managed to download it by coming back to the export page
#
benborges i wonder if some nginx tweaking could solve this, the question is how, i'm not a nginx expert
#
aaronpk it's probably a timeout setting in nginx
#
aaronpk so you could increase the timeout to let nginx run the script longer
#
benborges gonna investigate this, thanks all
#
aaronpk in general though, web servers don't like scripts to run for arbitrary lengths of time. it would be better if Known found an alternate way of handling that
#
benborges indeed, because i guess the larger the site, at some point it will be impossible to retrieve or to even create the archive
#
aaronpk yeah
j12t joined the channel
#
kylewm aaronpk: yeah, it's the general shared hosting problem... you can't count on being able to run a background queue, so you have to get creative
#
aaronpk yeah, i'm gonna have to decide if I want to make p3k require a background queue and as such prevent it from working on simple web hosts
#
kylewm happy medium might be a hacky solution for shared hosts (e.g., wp-cron) that can be swapped out with a background queue
#
aaronpk yeah, it's mostly a question of how many code paths i want to test, especially if i'm not using it myself
j12t, tommorris, cleverdevil-, sensiblemn, Simpson_ and j12t_ joined the channel