00:27:12 i need to create a virtual network interface 00:27:49 i want to create a internal virtual lan 00:27:58 any hints how to do that on fbsd? 00:29:59 nvm i found the solution 00:32:23 rwp: correct, it is every time. let me check the debug execution if it shows something. 00:34:01 rwp: error happens exactly after the bash completion user dir. 00:34:05 rwp: + BASH_COMPLETION_USER_FILE=/dev/null 00:34:05 bash: SRCDIR: unbound variable 00:35:38 bash_completion_user_file is set to /dev/null (but that is the default, I never touched that). 01:17:18 cybercrypto, It should be the line after the BASH_COMPLETION_USER_FILE=/dev/null line because that one reported and then after that you got the unbound variable. 01:17:53 But again, don't set -u, no one else's shell code is expecting to run with -u or -e active. If you feel you must set it then set it last after everyone else's code. 01:18:11 Find where you are doing a set -u and remove it. 01:18:54 With today's FreeBSD update it's unimportantly nice that "freebsd -kru" reports all three the same again. It's a silly thing I know. 01:22:23 i need a complete tutorial to ipsec ^^" 01:24:09 i got openvpn sorted but i want ipsec 01:32:11 the ipsec tutorial in freebsd is completly worng 01:32:28 i managed to set few first steps, then it's completly useless 01:32:51 i can manage to set the tunnel up and that it 01:43:01 rwp: Yes, when I mannualy set the variable, the error message disapear. I will investigate if somewhere it is me using -u (not that I changed mannually) 01:43:26 rwp: thanks for the help, keep you posted if any progress. 02:00:38 mane: have you considered wireguard? 02:00:56 i can do openvpn 02:01:08 someone else told me about wireguard already 02:01:29 i will try wireguard too 02:02:59 I have moved to wg completely (Free/OpenBSD, Linux). 03:14:53 freebsd documentation for openldap is horrid 03:14:57 and outdated 03:28:45 i need someone to tell me how to set up ldap 03:29:03 or at least hand me a proper howto 03:38:07 ok there is something usefull in the handbook, finally 03:57:04 <_0pr_> Hi guys, what is best practice to symlink a script, say ruby one, but it depends on a module in the original folder, when symlinked to /usr/local/bin, running it caused error, cannot find the denpendent module, only running from the original folder works... Anyone has any tips? 04:26:46 Is there a list for zfs or storage ? I don't see any. The only thing I'm finding anything about zfs is the handbook and the forums 04:27:36 Aw found a list for filesystems 04:31:24 yep, freebsd-fs@ 05:12:24 Thanks 05:42:25 mane, Last time I hated upon ipsec in the channel I apparently offended some ipsec users. But honestly I think ipsec is a terrible protocol. Never use it. Use openvpn or wireguard instead. 05:47:25 Or just ssh. 05:49:53 I also find sshuttle very useful. 06:35:28 how would i configure openldap client? 07:27:07 Hi 07:27:09 how much time could we expect to wait to see 14.1 coming ? 07:27:28 is that safe to instal 14.0, or should i wait for 14.1 ? 08:22:32 mane: for ipsec use strongswan 08:24:13 eoli3n: a friend of mine is running a few 14.0 instances without problems, you may want to look at https://www.freebsd.org/releases/14.0R/errata/#errata though 08:24:14 Title: FreeBSD 14.0-RELEASE Errata | The FreeBSD Project 08:24:17 jmnbtslsQE now i rather need to know how to properly set up openldap-server-26.6.6 and the clienets 08:24:20 eoli3n: looking at past releases, it's anywhere from 6-12 months until the first point release, weighted more to the longer side 08:25:44 eoli3n: we're already at p3, I hope we've got most wrinkles ironed out by now. but if your use case / hardware / configuration is very special, you might be the lucky one to discover even more bugs. that's just how software works 08:25:47 14.0 should be fine though for a fresh install. Generally I wait until a point release for upgrades from previous versions, as there's generally not rush 08:31:59 * meena started with RC3, but only because she missed RC1 08:32:13 or rather, ALPHA1 08:44:50 ok thanks, then i'll try the upgrade soon 08:48:08 a scary note on the upgrade page: After upgrading, it is not possible to use freebsd-update rollback to return to 12.4-RELEASE or 13.2-RELEASE. 08:48:53 of course there is always a possibility for zfs rollback :) so do not forget to place a snapshot prior upgrading 08:49:37 To quote Macbeth "I am in upgrades / Stepped in so far that should I wade no more, / Returning were as tedious as go o'er" 08:51:18 btw I should host ports also for 13.2 bsd versions, my question, will poudriere work as expected on 14.x ? 08:53:09 if you use a 13.2 jail 08:53:14 nerozero: ^ 08:53:53 poudriere do build ports in jails so ... ? 09:22:00 nerozero: Create a poudriere jail for each major version+arch combo for which you want to build packages 09:26:00 no, my question was - will this ^ work as expected? Because if I try to build a higher version BSD ports on a lower version BSD machine in jails, poudriere worns about it ... 09:26:21 s/worns/warns/g 09:28:57 the running kernel only creates an upper limit for the version in a jail, not a lower limit 09:38:34 nerozero: Is your builder box running 14? 09:53:13 vkarlsen, I still hesitate to upgrade to 14.0, but I would like to test it on a spare machine, so ... as an option I need my ports ( extra configured ) ... 09:54:57 * nerozero afk, if you reply to me, please add my nickname, will read later, thanks! 10:24:52 so, how do i log in with nis credentials on a nis network client? 10:53:39 After upgrading to 14.0-RELEASE I noticed my wifi is terrible. regdomain isn't used as specified in /etc/rc.conf for example. Defaults to US instead of NL. Startup and trying to get it to even work fully takes several netif restarts. I tried searching for it but can't seem to find anything. Anyone know what the issue might be? 10:54:44 After a netif stop/start it might get a IP adress and I can ping stuff on my LAN, but not the internet. Another restart makes that work somehow. 12:03:43 <_xor> Quick poll: Which do you prefer, readlink or realpath? 12:08:36 _xor: realpath 12:15:41 well, they do diffrent things, but when are you really interested where a symlink points and not the absolut path after resolving symlinks and stuff? 12:17:30 <_xor> There are instances where that information might be relevant (e.g. symlink should point to some object by convention, and if it doesn't, then create it). 12:19:13 yeah, but then you exactly know which one you need 12:41:49 readlink -f 12:44:36 _xor, actually stat, it support output formatting 13:45:35 well updated my home page, working on a project since yesterday :DD 13:45:37 https://vlepy.com/ 13:45:38 Title: Mirosław Leśniak 15:21:42 when i'm trying to compile a port (bitlbee w/ libpurple), is there a way to have it use the existing pkg pacakges for things like autoconf, xmlto, etc instead of trying to compile them all in ports? 15:33:52 Let's say, that I open a socket with IPV6_MULTICAST_LOOP set, send a packet with sendmsg() to multicast address and receive a reply from the kernel addressed to unicast address. Is it possible to receive those replies? If yes, then does it require some kind of specific receive socket configuration? 15:43:23 Demosthenex, "make install-missing-packages" in the port's dir. See ports(7) for more. 15:45:04 V_PauAmma_V: neato! 15:59:28 Hi folks, I have asked this question several days ago and had a few suggestions but none worked. I started the following thread https://forums.freebsd.org/threads/upgrading-13-2-14-0-from-source-is-not-successful.91263/ to try and get help from forum and also got some suggestions but they also didn't really help. Basically I tried to upgrade from 13.2-RELEASE to 14.0-RELEASE both via source and via binary updates. Compilation and installation (both world and 15:59:28 kernel) work fine. However after reboot, when issuing freebsd-version -k gives 14.0-RELEASE-p2, freebsd-version -r gives 13.2-RELEASE-p3. I've tried to use various boot environments, but the situation persists. I alo found the following thread https://serverfault.com/a/602263 but not sure whether this is applicable. Any help is appreciated. 15:59:29 Title: Upgrading 13.2 -> 14.0 from source is not successful | The FreeBSD Forums 15:59:30 Title: Conflicting information about the running kernel version in FreeBSD - Server Fault 16:08:06 speaking of install-missing-packages, why does it include build-dependencies of dependencies? shouldn't it let pkg resolve dependencies? 18:12:41 any ideas what happened to this zfs pool? host memory corruption maybe? https://bsd.to/CA0p 18:12:42 Title: dpaste/CA0p (Plain Code) 18:53:28 unixwitch, First, I don't know, but are there any kernel errors logged to /var/log/messages? 18:54:08 rwp: no 18:54:23 And then I would check the SMART data from each of the drives, starting with the ada0 and ada1 drives in the cache. smartctl -l error 18:56:25 Then I would look at the "zpool status -v" output as -v will add information about specific files that are affected. 18:56:35 rwp: i was assuming it wasn't a disk error due to lack of checksum errors, but i guess i'll check that (i didn't get any error mails from smartd though) 18:56:52 i included the zpool -v output in the paste, no files are listed there, it seems to be only metadata corruption 18:57:43 i wouldn't mind losing the data on this zvol (or its snapshot? as the zvol itself seems fine) since it's backed up anyway, but i'm worried the zpool won't import properly if i reboot now 18:59:12 Oh, that was -v there, sorry I didn't see it because I didn't see any affected files. I guess that is good. 19:00:03 smartctl -l error doesn't show anything concerning, a couple of disks have a small number of corrected errors but that's expected given their age 19:00:15 Here is an example error from my system from earlier in the year that shows the files listed with -v, just for an example of what it might have said: https://bsd.to/PnYw/raw 19:00:16 Title: PnYw 19:01:06 yeah, i saw that last month when i had an unrelated instance of data corruption due to the ossl(4) bug :-) 19:01:25 (which has been fixed and i don't have ossl(4) in the kernel anymore anyway, so it's not a repeat of that) 19:03:26 In my case it was a hard crash of the system. In my case the affected files were all temporary and log files that could go away. I was able to delete the files and snapshots and then scrub things clean. 19:04:33 i'm going to try deleting the affected dataset entirely a bit later (data/vm/media/disk1) but i need to wait until people aren't using it first. i suspect that might fail though because it seems like this prevents zfs from enumerating the snapshots at all 19:08:50 It's listed as an I/O error though. I don't see how it can be an I/O error if the kernel is not also listing it in a log file as an I/O error. 19:09:47 And if it is an actual I/O error then I expect to see a physical hardware manifestation of the problem. That's good and bad. Good because there is redundancy for the devices, bad because the controller is shared. But the actual problem has yet to be determined. 19:10:23 And if it is not an actual I/O error then it does seem like deleting the affected data, scrubs, and such should clear it out. But if it is not a hardware problem then why did the array get into that state? 19:10:44 I know you have asked yourself all of these questions already. I am really just confirming your analysis. 19:10:54 i think EIO in this case is just a general error code when ZFS can't read the data for some reason, not an actual disk I/O error 19:11:33 i'm waiting to see if scrub fixed it, that's going to take a while though: 2.23T / 18.8T scanned at 3.20G/s, 519G / 18.8T issued at 745M/s 19:22:02 unixwitch, I'll just mention some random thoughts and you pick out any that might apply. Are backups otherwise good and current? Do you have a spare disk on the shelf just in case? I run a SMART short selftest daily on every disk, I stagger the times so only one test is running on one disk in the array at any time. 19:23:24 rwp: i have a cold spare disk but since there's no indication anything is wrong with the disks, i'm not sure what i'd do with it :-) only part of the pool is backed up because there are very large, but low-value files (~10TB worth) that i don't want to pay backup costs for... i thought that was a reasonable compromise, but now i'm running into monthly data corruption issues, i might rethink that. and yes, smartd is set up to run ~weekly self tests 19:23:34 Depending upon the drive I used to be able to run long selftests but on the drives I currently have the long selftests are several hours long and degrade performance for all of that time and I stopped running long selftest on my drives. The short ones are okay still though. YMMV. 19:24:34 i have it staggered so each disk runs a long test at a 2-two interval, so each disk is tested once per month. the test takes ~18 hours on these disks though so it still hurts performance a bit... i've been meaning to look into running sectioned/partial tests 19:24:40 s/2-two/2-day 19:25:33 (aiui, that allows to e.g. test 2TB of the disk per day, so you can run all the tests during off hours... but i don't know if SCSI disks support this or if it's ATA-only) 19:25:36 There is no canonical right answer. You have to look at your own setup and make a judgement call individually. It's all different depending upon arrays and the collection of drives and the controller used. 19:27:10 I am still fixated on the zfs array reporting being an I/O error but the kernel not logging an I/O error. That's shaking my model of the machine. 19:27:17 Your data is probably okay though. 19:29:51 rwp: zfs returns EIO whenever it can't read the data, which includes corrupted pools. it doesn't always correlate with a physical I/O error 19:30:20 it *should* at least correlate with a checksum error but in this case it seems like either a ZFS bug, or some sort of memory/cpu hardware issue 19:30:36 (i'd say controller hardware issue, but everything is either mirror or raidz, so a controller issue should have been caught as a checksum error) 19:33:15 I am just working from the experiences I have had so far. But I am very happy that I have not hit every storage array problem! Happy to avoid them. But have hit a few over the years. So just relating based upon those. (The saying is, We are always fighting the last battle.) 19:35:51 I look forward to hearing the results of the currently running scrub. Let's expect that the scrub will repair everything unless and until we learn otherwise. 19:35:56 Good luck! 20:00:35 Hmm I'm reinstalling freebsd and it's taking forever to boostrap pkg 20:00:52 Anyone having issues with the server ? 20:01:56 jb1277976: try Ctrl+C and restart the bootstrap? 20:02:06 "the server" is a CDN 20:02:18 Yea did that and tried another they same issue 20:02:27 That's probably why 20:02:36 Anyway to fix ? 20:04:12 Even if I ssh to it it still gonna try to bootstrap 20:04:59 jb1277976: does your networking work? can you 'ping' anything? 20:05:20 oh is this during bsdinstall 20:06:01 Yes I'm in the network chatting here 20:06:12 It finished let's see how installing xorg goes 20:06:37 It's stalled 20:06:50 Can I change the ftp or something 20:08:55 you can edit /etc/pkg/FreeBSD.conf, i think you're supposed to copy it to /usr/local/etc/pkg/repos.d/FreeBSD.conf and edit it there though 20:09:07 'repos' not 'repos.d' sorry 20:14:17 Can I change the mirror there ? 20:16:29 jb1277976: yes, just put in the URL to the mirror you want to use 20:16:43 like i have this: url: "https://pkg.eden.le-Fay.org/${ABI}/latest" (but that particular example won't work for you since that's a private mirror) 20:17:02 Where is the original freebsd.conf ? 20:17:10 /etc/pkg/FreeBSD.conf 20:23:01 unixwitch where did you find that mirror? 20:23:27 jb1277976: i own that particular mirror, but you can find a list of public mirrors here: http://pkg.freebsd.org/ 20:23:29 Title: pkg0.nyi.FreeBSD.org 20:23:45 (in the 'other mirrors' section at the bottom of the page) 20:24:40 Thanks 20:29:30 unixwitch can you pastebin your freebsd.conf I'm getting no srv records 20:29:44 Want to make sure mine look the same 20:33:06 jb1277976: https://bsd.to/TTmW 20:33:07 Title: dpaste/TTmW (Plain Code) 20:33:21 jb1277976: note that only pkg.freebsd.org has SRV records, you don't need those if you pick a specific mirror (pkg.XXX.freebsd.org) 20:33:34 Ok 20:34:24 Brb 21:12:41 back up 21:17:20 what was the issue/fix? 22:01:34 * unixwitch is wondering about switching from zfs to gmirror/gstripe on the basis that while ZFS does good work in detecting errors, a single error can render the entire pool broken which is not ideal behaviour 23:47:48 unixwitch: The "scrub of death" is a bit of a myth. 23:49:12 unixwitch: Here's some reading for you: https://jrs-s.net/2015/02/03/will-zfs-and-non-ecc-ram-kill-your-data/ 23:49:14 Title: Will ZFS and non-ECC RAM kill your data? – JRS Systems: the blog 23:50:13 (Funny enough, I was just listening to a podcast about misinformation and disinformation: https://bigpicturescience.org/episodes/skeptic-check-naomi-klein 23:50:16 ) 23:53:05 meena: tl;dr? i have ECC RAM so i don't thin kthat applies to be 23:53:14 and i have no idea what "scrub of death" refers to 23:53:40 I'm not mason 23:53:48 oops, sorry 23:53:52 mason: ^ 23:54:29 Also, i should learn a romance language