Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

files_sharing SMB Share getMountPoint() 6.0.4 Error #9535

Closed
grapefruitpower opened this issue Jul 9, 2014 · 18 comments
Closed

files_sharing SMB Share getMountPoint() 6.0.4 Error #9535

grapefruitpower opened this issue Jul 9, 2014 · 18 comments

Comments

@grapefruitpower
Copy link

Hi there,

we have problems with the App: file_external/files_sharing and mounted SMB shares. Users cant acces "Owncloud shared" Files if they come over SMB after updating from 6.0.3 to 6.0.4.

Test System (new installation but same Error!!!)
OS: ubuntu-server 14.04 LTS
Webserver: Apache2 PHP: 5.5.9 but also with 5.4.8
Owncloud: 6.0.4 (stable)
Focus on: App - file_external, SMB/CIFS
Description:
After mounting the SMB Share SERVER/FOLDER/ROOT with User: DOMAIN\user1. The SMB share is correctly mounted to the system. User1 has access to it. No Problem here.

User1 shares now the smb folder for user2. But user2 cant access the SMB Folder.

Apache2 Error.log - click on share from user2
[Tue Jul 08 05:10:43.282394 2014] [:error] [pid 15243] [client X.X.X.X:53123] PHP Fatal error: Call to a member function getMountPoint() on a non-object in /var/www/owncloud/apps/files_sharing/lib/sharedstorage.php on line 76, referer: http://X.X.X.X/owncloud/index.php/apps/ ... r=/Shared/[SHARED SMB FOLDER]

Some SQL info
OC_STORAGES:
ID:
home::admin
home::user1
home::user2
local::/var/www/owncloud/data/
smb::DOMAIN\user1@SERVER//FOLDER//

@PVince81
Copy link
Contributor

PVince81 commented Jul 9, 2014

@Xenopathic did you observe this as well ?

@PVince81
Copy link
Contributor

PVince81 commented Jul 9, 2014

CC @schiesbn

@RobinMcCorkell
Copy link
Member

@PVince81 No, I haven't used sharing in a while

@grapefruitpower
Copy link
Author

in Owncloud 7 RC1 is a new version of files_sharing and files_external.
0.5.2...
in OC6.0.4 its just 0.3.5. its a huge jump or? Is there a way to use 0.5.2 in Owncloud 6.0.4? Or are the difference to huge to deploy?

@PVince81
Copy link
Contributor

I don't know why the version number was bumped that high, but I'd recommend against trying to copy the new version to OC 6.0.4.

But if there's a specific patch/fix we could try and backport it.
Need to find it first...

@PVince81
Copy link
Contributor

@grapefruitpower I assume that it worked for you in 6.0.3 and broke in 6.0.4.
Also did it work in OC 7 RC 2 ?

I'll try and bisect between 6.0.3 and 6.0.4 to see what broke it.

@PVince81
Copy link
Contributor

As user1 I have shared "/smb/subdir" with user2.
On OC 6.0.3 user2 can access "/Shared/subdir" but not on OC 6.0.4.

This bug is confirmed.

@PVince81
Copy link
Contributor

And here we go, bisect result: this is the first breaking commit 9a5da34

Looks like it's the one that obfuscated the password.
Possibly a side-effect 😦

@PVince81
Copy link
Contributor

I debugged it a bit and found out that the mount points of "user1" aren't loaded properly when accessing the share from "user2".
The issue is that it uses the current user "user2" to search for mount.json instead of using the owner "user1".

I believe there has been a similar fix on OC 7 which will need backporting.

@PVince81
Copy link
Contributor

@grapefruitpower fix is here: #9635

Can you help testing ?

@PVince81
Copy link
Contributor

@karlitschek @craigpg setting to OC 6.0.5

@PVince81 PVince81 added this to the ownCloud 6.0.5 milestone Jul 15, 2014
@PVince81
Copy link
Contributor

Note: this is a regression from OC 6.0.3

@RobinMcCorkell
Copy link
Member

Ah, forgot I fixed this in master.

@grapefruitpower
Copy link
Author

it worked well. Thanks a lot. :-)

@PVince81
Copy link
Contributor

Thanks for confirming. 😄

@marxistvegan
Copy link

Hey folks, I see that this is closed, in a dev environment i had upgraded from 6.0.3 to 6.0.4 to which is where i noticed this problem. I was not sure if I needed to downgrade before upgrading again, so I actually just upgraded the 6.0.4 to 7.0.1 but the problem still exists
What is the recommended solution/path?

@PVince81
Copy link
Contributor

@marxistvegan can you confirm that you have the same setup, used the same steps and same log entries ? If the issue still exists for you it might be a different issue with similar symptoms.

@marxistvegan
Copy link

@PVince81 false positive we had two dev environments and i was using an old one that was not resolved this seems resolved as of now sorry for raising the concern

@lock lock bot locked as resolved and limited conversation to collaborators Aug 17, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants