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

Starting an application after RouDi was terminated floods the cmd line with error messages #654

Closed
elBoberido opened this issue Mar 29, 2021 · 0 comments · Fixed by #804 or #806
Closed
Assignees
Labels
bug Something isn't working
Milestone

Comments

@elBoberido
Copy link
Member

Required information

Operating system:
Ubuntu based

Compiler version:
all

Observed result or behaviour:
Wenn RouDi is terminated and therefore couldn't cleanup the unix domain socket and an application is started, the cmd line gets flooded with

../iceoryx/iceoryx_utils/source/posix_wrapper/unix_domain_socket.cpp:401 { iox::cxx::expected<iox::posix::IpcChannelError> iox::posix::UnixDomainSocket::initalizeSocket(iox::posix::IpcChannelMode) }  :::  [ 111 ]  Connection refused
No server for unix domain socket "/tmp/roudi"

Expected result or behaviour:
The application should gracefully handle the situation and wait till RouDi is started

Conditions where it occurred / Performed steps:
Open a terminal and start iox-roudi and run kill -9 [iox-roudi PID]. Now run ./iox-ex-subscriber and the cmd line get flooded with error messages

@elBoberido elBoberido added the bug Something isn't working label Mar 29, 2021
@elBoberido elBoberido added this to the Prio 2 milestone Mar 29, 2021
@elBoberido elBoberido added this to To do in v1.0 via automation Mar 29, 2021
@budrus budrus added this to To do in Sprints Apr 6, 2021
@budrus budrus removed this from To do in v1.0 Apr 15, 2021
@budrus budrus added this to To do in v2.x Apr 15, 2021
@mossmaurice mossmaurice moved this from To do to In progress in Sprints Apr 20, 2021
@mossmaurice mossmaurice moved this from In progress to To do in Sprints Apr 20, 2021
@budrus budrus moved this from To do to Current in Sprints May 17, 2021
@elBoberido elBoberido self-assigned this May 17, 2021
elBoberido added a commit to ApexAI/iceoryx that referenced this issue May 20, 2021
…socket

Signed-off-by: Mathias Kraus <mathias.kraus@apex.ai>
Sprints automation moved this from Current to Done May 20, 2021
v2.x automation moved this from To do to Done May 20, 2021
elBoberido added a commit that referenced this issue May 20, 2021
…there-is-an-outdated-socket

iox-#654 stop flooding output if there is an outdated socket
elBoberido added a commit to ApexAI/iceoryx that referenced this issue May 20, 2021
…socket

Signed-off-by: Mathias Kraus <mathias.kraus@apex.ai>
@elBoberido elBoberido linked a pull request May 21, 2021 that will close this issue
19 tasks
elBoberido added a commit to ApexAI/iceoryx that referenced this issue May 21, 2021
Signed-off-by: Mathias Kraus <mathias.kraus@apex.ai>
elBoberido added a commit to ApexAI/iceoryx that referenced this issue May 21, 2021
Signed-off-by: Mathias Kraus <mathias.kraus@apex.ai>
elBoberido added a commit to ApexAI/iceoryx that referenced this issue May 21, 2021
Signed-off-by: Mathias Kraus <mathias.kraus@apex.ai>
elBoberido added a commit that referenced this issue May 25, 2021
…there-is-an-outdated-socket-release-v1.0

backport of iox-#654, iox-#791, iox-#802 and iox-#808 to release branch
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
v2.x
Done
1 participant