Hold timer expired: difference between Received/Error
Quick question: what's the difference between 2011-04-29 18:24:36 <RMT> XXXX: Received: Hold timer expired 2011-04-30 00:05:42 <RMT> YYYY: Error: Hold timer expired We are running BIRD 1.2.5 ready. TIA and best regards, Arnold -- Arnold Nipper / nIPper consulting, Sandhausen, Germany email: arnold@nipper.de phone: +49 6224 9259 299 mobile: +49 152 53717690 fax: +49 6224 9259 333
Arnold, I could be wrong, but the most logical explanation would be:
2011-04-29 18:24:36 <RMT> XXXX: Received: Hold timer expired
Notification received, hold timer expired (error code 3.4, as per RFC1771).
2011-04-30 00:05:42 <RMT> YYYY: Error: Hold timer expired
Hold timer expired locally. Presumably a notification would be generated and sent to the remote peer before session tear-down. Is that not the case? Matthew Walster
Matthew, on 29.06.2011 01:59 Matthew Walster wrote:
I could be wrong, but the most logical explanation would be:
2011-04-29 18:24:36 <RMT> XXXX: Received: Hold timer expired
Notification received, hold timer expired (error code 3.4, as per RFC1771).
2011-04-30 00:05:42 <RMT> YYYY: Error: Hold timer expired
Hold timer expired locally. Presumably a notification would be generated and sent to the remote peer before session tear-down.
Is that not the case?
Would make sense. Otoh iirc <RMT> means that the message is received from the ReMoTe peer. I may be wrong. Arnold -- Arnold Nipper / nIPper consulting, Sandhausen, Germany email: arnold@nipper.de phone: +49 6224 9259 299 mobile: +49 152 53717690 fax: +49 6224 9259 333
On Wed, Jun 29, 2011 at 12:59:56AM +0100, Matthew Walster wrote:
Arnold,
I could be wrong, but the most logical explanation would be:
2011-04-29 18:24:36 <RMT> XXXX: Received: Hold timer expired
Notification received, hold timer expired (error code 3.4, as per RFC1771).
2011-04-30 00:05:42 <RMT> YYYY: Error: Hold timer expired
Hold timer expired locally. Presumably a notification would be generated and sent to the remote peer before session tear-down.
Yes, exactly that. -- Elen sila lumenn' omentielvo Ondrej 'SanTiago' Zajicek (email: santiago@crfreenet.org) OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net) "To err is human -- to blame it on a computer is even more so."
on 30.06.2011 08:14 Ondrej Zajicek wrote:
On Wed, Jun 29, 2011 at 12:59:56AM +0100, Matthew Walster wrote:
Arnold,
I could be wrong, but the most logical explanation would be:
2011-04-29 18:24:36 <RMT> XXXX: Received: Hold timer expired
Notification received, hold timer expired (error code 3.4, as per RFC1771).
2011-04-30 00:05:42 <RMT> YYYY: Error: Hold timer expired
Hold timer expired locally. Presumably a notification would be generated and sent to the remote peer before session tear-down.
Yes, exactly that.
Thanks ... and what does "<RMT>" stand for? When analysing the log I see <INFO> <RMT> <TRACE> <WARN> flags. All but "RMT" at least have an intuitive meaning to me. Arnold -- Arnold Nipper / nIPper consulting, Sandhausen, Germany email: arnold@nipper.de phone: +49 6224 9259 299 mobile: +49 152 53717690 fax: +49 6224 9259 333
On Thu, Jun 30, 2011 at 02:25:20PM +0200, Arnold Nipper wrote:
Yes, exactly that.
Thanks ... and what does "<RMT>" stand for? When analysing the log I see
flags. All but "RMT" at least have an intuitive meaning to me.
You are right:
Otoh iirc <RMT> means that the message is received from the ReMoTe peer
-- Elen sila lumenn' omentielvo Ondrej 'SanTiago' Zajicek (email: santiago@crfreenet.org) OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net) "To err is human -- to blame it on a computer is even more so."
on 30.06.2011 21:06 Ondrej Zajicek wrote:
On Thu, Jun 30, 2011 at 02:25:20PM +0200, Arnold Nipper wrote:
Yes, exactly that.
Thanks ... and what does "<RMT>" stand for? When analysing the log I see
flags. All but "RMT" at least have an intuitive meaning to me.
You are right:
Otoh iirc <RMT> means that the message is received from the ReMoTe peer
Aren't you contradicting yourself? On one hand a log message like 2011-04-30 00:05:42 <RMT> YYYY: Error: Hold timer expired does indicate ("<RMT>" flag) that it is received from the remote peer. On the other hand you say it means that the hold timer expired locally. Presumably a notification would be generated and sent to the remote peer before session tear-down. That does at least not make sense to me. Arnold -- Arnold Nipper / nIPper consulting, Sandhausen, Germany email: arnold@nipper.de phone: +49 6224 9259 299 mobile: +49 152 53717690 fax: +49 6224 9259 333
On Fri, Jul 01, 2011 at 04:01:19AM +0200, Arnold Nipper wrote:
on 30.06.2011 21:06 Ondrej Zajicek wrote:
On Thu, Jun 30, 2011 at 02:25:20PM +0200, Arnold Nipper wrote:
Yes, exactly that.
Thanks ... and what does "<RMT>" stand for? When analysing the log I see
flags. All but "RMT" at least have an intuitive meaning to me.
You are right:
Otoh iirc <RMT> means that the message is received from the ReMoTe peer
Aren't you contradicting yourself?
I didn't noticed that 'Error: Hold timer expired' also uses '<RMT>'. This is probably a bug, perhaps there should be '<ERR>'. -- Elen sila lumenn' omentielvo Ondrej 'SanTiago' Zajicek (email: santiago@crfreenet.org) OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net) "To err is human -- to blame it on a computer is even more so."
on 01.07.2011 12:14 Ondrej Zajicek wrote:
On Fri, Jul 01, 2011 at 04:01:19AM +0200, Arnold Nipper wrote:
on 30.06.2011 21:06 Ondrej Zajicek wrote:
On Thu, Jun 30, 2011 at 02:25:20PM +0200, Arnold Nipper wrote:
Yes, exactly that.
Thanks ... and what does "<RMT>" stand for? When analysing the log I see
flags. All but "RMT" at least have an intuitive meaning to me.
You are right:
Otoh iirc <RMT> means that the message is received from the ReMoTe peer
Aren't you contradicting yourself?
I didn't noticed that 'Error: Hold timer expired' also uses '<RMT>'. This is probably a bug, perhaps there should be '<ERR>'.
Not too sure what would be appropriate. Imho it's not really an error, isn't it? '<WARN>' or '<INFO>' could also do. But I agree it shouldn't be '<RMT>' Arnold -- Arnold Nipper / nIPper consulting, Sandhausen, Germany email: arnold@nipper.de phone: +49 6224 9259 299 mobile: +49 152 53717690 fax: +49 6224 9259 333
participants (3)
-
Arnold Nipper -
Matthew Walster -
Ondrej Zajicek