ovecot using Xapian
dovecot-ldap-2.3.21v0 LDAP authentication / dictionary support for Dovecot
dovecot-pigeonhole-0.5.21v1 Sieve mail filtering for Dovecot
Last configuration changes in dovecot were made long before upgrade and
I did not have problems with that configuration on 7.4
--
Best r
www.eskimo.com/~joji/cdce/obsd75
I'm reaching out to see if there are others using the cdce interface
that are seeing issues with the cdce interface after upgrade.
Thank you.
joseph
On 2024-04-17, Federico Giannici wrote:
> On 4/17/24 16:34, Stuart Henderson wrote:
>> On 2024-04-17, Kapetanakis Giannis wrote:
>>> One idea if you have old devices that cannot upgrade to a newer SSL/TLS
>>> protocol would be to run some kind of proxy between the
On 4/17/24 16:34, Stuart Henderson wrote:
On 2024-04-17, Kapetanakis Giannis wrote:
One idea if you have old devices that cannot upgrade to a newer SSL/TLS
protocol would be to run some kind of proxy between the client and the radius
server (stunnel?)
Don't know how well this plays with EAP
On 17/04/2024 17:37, Federico Giannici wrote:
> On 4/17/24 15:19, Stuart Henderson wrote:
>> This is most likely because of:
>>
>> https://www.openbsd.org/74.html
>> "Disabled TLSv1.0 and TLSv1.1 in libssl so that they may no longer be
>> selected for use."
>>
>> I don't think there's anything
On 4/17/24 15:19, Stuart Henderson wrote:
On 2024-04-17, Federico Giannici wrote:
Since we upgraded from OpenBSD amd64 7.3 to 7.5 (passing through 7.4)
the FreeRadius EAP authentication no longer works!
We are using a custom version of FreeRadius (because we had to do some
little changes and
On 2024-04-17, Kapetanakis Giannis wrote:
> One idea if you have old devices that cannot upgrade to a newer SSL/TLS
> protocol would be to run some kind of proxy between the client and the radius
> server (stunnel?)
>
> Don't know how well this plays with EAP.
> Maybe t
t
>> accepted in previous release?
> This is most likely because of:
>
> https://www.openbsd.org/74.html
> "Disabled TLSv1.0 and TLSv1.1 in libssl so that they may no longer be
> selected for use."
>
> I don't think there's anything simple you can do to reena
On 2024-04-17, Federico Giannici wrote:
> Since we upgraded from OpenBSD amd64 7.3 to 7.5 (passing through 7.4)
> the FreeRadius EAP authentication no longer works!
>
> We are using a custom version of FreeRadius (because we had to do some
> little changes and a module of our own), and
Since we upgraded from OpenBSD amd64 7.3 to 7.5 (passing through 7.4)
the FreeRadius EAP authentication no longer works!
We are using a custom version of FreeRadius (because we had to do some
little changes and a module of our own), and everything worked correctly
for many years.
Now, with
I had a similar experience on a VP2410, but solved it in a different way. I did
not connect a display and keyboard.
I attempted a remote 7.4 -> 7.5 sysupgrade a few days ago on a Protectli
VP2410; mine also came back after the upgrade reboot as 7.4.
So today I dispatched to the client s
I remotely upgraded the protectli vp2420 firewall appliance from 7.4
to 7.5 (amd64), and the upgrades went smoothly. However, the reboot
showed 7.4. Had bsd.upgrade, etc. created.
I then attached a monitor and keyboard to this appliance and ran
sysupgrade again, this time around the upgrade went
Thanks for your answers. I will prepare the reinstall based on your
suggestions.
Cheers
Ben
If you are by usb sticks you can find maybe useful one of old thread:
https://marc.info/?l=openbsd-misc=169896854913334=2
Please remember to update /etc/fstab accordingly to the new layout of the final
system
before to reboot.
-Dan
Apr 9, 2024 18:37:39 Stuart Henderson :
> Some options:
>
On 2024-04-09, Ben Jahmine wrote:
> Dear all.
>
> I just did my unattended upgrade to 7.5. I previously checked the
> available disk space in /usr, as suggested by the upgrade guide. My /usr
> size is 2 GB, as created by the installer. As this is above 1.1 GB I
> started the
Check if you have /usr/ports or /usr/src.
Le 9 avril 2024 15:16:17 GMT+02:00, Ben Jahmine a écrit :
>Dear all.
>
>I just did my unattended upgrade to 7.5. I previously checked the
>available disk space in /usr, as suggested by the upgrade guide. My /usr
>size is 2 GB, as created b
Dear all.
I just did my unattended upgrade to 7.5. I previously checked the
available disk space in /usr, as suggested by the upgrade guide. My /usr
size is 2 GB, as created by the installer. As this is above 1.1 GB I
started the unattended upgrade using sysupgrade.
The upgrade failed during
On Mon, Apr 8, 2024 at 2:38 PM Stuart Henderson
wrote:
>
> On 2024-04-08, Ioan Samarul wrote:
> > Hello to you all!
> >
> > I upgraded without problem to 7.5, everything went smooth as always,
> > except when I tried to upgrade the packages.
> >
> >
On 2024-04-08, Ioan Samarul wrote:
> Hello to you all!
>
> I upgraded without problem to 7.5, everything went smooth as always,
> except when I tried to upgrade the packages.
>
> This are the errors of `doas pkg_add -uV` (there is no version of
> firefox installed, if that
Hello to you all!
I upgraded without problem to 7.5, everything went smooth as always,
except when I tried to upgrade the packages.
This are the errors of `doas pkg_add -uV` (there is no version of
firefox installed, if that helps)
No pkgname in packing-list for .libs1-firefox-esr-91.13.0
Could someone kindly fix the wording on the 7.5 upgrade page.
It says "There were several configuration changes and changes in packages that
may require planning before starting the upgrade."
But the notes say "nothing of note this release", "nothing to remove this
release",
Thanks!
On 4/3/24 18:19, Karel Lucas wrote:
I want to use ETH1 for the input from my
ADSL modem, ETH2 and ETH3 for the output to my network. Furthermore, I
would like to use ETH4 for the update/upgrade of the firewall. Remove
the connection from ETH1, plug it into ETH4, and update/upgrade
for the output to my network. Furthermore, I
would like to use ETH4 for the update/upgrade of the firewall. Remove
the connection from ETH1, plug it into ETH4, and update/upgrade. Then
the connection returns to ETH1. ETH4 therefore receives an IP address
and ETH1,ETH2 and ETH3 not. But now the problem: as long
ut from my ADSL
> modem, ETH2 and ETH3 for the output to my network. Furthermore, I would like
> to use ETH4 for the update/upgrade of the firewall. Remove the connection
> from ETH1, plug it into ETH4, and update/upgrade. Then the connection
> returns to ETH1. ETH4 therefore receives
would like to use ETH4 for the update/upgrade of the firewall. Remove
the connection from ETH1, plug it into ETH4, and update/upgrade. Then
the connection returns to ETH1. ETH4 therefore receives an IP address
and ETH1,ETH2 and ETH3 not. But now the problem: as long as the network
connection
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
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".
>
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
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,
Stuart Henderson :
>
> Running out of space (especially in /usr) during sysupgrade might
> do it too.
When in single mode I reccomend to check also the root for /dev
content, 90% of times I run out of space happens there to me, anyway
I'm not sure about the connection with xterm and
On 2024-04-01, Peter N. M. Hansteen wrote:
>
> 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).
Running out of space (especially in /usr) during sysupgrade
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
If you have Xenocara installed, then I assume you can use xedit to modify files
on the system. I don't know twm, but it is probably possible to create a new
entry in its menu, through which you could run "xterm -e /bin/sh" to override
the default shell.
If this is not possible using twm, then
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
2024-04-01T19:17:31Z Sandeep Gupta :
> 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.
>
>
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
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
Dave Voutila writes:
> "Piotr K. Isajew" writes:
>
>> Hello,
>>
>> I'm observing this on one of my machines (which I seldom use
>> nowadays) after upgrading it to 7.4. The machine had existing
>> vm.conf setup which worked for me in the past.
>>
>> Now "rcctl start vmd" reports:
>> vmd(ok)
>>
"Piotr K. Isajew" writes:
> Hello,
>
> I'm observing this on one of my machines (which I seldom use
> nowadays) after upgrading it to 7.4. The machine had existing
> vm.conf setup which worked for me in the past.
>
> Now "rcctl start vmd" reports:
> vmd(ok)
>
> but just after that executing
On Fri, Feb 02, 2024 at 08:28:42AM +0100, Piotr K. Isajew wrote:
> Hello,
>
> I'm observing this on one of my machines (which I seldom use
> nowadays) after upgrading it to 7.4. The machine had existing
> vm.conf setup which worked for me in the past.
>
> Now "rcctl start vmd" reports:
> vmd(ok)
>
Ali Farzanrad wrote:
> Hi Stuard,
>
> Stuart Henderson wrote:
> > On 2023-11-17, Sonic wrote:
> > > Following -current:
> > > OpenBSD 7.4-current (GENERIC.MP) #1447: Wed Nov 15 09:56:54 MST 2023
> > > Upgrade via "sysupgrade -s" now fa
On Fri, Nov 17, 2023 at 2:43 PM Stuart Henderson wrote:
>
> Try booting bsd.rd and downloading a newer snap.
The latest bsd.rd is identical to the bsd.upgrade file.
The older bsd,rd from yesterday boots fine as the system does recover
from the failed upgrade if one has physical
Hi Stuard,
Stuart Henderson wrote:
> On 2023-11-17, Sonic wrote:
> > Following -current:
> > OpenBSD 7.4-current (GENERIC.MP) #1447: Wed Nov 15 09:56:54 MST 2023
> > Upgrade via "sysupgrade -s" now failing with:
> > init: single user shell terminated, r
Try booting bsd.rd and downloading a newer snap.
--
Sent from a phone, apologies for poor formatting.
On 17 November 2023 19:25:03 Sonic wrote:
On Fri, Nov 17, 2023 at 2:06 PM Stuart Henderson
wrote:
Bit old by now, boot bsd.rd and try a newer one?
If that fails too: which arch?
I'm
On Fri, Nov 17, 2023 at 2:06 PM Stuart Henderson
wrote:
>
> Bit old by now, boot bsd.rd and try a newer one?
>
> If that fails too: which arch?
I'm currently on #1447, amd64, from which I was running "sysupgrade -s".
Apparently boots from bsd.upgrade during the process.
On 17.11.2023. 20:05, Stuart Henderson wrote:
> On 2023-11-17, Sonic wrote:
>> Following -current:
>> OpenBSD 7.4-current (GENERIC.MP) #1447: Wed Nov 15 09:56:54 MST 2023
>> Upgrade via "sysupgrade -s" now failing with:
>> init: single user shell terminated,
On 2023-11-17, Sonic wrote:
> Following -current:
> OpenBSD 7.4-current (GENERIC.MP) #1447: Wed Nov 15 09:56:54 MST 2023
> Upgrade via "sysupgrade -s" now failing with:
> init: single user shell terminated, restarting
> init: single user shell terminated, restarting
Following -current:
OpenBSD 7.4-current (GENERIC.MP) #1447: Wed Nov 15 09:56:54 MST 2023
Upgrade via "sysupgrade -s" now failing with:
init: single user shell terminated, restarting
init: single user shell terminated, restarting
init: single user shell terminated, restarting
Chris
I have a virtual machine in UTM (which is a MacOS app that provides a
GUI to manage QEMU virtual machines) on my M1 Mac. This VM was running
7.3 and X11 was working fine with the "virtio-ramfb" video card, but
after using `sysupgrade` to upgrade to 7.4, it stopped working
(`startx`
On 2023-11-07, Laurent CARON wrote:
> Hi,
>
> After upgrading a 7.3 to 7.4 OpenBSD box, I noticed OSPF adjacencies
> using a password are not coming up with the following in /var/log/messages:
>
> ospfd[55040]: recv_packet: authentication error, neighbor ID X.X.X.X
> interface vlanXX
>
> After
Le 07/11/2023 à 10:59, Claudio Jeker a écrit :
Ugh. My bad. I forgot that iface->auth_key is not really a string. So the
code setting the auth_key would copy too much if you use a password with 8
chars. Using a password with 7 or less chars works fine.
As a result of this overflow the
On Tue, Nov 07, 2023 at 10:59:48AM +0100, Claudio Jeker wrote:
> On Tue, Nov 07, 2023 at 08:21:16AM +0100, Laurent CARON wrote:
> > Hi,
> >
> > After upgrading a 7.3 to 7.4 OpenBSD box, I noticed OSPF adjacencies using a
> > password are not coming up with the following in /var/log/messages:
> >
On Tue, Nov 07, 2023 at 08:21:16AM +0100, Laurent CARON wrote:
> Hi,
>
> After upgrading a 7.3 to 7.4 OpenBSD box, I noticed OSPF adjacencies using a
> password are not coming up with the following in /var/log/messages:
>
> ospfd[55040]: recv_packet: authentication error, neighbor ID X.X.X.X
>
Hi,
After upgrading a 7.3 to 7.4 OpenBSD box, I noticed OSPF adjacencies
using a password are not coming up with the following in /var/log/messages:
ospfd[55040]: recv_packet: authentication error, neighbor ID X.X.X.X
interface vlanXX
After removing the authentication, I was able to get
On 23 Oct 2023 09:32:19 -0600
"Andy Bradford"
wrote:
> Thus said Roger Marsh on Thu, 19 Oct 2023 17:23:47 -:
>
> > fixes the delay problem, but was the delay a predictable consequence
> > of some change? Or perhaps the entry should never have been expressed
> > in the way that led to
Thus said Roger Marsh on Thu, 19 Oct 2023 17:23:47 -:
> fixes the delay problem, but was the delay a predictable consequence
> of some change? Or perhaps the entry should never have been expressed
> in the way that led to the delay?
Most likely the cause is an unexpected side effect of
ing the Xclient role disks to the older hardware on which they now
sit proved simpler and effective but not perfect.
>
>
Roger
> On Sun, Oct 22, 2023 at 7:22 AM Roger Marsh wrote:
>
> > On Thu, 19 Oct 2023 17:23:47 +
> > Roger Marsh wrote:
> >
>
s probably a distraction from the "why did
the latency change" question.
On Sun, Oct 22, 2023 at 7:22 AM Roger Marsh wrote:
> On Thu, 19 Oct 2023 17:23:47 +
> Roger Marsh wrote:
>
> > Hi,
> >
> > After upgrade from 7.3 to 7.4 (on both boxes) the xterm
Let me joke that we clealry hope in 7.5 to slow down things further.
-- Daniele Bonini
On Thu, 19 Oct 2023 17:23:47 +
Roger Marsh wrote:
> Hi,
>
> After upgrade from 7.3 to 7.4 (on both boxes) the xterm session for this
> entry in .fvwmrc (on monitor):
>
> 'Exec exec ssh -Y opendev xterm -title roger@opendev'
>
> takes several seconds to deliver t
On 10/20/23 19:31, Federico Giannici wrote:
I just upgraded my OpenBSD 7.3 amd64 to 7.4. I used the usual procedure,
the one in the upgrade FAQ. After the upgrade kate (KDE texteditor) no
longer works!
If I execute "kate -v" here it is the output:
kate:/usr/X11R6/lib/libX11.so.
I just upgraded my OpenBSD 7.3 amd64 to 7.4. I used the usual procedure,
the one in the upgrade FAQ. After the upgrade kate (KDE texteditor) no
longer works!
If I execute "kate -v" here it is the output:
kate:/usr/X11R6/lib/libX11.so.17.1: /usr/X11R6/lib/libX11.so.18.0 :
WARNI
Hi,
After upgrade from 7.3 to 7.4 (on both boxes) the xterm session for this entry
in .fvwmrc (on monitor):
'Exec exec ssh -Y opendev xterm -title roger@opendev'
takes several seconds to deliver the xterm window, while I did not notice any
delay before upgrade.
For other usernames on opendev
On 2023-09-25, Tobias Fiebig wrote:
> On Mon, 2023-09-25 at 18:15 +0200, Rudolf Leitgeb wrote:
>> Either this, or the TLS 1.3 code was always buggy, but now
>> it was actually used per default.
> Yes, setting up nginx with enabled tlsv1.3 on 7.2 and earlier is also
> on the todo. Similarly,
On Mon, 2023-09-25 at 18:15 +0200, Rudolf Leitgeb wrote:
> Either this, or the TLS 1.3 code was always buggy, but now
> it was actually used per default.
Yes, setting up nginx with enabled tlsv1.3 on 7.2 and earlier is also
on the todo. Similarly, disabling tlsv1.3 and forcing tlsv1.3 on
earlier
Either this, or the TLS 1.3 code was always buggy, but now
it was actually used per default. Question: is there a similar
commit in your DNS server? Do you use this DNS server with
anything like TLS?
On Sun, 2023-09-24 at 21:31 +0200, Tobias Fiebig wrote:
>
> > But yes, getting a specific
> But yes, getting a specific commit there will be helpful.
Sadly it turns out that it is the commit i feared it would be:
> commit 7b24b93d67daa9c16d665129fd5d3e7dbc583e4f
> Author: Maxim Dounin
> Date: Fri Mar 24 02:57:43 2023 +0300
>
> SSL: enabled TLSv1.3 by default.
Feared,
> shows a similar memory leakage for mysql/mariadb (runs powerdns with a
> mysql backend, both from packages) since the upgrade to 7.3 in May as
> well. One further host seems to show a significantly higher use of
> inactive memory since 7.3. I found one more host with mariadb th
On Sun, 2023-09-24 at 13:07 +0200, Rudolf Leitgeb wrote:
> This libpcre2 library seems to be the only one, which is not
> used all over the place. The library itself may not even be buggy, it
> may just return something, which the new versions of the caller can't
> handle, or it may be unhappy
ently, I am going
> > > through
> > > all commits to see with which version it first appears.
> > >
> > > However, clicking around this morning, i noticed that my primary
> > > NS
> > > shows a similar memory leakage for mysql/mariadb (runs p
Currently, I am going
> > through
> > all commits to see with which version it first appears.
> >
> > However, clicking around this morning, i noticed that my primary NS
> > shows a similar memory leakage for mysql/mariadb (runs powerdns
> > with
> > a
> > m
ing, i noticed that my primary NS
> shows a similar memory leakage for mysql/mariadb (runs powerdns with
> a
> mysql backend, both from packages) since the upgrade to 7.3 in May as
> well. One further host seems to show a significantly higher use of
> inactive memory since 7.3.
to see with which version it first appears.
However, clicking around this morning, i noticed that my primary NS
shows a similar memory leakage for mysql/mariadb (runs powerdns with a
mysql backend, both from packages) since the upgrade to 7.3 in May as
well. One further host seems to show
Endeover:
In 7.3, I end up starting also unbound service by rcctl instead of
unbound-control (losing maybe something about security) hoping to give me a
better
general standard to control my services, including my approach
to sysupgrade.
Thanks to everyone who reply in the thread.
--
Thanks Steve.
Jul 30, 2023 00:07:35 Steve Litt :
> I use runit (on Void Linux) every day, and love it to death. Runit is
> extremely simple. S6 is a little more capable and a little more complex.
Thank you for all the hints, expecially about runit, I didn't know it.
I'm going trying to fix
Daniele B. said on Tue, 25 Jul 2023 16:33:50 +0200 (GMT+02:00)
>My unattended upgrade happend like that:
>
>- I took up unbound
>- sysupgrade
>- 1st fw_update (this probbly is okay)
>- reboot
>- installation of the sets
>- 2nd fw_update (this fails because unattende
On Jul 28, 2023 20:00:24 I was still sleeping when suddenly Paul said:
> If you really want to go without DNS resolution, I invite you to
> travel back a few decades and learn about /etc/hosts.
did you hear my
"True, the hosts.. Oh Jesus!"... ?
Many thx! :D
-- Daniele Bonini
in such a way to need this kind of tomfoolery.
On Tue, Jul 25, 2023 at 09:58:35AM +0200, Daniele B. wrote:
|
| Hello,
|
| Just coming from my fresh upgrade to OpenBSD 7.3 and thanks again for
| it.. ;)
|
| No particular problem except my realization that with my settings
| (unbound started manually
My unattended upgrade happend like that:
- I took up unbound
- sysupgrade
- 1st fw_update (this probbly is okay)
- reboot
- installation of the sets
- 2nd fw_update (this fails because unattended, local Unbound is down)
- reboot
- 3rd fw_update (this fails because unattended, local Unbound
Thanks Steve,
Jul 25, 2023 14:41:53 Steve Litt :
> chattr -i resolv.conf && echo nameserver 8.8.8.8 >> resolv.conf && chattr +i
> resolv.conf
>
> I also don't understand why you start unbound manually instead of from
> computer initialization. It sounds like if unbound started before
>
Daniele B. said on Tue, 25 Jul 2023 11:29:09 +0200 (GMT+02:00)
>Hello Stuart, thanks for this one..
>
>Yes, I agree that the final solution could be only the replace my
>listed nameserver. But do you remember I was using also the unmutable
>flag on resolv.conf ? :D
chattr -i resolv.conf &&
* but having a free to use failover network setting
for the specific case of the unattended installation sounds enough
attractive, isn it?
Jul 25, 2023 11:00:27 Stuart Henderson :
> On 2023-07-25, Daniele B. wrote:
>>
>> Hello,
>>
>> Just coming from my fresh upgrade to O
On 2023-07-25, Daniele B. wrote:
>
> Hello,
>
> Just coming from my fresh upgrade to OpenBSD 7.3 and thanks again for
> it.. ;)
>
> No particular problem except my realization that with my settings
> (unbound started manually) fw_update goes to fail (all the three
> at
Hello,
Just coming from my fresh upgrade to OpenBSD 7.3 and thanks again for
it.. ;)
No particular problem except my realization that with my settings
(unbound started manually) fw_update goes to fail (all the three
attempts) on each (unattended) upgrade. If fw_update happens
On 6/1/23 13:16, Samuel Jayden wrote:
Hi Boyd,
I noted the uptime values when I received notifications like "Internet is
slow", "Intranet is too slow" from users. In all of them, the load average
was 5 and above.
This is what I mean with the firewall just slowed down.
Also there were more
Hi Boyd,
I noted the uptime values when I received notifications like "Internet is
slow", "Intranet is too slow" from users. In all of them, the load average
was 5 and above.
This is what I mean with the firewall just slowed down.
Also there were more error messages like these:
pmap_unwire:
On 5/2/23 13:24, Samuel Jayden wrote:
My firewall just slowed down after upgrading from 7.2 to 7.3.
Hello Samuel,
When you mention that your "firewall just slowed down" specifically what
metric and/or anecdotal data are/were you using to determine this
particular status of its
On 2023-05-31, Sven F. wrote:
> On Wed, May 31, 2023 at 5:27 PM Stuart Henderson
> wrote:
>
>> On 2023-05-31, Mark (obsd) wrote:
>> >>
>> > I'm not the OP, but that's interesting to me because I'm wondering if it's
>> > why Prometheus'
>> > node_exporter from packages is reporting wildly wrong
?
From: owner-m...@openbsd.org on behalf of Sven F.
Sent: Thursday, June 1, 2023 00:35
To: misc@openbsd.org
Subject: Re: High Interrupt After 7.3 Upgrade
On Wed, May 31, 2023 at 5:27 PM Stuart Henderson
wrote:
> On 2023-05-31, Mark (obsd) wrote:
> >
On Wed, May 31, 2023 at 5:27 PM Stuart Henderson
wrote:
> On 2023-05-31, Mark (obsd) wrote:
> > Hi Chris,
> >
> > On Tue, May 30, 2023 at 8:59 AM Chris Cappuccio
> wrote:
> >
> >> Samuel Jayden [samueljaydan1...@gmail.com] wrote:
> >> > Hi again,
> >> >
> >> > Just for the record:
> >> > I've
On 2023-05-31, Mark (obsd) wrote:
> Hi Chris,
>
> On Tue, May 30, 2023 at 8:59 AM Chris Cappuccio wrote:
>
>> Samuel Jayden [samueljaydan1...@gmail.com] wrote:
>> > Hi again,
>> >
>> > Just for the record:
>> > I've downgraded to OpenBSD 7.2 (reinstalled) and everything is working
>> like
>> > a
Hi Chris,
On Tue, May 30, 2023 at 8:59 AM Chris Cappuccio wrote:
> Samuel Jayden [samueljaydan1...@gmail.com] wrote:
> > Hi again,
> >
> > Just for the record:
> > I've downgraded to OpenBSD 7.2 (reinstalled) and everything is working
> like
> > a charm again.
> > I don't know what is wrong
Samuel Jayden [samueljaydan1...@gmail.com] wrote:
> Hi again,
>
> Just for the record:
> I've downgraded to OpenBSD 7.2 (reinstalled) and everything is working like
> a charm again.
> I don't know what is wrong with 7.3 but ipi interrupt rate is too much and
> somehow OpenBSD performance is too
Hi again,
Just for the record:
I've downgraded to OpenBSD 7.2 (reinstalled) and everything is working like
a charm again.
I don't know what is wrong with 7.3 but ipi interrupt rate is too much and
somehow OpenBSD performance is too bad..
Thanks for reading.
On Tue, May 2, 2023 at 9:24 PM Samuel
Hello misc,
My firewall just slowed down after upgrading from 7.2 to 7.3.
When I look at some values on the system I’ve realized there are high
interrupts on it.
Total Interrupts are over 40.000
em1 is over 4000
em2 is over 3000
Clock is nearly 2000
ipi over 30.000
But there are no
On 2023-04-25, rea...@catastrophe.net wrote:
> So if ${daemon} is declared as "autossh", using the built-in
> pexp="${daemon}:.*" would kill off multiple running autossh
> instances.
The idea is that pexp should have a bit more of the command line so
it only matches the process started by that
On Tue, Apr 25, 2023 at 03:07:19PM -0600, Ashlen wrote:
>rc_exec is a function, not a variable. rc.subr(8) demonstrates how to
>use it. This is what I meant for you to do:
>
>rc_start() {
>rc_exec "${daemon} ${daemon_flags_1}" && \
>rc_exec "${daemon} ${daemon_flags_2}"
>}
Whoops, my
On 2023-04-25 14:20, rea...@catastrophe.net wrote:
> On Tue, Apr 25, 2023 at 01:06:35PM -0600, Ashlen wrote:
> >On 2023-04-25 10:45, rea...@catastrophe.net wrote:
> >> After upgrading to 7.3 autossh is failing using the following rc script
> >> in /etc/rc.d/autossh. It looks like maybe switching
On Tue, Apr 25, 2023 at 02:20:01PM -0500, rea...@catastrophe.net wrote:
> On Tue, Apr 25, 2023 at 01:06:35PM -0600, Ashlen wrote:
> >On 2023-04-25 10:45, rea...@catastrophe.net wrote:
> >> After upgrading to 7.3 autossh is failing using the following rc script
> >> in /etc/rc.d/autossh. It looks
On Tue, Apr 25, 2023 at 07:18:12PM -, Stuart Henderson wrote:
>On 2023-04-25, rea...@catastrophe.net wrote:
>> On Tue, Apr 25, 2023 at 08:32:35PM +0200, Antoine Jacoutot wrote:
[..]
>
>So let's ignore this ls -l red herring, which cannot have worked
>in 7.2 either (I think you might have
1 - 100 of 1697 matches
Mail list logo
