When processing the Make Develop command the configuration ends at "cd: 1: can't cd to ./extensions/joomla". There is in fact no Joomla directory in the extensions directory of this distribution. Can you assist?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Okay, I got past that one. Now getting this error when executing any command against the user script:
Traceback (most recent call last):
File "./user", line 13, in <module>
from suitepy import cli
ImportError: No module named suitepy
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm not sure why that would happen because the development make target is supposed to call the suitepy-development target. Anyway, you can cd into the suitepy dir and run 'sudo python setup.py develop' to add suitepy to the Python path.
Sorry for the installation trouble. We're hoping to have time to clean this up a bit in the not-too-distant future.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Got past that error, thanks. New error when adding user below (FYI-slapd is running):
root@xxxx-hosting:/opt/datasync-suite/bin# ./user add
Traceback (most recent call last):
File "./user", line 19, in <module>
cli.process_user(args)
File "/opt/suite/suitepy/suitepy/cli.py", line 451, in process_user
controller.configurePlugins()
File "/opt/suite/suitepy/suitepy/server/controller.py", line 24, in configurePlugins
libdatasync.plugin.load(config, config)
File "/opt/suite/lib/libdatasync/libdatasync/plugin.py", line 85, in load
implementation.initialize(config)
File "/opt/suite/suitepy/suitepy/core/plugins/ldapservice.py", line 22, in initialize
_connect()
File "/opt/suite/suitepy/suitepy/core/plugins/ldapservice.py", line 27, in _connect
_connection.simple_bind_s(_config, _config)
File "/usr/lib/python2.5/site-packages/python_ldap-2.3.11-py2.5-linux-i686.egg/ldap/ldapobject.py", line 206, in simple_bind_s
msgid = self.simple_bind(who,cred,serverctrls,clientctrls)
File "/usr/lib/python2.5/site-packages/python_ldap-2.3.11-py2.5-linux-i686.egg/ldap/ldapobject.py", line 200, in simple_bind
return self._ldap_call(self._l.simple_bind,who,cred,EncodeControlTuples(serverctrls),EncodeControlTuples(clientctrls))
File "/usr/lib/python2.5/site-packages/python_ldap-2.3.11-py2.5-linux-i686.egg/ldap/ldapobject.py", line 96, in _ldap_call
result = func(*args,**kwargs)
ldap.SERVER_DOWN: {'desc': "Can't contact LDAP server"}
Would I be better of to wait until this distro has been debugged a little more? I am just coming back to the forum with about a third of the issues I'm encountering, but I still hate to be a pest with a free piece of software.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I believe the bin/user script pulls the LDAP server configuration from etc/portal.yml, so double check that file exists (you can copy it from etc/portal.yml.in) and that the LDAPService and AuthenticationService sections point to localhost.
You can also run the slapcat command to make sure the LDAP server has been populated.
Feel free to continue asking questions. It let's us really know our installation pain points so we can plan where to make things easier.
I haven't done a lot of from-scratch installs yet, so my colleagues can help if I get stuck on a question.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
When processing the Make Develop command the configuration ends at "cd: 1: can't cd to ./extensions/joomla". There is in fact no Joomla directory in the extensions directory of this distribution. Can you assist?
We've dropped support for Joomla, but it looks like we haven't cleaned things up entirely.
Edit extensions/Makefile and remove 'joomla-dev' from the development make target on line 3.
Looks like there were other things that had not been cleaned up too, like Quickbooks.
I cant get past this error:
cd ./testing/integration && sudo python setup.py develop
Okay, I got past that one. Now getting this error when executing any command against the user script:
Traceback (most recent call last):
File "./user", line 13, in <module>
from suitepy import cli
ImportError: No module named suitepy
I'm not sure why that would happen because the development make target is supposed to call the suitepy-development target. Anyway, you can cd into the suitepy dir and run 'sudo python setup.py develop' to add suitepy to the Python path.
Sorry for the installation trouble. We're hoping to have time to clean this up a bit in the not-too-distant future.
Got past that error, thanks. New error when adding user below (FYI-slapd is running):
root@xxxx-hosting:/opt/datasync-suite/bin# ./user add
Traceback (most recent call last):
File "./user", line 19, in <module>
cli.process_user(args)
File "/opt/suite/suitepy/suitepy/cli.py", line 451, in process_user
controller.configurePlugins()
File "/opt/suite/suitepy/suitepy/server/controller.py", line 24, in configurePlugins
libdatasync.plugin.load(config, config)
File "/opt/suite/lib/libdatasync/libdatasync/plugin.py", line 85, in load
implementation.initialize(config)
File "/opt/suite/suitepy/suitepy/core/plugins/ldapservice.py", line 22, in initialize
_connect()
File "/opt/suite/suitepy/suitepy/core/plugins/ldapservice.py", line 27, in _connect
_connection.simple_bind_s(_config, _config)
File "/usr/lib/python2.5/site-packages/python_ldap-2.3.11-py2.5-linux-i686.egg/ldap/ldapobject.py", line 206, in simple_bind_s
msgid = self.simple_bind(who,cred,serverctrls,clientctrls)
File "/usr/lib/python2.5/site-packages/python_ldap-2.3.11-py2.5-linux-i686.egg/ldap/ldapobject.py", line 200, in simple_bind
return self._ldap_call(self._l.simple_bind,who,cred,EncodeControlTuples(serverctrls),EncodeControlTuples(clientctrls))
File "/usr/lib/python2.5/site-packages/python_ldap-2.3.11-py2.5-linux-i686.egg/ldap/ldapobject.py", line 96, in _ldap_call
result = func(*args,**kwargs)
ldap.SERVER_DOWN: {'desc': "Can't contact LDAP server"}
Would I be better of to wait until this distro has been debugged a little more? I am just coming back to the forum with about a third of the issues I'm encountering, but I still hate to be a pest with a free piece of software.
I believe the bin/user script pulls the LDAP server configuration from etc/portal.yml, so double check that file exists (you can copy it from etc/portal.yml.in) and that the LDAPService and AuthenticationService sections point to localhost.
You can also run the slapcat command to make sure the LDAP server has been populated.
Feel free to continue asking questions. It let's us really know our installation pain points so we can plan where to make things easier.
I haven't done a lot of from-scratch installs yet, so my colleagues can help if I get stuck on a question.