Posts by Trailerstar

    Hi macom ,

    thanks for pointing me to that thread.

    In the meanwhile I succesfully upgraded my v4 to v5.5.3-1 with that script and the given commands.

    At some point the installer asked me for several modules if I would like to keep my current customized configs or update with the new releases:


    I was afraid to maybe overwrite OMV-specific settings when upgrading to the highly current versions.

    Nevertheless I always chose to install the maintainer's version - and everything worked well.


    Cheers,

    Glad you finally solved it :thumbup:


    Please consider to upgrade to OMV5.

    OMV4 is based on Debian 9 and that will be end of life soon.

    The last time I considered an upgrade I found out that there's no inplace upgrade path from OMV 3.x to 4.x which resulted in a complete new installation.

    I did not read any manuals yet but I am hopeful that OMV evolved and an inplace upgrade from v4 to v5 is available now. Is it?


    The mentioned thread on GitHub gave me helpful information to solve the problem. Thank you, macom !

    For the records:

    Something broke during the upgrade from "openmediavault-flashmemory folder2ram plugin for OpenMediaVault" v 4.2.x up to v 4.2.2 with the sessions folder of NGinx. The permissions were lost or altered or not updated (I'm not exactly sure what happened).


    Deleting the sessions folder and re-creating it did help:

    Code
    sudo rm -rf /var/lib/php/sessions 
    sudo mkdir -m 777 /var/lib/php/sessions 
    ls /var/lib/php -l 
    sudo nginx -s reload

    After that I was able to log in to the web GUI.

    To avoid future problems with the folder2ram plugin I deinstalled it. I switched from an USB flash drive to a standard SSD a couple of months ago and preserved the plugin just out of habit.

    Thank you all for your support!

    Did some research in the logfiles and monitored my own login tries.


    Found this in openmediavault-webgui_error.log:

    Code
    2020/06/12 08:23:56 [error] 2062#2062: *56 FastCGI sent in stderr: "PHP message: PHP Warning: session_start(): open(/var/lib/php/sessions/sess_k7r8eiig1i8j3o18n0hr6l33u4, O_RDWR) failed: Permission denied (13) in /usr/share/php/openmediavault/session.inc on line 43" while reading response header from upstream, client: 127.0.0.1, server: openmediavault-webgui, request: "HEAD / HTTP/1.1", upstream: "fastcgi://unix:/var/run/php-fpm-openmediavault-webgui.sock:", host: "127.0.0.1"
    2020/06/12 08:24:13 [error] 2062#2062: *58 FastCGI sent in stderr: "PHP message: PHP Warning: session_start(): open(/var/lib/php/sessions/sess_ccne044kgksro7rfbaoiaghqp1, O_RDWR) failed: Permission denied (13) in /usr/share/php/openmediavault/session.inc on line 43
    PHP message: PHP Warning: session_regenerate_id(): open(/var/lib/php/sessions/sess_ccne044kgksro7rfbaoiaghqp1, O_RDWR) failed: Permission denied (13) in /usr/share/php/openmediavault/session.inc on line 67
    PHP message: PHP Warning: session_regenerate_id(): Session write failed. ID: files (path: /var/lib/php/sessions) in /usr/share/php/openmediavault/session.inc on line 67" while reading response header from upstream, client: 192.168.0.248, server: openmediavault-webgui, request: "POST /rpc.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php-fpm-openmediavault-webgui.sock:", host: "nas", referrer: "http://nas/"
    2020/06/12 08:24:14 [error] 2062#2062: *58 FastCGI sent in stderr: "PHP message: PHP Warning: session_start(): open(/var/lib/php/sessions/sess_ccne044kgksro7rfbaoiaghqp1, O_RDWR) failed: Permission denied (13) in /usr/share/php/openmediavault/session.inc on line 43" while reading response header from upstream, client: 192.168.0.248, server: openmediavault-webgui, request: "GET / HTTP/1.1", upstream: "fastcgi://unix:/var/run/php-fpm-openmediavault-webgui.sock:", host: "nas", referrer: "http://nas/"


    And found this in openmediavault-webgui_access.log:


    Code
    127.0.0.1 - - [12/Jun/2020:08:23:56 +0200] "HEAD / HTTP/1.1" 200 0 "-" "Monit/5.20.0"
    192.168.0.248 - - [12/Jun/2020:08:24:12 +0200] "GET /images/exclamation.svg HTTP/1.1" 304 0 "http://nas/css/theme-all.min.css" "Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/83.0.4103.97 Safari/537.36"
    192.168.0.248 - - [12/Jun/2020:08:24:12 +0200] "GET /extjs6/classic/theme-triton/resources/fonts/OpenSans-Bold.ttf HTTP/1.1" 304 0 "http://nas/extjs6/classic/theme-triton/resources/theme-triton-all_2.css" "Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/83.0.4103.97 Safari/537.36"
    192.168.0.248 - - [12/Jun/2020:08:24:13 +0200] "POST /rpc.php HTTP/1.1" 200 78 "http://nas/" "Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/83.0.4103.97 Safari/537.36"
    192.168.0.248 - - [12/Jun/2020:08:24:14 +0200] "GET / HTTP/1.1" 200 1870 "http://nas/" "Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/83.0.4103.97 Safari/537.36"
    127.0.0.1 - - [12/Jun/2020:08:24:26 +0200] "HEAD / HTTP/1.1" 200 0 "-" "Monit/5.20.0"

    Executed the commands without any errors (didn't get any sort of successful messages either).

    But that didn't help. GUI still returns to the login screen when trying to log me in.


    I assume that what I should look for is log files of nginx. Or does OMV write own logs in another location, too ?

    Hi guys,


    I'm running OMV 4.1.35-1 and from a couple of weeks ago I suddenly couldn't login to the Web GUI anymore:

    When I enter the credentials it starts loading the admin web page but then returns to the login screen.

    I can successfully login with SSH and as far as I can see all services run smoothly. I do not experience other problems.

    I randomly use the web gui so I can not state the exact point when it stopped letting me login.


    What I tried:

    - use another browser with empty cache or use private session,

    - df -h shows enough free space,

    - dpkg -l | grep openmediavault :


    ii openmediavault 4.1.35-1 all openmediavault - The open network attached storage solution

    ii openmediavault-autoshutdown 4.0.5 all OpenMediaVault AutoShutdown Plugin

    ii openmediavault-backup 4.0.6 all backup plugin for OpenMediaVault.

    ii openmediavault-diskstats 4.0.2-1 all OpenMediaVault disk monitoring plugin

    ii openmediavault-flashmemory 4.2.1 all folder2ram plugin for OpenMediaVault

    ii openmediavault-keyring 1.0 all GnuPG archive keys of the OpenMediaVault archive

    ii openmediavault-locate 3.4 all locate plugin for OpenMediaVault.

    ii openmediavault-omvextrasorg 4.1.16 all OMV-Extras.org Package Repositories for OpenMediaVault

    ii openmediavault-resetperms 3.3 all Reset Permissions

    ii openmediavault-route 4.0.4-1 all OpenMediaVault IP routing table plugin



    Any hints on that?


    Cheers,

    Yes, I agree to not backup tmp files or folders.
    But in this case there is nothing I could do about it. Deselecting it for example.
    Because the built-in backup in OMV GUI has just one button stating "Start".
    So I consider this function pretty useless, isn't it?

    Hi all,


    I use the biult-in backup function to backup OMV to a local folder, which is located on the local array.
    The backup fails with the following error messages. As far as I can see it fails to copy tmp files that are in use.
    What can I try to solve the problem?


    I solved this problem when I removed the wlan0 interface temporarily. Just used eth0 only. It seems that downloading and installing OMV somewhere somehow gets confused when there are delays in traffic (wifi) or when there are more than just one network interfaces with different IP adresses and/or gateways. Didn't investigate into this any further since it suddenly was working.

    Well, there may be more than one reason for that. I had the same problem a while ago with a external USB drive when I tried to copy the content over to my NAS. The external HDD was 2TB and I wasn't able to copy more than about 600-800 GBs then it stalled.
    I went through some steps.


    At first, I checked the BIOS settings and made sure that there is no sort of power-saver setting active for the USB port or the internal hub itself.
    Then I changed the cable to a really good and reliable one.
    None of this helped.


    Finally I found out that the cause of all things ;) was a temperature problem. The USB <-> SATA converter unit in the external enclosure became so hot after a while when I was transfering a heavy load of data over a longer period of time that the circuit board and the chips seam to reach a certain temperature value. Above that temperature level there seemed to occur transmission errors and finally a total breakdown of function. After letting it sit and cool down for one or two quarters of an hour the drive became available again.


    How I fixed the problem: I opened the case and set up a fan that was blowing air directly onto the circuit board and the chips and was able to copy the whole content of 2TBs. After this experience I sold the drive ;-)
    Another possible solution would be to remove the drive from the enclosure and connect it to a PC via SATA directly and copy over the content with the OS of the PC. But this depends on the File System of your drive.


    Regards,
    Sven

    Hello everyone,


    this is not directly a question about RAID - it's more sort of a question about hard drive health.
    When I migrated from my old storage to the OMV-based NAS I found out that some of the files on the old hard disks weren't readable anymore. The hard drive was healthy, SMART values were fine. I assume some bits or bytes on the old hard drive surface have "died" over the recent years (I ran that storage for about 4 years) without anyone or anything noticing. That happened when I once stored files on that old storage and never read them again. If I had I would have noticed before.
    Of course I ran and run a backup from everything and luckily was able to restore the faulting files. But that backup reads files and folders from the source only when they have been modified in any way. In that particular case the files were once written to the old storage intially, then backed up by the backup routine the next day (as it was detected as new) and from that on never read again for 4 years, neither from its original location nor from the backup location. Well, that's by design I assume.
    I'm worried the live hard drive and the backup drive may have dying bits over the years. That would make a restore impossible if by chance the same files were affected.
    What I'm looking for is some sort of file health check or inspection routine. If one of the same two files (either the original one in its live location or the backed-up one) may die I have the chance to restore. So what I'm lookin for is a frequent read test of all files and folders in the live location.
    At first I thought about turning the backup to fully backup everything again and again which of course includes sort of reading the files from the source but I would like to avoid the senseless writing of huge amount of data to the backup device. Reading seems more harmless to me :)
    Any ideas are highly appreciated!


    Kind regards,
    Sven