00:12:56 <hyc> ubuntu 18.04 going end of life https://ubuntu.com//blog/ubuntu-18-04-lts-end-of-life-keep-your-fleet-of-devices-up-and-running
00:13:25 <hyc> seems like it still has 5 years of security updates for it tho so we prob don't need to take action at this point
01:17:17 <gingeropolous> for a price
04:45:11 -xmr-pr- bjacquin opened pull request #8717: compatibility with boost 1.81.0
04:45:11 -xmr-pr- > https://github.com/monero-project/monero/pull/8717
18:30:45 <gingeropolous> hrm, was syncing recent master: Height: 2657424/2801893 (94.8%) on mainnet, not mining, net hash 2.72 GH/s, v14, 12(out)+0(in) connections, uptime 6d 3h 56m 5s
18:32:57 <gingeropolous> it fully syncd before, but i wanted to test running it with a high log level daemonized, as opposed to spitting out the logs to screen
18:33:25 <hyc> any errors in logs?
18:35:18 <gingeropolous> nothing in the active stream, and grepping my log files is doing this thing "Binary file bitmonero.log-2023-01-16-13-26-29 matches"
18:35:28 <gingeropolous> unleash the cat
18:37:01 <sech1> "binary file matches" is grep's way of telling there are non-ASCII characters in the log
18:37:09 <hyc> yes but there shouldn't be any
18:37:21 <hyc> unless the terminal control sequences for color/bold are getting logged
18:37:24 <sech1> it's probably 0x00 bytes
18:37:35 <sech1> after monerod crash or something like this
18:40:32 <gingeropolous> ok well nano to the rescue
18:40:35 <gingeropolous> "2023-01-16 13:14:43.275 [P2P6]  ERROR   net.cn  src/cryptonote_protocol/cryptonote_protocol_handler.inl:1714    [x.x.x.x:18080 OUT] Failed to request missing objects, dropping connection
18:40:43 <gingeropolous> just randomly selecting a logfile and searching
18:43:20 <gingeropolous> ah i could use the other thing... the one line awk there it is.
18:44:20 <gingeropolous> damn i need chatgpt
18:47:43 <moneromoooo> -a treats as ASCII
18:48:54 <moneromoooo> Binary crap can get logged if there is access races and flushes happen at byte boundaries.
18:49:02 <moneromoooo> If you log utf8 anyway.
18:49:31 <moneromoooo> I *think* it cannot happen with just one process now though, you'd have to have two daemons.
18:49:45 <moneromoooo> Which happens as soon as you run one daemon to send a command to another.
18:49:49 <gingeropolous> danke
18:49:51 <moneromoooo> Very small chance though.
18:51:04 <gingeropolous> only have one instance going
18:51:26 <gingeropolous> CPU is also 100% mining using xmrig. monerod niced to the background
18:51:38 <sech1> it should the other way around
18:51:44 <sech1> xmrig niced and monerod running at normal priority
18:51:54 <gingeropolous> wait u might be correct :P
18:55:09 <gingeropolous> it is that way. well close to it. xmrig is 19 and monerod is 0
18:55:44 <moneromoooo> Nice.
18:55:47 * moneromoooo runs
18:55:57 <moneromoooo> (at -19)
18:56:47 <gingeropolous> lulz
18:56:56 <gingeropolous> well im an idiot. out of space. carry on folks
18:57:09 <gingeropolous> thats what happens when u let it make 1 gig log files
18:57:31 <gingeropolous> don't drink too much coffee
19:02:02 <gingeropolous> hrm. can i figure out how to make that error appear when the status command is invoked..... mebbe tonight