libera/#maemo/ Wednesday, 2024-11-13

freemangordonjoerg: I tried to contact warfare, to no success, I guess my mail went to spam folder11:23
freemangordoncould you try to contact him?11:23
freemangordonxes: ping11:23
joergfreemangordon: I didn't hear of him since some months as well11:24
freemangordondo we know where servers are located?11:24
joergI hope he's well, or recovering11:24
joergyes, that's known11:24
freemangordonactually I think he replied here 1-2 moths ago11:25
joergyes11:25
freemangordonso, any clue what we can do? wait a bit more? or?11:26
sicelommm, our telecoms regular has now set 31st Dec 2026 for 2G & 3G shutdown, and banning importation of 2G/3G only devices from 31st Dec this year11:32
sixwheeledbeastBanning? interesting11:43
KotCzarnyhere 2g is left alone, but only for voice/emergency etc11:44
freemangordonguys, do we know anyone else but warfare who has (physical) access to maemo servers11:45
warfarefreemangordon: Nope, but I'll try to arrange DC access next week.13:08
warfarefreemangordon: Sorry, life got into the way.13:08
freemangordonwarfare: oh, sorry to hear that, hope you are ok13:09
warfarefreemangordon: Yes, should be all better now :)13:09
freemangordongreat! :)13:09
freemangordontake your time, wiki can wait13:10
joergoh hi warfare ! :-) Great to hear you're feeling better13:52
joerg>>The certificate for wiki.maemo.org expired on 8/2/2024.<<14:34
joergso good so far14:34
joerg>5GB of 9GB disk were filled with apache logs14:35
joergI killed "february"14:36
joergwhich cronjob is running letsencrypt cert update?15:01
joergfixed15:41
joerg(wiki that is)15:41
joergfreemangordon: are you available for tuning logrotate to cope with (apache) cronolog logfiles?19:01
freemangordonumm...19:02
joergsorta nuts that cronolog doesn't come with appropriate matching logrotate config file to start with19:02
freemangordonI am dev, not admin :)19:03
joergI'm retired19:08
freemangordonhow did you manage to bring it up?19:11
joerghttps://www.colinpretorius.org/blog/linux/cronolog.html pretty much lists the problem, boiling down to a "feature" for the author: >>This [logrotoate] is great for most cases, but is a problem if you want to keep logs permanently, like I do with my website. [...] The config file is set to run on all files matching pattern /var/log/apache2/*.log<<19:11
joergfreemangordon: it had 100% filled rootfs, >5GB of the 9.9GB were /var/log/apache/%YEAR//%MONTH/%DAY/* - I for now deleted .../2024/02/*19:13
freemangordonso, no HDD failure?19:13
KotCzarnyso, what's the point of keeping the logs if they need to be deleted anyway19:14
joergthe HDD failure is unrelated and very true19:14
freemangordonah19:14
joergKotCzarny: all logs are for analysis when problems occur19:17
KotCzarnyhow about offloading them to some backup site via cron?19:19
joergmore than 6 months are nearly always nonsense, probably 1 month is more than enough usually. Anyway the problem here is that the logrotate config file for apache logs doesn't match the "new" cronolog scheme used in apache19:19
joergI wonder if /etc/logrotate.d/apache2 config file could use an augmented /var/log/apache2/*.log, like /var/log/apache2/*/*/*/*.log19:24
KotCzarnyor just write a script to generate flat configs19:26
joerghmm?19:45
joerghttps://superuser.com/questions/702256/is-there-a-tool-like-cronolog-or-rotatelogs-but-also-with-compression-and-r  >>Expecting something like this:  `./my_program_that_generate_logs | cronologrotate /var/log/ololog/%Y_%M/%d.log --compress-after '30 days' --remove-after '1 year' `<<19:46
KotCzarnyfind /var/log/apache2/ -type f -name "*.log" -mtime +30  -exec gzip {} \;19:53
KotCzarnyfind /var/log/apache2/ -type f -name "*.gz" -mtime +366 -delete19:54
KotCzarnydone19:54
KotCzarnyrun daily19:54
KotCzarny(untested, try with -print first instead of -exec/delete)19:54
joergthanks20:07

Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!