| Time |
Nick |
Message |
| 07:36 |
|
BDorsey joined #evergreen |
| 07:44 |
|
kworstell-isl joined #evergreen |
| 08:16 |
|
collum joined #evergreen |
| 08:39 |
|
mmorgan joined #evergreen |
| 09:07 |
|
Dyrcona joined #evergreen |
| 09:13 |
|
dguarrac joined #evergreen |
| 09:24 |
|
Rogan joined #evergreen |
| 09:27 |
|
kworstell_isl joined #evergreen |
| 09:27 |
|
kworstell_isl_ joined #evergreen |
| 09:48 |
|
sleary joined #evergreen |
| 10:09 |
|
collum joined #evergreen |
| 10:40 |
|
collum joined #evergreen |
| 10:53 |
Dyrcona |
I'm always amused when I see '. ~/.bashrc' in crontab files. The first actual code in default .bashrc files basically exits if it isn't running interactively, which causes that '. ~/.bashrc' to do nothing. |
| 10:57 |
|
collum joined #evergreen |
| 11:22 |
|
Christineb joined #evergreen |
| 11:22 |
|
collum joined #evergreen |
| 11:59 |
|
collum joined #evergreen |
| 12:14 |
|
collum joined #evergreen |
| 12:22 |
|
jvwoolf joined #evergreen |
| 12:37 |
berick |
hm, cannot get nginx to cache stuff. cache dir remains empty. any nginx users, thoughts? https://gist.github.com/berick/1fd87074c66d3367926d5d67fe76f48e |
| 12:39 |
csharp_ |
berick: maybe root owning the parent directory affects it? |
| 12:43 |
berick |
this works OK: sudo -u www-data touch /var/cache/nginx/test |
| 12:43 |
berick |
ditto: sudo -u www-data ls -al /var/cache/nginx/ |
| 13:20 |
Dyrcona |
berick: Where do you tell nginx what directory to use for cache? |
| 13:21 |
berick |
Dyrcona: top of my paste. just above the server { } block |
| 13:21 |
berick |
also tried in the nginx.conf file |
| 13:21 |
Dyrcona |
Yeah, I just saw that line. |
| 13:22 |
Dyrcona |
Does nginx run as www-data? |
| 13:22 |
berick |
it does. |
| 13:22 |
berick |
user www-data; |
| 13:22 |
berick |
confirmed by log files it creates as well |
| 13:24 |
Dyrcona |
That's a head scratcher. Is there a #nginx channel? |
| 13:29 |
jeff |
what version of nginx and what distro/version? |
| 13:30 |
berick |
nginx/1.18.0 / ubuntu 22.04 |
| 13:31 |
jeff |
try setting use_temp_path=off in your proxy_cache_path directive. |
| 13:31 |
jeff |
by default files are written to a temporary location (and I don't know offhand what that defaults to) |
| 13:31 |
jeff |
Default: |
| 13:31 |
jeff |
proxy_temp_path proxy_temp; |
| 13:33 |
berick |
no obvious effect |
| 13:35 |
berick |
hm, from the error logs: |
| 13:35 |
berick |
2023/05/24 13:33:10 [debug] 940621#940621: *1 http cacheable: 0 |
| 13:35 |
jeff |
is your client setting something like a Vary: header? |
| 13:36 |
berick |
using curl |
| 13:36 |
berick |
minimal client headers |
| 13:37 |
jeff |
does the upstream server set Expires: and/or Cache-Control: headers? What do those look like? |
| 13:37 |
jeff |
(I don't know if you can ignore Expires, though I see you're trying to) |
| 13:38 |
berick |
yes. many "do not cache me"-type headers. hoping to ignore them via my nginx config. |
| 13:39 |
jeff |
documentation seems to say that you can ignore Expires, but ye old 2015 blog post mentions that Expires and/or Cache-Control with max-age are how nginx decides if it should cache something at all. https://www.nginx.com/blog/nginx-caching-guide/ |
| 13:41 |
berick |
oh! looks like this did it: proxy_cache_valid any 30m; |
| 13:41 |
berick |
from the site you linked jeff |
| 13:42 |
jeff |
nice! |
| 13:43 |
jeff |
glad to hear that you didn't have to stick one nginx in front of the origin to drop/mangle/set headers, then another in front of that to do the caching. ;-) |
| 13:43 |
berick |
hah seriously |
| 13:43 |
berick |
2023/05/24 13:42:33 [debug] 940705#940705: *4 http file cache send: /var/cache/nginx/9f5c623e777d5f8a26fa6fc148e4519d |
| 13:43 |
berick |
yay |
| 13:43 |
berick |
thanks |
| 13:44 |
jeff |
that's likely required because you're successfully ignoring the Expires/etc headers, and there's no default. |
| 13:44 |
berick |
ah, that makes sense |
| 13:45 |
jeff |
good to be careful when doing that, but this does look like something that isn't ever going to be returning private content that shouldn't be served to another unauthenticated client. |
| 13:45 |
berick |
right |
| 13:47 |
|
jvwoolf joined #evergreen |
| 14:00 |
csharp_ |
"it's nginx all the way down" |
| 14:01 |
|
jvwoolf left #evergreen |
| 14:46 |
|
mantis1 joined #evergreen |
| 14:46 |
mantis1 |
Does anyone keep the records of offline circs? I don't really see the point of keeping them if they're already processed but figure to ask in case I'm missing something. We're looking to purge irrelevant data from our db. |
| 15:01 |
|
kworstell-isl joined #evergreen |
| 15:02 |
Dyrcona |
mantis1: There's no better way to find out than to delete them. As soon as you do that, someone will open a ticket with a question that can only be answered by the deleted data. :) |
| 15:03 |
Dyrcona |
You could always pg_dump the data before deleting or truncating the tables to have an offline backup. |
| 15:25 |
|
kworstell-isl joined #evergreen |
| 15:26 |
|
sleary joined #evergreen |
| 15:27 |
sleary |
@gmcharlt I finally remembered to check my spam folder and found several confirmations sitting there. All sorted, thanks! |
| 15:27 |
pinesol |
sleary: You're going to have to answer to the Coca-Cola company. |
| 15:30 |
|
mantis1 left #evergreen |
| 15:35 |
gmcharlt |
sleary: cool |
| 15:37 |
|
kworstell_isl joined #evergreen |
| 16:15 |
csharp_ |
pinesol: you think you're so funny |
| 16:15 |
pinesol |
csharp_: I eat more coconut cream pie before breakfast than most people eat all day |
| 17:16 |
|
sleary joined #evergreen |
| 17:17 |
|
mmorgan left #evergreen |
| 18:01 |
|
dmoore joined #evergreen |
| 21:22 |
|
kco joined #evergreen |
| 23:21 |
|
sleary joined #evergreen |
