Jump to content

Red Brick not booting


rwblinn

Recommended Posts

Hi,

 

after connecting my (new) red brick via USB to a windows PC and configuring using the Brick Viewer. I rebooted the brick BUT ...the Green Light is ON (Linux bootmodus) but not blinking (Linux ready). Can also not connect via the Brick Viewer. The Brick has a wlan adapter and is reachable using ping.

 

Any hints?

Link zu diesem Kommentar
Share on other sites

Hi,

 

pls find the logs.

In the mean time:

* connected a master brick with several bricklets, a monitor with keyboard and mouse.

* Checked using lxterminal if brickd was running > is not.

* Started the brickd using sudo brickd.

* Brickv now shows the Red Brick but not the extensions.

* Did also a sudo apt-get update and upgrade plus reboot > but after reboot brickd is not running.

* Rebooted again > brickd not running > opened lxterminal > started brickd using sudo brickd > started brickv > connected via ipaddress > the masterbrick and connected UIDs are found (red_stack.c:506 SPI stack slave discovery done. found 1 slave with 4 UIDs)

* So, the question is why brickd stops and can not find the slaves during boot.

 

brickd.log

2014-12-29 17:30:26.604795 <I> <main_linux.c:275> Brick Daemon 2.2.0+redbrick started (daemonized)

2014-12-29 17:30:28.222705 <I> <red_extension.c:482> Could not find Extension at position 0

2014-12-29 17:30:28.223231 <I> <red_extension.c:482> Could not find Extension at position 1

2014-12-29 17:30:28.227047 <I> <redapid.c:306> Connected to RED Brick API Daemon

2014-12-29 17:30:28.734749 <I> <red_stack.c:506> SPI stack slave discovery done. Found 0 slave(s) with 0 UID(s) in total

2014-12-29 17:35:01.536539 <I> <red_stack.c:526> Starting reinitialization of SPI slaves

2014-12-29 17:35:03.586592 <I> <red_stack.c:506> SPI stack slave discovery done. Found 0 slave(s) with 0 UID(s) in total

 

redapid.log

2014-12-29 17:30:26.418443 <I> <main.c:309> RED Brick API Daemon 2.0.0 started (daemonized) on 1.3 (full) image

2014-12-29 17:30:28.226844 <I> <network.c:97> Brick Daemon connected

2014-12-29 17:42:15.375909 <I> <main.c:309> RED Brick API Daemon 2.0.0 started (daemonized) on 1.3 (full) image

2014-12-29 17:42:17.184630 <I> <network.c:97> Brick Daemon connected

2014-12-29 17:56:14.922549 <I> <main.c:309> RED Brick API Daemon 2.0.0 started (daemonized) on 1.3 (full) image

2014-12-29 17:56:16.734145 <I> <network.c:97> Brick Daemon connected

2014-12-29 17:57:15.531784 <I> <main.c:309> RED Brick API Daemon 2.0.0 started (daemonized) on 1.3 (full) image

2014-12-29 17:57:17.344387 <I> <network.c:97> Brick Daemon connected

2014-12-29 17:58:15.805319 <I> <main.c:309> RED Brick API Daemon 2.0.0 started (daemonized) on 1.3 (full) image

2014-12-29 17:58:18.382527 <I> <network.c:97> Brick Daemon connected

2015-01-03 15:16:23.068630 <I> <brickd.c:45> Brick Daemon disconnected by peer

2015-01-03 15:16:24.705548 <I> <signal.c:53> Received SIGTERM

2015-01-03 15:16:24.705875 <W> <session.c:165> Destroying session (id: 1) while it is still tracking 3 external reference(s) to the following objects (logged on debug level):

2015-01-03 15:16:24.706265 <I> <main.c:383> RED Brick API Daemon 2.0.0 stopped

2015-01-03 15:16:35.929036 <I> <main.c:309> RED Brick API Daemon 2.0.0 started (daemonized) on 1.3 (full) image

2015-01-03 15:16:37.740076 <I> <network.c:97> Brick Daemon connected

2015-01-03 16:04:03.548469 <W> <api.c:957> Unknown function ID 250

2015-01-03 16:06:16.246472 <I> <brickd.c:45> Brick Daemon disconnected by peer

2015-01-03 16:06:18.928020 <I> <network.c:97> Brick Daemon connected

2015-01-03 16:06:19.650473 <W> <api.c:957> Unknown function ID 250

2015-01-03 16:07:21.713381 <I> <brickd.c:45> Brick Daemon disconnected by peer

2015-01-03 16:07:24.408626 <I> <network.c:97> Brick Daemon connected

2015-01-03 16:07:25.588723 <W> <api.c:957> Unknown function ID 250

2015-01-03 16:07:56.620711 <W> <api.c:957> Unknown function ID 250

2015-01-03 16:10:14.047589 <I> <main.c:309> RED Brick API Daemon 2.0.0 started (daemonized) on 1.3 (full) image

2015-01-03 16:12:14.093732 <I> <main.c:309> RED Brick API Daemon 2.0.0 started (daemonized) on 1.3 (full) image

2015-01-03 16:21:15.155989 <I> <main.c:309> RED Brick API Daemon 2.0.0 started (daemonized) on 1.3 (full) image

2015-01-03 16:21:14.097470 <I> <main.c:309> RED Brick API Daemon 2.0.0 started (daemonized) on 1.3 (full) image

2015-01-03 16:30:15.359022 <I> <main.c:309> RED Brick API Daemon 2.0.0 started (daemonized) on 1.3 (full) image

2015-01-03 16:30:15.524451 <I> <main.c:309> RED Brick API Daemon 2.0.0 started (daemonized) on 1.3 (full) image

2015-01-03 17:02:14.505632 <I> <main.c:309> RED Brick API Daemon 2.0.0 started (daemonized) on 1.3 (full) image

2015-01-03 17:08:14.474640 <I> <main.c:309> RED Brick API Daemon 2.0.0 started (daemonized) on 1.3 (full) image

2015-01-03 17:08:14.849923 <I> <main.c:309> RED Brick API Daemon 2.0.0 started (daemonized) on 1.3 (full) image

2015-01-03 17:17:15.552346 <I> <main.c:309> RED Brick API Daemon 2.0.0 started (daemonized) on 1.3 (full) image

2015-01-03 17:26:57.576512 <I> <signal.c:53> Received SIGTERM

2015-01-03 17:26:57.577033 <I> <main.c:383> RED Brick API Daemon 2.0.0 stopped

2015-01-03 17:27:11.858495 <I> <main.c:309> RED Brick API Daemon 2.0.0 started (daemonized) on 1.3 (full) image

2015-01-03 17:30:47.040953 <I> <network.c:97> Brick Daemon connected

2015-01-03 17:33:32.567326 <I> <brickd.c:45> Brick Daemon disconnected by peer

2015-01-03 17:33:35.270745 <I> <network.c:97> Brick Daemon connected

2015-01-03 17:35:27.202084 <I> <brickd.c:45> Brick Daemon disconnected by peer

2015-01-03 17:35:28.597477 <I> <signal.c:53> Received SIGTERM

2015-01-03 17:35:28.597813 <W> <session.c:165> Destroying session (id: 3) while it is still tracking 16 external reference(s) to the following objects (logged on debug level):

2015-01-03 17:35:28.598384 <I> <main.c:383> RED Brick API Daemon 2.0.0 stopped

2015-01-03 17:35:41.576397 <I> <main.c:309> RED Brick API Daemon 2.0.0 started (daemonized) on 1.3 (full) image

2015-01-03 17:39:25.524075 <I> <network.c:97> Brick Daemon connected

Link zu diesem Kommentar
Share on other sites

Hi,

 

deleted the files and rebooted. Logs below. Seems an issue with server socket.

 

SOLVED: Actions taken: started brickd > started brickv > in settings brick daemon found the listen address 192.168.0.24 > changed to 0.0.0.0 > saved > rebooted the red brick > brickd running.

 

Thanks for your help

 

BRICKD

2015-01-04 17:53:52.471385 <I> <main_linux.c:275> Brick Daemon 2.2.0+redbrick started (daemonized)

2015-01-04 17:53:52.484484 <E> <network.c:202> Could not bind IPv4 server socket to '192.168.0.24' on port 4223: EADDRNOTAVAIL (99)

2015-01-04 17:53:52.484689 <E> <network.c:322> Could not open any socket to listen to

2015-01-04 17:53:52.485051 <I> <main_linux.c:392> Brick Daemon 2.2.0+redbrick stopped

REDAPI

2015-01-04 17:53:52.151358 <I> <main.c:309> RED Brick API Daemon 2.0.0 started (daemonized) on 1.3 (full) image

Link zu diesem Kommentar
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Gast
Reply to this topic...

×   Du hast formatierten Text eingefügt.   Formatierung jetzt entfernen

  Only 75 emoji are allowed.

×   Dein Link wurde automatisch eingebettet.   Einbetten rückgängig machen und als Link darstellen

×   Dein vorheriger Inhalt wurde wiederhergestellt.   Clear editor

×   Du kannst Bilder nicht direkt einfügen. Lade Bilder hoch oder lade sie von einer URL.

×
×
  • Neu erstellen...