00:05:34 kenrap and I just notice that this last microcode update doesn't cover Ryzen 9 08:28:23 hi - the certificate on sandbox.freebsdfoundation.org expired ages ago (08/02/2020), any idea whom to poke to fix that? 08:31:32 interestingly duckduckgo found showed that host even before the main freebsdfoundation.org site… 12:11:09 hi all 12:22:13 hi 15:03:21 /join #freebsd-ops 15:48:18 what's the earliest point you can upgrade to 14 using freebsd-update? the betas? 15:52:25 I think it's the RCs, but I'm not sure 15:52:27 <_xor> How's traffic shaping via ipfw? 15:52:39 * _xor is exploring ipfw again 15:56:24 markmcb: man page says: In general, binary updates are available for ALPHA, BETA, RC, and RELEASE 16:34:16 yuripv: thanks. i guess PRERELEASE is something separate? that's what confused me before. i dont think i had seen that one and it says it's not supported. 16:43:25 side note, i'm sure there's no changing it, but as a newcomer "release, stable, and current" are terribly confusing, and release sounds like the least desireable of the three just based on what the words literally mean. stable and current should get a "dev" prefix or something. 16:59:28 How do I record a kernel panic as a log file? 17:10:06 Nevermind. I needed to set dumpdev back to "AUTO" for crashdumps. 17:26:46 hello my vps is sort of unresponsive in some ways 17:28:56 https://bsd.to/Bygy for example 17:28:57 Title: dpaste/Bygy (Plain Text) 17:29:07 I just wait literally and nothing seems to happen 17:32:12 ahoi, installing freebsd 13.2 what is the difference betwenn "GPT (BIOS)" and plain "GPT"? 18:13:38 how do I get the pkg manager to work? 18:29:48 If sixpiece comes back, may be worth pointing them to https://docs.freebsd.org/en/books/handbook/ports/#pkgng-intro and ask them to be more specific on what they're trying to achieve. 18:29:49 Title: Chapter 4. Installing Applications: Packages and Ports | FreeBSD Documentation Portal 18:57:36 Going nuts trying to get a web app with a /cgi-bin working with fcgiwrapper ... when I try and run fcgiwrapper in the foreground and then call the cgi-bin scripts nothing shows in the console 18:57:41 What's the best way to debug? 19:02:12 This is related to FreeBSD? 19:16:02 Well... it's the platform I'm on. I take your point, but generally I find it very hard to find/get support for things running on FreeBSD in non-freebsd forums 19:40:42 SpaceBass: try use printf (or equivalent) to output debug info to /tmp/your_temp_file.log 19:44:34 Right now it's like my nginx isn't even passing things to fcgiwrapper 19:45:55 SpaceBass: ktrace the running process and see if it's firing off some kind of error when it ought to be invoking fcgiwrapper 19:47:45 I would check nginx logs files first, it could be some misconfiguration 19:48:12 Access shows the right url with a success... error (set to debug) shows nothing related to fcgi 19:48:15 Same thing, only less complete. Easier I guess. 19:48:28 SpaceBass: kk, back to ktrace then 19:49:08 Would I ktrace nginx? 19:49:22 man ktrace, but essentially ktrace -p 19:49:39 Pid of what though? 19:50:11 * checkpoint thinks that ktracing nginx could be a bit complicated :) 19:50:27 Not if you just search out invocations and/or errors. 19:50:41 Tracing doesn't mean second-guessing every action from launch. 19:56:55 stranegly I cannot connect ktrace to a pid, it quits instantly: 19:56:57 rz@butterfly:~ % sudo ktrace -p 78720 -tc 19:56:57 rz@butterfly:~ % echo $? 19:56:59 0 19:57:43 ktrace just starts the trace 19:58:04 Yeah I didn't get output either 19:58:08 there should now be a file ktrace.out in the directory you ran ktrace in, which is appended to by the process 19:58:22 it's a binary file, use kdump to interpret it 19:59:57 RhodiumToad: yeah, got it, thanks. 20:01:10 Ah yeah that helps ... was trying to cat the blob :) 20:01:57 note that the trace will continue until all affected processes end or you explicitly stop it 20:03:51 Well if I'm reading it right, I think I'm at least confirming that I'm not passing anything to fcgiwrap 20:04:11 SpaceBass: Yeah, search for execs, and maybe see if they fail, for instance. 20:04:24 You should be able to find out if it's at least trying to invoke your cgi handler. 20:04:29 And if it is, what happens. 20:04:54 No invocations... I guess that's a start 20:05:01 Implies my nginx.conf is borked 20:05:03 I hope 20:05:34 SpaceBass: You might also verify that it's reading all the config bits you expect. Don't know if they're broken up or not. 20:06:42 SpaceBass, Do you have cgi-bin + nginx working yet? I have a working setup that I could share if not. 20:07:19 * checkpoint once had to debug a proprietary linux binary with ptrace which resulted in this small tool: https://github.com/Fabmicro-LLC/nosyscall 20:07:42 rwp, I copied a working setup from a nearly identical server... only difference is working server is 13.2 and my problem is 14.0 20:08:10 checkpoint: Why not strace, out of curiosity? 20:08:19 Hmm... I don't have 14.0 online here yet. Perhaps I should try that in a vm and see if I have the problem too. 20:09:52 mason: is there strace in FreeBSD ? 20:10:21 checkpoint, No strace. See truss. 20:10:25 mason: I had to run it on FreeBSD (my laptop), so I used Linuxulator 20:11:28 rwp: exactly, truss uses ptrace, and so I did. :) 20:11:38 checkpoint: Ah, that makes more sense now. 20:11:53 I assumed you were debugging it on GNu/Linux. 20:11:58 s/u/U/ 20:12:14 for the next to the last u anyway 20:13:14 mason: the very point was to make that overbloated proprietary piece of linux software run on my latop (FreeBSD) 20:15:36 I think its my nginx.conf ... not sure why I keep trying to force myself to use it and not apache 20:16:52 SpaceBass: is it too late to switch ? 20:17:01 Im stubborn :) 20:17:07 * checkpoint has never used nginx, frankly 20:17:17 And I can only change so many variables in this set up before I'll get totally lost :) 20:49:53 Think I got it! Added some debug lines to nginx logging and found the problem 20:53:12 * checkpoint never doubts printf() based debugging 20:59:43 SpaceBass: let me guess: some dependancy (module) is not met ? 21:00:16 No, just dumb error on my end... the root declaration for my cgi-bin included the full path, not just the root 21:44:36 SpaceBass, Given the choice between Nginx and Apache I will choose Nginx every time. 21:58:56 Spacebass: I agree with rwp, unless you have a specific need, configuring nginx is far lighter and more intuitive 22:01:14 It feels simpler and more lightweight, I just need more time with it 22:01:24 And now I need to figure out how to set my locale system-wide 22:09:54 SpaceBass: see defaults in /etc/login.conf 22:10:19 Its correct there... this port is so quirky... I had this problem last time I set it up but that was 3 years ago and of course I didn't document it 22:10:29 And the mainteiner isn't exactly easy to work with 22:12:14 what port is that exactly ? 22:12:55 security/p5-openxpki 22:15:34 There's some trick to getting it to display proper English in the WebUI vs I18N_OPENXPKI_LOGIN (for instance) 22:20:47 there's this code: 22:20:48 #default i18n language 22:20:48 my $language = "en_GB"; 22:20:55 in ./work/openxpki-openxpki-9bd1fea/tools/automated_wf_visual/wf_graphs.pl 22:22:17 try changing $language to "en_US.UTF-8" 22:23:13 also it accepts "langs" parameger 22:23:58 check into the code, it may give you some clue 22:28:59 I dont think its hard coded... there's a whole bit of documentation for setting in linux.. but the FreeBSD port is kinda mum on how to do it 22:32:53 Run a simple CGI that prints locale(1) to check that locale is used for your CGI scripts. Is is anything different from what locale(1) shows ? 23:02:39 Wondering if I need to update the backend mysql db to use utf8 23:50:41 which file has scrub cron in /etc/periodic/daily/ ? I want to remove as scrubbing the hdd 4tb takes half a day everyday 23:56:14 it doesn't do the scrub every day, only if it's been more than some threshold of days since the last completed one 23:56:50 daily_scrub_zfs_enable="NO" added to /etc/periodic.conf will disable it 23:57:30 also, it seems to be "NO" by default? did you turn it on yourself?