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

system time change cause POPO__CHUNK_LOCKING_ERROR #2381

Closed
JasonWang-Slamtec opened this issue Dec 4, 2024 · 1 comment
Closed

system time change cause POPO__CHUNK_LOCKING_ERROR #2381

JasonWang-Slamtec opened this issue Dec 4, 2024 · 1 comment

Comments

@JasonWang-Slamtec
Copy link

Required information

Operating system:
E.g. Ubuntu 20.04 LTS

Compiler version:
E.g. GCC 9

Eclipse iceoryx version:
E.g. v2.0.3

Observed result or behaviour:
process A is publisher, process B is subscriber
when system time changed, A output following log and crashed:
../iceoryx-2.0.3/iceoryx_hoofs/source/posix_wrapper/mutex.cpp:68 { bool iox::posix::mutex::lock() -> pthread_mutex_lock } ::: [ 22 ] Invalid argument
2024-12-04 11:27:16.335 [ Error ]: ICEORYX error! POPO__CHUNK_LOCKING_ERROR
after A rebooted, B can no longer receive data, while roudi is printing following logs:
2024-12-04 11:40:45.528 [Warning]: Received Keepalive from unknown process B
Communication returned to normal after B was restarted,

i use following command to change time:
date 120411312024.15

@elBoberido
Copy link
Member

elBoberido commented Dec 4, 2024

This is a duplicate of #2193.

Unfortunately, this bug is not easy to fix. You can have a look at #2193 for workarounds.

We have an idea how to properly fix it, but it's nothing which is done in an afternoon and takes quite some time.

Most of the iceoryx developers shifted their focus towards iceoryx2, where this problem does not occur. Is iceoryx2 also an option for you?

Alternatively, the root README.md has a link to commercial support for iceoryx in case the workarounds do not work for you and you cannot switch to iceoryx2.

To keep the technical discussion for this bug at a central place (#2193), I'll close this issue.

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

2 participants