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

appium contstantly restarting due to the inotify init failure #328

Closed
vdelendik opened this issue Jun 3, 2024 · 3 comments
Closed

appium contstantly restarting due to the inotify init failure #328

vdelendik opened this issue Jun 3, 2024 · 3 comments
Labels
bug Something isn't working
Milestone

Comments

@vdelendik
Copy link
Contributor

Couldn't initialize inotify.  Are you running Linux 2.6.13 or later, and was the
CONFIG_INOTIFY option enabled when your kernel was compiled?  If so,
something mysterious has gone wrong.  Please e-mail radu.voicilas@gmail.com
 and mention that you saw this message.
Exit status: 0
@vdelendik vdelendik added the bug Something isn't working label Jun 3, 2024
@vdelendik
Copy link
Contributor Author

it was fixed by increasing number of fs.inotify.max_user_instances on the Linux server itself. Going to add such recommendation in the documentation for mcloud-agent so moving ticket into the appropriate repo

@vdelendik vdelendik transferred this issue from zebrunner/appium Jun 3, 2024
@vdelendik vdelendik added this to the 2.7 milestone Jun 3, 2024
vdelendik added a commit that referenced this issue Jun 3, 2024
@vdelendik
Copy link
Contributor Author

documentation updated

@dhreben
Copy link
Contributor

dhreben commented Jun 4, 2024

Fixed

@dhreben dhreben moved this from Ready For QA to Done in Device Farm (MCloud) Jun 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Development

No branches or pull requests

2 participants