Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Topics - peterr

Pages: [1]
I have just gone back to playing around with event monitoring and have rss and jabber up and running.
Rss was fine to set up once I figured  out the address you enter as channel link, in the config, was not the address you use to access the feed. A little comment in the help link might have been useful but it became obvious when I pressed the syndicate button (on the basis of 'I wonder what that does?').

Jabber was more of a challenge!
I started out trying to use an existing user on our google apps domain - no luck as you enter a server name and user name but eBox then assumes the jabber id is user_name@server_name when it is user_name@domain_name.
Next try, I installed the Jabber server and tried to subscribe a user specific for the server (I have failed at this before but thought I would give it another go)
So I then activated jabber for a user and set them as the sender of alerts to me, at my google apps address - nothing came through even though jabber is set to use other servers.
Finally I activated a jabber account for me and had alerts sent to that - works if I am on site, which is fine.

Now I am left with 2 problems (the point of this post)
The state monitor is constantly sending out 'ebox up and running' messages - is there any way to stop them and have it only send out messages when it is in the process of shutting down (eg UPS has run down)? For now I am turning this one off.
I also tried the system load monitor - that drove me mad!!
I added a new threshold and entered 0.6 in the box Warning maximum: thinking that I could easily push the server over this to test it out. I was expecting 'If the value is greater than this value and less than failure maximum a warn event is sent' to mean I would be alerted if the system load went over 0.6. What I got was a constant stream of messages telling me the load was below the Warning maximum - not what I wanted at all.
The fee disk space watcher does not keep telling me I have space left - I only get a warning when I run out of space, which is what I want and expected to happen.

Any Ideas on fixing the threshold settings or am I doing something wrong with them?
Could the state monitor be selective about what it sends out?

Installation and Upgrades / Events - Jabber subscription failed
« on: February 11, 2010, 12:37:40 pm »
I have running jabber server and two other ebox servers and I want to enable the event dispatcher to IM any events that occur.
I tied setting up the dispatcher with an existing ebox user but the messages come from that user with no indication which server they relate to.  So I chaged teh settings to use a user related to the server e.g. admin.web or then I ticked the box - subscribe
The jabber server name is set the name of my server
The port is set to 5222 - that worked with a existing user
I filled in a password
and saved the settings
When I activated the jabber event dispatcher it told me 'subscription failed'

Any idea why?

Jabber is set up with ssl optional

Installation and Upgrades / samba failure on 1.4
« on: February 05, 2010, 10:04:13 am »
I was trying to upgrade from 1.3 to 1.4 but gave up and just reinstalled.
I have a working master and two working slaves - yesterday I set up file sharing on one slave, all seemed to go well and I got as far as creating a share with one group having read-only access and another group having administrator rights.
Today I started to find the problems - I then found there was a samba update available so I installed that this morning and started checking what did or did not work.
On my linux computer I have my username and password stored in my samba settings - this used to let me browse the folders on the old ebox server (those I was allowed to anyway).
Now I can enter the samba server but can not access the share I created (I am in the group with admin rights and also in the read-only groups) and I can not see my own shared folder. I get prompted for a username and password - entering my username and password does not give me access.
Looking in my user settings (on the ebox server) I noticed I do not have administrator rights on PDC/file share so I ticked the box and clicked change
Code: [Select]
A really nasty bug has occurred
Unknown error at EBox::UsersAndGroups::addUserToGroup Referral received
Unknown error at EBox::UsersAndGroups::addUserToGroup Referral received at /usr/share/perl5/EBox/ line 712
EBox::Ldap::_errorOnLdap('Net::LDAP::Modify=HASH(0xa91d38c)', 'HASH(0xa8cb77c)') called at /usr/share/perl5/EBox/ line 373
EBox::Ldap::modify('EBox::Ldap=HASH(0xa7044b0)', 'cn=Domain Admins,ou=Groups,dc=web,dc=dcmc', 'HASH(0xa8cb77c)') called at /usr/share/perl5/EBox/ line 1732
EBox::UsersAndGroups::addUserToGroup('EBox::UsersAndGroups=HASH(0xa08fadc)', 'peter.roots', 'Domain Admins') called at /usr/share/perl5/EBox/ line 844
EBox::Samba::setAdminUser('EBox::Samba=HASH(0x9a3efe0)', 'peter.roots', 'yes') called at /usr/share/perl5/EBox/CGI/Samba/ line 79
EBox::CGI::Samba::ActiveSharing::_user('EBox::CGI::Samba::ActiveSharing=HASH(0xa8cfc38)') called at /usr/share/perl5/EBox/CGI/Samba/ line 86
EBox::CGI::Samba::ActiveSharing::_process('EBox::CGI::Samba::ActiveSharing=HASH(0xa8cfc38)') called at /usr/share/perl5/EBox/CGI/ line 262
EBox::CGI::Base::run('EBox::CGI::Samba::ActiveSharing=HASH(0xa8cfc38)') called at /usr/share/perl5/EBox/CGI/ line 120
EBox::CGI::Run::run('EBox::CGI::Run', 'Samba/ActiveSharing', 'EBox') called at /usr/share/ebox/cgi/ebox.cgi line 19
ModPerl::ROOT::ModPerl::Registry::usr_share_ebox_cgi_ebox_2ecgi::handler('Apache2::RequestRec=SCALAR(0xa90d1c4)') called at /usr/lib/perl5/ModPerl/ line 204
eval {...} called at /usr/lib/perl5/ModPerl/ line 204
ModPerl::RegistryCooker::run('ModPerl::Registry=HASH(0xa84e7f0)') called at /usr/lib/perl5/ModPerl/ line 170
ModPerl::RegistryCooker::default_handler('ModPerl::Registry=HASH(0xa84e7f0)') called at /usr/lib/perl5/ModPerl/ line 31
ModPerl::Registry::handler('ModPerl::Registry', 'Apache2::RequestRec=SCALAR(0xa90d1c4)') called at -e line 0
eval {...} called at -e line 0
Currently I have no shares other than the one I created under filesharing>shares so I went to userandgroups>groups and tried to edit a group (created on the master before I set up the file share slave). One group is for everyone and the others are more limited - the attempt to edit any group (wanted to add a file share to each one) gave this
Code: [Select]
A really nasty bug has occurred
Can't call method "get_value" on an undefined value
Can't call method "get_value" on an undefined value at /usr/share/perl5/EBox/ line 740.
So basically samba is not working properly - to the extent of being able to see the server and some shared folders but that is about it, can't enter any of them.
Any ideas where to go next?
All 3 servers are up to date as of this morning

Installation and Upgrades / 1.4-rc1 install failure
« on: February 02, 2010, 12:40:07 pm »
I have just installed 1.4rc1 from the cd image
Currently I have 3 servers running 1.3.16 a master ldap and web server a slave with samba and egroupware and another slave with jabber and asterisk.
I was replacing the jabber/asterisk server
All went well to begin with - I installed using teh simple option from the cd and then opted for the pick packages rather than the pick function option for the final stage.
I installed U&G jabber and asterisk with backup, monitor and software.
From the web interface I configured the firewall to allow ldap
I activated network, firewall, backup, events, logs and monitor and then saved - got a warning that firewall and logs had unsaved settings but were not activated.  I checked in module status and they both were activated.
I then configured U&G setting as slave and entering the ip of the master and the password.
When I saved settings I again was told firewall and logs had unsaved settings but were not activated.
I then activated U&G and got the following
Code: [Select]
A really nasty bug has occurred
Failed to enable: Replication failed
Failed to enable: Replication failed at /usr/share/perl5/EBox/CGI/ServiceModule/ line 74
EBox::CGI::ServiceModule::ConfigureModuleController::_process('EBox::CGI::ServiceModule::ConfigureModuleController=HASH(0xb5...') called at /usr/share/perl5/EBox/CGI/ line 262
EBox::CGI::Base::run('EBox::CGI::ServiceModule::ConfigureModuleController=HASH(0xb5...') called at /usr/share/perl5/EBox/CGI/ line 120
EBox::CGI::Run::run('EBox::CGI::Run', 'ServiceModule/ConfigureModuleController', 'EBox') called at /usr/share/ebox/cgi/ebox.cgi line 19
ModPerl::ROOT::ModPerl::Registry::usr_share_ebox_cgi_ebox_2ecgi::handler('Apache2::RequestRec=SCALAR(0xafd9780)') called at /usr/lib/perl5/ModPerl/ line 204
eval {...} called at /usr/lib/perl5/ModPerl/ line 204
ModPerl::RegistryCooker::run('ModPerl::Registry=HASH(0xb530f74)') called at /usr/lib/perl5/ModPerl/ line 170
ModPerl::RegistryCooker::default_handler('ModPerl::Registry=HASH(0xb530f74)') called at /usr/lib/perl5/ModPerl/ line 31
ModPerl::Registry::handler('ModPerl::Registry', 'Apache2::RequestRec=SCALAR(0xafd9780)') called at -e line 0
eval {...} called at -e line 0
2 questions
1) any idea what went wrong?

2) Could I have upgraded my 1.3 installs to 1.4? I notice that 1.4 is still using teh same repository as 1.3 but my 1.3 installs say they are fully up to date

Installation and Upgrades / ebox 1.3.16 and asterisk
« on: January 28, 2010, 09:12:16 am »
Just upgraded to 1.3.16 on my asterisk/jabber server and the upgrade failed due to dependancy probelms (error not helpful enough to say which dependancy problems though)
Basically dahdi is not getting configured and this killed asterisk.  After a reboot I tried installing dahdi again and I got this.
Code: [Select]
dahdi-modules-ebox is already the newest version.
The following packages were automatically installed and are no longer required:
Use 'apt-get autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
3 not fully installed or removed.
After this operation, 0B of additional disk space will be used.
Setting up dahdi (1:2.2.0-1~ebox0~hardy0) ...
Loading DAHDI hardware modules:
FATAL: Module dahdi not found.
   dahdi: error   dahdi_dummy: error   dahdi_transcode: error
Error: missing /dev/dahdi!
invoke-rc.d: initscript dahdi, action "start" failed.
dpkg: error processing dahdi (--configure):
 subprocess post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of asterisk:
 asterisk depends on dahdi; however:
  Package dahdi is not configured yet.
dpkg: error processing asterisk (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of ebox-asterisk:
 ebox-asterisk depends on asterisk; however:
  Package asterisk is not configured yet.
dpkg: error processing ebox-asterisk (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
E: Sub-process /usr/bin/dpkg returned an error code (1)
According to my QuteCom client I am on line with sip. according to the dashboard I and 2 other clients are online with sip but VoIP is not apparently running (according to dashboard)
Starting VoIP via dashboard worked but all the logged in clients got kicked off (dashboard) but were still on line in QuteCom
so seem to be working but with a system not fully configured.
(I did the initial upgrage via ebox interface, which failed, so I then repeated it via apt-get)

Installation and Upgrades / dahdi-tools and asterisk meetings
« on: January 07, 2010, 01:22:01 pm »
Using ebox 1.3.12
I thought I would try out asterisk meetings but found I needed dahdi-linux and dahdi-tools to do it

sudo apt-get install dahdi-linux dahdi-tools tells me that dahdi-linux is already installed as the latest version but dahdi-tools can not be found
I tried enabling backports and partner archives but still dahdi-tools was not found - any idea where I can get this?


Installation and Upgrades / ebox 1.3.12 no longer able to log in
« on: January 07, 2010, 12:36:52 pm »
Until today I had 3 ebox servers running in master/slave mode.
Previously egroupware worked fine on one of them but after an upgrade (then a reinstall) egroupware failed due to the mail server not running.
A upgrade today fixed that and I was able to get the mail server running and start egroupware then get all my users setup with egroupware.
While doing this I noticed that file sharing had stopped working although dashboard showed all the services were up and running.
I thought I would restart the server and see if this sorted it out - when I tried to log in through the web interface I got this -

A really nasty bug has occurred
Can't call method "bind" on an undefined value
Can't call method "bind" on an undefined value at /usr/share/perl5/EBox/ line 215.

The other 2 servers, which I also updated today, are running fine - one just has users and groups running (as master) and a web server.  The other has jabber and asterisk and is a slave to the web server.

My failed server is (or was) running egroupware, file share and PDC - file share and PDC were working fine before I upgraded but I had not checked after the upgrade if PDC still worked.

All the servers are running the monitor and software modules and I hope to be able to use the PDC machine to authenticate linux machines though this has not yet worked (perhaps as it is a slave not a master ldap server).

Any suggestions where to go next?

I have been trying for a long time to authenticate a linux box against a ebox server using ldap (a long ongoing discussion on the emai list). so far no success (ebox1.3.10)

The problem seems to be one of binding to the ldap server - my ubuntu or kubuntu machines seem to link to the server ok then try to bind with the uid of the user trying to authenticate.  Back comes a failure as can't bind to ldap server: uid=my user,ou=Users,dc=mydomain.

As a distraction I went back to looking at the egroupware part of the system - up to now I have been playing with groupdav to read the address book but thought that ldap would be a better alternative. Why? Because the ebox/egroupware accounts are stored in ldap and the contacts are in sql - ok (sort of) if you access egroupware by the web interface but you can't see both account holders and contacts at the same time.  In a client like Kontact you need access via groupdav and ldap to see all your addresses.
Today i installed egroupware-ldap and switched my egroupware over to store contacts in ldap
When I tried to look at the address book in egroupware, what should happen but can't bind to ldap server: uid=my user,ou=Users,dc=mydomain

So it seems there is a fundamental problem of a user binding to the ldap server in order to interogate it, either because that user wants to authenticate against the server or just to look up information in it.
Ebox itself seems to always use its own special user/password to bind, which is fine but how do I change things so that an ordinary user can bind with their password?
Without this it seems impossible to authenticate against ebox and solving this would probably mean egroupware could use ldap for contacts as well

If anyone has any idea how to change access rights on ebox, without leaving it wide open to someone mucking up the database by mistake I would love to hear from you ;)

Installation and Upgrades / ldap passwords and master/slave
« on: November 02, 2009, 01:09:56 pm »
Can someone help me understand what is going as I am confused over how the passwords work with ldap?
I have successfully wrecked several servers already so I have had lots of experience now at installing ebox1.3!!
Until recently I had 3 ebox servers running with one master and 2 slaves - the slaves were linked using the password stored in /var/lib/ebox/conf/ebox-ldap.passwd not the ldap admin password entered during installation.
What are these two passwords, why are they different and when is one used rather than the other?  This bit really puzzles me - I am quite happy to use this one here and that one there but would like to know why (I know, curiosity killed the cat).

I was just trying to get a linux client to authenticate against the ldap master (worked ok with a windows client) but it did not work - big mistake, I ran dpkg-reconfigure slapd to find out if I was using the right dn.  I was but this killed the ldap!  I reinstalled ubuntu and ebox (never managed to clear out usersandgroups without a full reinstall of the server) and this time round my server asked about linking to a ldap server for authentication (never done that before). I ignored this and carried on and ended up with a working usersandgroups on my new master but now the slaves don't sync to it.  I looked in /var/lib/ebox/conf to see if the password was different to last time but I have no ebox-ldap.passwd this time.

I decided to try dpkg-reconfigure slapd again and see what happened - Yup it broke usersandgroups again! oops!

So, any idea how to replace a busted ldap master and get it to sync with 2 existing slaves?

ps (I am still smiling, I know this is only beta software)
pps (I guess I am going to know a lot about ebox installation by the time I finish)

Installation and Upgrades / 1.3 usersandgroups failure
« on: October 26, 2009, 09:55:50 am »
I have not touched usersandgroups for a little while on two ebox servers so I don't know when this problem developed but this morning I ran an update and tried usersandgroups afterwards.  The first difficulty I encounterd was I tried to authenticate a linux box with ebox - that failed last week and I tried again today.  This lead me to look at users and that is when I ran into problems this morning.
First I noticed on a ebox that was already running usersandgroups that all my users, when I went to edit, showed asterisk and jabber as disabled and egroupware showed as default profile even on my account which was set to an admin profile I had created.
If I tried to change asterisk, for example to enabled, I got this
A really nasty bug has occurred
Unknown error at EBox::AsteriskLdapUser::_addUser objectClass: value #0 invalid per syntax
Unknown error at EBox::AsteriskLdapUser::_addUser objectClass: value #0 invalid per syntax at /usr/share/perl5/EBox/ line 637
EBox::Ldap::_errorOnLdap('Net::LDAP::Modify=HASH(0xa7d5a3c)', 'HASH(0x969a57c)') called at /usr/share/perl5/EBox/ line 344
EBox::Ldap::modify('EBox::Ldap=HASH(0x993d288)', 'uid=peter.roots,ou=Users,dc=dcmc', 'HASH(0x969a57c)') called at /usr/share/perl5/EBox/ line 119
EBox::AsteriskLdapUser::_addUser('EBox::AsteriskLdapUser=HASH(0xa979b54)', 'peter.roots') called at /usr/share/perl5/EBox/ line 243
EBox::AsteriskLdapUser::setHasAccount('EBox::AsteriskLdapUser=HASH(0xa979b54)', 'peter.roots', 1) called at /usr/share/perl5/EBox/CGI/Asterisk/ line 48
EBox::CGI::Asterisk::AsteriskUserOptions::_process('EBox::CGI::Asterisk::AsteriskUserOptions=HASH(0xa98ec6c)') called at /usr/share/perl5/EBox/CGI/ line 261
EBox::CGI::Base::run('EBox::CGI::Asterisk::AsteriskUserOptions=HASH(0xa98ec6c)') called at /usr/share/perl5/EBox/CGI/ line 120
EBox::CGI::Run::run('EBox::CGI::Run', 'Asterisk/AsteriskUserOptions', 'EBox') called at /usr/share/ebox/cgi/ebox.cgi line 19
ModPerl::ROOT::ModPerl::Registry::usr_share_ebox_cgi_ebox_2ecgi::handler('Apache2::RequestRec=SCALAR(0xa783684)') called at /usr/lib/perl5/ModPerl/ line 204
eval {...} called at /usr/lib/perl5/ModPerl/ line 204
ModPerl::RegistryCooker::run('ModPerl::Registry=HASH(0xa7a45e0)') called at /usr/lib/perl5/ModPerl/ line 170
ModPerl::RegistryCooker::default_handler('ModPerl::Registry=HASH(0xa7a45e0)') called at /usr/lib/perl5/ModPerl/ line 31
ModPerl::Registry::handler('ModPerl::Registry', 'Apache2::RequestRec=SCALAR(0xa783684)') called at -e line 0
eval {...} called at -e line 0

I get a similar error if I try to add a new user (I have not tried to delete one though)

my jabber and asterisk clients think I am online and dashboard thinks one other user is online with asterisk (though I can't get at his computer just now to check if I can communicate with him) even all the accounts are currently shown as disabled.

On another ebox machine, that had usersandgroups installed but not activated I tried to activate it and failed.  I uninstalled uag, reinstalled it and tried to activate it again and got this
A really nasty bug has occurred
Failed to enable: Can't connect to LDAP server
Failed to enable: Can't connect to LDAP server at /usr/share/perl5/EBox/CGI/ServiceModule/ line 74
EBox::CGI::ServiceModule::ConfigureModuleController::_process('EBox::CGI::ServiceModule::ConfigureModuleController=HASH(0xa3...') called at /usr/share/perl5/EBox/CGI/ line 261
EBox::CGI::Base::run('EBox::CGI::ServiceModule::ConfigureModuleController=HASH(0xa3...') called at /usr/share/perl5/EBox/CGI/ line 120
EBox::CGI::Run::run('EBox::CGI::Run', 'ServiceModule/ConfigureModuleController', 'EBox') called at /usr/share/ebox/cgi/ebox.cgi line 19
ModPerl::ROOT::ModPerl::Registry::usr_share_ebox_cgi_ebox_2ecgi::handler('Apache2::RequestRec=SCALAR(0x8f45ab8)') called at /usr/lib/perl5/ModPerl/ line 204
eval {...} called at /usr/lib/perl5/ModPerl/ line 204
ModPerl::RegistryCooker::run('ModPerl::Registry=HASH(0xa3b1e50)') called at /usr/lib/perl5/ModPerl/ line 170
ModPerl::RegistryCooker::default_handler('ModPerl::Registry=HASH(0xa3b1e50)') called at /usr/lib/perl5/ModPerl/ line 31
ModPerl::Registry::handler('ModPerl::Registry', 'Apache2::RequestRec=SCALAR(0x8f45ab8)') called at -e line 0
eval {...} called at -e line 0

The first server was set a the ldap master and has been working fine the second I was trying to set up as a master (later plan was to reinstall the old one and set as slave).
Under users the mode of the second server is set to master, the ldap password is present the AD user is set to eboxadsync (I did not do that, that appeared after I reinstalled uag). I have tried reentering the ldap password in case this had messed up somewhere

I am guessing these two issues are somehow related to each other, presumably due to a problem in the ldap server, but have no idea where to go from here.

Incidentally the egroupware server (on first ebox server) is working but any attempt to alter a user results in something like this
ldap_modify(,,ou=Users,dc=dcmc,Array ( [objectclass] => Array (
  • => inetorgperson [1] => posixaccount [2] => passwordholder [3] => asterisksipuser [4] => asteriskvoicemail [5] => eboxegwaccount [6] => userjabberaccount [7] => couriermailaccount [8] => usereboxmail [9] => top [10] => person [11] => organizationalperson [12] => shadowaccount ) [uidnumber] => 2006 [uid] => [gidnumber] => 1901 [givenname] => Finance [sn] => Office [mail] => [cn] => Finance Office [shadowexpire] => Array ( ) ) ) Invalid syntaxldap_modify(,'cn=__USERS__,ou=Groups,dc=dcmc',Array ( [memberuid] => Array (
  • => peter.roots [1] => ) ) ))

Should this be of any help in tracking down what is going wrong


Installation and Upgrades / UserCorner refused connection
« on: October 15, 2009, 11:25:11 am »
User corner seems to be having problems at https://ebox:8888 using ebox1.3
I get asked for a username and password then I get this
Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator, webmaster@localhost and inform them of the time the error occurred, and anything you might have done that may have caused the error.

More information about this error may be available in the server error log.

I have just updated my system and got masses of errors along the lines of
Setting up ebox-webserver (1.3.6-0ubuntu1~ppa1~hardy1) ...
WARNING **: Owner of /tmp/orbit-ebox-usercorner is not the current user
WARNING **: Owner of /tmp/orbit-ebox-usercorner is not the current user

** (gconftool-2:26209): WARNING **: Owner of /tmp/orbit-ebox-usercorner is not the current user

** (gconftool-2:26210): WARNING **: Owner of /tmp/orbit-ebox-usercorner is not the current user

 * Restarting eBox module: webserver                                     [ OK ]

A farily reasonable error as the owner of this folder is ebox-usercorner and the update is being run as root (sudo) but is this in anyway connected to the reason I can not access usercorner?

Installation and Upgrades / ldap master slave problem
« on: October 13, 2009, 12:35:35 pm »
I have just installed a second ebox1.3 server (web and usersandgroups)
When I set the usersandgroups to slave mode and tried to activate the module it failed.  Initally I had an error about a non existant apparmor file (got rid of this by creating the file)
Then I had several failed attempts due to ldap password failures (copied password from the ebox-ldap.passwd file on the master.
Then I found the slave ldap was not starting up so commented out the SLAPD_NO_START in etc/default/slapd

now I am getting:-

A really nasty bug has occurred
Failed to enable: Can't call method "get_value" on an undefined value at /usr/share/perl5/EBox/ line 2455.
Failed to enable: Can't call method "get_value" on an undefined value at /usr/share/perl5/EBox/ line 2455.
at /usr/share/perl5/EBox/CGI/ServiceModule/ line 74
EBox::CGI::ServiceModule::ConfigureModuleController::_process('EBox::CGI::ServiceModule::ConfigureModuleController=HASH(0xa4...') called at /usr/share/perl5/EBox/CGI/ line 261
EBox::CGI::Base::run('EBox::CGI::ServiceModule::ConfigureModuleController=HASH(0xa4...') called at /usr/share/perl5/EBox/CGI/ line 120
EBox::CGI::Run::run('EBox::CGI::Run', 'ServiceModule/ConfigureModuleController', 'EBox') called at /usr/share/ebox/cgi/ebox.cgi line 19
ModPerl::ROOT::ModPerl::Registry::usr_share_ebox_cgi_ebox_2ecgi::handler('Apache2::RequestRec=SCALAR(0xa43e09c)') called at /usr/lib/perl5/ModPerl/ line 204
eval {...} called at /usr/lib/perl5/ModPerl/ line 204
ModPerl::RegistryCooker::run('ModPerl::Registry=HASH(0xa43e60c)') called at /usr/lib/perl5/ModPerl/ line 170
ModPerl::RegistryCooker::default_handler('ModPerl::Registry=HASH(0xa43e60c)') called at /usr/lib/perl5/ModPerl/ line 31
ModPerl::Registry::handler('ModPerl::Registry', 'Apache2::RequestRec=SCALAR(0xa43e09c)') called at -e line 0
eval {...} called at -e line 0

Any idea where to go next?

Installation and Upgrades / ebox 1.3 egroupware syncronise
« on: September 29, 2009, 01:18:09 pm »
I am trying to sync the address book and calender in egroupware to Kontact (at the moment, later I need to try Outlook and/or Thunderdird)
I should be able to use either groupdav or xmlrpc but can't get either to work.
I have set 'Enable the xmlrpc service' to 'yes' in egroupware Admin>site configuration
I have enabled both groupdav and egw-pear from the Admin>User groups
Then when groupdav and xmlrpc still did not work I did a 'pear install XML_RPC'  but still no luck

In the Kontact calendar and address book, groupdav does nothing, apart from checking about a certificate mismatch on the first try.  No errors, but unable to update the folder list.
I am using as the url with my username and password.  Using http results in me being asked for a username and password but, again, no sync or even update of folder list.

With xmlrpc the calendar gives no errors but does not sync using domain = default (or ebox or one of the group names I created) and my username and password.
with the address book I used the same settings and got the error 'Received invalid XML markup: unexpected character at 1:50' both before and after I installed XMP_RPC in pear.

I thought about using ldap but although I can access ldap in Kontact I can't figure out the right settings to use.  Picking 'subtree  query' gives me everything but egroupware is obviously not storing addresses, other than the account address details, in ldap anyway so not really a solution unless I can make egroupware use ldap without messing up ebox!

Any ideas anyone?

Pages: [1]