gmake compile of python3.12 crashes on openBSD 7.5 but not on openBSD 7.4
I was able to compile Python 3.12 from source code on openBSD 7.4. However, after upgrade to 7.5 the compile process crashes with core dump: cc -pthread -g -Wl,--export-dynamic -o Programs/_testembed Programs/_testembed.o -L. -lpython3.12 -lpthread -lutil -lm _testembed.c:1848 (./Programs/_testembed.c:1848)(Programs/_testembed.o:(test_init_use_frozen_modules)): warning: wcscpy() is almost always misused, please use wcslcpy() sed -e "s,/usr/bin/env python3,/home/kabiraatmonallabs/Execution/Runtime/bin/python3.12," < ./Tools/scripts/2to3 > build/scripts-3.12/2to3-3.12 sed -e "s,/usr/bin/env python3,/home/kabiraatmonallabs/Execution/Runtime/bin/python3.12," < ./Tools/scripts/idle3 > build/scripts-3.12/idle3.12 sed -e "s,/usr/bin/env python3,/home/kabiraatmonallabs/Execution/Runtime/bin/python3.12," < ./Tools/scripts/pydoc3 > build/scripts-3.12/pydoc3.12 Illegal instruction (core dumped) gmake[2]: *** [Makefile:1142: checksharedmods] Error 132 gmake[2]: Leaving directory '/home/kabiraatmonallabs/Execution/Runtime/Python-3.12.2' gmake[1]: *** [Makefile:793: profile-gen-stamp] Error 2 gmake[1]: Leaving directory '/home/kabiraatmonallabs/Execution/Runtime/Python-3.12.2' gmake: *** [Makefile:805: profile-run-stamp] Error 2 I am unable to find a proper debugger into which to load the python.core generated after core dump, so can't provide any useful debug info. I don't think this is due to some changes in Python code that is creating the core dump. Any ideas would be helpful. Thanks Sandeep
unable to startx/xinit on additional virtual terminal
I am running OpenBSD on a laptop with X windows starting on f5 vtty via Xenodm login manager. I am unable to start another session of X from a different vtty. xinit or startx fails with Fatal server error: - no console drivers found Supported drivers: wscons I should be able to launch an additional x11 session given one is already running by default.
Re: need help to access my machine after upgrade -- system immediately logs me out
Cool. That worked. Also my system is back up and running. Turns out the i3
libraries installed had become incompatible with the rest of the system.
Simply deleted those and glib2 packages and reinstalled everything. Works
well now. Thanks for all the help :).
Cheers
Sandeep
On Wed, Apr 3, 2024 at 12:51 AM Otto Moerbeek wrote:
> On Wed, Apr 03, 2024 at 12:45:33AM +0530, Sandeep Gupta wrote:
>
> > Thank you for all the inputs. This is so useful. I am able to at least
> > access the file system and rescue the data.
> > However, I'm not able to restore the system yet. The command "pkg_add
> -u"
> > runs into "out of memory error".
> > ulimit -a shows decent memory:
> > memory(kbytes) 11872836.
>
> you want to increase the data limit, ulimit -d
>
> -Otto
>
> >
> > On Tue, Apr 2, 2024 at 5:04 PM Stuart Henderson <
> stu.li...@spacehopper.org>
> > wrote:
> >
> > > On 2024-04-01, Sandeep Gupta wrote:
> > > >
> > > > However when i tried to log from the console -- the login message
> shows
> > > but
> > > > the system logs me out immediately.
> > > > On the desktop gui too, with only root I was able to login. But
> running
> > > > xterm from the fvwm menu fails.
> > > > I am a bit clueless as to how to gain access to the system.
> > >
> > > Try this:
> > >
> > > Boot into single-user mode ("boot -s" at the boot loader prompt)
> > > fsck -p
> > > mount -a -t nonfs
> > >
> > > Hopefully that will get you access to the system. You can try looking
> at
> > > system logs to see if that gives any clues about the problem. TERM
> won't
> > > be set so you may want to use e.g. "TERM=xterm less /var/log/messages"
> > > etc. $HOME/.xsession-errors might give some clues too.
> > >
> > > If you think that updating packages might help then 'sh /etc/netstart'
> > > to get working net and proceed with pkg_add -u as usual.
> > >
> > >
> > >
>
Re: need help to access my machine after upgrade -- system immediately logs me out
For disclousre, I was able to access the shell/file system via Boot into
single-user mode ("boot -s" at the boot loader prompt) -- followed by
fsck -p
mount -a -t bonds as mentioned in earlier replies.
Thank you.
On Wed, Apr 3, 2024 at 12:45 AM Sandeep Gupta
wrote:
> Thank you for all the inputs. This is so useful. I am able to at least
> access the file system and rescue the data.
> However, I'm not able to restore the system yet. The command "pkg_add -u"
> runs into "out of memory error".
> ulimit -a shows decent memory:
> memory(kbytes) 11872836.
>
> On Tue, Apr 2, 2024 at 5:04 PM Stuart Henderson
> wrote:
>
>> On 2024-04-01, Sandeep Gupta wrote:
>> >
>> > However when i tried to log from the console -- the login message shows
>> but
>> > the system logs me out immediately.
>> > On the desktop gui too, with only root I was able to login. But running
>> > xterm from the fvwm menu fails.
>> > I am a bit clueless as to how to gain access to the system.
>>
>> Try this:
>>
>> Boot into single-user mode ("boot -s" at the boot loader prompt)
>> fsck -p
>> mount -a -t nonfs
>>
>> Hopefully that will get you access to the system. You can try looking at
>> system logs to see if that gives any clues about the problem. TERM won't
>> be set so you may want to use e.g. "TERM=xterm less /var/log/messages"
>> etc. $HOME/.xsession-errors might give some clues too.
>>
>> If you think that updating packages might help then 'sh /etc/netstart'
>> to get working net and proceed with pkg_add -u as usual.
>>
>>
>>
Re: need help to access my machine after upgrade -- system immediately logs me out
Thank you for all the inputs. This is so useful. I am able to at least
access the file system and rescue the data.
However, I'm not able to restore the system yet. The command "pkg_add -u"
runs into "out of memory error".
ulimit -a shows decent memory:
memory(kbytes) 11872836.
On Tue, Apr 2, 2024 at 5:04 PM Stuart Henderson
wrote:
> On 2024-04-01, Sandeep Gupta wrote:
> >
> > However when i tried to log from the console -- the login message shows
> but
> > the system logs me out immediately.
> > On the desktop gui too, with only root I was able to login. But running
> > xterm from the fvwm menu fails.
> > I am a bit clueless as to how to gain access to the system.
>
> Try this:
>
> Boot into single-user mode ("boot -s" at the boot loader prompt)
> fsck -p
> mount -a -t nonfs
>
> Hopefully that will get you access to the system. You can try looking at
> system logs to see if that gives any clues about the problem. TERM won't
> be set so you may want to use e.g. "TERM=xterm less /var/log/messages"
> etc. $HOME/.xsession-errors might give some clues too.
>
> If you think that updating packages might help then 'sh /etc/netstart'
> to get working net and proceed with pkg_add -u as usual.
>
>
>
Re: need help to access my machine after upgrade -- system immediately logs me out
Very likely that would be issue. The problem is that I am not able to access a shell for root or the regular user. On the console, I get logged out immediately. On GUI, fvwm, the root is able to login. I can launch top and other utilities. But I am not able to launch xterm. I guess I would have to boot using external usb, mount the disk and repair it. On Tue, Apr 2, 2024 at 1:57 AM Peter N. M. Hansteen wrote: > On Tue, Apr 02, 2024 at 12:44:01AM +0530, Sandeep Gupta wrote: > > Hello, > > > > I need to access my desktop local machine after I did a sysupgrade -s (I > > had reasons to do so because some rust libraries were too old for some > > applications). > > Sysupgrade seems to have gone fine. Disk is healthy no issues reported. > > > > However when i tried to log from the console -- the login message shows > but > > the system logs me out immediately. > > On the desktop gui too, with only root I was able to login. But running > > xterm from the fvwm menu fails. > > This sounds very much like a situation where the base system and packages > are out seriously of sync AND your user is et up with a default shell from > packages (I am guessing bash). > > The solution would likely be to log in as root, run pkg_add -D snap -u > to get the latest snapshot packages, then try to log in as your regular > user. > > > -- > Peter N. M. Hansteen, member of the first RFC 1149 implementation team > https://bsdly.blogspot.com/ https://www.bsdly.net/ https://www.nuug.no/ > "Remember to set the evil bit on all malicious network traffic" > delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds. > >
need help to access my machine after upgrade -- system immediately logs me out
Hello, I need to access my desktop local machine after I did a sysupgrade -s (I had reasons to do so because some rust libraries were too old for some applications). Sysupgrade seems to have gone fine. Disk is healthy no issues reported. However when i tried to log from the console -- the login message shows but the system logs me out immediately. On the desktop gui too, with only root I was able to login. But running xterm from the fvwm menu fails. I am a bit clueless as to how to gain access to the system. Some help would be great. -S
nodejs/node package seems broken on openbsd 7.4 on amd64
As best i can see, node (node-18.18) is broken and cannot be used at all.
No matter the package config "npm install" results in same error:
```
npm install
npm ERR! code 1
npm ERR! path
/home/kabiraatmonallabs/Garage/my-skeleton-app/node_modules/esbuild
npm ERR! command failed
npm ERR! command sh -c node install.js
npm ERR! node:internal/errors:865
npm ERR! const err = new Error(message);
npm ERR! ^
npm ERR!
npm ERR! Error: Command failed:
/home/kabiraatmonallabs/Garage/my-skeleton-app/node_modules/esbuild/bin/esbuild
--version
npm ERR! at checkExecSyncError (node:child_process:890:11)
npm ERR! at Object.execFileSync (node:child_process:926:15)
npm ERR! at validateBinaryVersion
(/home/kabiraatmonallabs/Garage/my-skeleton-app/node_modules/esbuild/install.js:99:28)
npm ERR! at
/home/kabiraatmonallabs/Garage/my-skeleton-app/node_modules/esbuild/install.js:286:5
{
npm ERR! status: null,
npm ERR! signal: 'SIGILL',
npm ERR! output: [ null, Buffer(0) [Uint8Array] [], Buffer(0)
[Uint8Array] [] ],
npm ERR! pid: 50423,
npm ERR! stdout: Buffer(0) [Uint8Array] [],
npm ERR! stderr: Buffer(0) [Uint8Array] []
npm ERR! }
npm ERR!
npm ERR! Node.js v18.18.0
```
Re: running on aws
Thank you. I reviewed that approach. I don't have a proper machine (machine
with vmm) to give this a try.
Although I do wish to know what is wrong with my approach. If the
aws-openbsd works then this approach should also work. Its more
accessible. Both are using /dev/sda1 for the EBS device name.
```
--root-device-name /dev/sda1 --virtualization-type hvm \
--description "${DESCR}" --block-device-mappings \
DeviceName="/dev/sda1"
```.
On Sun, May 7, 2023 at 6:34 PM Renato dos Santos wrote:
> Try with this https://github.com/shazaum/aws-openbsd
>
> Em sáb, 6 de mai de 2023 15:42, Sandeep Gupta
> escreveu:
>
>> I have installed openbsd 7.3 image on a EBS volume. Then created an AMI
>> image and launched an instance
>> from this image. Looked promising as I can see initial boot messages.
>> The attached screenshot shows the current state of the boot.
>> My guess is that I am not using fstab entry correctly for aws.
>> The current entry looks
>>
>> /dev/sd0b none swap sw
>> /dev/sd0a / ffs rw 1 1
>>
>> The ami=image was created using the "
>> aws ec2 register-image --name "OpenBSD-AMI" --description "OpenBSD AMI
>> based on snapshot" --architecture x86_64 --root-device-name /dev/sda1
>> \
>> --block-device-mappings
>>
>> "[{\"DeviceName\":\"/dev/sda1\",\"Ebs\":{\"SnapshotId\":\"snap-0a1947fcaa2bda898\"}}]"
>>
>> The /dev/sda1 is required on aws and can't be changed.
>>
>>
>> Bit stuck at this stage as I don't know what other fstab entry to try or
>> how
>>
>> to see what devices the os is seeing. I can mount the device in other
>> bsd instance
>>
>> and investigate the dmesg if that would help.
>>
>
Re: permission denied when writing to mounted directory exported by NFS server
On test setup I got this fixed. I will try to see if it works on actual system. I made following changes: - modified /etc/exports entry ` /nfs/testdir -alldirs -maproot=root:wheel -network=192.168.0 -mask=255.255.255.0 ` The not-working version used "-maproot=root". - started nfsd from command line ` doas /sbin/nfsd -tun 4 ` For some reason starting using rcctl fails as can be seen below: ``` You have new mail. openbsd$ doas rcctl start portmap mountd nfsd nfsd(failed) openbsd$ doas /sbin/nfsd -tun 4 openbsd$ ps aux | grep nfsd root 21178 0.0 0.1 480 1132 ?? S 12:51PM0:00.01 nfsd: master root 95864 0.0 0.0 176 520 ?? S 12:51PM0:00.00 nfsd: server root 29237 0.0 0.0 176 520 ?? S 12:51PM0:00.00 nfsd: server root 37092 0.0 0.0 176 520 ?? S 12:51PM0:00.00 nfsd: server root 40371 0.0 0.0 176 520 ?? S 12:51PM0:00.00 nfsd: server adming 20594 0.0 0.1 524 1264 00 S+p12:51PM0:00.02 grep nfsd ``` For debugs, here is output of rpcinfo: [adming@cluster-node2]~% rpcinfo -p 192.168.0.122 program vers proto port service 102 tcp111 portmapper 102 udp111 portmapper 151 udp859 mountd 153 udp859 mountd 151 tcp806 mountd 153 tcp806 mountd 132 udp 2049 nfs 133 udp 2049 nfs 132 tcp 2049 nfs 133 tcp 2049 nfs Since, on both client and server, the root is writing -- the uid and gid is 0. On Fri, Feb 10, 2023 at 5:13 AM wrote: > On Thu, Feb 09, 2023 at 08:40:50AM +0100, Daniele B. wrote: > > Unfortunately - personal experience - NFS is not the best offering from > OpenBSD: it is enough > > combersome to setup and easy to lose grip: something unsafe to keep me > away from it. > > > > > What exactly do you mean ? > > rcctl enable portmap mountd nfsd > > what is so cumbersome with that ? > > What can we do better ? > > > > However, for your testing purposes, I can suggest you there is a > specific tool to test, server and client > > status. looking to the man I guess it should be nfsstat pointed to one > or the other host same time. > > Probably some other people could be more detailed. > > > > -- Daniele Bonini > > > > Feb 8, 2023 17:00:09 Sandeep Gupta : > > > > > Looking at the docs I am not able > > > to find any otherconfig options for access control on the client side. > > > There is nothing in the logs on the server side as well. Any pointers > to > > > debug/fix would be of great help. > > > >
Re: permission denied when writing to mounted directory exported by NFS server
Following up on this. I looked into the /var/log/messages/ and /var/log/daemon. Both are quite after starting the portmap, mountd, and nfsd services. Here is verbose output from the client side when mounting the share: ``` [adming@cluster-node2]~% sudo mount -t nfs -o rw,noauto -v 192.168.0.122:/nfs/testdir /home/adming/mntpt2 mount.nfs: timeout set for Thu Feb 9 11:34:52 2023 mount.nfs: trying text-based options 'vers=4.2,addr=192.168.0.122,clientaddr=192.168.0.187' mount.nfs: mount(2): Protocol not supported mount.nfs: trying text-based options 'vers=4,minorversion=1,addr=192.168.0.122,clientaddr=192.168.0.187' mount.nfs: mount(2): Protocol not supported mount.nfs: trying text-based options 'vers=4,addr=192.168.0.122,clientaddr=192.168.0.187' mount.nfs: mount(2): Protocol not supported Created symlink /run/systemd/system/remote-fs.target.wants/rpc-statd.service → /usr/lib/systemd/system/rpc-statd.service. mount.nfs: trying text-based options 'addr=192.168.0.122' mount.nfs: prog 13, trying vers=3, prot=6 mount.nfs: trying 192.168.0.122 prog 13 vers 3 prot TCP port 2049 mount.nfs: prog 15, trying vers=3, prot=17 mount.nfs: trying 192.168.0.122 prog 15 vers 3 prot UDP port 724 [adming@cluster-node2]~% cd mntpt2 [adming@cluster-node2]~/mntpt2% ls alfpha testfile [adming@cluster-node2]~/mntpt2% touch y touch: cannot touch 'y': Permission denied ``` Am out of ideas as what to test/debug. On Wed, Feb 8, 2023 at 9:27 PM Sandeep Gupta wrote: > I have a default installation of openbsd, with portmap, mountd, nfsd > services started via rcctl. I have following entry in /etc/exports > > /nfs/testdir -alldirs -maproot=root -network=192.168.0 -mask=255.255.255.0 > > I am able to mount the exported share on client (centos) as follows: > > sudo mount -t nfs -o rw,noauto -v 192.168.0.122:/nfs/testdir mntpt3 > > From the client, I can read the contents. But writing inside the mounted > directory yields permission denied error. Looking at the docs I am not able > to find any otherconfig options for access control on the client side. > There is nothing in the logs on the server side as well. Any pointers to > debug/fix would be of great help. >
Re: stuck on configuring netboot raspberry pi from an openbsd VM : RPC time for server 192.168.0.255
Yes we do need those. The only change is that instead of dhcpd, I am using dnsmasq which takes care of tftp and dhcp services. I figured out the error was because I had not started the bootparamd. Once I started the bootparamd, the client boots passed that error and panics with nfs mount. I am investigating that error currently. On Thu, Feb 9, 2023 at 1:17 AM wrote: > > I have configured "/etc/dnsmasq", "/etc/ethers", "/etc/hosts", and > > "/etc/exports" and "/etc/bootparams". > > The PXE boot in UEFI boot is able to contact the tftp/dhcp server and > > download the bsd kernel and boot up > > However, just before (or while) mounting nfs shares as root I get the > > RPC > > timeout error. > > > > ``` > > nfs_boot: using interface bse0 with revarp & bootparams > > RPC timeout for server 192.168.0.255 > > ``` > > You didn't say if you did this but you also need to change > > /etc/dhcpd.conf > > and enable rarpd, dhcpd, bootparamd, nfs_server, and finally portmap > on your boot server. > > Use tcp not udp for NFS. Add to the fstab for the mount point. > > Add a swapfile for the client; ideally a local disk but NFS will do. It > doesn't need to be large. > > My notes on diskless date back to OpenBSD 4.x but I'm pretty sure you > need these even now. > > > J > >
permission denied when writing to mounted directory exported by NFS server
I have a default installation of openbsd, with portmap, mountd, nfsd services started via rcctl. I have following entry in /etc/exports /nfs/testdir -alldirs -maproot=root -network=192.168.0 -mask=255.255.255.0 I am able to mount the exported share on client (centos) as follows: sudo mount -t nfs -o rw,noauto -v 192.168.0.122:/nfs/testdir mntpt3 >From the client, I can read the contents. But writing inside the mounted directory yields permission denied error. Looking at the docs I am not able to find any otherconfig options for access control on the client side. There is nothing in the logs on the server side as well. Any pointers to debug/fix would be of great help.
stuck on configuring netboot raspberry pi from an openbsd VM : RPC time for server 192.168.0.255
So, after tons of research and trial and error, I was finally able to netboot the bsd kernel served from a VM running OpenBSD. I have configured "/etc/dnsmasq", "/etc/ethers", "/etc/hosts", and "/etc/exports" and "/etc/bootparams". The PXE boot in UEFI boot is able to contact the tftp/dhcp server and download the bsd kernel and boot up However, just before (or while) mounting nfs shares as root I get the RPC timeout error. ``` nfs_boot: using interface bse0 with revarp & bootparams RPC timeout for server 192.168.0.255 ``` In an old post ( https://www.mail-archive.com/search?l=misc@openbsd.org=subject:%22Trying+to+set+diskless%5C%288%5C%29+%5C-%5C-+hanging+in+%5C%22RPC+timeout+for+server%5C%22%22=newest=1), someone mentioned that in some old post that had similar issue and it was related to broadcast address not being captured by bootparamd. My netboot server is on a network bridge. Could that be an issue? I am not totally familiar with ins-and-outs of networking for these protocols so am little lost. How to go about debugging this? Has any come across this issue or can help, would be great. Thanks -S
Re: running openbsd as guest OS under KVM virtualization on Raspberry Pi 4
:). Got this working. My stumbling block was install72 was an img file, while all the KVM vm installations start with iso image. I didn't know how to make KVM read install72.img. I found qemu-img which converts img to qcow2 format that can be directly read by KVM engine. After that, it was a breeze, added an extra virtIO disk on which the openBSD can be installed from the qcow2 image. On Fri, Dec 23, 2022 at 6:15 PM Bodie wrote: > On Fri Dec 23, 2022 at 12:29 PM CET, Sandeep Gupta wrote: > > Has anyone tried running openbsd as a guest OS under KVM on arm hardware? > > I have posted the question also on serverfault ( > > > https://serverfault.com/questions/1118710/install-openbsd-as-guest-os-in-kvm-virtualization-on-fedora-running-raspberry-pi > ). > > > > If anyone has experience/ideas on how to go about it, it will be of great > > help. > > I feel it should be feasible to run openbsd under KVM. > > > > These are computers. They do not run feelings. > > 1) Have Raspberry Pi 4 - done > 2) Install/Enable KVM in Linux on RPI 4 - you probably did that > 3) https://www.openbsd.org/arm64.html - something to do for you > 4) Report on misc@ how it went and include dmesg or any errors > > > Thanks > > Sandeep > >
running openbsd as guest OS under KVM virtualization on Raspberry Pi 4
Has anyone tried running openbsd as a guest OS under KVM on arm hardware? I have posted the question also on serverfault ( https://serverfault.com/questions/1118710/install-openbsd-as-guest-os-in-kvm-virtualization-on-fedora-running-raspberry-pi). If anyone has experience/ideas on how to go about it, it will be of great help. I feel it should be feasible to run openbsd under KVM. Thanks Sandeep
Re: virtualization in openbsd running on Raspberry pi
Got it. Thank you for confirming. On Thu, Dec 22, 2022 at 8:58 AM Mike Larkin wrote: > On Thu, Dec 22, 2022 at 08:47:00AM +0530, Sandeep Gupta wrote: > > Just wanted to double confirm that it's not possible to run virtual > > instances of openBSD on openBSD running on Raspberry Pi. > > This is because the CPU has no support for SLAT/EPT (but these are only > for > > intel/amd. doesn't say about arm). > > > > Also, in my instance, I don't see vmctl installed. In fact, doing `rcctl > > start vmd` fails. But don't see error messages in /var/log/messages. > > Where are error messages logged for running daemons? > > > > Thanks > > Sandeep > > vmm/vmd is only supported on amd64. >
virtualization in openbsd running on Raspberry pi
Just wanted to double confirm that it's not possible to run virtual instances of openBSD on openBSD running on Raspberry Pi. This is because the CPU has no support for SLAT/EPT (but these are only for intel/amd. doesn't say about arm). Also, in my instance, I don't see vmctl installed. In fact, doing `rcctl start vmd` fails. But don't see error messages in /var/log/messages. Where are error messages logged for running daemons? Thanks Sandeep
Re: unable to install texlive_texmf-full due to python reaching 2.7 end-of-life
HI Stuart, I was redoing the install to reproduce the error messages. But this time it went fine. I guess the difference was previously I ran the command as root and this time as sudo/doas user. Might be something to do with PATH environment for root vs. non-root user. Sorry for the noise. Thanks -S out Description: Binary data
unable to install texlive_texmf-full due to python reaching 2.7 end-of-life
Is there a workaround for installing texlive_full on openbsd 7.1? Installing via package manager currently fails because it has Python2.7 as dependency which has reached end-of-life. Can I force the installation? Thanks Sandeep
Trying to install openBSD on Raspberry Pi CM4+IO board ..keyboard hangs
Hello, I managed to get the OpenBSD installer up and running on CM4 mounted on the Pi official I/O board. I installed UEFI bootloader in emmc and had OpenBSD miniroot image burnt on SSD (connected to usb 3.0 over pcie). When CM4 boots it invokes the UEFI loader, which drops me at UEFI prompt. At the prompt I do "set tty fb0" and then "boot" which hands over the booting to openBSD. Which runs through fine. However, the moment openBSD installer starts, the keyboard hangs/doesn't get recognized. So I stuck at the Install/Update/... option prompt of the bootloader. Is there a simple workaround for this? I am not sure if there are other roadblocks down the installation road but it seems promising enough to try if the keyboard issue is a minor hassle. Thanks for taking a look at this. -Sandeep
disk perf tool fio hangs on Pi4
Hello, I was doing some disk iops perf testing on a fresh install of OpenBSD on Rpi4 using the fio tool. I am at most able to run 2 runs of fio after which the system would hang. On the runs that do get completed I get a very low iops number. I thought the problem may be either in the fio tool or in the hardware disk driver. So I did a fresh install of Raspian and redid the tests. The benchmarks run without hassle and perf numbers are good too. What should the next recourse be? Also, it seems the benchmark numbers are better with direct I/O then without. But, it seems openBSD does not support direct I/O. Thanks Sandeep
Re: OpenBSD hardware accelerated video? (In X on Intel/AMDGPU/ARM64)
I would great to have hardware acceleration for Raspberry Pi. But Pi's video hardware drivers are not open source. They are some propriety binary bits. Even theoretically, I don't see if those binary bits can be used within OpenBSD system. On Thu, Jul 21, 2022 at 2:20 AM Mihai Popescu wrote: > > With your email now however the original question remains: Does OpenBSD > actually support hardware accelerated video decoding today? > > General answer: NO. > > A more detailed answer is like this: there is a talk on the list about > libvaapi (if i recall correctly) implementation for intel only. It was > suggested, I am not sure if landed into the ports. > Hardware video decoding must be done thru some libs, I think they are > vaapi and vdpau for the moment. Then the used software (vlc, mpv, > chromium, firefox) must be compiled with support for one of these, or > both maybe. > > Both ways are praised and hated on the internet, depending of what you > read. As always, there is much marketing involved. > > Anyone is welcome to correct some possible mistakes, I am not a video > hardware expert. > >
Re: booting OpenBSD on Raspberry pi4 without using sdcard for UEFI
Yes, the document does mention: - standard miniroot supports boot without additional firmware - by default, the kernel output is on console On Sat, May 21, 2022 at 2:53 PM Stuart Henderson wrote: > On 2022-05-20, Sandeep Gupta wrote: > > Hello, > > > > This post here ( > > http://matecha.net/posts/openbsd-on-pi-4-with-full-disk-encryption/) > claims > > its possible to > > boot OpenBSD directly from USB without the need for UEFI on sdcard. > > I tried today but couldn't get it to work. I got a blank screen during > the > > installation process. What I did was > > 1) updated the eeprom (bootloader) > > 2) set boot to usb > > 3) wrote install71.img onto ssd. > > > > The boot process did start but I got a blank screen. I was wondering if > > anyone has tried and has had success with booting > > OpenBSD directly from USB. > > See "ibstall on Raspberry Pi" in the INSTALL.arm64 file. > > -- > Please keep replies on the mailing list. > >
Re: booting OpenBSD on Raspberry pi4 without using sdcard for UEFI
Hi David, Got it. Will try the install over serial line. One pleasant surprise I found is that once OpenBSD is installed using UEFI/sd, you don't need the sd card for reboots. The bootloader picks up the os from the usb directly. This is with the latest eeprom. Nice to have the sd not occupied :). Thanks Sandeep On Sat, May 21, 2022 at 12:31 AM David Demelier wrote: > > > On 20 May 2022, at 18:27, Sandeep Gupta wrote: > > > > Hello, > > > > This post here ( > > http://matecha.net/posts/openbsd-on-pi-4-with-full-disk-encryption/) > claims > > its possible to > > boot OpenBSD directly from USB without the need for UEFI on sdcard. > > I tried today but couldn't get it to work. I got a blank screen during > the > > installation process. What I did was > > 1) updated the eeprom (bootloader) > > 2) set boot to usb > > 3) wrote install71.img onto ssd. > > > > The boot process did start but I got a blank screen. I was wondering if > > anyone has tried and has had success with booting > > OpenBSD directly from USB. > > > > Thanks > > sandeep > > > > Hi, > > It’s possible to boot from USB only, it’s what I do with a special USB to > NVMe adapter in an argon case but in the process I do, you still need a SD > card and a TTL cable prior to boot only from USB. > > 1. Burn install71.img or miniroot71.img to the SD card > 2. Plug the appropriate TX/RX/GND pins on the board and open a serial line > (using cu/picocom) > 3. Insert the SD card and power on the Pi > 4. Install as usual to the correct USB disk > 5. Reboot. > > The install script uses labels in /etc/fstab which means it will just work > out of the box. > > Note: use an ethernet wire as well if you choose the miniroot, there are > no firmware for bwfm in 7.1 IIRC. > > Regarding your question, you get a blank screen because the installer in > ARM uses serial console by default. > > HTH > > -- > David > >
booting OpenBSD on Raspberry pi4 without using sdcard for UEFI
Hello, This post here ( http://matecha.net/posts/openbsd-on-pi-4-with-full-disk-encryption/) claims its possible to boot OpenBSD directly from USB without the need for UEFI on sdcard. I tried today but couldn't get it to work. I got a blank screen during the installation process. What I did was 1) updated the eeprom (bootloader) 2) set boot to usb 3) wrote install71.img onto ssd. The boot process did start but I got a blank screen. I was wondering if anyone has tried and has had success with booting OpenBSD directly from USB. Thanks sandeep
Re: nxserver on OpenBSD
I can imagine. Will give tigervnc a try. I have started towards compiling x2go for OpenBSD. Its running into trivial issues like compilation failures ( https://github.com/ArcticaProject/nx-libs/issues/1044). Will see how it goes. Thank you -S On Thu, Mar 24, 2022 at 2:49 PM Stuart Henderson wrote: > On 2022-03-24, Sandeep Gupta wrote: > > Hello, > > > > I am looking for an nxserver for openBSD. It seems all the well know > > solutions -- NoMachine, OpenNX, nxserver. The only one which is actively > > worked on is X2GO. Just wanted to confirm if OpenBSD has support for any > of > > the nxserver solutions or is there plan/intend to support one. > > Seems your best bet would be to run an NX server on Linux as a proxy as > suggested in > > > https://x2go-user.x2go.narkive.com/NUuuZlc7/compile-and-run-x2go-server-in-openindiana-freebsd > > If you can use a different protocol, tigervnc is in packages (and was an > absolute pain to get to build!). > > >
nxserver on OpenBSD
Hello, I am looking for an nxserver for openBSD. It seems all the well know solutions -- NoMachine, OpenNX, nxserver. The only one which is actively worked on is X2GO. Just wanted to confirm if OpenBSD has support for any of the nxserver solutions or is there plan/intend to support one. Thanks Sandeep
Re: how to recover a corrupted disk
much ado for nothing... It seems when I yanked the data cable, it wasn't the disk that got corrupted. It was the UEFI loader on sdcard that had become corrupted. Not sure when that had happened. This issue is documented here (https://github.com/pftf/RPi4/issues/97). I had ended up formatting the disk unnecessarily. Thanks a ton for pitching in suggestions. On Wed, Dec 1, 2021 at 7:30 PM Ian Darwin wrote: > > On Wed, Dec 01, 2021 at 01:39:39PM +0530, Sandeep Gupta wrote: > > Hello, > > All partitions except for /dev/rsd1c and /dev/rsd1i are clean. > > For /dev/rsd1c , I get "BAD SUPER BLOCK: MAGIC NUMBER WRONG". > > For /dev/rsd1i, I get "UNEXPECTED INCONSISTENCY". > > If that's the case, you are probably done! You could mount > your 'a' partition manually on /mnt, look in /mnt/etc/fstab, and > see which letter partitions belong where; use that info to make > sure you have "found" all your partitions. > > BTW, in addition to scan_ffs in base, there is testdisk in ports, > which I think does a better job ATM of finding FFS2 filesystems. > > As mentioned, DO NOT do anything with 'c' partition (be glad, > be very glad, that it didn't find anything resembling a superblock > when fsck'ing 'c'!). It's not a mountable partition but a 'wrapper' > for the whole disk.
Re: how to recover a corrupted disk
Not sure why not. It seems the rsd1c is where the superblock is. Also there is no other mechanism to refer to the whole disk. I guess it's time to format the disk. On Wed, Dec 1, 2021 at 4:20 PM Janne Johansson wrote: > > Den ons 1 dec. 2021 kl 11:09 skrev Sandeep Gupta : > > @Peter, @Janne: Thanks for the infos. Newfs seemed promising but it > > seems like the disk is beyond repair :(. > > I did newfs -N and got quite a few location of superblocks: > > Then I tried > > fsck_ffs -b #blockid /dev/rsd1c > > You should *NOT* newfs or fsck against the "C" partition. > > > -- > May the most significant bit of your life be positive.
Re: how to recover a corrupted disk
@Peter, @Janne: Thanks for the infos. Newfs seemed promising but it seems like the disk is beyond repair :(. I did newfs -N and got quite a few location of superblocks: Then I tried fsck_ffs -b #blockid /dev/rsd1c No matter which blockid i tried, it always gave the same BAD SUPER BLOCK: MAGIC NUMBER WRONG. I guess I would have to wipe it clean from here. On Wed, Dec 1, 2021 at 2:06 PM Janne Johansson wrote: > > Den ons 1 dec. 2021 kl 09:12 skrev Sandeep Gupta : > > I am running OpenBSD 7.0 on RPi4. I accidentally removed the usb > > cable connecting the sata ssd to the RPi4. > > Well OpenBSD froze and upon reboot I got the very comforting > > Synchronous Exception message. > > Thankfully, I have another RPi4 running OpenBSD. I can mount the > > corrupted disk ( did the necessary backups). I did fsck on all the > > partitions. > > All partitions except for /dev/rsd1c and /dev/rsd1i are clean. > > For /dev/rsd1c , I get "BAD SUPER BLOCK: MAGIC NUMBER WRONG". > > The "c" partition is not meant to hold filesystems, it is the device > used to talk to "the whole disk" for fdisk and such tools. > > > For /dev/rsd1i, I get "UNEXPECTED INCONSISTENCY". > > If you had any non-bsd filesystems (like a small MSDOS/FAT partition > for booting/firmware/arm blob stuff), it will end up as sdXi (and > j,k,l, and so on if you have more than one foreign fs), so if that is > the case, then it is not unexpected to see FFS' fsck have issues with > FAT filesystems. > > -- > May the most significant bit of your life be positive.
how to recover a corrupted disk
Hello, I am running OpenBSD 7.0 on RPi4. I accidentally removed the usb cable connecting the sata ssd to the RPi4. Well OpenBSD froze and upon reboot I got the very comforting Synchronous Exception message. Thankfully, I have another RPi4 running OpenBSD. I can mount the corrupted disk ( did the necessary backups). I did fsck on all the partitions. All partitions except for /dev/rsd1c and /dev/rsd1i are clean. For /dev/rsd1c , I get "BAD SUPER BLOCK: MAGIC NUMBER WRONG". For /dev/rsd1i, I get "UNEXPECTED INCONSISTENCY". I tried scan_ffs -l sd1 but it didn't report the full disklabel for sd1. What's the least disruptive way out of this quagmire? Or, things are beyond repair and should I wipe clean and start over? Thanks. Sandeep
Re: debugging 500 Internal error in httpd+gunicorn setup
Success..sort of.
Following path setup seems to work:
for httpd:
server "www.example.com" {
root "/htdocs/www.example.com/"
location "/app" {fastcgi socket
"/htdocs/www.example.com/run/gunicorn.sock"}
}
for uvicorn:
--bind=unix:/var/www/htdocs/www.example.com/run/gunicorn.sock. The
location path was not correct.
With this gunicorn seems to receives bits from httpd. Although it
doesn't like what it gets -- might be mismatch in protocol type
[2021-11-22 22:07:30 +0530] [1631] [WARNING] Invalid HTTP request received.
Traceback (most recent call last):
File
"/home/shared/Builds/Python-3.10.0/lib/python3.10/site-packages/uvicorn/protocols/http/h11_impl.py",
line 136, in handle_events
event = self.conn.next_event()
File
"/home/shared/Builds/Python-3.10.0/lib/python3.10/site-packages/h11/_connection.py",
line 443, in next_event
exc._reraise_as_remote_protocol_error()
File
"/home/shared/Builds/Python-3.10.0/lib/python3.10/site-packages/h11/_util.py",
line 76, in _reraise_as_remote_protocol_error
raise self
File
"/home/shared/Builds/Python-3.10.0/lib/python3.10/site-packages/h11/_connection.py",
line 425, in next_event
event = self._extract_next_receive_event()
File
"/home/shared/Builds/Python-3.10.0/lib/python3.10/site-packages/h11/_connection.py",
line 367, in _extract_next_receive_event
event = self._reader(self._receive_buffer)
File
"/home/shared/Builds/Python-3.10.0/lib/python3.10/site-packages/h11/_readers.py",
line 68, in maybe_read_from_IDLE_client
raise LocalProtocolError("illegal request line")
h11._util.RemoteProtocolError: illegal request line
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
-- VISUAL --
6 9,0-1 All
0 curl 1* etc/httpd.conf 2 /var/www/logs 3 curl 4
htdocs/example.com 5- gunicorn 6 rc.d 7 simpleapp 8 nginx
On Mon, Nov 22, 2021 at 6:59 PM Sandeep Gupta wrote:
>
> I can generate ktrace.out but I am not able to view the output.
> The command "kdump -f ktrace.out" does not yield any output.
>
> On Mon, Nov 22, 2021 at 5:33 PM Peter J. Philipp
> wrote:
> >
> > On Mon, Nov 22, 2021 at 05:18:42PM +0530, Sandeep Gupta wrote:
> > > Below is my simple httpd.conf entry:
> > >
> > > server "www.example.com" {
> > > listen on * port 80
> > > root "/htdocs/www.example.com/"
> > > location "/app" {fastcgi socket "/run/gunicorn.sock"}
> > > }
> > >
> > > In the background gunicorn server is running. When I access
> > > www.example.com/app, I get 500 Internal Server Error. There is nothing
> > > in the httpd error log (/var/www/logs/error.log). The gunicorn server
> > > doesn't report any incoming request.
> > > Hence, I thing request breaks down in the httpd part before
> > > forwarding to the request to gunicorn.
> > > How do I go about debugging httpd requests. I have put "-v -d" in the
> > > httpd_flags in /etc/rc.conf.local but doesnt produce any additional
> > > log messages.
> > >
> > >
> > > Thanks
> > > -S
> >
> > I keep on having the same problem. The way to debug the CGI is with
> > slowcgi.
> > I usually ktrace -p (pid of slowcgi) -i and watch the ktrace.out and then
> > turn off ktrac'ing with ktrace -C. Since the 500 Internal Server Error is
> > not really informative.
> >
> > Best Regards,
> > -peter
Re: debugging 500 Internal error in httpd+gunicorn setup
I can generate ktrace.out but I am not able to view the output.
The command "kdump -f ktrace.out" does not yield any output.
On Mon, Nov 22, 2021 at 5:33 PM Peter J. Philipp wrote:
>
> On Mon, Nov 22, 2021 at 05:18:42PM +0530, Sandeep Gupta wrote:
> > Below is my simple httpd.conf entry:
> >
> > server "www.example.com" {
> > listen on * port 80
> > root "/htdocs/www.example.com/"
> > location "/app" {fastcgi socket "/run/gunicorn.sock"}
> > }
> >
> > In the background gunicorn server is running. When I access
> > www.example.com/app, I get 500 Internal Server Error. There is nothing
> > in the httpd error log (/var/www/logs/error.log). The gunicorn server
> > doesn't report any incoming request.
> > Hence, I thing request breaks down in the httpd part before
> > forwarding to the request to gunicorn.
> > How do I go about debugging httpd requests. I have put "-v -d" in the
> > httpd_flags in /etc/rc.conf.local but doesnt produce any additional
> > log messages.
> >
> >
> > Thanks
> > -S
>
> I keep on having the same problem. The way to debug the CGI is with slowcgi.
> I usually ktrace -p (pid of slowcgi) -i and watch the ktrace.out and then
> turn off ktrac'ing with ktrace -C. Since the 500 Internal Server Error is
> not really informative.
>
> Best Regards,
> -peter
debugging 500 Internal error in httpd+gunicorn setup
Below is my simple httpd.conf entry:
server "www.example.com" {
listen on * port 80
root "/htdocs/www.example.com/"
location "/app" {fastcgi socket "/run/gunicorn.sock"}
}
In the background gunicorn server is running. When I access
www.example.com/app, I get 500 Internal Server Error. There is nothing
in the httpd error log (/var/www/logs/error.log). The gunicorn server
doesn't report any incoming request.
Hence, I thing request breaks down in the httpd part before
forwarding to the request to gunicorn.
How do I go about debugging httpd requests. I have put "-v -d" in the
httpd_flags in /etc/rc.conf.local but doesnt produce any additional
log messages.
Thanks
-S
Re: running a process under nologin user
That works. Thank you so much. On Mon, Nov 22, 2021 at 1:15 PM Janne Johansson wrote: > > Den mån 22 nov. 2021 kl 06:27 skrev Sandeep Gupta : > > The httpd server runs under user www. In my web deployment setup, the > > httpd server communicates over uWSGI/gunicorn server over unix domain > > sockets. > > I am not able to launch uwsgi (or gunicorn) server under www user. > > The command > > "doas -u www " gives error > > "operation not permitted". As root, trying to lauch a shell "su www > > -l /bin/bash" returns "The account is currently not available". > > Whats the recommended way to launch process under www? > > > machine# su -s /bin/sh www > machine$ id > uid=67(www) gid=67(www) groups=67(www) > machine$ > > -- > May the most significant bit of your life be positive.
running a process under nologin user
The httpd server runs under user www. In my web deployment setup, the httpd server communicates over uWSGI/gunicorn server over unix domain sockets. I am not able to launch uwsgi (or gunicorn) server under www user. The command "doas -u www " gives error "operation not permitted". As root, trying to lauch a shell "su www -l /bin/bash" returns "The account is currently not available". Whats the recommended way to launch process under www? Thanks. -S
Re: Raspberry Pi 4 Model B
My install setup uses both microSD and usb-attached SSD. The microSD has UEFI boot loader and SSD has the miniroot.img. Because there is two media, the installer which disks to install on. I am not sure how to complete installation using only usb-attached SSD -- how to write both UEFI and bsd installer on usb. Should be feasible. I was confused about the hostname -- if it is the location of the server or the url to be given to machine. Thats why different entries. I am not fiddling with setup anymore on now as well :). On Tuesday, October 5, 2021, Peter J. Philipp wrote: > [inline below] > On Mon, Oct 04, 2021 at 11:40:30PM +0530, Sandeep Gupta wrote: > > Some progress. Thank you. Still stuck though. Post network > > configuration, The boot installer asks for > > HTTP Server? (hostname or 'done'). hostname. > > Server Directory? [pub/OpenBSD/7.0/arm64]. > > > > It fails at this step: > > > > Unable to connect using https. Use http instead. > > Looked at found no OpenBSD/arm64 7.0 sets. > > This may be connectivity related I dunno. Is it true that you put the > installer on the micro SD card and then installed on top of that same > image? At which point your installer needs flashing after every powercycle > when it fails to install. > > When I installed I installed right on a USB disk and that's what I want to > recommend to you too. Either put the install media on a USB stick or on > the sd card and install to USB stick. With newer eeprom raspberry pi 4's > can boot directly off USB. > > Then you'd have the install sets on disk media (may have to be mounted > first > but the installer will guide you through that, it asks if disk media is > already > mounted and if not asks you which disk it's on). > > Anyhow this is the safer alternative than downloading via http as I don't > know if the snapshot installer can signify off any install media. > > I'm glad you're making so much progress. It took me two days as well to > get it to install the way I wanted, and now I'm reluctant to upgrade my > snapshot from jul 21st because people are getting snagged on the installer > a lot. I'm likely going to wait until release 7.0 to upgrade it's only > about > a month away, since the rpi4 is my workstation for everyday use. > > Anyways, good luck! > > > > I tried with pub/OpenBSD/snapshots/arm64. That didn't work either. > > hmmm. Oh wait, are you entering "hostname" as in the example above? I > kinda > missed that. Try "cdn.openbsd.org" instead. How did I not see this? > > [rest cut] > > Best Regards, > -peter >
Re: Raspberry Pi 4 Model B
Some progress. Thank you. Still stuck though. Post network configuration, The boot installer asks for HTTP Server? (hostname or 'done'). hostname. Server Directory? [pub/OpenBSD/7.0/arm64]. It fails at this step: Unable to connect using https. Use http instead. Looked at found no OpenBSD/arm64 7.0 sets. I tried with pub/OpenBSD/snapshots/arm64. That didn't work either. On Thu, Sep 30, 2021 at 11:48 AM Stuart Henderson wrote: > > Change the server directory to /pub/OpenBSD/snapshots/arm64. We're in the > awkward time where the version number is just 7.0 so the installer thinks it > is a released version, but the release hasn't been made yet, and there is no > mechanism for the installer to fetch that information online, so you have to > do it manually. > > -- > Sent from a phone, apologies for poor formatting. > > > On 30 September 2021 03:18:36 Sandeep Gupta wrote: >> >> This is my second attempt to install openBSD on RPI4. I write out the UEFI >> to sdcard and miniroot.img to usb-ssd drive which takes some 16MB of space. >> The rest I create a new fat32 partition. This works -- the boot loader kicks >> off the openBSD installer. >> The installer after asking for disk partitions, reaches till installing >> sets.However, >> it doesn't give me option to install bsd or bsd.rd (see attached pic below). >> >> Not sure if I am messing up the disk partition where openbsd should be >> installed. I tried both sd1 and sd1a. But both end up having the same issue. >> >> -S >> >> On Wednesday, September 29, 2021, Stuart Henderson >> wrote: >> > >> > On 2021-09-28, Peter J. Philipp wrote: >> > > On Tue, Sep 28, 2021 at 10:04:25AM -0700, Joseph Olatt wrote: >> > >> I tried the following snapshot: >> > >> >> > >> https://cdn.openbsd.org/pub/OpenBSD/snapshots/arm64/miniroot70.img >> > >> >> > >> Build date: 27-Sep-2021 20:10 >> > >> Size: 45088768 >> > >> >> > >> Didn't have much luck. The install process rebooted after the following >> > >> error: >> > >> >> > >> bwfm0: failed loadfirmware of file >> > >> brcmfmac43455-sdio.raspberrypi,4-model-b.bin >> > >> panic: do_el0_error >> > > >> > > What happens when you boot with -c and 'disable bwfm' then exit? Is >> > > that not >> > > an option anymore? >> > >> > I am pretty sure the do_el0_error is unrelated to the loadfirmware() >> > failing >> > (which is just because the firmware for the device isn't installed yet). >> > >> > > >
installing openbsd on raspberry pi 4
Hello, I am stuck on installing openbsd 6.8 (or 6.9) on rpi 4. I am able to boot the openbsd installer off of USB drive using UEFI boot loader (on sd card). However the installer fails at the step "What timezone are you in?". It doesn't like any timezone I input. Just before this step I get the error "cd: /mnt/user/share/zoneinfo -- No such file or directory". I am not able to tell installer to skip this step. Another issue I am facing is that installer giving warning: "Are you *SURE* your install is complete without bsd" and other similar warnings. where should I place bsd, bsd.mp, and other files for installer to pick those up. On the usb drive I have only written miniroot68.img. This creates two partitions. None of these partitions seems like there correct place for bsd and other distribution sets files. Any pointers/help would be great. Thanks -S
