00:34:55 where can I found the log of #freebsd ? 00:37:09 I don't think there's a public log. Why do you ask? 00:39:10 CrtxReavr: thank you again. "accept_rtadv" is the key to solve the no ipv6 address problem of my wireless connection. 00:39:50 V_PauAmma_V: I remembered who told me that argument. 00:40:40 * V_PauAmma_V nods. 01:48:05 I see curl finally got updated in the quarterly packages 02:33:38 <_xor> RhodiumToad: You around? 03:33:42 _xor: ya? 03:46:07 <_xor> RhodiumToad: Want to help me make some sense of a truss (or ktrace) dump? 03:46:56 ok... 03:47:07 <_xor> One minute, let me termbin it. 03:47:40 <_xor> Does termbin automatically add line numbers? I'll add those first if not. 03:47:55 <_xor> Oh wait, it's plain text on there isn't it? I think I was thinking of pastebin that does that. 03:50:27 <_xor> https://termbin.com/p9mi 03:50:28 if you want something a little less minimal than termbin, it's easy to paste to dpaste using curl 03:50:45 <_xor> No biggie, just ran it through nl and then nc to termbin. 03:51:09 <_xor> That one is truss, because that's the default in my head, but if you prefer ktrace, I can do that too. 03:51:58 ok, what are you looking for? 03:52:03 <_xor> Basically, I can't exactly tell where the start of the error event occurs exactly since I'm sure the rest of it is the trap/handler/whatever cleaning stuff up and dumping the message. 03:52:29 I'm not sure there's any error here to see. 03:52:32 <_xor> It seems like it's somewhere around line 80ish? 03:52:36 <_xor> Ah hmm 03:52:51 <_xor> So here's the basic gist of what this is... 03:53:22 I mean I can see it writing what looks like an error message 03:53:35 but that error doesn't seem to be the result of any system call failure 03:53:45 <_xor> That port I mentioned the other day that I've been using for a while, sysutils/rtx, I have an internal version of that port (since it didn't exist in the tree at the time). I just bumped it to the latest version which is failing to build. Ok, no biggie, nothing new. 03:55:10 <_xor> https://termbin.com/ar9g 03:55:28 <_xor> There's the actual error from the poudriere testport log. 03:57:32 well the error in the truss output is a different one 03:57:48 <_xor> Line 22 is the point of interest since the "build-time information: Os" is basically it saying that it can't determine the OS. Ok, great, so a compile-time generated file that embed build-info is screwing up. I suspect it's because it's missing a FreeBSD branch in some compile-time conditional. 03:58:19 <_xor> The truss output is from a run on build-script-build, where poudriere says the build bombed. 03:58:42 <_xor> It's the executable referenced on line 16 of the poudriere log. 03:59:15 ... so? it obviously did something different 03:59:56 <_xor> By "it" do you mean build-script-build? 04:02:21 <_xor> https://termbin.com/wlb5 04:02:56 I mean whatever you ran truss on did something different to what happened under poudriere. 04:03:23 <_xor> There's some more context, as I dropped into the builder jail and manually ran that executable. That's the error causing the build to fail (though I'm wondering now about environment variables that are set during build, so that message might not be accurate). 04:03:24 don't you see that from the difference in the error? 04:04:03 note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace <-- did you try that? 04:04:07 <_xor> Yes 04:04:22 and? 04:04:24 <_xor> I did both, RUST_BACKTRACE=1 and RUST_BACKTRACE=full 04:04:29 <_xor> Let me get those, one sec... 04:05:31 <_xor> Do you know if truss passes environment variables on to the child as-is or should I run /usr/bin/env as the command passed to truss? 04:06:05 it shouldn't clobber the env 04:06:19 truss will pass the env 04:07:34 what would 'urdlck' status in top mean ? 04:08:19 sounds like a wait channel 04:08:41 yeah, ./kern_umtx.c:3193: error = umtxq_sleep(uq, "urdlck", timeout == NULL ? 04:09:09 so it's sleeping in _umtx_op, which is generally our analog of the linux 'futex' 04:09:33 used to implement thread sync primitives 04:11:07 looks like it's trying to lock a read/write lock in read mode 04:11:34 https://pastebin.com/QVTUwpqG 04:11:35 Title: last pid: 65521; load averages: 12.58, 31.13, 18.67 - Pastebin.com 04:11:54 I'm running a heavy usage web server, php-fpm has about 2000 threads running when this happens, but the upper limit is 3000 04:12:12 then all of a sudden the load spikes up, apparently I run out of space - hard to say, I can't even ssh to the box when that happens 04:12:34 <_xor> Here's the truss dump with RUST_BACKTRACE=1... 04:12:41 <_xor> https://termbin.com/kkjw 04:12:49 <_xor> https://termbin.com/yakrp 04:12:54 <_xor> stderr and stdout 04:13:40 _xor: that's still not the same error as in your poudriere log 04:14:33 <_xor> You're referring to NotFound vs. NotPresent? 04:15:12 seriously, what part of the error message is _not_ different? 04:16:16 compare "thread 'main' panicked at 'Failed to acquire build-time information ..." with "thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value ..." 04:16:53 if you can't reproduce the same error, then you're just wasting time trying to investigate the wrong thing 04:17:28 <_xor> Dude, c'mon, I'm not a genius, but I'm also not a complete moron. NotFound is from the build tool invoked as part of the cargo build process. NotPresent is the actual source of the error, it's just not making its way up into the poudriere log. 04:17:44 <_xor> Ok sorry for wasting time. 04:18:53 last1: sounds like you're running out of memory, have you looked into that? 04:20:45 <_xor> I wanted to confirm it just now, but yeah, NotPresent is from the child process and the primary error. The parent process handles the error, but for whatever reason, it swallows it and throws its own NotFound error (I think because it's checking for the file the child process is supposed to produce, but fails to do so). 04:21:02 so then you need to trace the child process 04:21:09 <_xor> That's what that was. 04:21:11 this is where ktrace -i comes in handy 04:23:09 btw, are you trying to run the command from outside the poudriere jail? that's not likely to work well 04:23:30 enter the jail instead and run it from inside 04:23:35 yeah, I don't know. I think php-fpm processes are accumulating and not dying off or something until, yes, I do run out of ram 04:23:43 even though I've set them to quit after serving 20 requests 04:23:45 <_xor> It's all from within the builder jail. 04:24:24 _xor: the fact that your paste has a current dir name starting /poudriere/data/.m/13-amd64-main-default/ref/wrkdirs/... suggests not 04:24:54 <_xor> You're right, my bad, this one specifically is from the host. All of the other ones are from within the builder jail. 04:25:00 that'll work fine for relative paths, but for absolute ones it'll look to the host, which won't work well 04:25:11 <_xor> I'm going to delete this one and re-run it from within the jail again, one minute. 04:26:26 <_xor> When I say all of the other ones, I mean from last night. Just now I was trying to be quick and realized I could do it from the host, but the chroot slipped my mind. 04:27:25 <_xor> I'm just going to kill this directory of logs and start clean. Going to trigger the build again, so it'll take a few minutes, but I'll have the most recent, proper logs. 04:29:21 <_xor> Does dpaste support uploading multiple files in one request? 04:30:15 not afaik. 04:35:17 <_xor> I'm going to run `ktrace ... ./build-script-build`, any specific flags? 04:35:26 <_xor> (already ran truss) 04:35:42 -i 04:35:47 <_xor> ok 04:36:52 <_xor> Any specific flags to kdump? 04:46:43 no 04:55:45 <_xor> https://nopaste.net/ktrace.dump.txt 04:55:52 <_xor> https://nopaste.net/ktrace.stdout.txt 04:58:17 so, still not the same error message 04:59:53 <_xor> Ok, how about this specific trace though? Forget the poudriere log for now. At what point in the trace did the error occur? 05:00:13 it occurred inside the program, nothing to do with any OS calls 05:00:43 <_xor> Oh handled completely within the program. 05:00:47 <_xor> gah 05:01:07 all one can tell from the trace is that it's before the point where it starts writing "thread '" 05:01:40 <_xor> Yup, I originally wondered if it was because it wasn't able to read /etc/malloc.conf 05:01:45 and probably not much before; the preceding mmap call is probably part of a successful memory allocation 05:01:48 nah, that's normal 05:01:57 no, malloc.conf is not normally expected to exist 05:02:17 it's for debugging or tuning malloc by providing options 05:02:27 i still think the concept of malloc.conf is totally funky, but I understand it's probably the best way to do it 05:02:35 <_xor> Yeah I saw that in the man page, but what actually reads that. Would it be the program or some platform lib? 05:02:40 (one of those options is to log all mallocs to ktrace) 05:02:46 <_xor> Yes, I thought it was odd that it used symlinks :| 05:02:58 it's read by the malloc library, inside libc 05:03:35 <_xor> It made me wonder if it's something that the program was trying to read and NOT ignoring the returned error from readlink, or if it was being read by some sys lib and was being ignored as expected. 05:03:39 <_xor> Sounds like the latter. 05:05:09 <_xor> kern.sched.cpusetsizemin also confused me for a second because it wasn't showing up on my desktop, but then I realized that my desktop runs 13.1-STABLE and the build machine is 13.2-STABLE, which is where I guess that was introduced. 05:08:39 that's used internally in libthr 05:15:19 <_xor> Well, at least I have some more info now to go further. I tried patching the references to the relevant rust code last night, but that didn't work. That was when I dropped into the builder jail to poke and prod around, namely with build-script-build, but wasn't sure where the error was exactly, but didn't realize it's being handled completely by 05:15:19 <_xor> the program, not in response to some failed syscall. 05:20:52 _this_ error is internal to the program. we can't tell from the information shown what the error shown in the logs is from. 05:32:45 Whenever we have a hardware failure during a running FreeBSD system, what log file reports the failure event furtherly/should we check first? 05:33:03 a failing hdd, for instance. 05:37:11 usually /var/log/messages 05:37:39 kernel messages end up there unless you configured syslog.conf in some unusual way 05:38:16 output of `dmesg` may also be relevant 07:14:50 RhodiumToad: Thank you. 07:57:47 i forget who i was talking to, about my chromebook - it uses i2c drivers for touchpad, and sound, and presumably network too since that didn't work OOTB; is that something i can fix by porting linux drivers with linuxKPI 09:08:24 ixmpp: I've seen Val do lots of work around i2c: https://reviews.freebsd.org/search/query/9trYNzO6ROhe/#R 09:08:46 Title: Query: Advanced Search 09:09:19 looks like the query is base64 encoded 09:21:31 decodes to garbage though 09:21:59 i think i've tried val's existing efforts in past attempts, but fair enough 09:44:33 Any idea why the ping acts like this? 09:44:54 [FreeBSD-root@:~]# ping google.se - ping: UDP connect: No route to host 09:45:06 [FreeBSD-root@:~]# ping -4 google.se - PING google.se (172.217.18.99): 56 data bytes 09:45:26 default of the ping request is UDP? 09:45:34 you have ipv6_prefer specified in rc.conf? 09:46:14 it doesn't do that for me, and i don't have anything ipv6-related in rc.conf :) 09:46:16 yuripv: Contrarily, I actually have: ip6addrctl_enable="NO" - ip6addrctl_policy="ipv4_prefer" - ipv6_activate_all_interfaces="NO" - ipv6_network_interfaces="none" 09:46:33 ip6addrctl_enable="NO" <-- i guess that is the problem 09:46:45 if you don't want ipv6, simply do nothing. 09:48:37 I don't really remember why, but I think there were services/commands prefering IPV6 by the default and I think, back then, I solved it like that way.. 09:48:50 yuripv: that was the reason, i guess. 10:54:00 it's ICMP or ICMPv6, not UDP 11:43:06 debdrup: So, the issue isn't really the ip6* settings in my rc.conf? 11:43:15 btw: I've PF running as well. 11:43:21 *btw, 11:44:35 no, it's ipv6 settings in rc.conf; for me it's: $ ping -6 google.se -> ping: UDP connect: No route to host 11:44:43 no firewalls and no v6 11:46:50 "get the source address. XXX since we revoked the root privilege, we cannot use a raw socket for this." 11:47:07 (that's why UDP in error messages) 13:43:17 CrtxReavr angry_vincent meena So its a known issue and I should wait for its resolution? Also, if I install obs-studio, it removes neovim. What can be done here? 13:43:51 sorry, i do not follow 13:44:12 Sorry, gotta focus on the stuff I actually get paid for today. 13:44:37 angry_vincent this I mean. https://forums.freebsd.org/threads/freebsd-13-2-and-virtualbox-ose.88747/page-3 13:44:38 Title: Solved - freebsd 13.2 and virtualbox-ose | Page 3 | The FreeBSD Forums 13:44:51 Beladona: my question was about custom kernel 13:45:37 angry_vincent what was the question? 13:46:32 [20:39:41] Beladona: do you use custom kernel? 13:47:33 angry_vincent I never made a custom one. I don't even know what it is. I just followed https://docs.freebsd.org/en/books/handbook/cutting-edge/#makeworld 13:47:35 Title: Chapter 25. Updating and Upgrading FreeBSD | FreeBSD Documentation Portal 13:48:05 to solve https://pastebin.mozilla.org/4BsTybXP/raw 13:49:35 why are you so against compiling that damn module with MAKE_JOBS_UNSAFE? 13:50:08 it literally means: it's unsafe to compile this with make -j>1 13:55:12 while this is true, i think, the prblem, is that this module needed be propely built against newer kernel 13:56:46 i do not know what is exactly different between kernel 13.1 and 13.2 changd that makes this module to barf 14:03:31 meena what exact command i need to pass with MAKE_JOBS_UNSAFE=YES ? at what step to use it? 14:06:21 Hi everbody, i make customs in freebsd's source and now how to make a ISO based in freebsd source? 14:07:15 Beladona: you can set this in /etc/make.conf ro maybe with `env` 14:07:38 but i do not know if such variables can be set once or not 14:10:00 @angry_vincent is possible make inside linux ? or only inside another freebsd ? 14:10:48 i do not understand the question, sorry 14:15:36 @angry_vincent Sorry, I don't know if I made myself clear, my English is not good enough to write, come on. Is it possible to generate a freebsd iso using a linux distro? Or will I have to install a freebsd (or another BSD) to do this? 14:18:38 mbnunes: freebsd builds on FreeBSD, Linux and macOS 14:19:42 mbnunes: i do not know, i have not tried building FreeBSD outside FreeBSD 14:20:38 Beladona: you set it in make.conf 14:21:26 Ever open your irc client.. scroll back a little and just decide "Nope. there's too much dumb there today" and close the client? Thats about where i am today 14:26:28 meena I thought its like `make MAKE_JOBS_UNSAFE=yes` 14:27:09 or env MAKE_JOBS_UNSAFE=yes 14:27:38 if anything, it would be make -j1 14:33:07 meena isn't it -j1 by default if someone do not metnioned `-j`? 14:34:36 I am doing make make MAKE_JOBS_UNSAFE=yes buildworld buildkernel 14:35:42 it is not about buildworld and buildkernel 14:35:53 it was about the module itself 14:36:21 angry_vincent then what should be done? 14:37:09 echo "MAKE_JOBS_UNSAFE=yes" >> /etc/make.conf 14:37:45 try building virtualbox-ose-kmod again 14:40:47 angry_vincent building? like this? `cd /usr/ports/emulators/virtualbox-ose/; auto-mark-install-from-source emulators/virtualbox-ose-kmod kbi ` 15:11:52 no idea what does this do 15:12:01 just make install 15:24:20 angry_vincent `cd /usr/ports/emulators/virtualbox-ose/; make install` ? 15:24:34 Yes. 15:33:49 fckin freenode... if you try to connect irc.libera.net instead of irc.libera.chat it sends you to their servers 15:34:00 ops sorry, wrong channel 15:59:18 Hi, how do i fix this situation? I upgraded matrix-synapse to the newest version and now it's broken because py-canonicaljson was upgraded to the wrong version. see: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=270737 15:59:20 Title: 270737 – net-im/py-matrix-synapse: 1.80.0 fails to start with devel/py-canonicaljson 2.0.0 16:02:42 Is it possible to downgrade py-canonicaljson? 16:52:53 if you have an older version in your package cache: sure 16:54:51 Oh great, someone is going to do a custom build of FreeBSD and call it FreeBSD. Yeah, that's definitely going to go well, considering it's trademarked. 16:55:58 what where? 17:01:28 y'all made me go on "hacker" "news". 17:02:11 meena, You go so we do not have to 17:02:50 this is the first time in years I've opened the front page 17:11:22 rtprio: backlog. 17:11:29 meena: why would you willingly go there? 17:12:44 madetrarked 17:20:34 FrisBeeSD (why just infringe on one ™?) 17:21:35 i only see a question about building freebsd iso with modifications; don't see anything wrong with it, i do it all the time to test stuff 18:34:49 did i miss a java jre w/o x11 somewhere? 18:40:29 angry_vincent done. Now what to do? reinstall vritualbox? 18:41:07 debdrup when do you think obs-studio and neovim conflict be resolved? 18:41:48 Beladona: maybe, i do not know. if virtualbox-ose is fixed you can try rebuiling virtualbox too 18:42:59 angry_vincent not fixed. Same issue 18:43:36 ie https://pastebin.mozilla.org/4BsTybXP/raw 18:48:01 Beladona: you may want to read https://reviews.freebsd.org/D39474 18:48:02 Title: ⚙ D39474 FreeBSD Handbook: OS upgrades: kernel modules 18:49:09 angry_vincent I tried again and this time kldload vboxdrv just worked 18:49:22 I guess the rebuild was successful. 18:49:24 thanks ! 18:50:57 strike while the iron is hot 18:52:18 :) 18:55:30 ? 19:04:22 ok, so what's the syntax to properly set root's shell to /bin/sh? chsh -s /bin/sh root didn't take across logins 19:07:25 root shell is already /bin/sh i believe 19:08:07 but is simple chsh -s /usr/local/bin/bash while logged as root or as user 19:09:33 ( it was example ) 19:24:58 Demosthenex: "didn't take across logins" — yeah, no, it wouldn't 19:26:50 huh? 19:26:57 why wouldn't it? 19:28:33 btw, probably not a good idea to change root's shell to something other than sh or csh, I'm pretty sure it still gets invoked unnecessarily by the 'service' command 19:28:38 RhodiumToad: logged in sessions aren't gonna change shells 19:28:55 RhodiumToad: good grief 19:29:01 I assumed they meant it didn't stick across logout/login? 19:29:27 'service' and rc.subr generally are a crawling horror 19:29:41 so many levels of shell quoting and parsing 19:30:15 if it weren't for the fact that all the important files are root-owned and not writable by others it would be a security nightmare 19:32:40 * LxGHTNxNG feels woozy 20:01:40 obs neovim https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=267656 20:01:42 Title: 267656 – x11-wm/enlightenment multimedia/obs-studio: luajit-2.0.5_6 conflicts with luajit-devel-2.1.0.20221004_1 on /usr/local/bin/luajit 20:15:20 anyone know what to do about this: https://bsd.to/mQym ? 20:15:21 Title: dpaste/mQym (Bash) 20:20:27 trev: looks like it's expecting some directory to exist, which doesn't? 20:25:50 yeah maybe the profile, but that does exist. maybe it's looking somewhere else 20:27:02 the "can't find profile directory" error may be a harmless red herring 20:29:13 eventually i get "Firefox is already running, but is not responding. To use Firefox, you must first close the existing Firefox process, restart your device, or use a different profile." 20:29:33 you would think it would just open a new tab... 20:29:50 oh wait i didn't notice the "not responding" 20:30:10 i wonder if it's cause i don't have dbus running 20:44:53 <_xor> RhodiumToad: Figured out what the issue was, need to implement a bit of code to fix the build. Question last night was more an exercise in reading the trace, that's why I wasn't as concerned about the poudriere log. I got the general idea from the trace, but I wasn't sure if there was anything that jumped out (e.g. uncommon return value from a 20:44:53 <_xor> call) that I was missing. 20:49:08 truss/ktrace/etc are only useful when the error is being induced by something that the program is getting from the OS 20:49:16 (or not getting) 20:58:17 <_xor> Right. I couldn't see anything obvious in the trace, but I'm not confident enough in my reading of it to assume that there wasn't. I get that it didn't fault in there and that the unexpected state was in the program and also handled by it. Just wasn't sure if I was missing something obvious in the trace, hence the more experienced eyes looking at 20:58:18 <_xor> it. 20:58:57 <_xor> Last time I dealt with traces, it was on Windows. I've not done much of anything on FreeBSD at the system level, though I've been reading /usr/src little by little. 21:44:02 I have a pretty weird situation. Running FreeBSD 13.2 and I have an Intel X550-T2 nic, it's 10Gb 21:44:27 FreeBSD uses the ix driver for it, but on the first port ix0 I can only get 1Gb/sec for autoselect 21:44:39 if I plug the same cable, from the same switch into ix1, I get 10Gbps 21:45:01 in rc.conf I have just ifconfig_ix0="media autoselect" 21:45:05 no speed preference whatsoever 21:46:04 is that two ports on the same card, or two cards? 21:47:01 my first guess would be not getting a good enough electrical connection on all necessary pins in one of the ports 21:47:16 two ports on the same card 21:47:36 any idea when https://www.freshports.org/textproc/libxml2/ might get an update to not be vulnerable? 21:47:37 Title: FreshPorts -- textproc/libxml2: XML parser library for GNOME 21:47:57 when is libxml2 not vulnerable 21:48:13 excellent point 21:49:37 so it's like the jack itself that you think is faulted somehow ? 21:49:45 could be 21:50:04 the higher speed you want to go, the more important it becomes to have good connections everywhere 21:51:20 weird. I did see that the ix0 port has two lights: green + orange, ix1 has: green+green 22:09:04 last1: Is it because of speed duplex differences? 22:27:50 it's not 22:27:58 I suspect the card is faulty as Rhodium said 22:28:07 there's quite a few hits on Google of people having similar issues 22:28:29 I always held the Intel cards in high regard - but can you guys recommend something better for 10gbps ? 22:28:32 meena: across logins = new connections 22:28:57 a new login shell should have spawned, and it was ignored. 22:32:55 Demosthenex: does it look right in vipw? 22:37:18 https://pastebin.com/0yZy7msb 22:37:21 Title: zpool list -vNAME SIZE ALLOC FREE CKPOINT EXPANDSZ FRAG CAP - Pastebin.com 22:37:31 ~280Tb online with a single dev special device 22:37:36 gotta love zfs 23:44:20 283T 972K, heh 23:44:53 that does not count as "online" (yet) :p