Project

General

Profile

Bug #13644

Out Of Swap Space Kills BT Sync

Added by Fran Mulvey over 4 years ago. Updated about 3 years ago.

Status:
Closed: User Config Issue
Priority:
No priority
Assignee:
Joshua Ruehlig
Category:
Middleware
Target version:
Seen in:
Severity:
New
Reason for Closing:
Reason for Blocked:
Needs QA:
Yes
Needs Doc:
Yes
Needs Merging:
Yes
Needs Automation:
No
Support Suite Ticket:
n/a
Hardware Configuration:
ChangeLog Required:
No

Description

Hello can you tell me how to correct this swap space issue. I am not a programmer, a novice NAS user:

Feb 16 02:21:07 Mulvserver kernel: pid 4837 (btsync), uid 817, was killed: out of swap space
Feb 16 02:21:07 Mulvserver kernel: pid 4837 (btsync), uid 817, was killed: out of swap space
Feb 16 11:32:55 Mulvserver kernel: arp: 192.168.1.101 moved from a4:ba:db:02:fa:ef to 02:d9:b4:00:0e:0a on epair1b
Running Processes x
last pid: 35403; load averages: 0.00, 0.00, 0.00 up 0+15:55:48 11:40:46
43 processes: 1 running, 42 sleeping

Mem: 579M Active, 556M Inact, 9966M Wired, 14M Cache, 745M Free
ARC: 8894M Total, 294M MFU, 8179M MRU, 288K Anon, 37M Header, 384M Other
Swap: 8192M Total, 637M Used, 7554M Free, 7% Inuse

PID USERNAME    THR PRI NICE   SIZE    RES STATE   C   TIME    WCPU COMMAND
53448 989 66 20 0 1178M 504M uwait 0 39:18 0.00% mono-sgen
3012 root 12 20 0 243M 14160K uwait 1 2:33 0.00% collectd
2950 root 6 20 0 501M 91444K usem 0 2:05 0.00% python2.7
2954 root 1 52 0 200M 12924K select 5 0:20 0.00% python2.7
1819 root 1 20 0 120M 4776K kqread 3 0:05 0.00% syslog-ng
4908 root 6 23 0 168M 12504K usem 7 0:05 0.00% python2.7
46426 root 6 20 0 164M 13708K usem 0 0:05 0.00% python2.7
46829 root 2 52 0 170M 3204K select 0 0:02 0.00% python2.7
6891 root 1 52 0 174M 3204K ttyin 3 0:01 0.00% python2.7
2381 root 1 20 0 26384K 1848K select 3 0:01 0.00% ntpd
849 www 1 20 0 30500K 1744K kqread 1 0:01 0.00% nginx
2658 root 1 20 0 259M 3116K select 1 0:01 0.00% smbd
2655 root 1 20 0 209M 2668K select 4 0:00 0.00% nmbd
24443 nobody 1 20 0 14064K 1648K select 2 0:00 0.00% mdnsd
1822 root 1 -52 r0 12056K 8036K nanslp 5 0:00 0.00% watchdogd
2665 root 1 20 0 242M 3172K select 2 0:00 0.00% winbindd
40229 root 1 20 0 14184K 412K nanslp 5 0:00 0.00% cron
4668 root 1 20 0 14184K 392K nanslp 4 0:00 0.00% cron
x
Feb 16 02:21:06 Mulvserver swap_pager_getswapspace(16): failed
Feb 16 02:21:06 Mulvserver swap_pager_getswapspace(16): failed
Feb 16 02:21:06 Mulvserver swap_pager_getswapspace(2): failed
Feb 16 02:21:06 Mulvserver swap_pager_getswapspace(16): failed
Feb 16 02:21:06 Mulvserver swap_pager_getswapspace(16): failed
Feb 16 02:21:06 Mulvserver swap_pager_getswapspace(10): failed
Feb 16 02:21:06 Mulvserver swap_pager_getswapspace(16): failed
Feb 16 02:21:06 Mulvserver swap_pager_getswapspace(16): failed
Feb 16 02:21:06 Mulvserver swap_pager_getswapspace(2): failed
Feb 16 02:21:06 Mulvserver swap_pager_getswapspace(3): failed
Feb 16 02:21:06 Mulvserver swap_pager_getswapspace(4): failed
Feb 16 02:21:06 Mulvserver swap_pager_getswapspace(14): failed
Feb 16 02:21:06 Mulvserver swap_pager_getswapspace(16): failed
Feb 16 02:21:06 Mulvserver swap_pager_getswapspace(11): failed
Feb 16 02:21:06 Mulvserver swap_pager_getswapspace(16): failed
Feb 16 02:21:06 Mulvserver swap_pager_getswapspace(16): failed
Feb 16 02:21:06 Mulvserver swap_pager_getswapspace(5): failed

History

#1 Updated by Fran Mulvey over 4 years ago

  • File ixdiagnose.tgz added

#2 Updated by Sean Fagan over 4 years ago

There's not really anything we can do. This is either 3rd Party to Resolve, or Configuration Issue.

You've got 12g of ram, and 8g of swap space, and something is consuming all that memory. Unfortunately, we don't know that it's btsync, just that btsync wanted memory when there was none left.

The options I can think are to get more disks for swap space, add more physical memory, or keep track of which processes are using memory before it runs out.

#3 Updated by Joshua Ruehlig over 4 years ago

  • Status changed from Unscreened to Closed: User Config Issue

#4 Avatar?id=14398&size=24x24 Updated by Kris Moore about 4 years ago

  • Seen in changed from Unspecified to N/A

#5 Updated by Dru Lavigne about 3 years ago

  • File deleted (ixdiagnose.tgz)

#6 Updated by Dru Lavigne about 3 years ago

  • Target version set to N/A
  • Private changed from Yes to No

Also available in: Atom PDF