Important message for Apple Silicon OpenBSD/arm64 users

As indicated here: https://social.treehouse.systems/@AsahiLinux/112449204541186432 The system firmware that comes with macOS Sonoma 14.5 triggers a bug in the m1n1 bootloader that is used to boot OpenBSD on these machines. The bug will prevent OpenBSD from booting on some machines after the

Re: replying to mailing list message after subscribing

On Fri, 15 Mar 2024 18:57:29 +0100, Evan Sherwood wrote: > Is that something you can do because you're a list administrator or > something? Still wondering if there is a way to do this without asking > someone to resend an email. Yes, it is something I can do because I'm a list administrator.

Re: replying to mailing list message after subscribing

> you should be able to reply to the copy in your "sent" folder Good to know. > I just re-sent the original messages to your new address so you should > now have a copy to reply to. Thanks! Is that something you can do because you're a list administrator or something? Still wondering if there

Re: replying to mailing list message after subscribing

On Fri, 15 Mar 2024 18:19:28 +0100, Evan Sherwood wrote: > I sent a message to this list earlier from a ProtonMail account, and > none of the replies have arrived (not even in Junk), even though I see > there are replies via the web archive... so I don't have a message to > reply to.

replying to mailing list message after subscribing

Apologies for the newbie question: I'm new to mailing lists. ;D I sent a message to this list earlier from a ProtonMail account, and none of the replies have arrived (not even in Junk), even though I see there are replies via the web archive... so I don't have a message to reply to. I've since

dhcpleaseed message in cloud environment

Hi, I have an OpenBSD 7.4 VM on Vultr and I sometimes notice the following from dhcpleased in syslogd: Feb 22 21:50:51 server dhcpleased[83222]: parse_dhcp: message from too short Although the message is referred to as being "too short", dhcpleased successfully acquires an IP

Re: Logging daemon message in a specific file

Hello Ze, Stuart, Thank you for your answers.Yes I did read the man page before sending my message but I understood "that further blocks would be evaluated cancelling !!prog" and therefore isakmpd and unbound would be logged in messages. At the end I didn't give a chance to this !*

Re: Logging daemon message in a specific file

On 2023-11-12, Rosen Iliev wrote: > Hello, > > man syslog.conf is your friend. > > /!!prog/ causes the subsequent block to abort evaluation when a message > matches, ensuring that only a single set of actions is taken. /!*/ ><https://man.openbsd.org/syslog.conf.5#!

Re: Logging daemon message in a specific file

ges. So I'm happy the way it behaves for isakmpd and unbound because > it's logged in their files and not in messages.The problem is that any other > message are not logged in messages. No more syslogs are added to messages. > > !!isakmpd > daemon.* 

Re: Logging daemon message in a specific file

Hello, man syslog.conf is your friend. /!!prog/ causes the subsequent block to abort evaluation when a message matches, ensuring that only a single set of actions is taken. /!*/ <https://man.openbsd.org/syslog.conf.5#!*> can be used to ensure that any ensuing blocks are further eva

Logging daemon message in a specific file

,user.info /var/log/messages 2) With this second method, the messages are logged in their files but not in messages. So I'm happy the way it behaves for isakmpd and unbound because it's logged in their files and not in messages.The problem is that any other message

Re: Smtpd is not adding message-id

On 09.10.23 22:56, Todd C. Miller wrote: I just committed the fix but I don't think there is a workaround. You will need to patch and recompile smtpd. Thank you very much. Have a great day -- Nicolas Goy Engineer & Developer https://www.kuon.ch https://www.goyman.com

Re: Smtpd is not adding message-id

On Mon, 09 Oct 2023 19:32:50 +0200, Nicolas Goy wrote: > I am hitting this issue with some go based process that send emails: > > https://github.com/OpenSMTPD/OpenSMTPD/issues/1068 > > Basically the client is not putting any Message-Id header and smtpd is > not adding it when

Smtpd is not adding message-id

Hello, I am hitting this issue with some go based process that send emails: https://github.com/OpenSMTPD/OpenSMTPD/issues/1068 Basically the client is not putting any Message-Id header and smtpd is not adding it when sending the email. Do you have an idea how to work around it? Or do I need

Re: smtpd.comf: '... reject "message"' fails

Florian Obser writes: > > You need this one: > > filter filter-name phase phase-name match conditions decision > Register a filter filter-name. A decision about what to do with > the mail is taken at phase phase-name when matching conditions. > Phases,

Re: smtpd.comf: '... reject "message"' fails

On Fri, 21 Oct 2022 15:58:54 -, Stuart Henderson wrote: > (For those that don't know, it seems that T-Online.de block incoming > email from most IPs by default and anyone wanting to send them mail > has to explicitly contact them to ask permissions, and they make you > jump through hoops

Re: smtpd.comf: '... reject "message"' fails

On 2022-10-21, Lyndon Nerenberg (VE7TFX/VE6BBM) wrote: > My reading of smtpd.conf says that any reject action should be able > to take a message parameter. Yet the following line is rejected > with a syntax error message: > > match mail-from rdns regex "\.t-online\.de$&qu

Re: smtpd.comf: '... reject "message"' fails

On 2022-10-20 21:38 -07, "Lyndon Nerenberg (VE7TFX/VE6BBM)" wrote: > My reading of smtpd.conf says that any reject action should be able > to take a message parameter. Yet the following line is rejected > with a syntax error message: > > match mail-from rdns regex &quo

smtpd.comf: '... reject "message"' fails

My reading of smtpd.conf says that any reject action should be able to take a message parameter. Yet the following line is rejected with a syntax error message: match mail-from rdns regex "\.t-online\.de$" reject "550 5.7.1 you don't accept our mail, so we don't accept yours.

odd shutdown message

I have a VPS at openbsd amsterdam that shutdown with the message that _unbound shut it down when it was my user OR root. sky# zgrep unbound /var/log/authlog*gz /var/log/authlog.0.gz:Nov 26 08:59:04 sky shutdown: reboot by _unbound: It was recorded in the logs as such. I haven't totally figured

Re: rad daemon strange error message

Thanks a lot. You were right and my eyes have corrected the misspelling. After correcting the config the RAD server seems to work correctly. kind regards On Wed, 30 Jun 2021 13:58:17 +0200 Markus Wernig wrote: > On 6/30/21 1:32 PM, Pierre Dupond wrote: > > veteher30 has no IPv6 link-local

Re: rad daemon strange error message

On 6/30/21 1:32 PM, Pierre Dupond wrote: > veteher30 has no IPv6 link-local address, ignoring ^ I don't know rad, but from the output above there seems to be a typo in some config.

rad daemon strange error message

Hi All, I am trying to setup the rad daemon on a quite complicated configuration. I receive however a strange error message which I don't understand fully. The message claims that there is no link local address on the device "vether30". But, as far as I understand a su

DHCP client always no lease message but got IP

Hello, Most recent snaphots. amd64, DHCP client for interface is always displaying no lease . sleeping. It actually gets the IP address, but this message is always there. I tried with more routers, same thing. Thanks

IPv6 over PPPoE with Plusnet/QSC, IP6CP message gets rejected?

with a pcap file of a working handshake, presumably from a non-BSD client. they show the pppoe client sending a IP6CP Conf-Request message to the server, and the server responding with a IP6CP Conf-Request message on its own. after that, NDP RA and DHCPv6 messages handle the actual WAN and LAN

Re: Message WARNING: CHECK AND RESET THE DATE! in kvm guests

On Tue, Jun 02, 2020 at 08:28:13AM +, Carlos Lopez wrote: > Hi Otto, > > After some days without problems, it has happened again: > > root on sd0a (912329c5d9d2b184.a) swap on sd0b dump on sd0b > WARNING: clock gained 3 days > WARNING: CHECK AND RESET THE DATE! > > With version 6.6 I

Re: Message WARNING: CHECK AND RESET THE DATE! in kvm guests

Hi Otto, After some days without problems, it has happened again: root on sd0a (912329c5d9d2b184.a) swap on sd0b dump on sd0b WARNING: clock gained 3 days WARNING: CHECK AND RESET THE DATE! With version 6.6 I never had these problems. I am using default conf for ntpd, but some errors

Re: Message WARNING: CHECK AND RESET THE DATE! in kvm guests

On Mon, May 25, 2020 at 07:53:47AM +, Carlos Lopez wrote: > Hi all, > > After upgrading four kvm guests to OpenBSD 6.7, I see the following messages > when these guests starts: > > WARNING: clock gained 2 days > WARNING: CHECK AND RESET THE DATE! This means the clock compared to the last

Message WARNING: CHECK AND RESET THE DATE! in kvm guests

Hi all, After upgrading four kvm guests to OpenBSD 6.7, I see the following messages when these guests starts: WARNING: clock gained 2 days WARNING: CHECK AND RESET THE DATE! All four guests are fully patched. Dmesg output: OpenBSD 6.7 (GENERIC) #1: Sat May 16 16:07:20 MDT 2020

Re: LDPD includes non-default rdomain interfaces to address message type

d. moreover ldp address message structure is nothing about the > configuration at all. > > чт, 7 мая 2020 г., 21:29 Theo de Raadt : > > Sergey wrote: > > > ok theo, you are very user friendly as always. > > you may be think that users should sol

Re: LDPD includes non-default rdomain interfaces to address message type

Sergey wrote: > ok theo, you are very user friendly as always. > you may be think that users should solve their issues themself and would be > nice if > they will post their effort here for you, very fair. You want the people on misc@ to decide for you if code from 2018 might work better than

Re: LDPD includes non-default rdomain interfaces to address message type

PLS PE router with many domains, and i noticed that > > ldpd sends huge ldp address message including all interfaces > > in every rdomains. > > Looking at the -current sources it seems there is the same behavior, > > but may be im wrong. > > Can someone confirm

Re: LDPD includes non-default rdomain interfaces to address message type

Sergey wrote: > Hi. > > Im using the pretty old release 5.5 on openbsd box acting > as MPLS PE router with many domains, and i noticed that > ldpd sends huge ldp address message including all interfaces > in every rdomains. > Looking at the -current sources it seems there

LDPD includes non-default rdomain interfaces to address message type

Hi. Im using the pretty old release 5.5 on openbsd box acting as MPLS PE router with many domains, and i noticed that ldpd sends huge ldp address message including all interfaces in every rdomains. Looking at the -current sources it seems there is the same behavior, but may be im wrong. Can

Re: "not MAP_STACK" message in dmesg / system message buffer

: [a.out]94530/186499 sp=7f7ff5fe58c0 inside > 7f7fff7e7000-7f7e6000: not MAP_STACK > Feb 25 20:07:09 hamlet /bsd: [a.out]9523/344960 sp=7f7ff5fd9fd0 inside > 7f7fff7db000-7f7db000: not MAP_STACK > > I have not seen a segfaulting program being logged in system > message

Re: "not MAP_STACK" message in dmesg / system message buffer

> > 7f7fff7d5000-7f7d5000: not MAP_STACK > > Feb 25 20:06:49 hamlet /bsd: [a.out]94530/186499 sp=7f7ff5fe58c0 inside > > 7f7fff7e7000-7f7e6000: not MAP_STACK > > Feb 25 20:07:09 hamlet /bsd: [a.out]9523/344960 sp=7f7ff5fd9fd0 inside > > 7f7fff7db000-7f7ff

Re: "not MAP_STACK" message in dmesg / system message buffer

side > 7f7fff7e7000-7f7e6000: not MAP_STACK > Feb 25 20:07:09 hamlet /bsd: [a.out]9523/344960 sp=7f7ff5fd9fd0 inside > 7f7fff7db000-7f7db000: not MAP_STACK > > I have not seen a segfaulting program being logged in system > message buffer before. Is it expected behavi

"not MAP_STACK" message in dmesg / system message buffer

7f7fff7db000-7f7db000: not MAP_STACK I have not seen a segfaulting program being logged in system message buffer before. Is it expected behaviour? Just curious, the message was a bit confusing. The system is amd64-current. -- Andre

Fixed! (was: unwindctl doesn't connect to unwind, error message: "unwindctl: connect: /var/run/unwind.sock: No such file or directory")

Hi, with the latest snapshot the problem is solved:     vatrox$ unwindctl status DoT         selected type status            *  DoT validating            histogram[ms]            <10   <20   <40   <60   <80  <100 <200  <400  <600  <800 <1000 

Re: unwindctl doesn't connect to unwind, error message: "unwindctl: connect: /var/run/unwind.sock: No such file or directory"

gt; > > > > Felix > > > > > > On 2019-11-06 16:08, Otto Moerbeek wrote: > > > > On Wed, Nov 06, 2019 at 03:41:10PM +0100, Felix Maschek wrote: > > > > > > > > > Hi, > > > > > > > > > > I've used

Re: unwindctl doesn't connect to unwind, error message: "unwindctl: connect: /var/run/unwind.sock: No such file or directory"

Moerbeek wrote: On Wed, Nov 06, 2019 at 03:41:10PM +0100, Felix Maschek wrote: Hi, I've used unwind for some weeks and observed a problem after upgrading to last snapshot (after some weeks). Calling unwindctl leads to the following error message:     vatrox$ unwindctl status DoT    

Re: unwindctl doesn't connect to unwind, error message: "unwindctl: connect: /var/run/unwind.sock: No such file or directory"

On Wed, Nov 06, 2019 at 04:29:16PM +0100, Otto Moerbeek wrote: > On Wed, Nov 06, 2019 at 04:16:10PM +0100, Felix Maschek wrote: > > > Hi, > > > > unwind is running and does talk to 9.9.9.9 (checked with DNS Leak Test - > > bash.ws ): > > > >     vatrox$ ps -A | grep

Re: unwindctl doesn't connect to unwind, error message: "unwindctl: connect: /var/run/unwind.sock: No such file or directory"

te: > > On Wed, Nov 06, 2019 at 03:41:10PM +0100, Felix Maschek wrote: > > > > > Hi, > > > > > > I've used unwind for some weeks and observed a problem after upgrading to > > > last snapshot (after some weeks). > > > > > > Calling unwindctl

Re: unwindctl doesn't connect to unwind, error message: "unwindctl: connect: /var/run/unwind.sock: No such file or directory"

alling unwindctl leads to the following error message:     vatrox$ unwindctl status DoT     unwindctl: connect: /var/run/unwind.sock: No such file or directory My configuration (which still is functional):     /etc/rc.conf.local:         unwind_flags=""     /etc/dhclient.conf:

Re: unwindctl doesn't connect to unwind, error message: "unwindctl: connect: /var/run/unwind.sock: No such file or directory"

On Wed, Nov 06, 2019 at 03:41:10PM +0100, Felix Maschek wrote: > Hi, > > I've used unwind for some weeks and observed a problem after upgrading to > last snapshot (after some weeks). > > Calling unwindctl leads to the following error message: > >     vatr

unwindctl doesn't connect to unwind, error message: "unwindctl: connect: /var/run/unwind.sock: No such file or directory"

Hi, I've used unwind for some weeks and observed a problem after upgrading to last snapshot (after some weeks). Calling unwindctl leads to the following error message:     vatrox$ unwindctl status DoT     unwindctl: connect: /var/run/unwind.sock: No such file or directory My configuration

Re: umsm0: this device is not using CDC notify message in intr pipe. HP Compaq dc5750

On Fri, 5 Jul 2019, Kihaguru Gathura wrote: This was working up and until OpenBSD 6.4 amd64. With OpenBSD 6.5 i386 release on a Samsung nc10 nettop and with a Huawei E372 modem umsm is working. I do not know what is happening in current. For me it would be a catastrophe if it stops

Re: umsm0: this device is not using CDC notify message in intr pipe. HP Compaq dc5750

On 6/29/19, Chris Cappuccio wrote: > Kihaguru Gathura [pqscr...@gmail.com] wrote: >> Hello, >> >> Huawei E303 modem now detaches in OpenBSD 6.5 This works fine on >> OpenBSD 6.2 same machine. >> > > There's a remote chance that this is fixed in 6.5-current. Some USB work > has been going on. But

Re: umsm0: this device is not using CDC notify message in intr pipe. HP Compaq dc5750

Kihaguru Gathura [pqscr...@gmail.com] wrote: > Hello, > > Huawei E303 modem now detaches in OpenBSD 6.5 This works fine on > OpenBSD 6.2 same machine. > There's a remote chance that this is fixed in 6.5-current. Some USB work has been going on. But if that doesn't work, you'll have to try more

umsm0: this device is not using CDC notify message in intr pipe. HP Compaq dc5750

om removable umass1 at uhub0 port 10 configuration 1 interface 4 "HUAWEI HUAWEI Mobile" rev 2.00/1.02 addr 2 umass1: using SCSI over Bulk-Only scsibus3 at umass1: 2 targets, initiator 0 sd2 at scsibus3 targ 1 lun 0: SCSI2 0/direct removable vscsi0 at root scsibus4 at vscsi0: 256 targets

Re: Ansible install Re: Reboot and re-link (ignore previously sent message)

[Please ignore the previous message I sent on this topic. I accidentally pressed 'Send' before my message was complete.] On 22/06/2019 19:52, cho...@jtan.com wrote: > Lyndon Nerenberg writes: >> We are looking forward to that. *However*, there is a lot to be >> said for regularl

libssl/libtls signal the wrong signature algorithm in ServerKeyExchange message

In case an ECDSA based server certificate with ECDHE based key exchange is used, I've notice that the ServerKeyExchange message (always?) signals that this message has been signed with ecdsa-secp521r1-sha512 (0x0603) [tested on current with TLS 1.2 with P-256 as well as with P-521 server

About some smptd(8) log message

uot;vdomains" and "valiases" tables), it appears a "Mailing list expansion problem" message: [...] smtp failed-command command="RCPT TO:" result="524 5.2.4 Mailing list expansion problem: " In case what I assumed above is correct. :-) Is the "Maili

Re: chflags error message

Hi Marcus, [redirecting to misc@, this is not a bug and all is working as intended] By the time your recursive chflags gets to pkg_add, it will already have the flag. Note that these flags are per inode, and several files under /usr/sbin have the same inode: [weerd@despair] $ cd /usr/sbin; ls

isakmpd: dropped message from 192.168.1.1 port 500 due to notification type INVALID_FLAGS

Dear Friends, IPSEC+L2TP fails with the following messages on IPSEC router: isakmpd[76756]: message_recv: cleartext phase 2 isakmpd[76756]: dropped message from 192.168.1.1 port 500 due to notification type INVALID_FLAGS Aug 17 isakmpd[76756]: transport_send_messages: giving up on exchange peer

Dmesg Crash error message

Hello readers, I read crash(8) first, my kernel told me : process: table is full syncing disk init died. Did i ran too much process ? where can i check that ? Best. ( i m upgrading and this is 6.0 , i guess the message may appear again

Re: iked support for IKEv2 Message Fragmentation (RFC 7383)

Tim Stewart writes: > Hello misc@, > > My IKEv2 sessions are occasionally down due to transit networks dropping > UDP fragments for one reason or another[1]. It happens frequently > enough that I am considering implementing support for RFC 7383 in > iked. > > Before I dig in, I feel that I

iked support for IKEv2 Message Fragmentation (RFC 7383)

Hello misc@, My IKEv2 sessions are occasionally down due to transit networks dropping UDP fragments for one reason or another[1]. It happens frequently enough that I am considering implementing support for RFC 7383 in iked. Before I dig in, I feel that I should ask if anyone has already started

Re: Disabling message CRCs in SSHD

Thanks. Appreciate it!! :) > Sent: Saturday, April 28, 2018 at 11:11 AM > From: "Darren Tucker" <dtuc...@dtucker.net> > To: "Hess THR" <hessnovth...@mail.com> > Cc: "OpenBSD Misc List" <misc@openbsd.org> > Subject: Re: Disabli

Re: Disabling message CRCs in SSHD

H code) but didn't found it, didn't even find > similar for disabling message CRCs: Short answer: It's gone, you can ignore that part. Long answer: CRC32 was the message integrity method for SSH Protocol v1 and the last of the SSH1 code was removed[0] in the 7.6 release[1] (in part because CRC32

Disabling message CRCs in SSHD

Based on the: http://www.vegardno.net/2017/03/fuzzing-openssh-daemon-using-afl.html I tried to search for these code pieces (I know he was using openbsd-compat and not the original OpenSSH code) but didn't found it, didn't even find similar for disabling message CRCs: in the ( https

Re: Message arrived but could not be stored

> > The appended message was received, but could not be stored in the mail > database on imap.lrau.net. > > The error detected was: Content-Language: Unparseable value: "English & Greek" > > Here are a few header fields from the message (possibly corrupted due to

Feb 10 snapshot - nd6_dad_timer kernel message

Hello, I upgraded my Feb 8 snapshot to Feb 10. After bsd.rd was booted, I saw this kernel message I have not seen before: nd6_dad_timer: called with non-tentative address 2601:2c2:600:2c5d:898e:c06d:294c:16c8(re0) After completing the install, I couldn't connect using IPv6: b1$ ping6

Re: How to send a bug report with sendbug? What to configure to actually send the message?

Thanks for the answer. On Friday, February 9, 2018 1:29 AM, "ed...@pettijohn-web.com" <ed...@pettijohn-web.com> wrote: On Feb 8, 2018 4:26 PM, Tom Smyth <tom.sm...@wirelessconnect.eu> wrote: > > Hi Zolt > > you can open the message on a co

Re: How to send a bug report with sendbug? What to configure to actually send the message?

On Friday, February 9, 2018 12:33 AM, Tom Smyth <tom.sm...@wirelessconnect.eu> wrote: Hi Zolt you can open the message on a command terminal ...  copy and paste the message manually into a working email client, make sure the subject and email addresses are consistent I hope this

Re: How to send a bug report with sendbug? What to configure to actually send the message?

On Feb 8, 2018 4:26 PM, Tom Smyth <tom.sm...@wirelessconnect.eu> wrote: > > Hi Zolt > > you can open the message on a command terminal ...  copy and paste > the message manually into a working email client, > make sure the subject and email addresses are consistent > &g

Re: How to send a bug report with sendbug? What to configure to actually send the message?

Hi Zolt you can open the message on a command terminal ... copy and paste the message manually into a working email client, make sure the subject and email addresses are consistent I hope this helps ... Tom Smyth On 8 February 2018 at 21:37, Zsolt Kantor <zsoltkan...@yahoo.co.uk>

How to send a bug report with sendbug? What to configure to actually send the message?

Hello, I'm very new to the OpenBSD OS, I found a bug in the inteldrm driver and I want to send it with sendbug. Probably something needs to be configured to actually send out the message, because I sent the bug report, but it only landed in my local mailbox. The question is what should I

Re: message authentication code incorrect

On Jan 24 14:13:56, openbsd+m...@list.imperialat.at wrote: > Hello Jan, > > See https://marc.info/?l=openbsd-cvs=151673244010209=2 and > https://marc.info/?l=openbsd-cvs=151673766411788=2. > So it's probably fixed in the next snapshot. Yes it is. Thanks. Jan

Re: message authentication code incorrect

Bad packet length 1349676916. ssh_dispatch_run_fatal: Connection to 147.32.233.137 port 22: message authentication code incorrect Jan > from an amd64 machien running the Jan 19 snapshot: > > $ ssh -v biblio.stare.cz > OpenSSH_7.6, LibreSSL 2.7.0 > debug1: Read

Re: message authentication code incorrect

On Wed, Jan 24 2018, Jan Stary wrote: > On Jan 23 16:48:57, h...@stare.cz wrote: >> I just upgraded my current/amd64 and now con't ssh to it > > In fact, I can't ssh _fom_ it either: > > $ ssh wherever > write: Socket is not connected > > has something changed with ssh or sshd?

Re: message authentication code incorrect

SH* compat 0x0400 >> debug1: Authenticating to biblio.stare.cz:22 as 'hans' >> debug1: SSH2_MSG_KEXINIT sent >> Bad packet length 1349676916. >> ssh_dispatch_run_fatal: Connection to 147.32.233.137 port 22: message >> authentication code incorrect >> >> Jan >> >

Re: message authentication code incorrect

io.stare.cz:22 as 'hans' > debug1: SSH2_MSG_KEXINIT sent > Bad packet length 1349676916. > ssh_dispatch_run_fatal: Connection to 147.32.233.137 port 22: message > authentication code incorrect > > Jan >

Re: message authentication code incorrect

ug1: Remote protocol version 2.0, remote software version OpenSSH_7.6 > debug1: match: OpenSSH_7.6 pat OpenSSH* compat 0x0400 > debug1: Authenticating to biblio.stare.cz:22 as 'hans' > debug1: SSH2_MSG_KEXINIT sent > Bad packet length 1349676916. > ssh_dispatch_run_fatal: Connection to 147.32.233.137 port 22: message > authentication code incorrect > > Jan >

message authentication code incorrect

: SSH2_MSG_KEXINIT sent Bad packet length 1349676916. ssh_dispatch_run_fatal: Connection to 147.32.233.137 port 22: message authentication code incorrect Jan

Re: Strange message from syspatch

On 2018-01-12, Stuart Henderson <s...@spacehopper.org> wrote: > On 2018-01-12, dmitry.sensei <dmitry.sen...@gmail.com> wrote: >> Strange message from syspatch: >> # syspatch >> ftp: SSL write error: no OCSP URLs in peer certificate >> # > > Simplest

Re: Strange message from syspatch

On 2018/01/12 09:03, Bryan Harris wrote: > I once had incorrect VM time causing OCSP response like it was out of date, > and syspatch > refused in a similar way. Yes. That causes problems for the installer too, it's unable to fetch the list of mirrors (and ironically the time that it uses to

Re: Strange message from syspatch

t;dmitry.sen...@gmail.com> wrote: > > Strange message from syspatch: > > # syspatch > > ftp: SSL write error: no OCSP URLs in peer certificate > > # > > Simplest workaround is to download the files yourself and use a local > url in /etc/installurl, e.g. file://

Re: Strange message from syspatch

On 2018-01-12, dmitry.sensei <dmitry.sen...@gmail.com> wrote: > Strange message from syspatch: > # syspatch > ftp: SSL write error: no OCSP URLs in peer certificate > # Simplest workaround is to download the files yourself and use a local url in /etc/installurl, e.g. file:///tmp

Strange message from syspatch

Strange message from syspatch: # syspatch ftp: SSL write error: no OCSP URLs in peer certificate # what does this message mean and what to check? OpenBSD 6.2-stable GENERIC.MP#2 amd64 we have a fortinet in the middle. Previously, it did not interfere with the utility, since I added its

Re: FastCGI sent in stderr: "PHP message: PHP Warning: Unknown: Unable to create temporary file, Check permissions in temporary files directory.

e >> chroot? If I were to guess, I would bet that php is trying to create a >> file after chrooting itself, and inside the chroot, /var/www/tmp doesn't >> exist. Try setting those env vars to /tmp and see if that works. >> >> Todd >> >> On Tue, Jul 25, 2

Re: FastCGI sent in stderr: "PHP message: PHP Warning: Unknown: Unable to create temporary file, Check permissions in temporary files directory.

itself, and inside the chroot, /var/www/tmp doesn't > exist. Try setting those env vars to /tmp and see if that works. > > Todd > > On Tue, Jul 25, 2017 at 09:03:38AM +0200, Stephane HUC "PengouinBSD" wrote: >> Hi all. >> >> I have this error on my,OpenBSD s

Re: FastCGI sent in stderr: "PHP message: PHP Warning: Unknown: Unable to create temporary file, Check permissions in temporary files directory.

exist. Try setting those env vars to /tmp and see if that works. Todd On Tue, Jul 25, 2017 at 09:03:38AM +0200, Stephane HUC "PengouinBSD" wrote: > Hi all. > > I have this error on my,OpenBSD server (6.1) : > > FastCGI sent in stderr: "PHP message: PHP Warning

Re: FastCGI sent in stderr: "PHP message: PHP Warning: Unknown: Unable to create temporary file, Check permissions in temporary files directory.

On 25 July 2017 5:03:38 pm AEST, "Stephane HUC "PengouinBSD"" <b...@stephane-huc.net> wrote: >Hi all. > >I have this error on my,OpenBSD server (6.1) : > >FastCGI sent in stderr: "PHP message: PHP Warning: Unknown: Unable to >create temporary fil

FastCGI sent in stderr: "PHP message: PHP Warning: Unknown: Unable to create temporary file, Check permissions in temporary files directory.

Hi all. I have this error on my,OpenBSD server (6.1) : FastCGI sent in stderr: "PHP message: PHP Warning: Unknown: Unable to create temporary file, Check permissions in temporary files directory. in Unknown on line 0 I use nginx+php70_fpm ! The php-fpm.conf for the instance:

No message-id header on port 587 - OpenSMTPD

I have configured an OpenSMPTD server to use port 587 upon which to receive inbound mail. When the email is delivered I do not see a message-id from this originating SMTP server, instead I see a message-id header inserted by the last server in the line, i.e. in this case my office's Exchange

Re: Missing message-ID header in OpenSMTPD emails

I don't use the submission port on either server, just port 25, but 5.9 sends a message-id and 6.0 does not. What does "/if necessary/" mean for the 5.9 server? What is the deciding factor to make the header necessary? I would like the v6.0 server to send a message-id too, how do I mak

Re: Missing message-ID header in OpenSMTPD emails

LD wrote: > I don't use the submission port on either server, just port 25, but 5.9 > sends a message-id and 6.0 does not. What does "/if necessary/" mean for the > 5.9 server? What is the deciding factor to make the header necessary? I > would like the v6.0 server to send a

Missing message-ID header in OpenSMTPD emails

I have an OpenBSD 5.9 and an OpenBSD 6.0 server each set up as email servers. The v5.9 server adds a message-id header to outgoing emails, the v6.0 does not. Looking at the change log for each release it states that for v5.9 "/Add Message-Id header if necessary/" and v6.0 "/A

Re: splassert: yield message on 5 Feb snapshot (amd64)

Stefan Wollny wrote: > at least with > > $ dmesg | grep Open > OpenBSD 6.0-current (GENERIC.MP) #166: Wed Feb 8 19:15:03 MST 2017 > > the issue still persists. The patch that solve the issue (at least in my machine) was committed today:

Re: splassert: yield message on 5 Feb snapshot (amd64)

Am 02/09/17 um 18:02 schrieb Martin Pieuchot: > On 09/02/17(Thu) 17:55, Stefan Wollny wrote: >> Am 02/08/17 um 17:57 schrieb Hrvoje Popovski: >>> On 8.2.2017. 17:51, Scott Vanderbilt wrote: >>>> Updated a machine to latest (5 Feb.) snapshot of amd64. I'm now seeing &g

Re: splassert: yield message on 5 Feb snapshot (amd64)

On 09/02/17(Thu) 17:55, Stefan Wollny wrote: > Am 02/08/17 um 17:57 schrieb Hrvoje Popovski: > > On 8.2.2017. 17:51, Scott Vanderbilt wrote: > >> Updated a machine to latest (5 Feb.) snapshot of amd64. I'm now seeing > >> the following message after booting that I've

Re: splassert: yield message on 5 Feb snapshot (amd64)

Am 02/08/17 um 17:57 schrieb Hrvoje Popovski: > On 8.2.2017. 17:51, Scott Vanderbilt wrote: >> Updated a machine to latest (5 Feb.) snapshot of amd64. I'm now seeing >> the following message after booting that I've not recalled seeing before: >> >>splassert: yield

Re: splassert: yield message on 5 Feb snapshot (amd64)

On 8.2.2017. 17:51, Scott Vanderbilt wrote: > Updated a machine to latest (5 Feb.) snapshot of amd64. I'm now seeing > the following message after booting that I've not recalled seeing before: > >splassert: yield: want 0 have 1 add sysctl kern.splassert=2 ...

splassert: yield message on 5 Feb snapshot (amd64)

Updated a machine to latest (5 Feb.) snapshot of amd64. I'm now seeing the following message after booting that I've not recalled seeing before: splassert: yield: want 0 have 1 Looking in the list archives, I see a thread from Sept. 2016 where the following response from Theo Buehler

Boot message: RSDT entry 4 is corrupt

"acpidump: RSDT entry 4 is corrupt" I get this message during the boot sequence. I'd just upgraded to the latest snapshot but possibly it had appeared earlier - I only noticed it because I was sorting out an unrelated problem. After a net search the only thing I could come up with

OpenBSD Stable(error message)

-package-args (wantlib-args) for details. i used cvs up -rOPENBSD_6_0 -Pd to update the port but i keep getting the same error message. Thanks!

Re: Interesting error message from disk testing

On Tue, 28 Jun 2016, STeve Andre' wrote: I am testing some new 8TB disks. I've taken to doing dd if=/dev/zero of=/dev/rsd3c bs=64k and dd if=/dev/rsd3c of=/dev/null bs=64k as a first test. It's depressing how often I've found problems on big disks. Today, the read test produced an

Interesting error message from disk testing

I am testing some new 8TB disks. I've taken to doing dd if=/dev/zero of=/dev/rsd3c bs=64k and dd if=/dev/rsd3c of=/dev/null bs=64k as a first test. It's depressing how often I've found problems on big disks. Today, the read test produced an error in the messages file I've not seen

Re: smtpd : reject with a message

On Wed, Apr 13, 2016 at 06:14:36PM +, Peter Fraser wrote: > Is there any method of added extra information when rejecting an email with > smtpd > > I am looking for an equivalent effect to the .REDIRECT or error message in > sendmail's virtualusertable > > for exampl

  1   2   3   4   5   >