plugout.net

Hi,

Any one have the same issue? I can't reproduce this, but the Administration console is sometimes not reachable.
I think after using transmission. But I am not sure. Had to reboot the disk, to get it working again.
The disk works fine...

This happens since 15-1 upgrade.

Regards.

Hi brinka

Currently fvdw and me don't have your issue.

I don't think that transmission can do this : there is no change with the transmission feature.

What are the running servers on your nwsp2? btsync and mldonkey can use many memory ressources

before restarting, try to open a shell terminal and do this command

Code: Select all

ps axf

No response from ps axf ....

When I do ps -ef processes are shown but don't get the command prompt back...

Could it be nzbget ?? Had never problems with this...

please check free space on the disk
give the command

Code: Select all

df

And see how much free space /dev/root has

It looks like that you have filled up the system partition with a download or so, this might happen if the files you download are not stored on partition 8

root@NetworkSpace2:/ # df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/root 247968 178992 56176 76% /
/dev/sda1 247968 178992 56176 76% /
/dev/sda5 790556 17576 764948 2% /rw_fs
tmpfs 5000 748 4252 15% /rw_fs/tmp/usr/var
/dev/sda8 958609700 689601196 259269584 73% /share/1000
/dev/root 198368 126032 62096 67% /lacie-boot
root@NetworkSpace2:/ #

No problem according to me...

No you have a problem on sda5 ! (very few free space)

So in putty, search if there are big files in the folder /tmp or /rw_fs

yep jocko is right you have something big stored on sda5
sda5 is mounted on the directory /rw_fs

do a directory listing of that folder to find out what is in there

Did some investigation, looks like locking.tdb is a big file....
root@NetworkSpace2:/rw_fs/tmp/usr/var/locks # ls -al
total 748
drwxr-xr-x 4 root root 440 2014-02-18 21:32 .
drwxrwxrwt 3 root root 60 2014-02-16 09:18 ..
-rw------- 1 root root 4096 2014-02-16 09:18 account_policy.tdb
-rw-r--r-- 1 root root 45056 2014-02-18 19:09 brlock.tdb
-rw-r--r-- 1 root root 219 2014-02-18 21:32 browse.dat
-rw-r--r-- 1 root root 12288 2014-02-18 20:24 connections.tdb
-rw-r--r-- 1 root root 696 2014-02-16 09:18 gencache.tdb
-rw------- 1 root root 4096 2014-02-16 09:18 group_mapping.tdb
-rw-r--r-- 1 root root 614400 2014-02-18 20:50 locking.tdb
-rw------- 1 root root 4096 2014-02-16 10:44 messages.tdb
-rw-r--r-- 1 root root 5 2014-02-16 09:18 nmbd.pid
-rw-r--r-- 1 root root 4096 2014-02-18 18:59 notify.tdb
-rw------- 1 root root 4096 2014-02-16 09:18 ntdrivers.tdb
-rw------- 1 root root 696 2014-02-16 09:18 ntforms.tdb
-rw------- 1 root root 4096 2014-02-16 09:18 ntprinters.tdb
drwxr-xr-x 2 root root 40 2014-02-16 09:18 perfmon
drwxr-xr-x 2 root root 40 2014-02-16 09:18 printing
-rw------- 1 root root 16384 2014-02-16 09:18 registry.tdb
-rw-r--r-- 1 root root 20480 2014-02-18 20:24 sessionid.tdb
-rw------- 1 root root 4096 2014-02-16 09:20 share_info.tdb
-rw-r--r-- 1 root root 5 2014-02-16 09:18 smbd.pid
-rw-r--r-- 1 root root 8192 2014-02-17 23:04 unexpected.tdb
root@NetworkSpace2:/rw_fs/tmp/usr/var/locks #

You could use the command du to find easily the big file

Code: Select all

du -ha /rw_fs

Note: currently my locking file is

Code: Select all

root@Kappa:/ # ls -al   /rw_fs/tmp/usr/var/locks/locking.tdb
-rw-r--r--  1 root root 262144 2014-02-18 19:04 /rw_fs/tmp/usr/var/locks/locking.tdb

so the size of your file is not big (~600kB)
the sda5 size is ~772MB

Hmmmm... Samba....