Beiträge von kalleyne

    OMV 3.0.81


    Earlier today, I used the GUI to remove a folder that I was sharing via Samba. Then, through the command line I destroyed the zpool and created a new one. This worked and I proceed to create a new folder which I shared through Samba.


    I looked at the System Logs. Every few seconds there is an alert from monit about the old zpool tank0 (which was destroyed) and the old filesystem - vol0 which was also destroyed.


    monit[2729]: Device /tank0/vol0 not found in /etc/mtab
    monit[2729]: 'fs_tank0_vol0' unable to read filesystem '/tank0/vol0' state


    How do I correct this so that the alerts stop and also to update the system to remove these old, no-longer-applicable references?
    Thanks.

    Updating this thread...


    We have a commercial interest in using OMV for a variety of projects. We are at the point where some coordination between the groups would be helpful. Understandably, Volker Theile is a busy guy but we believe that it would be important to make contact and present introductions at this stage so that he will be aware of our basic plans and activities.


    What's the best way to reach out to Volker?


    Thanks.

    subzero79. Good call.


    Yes, you are correct. The drive was filled at 100%. A quick removal of some huge files and web GUI admin work again....got into the system.


    But I had another system a couple days ago, OMV running in a KVM based VM where I had a similar situation. It was a fresh install of OMV, no patches applied....so the disk was practically empty. Could not get into the web GUI. Don't have this VM any longer but I'll monitor the situation and see if it occurs again.


    Thanks much for the help.

    Ok, I have a failing system here:


    Here is a slightly modified version of the tailed auth.log:


    Feb 25 12:04:16 host openmediavault-webgui[15215]: Authorized login from ::ffff:192.168.9.151 [username=admin, user-agent=Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/48.0.2564.116 Chrome/48.0.2564.116 Safari/537.36]
    Feb 25 12:04:16 host ool openmediavault-webgui[15215]: Unknown or unsupported timezone [tz=US/Central]
    Feb 25 12:04:41 host sshd[15228]: Accepted password for root from 192.168.9.151 port 36911 ssh2
    Feb 25 12:04:41 host sshd[15228]: pam_unix(sshd:session): session opened for user root by (uid=0)
    Feb 25 12:05:01 host CRON[15242]: pam_unix(cron:session): session opened for user root by (uid=0)
    Feb 25 12:05:01 host CRON[15243]: pam_unix(cron:session): session opened for user root by (uid=0)
    Feb 25 12:05:01 host CRON[15243]: pam_unix(cron:session): session closed for user root
    Feb 25 12:05:01 host CRON[15242]: pam_unix(cron:session): session closed for user root
    Feb 25 12:07:27 host passwd[15251]: pam_unix(passwd:chauthtok): password changed for admin
    Feb 25 12:07:42 host openmediavault-webgui[15252]: Authorized login from ::ffff:192.168.9.151 [username=admin, user-agent=Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/48.0.2564.116 Chrome/48.0.2564.116 Safari/537.36]
    Feb 25 12:07:43 host ool openmediavault-webgui[15252]: Unknown or unsupported timezone [tz=US/Central]
    Feb 25 12:07:49 host ool openmediavault-webgui[15252]: Unknown or unsupported timezone [tz=US/Central]
    Feb 25 12:07:49 host openmediavault-webgui[15252]: Authorized login from ::ffff:192.168.9.151 [username=admin, user-agent=Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/48.0.2564.116 Chrome/48.0.2564.116 Safari/537.36]
    Feb 25 12:07:49 host ool openmediavault-webgui[15252]: Unknown or unsupported timezone [tz=US/Central]


    So it would appear that Authorized logins are working. But perhaps there is a problem with "unsupported timezone"?

    We seeing a similar problem here. Between myself and another associate, we have seen this happen multiple times on multiple installs of OMV. For some odd reason the web-GUI admin password gets lost or erased so we are forced to use omv-firstaid to reset the admin password. However, it would appear that the omv-firstaid admin password reset is not completely reliable and very often the reset never happens. So, we are effectively locked out of the web-GUI. The quickest solution for us is to re-install OMV and apply patches right way. But as we approach production deadlines, re-installing is not an ideal solution. The passwords that we use for our testing are simple and don't contain any special characters.


    Hope that someone has some ideas to fix this issue. Thanks.