Admin console not accessable after 15-1 update

[fvdw]

An other thing, the power button doesnt react.... Have to pull out the power cord to reboot it...

:disapprove what is wrong here, did you modify the boot scripts ?

[brinka123]

Looks like uploading the firmware package doesn't work.... Disk stops spinning......

Still executing command, please wait...
That took a long time...

Installed 15-1 again....
Lets see how it operates now...

[fvdw]

the install should normally be ready in a few minutes

[brinka123]

Install took a long time. 20-30minutes. But it is OK now.

Thanks for the support so far. Looks like the previous install wasn't OK. Let's see whether it stays OK..

Thanks! Great NAS!!!

[brinka123]

After a few days of usage, not seen the problem anymore.
Reinstall of the FW did the trick....

Thanks..

[brinka123]

Tijdje goed gegaan, heb weer het zelfde.
1] Webserver nzbget niet meer berijkbaar. Ik draai nzbget -D
2] Daarnaar open ik admin console. Click op system information. Admin Console niet meer berijkbaar.
3] Weer het zelfde euvel, power button werkt niet meer, ps -ef stopt.
4] Heb gereboot door power eraf te halen. Alles werkt dan weer.

Toch iets met nzbget????

Output top M:

Code: Select all

top - 08:35:34 up 10:01,  3 users,  load average: 24.08, 23.68, 22.75
Tasks:  92 total,   1 running,  91 sleeping,   0 stopped,   0 zombie
Cpu(s):  0.3%us,  0.3%sy,  0.0%ni, 99.3%id,  0.0%wa,  0.0%hi,  0.0%si,  0.0%st
Mem:    251392k total,   248008k used,     3384k free,    61408k buffers
Swap:   514076k total,        0k used,   514076k free,   150036k cached

  PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
 1241 nobody    20   0 17836 7676 3988 S  0.0  3.1   0:02.11 httpd
 1053 nobody    20   0 17836 7672 3984 S  0.0  3.1   0:02.35 httpd
 1050 root      20   0 16744 5780 3440 S  0.0  2.3   0:02.71 httpd
 1349 Andre     20   0  170m 4212 1944 D  0.0  1.7   6:49.74 nzbget
 1066 root      20   0  8516 2400 1784 S  0.0  1.0   0:00.05 smbd
 1067 root      20   0  8516 1812 1196 S  0.0  0.7   0:00.00 smbd
 1155 root      20   0  3028 1416  784 S  0.0  0.6   0:00.01 rpc.mountd
 1063 root      20   0  5860 1380  904 S  0.0  0.5   0:01.09 nmbd
 1157 root      20   0  2588 1252  696 S  0.0  0.5   0:00.01 rpc.statd
 9986 root      20   0  4508 1092  872 D  0.0  0.4   0:00.09 ps
10072 root      20   0  2440 1076  868 R  0.7  0.4   0:02.11 top
10037 root      20   0  2368  924  748 S  0.0  0.4   0:01.19 dropbear



De 170m VIRT van nzbget is de boosdoener???
Ik heb nog ongeveer 3MB memory vrij...

[fvdw]

to be honest :dontknow

Some thoughts
Not enough free memory could be a memory leak of a program. Such a program allocates memory when running for instance when entering a loop and when not written properly it doesn't free memory when finished the loop and claiming again space when executing the loop again. In that way the program memory use grows over time until there is nothing left
In your case I don't see a program in the top that use lots of memory, but "top" doen't show a full memory map. Furthermore it still has 512 MB for swapping but so to see it doesn't use swap. But the command "free" is a better tool to see free memory. Anyhow a reboot should free up the memory if it is occupied by a program with a memory leak. If after a reboot the system runs ok than more close look to memory usage is an option.

More likely could be that a program is filling up the the system partition with for instance log files or other stuff
the command

Code: Select all

df -h

might disclose this information

If thats not the case then your hard disk may suffer from bad blocks...

[brinka123]

All looks normal:
When system "hangs":

Code: Select all

root@NetworkSpace2:/ # df -h
Filesystem                Size      Used Available Use% Mounted on
/dev/root               242.2M    174.8M     54.9M  76% /
/dev/sda2               242.2M    174.8M     54.9M  76% /
/dev/sda5               772.0M     17.1M    747.0M   2% /rw_fs
tmpfs                     4.9M    196.0K      4.7M   4% /rw_fs/tmp/usr/var
/dev/sda8               914.2G    573.0G    332.0G  63% /share/1000
/dev/root               193.7M    123.1M     60.6M  67% /lacie-boot
root@NetworkSpace2:/ # free
             total         used         free       shared      buffers
Mem:        251392       248368         3024            0        52352
-/+ buffers:             196016        55376
Swap:       514076            0       514076
root@NetworkSpace2:/ #


After reboot:

Code: Select all

root@NetworkSpace2:/ # df -h
Filesystem                Size      Used Available Use% Mounted on
/dev/root               242.2M    174.8M     54.9M  76% /
/dev/sda2               242.2M    174.8M     54.9M  76% /
/dev/sda5               772.0M     17.1M    747.1M   2% /rw_fs
tmpfs                     4.9M    152.0K      4.7M   3% /rw_fs/tmp/usr/var
/dev/sda8               914.2G    573.0G    332.0G  63% /share/1000
/dev/root               193.7M    123.1M     60.6M  67% /lacie-boot
root@NetworkSpace2:/ # free
             total         used         free       shared      buffers
Mem:        251392       150772       100620            0        99604
-/+ buffers:              51168       200224
Swap:       514076            0       514076
root@NetworkSpace2:/ #


[fvdw]

there is defentily a difference in amount of free memory after reboot, so something is consuming memory...

Is it working normally after reboot and what happens if you run it without nzbget ?

[fvdw]

if it works ok without using nzbget then it must be related with nzbget. In that case a recompile of nzbget could be considered as since it was compiled many changes were made such as an update of glibc and openssl.