| |
VE2JOS > SYSOP 03.04.16 11:03l 67 Lines 3086 Bytes #999 (0) @ WW
BID : 470035VE2JOS
Read: GUEST
Subj: VE2JOS is back...
Path: IW8PGT<IZ3LSV<F1OYP<F4DUR<CX2SA<ZL2BAU<XE1FH<VE3UIL<VE2JOS
Sent: 160403/0952Z @:VE2JOS.#MTL.QC.CAN.NOAM #:46826 [Montreal] $:470035VE2JOS
From: VE2JOS@VE2JOS.#MTL.QC.CAN.NOAM
To : SYSOP@WW
Hi everyones,
Just to say that after 2 weeks of troubles, both JOSNOD:VE2JOS-1 and
JOSBBS:VE2JOS are finally back in service.
The cause of this outage arises from a kernel update from 3.10.17 to 4.4.6
that led to serious ax25 stack issue.
When anyone who has connected in either of the axip links, it won't be
able to connect again thereafter.
For example, typing "netstat -A ax25" normally give this:
* VE2JOS-1 ax0 LISTENING 000/000 0 0
VK2DOT-1 VE2JOS-1 ax1 ESTABLISHED 001/002 0 0
VE3UIL-7 VE2JOS-1 ax2 ESTABLISHED 000/002 0 0
KB0WSA-6 VE2JOS-1 ax2 ESTABLISHED 004/006 0 0
F1OYP-5 VE2JOS-1 ax2 ESTABLISHED 000/002 0 0
OK2PEN-5 VE2JOS-1 ax1 ESTABLISHED 003/004 0 0
* VE2JOS-0 ax3 LISTENING 000/000 0 0
* VE2JOS-0 bpq4 LISTENING 000/000 0 0
* VE2JOS-0 ax2 LISTENING 000/000 0 0
* VE2JOS-0 ax1 LISTENING 000/000 0 0
* VE2JOS-0 ax0 LISTENING 000/000 0 0
VE3CGR-8 VE2JOS-1 ax0 ESTABLISHED 000/000 0 0
* VE2JOS-1 bpq4 LISTENING 000/000 0 0
* VE2JOS-1 ax3 LISTENING 000/000 0 0
* VE2JOS-1 ax2 LISTENING 000/000 0 0
* VE2JOS-1 ax1 LISTENING 000/000 0 0
* VE2JOS-1 ax0 LISTENING 000/000 0 0
However, with a 4.x kernel, it will give me:
* VE2JOS-1 ax0 LISTENING 000/000 0 0
VK2DOT-1 VE2JOS-1 ax1 LISTENING 001/002 0 0
VE3UIL-7 VE2JOS-1 ax2 LISTENING 000/002 0 0
KB0WSA-6 VE2JOS-1 ax2 ESTABLISHED 004/006 0 0
F1OYP-5 VE2JOS-1 ax2 ESTABLISHED 000/002 0 0
OK2PEN-5 VE2JOS-1 ax1 ESTABLISHED 003/004 0 0
* VE2JOS-0 ax3 LISTENING 000/000 0 0
* VE2JOS-0 bpq4 LISTENING 000/000 0 0
* VE2JOS-0 ax2 LISTENING 000/000 0 0
* VE2JOS-0 ax1 LISTENING 000/000 0 0
* VE2JOS-0 ax0 LISTENING 000/000 0 0
VE3CGR-8 VE2JOS-1 ax0 LISTENING 000/000 0 0
* VE2JOS-1 bpq4 LISTENING 000/000 0 0
* VE2JOS-1 ax3 LISTENING 000/000 0 0
* VE2JOS-1 ax2 LISTENING 000/000 0 0
* VE2JOS-1 ax1 LISTENING 000/000 0 0
* VE2JOS-1 ax0 LISTENING 000/000 0 0
In this example, VK2DOT-1, VE3UIL-7 and VE3CGR-8 have disconnected and
WON'T be able to connect again until that I stop all ax25 daemons, unload
all ax25 related modules and reload all ax25 modules and daemons again to
permit them to connect, only ONCE again!!!
The remedy: downgrade the kernel from 4.4.6 to 3.18.29.
In one word: DON'T mix ax25 and kernel version 4 or higher, at least don't
try that on a production system.
73 all de Jose, VE2JOS................
Read previous mail | Read next mail
| |
