01:37:21 is 'newfs -U -j -t -S 4096' readonable for a filesystem on a bhyve VM backed by zfs? i can't keep up with all the new types of su/journalling they keep adding 01:59:49 they added journaling ages ago 02:00:37 yes, but i haven't used UFS since the original softupdates 02:01:03 there's also two different types of journal, i guess gjournal is older and SU+J is preferred? newfs manpage doesn't really offer any guidance 02:09:43 yes, su+j is preferred afaik 07:11:02 it's also the default 07:11:39 as in, it's what's used by bsdinstall 07:13:23 both journaling and soft updates can be enabled at runtime with tunefs(8) too 07:20:10 Is journaling better (in terms of least data corruption & faster recovery) via "gjournal" or via "soft updates"? 07:22:02 journaling and softupdates and gjournal are three separate things, and SU+J are best used together 07:22:13 gjournal can, in theory, add journaling to any filesystem that doesn't have it 07:22:51 https://www.mckusick.com/softdep/suj.pdf is worth reading. 07:24:35 I wrote "journaling ... via "soft updates"" because of (from "newfs(8)"): -j Enable soft updates journaling ... 07:25:51 Read the paper to understand why it says that ;) 07:28:12 too long for now; will read later. 08:57:26 parv: btw, I was able to migrate back to CURRENT recently and tried out the drm-61-kmod package for my Arc A770 GPU, and sadly it kernel panics atm, even when I supplied the appropriate firmware bins from the linux-firmware by hand. :( 08:58:08 just to let you know 08:59:16 kenrap, Much appreciate the update. I had forgotten; after reading 2-3 times I realized why you had addressed me (because I had requested) 08:59:44 yeah, a month back or so :) 08:59:56 kenrap, Thanks to you for remembering for both of us 09:00:03 ;) 09:06:34 kenrap, So do you use VESA driver instead? 09:10:02 parv: I went back to my other GPU for now 09:10:14 Ah. Ok 09:53:27 hello hello! I hope you all are having a great Saturday! 10:07:56 Hi 11:47:15 https://freshbsd.org/freebsd/src/commit/aa3b7a2 \o/ 11:47:16 Title: FreeBSD / src / aa3b7a2 / /etc/rc add trace debug and verify - FreshBSD 11:52:57 Nice! 11:56:41 Yea, it's pretty neat 11:57:34 It will come in handy that's for sure :) 13:22:11 Happy Saturday 15:30:07 I've been a unix and linux user for decades but for some reason I have the hardest time understanding pam.d ... I'm trying to get winbind working for ssh, console, services, and sudo ... I can ssh in as a directory user and I can sudo for some commands (eg date) but I can'd sudo su - 15:30:14 /etc/pam.d/su https://paste.debian.net/1306872/ 15:30:17 Title: debian Pastezone 16:36:04 pam.d is an asshole. 16:36:13 Yep... on day three of fighting this 16:37:47 I also cannot mount any NFS shares on this new box, I get Stale NFS file handle every time 16:40:04 Pam and I aren't friends... I wish it was as simple as updating nsswitch.conf. 16:40:23 I just wish there was good documentation 16:40:38 Currently I can't sudo su - because it doesnt think root is a pam_winbind user 16:40:58 Does it work outside of sudo? 16:41:12 No, I can't login as root on the console anymore either 16:41:57 You'll prob want to boot into recovery and look at the contents of nsswitch.conf 16:42:08 Did you edit nsswitch.conf or only pam.d stuff? 16:42:17 Both 16:42:28 Do you remember what you set for the passwd line? 16:42:35 I dont think it's an nsswitch issue... it's almost certainly pam.d 16:42:51 passwd: files winbind 16:43:15 I can ssh in as a domain user and can sudo many things... I just can't switch to root because it seems to only be looking for domain users 16:43:16 files is in there so ya, no issues there like you said. 16:43:56 One sec, I run ldap so a little diff but same idea. Let me pull up my notes there. Did you remove anything from the pam files or just add? 16:45:14 Ok, in pam.d, I edit: sshd, su, and system 16:45:28 And I'm only adding lines 16:45:29 Which version of freebsd are you running btw? 16:45:48 13.2 16:50:32 https://pastebin.com/RiywNRpa <-- this is a snip from my notes for how I edit pam.d 16:50:33 Title: sshd```bashvi sshd``````bash## $FreeBSD$## PAM configuration for - Pastebin.com 16:50:44 bsd.to is throwing http 500 errors. 16:51:47 Thanks for sharing that 16:52:41 It's ldap instead of winbind but should at least serve as a reference for what I added and where. Just look for the ldap lines. 16:52:56 Yep going to try and emulate 17:04:00 Damn its just getting worse now 17:05:35 Can you restore the pam.d files to their orig? 17:05:52 I did, and that gets me back in with local users 17:06:22 Ok good! In theory you should be able to drop the winbind entries into the same spots I did my ldap entries. 17:06:53 I'm on FreeBSD 14-release so my files look different from yours ... but I essentially dropped them in the same place 17:07:04 Now auth.log shows success but ssh and sudo still fail 17:07:18 Do the logs say why they failed? 17:08:52 pam_winbind(sshd): user 'XXXX' granted access 17:08:53 Failed keyboard-interactive/pam 17:10:20 I gotta run, going to a bday party. 17:10:47 I wish you luck 17:10:52 I'll be back later today tho 17:30:30 No updates needed to update system to 13.2-RELEASE-p9. 17:30:54 freebsd-version -k > 13.2-RELEASE-p8 17:30:58 why? 17:31:42 i have done freebsd-update -r upgrade for 13.2 and did run install 3 times + rebooted 17:32:04 freebsd-version -kru ? 17:32:34 pretty sure the kernel did not change in -p9 17:32:34 twice 13.2-RELEASE-p8 and third pos 13.2-RELEASE-p9 17:33:35 freebsd-update install > No updates are available to install. 17:34:39 your userland is at -p9, the kernel did not change after -p8 and you are running -p8, all fine 17:38:38 lsof: WARNING: compiled for FreeBSD release 13.2-RELEASE-p9; this is 13.2-RELEASE-p8. 17:42:08 that seems to be a bug in how lsof detects the freebsd version 17:46:00 so i was useful 17:46:05 :) 17:49:00 ah, well, while building packges in poudriere you can't know what the kernel version will be, so the userland version gets compiled in for that https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225986#c27 17:49:03 Title: 225986 – sysutils/lsof false warning 18:12:49 ok 18:38:45 hm php 8.2 yourls installed. configured. under nginx all php pages blank. running directly php info.php does not produce any error. in nginx error nothing. access log shows 200 18:39:14 in php.ini errors turned on 18:39:27 i cant get any php in web showing up. all blank 18:42:02 php-fpm 18:42:13 this was pkg upgrade from php 7 as well 18:46:16 i mean no error 18:50:28 so nginx gives 200, no error on logs, from command line works info.php for example but when requesting over web server then blank 18:56:20 hm php-fpm is configured ritgh way and nginx uses same socket 19:05:17 ivaat: obviously not or it would be working. do you want to share your configs or should we just guess 19:09:27 rtprio, if socket would be wrong then nginx would throw error. i get 200 ok. sharing conf right now. one moment 19:16:55 it's probably php that's unhappy; turn up the logging for it 19:18:19 rtprio, www.conf for php-fpm https://paste.ovh/view/6842b91e | nginx.conf https://paste.ovh/view/d3bc319a | https://paste.ovh/view/f0560b74 19:18:21 Title: nginx.conf - paste.ovh - troubleshoot easily 19:18:33 error loggin is turned on 19:19:18 on command line php does not print any error 19:19:33 when executing php info.php for example 19:19:51 i suspect that your app is more complicated than info.php eh 19:20:41 did you turn up errors in php.ini too ? 19:21:29 ovh has their own TLD? what a bunch of clowns. 19:22:48 app may be complicated than that but phpinfo should run too.. all php files under freebsd 13.2 nginx, php-fpm php 8.2.14 over web white blank page 19:23:13 in old php 7 worked.. this was upgrade 19:23:38 and the app supports php 82? 19:24:06 turn up the error level and logging in php.ini too 19:24:20 yes but again simple should work as well 19:24:21 ivaat: Start removing all the stuff from line 9, up to (including) line 124, save and exit. make sure there is no mistake, so check with: nginx -t and if it says OK, then reload nginx with; nginx -s reload 19:24:29 and finally try a sample php file again. 19:24:34 https://paste.ovh/view/d3bc319a 19:24:35 Title: nginx.conf - paste.ovh - troubleshoot easily 19:25:13 adding the file into; /usr/local/www/shareurl.net/http/sample.php and checking with: yourwebsite/sample.php 19:25:41 thats what i did 19:25:59 you think sql injectiopn protection rules may affect? 19:26:04 i will try 19:26:13 used to work 19:28:55 nope, nothing 19:29:13 location / { try_files $uri $uri/ /yourls-loader.php$is_args$args; } 19:29:16 What's this? 19:29:28 this yourls docs nginx rule 19:29:43 yourls is php app 19:33:44 ivaat: Do you have /usr/local/etc/php.ini file 19:33:46 ? 19:35:00 ivaat: You removed an older version of PHP and installed PHP 8.2, have you created/updated your /usr/local/etc/php.ini file? 19:35:46 yes i copied for test production ini file to /usr/local/etc/php.ini 19:36:25 cp /usr/local/etc/php.ini-production /usr/local/etc/php.ini 19:43:58 ivaat: How about the content of /usr/local/etc/nginx/nginx.conf? 19:44:21 tercaL, i removed the lines you recommended. did not help 19:44:38 Pastelink the /usr/local/etc/nginx/nginx.conf file please. 19:48:06 tercaL, https://paste.ovh/view/484017dd 19:48:07 Title: nginx.conf - paste.ovh - troubleshoot easily 19:58:48 i have to go for today. thank you for responding 20:42:42 hmm, what does this mean Feb 10 19:33:15 thyme gssd[913]: gss_acquire_cred: principal_name for non-root 21:45:40 only one more PR and then I have nothing else assigned \o/