So we have about 1.3T of logs on toollabs. P628 lists the biggest offender. Almost 1T is just one log file, filled with php warnings and notices. There's a NFS backup going on, so we should clean these up after.
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | • Bstorm | T126083 overhaul labstore setup [tracking] | |||
| Resolved | None | T98652 Clean up huge logs on toollabs | |||
| Resolved | scfc | T100572 wikiviewstats rapidly fills error.log |
Event Timeline
Comment Actions
Don't attempt to rm these from the labs instances tho - should be removed on the server directly or we'll kill NFS :)
Comment Actions
Actually, unlinking a file via NFS should not be any harder on the server than doing it directly - the real thing to watch out for is to make sure it is not currently opened by any process. Something that /can/ be done from the server which might be a better idea is to simply truncate the file.
Comment Actions
cluebot's error log grew to 1.5T again, deleted and notifying maintainer (https://en.wikipedia.org/wiki/User_talk:Rich_Smith#Cluebot.27s_error_logs)
Comment Actions
This has happened a few times and we will have to continue to clean things up. I'm hopeful T126623 will make it easier to identify and easier for users to understand in teh future. For now I'm going to resolve this as there isn't active cleanup in progress.