IRC log of #cubox of Sun 20 Jul 2014. All times are in CEST < Back to index

14:20 quitte rabeeh: about the usom with intact fuses: do you think it will be enough to request that in the order notes field?
14:22 malte rabeeh has offtime till tuesday
14:24 quitte malte: okay thanks. I'll wait with the order until after the finals then, I guess.
14:24 malte yes
22:54 heap hi, can anybody take a look what those errors in dmesg logs are from? https://www.dropbox.com/s/elg8aodzr1kw2a2/dmesg_log
22:55 heap i have no swap, swappines is set to 60, its cuboxpro 2g ram
23:07 cbxbiker61 Process insync-portable , i have no idea what that is
23:29 heap cbxbiker61: just client / app , i mean why those processes are dying .. because doesnt have enought ram?
23:33 cbxbiker61 how long was the machine running before those errors?
23:34 cbxbiker61 it's probably a single program that has a bad memory leak
23:34 cbxbiker61 just run top for an extended period of time and see which program is eating your ram
23:35 cbxbiker61 very few programs that you would want to run on an arm chip would actually need 2G ram
23:40 heap cbxbiker61: 10 days
23:41 heap cbxbiker61: backuppc crashed few times too
23:41 cbxbiker61 yeah, almost for sure it's a memory leak you can identify with top
23:41 heap how with top?
23:41 heap free says: Mem: 1637 1598 38
23:42 cbxbiker61 top will show how much mem is allocated to a particular process, the problematic program will continue to grow until until the system runs out of memroy
23:42 heap if i take a look into htop this insync eating 40% of ram
23:43 heap is it possible to generate dump or something to be able to find out this leak?
23:45 cbxbiker61 if you have source code you could use valgrind to analyze the problem
23:46 cbxbiker61 otherwise what you may have to do is use systemd features to restart the program periodically
23:49 cbxbiker61 make sure your configuration files are ok...sometimes a whacky config file will cause a program to behave badly
23:56 heap cbxbiker61: ok thanks
23:56 heap so its not hw or os problem?
23:57 cbxbiker61 very unlikely, but yeah, run top and watch how that memory keeps growing and you'll know for sure