Re,
On 14.01.19 18:40, Theo de Raadt wrote:
> We accept reasonable bug reports from systems with a few changes. You do NOT
> have
> a few changes, you have a huge pile of them, and therefore you are
> 'responsible
> for all the pieces'.
...
> Almost assuredly you are being burned by your own ch
On 14.1.2019. 16:25, Hrvoje Popovski wrote:
> On 14.1.2019. 10:02, Marco Prause wrote:
>> splassert: bstp_notify_rtage: want 2 have 0
>> splassert: bstp_notify_rtage: want 2 have 0
>> splassert: bstp_notify_rtage: want 2 have 0
>> splassert: bstp_notify_rtage: want 2 have 0
>> splassert: bstp_notif
On Mon, 14 Jan 2019 18:27:56 +0100, Marco Prause
wrote:
>
>
> Am 14. Januar 2019 16:40:48 MEZ schrieb Theo de Raadt :
> >It sure looks like you have a pile of your own changes which are highly
> >unconventional,
> >and you are very far away from a stock OpenBSD configuration.
>
> Well, that's
Marco Prause wrote:
> Am 14. Januar 2019 16:40:48 MEZ schrieb Theo de Raadt :
> >It sure looks like you have a pile of your own changes which are highly
> >unconventional,
> >and you are very far away from a stock OpenBSD configuration.
>
> Well, that's right so far, because I have decided to us
Am 14. Januar 2019 16:40:48 MEZ schrieb Theo de Raadt :
>It sure looks like you have a pile of your own changes which are highly
>unconventional,
>and you are very far away from a stock OpenBSD configuration.
Well, that's right so far, because I have decided to use the tool resflash to
create
It sure looks like you have a pile of your own changes which are highly
unconventional,
and you are very far away from a stock OpenBSD configuration.
Having made those decisions, you are responsible for your own issues.
Sorry.
> Hi Stuart,
>
> thanks for having a look at this.
>
>
> > Is it
On 14.1.2019. 10:02, Marco Prause wrote:
> splassert: bstp_notify_rtage: want 2 have 0
> splassert: bstp_notify_rtage: want 2 have 0
> splassert: bstp_notify_rtage: want 2 have 0
> splassert: bstp_notify_rtage: want 2 have 0
> splassert: bstp_notify_rtage: want 2 have 0
> splassert: bstp_notify_rta
Just a small follow-up to my previous email:
I've just had a look at the hardware, that causes the problem before
I've exchanged it with the new one, that now also produce the problem.
This server seems to have the same hardware-setup then the server1, I
mentioned the email before, which is not f
Hi Stuart,
thanks for having a look at this.
> Is it the same or different hardware type and BIOS version for the
> working and hanging machines? (maybe diff the two dmesgs)
>
> Same or different filesystem mount options? (Are you using softdep?)
it's (nearly) the same hardware.
But thanks to
On 2019-01-14, Marco Prause wrote:
> after an initial boot, everything is working fine for round about 4 hours.
>
> After 4 hours, it is not possible to login into the backup/secondary
> openbsd-server via ssh or even via serial console, but it seems to still
> forward traffic correctly. Also the
Hi all @misc,
1st things 1st : sorry for my long description, but :
after upgrading from 6.3-stable to 6.4-stable (and later also current)
in our integration stage, I've met a strange problem.
I run OpenBSD in a hub-and-spoke vpn architecture in round about 14
distributed datacenters.
6.3-stabl
11 matches
Mail list logo
