Ticket #3085 (closed defect: worksforme)
Can't call method 'elementByName' on an undefined value
| Reported by: | info@… | Owned by: | jacalvo@… |
|---|---|---|---|
| Milestone: | 2.2 | Component: | base |
| Severity: | normal | Keywords: | |
| Cc: |
Description (last modified by jacalvo@…) (diff)
Hello,
i am using the lates iso of RC 2.2 of zentyal.
The following steps i wanted to do:
- adding a new user
- customizing the needs of quota and permission inside of the "user tab"
- i apply "save settings" (red, right above command)
After a few seconds i got the erroy: "Can't call method 'elementByName' on an undefined value".
I think, it is possible that this error message comes from LDAP (it sounds like an ldap object).
It is very important to use the new user. Actually this is not possible.
But, this is why i am wondering, other users added on the same way could i add without this error and they are functionally.
thanks for your answers and/or workarround
Stephan Kurth IT Senior Architekt Stephan Kurth IT-Consulting
Error
Can't call method 'elementByName' on an undefined value
Trace
Can't call method 'elementByName' on an undefined value at /usr/share/perl5/EBox/OpenVPN/Daemon.pm line 98.
Attachments
Change History
Changed 22 months ago by anonymous
-
attachment
zentyal.log
added
comment:1 Changed 22 months ago by jacalvo@…
- Description modified (diff)
- Summary changed from Bug report from Zentyal Server to Can't call method 'elementByName' on an undefined value
comment:2 Changed 22 months ago by jamor@…
Hello Stephan, isnt a LDAP problem but a problem related with backend configuration. Maybe it is corrupt.
It seems to originate in the openvpn module. Could you remove temporally any server/client do you have in this module, save changes and try again?. Then if it is working you could reconfigure openvpn.
comment:3 Changed 21 months ago by jacalvo@…
- Status changed from new to closed
- Resolution set to worksforme
As javier says, this is most probably a data corruption and we are not able to reproduce it.
Please reopen if you are sure it's a bug in the Zentyal code and you can provide detailed steps on how to reproduce it. Thanks.
zentyal.log