Cannot login to web gui

  • Hi Help,


    My unit has been doing great for a few months now. Recently updated FTP to explicit FTP over TLS with a self-signed cert. I did just recently do large FTP jobs [last night]. Now this morning I cannot login to the web gui.

    • It refreshes the page when I attempt, back to the login page, without any error. [only highlighting the user name field in red, that it requires a username on the new session]
    • FTP server is still running and usable.
    • Also still connected to the samba share.
    • Incognito Chrome does not change the behavior.
    • This symptom also persists thru a reboot.

    Since I wasn't doing anything that would prompt a configuration backup I don't currently have one and therefore really hope I can avoid a re-install of the OS.


    Thank you to those willing to help solve this with me!


    Things I have tried and verified;

    1. I can SSH to unit.

    2. From SSH ran;

    apt-get clean

    rm /var/log/*gz

    dpkg-reconfigure tzdata [verified timezone is correct]
    df-h shows the following and I have been troubleshooting /dev/sde2 47G 47G 0 100% /

    Filesystem Size Used Avail Use% Mounted on

    udev 3.9G 0 3.9G 0% /dev

    tmpfs 785M 79M 706M 11% /run

    /dev/sde2 47G 47G 0 100% /

    tmpfs 3.9G 120K 3.9G 1% /dev/shm

    tmpfs 5.0M 0 5.0M 0% /run/lock

    tmpfs 3.9G 0 3.9G 0% /sys/fs/cgroup

    /dev/sde1 511M 6.3M 505M 2% /boot/efi

    tmpfs 3.9G 0 3.9G 0% /tmp

    /dev/md0 7.3T 193G 7.1T 3% /srv/dev-disk-by-label-Data


    fdisk -l Expands on this;

    Disk /dev/sdb: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors

    Disk model: WDC WD2003FYYS-1

    Units: sectors of 1 * 512 = 512 bytes

    Sector size (logical/physical): 512 bytes / 512 bytes

    I/O size (minimum/optimal): 512 bytes / 512 bytes



    Disk /dev/sda: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors

    Disk model: WDC WD2000FYYZ-0

    Units: sectors of 1 * 512 = 512 bytes

    Sector size (logical/physical): 512 bytes / 512 bytes

    I/O size (minimum/optimal): 512 bytes / 512 bytes



    Disk /dev/sdc: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors

    Disk model: WDC WD2000FYYZ-0

    Units: sectors of 1 * 512 = 512 bytes

    Sector size (logical/physical): 512 bytes / 512 bytes

    I/O size (minimum/optimal): 512 bytes / 512 bytes



    Disk /dev/sdd: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors

    Disk model: TOSHIBA MG03ACA2

    Units: sectors of 1 * 512 = 512 bytes

    Sector size (logical/physical): 512 bytes / 512 bytes

    I/O size (minimum/optimal): 512 bytes / 512 bytes



    Disk /dev/sde: 55.9 GiB, 60022480896 bytes, 117231408 sectors

    Disk model: KINGSTON SV300S3

    Units: sectors of 1 * 512 = 512 bytes

    Sector size (logical/physical): 512 bytes / 512 bytes

    I/O size (minimum/optimal): 512 bytes / 512 bytes

    Disklabel type: gpt

    Disk identifier: BCF918D6-9867-450F-B519-70A10DE699FA


    Device Start End Sectors Size Type

    /dev/sde1 2048 1050623 1048576 512M EFI System

    /dev/sde2 1050624 100710399 99659776 47.5G Linux filesystem

    /dev/sde3 100710400 117229567 16519168 7.9G Linux swap



    Disk /dev/md0: 7.3 TiB, 8001054310400 bytes, 15627059200 sectors

    Units: sectors of 1 * 512 = 512 bytes

    Sector size (logical/physical): 512 bytes / 512 bytes

    I/O size (minimum/optimal): 524288 bytes / 2097152 bytes

  • Fixed it; syslog filled up.


    Quick and dirty what to do if you run into this.


    Check log sizes

    du -hsx /var/* | sort -rh | head -10

    Get specific log size

    ls -alh /var/log/

    Delete largest log and reboot

    rm -f *file*

  • z3r0gt

    Hat das Label gelöst hinzugefügt.
  • Probably that is just the symptom, not the problem. You need to find out what is filling your syslog up and fix that, Otherwise it will happen again.

    That is what I am looking into now! macom Any suggestions?


    I do have FTP 'Transfer log' enabled. Trying to see if I can extra option it to make it minimal logging. I can only deduce right now that transferring the hundreds of files filled up the log.


    Also totally separate, trying to find the best config backup solution. Best being smallest and repeatable/schedule-able. Granted I have a 60GB SSD for the OS now, I could upgrade to a 250 but still to what end. 46.5GB used for main OS partition is 56% full just running which I find is a lot of use.

  • z3r0gt

    Hat das Label gelöst entfernt.
    • Offizieller Beitrag

    Any suggestions?

    Have a look inside the log files. If they became that big, there will be many very similar log entries. Then you need to find out what they are related to.

    Transferring hundreds of files should not be the issue. There must be something else.

    Also totally separate, trying to find the best config backup solution. Best being smallest and repeatable/schedule-able. Granted I have a 60GB SSD for the OS now, I could upgrade to a 250 but still to what end. 46.5GB used for main OS partition is 56% full just running which I find is a lot of use.

    There is the backup-plugin from omv-extras which uses different methods to backup the root filesystem on demand or regularly, if you want

  • Have a look inside the log files. If they became that big, there will be many very similar log entries. Then you need to find out what they are related to.

    Transferring hundreds of files should not be the issue. There must be something else.

    There is the backup-plugin from omv-extras which uses different methods to backup the root filesystem on demand or regularly, if you want

    Thank you macom! I'll look into these. I did review the syslog just now and it is writing 2 lines for every single SMB transfer that I am doing now which fill up 800+ pages within seconds. I'll still need to look out for any errors but at the moment it just seems that the verbose logging is too high. I can't see a way to turn it down.

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!