Our ACID box crashed this evening; could not ssh into it, and green lights
on URIs not blinking. Rebooted after front panel shutdown, and the URI on
node 27178 blinked real slow, and audio out of the radio was marginally
there and choppy. Performed this twice with the same results then rebooted
via ssh. The repeater is acting normal now, but I'm wondering what might be
happening, and looking to not have a repeat performance.
Below are the last few messages recorded after reboot. This pattern was the
same for all three reboots. Here are my questions.
Why would chan_usbradio.c assign USB device 4-1 (nothing there) to usb27179?
Is the "possibly stuck USB read channel" a timing test? This seemed to pass
shortly after. The stuck channel was the one that was blinking slowly and
not responding properly to the radio.
Thanks,
Bob
kk6ecm
[Oct 28 18:51:46] NOTICE[2829] app_rpt.c: Normal Repeater Init 27178
[Oct 28 18:51:46] NOTICE[2829] app_rpt.c: Normal Repeater Init 27179
[Oct 28 18:51:46] NOTICE[2839] chan_usbradio.c: Assigned USB device 4-1 to
usbradio channel usb27179
[Oct 28 18:51:46] WARNING[2838] chan_usbradio.c: Loaded parameters from
usbradio_tune_usb27178.conf for device usb27178 .
[Oct 28 18:51:46] WARNING[2839] chan_usbradio.c: Loaded parameters from
usbradio_tune_usb27179.conf for device usb27179 .
[Oct 28 18:51:46] WARNING[2836] chan_usbradio.c: Possibly stuck USB read
channel. [usb27178]
[Oct 28 18:51:46] WARNING[2836] chan_usbradio.c: Nope, USB read channel
[usb27178] wasn't stuck after all.
Our ACID box crashed this evening; could not ssh into it, and green lights
on URIs not blinking. Rebooted after front panel shutdown, and the URI on
node 27178 blinked real slow, and audio out of the radio was marginally
there and choppy. Performed this twice with the same results then rebooted
via ssh. The repeater is acting normal now, but I'm wondering what might
be
happening, and looking to not have a repeat performance.
Below are the last few messages recorded after reboot. This pattern was
the
same for all three reboots. Here are my questions.
Why would chan_usbradio.c assign USB device 4-1 (nothing there) to
usb27179?
Is the "possibly stuck USB read channel" a timing test? This seemed to
pass
shortly after. The stuck channel was the one that was blinking slowly and
not responding properly to the radio.
Thanks,
Bob
kk6ecm
[Oct 28 18:51:46] NOTICE[2829] app_rpt.c: Normal Repeater Init 27178
[Oct 28 18:51:46] NOTICE[2829] app_rpt.c: Normal Repeater Init 27179
[Oct 28 18:51:46] NOTICE[2839] chan_usbradio.c: Assigned USB device 4-1 to
usbradio channel usb27179
[Oct 28 18:51:46] WARNING[2838] chan_usbradio.c: Loaded parameters from
usbradio_tune_usb27178.conf for device usb27178 .
[Oct 28 18:51:46] WARNING[2839] chan_usbradio.c: Loaded parameters from
usbradio_tune_usb27179.conf for device usb27179 .
[Oct 28 18:51:46] WARNING[2836] chan_usbradio.c: Possibly stuck USB read
channel. [usb27178]
[Oct 28 18:51:46] WARNING[2836] chan_usbradio.c: Nope, USB read channel
[usb27178] wasn't stuck after all.
To unsubscribe from this list please visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down
to the bottom of the page. Enter your email address and press the
"Unsubscribe or edit options button"
You do not need a password to unsubscribe, you can do it via email
confirmation. If you have trouble unsubscribing, please send a message to
the list detailing the problem.
The “Possibly stuck” thing is pretty normal. After I realized that it was
pretty much normal behavior, I considered changing the code not to
output that, but I kept it because it’s harmless and sorta humorous.
Our ACID box crashed this evening; could not ssh into it, and green lights
on URIs not blinking. Rebooted after front panel shutdown, and the URI on
node 27178 blinked real slow, and audio out of the radio was marginally
there and choppy. Performed this twice with the same results then rebooted
via ssh. The repeater is acting normal now, but I’m wondering what might be
happening, and looking to not have a repeat performance.
Below are the last few messages recorded after reboot. This pattern was the
same for all three reboots. Here are my questions.
Why would chan_usbradio.c assign USB device 4-1 (nothing there) to usb27179?
Is the “possibly stuck USB read channel” a timing test? This seemed to pass
shortly after. The stuck channel was the one that was blinking slowly and
not responding properly to the radio.
Thanks,
Bob
kk6ecm
[Oct 28 18:51:46] NOTICE[2829] app_rpt.c: Normal Repeater Init 27178
[Oct 28 18:51:46] NOTICE[2829] app_rpt.c: Normal Repeater Init 27179
[Oct 28 18:51:46] NOTICE[2839] chan_usbradio.c: Assigned USB device 4-1 to
usbradio channel usb27179
[Oct 28 18:51:46] WARNING[2838] chan_usbradio.c: Loaded parameters from
usbradio_tune_usb27178.conf for device usb27178 .
[Oct 28 18:51:46] WARNING[2839] chan_usbradio.c: Loaded parameters from
usbradio_tune_usb27179.conf for device usb27179 .
[Oct 28 18:51:46] WARNING[2836] chan_usbradio.c: Possibly stuck USB read
channel. [usb27178]
[Oct 28 18:51:46] WARNING[2836] chan_usbradio.c: Nope, USB read channel
[usb27178] wasn’t stuck after all.
To unsubscribe from this list please visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the “Unsubscribe or edit options button”
You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.
` Also, there is a rash of motherboards floating around out there
with bad capacitors on them. Look for puffed up or even open and
spewing out contents. Mostly on Dell and Hewlett Packard boards,
but they were distributed everywhere, and even wound up in
Motorola Spectra radios. Just changed 12 of them on a Dell Optiplex
GX-280 motherboard last week. Node was working fine until it lost
power, then would not boot. Works fine with new caps.
N5ZUA
`
···
On 10/28/2015 11:07 PM, Jim Duuuude
wrote:
The "Possibly stuck" thing is pretty normal. After
I realized that it was
pretty much normal behavior, I considered changing the code not
to
output that, but I kept it because it's harmless and sorta
humorous.
Jim
> From: > To: > Date: Wed, 28 Oct 2015 19:49:34 -0700
Subject: [App_rpt-users] ACID CentOS Crash - Looking for
the cause
Our ACID box crashed this evening; could not ssh into it,
and green lights
on URIs not blinking. Rebooted after front panel
shutdown, and the URI on
node 27178 blinked real slow, and audio out of the radio
was marginally
there and choppy. Performed this twice with the same
results then rebooted
via ssh. The repeater is acting normal now, but I’m
wondering what might be
happening, and looking to not have a repeat performance.
Below are the last few messages recorded after reboot.
This pattern was the
same for all three reboots. Here are my questions.
Why would chan_usbradio.c assign USB device 4-1 (nothing
there) to usb27179?
Is the “possibly stuck USB read channel” a timing test?
This seemed to pass
shortly after. The stuck channel was the one that was
blinking slowly and
not responding properly to the radio.
Thanks,
Bob
kk6ecm
[Oct 28 18:51:46] NOTICE[2829] app_rpt.c: Normal Repeater
Init 27178 > [Oct 28 18:51:46] NOTICE[2829] app_rpt.c: Normal Repeater
Init 27179 > [Oct 28 18:51:46] NOTICE[2839] chan_usbradio.c: Assigned
USB device 4-1 to
usbradio channel usb27179
[Oct 28 18:51:46] WARNING[2838] chan_usbradio.c: Loaded
parameters from
usbradio_tune_usb27178.conf for device usb27178 .
[Oct 28 18:51:46] WARNING[2839] chan_usbradio.c: Loaded
parameters from
usbradio_tune_usb27179.conf for device usb27179 .
[Oct 28 18:51:46] WARNING[2836] chan_usbradio.c: Possibly
stuck USB read
channel. [usb27178]
[Oct 28 18:51:46] WARNING[2836] chan_usbradio.c: Nope,
USB read channel
[usb27178] wasn’t stuck after all.
App_rpt-users mailing list
To unsubscribe from this list please visit
and
scroll down to the bottom of the page. Enter your email
address and press the “Unsubscribe or edit options button”
You do not need a password to unsubscribe, you can do it
via email confirmation. If you have trouble unsubscribing,
please send a message to the list detailing the problem.
_______________________________________________
App_rpt-users mailing list
To unsubscribe from this list please visit and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button"
You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.
Also do a check of the hard drive, see if something is messed up on it -- like it is going south. I've had *nix boxes do some strange stuff before when a hard drive starts to die and times out on reads, etc.
Stacy
KG7QIN
···
On 10/28/2015 07:49 PM, kk6ecm wrote:
Our ACID box crashed this evening; could not ssh into it, and green lights
on URIs not blinking. Rebooted after front panel shutdown, and the URI on
node 27178 blinked real slow, and audio out of the radio was marginally
there and choppy. Performed this twice with the same results then rebooted
via ssh. The repeater is acting normal now, but I'm wondering what might be
happening, and looking to not have a repeat performance.
Below are the last few messages recorded after reboot. This pattern was the
same for all three reboots. Here are my questions.
Why would chan_usbradio.c assign USB device 4-1 (nothing there) to usb27179?
Is the "possibly stuck USB read channel" a timing test? This seemed to pass
shortly after. The stuck channel was the one that was blinking slowly and
not responding properly to the radio.
Thanks,
Bob
kk6ecm
[Oct 28 18:51:46] NOTICE[2829] app_rpt.c: Normal Repeater Init 27178
[Oct 28 18:51:46] NOTICE[2829] app_rpt.c: Normal Repeater Init 27179
[Oct 28 18:51:46] NOTICE[2839] chan_usbradio.c: Assigned USB device 4-1 to
usbradio channel usb27179
[Oct 28 18:51:46] WARNING[2838] chan_usbradio.c: Loaded parameters from
usbradio_tune_usb27178.conf for device usb27178 .
[Oct 28 18:51:46] WARNING[2839] chan_usbradio.c: Loaded parameters from
usbradio_tune_usb27179.conf for device usb27179 .
[Oct 28 18:51:46] WARNING[2836] chan_usbradio.c: Possibly stuck USB read
channel. [usb27178]
[Oct 28 18:51:46] WARNING[2836] chan_usbradio.c: Nope, USB read channel
[usb27178] wasn't stuck after all.
To unsubscribe from this list please visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button"
You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.