From Stefan.Stirzaker at health.gov.au Wed Apr 5 13:44:54 2006 From: Stefan.Stirzaker at health.gov.au (Stefan.Stirzaker at health.gov.au) Date: Wed, 5 Apr 2006 13:44:54 +1000 Subject: [albatross-users] ALbatross 1.33 Message-ID: HI All, Has anyone had this problem? I have installed albatross 1.33 but when I try and start it, it fails and when I run the tests in the test directory they all pass except one test which comes up with "cannot connect to session server". Anythoughts on what I've done wrong to not make Albatross start up? The script I'm using is start() { local _log_prefix='/var/log/albatross' local _subsystem='al-session-daemon' /bin/su -l albatross -s /bin/sh -c \ "/usr/local/src/bin/al-session-daemon --pidfile=${_log_prefix}/$ {_subsystem}.pid --log=${_log_prefix}/${_subsystem}.log start > /dev/null 2>&1" < /dev/null [ "$?" -eq 0 ] && success || failure touch /var/lock/subsys/albatross return $? } Stefan Stirzaker Office of Health Protection Surveillance Branch Surveillance Policy & Systems Section (02) 6289 4576 ******************************************************************************** "Important: This transmission is intended only for the use of the addressee and may contain confidential or legally privileged information. If you are not the intended recipient, you are notified that any use or dissemination of this communication is strictly prohibited. If you receive this transmission in error please notify the author immediately and delete all copies of this transmission." ******************************************************************************** From andrewm at object-craft.com.au Wed Apr 5 14:28:23 2006 From: andrewm at object-craft.com.au (Andrew McNamara) Date: Wed, 05 Apr 2006 14:28:23 +1000 Subject: [albatross-users] ALbatross 1.33 In-Reply-To: References: Message-ID: <20060405042823.B584C6F44C5@longblack.object-craft.com.au> >Has anyone had this problem? I have installed albatross 1.33 but when I >try and start it, it fails and when I run the tests in the test directory >they all pass except one test which comes up with "cannot connect to >session server". > >Anythoughts on what I've done wrong to not make Albatross start up? Use ps to see if the session daemon is running. If no, either the init.d script is failing, or the session daemon is aborting during startup for some reason. To work out which - look at the session daemon log file (apparently /var/log/albatross/al-session-daemon.log in your case) - if the session daemon is aborting, it will have logged the reason. You could also temporarily remove the "> /dev/null 2>&1" from your init.d script and run it by hand to see any errors generated by this part of the script. Are you sure /usr/local/src/bin is the correct path? /usr/local/bin would be more typical. >The script I'm using is > >start() { > local _log_prefix='/var/log/albatross' > local _subsystem='al-session-daemon' > > /bin/su -l albatross -s /bin/sh -c \ > "/usr/local/src/bin/al-session-daemon >--pidfile=${_log_prefix}/$ >{_subsystem}.pid --log=${_log_prefix}/${_subsystem}.log start > /dev/null >2>&1" > < /dev/null > > [ "$?" -eq 0 ] && success || failure > touch /var/lock/subsys/albatross > > return $? >} -- Andrew McNamara, Senior Developer, Object Craft http://www.object-craft.com.au/ From Stefan.Stirzaker at health.gov.au Thu Apr 6 08:58:20 2006 From: Stefan.Stirzaker at health.gov.au (Stefan.Stirzaker at health.gov.au) Date: Thu, 6 Apr 2006 08:58:20 +1000 Subject: [albatross-users] ALbatross 1.33 Message-ID: Hi Andrew, I'll try removing the pipe to null from init.d but the session daemon isn't creating a log file at all in the specified directory. Or do you need to create the file manually? I assumed it would create it if it doesn't exists. As this is a new installation on a machine it doesn't already have the file. I'm sure the path is correct as I double checked it as I thought the same as you. Thanks Stefan Stirzaker Office of Health Protection Surveillance Branch Surveillance Policy & Systems Section (02) 6289 4576 |---------+-----------------------------> | | Andrew McNamara | | | | | | | | | 05/04/2006 02:28 | | | PM | | | | |---------+-----------------------------> >------------------------------------------------------------------------------------------------------------------------------| | | | To: Stefan.Stirzaker at health.gov.au | | cc: albatross-users at object-craft.com.au | | Subject: Re: [albatross-users] ALbatross 1.33 | >------------------------------------------------------------------------------------------------------------------------------| >Has anyone had this problem? I have installed albatross 1.33 but when I >try and start it, it fails and when I run the tests in the test directory >they all pass except one test which comes up with "cannot connect to >session server". > >Anythoughts on what I've done wrong to not make Albatross start up? Use ps to see if the session daemon is running. If no, either the init.d script is failing, or the session daemon is aborting during startup for some reason. To work out which - look at the session daemon log file (apparently /var/log/albatross/al-session-daemon.log in your case) - if the session daemon is aborting, it will have logged the reason. You could also temporarily remove the "> /dev/null 2>&1" from your init.d script and run it by hand to see any errors generated by this part of the script. Are you sure /usr/local/src/bin is the correct path? /usr/local/bin would be more typical. >The script I'm using is > >start() { > local _log_prefix='/var/log/albatross' > local _subsystem='al-session-daemon' > > /bin/su -l albatross -s /bin/sh -c \ > "/usr/local/src/bin/al-session-daemon >--pidfile=${_log_prefix}/$ >{_subsystem}.pid --log=${_log_prefix}/${_subsystem}.log start > /dev/null >2>&1" > < /dev/null > > [ "$?" -eq 0 ] && success || failure > touch /var/lock/subsys/albatross > > return $? >} -- Andrew McNamara, Senior Developer, Object Craft http://www.object-craft.com.au/ ******************************************************************************** "Important: This transmission is intended only for the use of the addressee and may contain confidential or legally privileged information. If you are not the intended recipient, you are notified that any use or dissemination of this communication is strictly prohibited. If you receive this transmission in error please notify the author immediately and delete all copies of this transmission." ******************************************************************************** From andrewm at object-craft.com.au Thu Apr 6 09:19:08 2006 From: andrewm at object-craft.com.au (Andrew McNamara) Date: Thu, 06 Apr 2006 09:19:08 +1000 Subject: [albatross-users] ALbatross 1.33 In-Reply-To: References: Message-ID: <20060405231908.EE9D26F44C5@longblack.object-craft.com.au> >I'll try removing the pipe to null from init.d but the session daemon isn't >creating a log file at all in the specified directory. Or do you need to >create the file manually? I assumed it would create it if it doesn't >exists. As this is a new installation on a machine it doesn't already have >the file. The daemon will create the log file, and at the very least, it should contain a line like: Server starting at Thu Apr 6 09:18:10 2006 Because this is not happening, I would suspect a problem with the init.d script, or the daemon does not have permission to write to the log directory. -- Andrew McNamara, Senior Developer, Object Craft http://www.object-craft.com.au/ From Stefan.Stirzaker at health.gov.au Thu Apr 6 09:50:39 2006 From: Stefan.Stirzaker at health.gov.au (Stefan.Stirzaker at health.gov.au) Date: Thu, 6 Apr 2006 09:50:39 +1000 Subject: [albatross-users] ALbatross 1.33 Message-ID: Hi Andrew, Sorry to bother you again. I've gotten further this time, seems I'm missing somthing but not sure what. /bin/su -l albatross -s /bin/sh -c "/usr/local/src/bin/al-session-daemon --pidfile=/var/log/albatross/al-session-daemon.pid --log=/var/log/albatross/al-session-daemon.log start" Traceback (most recent call last): File "/usr/local/src/bin/al-session-daemon", line 26, in ? from albatross import simpleserver File "/usr/lib/python2.3/site-packages/albatross/__init__.py", line 9, in ? from albatross.context import * File "/usr/lib/python2.3/site-packages/albatross/context.py", line 12, in ? import cPickle ImportError: /usr/lib/python2.3/lib-dynload/cPickle.so: undefined symbol: PyUnicodeUCS4_AsUTF8String Stefan Stirzaker Office of Health Protection Surveillance Branch Surveillance Policy & Systems Section (02) 6289 4576 |---------+-------------------------------------------> | | Andrew McNamara | | | | | | Sent by: | | | albatross-users-bounces at object-c| | | raft.com.au | | | | | | | | | 06/04/2006 09:19 AM | | | | |---------+-------------------------------------------> >------------------------------------------------------------------------------------------------------------------------------| | | | To: Stefan.Stirzaker at health.gov.au | | cc: albatross-users at object-craft.com.au | | Subject: Re: [albatross-users] ALbatross 1.33 | >------------------------------------------------------------------------------------------------------------------------------| >I'll try removing the pipe to null from init.d but the session daemon isn't >creating a log file at all in the specified directory. Or do you need to >create the file manually? I assumed it would create it if it doesn't >exists. As this is a new installation on a machine it doesn't already have >the file. The daemon will create the log file, and at the very least, it should contain a line like: Server starting at Thu Apr 6 09:18:10 2006 Because this is not happening, I would suspect a problem with the init.d script, or the daemon does not have permission to write to the log directory. -- Andrew McNamara, Senior Developer, Object Craft http://www.object-craft.com.au/ _______________________________________________ Albatross-users mailing list Albatross-users at object-craft.com.au https://www.object-craft.com.au/cgi-bin/mailman/listinfo/albatross-users ******************************************************************************** "Important: This transmission is intended only for the use of the addressee and may contain confidential or legally privileged information. If you are not the intended recipient, you are notified that any use or dissemination of this communication is strictly prohibited. If you receive this transmission in error please notify the author immediately and delete all copies of this transmission." ******************************************************************************** From andrewm at object-craft.com.au Thu Apr 6 10:00:21 2006 From: andrewm at object-craft.com.au (Andrew McNamara) Date: Thu, 06 Apr 2006 10:00:21 +1000 Subject: [albatross-users] ALbatross 1.33 In-Reply-To: References: Message-ID: <20060406000021.D56806F44C5@longblack.object-craft.com.au> >Sorry to bother you again. I've gotten further this time, seems I'm missing >somthing but not sure what. > > > /bin/su -l albatross -s /bin/sh -c "/usr/local/src/bin/al-session-daemon >--pidfile=/var/log/albatross/al-session-daemon.pid >--log=/var/log/albatross/al-session-daemon.log start" > >Traceback (most recent call last): > File "/usr/local/src/bin/al-session-daemon", line 26, in ? > from albatross import simpleserver > File "/usr/lib/python2.3/site-packages/albatross/__init__.py", line 9, in >? > from albatross.context import * > File "/usr/lib/python2.3/site-packages/albatross/context.py", line 12, in >? > import cPickle >ImportError: /usr/lib/python2.3/lib-dynload/cPickle.so: undefined symbol: >PyUnicodeUCS4_AsUTF8String This means your python installation is broken in some way (probably bad shared library path). I'm a little reluctant to suggest too much here - I'm assuming you're using a RedHat system, and they require a specific version of python installed and working for their system management tools, and inadvertently breaking that python install will render your machine largely unmanageable. If you have a support contract with RedHat, asking them to help you install Python 2.3 might be worthwhile. Failing that, maybe someone on the list has been through this before (I haven't done it for years)? -- Andrew McNamara, Senior Developer, Object Craft http://www.object-craft.com.au/ From alan.junk at sunwave.com Wed Apr 12 04:31:38 2006 From: alan.junk at sunwave.com (Alan Meadows) Date: Tue, 11 Apr 2006 11:31:38 -0700 Subject: [albatross-users] al-if and al-setarg Message-ID: <6.0.3.0.2.20060411112439.01c04ec0@N/A> Hello Albatross users, I was trying to wrap an al-if around an al-setarg today in a template and ran into trouble. Here is what I was trying to do: Create Additional SPF Record Enter an additional SPF records for this domain below. IP Address/Range Hostname Albatross produced the following error: HTML Traceback: File "lib/includes/forminput", line 7, in al-macro File "lib/includes/forminput", line 15, in al-usearg Python Traceback: File "/usr/lib/python2.4/site-packages/albatross/context.py", line 127, in get_macro_arg raise ApplicationError('undefined macro argument "%s"' % name) ApplicationError: undefined macro argument "label" I was able to make it work by moving the al-if higher up the chain, but I think the template becomes a little more redundant and harder to read: Create Additional SPF Record Enter an additional SPF records for this domain below. IP Address/Range Hostname Is there something I can do about this? Am I approaching this the wrong way? Thanks! Alan From gabriel.cooper at mediapulse.com Wed Apr 12 04:42:21 2006 From: gabriel.cooper at mediapulse.com (Gabriel Cooper) Date: Tue, 11 Apr 2006 14:42:21 -0400 Subject: [albatross-users] al-if and al-setarg In-Reply-To: <6.0.3.0.2.20060411112439.01c04ec0@N/A> References: <6.0.3.0.2.20060411112439.01c04ec0@N/A> Message-ID: <443BF88D.9020700@mediapulse.com> Alan Meadows wrote: > > > > IP > Address/Range > > name="label">Hostname > > IP Address/Range Hostname