The topic for #zenoss-testing is: Zenoss QA Test Day April 1 - Trunk Source Builds: http://is.gd/b5Ur3 (8:11:46 AM)

mode (+o mrayzenoss) by ChanServ (8:11:47 AM)

zenglenn [~18adbbda@gateway/web/freenode/x-zhhgkvohidoqgbfb] entered the room. (9:51:14 AM)

9:51:48 AM zenglenn: hello everybody

9:52:55 AM mrayzenoss: howdy

9:53:30 AM zenglenn: anyone interested in snowleopard?

9:54:00 AM zenglenn: i've made some progress there...but not quite to the point of nirvana

9:54:46 AM zenglenn: well unless you can do without events

mode (+o bbibeault) by ChanServ (10:06:25 AM)

bbibeault [~Adium@rrcs-24-173-187-218.sw.biz.rr.com] entered the room. (10:06:25 AM)

10:19:21 AM mrayzenoss: I'll go build snow leopard

10:19:33 AM mrayzenoss: firing up some EC2 instances to build lots of platforms

10:19:54 AM zenglenn: you'll want http://dev.zenoss.org/svn/sandboxen/gstreiff/snowleopard/inst

10:20:53 AM zenglenn: it builds and zodb loads, but something is wonky with the mysql bindings at runtime

10:22:22 AM zenglenn: File: "/zenhome/lib/python/MySQLdb/__init__.py", line 27, in <module> import _mysql

10:22:38 AM zenglenn: ImportError: dynamic module does not define init function (init_mysql)

10:23:10 AM zenglenn: this when I try to fire up zenhub

10:27:29 AM zenglenn: here are my deltas thus far: http://dev.zenoss.com/trac/log/sandboxen/gstreiff/snowleopard

10:42:28 AM bureado: docs/DOC-5291 <- I think this document should specify svn is needed in the build environment

10:42:48 AM bureado: The install.sh doesn't say anything about it and will rather fail with a find error.

10:48:55 AM mrayzenoss: hmm… good point

10:49:22 AM mrayzenoss: I guess if you're using the tarball you don't need SVN

10:49:33 AM mrayzenoss: but I usually recommend SVN

10:49:42 AM zenglenn: i'll chat with Sharon about that

10:50:03 AM mrayzenoss: or bureado could leave a comment on that page and Sharon would roll it up

10:50:11 AM bureado: I'll do that.

10:50:13 AM zenglenn: perfect

10:58:20 AM bureado: Done, thanks.

11:07:41 AM zenglenn: Also, Sharon has a tips/troubleshooting section for the install guide in the pipeline.

11:07:43 AM zenglenn: http://dev.zenoss.com/trac/ticket/6378

mistich [~mistich@nat-vlan0202.sat4.rackspace.com] entered the room. (11:29:30 AM)

11:54:15 AM bureado: I'm having this on Debian Squeeze:

11:54:15 AM bureado: configuring: /home/zenoss/build/rrdtool-1.3.9/Makefile

11:54:15 AM bureado: make: *** [/home/zenoss/build/rrdtool-1.3.9/Makefile] Error 1

11:54:50 AM bureado: I'm trying to figure out what's going on, seems that automake doesn't like the .am files there.

11:55:02 AM bureado: Well, in fact, there's no Makefile for rrdtool.

11:57:10 AM bureado: Oh, it seems that I'm lacking libxml2-dev, too.

11:57:59 AM bureado: I'm also getting This script requires the Sun JDK 1.6 or greater.

11:58:13 AM bureado: But this doesn't seem to be affecting, do you build Zenoss with the JDK?

zenglenn left the room (quit: Ping timeout: 252 seconds). (12:03:46 PM)

12:08:51 PM mrayzenoss: hmm… the JDK requirement is new

12:09:09 PM mrayzenoss: there's some javascript compression tool in the build chain now

12:09:14 PM bureado: Ok, I'll see if I can complete install.sh without it. It's building now.

12:09:16 PM mrayzenoss: I'll try to get Glenn back here

12:09:19 PM bureado: Yes, I saw those .js...

12:09:23 PM bureado: Glenn Beck?!

12:09:27 PM bureado: Oh, Glenn back

12:09:45 PM bureado: BTW nice Fool's Day tweet, I skipped a couple heartbeats

12:10:53 PM mrayzenoss:

1:24:00 PM mrayzenoss: building on Debian 5 and Ubuntu 9.10 right now

1:24:30 PM mrayzenoss: if I knew what I was doing on Solaris, I'd be building there too

1:37:06 PM mrayzenoss: ok, had to add unzip to my build chain, that's new

1:37:22 PM mrayzenoss: and I'll need to get a Sun JDK

zenglenn [~18adbbda@gateway/web/freenode/x-rlcmkizsvogqmvad] entered the room. (1:57:52 PM)

1:58:50 PM zenglenn: not sure if you got an answer on the jdk...the 1.6 requirement is for a java script minifier we use.  otherwise you could get away with jdk 1.5 at the expense of some ui performance

cluther [~cluther@rrcs-24-173-187-218.sw.biz.rr.com] entered the room. (2:09:13 PM)

mode (+o cluther) by ChanServ (2:09:13 PM)

mistich left the room ("Leaving."). (2:47:05 PM)

cluther left the room (quit: Quit: cluther). (2:48:39 PM)

cluther [~cluther@204.12.34.212] entered the room. (2:49:29 PM)

mode (+o cluther) by ChanServ (2:49:29 PM)

3:36:47 PM mrayzenoss: Debian 5 and Ubuntu 9.10 successfully completed a source build

3:37:04 PM mrayzenoss: Should it work if I start them up?

3:38:42 PM mrayzenoss: oh, much sadness

4:16:29 PM mrayzenoss: http://dev.zenoss.org/trac/ticket/6395

bbibeault left the room (quit: Quit: Leaving.). (4:48:45 PM)

5:06:32 PM bureado: mrayzenoss: My build failed again (Debian Squeeze) -- may I have a list of the packages you have in your build env? dpkg --get-selections | mail -s 'mray packages' joseparrella@gmail.com

5:07:13 PM bureado: mrayzenoss: From your error.log you seem to be missing librrd4

5:07:21 PM mrayzenoss: here are my notes: http://pastebin.org/130778

5:07:51 PM mrayzenoss: librrd4 is supposedly being built in the build

5:08:16 PM mrayzenoss: oops, those are my 2.5.x notes

5:08:26 PM zenglenn: @matt  actually you hit the same issue i did with the dynamic linker not finding librrd*.so.  at the time, i worked around the issue by editing a file in /etc/ld.so.d to point back to the otherwise invisible module under $ZENHOME

5:08:30 PM bureado: Ah, I see. Then it's probably not being installed or not being installed in LD_PATH.

5:08:39 PM bureado: zenglenn: ack

5:08:53 PM bureado: mrayzenoss: You have a few commands por trunk.

5:09:05 PM bureado: mrayzenoss: I'll install the packages you have in the first line, though, and try again.

5:09:07 PM mrayzenoss: #trunk

svn co http://dev.zenoss.org/svn/trunk/inst zenossinst

cd zenossinst

./install.sh

5:09:24 PM bureado: Right.

5:09:53 PM mrayzenoss: it eventually gets through the build, but the startup fails.  Glenn's investigating, says he thinks he's already got the fix

5:10:17 PM bureado: mrayzenoss: However, you're building for Debian 5, which Python are you using? And if it's 2.6, how did you backport it? (not that I think itś related to the bug, though)

5:10:54 PM mrayzenoss: unfortunately for now the zenoss build includes building it's own Python 2.6.2

5:11:05 PM zenglenn: correct

5:11:19 PM mrayzenoss: using the system python is one of the first things on Glenn's todo

5:11:26 PM bureado: Oh.

5:11:37 PM zenglenn: funny...my list of first things is getting longer

5:11:39 PM zenglenn:

5:11:46 PM zenglenn: but indeed

5:12:06 PM mrayzenoss: well, that leads to your #2 first thing, using system versions of libraries

5:12:26 PM bureado: Well, if find /usr/local/zenoss -type f -name 'librrd.so.4' brings something up, adding that path to /etc/ld.so.conf.d/ as zenglenn suggested should do.

5:12:28 PM zenglenn: that would make for a much faster build

5:12:28 PM mrayzenoss: and a corollary first thing, using cached builds instead of rebuilding everything

5:12:38 PM bureado: 17:42 <@mrayzenoss> and a corollary first thing, using cached builds instead of rebuilding everything

5:12:42 PM bureado: +1

5:12:58 PM bureado: But why don't you use system stuff? I mean, what are the main showstoppers for that?

5:13:15 PM zenglenn: history and a crusty makefile

5:13:17 PM mrayzenoss: historically we've had a very monolithic build

5:13:43 PM mrayzenoss: we included everything because sometimes it wasn't on the machine we needed to install on

5:13:55 PM zenglenn: it /does/ give you the virtue of a more or less controlled build environment

5:13:59 PM mrayzenoss: which can be a vicious circle

5:14:10 PM bureado: e.g., I think that if mrayzenoss just aptitude install librrd4 now, services should boot. That's a good indicator that the app wouldn't depend THAT much on stuff uner /u/l/zenoss

5:14:10 PM zenglenn: but it is not very distro friendly

5:14:14 PM bureado: Yes, yes, I hear you.

5:14:24 PM bureado: And then you'll have like people with librrd2 and they will run into strange problems

5:14:39 PM zenglenn: right

5:14:40 PM mrayzenoss: I'll go restart my instances and try that

5:14:42 PM bureado: and they will blame it on Zenoss and not on their own old system stuff

5:15:33 PM mrayzenoss: yup, which further discourages opening up the build

5:15:43 PM mrayzenoss: but we're doing it anyway, because we're crazy like that

5:16:37 PM bureado: BTW just came back from a customer, finished a Zenoss deployment project, had the honor of turning off the WhatsUp! "server"

5:17:03 PM mrayzenoss: yay!

5:17:18 PM bureado: Client committed to make me insane, focused on having the zapplet running on Windows with sound alerts.

5:17:30 PM mrayzenoss: lol

5:17:58 PM bureado: After building trunk, I'll try and get the sound alerts into that zapplet thing, I used a solution found in the forums, using nc.exe for Windows... which Kaspersky finds as 'dangerous content'.

5:18:21 PM bureado: But that means that for the rest of it, you people make a great work!

5:19:15 PM bureado: They didn't even notice the switch in terms of functionality, and really appreciated an interactive Web interface for their jobs. Well, all our customers with Zenoss do.

5:20:36 PM zenglenn: you've just inspired me to go home work 4 more hours

5:20:39 PM mrayzenoss: bureado: you seem to be correct, installing librrd4 cleared up the issues

5:20:54 PM zenglenn: hey guys taking off ... (waves)

zenglenn left the room (quit: ). (5:21:04 PM)

5:22:07 PM bureado: mrayzenoss: Right. You're using system's librrd4 now. If you'd like to use the other one, you should first find the path to it (find /usr/local/zenoss -type f -name 'librrd.so.*' should do) and add it as the sole content of a file under /etc/ld.so.conf.d/

5:22:22 PM bureado: mrayzenoss: And then removing librrd4 with aptitude since system libraries take precedence over the ones on ld.so.conf.d

5:22:39 PM mrayzenoss: doh

5:22:47 PM mrayzenoss: my EC2 instance doesn't have port 8080 available

5:23:14 PM bureado: mrayzenoss: But is a good indicator, at least some libraries which are common, well maintained, reasonably up-to-date in modern distros might be removed from the build process in order to speed it up and keep critical stuff in there, such as Python.

5:24:26 PM bureado: Actually for and end customer which just uses the stack installer it doesn't make a difference to use the .python.bin or system's Python, it's just a matter of making Zenoss more attractive for distros to maintain themselves.

5:24:40 PM mrayzenoss: yeah, that's the point of this exercise

5:25:02 PM mrayzenoss: we won't be providing or maintaining the packages for the distros

5:25:31 PM mrayzenoss: we'll still deliver the same artifiacts

5:25:47 PM mrayzenoss: ideally they'll help us find compatibility issues before we hit them

5:26:15 PM mrayzenoss: and make our install even more friendly

5:28:07 PM mrayzenoss: hmmm, this is good.  librrd4 in lenny is 1.3

5:28:17 PM mrayzenoss: squeeze is 1.4, which we don't support yet

5:53:35 PM mrayzenoss: bureado: docs/DOC-5838

5:53:42 PM mrayzenoss: gotta run, be back tomorrow