Re: Another kernel fault incident on a Vultr OpenBSD VM
Hi, * Mihai Popescu wrote: > > It lowers my confidence in Vultr as a reliable OpenBSD host. > > Very well, it will match the confidence of running OpenBSD on a virtual > machine. I have all my public OpenBSD instances running as virtual machines at IONOS (ionos.com). Their VPS product is based on VMWare ESXI and I have my machines running there since early 6.x. So far all rock stable, one can upload custom ISOs, has KVM access and you can even type your softraid passphrase via keyboard and no need to use the softkeyboard (as with others). Cheers Matthias
Re: Another kernel fault incident on a Vultr OpenBSD VM
Sorry to hear about your issues. Vultr has been top notch in my experience. I have a couple of Vultr hosted nodes in different data centers that have been running OpenBSD, they’ve been online for four years now (with downtime for logging into the console to activate FDE during reboots from syspatch and sysupgrades ofc.) I’ve not encountered any real issues that wasnt pre-announced - and what downtime there has been has been scant. > On Apr 15, 2022, at 4:31 PM, open...@maniaphobic.org wrote: > > Hi all, > > I'm posting this for the benefit of OpenBSD community members hosting virtual > machines on Vultr. > > I encountered the same failure that Claus A. reported in December: > > > cd*.iso reboot loop (vultr, Skylake AVX MDS) > https://www.mail-archive.com/misc@openbsd.org/msg180415.html > > > To summarize, the VM halts with this kernel fault during boot, shortly before > running fsck: > > > kernel: privileged instruction fault trap, code=0 > Stopped at mds_handler_skl_avx+0x33: clflush > __ALIGN_SIZE+0x500(%rid,%rax,8) > > > It then drops in to ddb. > > As in Claus's case, the solution was to ask Vultr support to migrate the > guest to another hypervisor. The representative assigned to my case was > unable to explain the root cause. > > This is the second incident in the past month that resulted in a lengthy > service outage caused by a Vultr misconfiguration. In the previous incident, > the representative told me, "OpenBSD has very special configurations that are > required on our end to work properly with our virtualization software". It > lowers my confidence in Vultr as a reliable OpenBSD host.
Re: no output from zathura
I've committed a fix. If you report problems with ports, it would help to include at least: - OpenBSD version and machine arch (it never hurts to include the full dmesg) - Package version - (plus the description of what happens, any console messages etc, like you included here) And preferably on ports@ rather than misc. On 2022-04-18, Shadrock Uhuru wrote: > Hi everyone > i have zathura zathura-ps zathura-pdf-mupdf installed, > i run zathura from the command line with zathura file.pdf which opens zathura > with nothing > displayed, > the shell that i run zathura from displays the following > > zathura:/usr/local/lib/zathura/libpdf-mupdf.so: undefined symbol > 'jbig2_ctx_new_imp' > zathura:/usr/local/lib/zathura/libpdf-mupdf.so: undefined symbol > 'jbig2_data_in' > zathura:/usr/local/lib/zathura/libpdf-mupdf.so: undefined symbol > 'jbig2_make_global_ctx' > zathura:/usr/local/lib/zathura/libpdf-mupdf.so: undefined symbol > 'jbig2_global_ctx_free' > zathura:/usr/local/lib/zathura/libpdf-mupdf.so: undefined symbol > 'jbig2_complete_page' > zathura:/usr/local/lib/zathura/libpdf-mupdf.so: undefined symbol > 'jbig2_page_out' > zathura:/usr/local/lib/zathura/libpdf-mupdf.so: undefined symbol > 'jbig2_release_page' > zathura:/usr/local/lib/zathura/libpdf-mupdf.so: undefined symbol > 'jbig2_ctx_free' > zathura:/usr/local/lib/zathura/libpdf-mupdf.so: undefined symbol > 'opj_set_default_decoder_parameters' > zathura:/usr/local/lib/zathura/libpdf-mupdf.so: undefined symbol > 'opj_create_decompress' > zathura:/usr/local/lib/zathura/libpdf-mupdf.so: undefined symbol > 'opj_set_info_handler' > zathura:/usr/local/lib/zathura/libpdf-mupdf.so: undefined symbol > 'opj_set_warning_handler' > zathura:/usr/local/lib/zathura/libpdf-mupdf.so: undefined symbol > 'opj_set_error_handler' > zathura:/usr/local/lib/zathura/libpdf-mupdf.so: undefined symbol > 'opj_setup_decoder' > zathura:/usr/local/lib/zathura/libpdf-mupdf.so: undefined symbol > 'opj_stream_default_create' > zathura:/usr/local/lib/zathura/libpdf-mupdf.so: undefined symbol > 'opj_stream_set_read_function' > zathura:/usr/local/lib/zathura/libpdf-mupdf.so: undefined symbol > 'opj_stream_set_skip_function' > zathura:/usr/local/lib/zathura/libpdf-mupdf.so: undefined symbol > 'opj_stream_set_seek_function' > zathura:/usr/local/lib/zathura/libpdf-mupdf.so: undefined symbol > 'opj_stream_set_user_data' > zathura:/usr/local/lib/zathura/libpdf-mupdf.so: undefined symbol > 'opj_stream_set_user_data_length' > zathura:/usr/local/lib/zathura/libpdf-mupdf.so: undefined symbol > 'opj_read_header' > zathura:/usr/local/lib/zathura/libpdf-mupdf.so: undefined symbol 'opj_decode' > zathura:/usr/local/lib/zathura/libpdf-mupdf.so: undefined symbol > 'opj_stream_destroy' > zathura:/usr/local/lib/zathura/libpdf-mupdf.so: undefined symbol > 'opj_destroy_codec' > zathura:/usr/local/lib/zathura/libpdf-mupdf.so: undefined symbol > 'opj_image_destroy' > zathura:/usr/local/lib/zathura/libpdf-mupdf.so: undefined symbol > 'gumbo_parse_with_options' > zathura:/usr/local/lib/zathura/libpdf-mupdf.so: undefined symbol > 'gumbo_destroy_output' > zathura:/usr/local/lib/zathura/libpdf-mupdf.so: undefined symbol > 'gumbo_normalized_tagname' > error: Could not load plugin '/usr/local/lib/zathura/libpdf-mupdf.so' (Cannot > load specified object). > error: Could not determine file type. > > --- > > this error appears if i try to open a pdf or ps file, > i managed to open one out of about ten ps files i tried, > is this a known problem or something i'm not doing right ? > > shadrock > > -- Please keep replies on the mailing list.
Re: yacc.h
Tito Mari Francis Escaño wrote: > Thanks for the response Omar. > The tarball can be downloaded from > https://sourceforge.net/projects/objc/files/src/objc-3.3.25.tar.gz Sorry, with "attach the tarball" I meant the ports' tarball. I assumed you had a WIP port, apologies. > The error is illustrated below: > [image: portable obj compiler error.png] for these things please avoid images: just copy and past the text into the email. Oh, and when doing so, please include the full log (if possible, sometimes certain bits can be removed if are long and it's really, really, really unlikely to not have issues; in doubt include everything.) you can use script(1) to transcript your terminal session, or maybe something simpler like $ make 2>&1 | tee build.log and then include `build.log' in the email. I'm not joking, the most interesting thing (i.e. how lex.m was produced) is outside of your screenshot; most likely right in the line before the one at the top... > I already installed Bison hoping it will provide yacc.h, but it didn't also > include that file. > I also tried using the y.tab.h file but it had the same error. > I tried to comment out the yacc.h header, still got the same error message. First of all, from where did you get a /usr/local/bin/objc executable? I don't find anything that provides it in packages. I can't build this objc because I need a bootstrap compiler. I admit I haven't tried hard and only glazed ad the *.txt files; but when asking please include the list of things you did if they're not incredibly obvious. It's difficult to help without knowing what things you did. I don't have a magic ball. Anyway, I can *guess* what's happening. yacc (or bison) isn't producing the yacc.h file that is included in src/obj/lex.lm (there are other files named so, files, but I think it's from that.) You can take a look at what files are produced (maybe y.tab.h?) and patch lex.lm to include the correctly-named file. Or find a way to make yacc/bison (or whatever the configure choosen) to produce yacc.h (again, in case of yacc see the -d flag and -o). Since this is an autoconf-based project, remember to re-run ./configure if you install other software (it doesn't notice otherwise) > On Tue, Apr 19, 2022 at 1:44 AM Omar Polo wrote: > > > Tito Mari Francis Escaño wrote: > > > Hi everyone, > > > I'm trying to build Portable Object Compiler from > > > https://sourceforge.net/projects/objc/ in OpenBSD snapshot but it keeps > > > complaining that it can't find yacc.h so it won't push through. > > > > It's always a good idea to share a tarball, especially when asking for > > help. It makes your situation "reproducible" (sorta) so it's easier for > > someone else to help you debug the issue. It's also incredibly useful > > to also copy/paste the *exect* output from your command, including the > > errors. > > > > > I have the build tools installed during initial installation, so I was > > > wondering where the problem is. > > > Is there such a thing as yacc.h in any package or ports? > > > > When in doubt you can use pkglocate to look for files owned by packages, > > even if you don't have them installed. It's an incredibly useful tool. > > However, in this case I doubt it'll help you. > > > > yacc is included in base and given that's a parser generator I don't > > find strange to have it as requirement for a compiler. Yacc usually > > generates a file called `y.tab.c' and, if -d is provided, it generates > > y.tab.h too. Bison (a GNU implementation of yacc) does the same but > > instead of the "y" uses the name of the yacc file as base for the output > > IIRC. > > > > Maybe playing with the -d, -b and/or -o flags helps? what if you > > "force" it to use GNU bison? > > > > > Please let me know. > > > Thanks. > > > > > >
Re: Another kernel fault incident on a Vultr OpenBSD VM
Hi everyone, Another good alternative is "transip .eu" They use KVM as a virtualization platform and i think there was no major issue about OpenBSD since version 6.0. (at least for me).
Re: Another kernel fault incident on a Vultr OpenBSD VM
I also can recommend openbsd.amsterdam :) My OpenBSD VM at netcup.de (KVM) also runs without any issues for over year On 4/18/22 00:00, Alexis wrote: Mihai Popescu writes: It lowers my confidence in Vultr as a reliable OpenBSD host. Very well, it will match the confidence of running OpenBSD on a virtual machine. Not sure exactly what you mean by that, but i can say i'm very happy with my OpenBSD VM provided by openbsd.amsterdam. Alexis.
no output from zathura
Hi everyone i have zathura zathura-ps zathura-pdf-mupdf installed, i run zathura from the command line with zathura file.pdf which opens zathura with nothing displayed, the shell that i run zathura from displays the following zathura:/usr/local/lib/zathura/libpdf-mupdf.so: undefined symbol 'jbig2_ctx_new_imp' zathura:/usr/local/lib/zathura/libpdf-mupdf.so: undefined symbol 'jbig2_data_in' zathura:/usr/local/lib/zathura/libpdf-mupdf.so: undefined symbol 'jbig2_make_global_ctx' zathura:/usr/local/lib/zathura/libpdf-mupdf.so: undefined symbol 'jbig2_global_ctx_free' zathura:/usr/local/lib/zathura/libpdf-mupdf.so: undefined symbol 'jbig2_complete_page' zathura:/usr/local/lib/zathura/libpdf-mupdf.so: undefined symbol 'jbig2_page_out' zathura:/usr/local/lib/zathura/libpdf-mupdf.so: undefined symbol 'jbig2_release_page' zathura:/usr/local/lib/zathura/libpdf-mupdf.so: undefined symbol 'jbig2_ctx_free' zathura:/usr/local/lib/zathura/libpdf-mupdf.so: undefined symbol 'opj_set_default_decoder_parameters' zathura:/usr/local/lib/zathura/libpdf-mupdf.so: undefined symbol 'opj_create_decompress' zathura:/usr/local/lib/zathura/libpdf-mupdf.so: undefined symbol 'opj_set_info_handler' zathura:/usr/local/lib/zathura/libpdf-mupdf.so: undefined symbol 'opj_set_warning_handler' zathura:/usr/local/lib/zathura/libpdf-mupdf.so: undefined symbol 'opj_set_error_handler' zathura:/usr/local/lib/zathura/libpdf-mupdf.so: undefined symbol 'opj_setup_decoder' zathura:/usr/local/lib/zathura/libpdf-mupdf.so: undefined symbol 'opj_stream_default_create' zathura:/usr/local/lib/zathura/libpdf-mupdf.so: undefined symbol 'opj_stream_set_read_function' zathura:/usr/local/lib/zathura/libpdf-mupdf.so: undefined symbol 'opj_stream_set_skip_function' zathura:/usr/local/lib/zathura/libpdf-mupdf.so: undefined symbol 'opj_stream_set_seek_function' zathura:/usr/local/lib/zathura/libpdf-mupdf.so: undefined symbol 'opj_stream_set_user_data' zathura:/usr/local/lib/zathura/libpdf-mupdf.so: undefined symbol 'opj_stream_set_user_data_length' zathura:/usr/local/lib/zathura/libpdf-mupdf.so: undefined symbol 'opj_read_header' zathura:/usr/local/lib/zathura/libpdf-mupdf.so: undefined symbol 'opj_decode' zathura:/usr/local/lib/zathura/libpdf-mupdf.so: undefined symbol 'opj_stream_destroy' zathura:/usr/local/lib/zathura/libpdf-mupdf.so: undefined symbol 'opj_destroy_codec' zathura:/usr/local/lib/zathura/libpdf-mupdf.so: undefined symbol 'opj_image_destroy' zathura:/usr/local/lib/zathura/libpdf-mupdf.so: undefined symbol 'gumbo_parse_with_options' zathura:/usr/local/lib/zathura/libpdf-mupdf.so: undefined symbol 'gumbo_destroy_output' zathura:/usr/local/lib/zathura/libpdf-mupdf.so: undefined symbol 'gumbo_normalized_tagname' error: Could not load plugin '/usr/local/lib/zathura/libpdf-mupdf.so' (Cannot load specified object). error: Could not determine file type. --- this error appears if i try to open a pdf or ps file, i managed to open one out of about ten ps files i tried, is this a known problem or something i'm not doing right ? shadrock
Re: Auto layout for disk partitions - a new user's perspective
"James Mintram" writes: > For context, I need erlang 24 + elixir 13 and the current packages > are older than that. Which is why I have found myself working > with ports almost immediately (pro level yak shaving..) There were a post in ports mailing list with a patch for erlang port update: https://marc.info/?l=openbsd-ports&m=162162511924040&w=2 You may want to use it as starting point. -- Renato
Re: yacc.h
Thanks for the response Omar. The tarball can be downloaded from https://sourceforge.net/projects/objc/files/src/objc-3.3.25.tar.gz The error is illustrated below: [image: portable obj compiler error.png] I already installed Bison hoping it will provide yacc.h, but it didn't also include that file. I also tried using the y.tab.h file but it had the same error. I tried to comment out the yacc.h header, still got the same error message. On Tue, Apr 19, 2022 at 1:44 AM Omar Polo wrote: > Tito Mari Francis Escaño wrote: > > Hi everyone, > > I'm trying to build Portable Object Compiler from > > https://sourceforge.net/projects/objc/ in OpenBSD snapshot but it keeps > > complaining that it can't find yacc.h so it won't push through. > > It's always a good idea to share a tarball, especially when asking for > help. It makes your situation "reproducible" (sorta) so it's easier for > someone else to help you debug the issue. It's also incredibly useful > to also copy/paste the *exect* output from your command, including the > errors. > > > I have the build tools installed during initial installation, so I was > > wondering where the problem is. > > Is there such a thing as yacc.h in any package or ports? > > When in doubt you can use pkglocate to look for files owned by packages, > even if you don't have them installed. It's an incredibly useful tool. > However, in this case I doubt it'll help you. > > yacc is included in base and given that's a parser generator I don't > find strange to have it as requirement for a compiler. Yacc usually > generates a file called `y.tab.c' and, if -d is provided, it generates > y.tab.h too. Bison (a GNU implementation of yacc) does the same but > instead of the "y" uses the name of the yacc file as base for the output > IIRC. > > Maybe playing with the -d, -b and/or -o flags helps? what if you > "force" it to use GNU bison? > > > Please let me know. > > Thanks. > > >
Re: reordering libraries: fdcresult: overrun
rtw0 dtw0 writes: > Hi, > When my OpenBSD vm boots I receive the following message: > > *reordering libraries: fdcresult: overrun* > Vm version, host version, etc. etc. Not enough info here. There was an issue address in vmm(4) that caused noise from the fdc(4) driver, but that was fixed in November and will be in 7.1 once released. https://cvsweb.openbsd.org/cgi-bin/cvsweb/src/sys/arch/amd64/amd64/vmm.c?rev=1.295&content-type=text/x-cvsweb-markup -dv
reordering libraries: fdcresult: overrun
Hi, When my OpenBSD vm boots I receive the following message: *reordering libraries: fdcresult: overrun* How serious is this system report? Cheers, Andy
Re: yacc.h
Tito Mari Francis Escaño wrote: > Hi everyone, > I'm trying to build Portable Object Compiler from > https://sourceforge.net/projects/objc/ in OpenBSD snapshot but it keeps > complaining that it can't find yacc.h so it won't push through. It's always a good idea to share a tarball, especially when asking for help. It makes your situation "reproducible" (sorta) so it's easier for someone else to help you debug the issue. It's also incredibly useful to also copy/paste the *exect* output from your command, including the errors. > I have the build tools installed during initial installation, so I was > wondering where the problem is. > Is there such a thing as yacc.h in any package or ports? When in doubt you can use pkglocate to look for files owned by packages, even if you don't have them installed. It's an incredibly useful tool. However, in this case I doubt it'll help you. yacc is included in base and given that's a parser generator I don't find strange to have it as requirement for a compiler. Yacc usually generates a file called `y.tab.c' and, if -d is provided, it generates y.tab.h too. Bison (a GNU implementation of yacc) does the same but instead of the "y" uses the name of the yacc file as base for the output IIRC. Maybe playing with the -d, -b and/or -o flags helps? what if you "force" it to use GNU bison? > Please let me know. > Thanks.
Re: Auto layout for disk partitions - a new user's perspective
As a long time OpenBSD user I install from packages but also build from ports. There is a usage case for both, but realize building packages is not a "standard" system. Twenty years ago building packages from ports was the norm, but not today. 73 diana On April 18, 2022 9:35:27 AM MDT, Thomas Frohwein wrote: > > >I think it might be worth repeating that packages are the recommended >way to use third-party software. And that's also a great justification >why there is no /usr/ports partition on a default install. > >Unless you are doing ports development work, you shouldn't need the >ports tree.
Re: Auto layout for disk partitions - a new user's perspective
On Mon, Apr 18, 2022 at 04:15:46PM +, James Mintram wrote: > Thanks for all of the very useful replies, I have managed to get > everything working. > > For context, I need erlang 24 + elixir 13 and the current packages > are older than that. Which is why I have found myself working > with ports almost immediately (pro level yak shaving..) > > I ended up carving out some space from the /home partition > for ports and setting WRKOBJDIR as recommended. > > As for the /usr/src folder, I personally like to work with git > due to familiarity with the tools. I have seen got, and like the > idea of separating the repository from the worktree, so I will > look into using that. It also possible to change the sizes of the auto layout: choose " (E)dit auto layout" during install and type: R You can use suffixes and use increments, e.g. +4G to add 4G to a partition. -Otto > > On Mon, 18 Apr 2022, at 3:35 PM, Thomas Frohwein wrote: > > On Mon, Apr 18, 2022 at 01:36:18PM -, Stuart Henderson wrote: > > > > [...] > > > > > > 2) Should there be a /usr/local/pobj partition created with correct > > > > mount > > > > options? (I appreciate building ports is an "advanced" thing to do - > > > > but it > > > > feels weird having to mess with partition layout after a fresh install > > > > just to > > > > build them) > > > > > > Ports doesn't use /usr/local/pobj by default (you can set it via WRKOBJDIR > > > in mk.conf, but /usr/local isn't a great place for a filesystem with rapid > > > changes during a port build). Also, /usr/local/pobj *is* normally > > > wxallowed. > > > > > > If you are using ports I would strongly recommend a separate filesystem > > > for /usr/ports, either with default ports-related directories (i.e. don't > > > change dirs in mk.conf) and set that wxallowed, or with a separate > > > WRKOBJDIR > > > on a wxallowed filesystem. > > > > I think it might be worth repeating that packages are the recommended > > way to use third-party software. And that's also a great justification > > why there is no /usr/ports partition on a default install. > > > > Unless you are doing ports development work, you shouldn't need the > > ports tree. There are rare ports which don't have a package (for > > license reasons). If you need one of them, CVS has the advantage over > > git that you can checkout a subdirectory. If you do this for an > > individual port, the space requirements should be minimal. Still, for > > regular use you shouldn't need to deal with any of this. > > > > >
yacc.h
Hi everyone, I'm trying to build Portable Object Compiler from https://sourceforge.net/projects/objc/ in OpenBSD snapshot but it keeps complaining that it can't find yacc.h so it won't push through. I have the build tools installed during initial installation, so I was wondering where the problem is. Is there such a thing as yacc.h in any package or ports? Please let me know. Thanks.
Re: Auto layout for disk partitions - a new user's perspective
On Mon, Apr 18, 2022 at 01:36:18PM -, Stuart Henderson wrote: [...] > > 2) Should there be a /usr/local/pobj partition created with correct mount > > options? (I appreciate building ports is an "advanced" thing to do - but it > > feels weird having to mess with partition layout after a fresh install just > > to > > build them) > > Ports doesn't use /usr/local/pobj by default (you can set it via WRKOBJDIR > in mk.conf, but /usr/local isn't a great place for a filesystem with rapid > changes during a port build). Also, /usr/local/pobj *is* normally wxallowed. > > If you are using ports I would strongly recommend a separate filesystem > for /usr/ports, either with default ports-related directories (i.e. don't > change dirs in mk.conf) and set that wxallowed, or with a separate WRKOBJDIR > on a wxallowed filesystem. I think it might be worth repeating that packages are the recommended way to use third-party software. And that's also a great justification why there is no /usr/ports partition on a default install. Unless you are doing ports development work, you shouldn't need the ports tree. There are rare ports which don't have a package (for license reasons). If you need one of them, CVS has the advantage over git that you can checkout a subdirectory. If you do this for an individual port, the space requirements should be minimal. Still, for regular use you shouldn't need to deal with any of this.
Re: Auto layout for disk partitions - a new user's perspective
the installer creates partition layouts for a variety of _regular_ usage patterns. Both of these situations you describe are not the normal pattern. We don't want to over-allocate space to specific purposes like that. Other systems do one giant root partition and then avoid these space issues. There are downsides with the policy of creating seperate partitions like we do, so that we can vary mountpoint flat options. We kind of shrug and cope with it. James Mintram wrote: > Hi. I am new to OpenBSD, so these questions come from my first > experience with the system. > > I selected the auto layout option when partitioning my 256GB drive. I have > then found issues while doing the following: > > 1) Cloning src from the github mirror and checking it out, completely fills > the /usr/src parition. > > 2) Building some ports fail because /usr/local/pobj is not on an wxallowed fs. > > > My questions are: > > 1) Should the default /usr/src partition be bigger on large disks? > > 2) Should there be a /usr/local/pobj partition created with correct mount > options? (I appreciate building ports is an "advanced" thing to do - but it > feels weird having to mess with partition layout after a fresh install just > to > build them)
Is there a way to build mod_auth_kerb?
Hello, I am trying to build mod_auth_kerb for apache2 on OpenBSD 6.9 I installed heimdal-libs-7.7.0p0 and downloaded the latest src for mod_auth_kerb from github After unpacking and configuring the following way: ./configure --with-krb5=/usr/local/heimdal --with-krb4=no I try to run 'make' I get a bunch of warnings like these: ``` /usr/local/heimdal/include/krb5-protos.h:18:52: note: expanded from macro 'KRB5_DEPRECATED_FUNCTION' #define KRB5_DEPRECATED_FUNCTION(x) __attribute__((__deprecated__(x))) ^ src/mod_auth_kerb.c:1547:47: warning: incompatible pointer types passing 'request_rec *' (aka 'struct request_rec *') to parameter of type 'const char *' [-Wincompatible-pointer-types] log_rerror(APLOG_MARK, APLOG_ERR, 0, r, ^ src/mod_auth_kerb.c:379:46: note: passing argument to parameter 'fmt' here const request_rec *r, const char *fmt, ...) ^ src/mod_auth_kerb.c:1553:50: warning: incompatible pointer types passing 'request_rec *' (aka 'struct request_rec *') to parameter of type 'const char *' [-Wincompatible-pointer-types] log_rerror(APLOG_MARK, APLOG_NOTICE, 0, r, ^ src/mod_auth_kerb.c:379:46: note: passing argument to parameter 'fmt' here const request_rec *r, const char *fmt, ...) ^ src/mod_auth_kerb.c:1560:44: warning: incompatible pointer types passing 'request_rec *' (aka 'struct request_rec *') to parameter of type 'const char *' [-Wincompatible-pointer-types] log_rerror(APLOG_MARK, APLOG_DEBUG, 0, r, ^ src/mod_auth_kerb.c:379:46: note: passing argument to parameter 'fmt' here const request_rec *r, const char *fmt, ...) ``` and the following error: ``` Error while executing cc -O2 -pipe -g -D_POSIX_THREADS -pthread -I/usr/local/include/apache2 -I/usr/local/include/apr-1/ -I/usr/local/include/apr-1/ -I/usr/local/include/db4 -I/usr/local/include -I. -Ispnegokrb5 -I/usr/local/heimdal/include -I/usr/local/include -c src/mod_auth_kerb.c -fPIC -DPIC -o src/.libs/mod_auth_kerb.o apxs:Error: Command failed with rc=65536 . *** Error 1 in /root/mod_auth_kerb-master (Makefile:16 'src/mod_auth_kerb.so') ``` Is it possible to compile that module on OpenBSD at all? -- Best regards Maksim Rodin
Re: Another kernel fault incident on a Vultr OpenBSD VM
Ramnode allows the easy use of OpenBSD on their VMs. You can bring your own ISO file. Sent from my iPhone > On Apr 18, 2022, at 3:25 AM, Sean Kamath wrote: > > I’ve been running a few Vultr instances since. . . before 2018. > Periodically, something comes up. I think in the 5-ish years, I’ve had 2 > issues. Raise an issue with their support team and state what happened. > Both times, they responded with some information and that they needed to > change/rebuild some configuration. They responded quickly and fixed the > other instances that weren’t affected (because if they live migrated to other > servers, it would then become a problem). > > My point is just that, yeah, there can be issues, but the support folks seem > to know how to handle OpenBSD reasonably well. > > Sean > > PS I forget exactly what the first issue was some 1453 days ago, but it > apparently wouldn’t boot. The second issue was 103 days ago, and would cause > the VM to lockup after something like 10 hours (it was variable). > > PPS I’m still way behind in upgrades, so can’t speak for anything after 6.7 > >> On Apr 17, 2022, at 16:42, Hakan E. Duran wrote: >> >> For whatever it is worth, I have been using an OpenBSD VM with Vultr >> since 6.7 edition and so far didn't have issues. I may have been a lucky >> one that landed on their good side, but I am quite happy with them so >> far. >> >> Hakan >> >>> On 22/04/17 04:00PM, latin...@vcn.bc.ca wrote: > > Mihai Popescu writes: > >>> It lowers my confidence in Vultr as a reliable OpenBSD host. >> >> Very well, it will match the confidence of running OpenBSD on a >> virtual machine. > > Not sure exactly what you mean by that, but i can say i'm very > happy with my OpenBSD VM provided by openbsd.amsterdam. > > > Alexis. > >>> >>> What are the most appropriated hosting vendors for OpenBSD vm? I have 3 >>> with vultr! and thinking to use my old laptop for them! >>> >>> >>> >
Re: Auto layout for disk partitions - a new user's perspective
On 2022-04-18, James Mintram wrote: > Hi. I am new to OpenBSD, so these questions come from my first > experience with the system. > > I selected the auto layout option when partitioning my 256GB drive. I have > then found issues while doing the following: > > 1) Cloning src from the github mirror and checking it out, completely fills > the /usr/src parition. > > 2) Building some ports fail because /usr/local/pobj is not on an wxallowed fs. > > My questions are: > > 1) Should the default /usr/src partition be bigger on large disks? /usr/src is sized for just a checkout rather than a full repository mirror with history. This is normal for cvs (and if you do have a full repo mirror with cvs, that would be in a different place than /usr/src). If you're using the git conversion you could do a shallow checkout, or use a larger fs, or place it elsewhere. On a typical system I don't think it's helpful to have this much larger (though it is now starting to get a little tight for a checkout so maybe it could go up a few hundred MB). /usr/src isn't needed on a typical machine and raising the size will impact on sizes of other partitions, which might make it more likely people run into harder problems later.. > 2) Should there be a /usr/local/pobj partition created with correct mount > options? (I appreciate building ports is an "advanced" thing to do - but it > feels weird having to mess with partition layout after a fresh install just > to > build them) Ports doesn't use /usr/local/pobj by default (you can set it via WRKOBJDIR in mk.conf, but /usr/local isn't a great place for a filesystem with rapid changes during a port build). Also, /usr/local/pobj *is* normally wxallowed. If you are using ports I would strongly recommend a separate filesystem for /usr/ports, either with default ports-related directories (i.e. don't change dirs in mk.conf) and set that wxallowed, or with a separate WRKOBJDIR on a wxallowed filesystem. -- Please keep replies on the mailing list.
Re: Another kernel fault incident on a Vultr OpenBSD VM
I’ve been running a few Vultr instances since. . . before 2018. Periodically, something comes up. I think in the 5-ish years, I’ve had 2 issues. Raise an issue with their support team and state what happened. Both times, they responded with some information and that they needed to change/rebuild some configuration. They responded quickly and fixed the other instances that weren’t affected (because if they live migrated to other servers, it would then become a problem). My point is just that, yeah, there can be issues, but the support folks seem to know how to handle OpenBSD reasonably well. Sean PS I forget exactly what the first issue was some 1453 days ago, but it apparently wouldn’t boot. The second issue was 103 days ago, and would cause the VM to lockup after something like 10 hours (it was variable). PPS I’m still way behind in upgrades, so can’t speak for anything after 6.7 > On Apr 17, 2022, at 16:42, Hakan E. Duran wrote: > > For whatever it is worth, I have been using an OpenBSD VM with Vultr > since 6.7 edition and so far didn't have issues. I may have been a lucky > one that landed on their good side, but I am quite happy with them so > far. > > Hakan > > On 22/04/17 04:00PM, latin...@vcn.bc.ca wrote: >>> >>> Mihai Popescu writes: >>> > It lowers my confidence in Vultr as a reliable OpenBSD host. Very well, it will match the confidence of running OpenBSD on a virtual machine. >>> >>> Not sure exactly what you mean by that, but i can say i'm very >>> happy with my OpenBSD VM provided by openbsd.amsterdam. >>> >>> >>> Alexis. >>> >> >> What are the most appropriated hosting vendors for OpenBSD vm? I have 3 >> with vultr! and thinking to use my old laptop for them! >> >> >>
