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

Can't call method "subModel" on an undefined value at /usr/share/perl5/EBox/Samba.pm line 336 #1865

Closed
mmartinello opened this issue Feb 14, 2019 · 4 comments
Labels
Reason: Invalid Indicates that an issue or pull request is no longer relevant

Comments

@mmartinello
Copy link

After updating Zentyal from 5.1 to 6.0 the package zentyal-samba does not complete the update process due to this error:

root@server-z1:/# dpkg --configure -a
Setting up zentyal-samba (6.0.1) ...
Can't call method "subModel" on an undefined value at /usr/share/perl5/EBox/Samba.pm line 336.
dpkg: error processing package zentyal-samba (--configure):
 installed zentyal-samba package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
 zentyal-samba

I tried to uninstall and reinstall zentyal-samba but the problem is the same.
The Samba module is unusable, so this is a big problem.
I searched for this problem but I did not find anything resolutive.

Could you help me please?
Thanks!

@mmartinello
Copy link
Author

I solved purging the package zentyal-samba and reinstalling it from scratch.
But after this the user and group list in the Samba module became empty, so this is not a valid resolution.

@TravisRothlisberger
Copy link

The conditional at line 333 in Samba.pm is only used to add a service configuration for samba at TCP ports 49152 - 65535. I worked around this by temporarily modifying the conditional to if (0) { ... so that it wouldn't try and execute this. I then added the service configuration manually in the web interface. Everything seems to be OK so far.

@brunolorente brunolorente added the Reason: Invalid Indicates that an issue or pull request is no longer relevant label Jul 1, 2019
@brunolorente
Copy link
Member

Thank you for reporting this, we cannot reproduce the issue so we think that is an isolated issue.

@Neustradamus
Copy link

@mmartinello: Have you found a solution?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Reason: Invalid Indicates that an issue or pull request is no longer relevant
Projects
None yet
Development

No branches or pull requests

4 participants