Author Topic: Remoteswitch über redbrick zerlegt den brick daemon  (Read 866 times)

Ming

  • Newbie
  • *
  • Posts: 3
    • View Profile
Remoteswitch über redbrick zerlegt den brick daemon
« on: January 14, 2017, 23:03:50 »
Moin,

ich habe ein Problem mit einem Remote Switch. Es fubnktioniert alles, wenn der Master direkt mit dem Rechner verbunden ist. Wird er über einen Red Brick angesprochen, bleibt der Brickviewer hängen. Das Problem haben schon mehrere User berichtet. Ich hab mal das Log des Brickdeamons angehängt. Der Daemon muß danach neu gestartet werden...

Was kann ich tun?

Ming

2017-01-14 22:42:54.893966 <I> <main_macosx.c:148> Brick Daemon 2.2.3 started (pid: 37784, daemonized: 1)
2017-01-14 22:42:54.938817 <I> <usb.c:191> Added USB device (bus: 253, device: 3) at index 0: RED Brick [2Fuoqp]
2017-01-14 22:44:16.335388 <W> <libusb:darwin_transfer_status> transfer error: device not responding (value = 0xe00002ed)
2017-01-14 22:44:16.335451 <W> <usb_transfer.c:116> Read transfer 0x7ff385810ce0 (0x7ff383f01568) returned with an error from RED Brick [2Fuoqp]: LIBUSB_TRANSFER_ERROR (1)
2017-01-14 22:44:16.335567 <E> <libusb:submit_bulk_transfer> bulk transfer failed (dir = In): pipe is stalled (code = 0xe000404f)
2017-01-14 22:44:16.335589 <E> <usb_transfer.c:281> Could not submit read transfer 0x7ff385810ce0 (0x7ff383f01568) to RED Brick [2Fuoqp]: LIBUSB_ERROR_PIPE (-9)
2017-01-14 22:44:16.347761 <I> <usb.c:388> Removing USB device (bus: 253, device: 3) at index 0: RED Brick [2Fuoqp]
2017-01-14 22:44:16.347828 <W> <libusb:darwin_abort_transfers> aborting all transactions on interface 0 pipe 1
2017-01-14 22:44:16.347859 <W> <usb_transfer.c:191> Could not cancel pending read transfer 0x7ff385810c00 (0x7ff383f012e8) for RED Brick [2Fuoqp]: LIBUSB_ERROR_NO_DEVICE (-4)
2017-01-14 22:44:16.347883 <W> <usb_transfer.c:227> Leaking pending read transfer 0x7ff385810c00 (0x7ff383f012e8) for RED Brick [2Fuoqp]
2017-01-14 22:44:16.347933 <W> <libusb:darwin_abort_transfers> aborting all transactions on interface 0 pipe 1
2017-01-14 22:44:16.347948 <W> <usb_transfer.c:191> Could not cancel pending read transfer 0x7ff385810c70 (0x7ff383f01428) for RED Brick [2Fuoqp]: LIBUSB_ERROR_NO_DEVICE (-4)
2017-01-14 22:44:16.347959 <W> <usb_transfer.c:227> Leaking pending read transfer 0x7ff385810c70 (0x7ff383f01428) for RED Brick [2Fuoqp]
2017-01-14 22:44:16.347977 <W> <libusb:darwin_abort_transfers> aborting all transactions on interface 0 pipe 1
2017-01-14 22:44:16.347987 <W> <usb_transfer.c:191> Could not cancel pending read transfer 0x7ff385810d50 (0x7ff383f016a8) for RED Brick [2Fuoqp]: LIBUSB_ERROR_NO_DEVICE (-4)
2017-01-14 22:44:16.347997 <W> <usb_transfer.c:227> Leaking pending read transfer 0x7ff385810d50 (0x7ff383f016a8) for RED Brick [2Fuoqp]
2017-01-14 22:44:16.348008 <W> <libusb:darwin_abort_transfers> aborting all transactions on interface 0 pipe 1
2017-01-14 22:44:16.348017 <W> <usb_transfer.c:191> Could not cancel pending read transfer 0x7ff385810dc0 (0x7ff383f017e8) for RED Brick [2Fuoqp]: LIBUSB_ERROR_NO_DEVICE (-4)
2017-01-14 22:44:16.348027 <W> <usb_transfer.c:227> Leaking pending read transfer 0x7ff385810dc0 (0x7ff383f017e8) for RED Brick [2Fuoqp]
2017-01-14 22:44:16.348037 <W> <libusb:darwin_abort_transfers> aborting all transactions on interface 0 pipe 1
2017-01-14 22:44:16.348046 <W> <usb_transfer.c:191> Could not cancel pending read transfer 0x7ff385810e30 (0x7ff383f01928) for RED Brick [2Fuoqp]: LIBUSB_ERROR_NO_DEVICE (-4)
2017-01-14 22:44:16.348056 <W> <usb_transfer.c:227> Leaking pending read transfer 0x7ff385810e30 (0x7ff383f01928) for RED Brick [2Fuoqp]
2017-01-14 22:44:16.348066 <W> <libusb:darwin_abort_transfers> aborting all transactions on interface 0 pipe 1
2017-01-14 22:44:16.348075 <W> <usb_transfer.c:191> Could not cancel pending read transfer 0x7ff385810ea0 (0x7ff383f01b38) for RED Brick [2Fuoqp]: LIBUSB_ERROR_NO_DEVICE (-4)
2017-01-14 22:44:16.348084 <W> <usb_transfer.c:227> Leaking pending read transfer 0x7ff385810ea0 (0x7ff383f01b38) for RED Brick [2Fuoqp]
2017-01-14 22:44:16.348095 <W> <libusb:darwin_abort_transfers> aborting all transactions on interface 0 pipe 1
2017-01-14 22:44:16.348104 <W> <usb_transfer.c:191> Could not cancel pending read transfer 0x7ff385810f10 (0x7ff383f01c78) for RED Brick [2Fuoqp]: LIBUSB_ERROR_NO_DEVICE (-4)
2017-01-14 22:44:16.349519 <W> <usb_transfer.c:227> Leaking pending read transfer 0x7ff385810f10 (0x7ff383f01c78) for RED Brick [2Fuoqp]
2017-01-14 22:44:16.349540 <W> <libusb:darwin_abort_transfers> aborting all transactions on interface 0 pipe 1
2017-01-14 22:44:16.349549 <W> <usb_transfer.c:191> Could not cancel pending read transfer 0x7ff385810f80 (0x7ff383f01db8) for RED Brick [2Fuoqp]: LIBUSB_ERROR_NO_DEVICE (-4)
2017-01-14 22:44:16.349559 <W> <usb_transfer.c:227> Leaking pending read transfer 0x7ff385810f80 (0x7ff383f01db8) for RED Brick [2Fuoqp]
2017-01-14 22:44:16.349569 <W> <libusb:darwin_abort_transfers> aborting all transactions on interface 0 pipe 1
2017-01-14 22:44:16.349578 <W> <usb_transfer.c:191> Could not cancel pending read transfer 0x7ff385810ff0 (0x7ff383f01ef8) for RED Brick [2Fuoqp]: LIBUSB_ERROR_NO_DEVICE (-4)
2017-01-14 22:44:16.349587 <W> <usb_transfer.c:227> Leaking pending read transfer 0x7ff385810ff0 (0x7ff383f01ef8) for RED Brick [2Fuoqp]
2017-01-14 22:44:16.349691 <W> <libusb:darwin_close> USBDeviceClose: no connection to an IOService

photron

  • Tinkerforge Staff
  • Administrator
  • Hero Member
  • *****
  • Posts: 2.471
    • View Profile
Re: Remoteswitch über redbrick zerlegt den brick daemon
« Reply #1 on: January 16, 2017, 17:26:30 »
Teste mal bitte diese Version.

Ming

  • Newbie
  • *
  • Posts: 3
    • View Profile
Re: Remoteswitch über redbrick zerlegt den brick daemon
« Reply #2 on: January 16, 2017, 20:29:04 »
Moin, das hat leider nicht geholfen. Aber ich habe folgendes beobachtet.

Setup: brickd und viewer auf Mac, jeweils neuste Version. Auf dem red brick läuft der daemon 2.2.2 wie vorinstalliert.

2017-01-16 20:22:23.701101 <I> <red_usb_gadget.c:140> Disconnected from RED Brick USB gadget
2017-01-16 20:22:28.838024 <I> <main_linux.c:281> Brick Daemon 2.2.2+redbrick started (pid: 6735, daemonized: 1)
2017-01-16 20:22:28.897408 <I> <usb.c:154> Added USB device (bus: 1, device: 5) at index 0: RED Brick [2Fuoqp]
2017-01-16 20:22:30.525431 <I> <red_extension.c:524> Could not find Extension at position 0
2017-01-16 20:22:30.525931 <I> <red_extension.c:524> Could not find Extension at position 1
2017-01-16 20:22:30.526311 <I> <network.c:373> Added new client (N: g_red_brick, T: file, H: 28, A: disabled)
2017-01-16 20:22:30.526379 <I> <red_usb_gadget.c:115> Connected to RED Brick USB gadget
2017-01-16 20:22:30.532292 <I> <redapid.c:309> Connected to RED Brick API Daemon
2017-01-16 20:22:31.282331 <I> <red_stack.c:531> SPI stack slave discovery done. Found 1 slave(s) with 2 UID(s) in total

Dann connecte ich den brickviewer auf meinem Mac:

2017-01-16 20:24:24.702712 <W> <network.c:269> Dropped 1 pending request(s) (uid: 2Fuoqp)
2017-01-16 20:24:24.705828 <W> <network.c:269> Dropped 1 pending request(s) (uid: 2Fuoqp)
2017-01-16 20:24:24.707427 <W> <network.c:269> Dropped 1 pending request(s) (uid: 2Fuoqp)
2017-01-16 20:24:24.709507 <W> <network.c:269> Dropped 1 pending request(s) (uid: 2Fuoqp)
2017-01-16 20:24:24.711443 <W> <network.c:269> Dropped 1 pending request(s) (uid: 2Fuoqp)
2017-01-16 20:24:24.716966 <W> <network.c:269> Dropped 1 pending request(s) (uid: 2Fuoqp)
2017-01-16 20:24:24.721605 <W> <network.c:269> Dropped 1 pending request(s) (uid: 2Fuoqp)
2017-01-16 20:24:24.723460 <W> <network.c:269> Dropped 1 pending request(s) (uid: 2Fuoqp)
2017-01-16 20:24:24.726523 <W> <network.c:269> Dropped 1 pending request(s) (uid: 2Fuoqp)
2017-01-16 20:24:24.728876 <W> <network.c:269> Dropped 1 pending request(s) (uid: 2Fuoqp)
2017-01-16 20:24:24.730586 <W> <network.c:269> Dropped 1 pending request(s) (uid: 2Fuoqp)
2017-01-16 20:24:24.735866 <W> <network.c:269> Dropped 1 pending request(s) (uid: 2Fuoqp)
2017-01-16 20:24:24.737744 <W> <network.c:269> Dropped 1 pending request(s) (uid: 2Fuoqp)
2017-01-16 20:24:24.739373 <W> <network.c:269> Dropped 1 pending request(s) (uid: 2Fuoqp)
2017-01-16 20:24:24.742309 <W> <network.c:269> Dropped 1 pending request(s) (uid: 2Fuoqp)

endlose wiederholungen, dann kommt:

2017-01-16 20:24:24.870223 <W> <network.c:541> Broadcasting response (U: 68y3Ww, L: 9, F: 5, S: 12, E: 0) because no client/zombie has a matching pending request
2017-01-16 20:24:24.871871 <W> <network.c:541> Broadcasting response (U: 68y3Ww, L: 9, F: 5, S: 12, E: 0) because no client/zombie has a matching pending request
2017-01-16 20:24:24.873485 <W> <network.c:269> Dropped 1 pending request(s) (uid: 2Fuoqp)
2017-01-16 20:24:24.875334 <W> <network.c:541> Broadcasting response (U: 68y3Ww, L: 9, F: 5, S: 12, E: 0) because no client/zombie has a matching pending request
2017-01-16 20:24:24.876981 <W> <network.c:541> Broadcasting response (U: 68y3Ww, L: 9, F: 5, S: 12, E: 0) because no client/zombie has a matching pending request
2017-01-16 20:24:24.878448 <W> <network.c:541> Broadcasting response (U: 68y3Ww, L: 9, F: 5, S: 12, E: 0) because no client/zombie has a matching pending request
2017-01-16 20:24:24.880187 <W> <network.c:541> Broadcasting response (U: 68y3Ww, L: 9, F: 5, S: 12, E: 0) because no client/zombie has a matching pending request
2017-01-16 20:24:24.881849 <W> <network.c:269> Dropped 1 pending request(s) (uid: 2Fuoqp)
2017-01-16 20:24:24.882660 <W> <network.c:541> Broadcasting response (U: 68y3Ww, L: 9, F: 5, S: 12, E: 0) because no client/zombie has a matching pending request
2017-01-16 20:24:24.883336 <W> <network.c:541> Broadcasting response (U: 68y3Ww, L: 9, F: 5, S: 12, E: 0) because no client/zombie has a matching pending request

......

dann kommt:

2017-01-16 20:25:27.483980 <W> <network.c:440> Pending requests list for client (N: g_red_brick, T: file, H: 28, A: disabled) is full, dropping 1 pending request(s)
2017-01-16 20:25:27.485280 <W> <writer.c:108> Write backlog for client (N: g_red_brick, T: file, H: 28, A: disabled) is full, dropping 1 queued response(s), 50384 +1 dropped in total
2017-01-16 20:25:27.485949 <W> <network.c:440> Pending requests list for client (N: g_red_brick, T: file, H: 28, A: disabled) is full, dropping 1 pending request(s)
2017-01-16 20:25:27.487165 <W> <writer.c:108> Write backlog for client (N: g_red_brick, T: file, H: 28, A: disabled) is full, dropping 1 queued response(s), 50385 +1 dropped in total
2017-01-16 20:25:27.488486 <W> <writer.c:108> Write backlog for client (N: g_red_brick, T: file, H: 28, A: disabled) is full, dropping 1 queued response(s), 50386 +1 dropped in total
2017-01-16 20:25:27.489602 <W> <network.c:440> Pending requests list for client (N: g_red_brick, T: file, H: 28, A: disabled) is full, dropping 1 pending request(s)
2017-01-16 20:25:27.491188 <W> <writer.c:108> Write backlog for client (N: g_red_brick, T: file, H: 28, A: disabled) is full, dropping 1 queued response(s), 50387 +1 dropped in total
2017-01-16 20:25:27.492118 <W> <writer.c:108> Write backlog for client (N: 192.168.188.24:53420, T: plain-socket, H: 30, A: disabled) is full, dropping 1 queued response(s), 50302 +1 dropped in total

das läuft dann endlos und schreibt mehrere megabytes pro minute logs.



Ming

  • Newbie
  • *
  • Posts: 3
    • View Profile
Re: Remoteswitch über redbrick zerlegt den brick daemon
« Reply #3 on: January 16, 2017, 21:11:23 »
Und was mir noch auffällt, auf dem redbrick zieht der brickd ezxtrem an der cpu:

 PID USER      PR  NI    VIRT    RES    SHR S %CPU %MEM     TIME+ COMMAND                                                                                                                       
 3343 root      20   0   18384    888    684 R 67.6  0.2   0:50.02 brickd   

Der red wurde frisch gebootet und tut nichts. Log:

2017-01-16 21:08:15.392507 <I> <usb.c:154> Added USB device (bus: 1, device: 5) at index 0: RED Brick [2Fuoqp]
2017-01-16 21:08:17.020580 <I> <red_extension.c:524> Could not find Extension at position 0
2017-01-16 21:08:17.022756 <I> <red_extension.c:524> Could not find Extension at position 1
2017-01-16 21:08:17.024284 <I> <network.c:373> Added new client (N: g_red_brick, T: file, H: 28, A: disabled)
2017-01-16 21:08:17.025226 <I> <red_usb_gadget.c:115> Connected to RED Brick USB gadget
2017-01-16 21:08:17.031719 <I> <redapid.c:309> Connected to RED Brick API Daemon
2017-01-16 21:08:18.037112 <I> <red_stack.c:531> SPI stack slave discovery done. Found 1 slave(s) with 2 UID(s) in total

photron

  • Tinkerforge Staff
  • Administrator
  • Hero Member
  • *****
  • Posts: 2.471
    • View Profile
Re: Remoteswitch über redbrick zerlegt den brick daemon
« Reply #4 on: January 17, 2017, 10:45:10 »
Okay, da ist irgend was grob faul :(

Wenn du sagst, dass die neue brickd Version für den Mac nicht geholfen hat, dann meinst du, dass brickd auf dem Mac immer noch diese Fehler aus deinem ersten Post ausgibt, abstürzt und dann von Hand neugestartet werden muss?

Ist UID 68y3Ww ein Master Brick, oder was für ein Brick ist das?

Ist IP Adresse 192.168.188.24 der Mac?

Kannst du dir auch mal die /var/log/redapid.log Datei auf dem RED Brick ansehen?