Time |
Nickname |
Message |
03:48
🔗
|
chfoo |
things i need to do: finish writing the export script, add more shorteners, |
03:49
🔗
|
chfoo |
look into the web ui's font issue, change the sleep time to account for network latency, and figure out how to resume the existing shorteners |
03:51
🔗
|
chfoo |
the tracker seems to be using 100% usage for some reason too |
20:26
🔗
|
Fusl |
|
20:26
🔗
|
Fusl |
what does this mean? i get this constantly on all my servers where i run urlteam crawler: Error communicating with tracker: 429 Client Error: 192.121.170.7 has pending claims in all shorteners. Check that your client is up to date, you're running at most 1 client per shortener then contact a tracker administrator to release any pending claims.. |
20:35
🔗
|
chfoo |
i'm checking the tracker |
20:35
🔗
|
chfoo |
it's really really slow right now |
20:35
🔗
|
chfoo |
i think a bad item is being recycling around and around |
20:36
🔗
|
chfoo |
but the error report viewer page is broken right now so i can't figure it out yet |
20:39
🔗
|
Fusl |
i mean, they *do* crawl without problems but they often just throw this error (several times per minute) |
20:43
🔗
|
arkiver |
chfoo: are the urlteam tracker and the tracker for project like twitpic the same? or seperate trackers? |
20:43
🔗
|
chfoo |
arkiver: completely separate trackers |
20:43
🔗
|
arkiver |
ah ok |
20:44
🔗
|
arkiver |
that was just out of interest, thanks |
21:35
🔗
|
chronomex |
urlteam is on a different machine than the normal archiveteam tracker |
21:44
🔗
|
chfoo |
the old urlteam tracker was on another server. the new one is on the same server |
21:44
🔗
|
chfoo |
installed under the tinytown user account |
22:01
🔗
|
chronomex |
oh really, ok |
22:01
🔗
|
chronomex |
when did this change? |
22:02
🔗
|
chronomex |
thanks for letting me know, i'll ping you specifically when i get my ass in gear enough to migrate it to a different box |
22:12
🔗
|
chfoo |
changed slowly over the past 6 months |
22:12
🔗
|
chronomex |
ok |
22:13
🔗
|
chfoo |
it new urlteam tracker doesn't need a separate server though |
22:13
🔗
|
chfoo |
it uses up disk and cpu while the normal tracker uses up memory |
22:13
🔗
|
chfoo |
so it fits in well i guess |
22:13
🔗
|
chronomex |
rad |
22:13
🔗
|
chronomex |
yeah i've been getting more high-disk-activity alarms this month, that's probably why |
22:14
🔗
|
chronomex |
i'll change the threshold on that |
22:14
🔗
|
chronomex |
eventually |