Re: Error messages with VMM on 6.6 and 6.7

On Tue, Jun 02, 2020 at 10:18:32AM +0800, jrmu wrote: > OpenBSD VMM suffers from error messages and possibly spontaneous crashing > > System : OpenBSD 6.7 > Details : OpenBSD 6.7 (GENERIC.MP) #182: Thu May 7 11:11:58 MDT > 2020 >

Error messages with VMM on 6.6 and 6.7

OpenBSD VMM suffers from error messages and possibly spontaneous crashing System : OpenBSD 6.7 Details : OpenBSD 6.7 (GENERIC.MP) #182: Thu May 7 11:11:58 MDT 2020 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP

Re: ttyC0 floods with error messages

I'm the original poster of this thread, don't mean to whip a dead horse, but this post is to confirm the state of this issue. The most recent -current release before this post has fixed this issue for me. OpenBSD 6.6-current (GENERIC.MP) #573: Sat Dec 28 19:13:57 MST 2019

Re: ttyC0 floods with error messages

"Raymond, David" wrote: > I get similar stuff on console 1 but not on the others on all my > OpenBSD machines. As I use X windows and have clean consoles 2-4 > available if necessary, I just ignore it. > > Dave Raymond > > > On 12/16/19, putridsou...@gmail.com wrote: > > The error does not

Re: ttyC0 floods with error messages

On 12-16 10:48, Raymond, David wrote: > I get similar stuff on console 1 but not on the others on all my > OpenBSD machines. As I use X windows and have clean consoles 2-4 > available if necessary, I just ignore it. I get similar messages in dmesg (used to be on the first console), and every

Re: ttyC0 floods with error messages

USB subsystem bugs. Whoever said it was your mouse or cable is being an inaccurate jerk. Raymond, David wrote: > I get similar stuff on console 1 but not on the others on all my > OpenBSD machines. As I use X windows and have clean consoles 2-4 > available if necessary, I just ignore it. >

Re: ttyC0 floods with error messages

I get similar stuff on console 1 but not on the others on all my OpenBSD machines. As I use X windows and have clean consoles 2-4 available if necessary, I just ignore it. Dave Raymond On 12/16/19, putridsou...@gmail.com wrote: > The error does not seem to be a faulty mouse and I > don't use

Re: ttyC0 floods with error messages

The error does not seem to be a faulty mouse and I don't use a KVM switch anyway so it is not the source. Following on pervious reply, I tried on a new mouse. But was greeted with the same error: wsmouse0 detached ums0 detached uhidev0 detached uhidev0 at uhub0 port 4 configuration 1 interface 0

Re: ttyC0 floods with error messages

On Fri, Dec 13, 2019 at 8:42 AM wrote: > After boot, the following error message floods the virtual console on > ttyC0 repeatedly, rest of virtuals console stay clear somehow. Is there a > way to > treat this permanently, other than Ctrl-l everytime, or disconnecting the > mouse. > There must be

Re: ttyC0 floods with error messages

On Fri, 13 Dec 2019, putridsou...@gmail.com wrote: Date: Fri, 13 Dec 2019 19:12:41 +0530 (IST) From: putridsou...@gmail.com To: misc@openbsd.org Subject: ttyC0 floods with error messages After boot, the following error message floods the virtual console on ttyC0 repeatedly, rest of virtuals

ttyC0 floods with error messages

After boot, the following error message floods the virtual console on ttyC0 repeatedly, rest of virtuals console stay clear somehow. Is there a way to treat this permanently, other than Ctrl-l everytime, or disconnecting the mouse. There must be some config to disable this direct dumping of

Re: help understanding ikectl error messages

Thanks Stuart for replies! I can confirm that I could proceed without issues on 6.2-current. :-) BR, Andreas mån 15 jan. 2018 kl. 10:31 skrev Stuart Henderson : > On 2018/01/15 06:35, Andreas Thulin wrote: > > Sorry, my bad! > > > > 6.2-stable. And after sending my e-mail,

Re: help understanding ikectl error messages

On 2018/01/15 06:35, Andreas Thulin wrote: > Sorry, my bad! > > 6.2-stable. And after sending my e-mail, I found a post about this issue, > that ended up in > ikeca.c (?) having been patched on 8 November last year to resolve the same > issue, I believe. I > have installed 6.2-current on

Re: help understanding ikectl error messages

Sorry, my bad! 6.2-stable. And after sending my e-mail, I found a post about this issue, that ended up in ikeca.c (?) having been patched on 8 November last year to resolve the same issue, I believe. I have installed 6.2-current on another machine to figure out if that solves the problem. BR,

Re: help understanding ikectl error messages

On 2018-01-09, Andreas Thulin wrote: > Hi! > > Following the example on https://man.openbsd.org/ikectl, I > > # ikectl ca test create > ...and then > # ikectl ca test certificate sub.domain.com create > ...filled out "the form", but after that... > Using configuration

help understanding ikectl error messages

Hi! Following the example on https://man.openbsd.org/ikectl, I # ikectl ca test create ...and then # ikectl ca test certificate sub.domain.com create ...filled out "the form", but after that... Using configuration from /etc/ssl/test/sub.domain.com-ssl.cnf Check that the request matches the

Re: understanding ldapd log error messages

> Use the options "-dv" at first. If you need to see th BER messages > use "-dvv" (see also "man ldapd"). Do you see anything in this snipped b,dc=org by any, in namespace dc=autonlab,dc=org Apr 23 23:19:09.481 [18682] found dn uid=rrabbany,ou=users,dc=autonlab,dc=org Apr 23 23:19:09.481

Re: understanding ldapd log error messages

Robert Klein wrote: > Hi, > > On Sat, 22 Apr 2017 21:55:58 -0400 > Predrag Punosevac wrote: > > > Predrag Punosevac write: > > > Hi misc, > > > > > > ldapd on one of my two ldap servers stop working overnight > > > > > > > ldapd died again

Re: understanding ldapd log error messages

Hi, On Sat, 22 Apr 2017 21:55:58 -0400 Predrag Punosevac wrote: > Predrag Punosevac write: > > Hi misc, > > > > ldapd on one of my two ldap servers stop working overnight > > > > ldapd died again overnight. I noticed that this started happening not > right after the

Re: understanding ldapd log error messages

Predrag Punosevac write: > Hi misc, > > ldapd on one of my two ldap servers stop working overnight > ldapd died again overnight. I noticed that this started happening not right after the upgrade to 6.1 but less than 24h after I added a person to my LDAP database. How do I go about debugging a

understanding ldapd log error messages

Hi misc, ldapd on one of my two ldap servers stop working overnight # uname -a OpenBSD atlas.int.autonlab.org 6.1 GENERIC.MP#20 amd64 I manually restarted it and it appears to work OK. I started digging little bit through the log

Error messages in dmesg output about intel_dp_set_link_train and i915_write32

Hi guys, I just upgraded my laptop from 5.7 to 5.8 and I notice error messages in my dmesg output. Any ideas? OpenBSD 5.8 (GENERIC.MP) #1236: Sun Aug 16 02:31:04 MDT 2015 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 4178116608 (3984MB) avail mem

Re: help with bgpd error messages

On Thu, 7 May 2015 13:01:49 +0200 Marko Cupać marko.cu...@mimar.rs wrote: On Wed, 6 May 2015 10:53:38 + (UTC) Stuart Henderson s...@spacehopper.org wrote: Can you get a packet capture of TCP port 179 during a failure? tcpdump -i interface -w bgp.`date +%Y%m%d-%H%M`.pcap -s1500 tcp

Re: help with bgpd error messages

On Wed, 6 May 2015 10:53:38 + (UTC) Stuart Henderson s...@spacehopper.org wrote: Can you get a packet capture of TCP port 179 during a failure? tcpdump -i interface -w bgp.`date +%Y%m%d-%H%M`.pcap -s1500 tcp and port 179 It might be best to run it from a script run from cron which

Re: help with bgpd error messages

On Wed, 29 Apr 2015 11:02:09 +0200 Marko Cupać marko.cu...@mimar.rs wrote: On Tue, 28 Apr 2015 15:11:21 +0200 Claudio Jeker cje...@diehard.n-r-g.com wrote: The fatal in RDE: peer_up: bad state bug is fixed in 5.7 IIRC. Not sure if it was backported to 5.6. As a workaround you can disable

Re: help with bgpd error messages

* Marko Cupać marko.cu...@mimar.rs [2015-05-06 12:01]: I am on 5.7 release + errata patches now, and bgpd crashed again: May 6 10:06:07 bgp1 bgpd[11681]: neighbor 82.117.192.121 (sbb): sync error I guess bug is not solved in 5.7 release then. Maybe 5.7 stable? Sigh. THERE IS NO BUG. As I

Re: help with bgpd error messages

On 2015-05-06, Marko Cupać marko.cu...@mimar.rs wrote: On Wed, 29 Apr 2015 11:02:09 +0200 Marko Cupać marko.cu...@mimar.rs wrote: On Tue, 28 Apr 2015 15:11:21 +0200 Claudio Jeker cje...@diehard.n-r-g.com wrote: The fatal in RDE: peer_up: bad state bug is fixed in 5.7 IIRC. Not sure if

Re: help with bgpd error messages

On Wed, May 06, 2015 at 03:10:44PM +0200, Henning Brauer wrote: * Marko Cupa?? marko.cu...@mimar.rs [2015-05-06 12:01]: I am on 5.7 release + errata patches now, and bgpd crashed again: May 6 10:06:07 bgp1 bgpd[11681]: neighbor 82.117.192.121 (sbb): sync error I guess bug is not

Re: help with bgpd error messages

On Tue, 28 Apr 2015 15:11:21 +0200 Claudio Jeker cje...@diehard.n-r-g.com wrote: The fatal in RDE: peer_up: bad state bug is fixed in 5.7 IIRC. Not sure if it was backported to 5.6. As a workaround you can disable the graceful restart capability to not trigger that code path. I was intending

Re: help with bgpd error messages

On Tue, Apr 28, 2015 at 11:28:31AM +0200, Marko Cupa?? wrote: Hi, I have a pair of OpenBSD 5.6 firewalls running releases happily for years (I think since 5.1). They are in CARP failover mode, running bgp sessions with upstrem providers and filtering traffic. Few days ago I had Internet

help with bgp error messages

Hi, I have a pair of OpenBSD 5.6 firewalls running releases happily for years (I think since 5.1). They are in CARP failover mode, running bgp sessions with upstrem providers and filtering traffic. Few days ago I had Internet outage (first in years), which appear to happen as a result of bgpd

help with bgpd error messages

Hi, I have a pair of OpenBSD 5.6 firewalls running releases happily for years (I think since 5.1). They are in CARP failover mode, running bgp sessions with upstrem providers and filtering traffic. Few days ago I had Internet outage (first in years), which appear to happen as a result of bgpd

relayd, how to customize error messages?

but that only modified the relayd address webserver and not the relayd error messages. Thank you. David

Error messages from bridge machines

I have 2 OpenBSD machines providing a bridge between 2 physical locations for a specific subnet. Last night, I got the following error messages on them: Oct 28 07:23:13 pb48 isakmpd[11605]: message_recv: invalid cookie(s) +0e113721bf798717 6b4e0004066c308e Oct 28 07:23:13 pb48 isakmpd[11605

Re: Error messages from bridge machines

On Wed, Oct 28, 2009 at 06:40:41AM -0500, stan wrote: I have 2 OpenBSD machines providing a bridge between 2 physical locations for a specific subnet. Last night, I got the following error messages on them: Oct 28 07:23:13 pb48 isakmpd[11605]: message_recv: invalid cookie(s

Realtek 8169 chip PCMCIA network card error messages

Hi! When I plug in a Linksys PCM1000 Gigabit Network card to my PCMCIA slot, I can see these messages in dmesg: re0 at cardbus0 dev 0 function 0 Realtek 8169 rev 0x10: RTL8169/8110SB (0x1000), irq 268505099, address 00:12:17:f0:c8:21 re0: PHY write failed re0: PHY write failed re0: PHY read

Re: error messages

On 5/16/05, Ryan Corder [EMAIL PROTECTED] wrote: On Mon, 2005-05-16 at 18:45 +0300, Kaj Mdkinen wrote: I connect to my firewall with putty. How can I get rid of messages like these from appearing in my ssh terminal session? check your /etc/syslog.conf to see if errors, etc are being

Re: error messages

On 2005-05-16 at 17:45:29 Kaj Mdkinen wrote: I connect to my firewall with putty. How can I get rid of messages like these from appearing in my ssh terminal session? These appeared twice a second so it is wery hard to work with the console. (It was obviously someone trying to get access to

Re: error messages

On Mon, 16 May 2005 18:45:29 +0300, Kaj Mdkinen [EMAIL PROTECTED] wrote: I connect to my firewall with putty. How can I get rid of messages like these from appearing in my ssh terminal session? These appeared twice a second so it is wery hard to work with the console. (It was obviously someone

Re: error messages

On Mon, 2005-05-16 at 22:34 +0200, Stefan Kell wrote: Hi, I would change the sshd-port from 22 to something different. This way the attack would run into nirvana. ListenAddress your.ip.address:new_port And of course disallow root access in sshd_conf. PermitRootLogin no ryanc