On Jan 24, 2011, at 8:26 AM, Laurence Popiel wrote:

> I have the trunk up and running in test mode configured and accessible from 
> iCal and iPhones. I  now want to put in in production.I created a dir in /opt 
> and followed the steps to download. When I run the ./run -i script it appears 
> to compile but when i run the caldavd executable it tells me that is not 
> installed. Am I missing something? I also tried release ver 2.4 and fixed the 
> dead links ut get an error on line 379 saying unbound variable so I'm a bit 
> lost at the moment.
> Can anyone help with the proper steps to install as a service?

This is one part of the product I've never really used (as it's not needed in 
Mac OS X Server), so perhaps somebody with experience using it can chime in...

What exactly are the errors you get when trying to run caldavd? Did you notice 
any errors after issuing "run -i"?

-dre

>   
> 
> On Tue, Jan 18, 2011 at 12:02 AM, Laurence Popiel <[email protected]> wrote:
> Thanks. That was it. fat fingers.  
> 
> On Mon, Jan 17, 2011 at 6:59 PM, Andre LaBranche <[email protected]> wrote:
> 
> On Jan 17, 2011, at 3:52 PM, Laurence Popiel wrote:
> 
>> Ok back to the beginning. I have the server up and running on my test box 
>> using trunk rev 6738.
>> 
>> Just built my standalone server following the method I used successfully. 
>> All went well until I tried to run the server and got this error:
>> 
>> It starts to load and gets to Starting server then when it gets to
>> 
>>  File "usr/lib/python2.6/plist.py , line 301, in __getattr__
>> raise AttributeError , attr
>> AttributeError : append
>> 
>> any thoughts?
> 
> broken caldavd.plist?
> 
> xmllint --valid /path/to/your/config.plist
> 
> It should return nothing. If it finds an error, it will bark at you, e.g.:
> 
> bash-3.2# xmllint --valid /etc/caldavd/caldavd.plist > /dev/null
> /etc/caldavd/caldavd.plist:35: parser error : StartTag: invalid element name
>     <<string>icalvip.icalserver.rack</string> <!-- The hostname clients use 
> when
>      ^
> 
> You can always try the sample (dev) config if you're unsure whether yours 
> might be problematic.
> 
> -dre
> 
>> 
>> 
>> On Sun, Jan 16, 2011 at 12:35 AM, Laurence Popiel <[email protected]> wrote:
>> Finally after everyone's advise and help, I have the server up and running 
>> and sharing calendars. Since I am new to all of this and even more of a 
>> newbie when it comes to writing scripts, any advise on how to script server 
>> startup on boot and shutdown on reboot or shutdown.
>> 
>> larry
>> 
>> 
>> On Fri, Jan 14, 2011 at 3:03 PM, Andre LaBranche <[email protected]> wrote:
>> Well, don't run memcached as root. Are you setting UserName and GroupName in 
>> caldavd.plist? These should be set to some non-root user that can be used 
>> for running the various daemons. See caldavd-apple.plist for an example. You 
>> may need to create a user account for this purpose, though it should be fine 
>> to test it using  your personal account.
>> 
>> -dre
>> 
>> On Jan 14, 2011, at 11:43 AM, Laurence Popiel wrote:
>> 
>>> Well I followed the advise to use a release version 2.4 (not trunk) and 
>>> found that many of the links in the run script to pkgs are broken or 
>>> unavailable. I was able to repoint most of them but still to no avail.
>>>  At this point I went back to trunk and was able to run the script but it 
>>> too has another problem. It installs and it starts the server but it hangs 
>>> on the error below and never starts the server
>>> 
>>>  {memcached-Default} can't run as root without the -u switch 
>>> 
>>>  Anyone have any ideas as to how to get either version running.
>>> 
>>> On Wed, Jan 12, 2011 at 7:07 PM, Andre LaBranche <[email protected]> wrote:
>>> Cool, you're welcome :)
>>> 
>>> The responsiveness you experience on our mailing list changes from time to 
>>> time, but it's been pretty good lately - glad it's helpful. It's sort of an 
>>> interesting situation for us, because to date our most important target 
>>> platform is Mac OS X Server, since that is where our service is bundled and 
>>> sold. However, linux support is becoming more and more important, so it's 
>>> great to see people picking it up and running with it out in the world.
>>> 
>>> This probably goes without saying, but: the most important thing to know 
>>> about this and any other open source project is that the user (or 
>>> administrator) is responsible for validating the configuration and making 
>>> sure things are working as intended. Also, any support is usually offered 
>>> on a 'best effort' basis by the community, which may or may not be good 
>>> enough for business purposes. This is probably the biggest difference 
>>> between our open source distribution and what you find bundled with Mac OS 
>>> X Server.
>>> 
>>> In Cupertino, we've currently got zero inches of snow ;)
>>> -dre
>>> 
>>> On Jan 12, 2011, at 3:30 PM, Laurence Popiel wrote:
>>> 
>>>> Thanks dre,
>>>> it helps quite a lot. As a novice it has forced me to dive in headfirst 
>>>> and learn far more than I expected. Rather pleasantly i must say. also in 
>>>> all my years providing support in an enterprise environment (usual OSs for 
>>>> desktop and deployment) I have never experienced a community that is as 
>>>> responsive and willing helpful as your user community.
>>>> So thank you for all the work you have done and the gracious time you gave 
>>>> to help me.
>>>> 
>>>> Larry   (under 24" of snow today)
>>>> 
>>>> On Wed, Jan 12, 2011 at 5:16 PM, Andre LaBranche <[email protected]> wrote:
>>>> It's been a while since the last release, so trunk is pretty different 
>>>> from the last 'stable' release. It's generally not recommended to run 
>>>> trunk code in a production environment, or if you do, make sure to test it 
>>>> thoroughly for your use cases. One reason that you may wish to avoid trunk 
>>>> code is that long-term problems can crop up, e.g. when upgrading to the 
>>>> next major version, we only support upgrades from older releases and not 
>>>> necessarily development versions.
>>>> 
>>>> I would probably recommend testing the most recent release to see if it 
>>>> does the job for you. Regarding how to actually deploy it on the 
>>>> production host, the 'run' script has an 'install' method that can install 
>>>> the various resources in the standard locations (e.g. /usr/local/...), 
>>>> however things like process lifecycle management are left up to the 
>>>> administrator. I would recommend that you do all the testing of your 
>>>> target release (or dev code if you wish) on a non-production host, 
>>>> including the installation using run script, and also whatever scripts you 
>>>> wish to use to start and stop the service, etc.
>>>> 
>>>> There is not a great deal of documentation about our server outside of the 
>>>> PDF for iCal Server, however this is not targeted at the open source 
>>>> distribution, but rather the integrated distribution that is part of Mac 
>>>> OS X Server.
>>>> 
>>>> The documentation (in a somewhat tattered state, unfortunately) for the 
>>>> open source distribution is all located here: 
>>>> http://trac.calendarserver.org/
>>>> 
>>>> Hope this helps,
>>>> -dre
>>>> 
>>>> On Jan 12, 2011, at 1:36 PM, Laurence Popiel wrote:
>>>> 
>>>>> Now that I'm able to setup ad run the development version, where can I 
>>>>> find documentation on setting up in a small network production 
>>>>> environment. I'll have 8 users, three groups and 8 calendars. Does it 
>>>>> install differently and point to different config files ?
>>>>> 
>>>>> On Tue, Jan 11, 2011 at 12:51 PM, Andre LaBranche <[email protected]> wrote:
>>>>> Looks like one of the externally hosted dependencies is failing to 
>>>>> download... will check into it.
>>>>> 
>>>>> -dre
>>>>> 
>>>>> On Jan 11, 2011, at 8:38 AM, Guy wrote:
>>>>> 
>>>>>> Likely new checkins have broken something.. it's always risky running 
>>>>>> trunk..
>>>>>> 
>>>>>> The usual advice here is to pick a revision that works and use that... 
>>>>>> either something from the released branch. Or just check out and use the 
>>>>>> revision that worked for you when you where testing.
>>>>>> 
>>>>>> --Guy
>>>>>> 
>>>>>> On 11 Jan 2011, at 16:34, Laurence Popiel wrote:
>>>>>> 
>>>>>>> I am extremely new to Ubuntu and linux in general. I have installed 
>>>>>>> Ubuntu 10.04 and followed the steps outlined in several postings. After 
>>>>>>> a little trial and error I was able to set up and access the 
>>>>>>> CalendarServer and configure users by modifying the accounts.xml and 
>>>>>>> caldavd-dev.plist. I could connect via iCal and the two iphones in my 
>>>>>>> network.
>>>>>>> Since i was able to get it up and running I decided to build a server 
>>>>>>> to host the Calendar Server, afp file sharing, samba and use the server 
>>>>>>> for time Machine backups.
>>>>>>> 
>>>>>>> Using a pentium 4 box I installed Ubuntu 10.04 server and followed 
>>>>>>> these steps:
>>>>>>> 1) edit /etc/fstab to enable xattrs by adding the “user_xattr” option.
>>>>>>> 
>>>>>>> e.g. (all on one line):
>>>>>>> 
>>>>>>> UUID=8f2bb850-0e8f-4d81-bba5-fb93ef9b9990 /               ext4    
>>>>>>> errors=remount-ro,user_xattr 0       1
>>>>>>> 
>>>>>>> after doing the above you need to reboot, or “sudo mount / -o remount”
>>>>>>> 
>>>>>>> 2) sudo apt-get build-dep postgresql
>>>>>>> 
>>>>>>> 3) sudo apt-get install python-setuptools python-xattr python-twisted 
>>>>>>> subversion curl
>>>>>>> 
>>>>>>> 4) svn co 
>>>>>>> http://svn.macosforge.org/repository/calendarserver/CalendarServer/trunk
>>>>>>>  CalendarServer
>>>>>>> 
>>>>>>> 5) cd CalendarServer ; ./run -s
>>>>>>> 
>>>>>>> when I run ./run -s i get this:
>>>>>>> 
>>>>>>> Downloading libevent...
>>>>>>> 
>>>>>>> % Total %Received % Xferd AverageSpeed    Time     Time     Time     
>>>>>>> Current
>>>>>>> 
>>>>>>>                                                      Dload Upload      
>>>>>>> Total    Spent    Left       Speed
>>>>>>> 
>>>>>>> 0       0       0        0        0       0      0             0        
>>>>>>>   --:--:--  0:40:24  --:--:--
>>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>>>> The previous successful install was revision 6725 and it continued and 
>>>>>>> finished without a hangup.
>>>>>>> 
>>>>>>> now it is revision 6726 
>>>>>>> 
>>>>>>> Any ideas as to why it worked without a hitch 4 days ago and now I cant 
>>>>>>> get any further than what you see.
>>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>>>> _______________________________________________
>>>>>>> calendarserver-users mailing list
>>>>>>> [email protected]
>>>>>>> http://lists.macosforge.org/mailman/listinfo.cgi/calendarserver-users
>>>>>> 
>>>>>> _______________________________________________
>>>>>> calendarserver-users mailing list
>>>>>> [email protected]
>>>>>> http://lists.macosforge.org/mailman/listinfo.cgi/calendarserver-users
>>>>> 
>>>>> 
>>>> 
>>>> 
>>> 
>>> 
>> 
>> 
>> 
> 
> 
> 

_______________________________________________
calendarserver-users mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/calendarserver-users

Reply via email to