June 13, 200719 yr Hi! I just returned from a short trip during which I shutdown my UnRaid server. I started it back up to copy some files over and twice it has lost the network connection during the copying. I can ping it, but it won't respond to anything else. //tower goes to Tower Records and \\tower tells me no such network name exists. I logged into the box and copied the syslog to the flash drive and then shutdown the server using unmenu. The log is attached. I'm not sure how to read it, but it seems like it is running out of memory and shutting services down: Jun 12 16:50:26 Tower kernel: [ 939.335573] smbd invoked oom-killer: gfp_mask=0x200d2, order=0, oomkilladj=0 Jun 12 16:50:26 Tower kernel: [ 939.335581] [<c0132afe>] out_of_memory+0x70/0xda Jun 12 16:50:26 Tower kernel: [ 939.335592] [<c0133a52>] __alloc_pages+0x209/0x296 Jun 12 16:50:26 Tower kernel: [ 939.335598] [<c01317bd>] generic_file_buffered_write+0x174/0x56c Jun 12 16:50:26 Tower kernel: [ 939.335604] [<c0156308>] file_update_time+0x83/0x89 Jun 12 16:50:26 Tower kernel: [ 939.335609] [<c013202d>] __generic_file_aio_write_nolock+0x478/0x4a3 Jun 12 16:50:26 Tower kernel: [ 939.335615] [<c027f467>] sock_aio_read+0x50/0x5c Jun 12 16:50:26 Tower kernel: [ 939.335620] [<c014d374>] link_path_walk+0x97/0xa0 Jun 12 16:50:26 Tower kernel: [ 939.335625] [<c0132145>] generic_file_aio_write+0x52/0xb0 Jun 12 16:50:26 Tower kernel: [ 939.335630] [<c014727a>] do_sync_write+0xbf/0xfc Jun 12 16:50:26 Tower kernel: [ 939.335635] [<c0124799>] autoremove_wake_function+0x0/0x33 Jun 12 16:50:26 Tower kernel: [ 939.335641] [<c0147342>] vfs_write+0x8b/0x130 Jun 12 16:50:26 Tower kernel: [ 939.335645] [<c014755c>] sys_pwrite64+0x48/0x5f Jun 12 16:50:26 Tower kernel: [ 939.335648] [<c0102aa4>] syscall_call+0x7/0xb Jun 12 16:50:26 Tower kernel: [ 939.335653] ======================= Jun 12 16:50:26 Tower kernel: [ 939.335655] Mem-info: Jun 12 16:50:26 Tower kernel: [ 939.335657] DMA per-cpu: Jun 12 16:50:26 Tower kernel: [ 939.335660] CPU 0: Hot: hi: 0, btch: 1 usd: 0 Cold: hi: 0, btch: 1 usd: 0 Jun 12 16:50:26 Tower kernel: [ 939.335662] Normal per-cpu: Jun 12 16:50:26 Tower kernel: [ 939.335665] CPU 0: Hot: hi: 186, btch: 31 usd: 58 Cold: hi: 62, btch: 15 usd: 55 Jun 12 16:50:26 Tower kernel: [ 939.335669] Active:111012 inactive:109699 dirty:0 writeback:0 unstable:0 free:1826 slab:1596 mapped:9 pagetables:68 Jun 12 16:50:26 Tower kernel: [ 939.335674] DMA free:3560kB min:68kB low:84kB high:100kB active:4820kB inactive:4812kB present:16256kB pages_scanned:15395 all_unreclaimable? yes Jun 12 16:50:26 Tower kernel: [ 939.335677] lowmem_reserve[]: 0 873 Jun 12 16:50:26 Tower kernel: [ 939.335682] Normal free:3744kB min:3744kB low:4680kB high:5616kB active:439228kB inactive:433984kB present:894080kB pages_scanned:1366622 all_unreclaimable? yes Jun 12 16:50:26 Tower kernel: [ 939.335686] lowmem_reserve[]: 0 0 Jun 12 16:50:26 Tower kernel: [ 939.335688] DMA: 0*4kB 1*8kB 0*16kB 1*32kB 1*64kB 1*128kB 1*256kB 0*512kB 1*1024kB 1*2048kB 0*4096kB = 3560kB Jun 12 16:50:26 Tower kernel: [ 939.335697] Normal: 16*4kB 2*8kB 3*16kB 1*32kB 0*64kB 0*128kB 0*256kB 1*512kB 1*1024kB 1*2048kB 0*4096kB = 3744kB Jun 12 16:50:26 Tower kernel: [ 939.335705] Swap cache: add 0, delete 0, find 0/0, race 0+0 Jun 12 16:50:26 Tower kernel: [ 939.335707] Free swap = 0kB Jun 12 16:50:26 Tower kernel: [ 939.335709] Total swap = 0kB Jun 12 16:50:26 Tower kernel: [ 939.335710] Free swap: 0kB Jun 12 16:50:26 Tower kernel: [ 939.338220] 229376 pages of RAM Jun 12 16:50:26 Tower kernel: [ 939.338223] 0 pages of HIGHMEM Jun 12 16:50:26 Tower kernel: [ 939.338224] 2817 reserved pages Jun 12 16:50:26 Tower kernel: [ 939.338226] 279 pages shared Jun 12 16:50:26 Tower kernel: [ 939.338227] 0 pages swap cached Jun 12 16:50:26 Tower kernel: [ 939.338229] 0 pages dirty Jun 12 16:50:26 Tower kernel: [ 939.338230] 0 pages writeback Jun 12 16:50:26 Tower kernel: [ 939.338232] 9 pages mapped Jun 12 16:50:26 Tower kernel: [ 939.338233] 1596 pages slab Jun 12 16:50:26 Tower kernel: [ 939.338235] 68 pages pagetables Jun 12 16:50:26 Tower kernel: [ 939.338252] Out of memory: kill process 904 (emhttp) score 306 or a child Jun 12 16:50:26 Tower kernel: [ 939.338256] Killed process 904 (emhttp) There are more "kill process" lines for smbd. What is going on? I haven't changed anything in the system. It has 1GB of ram. Thanks
June 13, 200719 yr Hi! I just returned from a short trip during which I shutdown my UnRaid server. I started it back up to copy some files over and twice it has lost the network connection during the copying. I can ping it, but it won't respond to anything else. //tower goes to Tower Records and \\tower tells me no such network name exists. I logged into the box and copied the syslog to the flash drive and then shutdown the server using unmenu. The log is attached. I'm not sure how to read it, but it seems like it is running out of memory and shutting services down: Jun 12 16:50:26 Tower kernel: [ 939.335573] smbd invoked oom-killer: gfp_mask=0x200d2, order=0, oomkilladj=0 Jun 12 16:50:26 Tower kernel: [ 939.335581] [<c0132afe>] out_of_memory+0x70/0xda Jun 12 16:50:26 Tower kernel: [ 939.335592] [<c0133a52>] __alloc_pages+0x209/0x296 Jun 12 16:50:26 Tower kernel: [ 939.335598] [<c01317bd>] generic_file_buffered_write+0x174/0x56c Jun 12 16:50:26 Tower kernel: [ 939.335604] [<c0156308>] file_update_time+0x83/0x89 Jun 12 16:50:26 Tower kernel: [ 939.335609] [<c013202d>] __generic_file_aio_write_nolock+0x478/0x4a3 Jun 12 16:50:26 Tower kernel: [ 939.335615] [<c027f467>] sock_aio_read+0x50/0x5c Jun 12 16:50:26 Tower kernel: [ 939.335620] [<c014d374>] link_path_walk+0x97/0xa0 Jun 12 16:50:26 Tower kernel: [ 939.335625] [<c0132145>] generic_file_aio_write+0x52/0xb0 Jun 12 16:50:26 Tower kernel: [ 939.335630] [<c014727a>] do_sync_write+0xbf/0xfc Jun 12 16:50:26 Tower kernel: [ 939.335635] [<c0124799>] autoremove_wake_function+0x0/0x33 Jun 12 16:50:26 Tower kernel: [ 939.335641] [<c0147342>] vfs_write+0x8b/0x130 Jun 12 16:50:26 Tower kernel: [ 939.335645] [<c014755c>] sys_pwrite64+0x48/0x5f Jun 12 16:50:26 Tower kernel: [ 939.335648] [<c0102aa4>] syscall_call+0x7/0xb Jun 12 16:50:26 Tower kernel: [ 939.335653] ======================= Jun 12 16:50:26 Tower kernel: [ 939.335655] Mem-info: Jun 12 16:50:26 Tower kernel: [ 939.335657] DMA per-cpu: Jun 12 16:50:26 Tower kernel: [ 939.335660] CPU 0: Hot: hi: 0, btch: 1 usd: 0 Cold: hi: 0, btch: 1 usd: 0 Jun 12 16:50:26 Tower kernel: [ 939.335662] Normal per-cpu: Jun 12 16:50:26 Tower kernel: [ 939.335665] CPU 0: Hot: hi: 186, btch: 31 usd: 58 Cold: hi: 62, btch: 15 usd: 55 Jun 12 16:50:26 Tower kernel: [ 939.335669] Active:111012 inactive:109699 dirty:0 writeback:0 unstable:0 free:1826 slab:1596 mapped:9 pagetables:68 Jun 12 16:50:26 Tower kernel: [ 939.335674] DMA free:3560kB min:68kB low:84kB high:100kB active:4820kB inactive:4812kB present:16256kB pages_scanned:15395 all_unreclaimable? yes Jun 12 16:50:26 Tower kernel: [ 939.335677] lowmem_reserve[]: 0 873 Jun 12 16:50:26 Tower kernel: [ 939.335682] Normal free:3744kB min:3744kB low:4680kB high:5616kB active:439228kB inactive:433984kB present:894080kB pages_scanned:1366622 all_unreclaimable? yes Jun 12 16:50:26 Tower kernel: [ 939.335686] lowmem_reserve[]: 0 0 Jun 12 16:50:26 Tower kernel: [ 939.335688] DMA: 0*4kB 1*8kB 0*16kB 1*32kB 1*64kB 1*128kB 1*256kB 0*512kB 1*1024kB 1*2048kB 0*4096kB = 3560kB Jun 12 16:50:26 Tower kernel: [ 939.335697] Normal: 16*4kB 2*8kB 3*16kB 1*32kB 0*64kB 0*128kB 0*256kB 1*512kB 1*1024kB 1*2048kB 0*4096kB = 3744kB Jun 12 16:50:26 Tower kernel: [ 939.335705] Swap cache: add 0, delete 0, find 0/0, race 0+0 Jun 12 16:50:26 Tower kernel: [ 939.335707] Free swap = 0kB Jun 12 16:50:26 Tower kernel: [ 939.335709] Total swap = 0kB Jun 12 16:50:26 Tower kernel: [ 939.335710] Free swap: 0kB Jun 12 16:50:26 Tower kernel: [ 939.338220] 229376 pages of RAM Jun 12 16:50:26 Tower kernel: [ 939.338223] 0 pages of HIGHMEM Jun 12 16:50:26 Tower kernel: [ 939.338224] 2817 reserved pages Jun 12 16:50:26 Tower kernel: [ 939.338226] 279 pages shared Jun 12 16:50:26 Tower kernel: [ 939.338227] 0 pages swap cached Jun 12 16:50:26 Tower kernel: [ 939.338229] 0 pages dirty Jun 12 16:50:26 Tower kernel: [ 939.338230] 0 pages writeback Jun 12 16:50:26 Tower kernel: [ 939.338232] 9 pages mapped Jun 12 16:50:26 Tower kernel: [ 939.338233] 1596 pages slab Jun 12 16:50:26 Tower kernel: [ 939.338235] 68 pages pagetables Jun 12 16:50:26 Tower kernel: [ 939.338252] Out of memory: kill process 904 (emhttp) score 306 or a child Jun 12 16:50:26 Tower kernel: [ 939.338256] Killed process 904 (emhttp) There are more "kill process" lines for smbd. What is going on? I haven't changed anything in the system. It has 1GB of ram. Thanks It is easy to see why the unRaaid server was no longer responding... one of the last programs "killed" in unRaid's attempt to free memory was emhttp, the program that serves up unRaid's user interface web-page. Are you copying your files to folders in the "user shares" or to "disk1", "disk2", etc. If you are copying to user-shares, then that is your problem. Those folders, and any new files you create in them are in memory, not on the physical disks unless the folder you are writing to exists only on one disk. So... if not careful, you could run yourself out of memory by using it all up attempting to fit a >1GB file into your 1GB of ram. Until Tom releases "writable user shares" in the next release of unRaid, the user-shares should probably be shared as read-only. Joe L. PS. Glad that my "unmenu" script was of use to you.
June 13, 200719 yr Author Thanks! That's the problem. My next attempt was going to be to write to the disk rather than the share. I didn't realize I had to do that way. Makes sense, though. I thought that emhttp being killed was probably why I couldn't get the interface. And I guess smbd being killed is why I no longer could connect to the folders. Thanks!
June 13, 200719 yr I thought that emhttp being killed was probably why I couldn't get the interface. And I guess smbd being killed is why I no longer could connect to the folders. Exacly right. smdb is the Samba daemon. emhttp is the unRaid interface. Joe L.
December 4, 200718 yr I think I'm having the same problem. Whenever I go to the "shares" section emhttp gets killed. I have 2 disks, and on each disk, the root level directory is disk1 and disk2. In trying to figure out the user share feature. I went through explorer, and moved everything out of disk1 and disk2 and to the root level. I then added a share called "movies" in the shares section with * for disc included. After the gui came back, it displayed all of my folder in the root level in the share section. Only "movies" had the * in the disc included part. I can now see the content of the movies directory from both discs under explorer. This is when the problem started, as soon as I go to "shares" in the gui, emhttp gets killed. I tried to change "movies" to read-only as suggested previously, but the gui always times out afterwards due to emhttp being killed. How do I move the directories back? And how do I properly use the user share feature? The documentation is quite lacking, no mention of having to read-only to prevent this.
December 4, 200718 yr not sure of your actual problem. But the problem adressed in the thread were fixed on later releases. Stating your unraid version would be helpful, and the syslog file. /Rene
December 5, 200718 yr not sure of your actual problem. But the problem adressed in the thread were fixed on later releases. Stating your unraid version would be helpful, and the syslog file. /Rene I got it moved back. I guess I just don't really understand how user shares work. I mean, I get the concept that all directories in the root level with the same name will appear as one big directory. But how to get enable it so that it works is still unclear.
Archived
This topic is now archived and is closed to further replies.