Hello Dear

 

I have yesterday a problem with my unRAID Server:

- Can't login with my Android Handy with FTP (App Mixplorer)

- i can login with Kodi OS (Samba, installed on Raspberry Pi) but im kicked out after 2minutes...

- Server is down says the ControlR-App.

 

- I can allways go to the WEBGui with Laptop...

 

what can i do for fix it?

everything worked before

 

(sry my english is bad...)

 

thanks for your answere.

 

----------

Hallo

 

Ich hatte gestern ein Problem mit dem unRAID Server:

- Ich konnte nicht mit der Mixplorer-App (Android) per FTP auf die Daten zugreifen.

- Konnte mit dem Kodi OS (Samba) darauf zugreifen, aber flog nach ca 2min wieder raus.

- Der Server war gemäss der ControlR-App immer Down.

 

- Ich konnte jedoch jederzeit mit dem Laptop auf die WEBGUI zugreifen.

 

Was könnte hier das Problem sein?

 

Danke für jede Hilfe.

 

 

Edited December 11, 20178 yr by Newsletter

SYSLOG:

syslog.txt

 

who have an idea?  the server works very slowly...

3 minutes ago, Newsletter said:

SYSLOG:

syslog.txt

 

who have an idea?  the server works very slowly...

Instead of the syslog, post the entire Diagnostics Zip File.

9 minutes ago, Squid said:

Instead of the syslog, post the entire Diagnostics Zip File.

 

can i do this with SSH? (Webgui dosn't work now ) ... i have fix common problems installed..

Edited December 11, 20178 yr by Newsletter

yes

diagnostics

how can i do this with ssh? i search it and commands ...

Edited December 11, 20178 yr by Newsletter

command is

diagnostics

and then upload the resulting file.

1 hour ago, Squid said:

command is

diagnostics

and then upload the resulting file.

 

Ahh Okay  very simple ^^

 

tower-diagnostics-20171211-2120.zip

 

 

i become from fix common problems allways with the Serverstart this message:

Quote

 

Fix Common Problems: 11-12-2017 21:14

Errors have been found with your server.
Investigate at Settings / User Utilities / Fix Common Problems

 

 

Quote

Dec 11 21:15:51 Tower kernel: tun: Universal TUN/TAP device driver, 1.6
Dec 11 21:15:51 Tower kernel: tun: (C) 1999-2004 Max Krasnyansky <[email protected]>
Dec 11 21:15:52 Tower emhttp: nothing to sync
Dec 11 21:15:52 Tower sudo: root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/bin/bash -c /usr/local/emhttp/plugins/controlr/controlr -port 2378 -certdir '/boot/config/ssl/certs' -showups
Dec 11 21:15:52 Tower kernel: Ebtables v2.0 registered
Dec 11 21:15:52 Tower kernel: virbr0: port 1(virbr0-nic) entered blocking state
Dec 11 21:15:52 Tower kernel: virbr0: port 1(virbr0-nic) entered disabled state
Dec 11 21:15:52 Tower kernel: device virbr0-nic entered promiscuous mode
Dec 11 21:15:52 Tower avahi-daemon[4211]: Joining mDNS multicast group on interface virbr0.IPv4 with address 192.168.122.1.
Dec 11 21:15:52 Tower avahi-daemon[4211]: New relevant interface virbr0.IPv4 for mDNS.
Dec 11 21:15:52 Tower avahi-daemon[4211]: Registering new address record for 192.168.122.1 on virbr0.IPv4.
Dec 11 21:15:52 Tower kernel: virbr0: port 1(virbr0-nic) entered blocking state
Dec 11 21:15:52 Tower kernel: virbr0: port 1(virbr0-nic) entered listening state
Dec 11 21:15:52 Tower dnsmasq[5454]: started, version 2.76 cachesize 150
Dec 11 21:15:52 Tower dnsmasq[5454]: compile time options: IPv6 GNU-getopt no-DBus i18n IDN DHCP DHCPv6 no-Lua TFTP no-conntrack ipset auth no-DNSSEC loop-detect inotify
Dec 11 21:15:52 Tower dnsmasq-dhcp[5454]: DHCP, IP range 192.168.122.2 -- 192.168.122.254, lease time 1h
Dec 11 21:15:52 Tower dnsmasq-dhcp[5454]: DHCP, sockets bound exclusively to interface virbr0
Dec 11 21:15:52 Tower dnsmasq[5454]: reading /etc/resolv.conf
Dec 11 21:15:52 Tower dnsmasq[5454]: using nameserver 62.2.17.60#53
Dec 11 21:15:52 Tower dnsmasq[5454]: using nameserver 62.2.24.162#53
Dec 11 21:15:52 Tower dnsmasq[5454]: using nameserver 62.2.17.61#53
Dec 11 21:15:52 Tower dnsmasq[5454]: read /etc/hosts - 2 addresses
Dec 11 21:15:52 Tower dnsmasq[5454]: read /var/lib/libvirt/dnsmasq/default.addnhosts - 0 addresses
Dec 11 21:15:52 Tower dnsmasq-dhcp[5454]: read /var/lib/libvirt/dnsmasq/default.hostsfile
Dec 11 21:15:52 Tower kernel: virbr0: port 1(virbr0-nic) entered disabled state
Dec 11 21:20:45 Tower sshd[11593]: Accepted password for root from 192.168.0.122 port 6482 ssh2
Dec 11 21:22:29 Tower sshd[13946]: Accepted password for root from 192.168.0.122 port 6484 ssh2
Dec 11 21:42:54 Tower kernel: mdcmd (37): check nocorrect
Dec 11 21:42:54 Tower kernel: md: recovery thread: check ...
Dec 11 21:42:54 Tower kernel: md: using 1536k window, over a total of 2930266532 blocks.
Dec 11 21:46:45 Tower kernel: kvm: already loaded the other module
Dec 11 21:49:42 Tower emhttp: cmd: /usr/local/emhttp/plugins/fix.common.problems/scripts/showExtendedLog.sh
Dec 11 21:49:53 Tower root: Fix Common Problems Version 2017.10.15a
Dec 11 21:50:05 Tower root: Fix Common Problems: Warning: Docker Application openvpn-as has an update available for it
Dec 11 21:50:05 Tower root: Fix Common Problems: Warning: unRaid's built in FTP server is running
Dec 11 21:50:05 Tower root: Fix Common Problems: Warning: Deprecated plugin ca.backup.plg
Dec 11 21:50:06 Tower root: Fix Common Problems: Error: Docker Application openvpn-as is currently set up to run in bridge mode
Dec 11 21:50:06 Tower root: Fix Common Problems: Error: unclean shutdown detected of your server

 

Okay the docker "openvpn-as" have i removed. 

Edited December 11, 20178 yr by Newsletter

2 hours ago, Newsletter said:

Okay the docker "openvpn-as" have i removed. 

You didn't need to remove it.  Simply edit the container and switch network mode from bridge back to host where it belongs

 

Nothing particularly jumped out at me for the diagnostics and your problems, but I did make a PR to limetech to modify the diagnostics a bit to help out in situations like this.  (Athough it could be because of your rather low-powered CPU and the system currently running a parity check - it wouldn't cause a crash, but it might slow everything down enough to make you think it did)

In addition, it would be more helpful if the diagnostics obtained was from after an issue occurred.  It looks like this was provided right after the system booted up.