Welcome to Smart Home Forum by FIBARO
Dear Guest,
as you can notice parts of Smart Home Forum by FIBARO is not available for you. You have to register in order to view all content and post in our community. Don't worry! Registration is a simple free process that requires minimal information for you to sign up. Become a part of of Smart Home Forum by FIBARO by creating an account.
As a member you can:
- Start new topics and reply to others
- Follow topics and users to get email updates
- Get your own profile page and make new friends
- Send personal messages
- ... and learn a lot about our system!
Regards,
Smart Home Forum by FIBARO Team

Question
jin 0
I figured out that after some hours fibaro gateway become unresponsive.
searching the cause of the problem I discovered this:
top - 21:29:16 up 1 day, 12:53, 1 user, load average: 4.01, 2.35, 1.81
Tasks: 113 total, 5 running, 105 sleeping, 0 stopped, 3 zombie
Cpu(s): 87.8%us, 12.2%sy, 0.0%ni, 0.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Mem: 1023800k total, 367572k used, 656228k free, 45724k buffers
Swap: 249848k total, 0k used, 249848k free, 99812k cached
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
3466 www-data 20 0 42272 15m 5568 R 51 1.5 1:13.81 php
4086 www-data 20 0 42272 15m 5568 R 51 1.5 0:10.53 php
2974 www-data 20 0 42272 15m 5568 R 46 1.5 2:13.18 php
2236 www-data 20 0 44016 13m 3192 R 28 1.3 4:26.47 apache2
1232 mysql 20 0 139m 21m 6100 S 5 2.1 12:24.73 mysqld
13908 www-data 20 0 44532 13m 3192 S 5 1.4 4:21.11 apache2
root@fghc2:~# ps aux | grep php
www-data 2974 76.5 1.5 42272 15480 ? R 21:26 2:15 php /var/www/fibaro/advanced_scenes_check3.php 49
www-data 3466 70.2 1.5 42272 15480 ? R 21:27 1:15 php /var/www/fibaro/advanced_scenes_check3.php 49
www-data 4086 45.5 1.5 42272 15476 ? R 21:28 0:12 php /var/www/fibaro/advanced_scenes_check3.php 49
root@fghc2:~# strace -p 2974
Process 2974 attached - interrupt to quit
time(NULL) = 1332620935
time(NULL) = 1332620935
time(NULL) = 1332620935
time(NULL) = 1332620935
time(NULL) = 1332620935
time(NULL) = 1332620935
time(NULL) = 1332620935
time(NULL) = 1332620935
time(NULL) = 1332620935
time(NULL) = 1332620935
time(NULL) = 1332620935
time(NULL) = 1332620935
time(NULL) = 1332620935
time(NULL) = 1332620935
time(NULL) = 1332620935
time(NULL) = 1332620935
time(NULL) = 1332620935
time(NULL) = 1332620935
time(NULL) = 1332620935
time(NULL) = 1332620935
time(NULL) = 1332620935
time(NULL) = 1332620935
time(NULL) = 1332620935
time(NULL) = 1332620935
time(NULL) = 1332620935
time(NULL) = 1332620935
time(NULL) = 1332620935
time(NULL) = 1332620935
time(NULL) = 1332620935
time(NULL) = 1332620935
and so many many other lines..................
This bug is caused by a scene like the attached screenshot.
Moreover the problem is accentuated by overlap of the triggered scene (each time the motion sensor become "safe" the scene timer start). In a future release would be great if I can enable a check into scene programming to make certain scenes to "run only once at a time".
Let's me know if do you want major details.
Thank you very much for the support.
Best Regards.
PS. please put online a bug tracking system like Mantis BT to manage the bug reporting of Fibaro System, so these bug reports doesn't get lost into forum posts.
Please login or register to see this attachment.
5 answers to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.