Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

error message reportyed on FR2 #101

Open
prcvlusr opened this issue May 6, 2019 · 0 comments
Open

error message reportyed on FR2 #101

prcvlusr opened this issue May 6, 2019 · 0 comments

Comments

@prcvlusr
Copy link
Collaborator

prcvlusr commented May 6, 2019

FR1 (no issue):
15:28:53,256 FR.App INFO - frameReceiver version 0.6.1 starting up
15:28:53,256 FR.Controller TRACE - FrameRecevierController constructor
15:28:53,258 FR.Controller INFO - No frame decoder loaded: type not specified
15:28:53,258 FR.Controller INFO - Shared frame buffer manager not configured as no frame decoder configured
15:28:53,258 FR.Controller INFO - RX thread not configured as frame decoder and/or buffer manager configured
15:28:53,259 FR.Controller INFO - Loading decoder plugin PercivalEmulatorFrameDecoder from /home/prcvlusr/percival/percival-detector/data/prefix/lib/libPercivalEmulatorFrameDecoder.so
15:28:53,260 FR.Controller INFO - Created PercivalEmulatorFrameDecoder frame decoder instance
15:28:53,260 FR.Controller TRACE - FrameReceiverController::run()

FR2:
15:28:53,430 FR.App INFO - frameReceiver version 0.6.1 starting up
15:28:53,431 FR.Controller TRACE - FrameRecevierController constructor
15:28:53,433 FR.Controller ERROR - Configuration error: Binding frame ready notification channel endpoint tcp://*:5001 failed: Address already in use
15:28:53,434 FR.Controller INFO - Loading decoder plugin PercivalEmulatorFrameDecoder from /home/prcvlusr/percival/percival-detector/data/prefix/lib/libPercivalEmulatorFrameDecoder.so
15:28:53,435 FR.Controller INFO - Created PercivalEmulatorFrameDecoder frame decoder instance
15:28:53,436 FR.Controller TRACE - FrameReceiverController::run()

that is puzzling, also because tcp://*:5001 has not to do with FR2
the images from FR2 are acquired correctly, though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant