Beiträge von jmccusker

Just a heads up as I didn't see this posted elsewhere. I had issues with docker compose not connecting all networks to containers. Was a new issue as of version 2.19. I have a couple containers that connect to two networks. One or the other network would connect during 'up' but not both. This is resolved in version 2.20 from what I found elsewhere. Till then I've manually connected the containers with docker network connect command.

Just hoping I can keep someone from having to dig too deep to find this issue.

I thought I'd post this in case it might help someone else out. I ran an apt-upgrade tonight on a headless mediasmart server. Towards the end of the update there was a question about grub installation. I selected the boot drive and it completed without error. The upgrade finished and I rebooted. The server seemed to not boot. I pulled it apart and connected the VGA adapter assuming that I had messed up grub somehow but found there was no network available. What was before interface eth1 was now enp2s0. I changed all references to eth1 to enp2s0 in /etc/network/interfaces and all is well after reboot. I don't recall why I hard coded the network interface before and I am not an expert at all. Maybe if this config is left blank it would've auto-config and I wouldn't have an issue. The other thing i'm not sure of is if I had changed the file before restarting if it would work without having to change after the fact.

TL;DR Upgrade changed mediasmart server network interface from eth1 to enp2s0.

I spoke too soon... Came home from work and more of the errors shown in the 3rd panel of this thread. Any idea? Should I just ignore it? Thanks

Think I might have fixed it. After running commands shown above I ran...

postfix upgrade-configuration 
postfix reload

Which returned a message about file master.cf. Nothing now in the log after login.

Thanks for the help. Now showing this, which is what it did before my fiddling.

Dec 12 07:13:49 OMV2 postfix/pickup[16235]: DF94D30A: uid=999 from=<openmediavault-webgui>
Dec 12 07:13:49 OMV2 postfix/cleanup[16253]: DF94D30A: message-id=<20181212131349.DF94D30A@OMV2.-removed-.com>
Dec 12 07:13:49 OMV2 postfix/qmgr[16236]: DF94D30A: from=<openmediavault-webgui@OMV2.-removed-.com>, size=958, nrcpt=1 (queue active)
Dec 12 07:13:49 OMV2 postfix/smtp[16255]: fatal: missing host information in server description: :25
Dec 12 07:13:50 OMV2 postfix/qmgr[16236]: warning: private/smtp socket: malformed response
Dec 12 07:13:50 OMV2 postfix/qmgr[16236]: warning: transport smtp failure -- see a previous warning/fatal/panic logfile record for the problem description
Dec 12 07:13:50 OMV2 postfix/master[16234]: warning: process /usr/lib/postfix/sbin/smtp pid 16255 exit status 1
Dec 12 07:13:50 OMV2 postfix/master[16234]: warning: /usr/lib/postfix/sbin/smtp: bad command startup -- throttling

I upgraded a mediasmart server from 3 to 4 and now there are postfix errors in the log. They seem to only appear during webgui login. I dont and never did have notifications enabled. I searched here and google but can't seem to find the settings to disable this. So far I reinstalled postfix, ran some postfix upgrade-config-etc commands. Should I just ignore it?

Thanks for the help in advance.

I have a very vanilla setup, just a SMB share on a couple drives. However, I have an identical machine with nextcloud and a more involved setup. I was using this as a guinea pig before I dive into update that machine. This was the only real issue. I'm amazed at this
software and it's stability and keeping an old ex485 alive.

Dec 11 19:14:20 OMV2 postfix/pickup[29665]: 3FBED2EE: uid=999 from=<openmediavault-webgui>
Dec 11 19:14:20 OMV2 postfix/cleanup[31133]: 3FBED2EE: message-id=<20181212011420.3FBED2EE@OMV2.localdomain>
Dec 11 19:14:20 OMV2 postfix/qmgr[24021]: 3FBED2EE: from=<openmediavault-webgui@localhost.localdomain>, size=948, nrcpt=1 (queue active)
Dec 11 19:14:20 OMV2 postfix/error[31135]: 3FBED2EE: to=<admin@localhost.localdomain>, orig_to=<admin>, relay=none, delay=0.19, delays=0.12/0.01/0/0.05, dsn=5.0.0, status=bounced (localhost.localdomain)
Dec 11 19:14:20 OMV2 postfix/cleanup[31133]: 620172F9: message-id=<20181212011420.620172F9@OMV2.localdomain>
Dec 11 19:14:20 OMV2 postfix/qmgr[24021]: 620172F9: from=<>, size=2923, nrcpt=1 (queue active)
Dec 11 19:14:20 OMV2 postfix/bounce[31136]: 3FBED2EE: sender non-delivery notification: 620172F9
Dec 11 19:14:20 OMV2 postfix/qmgr[24021]: 3FBED2EE: removed
Dec 11 19:14:20 OMV2 postfix/error[31135]: 620172F9: to=<openmediavault-webgui@localhost.localdomain>, relay=none, delay=0.09, delays=0.04/0/0/0.04, dsn=5.0.0, status=bounced (localhost.localdomain)
Dec 11 19:14:20 OMV2 postfix/qmgr[24021]: 620172F9: removed

I selected the Boot From Clonezilla Once option and my system never was able to boot again. I'm able to load the OS with the HDD in a caddie on another system. I tried install-grub and update-grub. The system will not boot when i put the HDD back in the original system. I'm not sure what the boot from clonezilla option changes so I'm not sure where to start to fix it. I'd appreciate any help. Thanks for your help and time.

Had to have HideNoAccess on in extras window of the share not FTP setting. Working now.

Thanks for your help and time!

Zitat von subzero79

well you can change the default vroot to ~ with env variable. Then home folders will work without even sharing the whole home root folder. There is a very old thread in the forum that describes how to do it. Can’t find it know.

I added OMV_PROFTPD_DEFAULTROOT="~" to the file /etc/default/openmediavault. Is that correct? It errors out when making the new conf. Sorry for my idiocy.

I saw that and will be honest that I'm not that bright with linux and env variables(yet). I'm the guy that should be using a synology but I enjoy learning new things too much. If I run a set command will that take care of it?

Yep. it was indented. I didn't even realize i could apply in the shares window. I simply put HideNoAccess on in the shares options and it works. It's still not quite what I was hoping to accomplish though. The users home folders are still showing. Would there be a way to apply this to the root?

I figured out it should be
<Directory /Users>
HideNoAccess on
</Directory>

I'm guessing this is failing because the conf generator is trying to create this before the directory exists in or because it duplicates the auto-gen <Directory /Users> section.

Like the title says. I'm on OMV 3 and when I add HideNoAccess on to the advanced options I can't apply without an error. Is this not supported? I have a root folder shared that contains Users home folders. I share the Users folder as an FTP share. Permissions are OK, I can only read/write to the correct folders. I would just like for the listing of the Users directory to only return folders that the user has permissions. This from what i read is what HideNoAccess does.

I created a user called IpCameras that the cameras use as a login. That alone should provide a home directory with read/write. I also have a group called grpIPCAMERAS. I have my acct and the cameras acct as members of that group. I created a shared folder and gave that group read/write under priveleges and ACL.

FYI - I'm not a computer engineer and am fairly new to linux and downloaded OMV for the first time yesterday. I found this thread trying to solve the same problem without being able to get my cams to work. I'll help if I can, but I'm no expert.

Try turning on ident protocol. I had to select that to get my foscam C1 to talk to the ftp server. The folder also needed to be manually created with correct permissions for the camera's acct. I wouldn't be concerned about the dot. I'm guessing that's the linux current path reference.