Re: CARP Cold Spare
> On Sep 24, 2021, at 6:16 PM, Don Tek wrote: > > Would there be any ‘problem’ with configuring a 2-machine CARP setup and > then just keeping one machine powered-off until needed? > > I realize this defeats live failover, but this is not a requirement for my > customer. > > I just want them to be able to, in the event of a primary machine failure, > power-on the secondary and have it take over. Logic here is to otherwise not > have the secondary sucking power off the UPS’s in the event of a power > failure, or in general. > > Legit? > Sounds legit to me. Let’s you share the IP safely and easily, up or down.
Re: nextcloudclient fails to work with gnome-keyring
I have reproduced the issue in Fluxbox. ~.xession: /usr/local/bin/startfluxbox ~.fluxbox/startup if [ -z "$DBUS_SESSION_BUS_ADDRESS" ]; then eval $(dbus-launch --sh-syntax --exit-with-session) fi exec fluxbox Under a similar configuration in Linux, Nextcloud calls a prompt for creating a password database on first launch, and stores the credentials in a keyring. In OpenBSD this happens not. Some worrying logs from Nextcloud: 2021-09-25 00:52:25:016 [ info nextcloud.sync.credentials.webflow ]:Get QNAM 2021-09-25 00:52:25:667 [ info nextcloud.sync.credentials.webflow ]:Fetch from keychain! 2021-09-25 00:52:25:985 [ info nextcloud.sync.credentials.keychainchunk ]: Backend unavailable (yet?) Retrying in a few seconds. "Unknown error" 2021-09-25 00:52:36:312 [ warning nextcloud.sync.credentials.keychainchunk ]: Unable to read "someuser_clientCertificatePEM:https://somedomain.invalid/:0; chunk "0" "Unknown error" 2021-09-25 00:52:36:313 [ info nextcloud.sync.credentials.keychainchunk ]: Backend unavailable (yet?) Retrying in a few seconds. "Unknown error" 2021-09-25 00:52:46:491 [ warning nextcloud.sync.credentials.keychainchunk ]: Unable to read "someuser_clientKeyPEM:https://somedomain.invalid/:0; chunk "0" "Unknown error" 2021-09-25 00:52:46:491 [ warning nextcloud.sync.credentials.webflow ]: Unable to read client key "Unknown error" 2021-09-25 00:52:46:492 [ info nextcloud.sync.credentials.keychainchunk ]: Backend unavailable (yet?) Retrying in a few seconds. "Unknown error" 2021-09-25 00:52:56:186 [ warning nextcloud.sync.credentials.keychainchunk ]: Unable to read "someuser_clientCaCertificatePEM0:https://somedomain.invalid/:0; chunk "0" "Unknown error" "Unknown Error" is returned by qtkeychain when unable to operate its backend. Either there is a problem with libsecret or the PEBKAC level is astronomical at this point. Rubén Llorente wrote: > Hello there! > > I have been testing some machine for deployment as a workstation. I have set > up XFCE4 as a desktop environment (which is launched by my .xsession file). I > have also set nextcloudclient and installed gnome-keyring-daemon. > > I have found that Nextcloud Client is unable to leverage gnome-keyring in > order to save credentials securely. Nextcloud Client always complains because > the secrets agent cannot be used because of an "Unknown Error". > > Things I have tried in order to properly launch gnome-keyring-daemon include: > > Using an .xsession script such as: > > > . $HOME/.profile > eval $(/usr/local/bin/gnome-keyring-daemon --start ) > export GNOME_KEYRING_CONTROL GNOME_KEYRING_PID GPG_AGENT_INFO SSH_AUTH_SOCK > /usr/local/bin/startxfce4 > > Also, I have tried using the XFCE4 desktop configuration tool, enabling Gnome > Services on startup in the Advanced tab. > > Essentially, I can get the keyring started, but nextcloud, or qtkeychain, or > whatever backend is suppose to talk to gnome-keyring fails to find it. > > As a workarround I am using Kwalletd5 for the time being, which works. > > If anybody has any guide or instructions to set up gnome-keyring with > nextcloudclient, or ideas to get such setup working, I am eager to read your > ideas. > > The working environment is OpenBSD 6.9 -RELEASE amd64. > -- OpenPGP Key Fingerprint: 543F EB89 7FDE 8E33 AFF7 E794 E4AB 4807 58F7 6C76
Re: Raspberry Pi 4 Model B
I'm trying to load OpenBSD on a Raspberry Pi 4 Model B and I'm not having much luck. I've tried OpenBSD 6.9's miniroot69.img and the install process does not go past the U-Boot prompt. I was able to install OpenBSD 6.9 on that hardware. What issue did you encounter?
Raspberry Pi 4 Model B
Hi, I'm trying to load OpenBSD on a Raspberry Pi 4 Model B and I'm not having much luck. I've tried OpenBSD 6.9's miniroot69.img and the install process does not go past the U-Boot prompt. I tried miniroot70.img from the snapshots directory, as of today, and after displaying the following line: bwfm0: failed loadfirmware of file brcmfmac43455-sdio.raspberrypi,4-model-b.bin it reboots. Anybody else have success installing OpenBSD on this particular hardware? Any insights or suggestions? Thank you. joseph
CARP Cold Spare
Would there be any ‘problem’ with configuring a 2-machine CARP setup and then just keeping one machine powered-off until needed? I realize this defeats live failover, but this is not a requirement for my customer. I just want them to be able to, in the event of a primary machine failure, power-on the secondary and have it take over. Logic here is to otherwise not have the secondary sucking power off the UPS’s in the event of a power failure, or in general. Legit?
Re: Raspberry Pi 4 Model B
Have you read the Raspberry Pi instructions from https://ftp.openbsd.org/pub/OpenBSD/6.9/arm64/INSTALL.arm64 ? What does your UART output show after it boots? Andrew On Fri, Sep 24, 2021 at 2:45 PM Joseph Olatt wrote: > Hi, > > I'm trying to load OpenBSD on a Raspberry Pi 4 Model B and I'm not > having much luck. I've tried OpenBSD 6.9's miniroot69.img and the > install process does not go past the U-Boot prompt. > > I tried miniroot70.img from the snapshots directory, as of today, and > after displaying the following line: > > bwfm0: failed loadfirmware of file > brcmfmac43455-sdio.raspberrypi,4-model-b.bin > > it reboots. > > Anybody else have success installing OpenBSD on this particular > hardware? Any insights or suggestions? > > Thank you. > joseph > >
Re: sysctl hw.sensors.lm1 shows only one fan
Stuart Henderson wrote: > On 2021-09-24, Maksim Rodin wrote: > > My system has several fans connected to the MB (Supermicro X8SIL-F) > > "sysctl hw.sensors.lm1" shows only fan0. > > Is there a way to make my system (OpenBSD 6.9 stable) show more fans in > > that output? > > > > Try "boot -c" and "enable ipmi" "quit". > > Apparently some machines had a problem with this (IIRC there was some > IBM server with a problem) but most systems don't have a problem, and > some systems (including most Supermicro) do attach sensors there. I still get ipmi0: sendcmd failed On various other machines, when ipmi is enabled. Not right away, but eventually. The problem isn't that there are machines with busted IPMI, it is that our ipmi code is incredibly optimistic and doesn't know how to cope with failure. And as a result, the ipmi code will remain disabled until someone steps up and makes the code better. Having a few more sensors does not justify the potential problems.
Re: sysctl hw.sensors.lm1 shows only one fan
On 2021-09-24, Maksim Rodin wrote: > My system has several fans connected to the MB (Supermicro X8SIL-F) > "sysctl hw.sensors.lm1" shows only fan0. > Is there a way to make my system (OpenBSD 6.9 stable) show more fans in > that output? > Try "boot -c" and "enable ipmi" "quit". Apparently some machines had a problem with this (IIRC there was some IBM server with a problem) but most systems don't have a problem, and some systems (including most Supermicro) do attach sensors there. -- Please keep replies on the mailing list.
Re: sysctl hw.sensors.lm1 shows only one fan
Maksim Rodin wrote: > My system has several fans connected to the MB (Supermicro X8SIL-F) > "sysctl hw.sensors.lm1" shows only fan0. > Is there a way to make my system (OpenBSD 6.9 stable) show more fans in > that output? No. Other fans-speed sensors are probably connected in weird places, and there is effectively no industry standardization, our code only finds the simplest sensors and beyond that no developer has gone.
sysctl hw.sensors.lm1 shows only one fan
My system has several fans connected to the MB (Supermicro X8SIL-F) "sysctl hw.sensors.lm1" shows only fan0. Is there a way to make my system (OpenBSD 6.9 stable) show more fans in that output? -- Regards Maksim
