Time |
Nickname |
Message |
00:32
🔗
|
|
eythian_ has joined #urlteam |
00:32
🔗
|
|
eythian has quit IRC (Read error: Operation timed out) |
00:33
🔗
|
|
chazchaz_ has joined #urlteam |
00:37
🔗
|
|
chazchaz has quit IRC (Read error: Operation timed out) |
00:37
🔗
|
|
pikami_ has joined #urlteam |
00:38
🔗
|
Wingy |
To urlteam basically wardials url shorteners? |
00:41
🔗
|
|
markedL has quit IRC (Ping timeout: 496 seconds) |
00:41
🔗
|
|
pikami has quit IRC (Ping timeout: 496 seconds) |
00:42
🔗
|
|
markedL has joined #urlteam |
00:44
🔗
|
|
nyany__ has joined #urlteam |
00:44
🔗
|
|
nyany_ has quit IRC (Remote host closed the connection) |
00:45
🔗
|
|
markedL has quit IRC (Client Quit) |
01:46
🔗
|
|
MrRadar2 has quit IRC (Read error: Connection reset by peer) |
01:52
🔗
|
|
Dallas has quit IRC (Ping timeout: 864 seconds) |
01:53
🔗
|
|
Dallas has joined #urlteam |
01:58
🔗
|
Kaz |
something like that |
02:20
🔗
|
|
MrRadar2 has joined #urlteam |
03:29
🔗
|
|
klg_ has joined #urlteam |
03:29
🔗
|
|
Mayonaise has quit IRC (Read error: Operation timed out) |
03:31
🔗
|
|
Mayonaise has joined #urlteam |
03:31
🔗
|
|
systwi has quit IRC (Read error: Operation timed out) |
03:34
🔗
|
|
klg has quit IRC (Read error: Operation timed out) |
03:38
🔗
|
|
Wingy has quit IRC (Read error: Operation timed out) |
04:04
🔗
|
|
systwi has joined #urlteam |
04:24
🔗
|
|
markedL has joined #urlteam |
04:57
🔗
|
|
odemg has quit IRC (Ping timeout: 745 seconds) |
05:01
🔗
|
|
odemg has joined #urlteam |
12:20
🔗
|
|
Wingy has joined #urlteam |
12:33
🔗
|
Zerote_ |
Is the tracker down for everyone else? |
13:31
🔗
|
Wingy |
Tracker is giving 500s |
13:31
🔗
|
Wingy |
on done |
13:32
🔗
|
Wingy |
all of my threads have tasks but /api/done is 500 |
13:34
🔗
|
Wingy |
Zerote_ |
13:36
🔗
|
Wingy |
Now I’m getting 409 |
13:37
🔗
|
Wingy |
so tracker might be up? |
13:37
🔗
|
Wingy |
got a 404 on /api/get |
13:37
🔗
|
Zerote_ |
I'm seeing the same thing, was wondering if it was just me |
13:38
🔗
|
Wingy |
aw 500 on the new task |
13:39
🔗
|
Wingy |
angelonfire is at 0 tasks |
15:23
🔗
|
chfoo |
just restarted the tracker. if the homepage gives http 500, then it needs a restart |
15:50
🔗
|
|
Zerote_ has quit IRC (Read error: Operation timed out) |
16:05
🔗
|
|
Zerote has joined #urlteam |
16:32
🔗
|
|
dan- has quit IRC (Quit: ZNC - https://znc.in) |
16:32
🔗
|
|
dan- has joined #urlteam |
16:36
🔗
|
|
ivan- has joined #urlteam |
16:36
🔗
|
|
Fusl sets mode: +o ivan- |
16:36
🔗
|
|
Fusl_ sets mode: +o ivan- |
16:47
🔗
|
|
ivan has quit IRC (Ping timeout: 745 seconds) |
17:43
🔗
|
Wingy |
I'm getting 403s from bitly |
17:43
🔗
|
Wingy |
Reign in the concurrency? |
17:44
🔗
|
Wingy |
I'm running 24 urlteam threads |
18:03
🔗
|
Wingy |
So the tracker is back up |
20:49
🔗
|
JAA |
chfoo: Given what you said before, I take it HTTP 500 means Redis died and so the server fails to connect to it? |
20:51
🔗
|
JAA |
Wingy: bitly is just incredibly restrictive with their rate limits. I guess we should tweak the settings somehow to reduce how often workers get banned. The concurrency plays no role here though since you're anyway limited to one item per shortener and IP. |
20:51
🔗
|
Wingy |
Oh okay |
20:51
🔗
|
Wingy |
I'll keep my 4 instances |
20:52
🔗
|
chfoo |
it's the same redis issue. i suspect it's a concurrency bug probably fixed in newer versions |
20:53
🔗
|
JAA |
Ah |
20:53
🔗
|
JAA |
Redis was never updated since this was launched I guess? |
20:54
🔗
|
JAA |
The ArchiveTeam Wayâ„¢ |
20:54
🔗
|
chfoo |
redis has been updated once a long time ago, but python and none of the libraries were updated |
20:56
🔗
|
JAA |
I see. |
22:57
🔗
|
|
ivan- is now known as ivan |