This morning, I cant see unraid in network shares. Unraid webgui shows no drives. I cant get auto diagnostics logs but I can get the syslog. Not sure why.

 

Here are the syslog.

https://gist.github.com/syaifulnizamyahya/937ff7a1dbe2ccff73d33c78c6fdd6ed#file-unraidsyslog-txt

 

This has been happening for quite some time.

Syslog shows nothing of any particular interest.  What you should do however is disable mover loggings (Settings - schedule) so that if / when the problem happens again and you grab the syslog it's not spammed with "hey I moved this ok".

 

Only "weird" thing is that something on your network kept on logging into the system

Mar 16 01:58:29 Tower sshd[19366]: Accepted password for root from 172.17.0.2 port 45365 ssh2

every couple of seconds for hours.

The subject line says "Had to reboot". Can you get the diagnostics after the reboot? And please always attach rather than posting a link. Even if the syslog was too large as text, I'm sure it would have been small enough if you had zipped it.

3 hours ago, trurl said:

The subject line says "Had to reboot". Can you get the diagnostics after the reboot? And please always attach rather than posting a link. Even if the syslog was too large as text, I'm sure it would have been small enough if you had zipped it.

I can get the diagnostics after the reboot. Ill attach logs next time. sorry.  

 

3 hours ago, Squid said:

Syslog shows nothing of any particular interest.  What you should do however is disable mover loggings (Settings - schedule) so that if / when the problem happens again and you grab the syslog it's not spammed with "hey I moved this ok".

 

Only "weird" thing is that something on your network kept on logging into the system

 

Mar 16 01:58:29 Tower sshd[19366]: Accepted password for root from 172.17.0.2 port 45365 ssh2

every couple of seconds for hours.

Ill disable mover login next time. I find out who kept logging to my network.

here are my diagnostics after reboot

tower-diagnostics-20180317-0703.zip

 

i have disable mover loggings. lets see what happens.

Are you still having the problems after reboot? Have you tried booting in SAFE mode?

6 hours ago, trurl said:

Are you still having the problems after reboot? Have you tried booting in SAFE mode?

No problem after reboot. this happens after few days. i would say, once a week.

would there be a problem is i log a lots of things? i set rclone to do stuff and logs it. could this be the cause?

On the dashboard page you can monitor how much memory the LOG subsystem takes. By default it has a capacity of 128M, too much logging can easily overload it.

 

3 minutes ago, bonienl said:

On the dashboard page you can monitor how much memory the LOG subsystem takes. By default it has a capacity of 128M, too much logging can easily overload it.

 

Looking at the dashboard, i cant see how much of logs capacity that have been use. How can i know how much capacity that I have use?

2 hours ago, publicENEMY said:

Looking at the dashboard, i cant see how much of logs capacity that have been use.

Lower left of Dashboard, System Status, the line labeled "flash log docker" shows the percentage used of flash drive, log space, and docker img.

12 hours ago, trurl said:

Lower left of Dashboard, System Status, the line labeled "flash log docker" shows the percentage used of flash drive, log space, and docker img.

ah so thats what it means by flash log docker. That UI can be improved. 

i noticed that my docker has increased to 60%. How can I flush it?

1 hour ago, publicENEMY said:

i noticed that my docker has increased to 60%. How can I flush it?

 

The Docker FAQ has a section with several posts about docker image filling up. Have you looked there?

Sorry for asking. 

I have looked in the FAQ here, 

 

I have did as per guide. My doCker usage is still 60%.

 

Any advice?

Usage doesn't mean anything in and by itself.  60% usage on a 10Gig image: ok.  60% usage on a 100Gig image: not ok

 

Is it growing?