[00:27] I use postfix and amavis and have been getting cron emails from my backup machines erroneously labeled as spam. I've added the sender addresses to 51-whitelist with a value of -15.0, but this seems to be ignored. Does anyone know how I get amavis to use the sender whitelist in 51-whitelist? [00:41] bmunat: Just out of curiousity, why 51-whitelist instead of 50-user? [00:44] hmm, I think something (tutorial, etc.) told me to do it that way [00:44] guess I could try putting the map in 50-user [00:48] I'm pretty sure it won't matter, just curious. [00:49] bmunat: Would you pastebin your 51-whitelist? [00:52] argh, it keeps saying it tripped the spam filter... will try pastie [00:52] http://pastie.org/765476 [00:53] i'm not super-great with perl syntax... maybe I'm missing something. though amavis starts up, so I don't think I have a syntax error [00:54] do you know if matching a whitelist entry should make the spam headers not be added to the mail? [00:54] cuz after moving the contents of 51-whitelist into 50-user, I still see spam headers on a test mail from my backup machine [00:57] bmunat: Look at lines 145 - 155 of 20-user. What you have there is incomplete. [00:58] ScottK: 20-debian_defaults you mean? [00:58] bmunat: Yes. Sorry. [00:58] ahhh... I need to replace the entire data structure [00:59] duh, that makes sense [01:00] Don't forget you'll need some more bits at the end too. [01:05] yeah, got them... and a new test email from the backup machine still has the spam headers, but the score is much lower (close to -15, which is what I set it to), so it appears to be working [01:05] thank you so much for your help [01:05] bmunat: You're welcome. [02:51] ? === zzz2009 is now known as jla [02:56] test [02:56] jla: This is a channel for Ubuntu server support, not testing IRC... do you have a specific question about Ubuntu server? [02:57] Sorry, I thought my client had died [02:57] at the moment just lurking [02:58] jla: /ping is the way to check if you are still talking to the IRC server... [02:58] thanks [02:58] You're welcome. [02:59] i do have a ? why are so many of the config files for things like amavis split up into so many bits [03:00] so the updates can replace standard files [03:00] and leave your customized files [03:01] jla: The amavis thing really confused me at first, but now I really like it. [03:02] If it was all one big config file, when you changed anything, you'd almost certainly end up having to sort out maintainer changes versus yours on upgrades. The way they waterfall if you've set something specific you want, maintainer config changes won't affect that. [03:02] I have been trying to setup amavis/clamav/spamassassin and I am finding the chopped up files annoying, eg I thought i had config'd not to quarantine anything only to find a whole bunch of files in thq spamass qu directory. I didn't even look just deleted the whole damn thing [03:03] bacj in 5 [03:03] oh yeah... my quaratine dir was several gigs before i noticed it was doing that :-( [03:04] i just added a weekly cron job to delete everything over a week old [03:04] tho I've never actually had to retrieve something from quarantine.... [03:06] jla: I believe that the setup in the Ubuntu server guide works reasonably well. Even if it's not ideal for you, it's a good basis to start from. [03:08] this may be more of a mysql question, but I'm trying to get rid of the logrotate errors for the mysql logs on an ubuntu system (i.e. http://www.lornajane.net/posts/2008/Logrotate-Error-on-Ubuntu) and even though i've added the user to mysql i still get the logrotate errors... [03:08] not sure I agree, i think they are far too loose on things like spam/virii etc. we work on the basis that if it even smell like spam... discard it. why waste resources both human and electonic [03:09] i even did "GRANT ALL ON *.* TO 'debian-sys-maint'@'localhost' IDENTIFIED BY PASSWORD 'foo'" and flushed privileges.... and the debian-sys-maint user still can't connect [03:10] When I first started looking for a server distro I liked the sound of ubuntu, but the more I try to admin it the less enamored I am [03:16] The quarrantine (sp) example, why should bmunat have to run a cron job to clean it up, why not let the admin decide if they want to qu stuff or not. [03:28] UBUNTU AND LINUX ARE CANCER IN A SENSE IF YOU USE IT YOUR BODY WILL GET SEPSIS AND YOU WILL GET CANCER EVERYWHERE IN YOUR BODY\ [03:28] !ops [03:28] Help! Channel emergency! soren, lamont, mathiaz or tom [03:29] !staff' [03:29] !staff [03:29] Hey nalioth, jenda, rob, SportChick, seanw, Dave2, Christel, tomaw, Gary, PriceChild, niko or stew, I could use a bit of your time :) [03:30] ScottK: I can see some of the reason for separating some items, but they seem to have added things like whitelist in out of the way places. [03:31] jla: Don't worry about it. Put your own whitely in 50-user and it wil over-ride the maintainers. === Mike||gone is now known as Mike_lifeguard [03:39] ScottK: I guess so, but not having all the default config in one place makes trying to determine what needs to be over-ridden a pain [03:40] jla: this is how Debian does it [03:40] it does make life easier once you understand the system [03:45] jtaji: I not sure about that. the example I have been using is amavis-new quarantine directory, I don't want it or need it. if it smells like spam/virii we don't accept it, but the amavis setup from debian/ubuntu seems to work on the basis that spam should br delivered if not to the recipient then some where else why!!!!! [03:47] Spam should be dumped asap, not delivered [03:48] enough of my rantings [03:48] back tolurking [03:49] hehe.. tis ok [03:50] you certainly can't make everybody happy with defaults, either [04:10] I really like the way config files are split up, it's one of the more important reasons I use ubuntu [04:10] rather than one massive unmaintainable file, it's grouped logically [04:11] and you can still search for a directive with a grep -R if you don't know where it is [04:34] qman: I might agree if all the config files were in one place, again the example of amavis, most of the config files are in /etc/amavis, however at least two files are in /usr/shared/amavis/conf.d. [04:36] qman: if it were only amavis I might just mutter under my breath, however there are many packages that have been messed about. this creates problems most importantly it is difficult to get support from the developers. and documentation provided by the developers no longer applies === Mike_lifeguard is now known as Mike||gone [04:50] jla: you mean /etc/amavis/conf.d/ [04:51] oh I see them [04:52] http://packages.ubuntu.com/karmic/all/amavisd-new/filelist [04:53] I don't use it or have it installed to check.. but I'd assume those two aren't read in, and are meant to be copied into /etc/amavis/conf.d/ if desired, but aren't by default for some reason [04:54] I suspect that's the case, or a bug should be filed, because all system config files go in /etc, period [04:58] yeah [04:59] jtaji: they are read, the second turns off the various checks which are then turned on or not in 15-content_filter_mod. The fact that they are hidden and not in /etc/amavis/conf.d really worries me. What else are they hiding, if they don't respect total transparency we might as well stay with M$ and their tricks. [04:59] jtaji: the stuff in /var.... is not an accident [05:01] now you're just being silly, it's clearly transparent as you've found it [05:02] jla: For full transparency, as always, the best documentation is the source code. If you 100% need to, read it. Then ask Microsoft to do let you read theirs, and see how far you get. [05:02] and as for amavis defaults, as far as I know it's more common to not drop email into /dev/null, but rather to quarantine [05:03] I only found it by accident, when something did not make sense, so i went looking. [05:07] jamrsden: reading the code is fine, if you are a programmer, however how many server admins are programmers and would understand the source? as to M$ that was my point. [05:07] jmarsden: if you pay Microsoft enough -- if, for example, you're a multinational or a G8 government, you can sometimes get access to the source. [05:07] twb: True, but neither jla nor I are likely to meet those criteria. [05:07] Just mentioning it for completeness :-) [05:09] jtaji: why expend time and resources on things like spam and virii. we are seriously considering requiring pre-registration in order to send us email. [05:10] jla: At minimum, a good sysadmin understands the software packaging system that his systems use, and so can quickly and easily see where any given package puts its files. If that's not enough for you, which apparently it isn't or you wouldn't be complaining about amavis, then... time to read the source. [05:10] jla: fair enough, I'm just not sure your organization's requirements are in the majority [05:13] jmarsden: my concern is that in several cases I have found that there appears to be an attempt hid some of the files involved in packages I wish to use. i other cases the packages have been modified in ways that the original developers do not support, which can lead to other problems. [05:13] jla: Hidden files? That dpkg -L PACKAGENAME does not show? Really? [05:15] Or that you cannot see from looking at the source package if you care enough about the details to do that? Are these "hidden" files not mentioned anywhere at all in the package documentation? [05:15] * jmarsden installs amavis in a VM to check on this claim for himself... [05:16] jla: bottom line, FHS states that /usr/share/ hierarchy is for architecture independent data, so if those files aren't intended to be modified, then it might be the right spot [05:16] but sometimes it's a judgement call... and you might have found that different distros make different decisions sometimes [05:18] jmarsden: I think you will find that at least acouple of files in amavis are not in the documentation and are not with the other config files. [05:23] The two files in /usr/share/amavis/conf.d/ are specifically not to be edited, as comments within them state. So they are architechure-independent data files, and so are in a perfectly reasonable location per the FHS. As for being hidden -- they aren't hidden. Their names do not start with a leading period, their perms allow everyone to read them, and dpkg -L avamis-new clearly lists them. [05:25] Lastly, they *are* mentioned in the documentation, see /usr/share/amavisd-new/README.Debian [05:25] hi [05:26] jla: As I said earlier: "a good sysadmin understands the software packaging system that his systems use, and so can quickly and easily see where any given package puts its files" [05:26] jmarsden: the documentation for amavis-new is on the amavis-new web site, NOT on the debian site after all amavis-new is not devloped by debian, just A [05:27] jla: The documentation foe the amavisd-new Debian package is on your system when you install that package. [05:27] If you want to install it from a source tarball and use the upstream web site docs, that is your choice. [05:29] as postfix is documented on the postfix web site. If you are not the developer then pissing arround with what you don't own is bad manners. If you want a change then you should suggest then to the develops, contibute the code but to crap on somnebody elses rug is not nice! [05:31] jla: If you do not understand the value of a packaging system, use a distribution that does not use one. If you use Ubuntu, a good sysadmin would understand the Ubuntu packaging system as part of their sysadmin responsibilities. [05:32] BTW, the documentation for the Ubuntu postfix package is installed with it and more comes in the related postfix-doc package. [05:37] jmarsden: we can argue this till the cows come home. I happen to think that the modification that debian/ubuntu make just make life more difficult not easier. [05:38] twb: actually, even students can get access to a lot of Microsoft sourcecode if they need it for something study-related (& after signing a very strict NDA) [05:39] jla: "virii" is a non-existent word [05:39] jla: Your claim that "the" documentation for a Ubuntu package which you just installed is by definition on the upstream web site is clearly inaccurate, and demonstrates a total misunderstanding of what a software package is, IMO. [05:39] jla: I can understand feeling that way. I thought so initially too. [05:40] jmarsden: I think you're being a bit aggressive towards someone that is new here. [05:40] reading README.Debian is often a good start ☺ [05:41] ScottK: Probably. He made a claim he can't substantiate regarding this whole issue of "hidden" files, comparison with MS, etc etc... I'm not sure that was the best way to start out as a newcomer, if such he is. [05:41] README.Debian (or README.Debian.gz) should explain Debian/Ubuntu-specific configuration stuff [05:42] jmarsden: Certainly, but you've been around here long enough to know better. [05:44] JanC: In the case being discussed, it does. But it was claimed that this is not "the documentation". [05:44] I agree, however if I want to setup a package like amavis then I need to understand the full documentation, which is on the upstream site. in the case of postfix it is also available in the /var/doc... but that is not the case in all cases. [05:44] jmarsden: I can imagine not everybody new to Ubuntu/Debian doesn't know about that convention though [05:45] jla: if this sort of docs is missing from /usr/share/doc// then that's a bug you should report [05:46] JanC: Agreed. There is a difference between coming asking for help, and coming in talking about "... crap on somnebody elses rug ..." [05:47] well, if you have been trying to fix things for hours, politeness sometimes has something to desire ;) [05:48] ScottK: i am/was migrating my severs from centos/fedora to ubuntu. we currently have a number of services among them postfix/dovecot with amavis-new/clamav/spamassassin/postgrey spam control. [05:48] I hope jla will remember to check those docs in the future ☺ [05:49] jla: That's a good combination. [05:50] jmarsden: I may have come on a little strong there. [05:51] jla: Fair enough. [05:56] ScottK: we have managed to get our spam level down to about 5%. we work on the basis "that if smells like spam we can it" nothing that gets spamassassin > 5 is accepted, no viruses are accept , even to quarantine, the risks of accidentally triggering are too great, particularly as the majority of downstream are windows. [05:57] jla: One thing I think you will like about Ubuntu is that we actively maintain clamav so that the current release (once it's tested and reverse depends are updated if needed) is kept available for all supported releases. [06:02] getting late and my battery is low, so I had better exit stage right. [08:28] ok i switched kernels somehow [08:29] now it says im running 2.6.31-16-generic-pae instead of 2.6.31-16-server [08:29] how do i change it back [09:41] anyone know of a server info script that can output wiki markup? I used one ages ago that dumps mediawiki formatted server reports, just cant remember the name of it [09:43] You want to put server logs on a wiki? [09:48] twb: i want to put server hardware and software info on a wiki, like a parsed output of hwinfo [09:57] Ah. [09:58] I would just stick it in a PRE block, because I'm lazy [10:23] hi all [10:24] people, I have a interesting problem here. df command show that are there space, but qhen I try create any dir show not space left... [10:26] look http://dpaste.com/140854/ [10:26] J_P: What does 'df -i' show? [10:34] J_P: You're probably out of i-nodes. "df -i", like jpds suggests, will show you how many i-nodes (instead of space) are available. [10:35] * jpds hugs soren. [10:35] soren: o/ [10:35] jpds: sorry for long time, look there [10:35] http://dpaste.com/140856/ [10:36] Yeah, you're out of inodes. [10:36] soren: http://dpaste.com/140856/ [10:36] what is that? or why that? [10:38] jpds: how I repair that? [10:39] jpds: I would like have as reference the df -h correct.. [10:40] J_P: you probably created *many* small files somewhere [10:41] guntbert: humm.. I think yes. But not I. The ZoneMinder software that run on it.. [10:41] J_P: http://www.linfo.org/inode.html [10:47] jpds: yes [10:47] There are two ways in which a filesystem can run out of space: it can consume all the space for adding new data (i.e., to existing files or to new files), or it can use up all the inodes. The latter can bring computer use to a sudden stop just as easily as can the former, because exhaustion of the inodes will prohibit the creation of additional files even if sufficient HDD space exists. [10:47] well, I think that solution is use less HD space.. [10:48] J_P: you sulution would be to delete *many* files - its an inode problem and no space problem [10:48] *your [10:50] find /home -xdev -size -2048c or something [10:50] (I haven't been paying much attention.) [10:52] ok so USERS are able to CD wherever the hell they want in /etc/passwd and whatever, how can i keep them to /home only!? [10:53] tos_: why does it matter? [10:56] passwords are not stored in /etc/passwd, so you shouldn't worry about that [10:59] alex_joni: unless you specifically force that ;-) [10:59] Which would be a dumb thing to do [10:59] ttx: Hey, dude. [10:59] soren: how was your holiday break ? [11:00] ttx: My INBOX says "too long". [11:00] soren: My burndown chart says "too flat" :) [11:04] ttx: Yeah, that too. I had a /very/ short list of stuff I wanted to get done over the holidays. I haven't done anything. [11:04] soren: that's good ! [11:04] That's a point of view :) [11:06] I wanted to be left alone, and I got that for once [11:06] soren: http://www.structuredprocrastination.com/ [11:08] Fascinating [11:08] truly [11:08] soren: it advocates making sure your list of things to do is REALLY long [11:08] check [11:09] If I was one of those GTD wankers, I'd tell you that it changed my life. But it didn't, because I basically ignore the essay's advice. [11:09] * soren is a GTD wanker [11:10] :-) [11:10] They are never far away [11:10] My favourite part of that essay is the photo with the caption: "Author practices jumping rope with seaweed while work awaits." [11:12] I say this while making lunch at 10:20PM [11:19] cemc: I think the issue you saw with spamasassin and amavisd-new was bug 502615. I'm curious what you think of the proposed solution? [11:19] Launchpad bug 502615 in spamassassin "/etc/cron.daily/spamassassin should restart amavisd" [Undecided,New] https://launchpad.net/bugs/502615 [11:22] * soren lunches [11:26] ok what im trying to do is stop users from going to other directorys [11:27] tos_: why? [11:28] ScottK: that solution only works if sa-update is used from crontab, not when the spamassassin _package_ is updated. like you said, maybe not everyone is using sa-updates [11:29] twb... im just paranoid i guess [11:29] cemc: OK. I'm open to ideas then. [11:29] tos_: then unplug your system and turn it off [11:29] yeah [11:29] good idea [11:29] tos_: if you're concerned about security, you should start out by working out the attack vectors and then closing them down. [11:30] You don't start by picking a random thing to lock down, and trying to do it -- it's not a productive use of time. [11:38] ScottK: maybe it should check in postinst if there's amavis with spamcheck running... ? [11:39] cemc: I was thinking similarly. The concern I have is if there is a performance impact on heavily loaded sites. Not sure and not sure who to check with. [11:39] ScottK: performance impact in what way? by restarting avamis? [11:40] Yes. [11:40] If you stop all the running processes on a fast moving site, is that going to be a problem. [11:40] I'm guessing not since it's not like you're doing this every 5 minutes. [11:41] I think it's more of a potential concern for the sa-update cron job. [11:42] http://alestic.com/2010/01/vmbuilder-ebs-boot-ami [11:42] feedback welcomed [11:46] erichammond: you don't say what AMI and EBS stand for :P [11:47] ec2 makes me assume they're a eucalyptus thing [11:47] twb: Good point. However, if somebody doesn't know what those mean, they are not the target audience of this article :) [11:48] I figured :-) [11:50] EC2 is a service run by Amazon which provides on-demand, self-service, pay-as-you-go computing infrastructure including virtual servers. [11:50] Eucalyptus implements something like EC2 but you run it on your own hardware. [11:51] I use EC2 extensively. I've never used Eucalyptus. [11:52] When you start a virtual server on Amazon EC2 (or Eucalyptus for that matter, but I'll stop mentioning it) you need to tell it the Amazon machine image (AMI) which you want the server to run. [11:53] This determines the Linux distro (or OpenSolaris or Windows version) as well as what software is installed by default and how it is configured. [11:53] There are a number of publicly available AMIs which you can choose from, including Ubuntu ones built by the great folks on this channel. [11:54] In some situations, though, you may want to build your own custom AMIs which is what this article provides steps for advanced users to take and adapt. [11:55] erichammond: thx for the mini lecture - appreciated here :-) [11:56] EBS is Amazon's Elastic Block Store which is persistent storage on EC2. Instances run from normal (S3 based) AMIs lose everything stored on local disk when they are terminated. Instances run from EBS boot AMIs have their root disk stored persistently and they can stop/start at will just like you would expect from a normal physical computer. [11:57] I'm not sure if it's useful without me talking, but here is a presentation I gave about building custom AMIs for EC2 at OSCON 2009: http://oscon2009talk.notlong.com [11:59] I will be updating the talk to use vmbuilder instead of ec2ubuntu-build-ami for presenting at the next venue which will have me. [12:20] Hey folks, do you see any issues in deploying UEC on Amazon EC2? [12:27] alonswartz: It won't work. [12:28] erichammond, could you explain why? [12:31] alonswartz: There are VM experts on this channel. I am not one of them. All I know is that nobody has been able to get any second level VM working on top of of EC2's custom Xen framework and lived to tell the tale. [12:31] (As it turns out I can be an EC2 expert without knowing much about VMs. One of the beauties of EC2 is it hides (almost) all that stuff from you.) [12:32] i'm using samba 3.4.0 server and on linux client 3.4.4 [12:32] when copy big files, there are almost allways transmission errors. So when copy from client to server the resulting md5 sums of the copied files are almost allways different [12:32] this happens only with samba. I also used NFS or RSYNC and there were never errors so far [12:34] erichammond: I've been following alestic since its conception, you do great work! [12:35] it seems like an interesting project to get UEC running ontop of ec2, i'll give it a stab, but if those who have tried are willing to share their experience, that would be great [12:38] Aison: character set issue? just an idea [12:42] pmatulis, don't think so. Do the characterset affect the content of the file? [12:44] Aison: well you can configure samba for different character sets, so it must do something at that level [12:44] Aison: check your smb.conf for character sets (man smb.conf) [12:44] I think that only affects the filenames [12:45] Aison: like i said, just something to investigate (an idea) [12:46] I just noticed, that with windows clients, there are no errors ;) [12:51] alonswartz: The people who have tried to run a VM on top of EC2 and failed over the last few years shared their experience on the EC2 forum: http://ec2forum.notlong.com [12:51] It doesn't have the best search engine, unfortunately [12:52] erichammond: thanks, i'll take a look === freeflyi1g is now known as freeflying === cyphermox_ is now known as cyphermox [13:31] morning [13:31] mornin' [13:37] New bug: #498734 in samba (main) "nmbd stops randomly -> cannot access using hostname from Windows XP" [Low,Incomplete] https://launchpad.net/bugs/498734 [13:47] New bug: #501364 in postfix (main) "Postfix not sending SMFIC_RCPT to milter, libmilter rejecting state transition" [Wishlist,Confirmed] https://launchpad.net/bugs/501364 [13:48] morning, server devs :-) [13:49] morning kirkland === zzz2009 is now known as jla === dendro-a` is now known as dendro-afk [14:33] good morning / happy new year all. [14:35] morning smoser [14:42] someone knows; ppa build daemons can't access net during building? [14:44] ivoks: They can't. [14:44] that's bad... :/ [14:44] No it isn't. [14:44] hey smoser [14:45] well, depends on point of view [14:45] ivoks: its just like the regular builds [14:45] ivoks: happy new year btw [14:45] smoser: happy 2010 to you too ! [14:45] i have one source that uses network resource for building [14:45] zul: happy new year :) [14:45] happy new 20101 everybody! [14:46] warning: failed to load external entity "http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl" [14:46] ivoks: then it's not fully reproducible, since it depends on "something else" [14:46] i guess i should install docbook-xsl and use it instead of the network resource [14:47] ivoks: I don't know... but it sounds like a good idea :) [14:54] ivoks: I'm curious for your opinion on what we should do about bug 502615 [14:54] Launchpad bug 502615 in spamassassin "/etc/cron.daily/spamassassin should restart amavisd" [Undecided,New] https://launchpad.net/bugs/502615 [14:54] i'm wearing my cluster hat at the moment :) [14:55] why should it restart amavis? [14:55] huh? [14:55] amavis just uses spamassassin daemon [14:55] it isn't aware of spamassassin rules [14:55] OK, just comment in the bug then when you have a moment please. [14:55] it just pases mail to spamassassin [14:55] ok === robbiew_ is now known as robbiew [15:02] ivoks: Are you sure? [15:02] I'm not :) [15:02] i'm not; i didn't check [15:02] but if amavis calls spam client to check mail [15:03] i don't see why it shuould be restarted [15:03] it's like restarting firefox cause your apache now has PHP module :) [15:03] or restarting amavis cause you have new clamav [15:04] anyway, i'll take a look as soon as i finish cluster stuff [15:06] Anyone here familiar with NPIV? I have QLogic QLE2560 adapters and Brocade-switches with NPIV Enabled on the ports to the server. But /sys/class/fc_host/host3/max_npiv_vports is "0", and "echo '2100001b32fff001:2000001b32fff001' > /sys/class/fc_host/host3/vport_create" gives "write error: No space left on device"; I.e. no NPIV ports gets created. Ideas? [15:07] "port_type" is; NPort (fabric via point-to-point) [15:07] So that should be correct.. [15:08] hello [15:09] can anyone tell me how to go about having a CGI script run instead of index.html? [15:13] DavidLevin, hi [15:14] ..and Welcome :D [15:15] hi [15:26] mathiaz: happy new year [15:26] ivoks: happy new year ! [15:26] ivoks: how are you doing? [15:27] good, you? [15:28] ivoks: \o/ [15:28] jolly, eh? :D [15:28] i have a workaround for NFS'd /home in 9.10 [15:29] instead in /home, mount it in /media/home and then add mount -o bind /media/home /home to rc.local [15:29] :D [15:31] Zim_: Ehm, you'd have to set ExecCGI on that dir [15:32] Jeeves: thanks for the pointer [15:33] np! [15:33] hi mathiaz [15:33] Jeeves: Do i place the script in cgi-bin or the /var/www directory [15:34] Zim_: That depends [15:34] if you put it in the cgi-bin, your url looks differen [15:34] +t [15:35] Looks like I'll have rename the index.html to something else, plus change all the urls that link to it, and put the script in the www flder [15:36] Uh, possibly [15:44] zul: hi - what's the story about autofs? [15:44] zul: is autofs 5 stable enough to be move to main in place of autofs 4? [15:48] mathiaz: i think so both rhel and suse use it [15:49] mathiaz: im gong to done the MIR request today [15:56] kirkland: ttx: are the current lucid eucalyptus packages functional? [15:56] kirkland: ttx: or should I stick to the alpha1? [15:57] mathiaz: they should be functional [15:57] mathiaz: i think we'd like to know if they're not :-) [15:57] kirkland: ok - I'll test them [15:57] smoser: eta 3 mins [15:57] mathiaz: theer are a number of issues [15:58] mathiaz: like bug 499491 [15:58] Launchpad bug 499491 in openvpn "tun module no longer automatically available (was: Euca 1.6.2 fails to boot an instance)" [High,Invalid] https://launchpad.net/bugs/499491 [15:58] jibouman` and ttx: when you got a sec can you comment on bug 491510 [15:58] Launchpad bug 491510 in monit "MIR for monit." [Undecided,Incomplete] https://launchpad.net/bugs/491510 [16:05] folks, am I going nuts? I've just been told that there is not CGI language!?! I thought it was perl [16:05] Zim_: I do cgi in Python. [16:05] *no not not [16:06] cgi and programming language are reasonably orthogonal. [16:07] ScottK: am i understanding correctly when Im thinking you write a python script, but save it as .cgi? [16:07] It was more complex than that, but yes. [16:07] I also first set it up 5 years ago, so I don't recall the details. [16:07] cgi is an interface, not a language [16:08] a way to call programs from a web server. [16:08] thats what the I stands for ;) [16:08] in CGI :) [16:08] CGL ? :) [16:08] hehe [16:08] thanks chaps [16:10] zul: about bug 491510 -- you should check with the ubuntuone people [16:10] Launchpad bug 491510 in monit "MIR for monit." [Undecided,Incomplete] https://launchpad.net/bugs/491510 [16:10] how badly needed it is, and would it be server or clientside. [16:11] *sigh* ok [16:12] Hmmm [16:13] Is there a channel about Launchpad/PPA on Freenode? [16:14] Jeeves_: #launchpad [16:14] I could've guessed that :) [16:15] ScottK: a restart of amavis maybe needed in order to fix stale any stale sockets. If I remember correctly amavis uses the spamassissin socket and smtp protocol to pass email for checking. If you stop adn restart [16:15] If anyone happends to google this: Brocade switches has to be in "Access Gateway Mode" to enable NPIV to hosts, even if you've set each port to "Enable NPIV". If it is not set up in such a way, max_npiv_vports is reported as 0. Using "Access Gateway Mode" disables all other normal switch features like zoning, so that kinda blows. [16:15] jla: right, restarting amavis is pointless [16:15] ivoks: I think that's the opposite of what he said? [16:15] If you restart spamassassin i think amavis will be using the "wrong" socket. [16:16] that's a bug in amavis [16:16] Does it eventually straighten itself out or does it last forever? [16:17] i'll do some testing tomorrow [16:18] Thanks [16:19] and hopefully start working on mail stack [16:19] How that a bug, amavis picks up spamassassin's socket when it starts and keeps it open, you kill the sa the socket is now stale, a reload/restart fixes the problem [16:19] ttx: so eucalyptus.conf .... [16:19] ttx: to fix Bug #458211, i'd like to change the way its generated [16:20] Launchpad bug 458211 in eucalyptus "eucalyptus.conf, euca_conf is confusing and underdocumented" [Undecided,Confirmed] https://launchpad.net/bugs/458211 [16:20] ttx: and fix and fix Bug #487275, too [16:20] Launchpad bug 487275 in eucalyptus "eucalyptus.conf should not be a conffile" [High,Triaged] https://launchpad.net/bugs/487275 [16:20] ttx: i'd like to move all of the documentation into a manpage [16:20] ttx: and generate the file such that it's not a conffile [16:20] ttx: and only write the pertinent parts to eucalyptus.conf [16:21] ivoks: If you start working on it, that's great. I've had no time. You might want to start with making the dovecot-postfix patch in dovecot apply so the package will build. [16:21] ttx: as the eucalyptus-nc's eucalyptus.conf (for instance) contains a bunch of cruft that's not pertinent to NCs [16:21] kirkland: you would generate it from user-configurable or state-driven bits ? [16:21] ScottK: yep... [16:21] s/or/and/ [16:21] take care... got to go now [16:22] kirkland: I have two issues with it currently [16:22] ScottK: Again from memory the condition lasts until amavis is restarted. Also from memory you may also need a restart because amavis builds its own sa config dynamically [16:22] kirkland: one is the "non-pertinent" thing [16:22] kirkland: the other is the "let's make euca_conf rewrite parts of it" approach [16:22] jla: Thanks. I'll be interested to see what ivoks' testing produces. He's pretty smart about this stuff. [16:22] ttx: i don't think i understand your question ... [16:22] ttx: user-configurable == debconf ? [16:23] kirkland: my question doesn't make sense, i'll rephrase [16:23] kirkland: what do you mean by "generate the file" ? [16:24] ttx: well, drop it from the files installed by the package [16:24] ttx: and generate it in the postinst, if it doesn't already exist [16:24] ttx: that was my initial thought [16:25] ttx: debconf'ing each of the items would be nice, i thought [16:25] ttx: since we already do some of them [16:25] ttx: and would put a prettier front end on it [16:25] ttx: make it far more usable [16:25] kirkland: one issue is that euca_conf rewrites eucalyptus.conf [16:25] ttx: though that's slightly more work that I'd want to commit to for a2 [16:26] kirkland: another way to do it would be to make eucalyptus.conf source several files, some of them user-configurable, some of them state-driven (like the NODES= line) [16:27] ttx: i think i like that idea ... create a hierarchy of sourced files [16:27] and make sure euca_conf only messes with /var/lib/eucalyptus/configured_nodes and friends [16:27] ttx: we could install a "base" eucalyptus-base.conf with the common defaults [16:28] kirkland: ultimately I'd like the component registration process not require to run as root [16:28] ttx: then debconf could write eucalyptus-custom.conf [16:28] ttx: ah, debconf requires root, right [16:28] kirkland: at that point autoregistration through euca_conf needs to rewrite eucalyptus.conf === mushroomb1ue is now known as mushroomblue [16:29] ttx: right [16:29] kirkland: so all the registration tasks run as root, which is... scary. [16:29] ttx: okay, i'll think on this a little more, but I like the idea of a hierarchy of sourced files [16:30] * ScottK looks at Bug #502071 and thinks "Not bad". Fixes uploaded, tested and relesead for production in two days on 5 releases. [16:30] Launchpad bug 502071 in spamassassin "FH_DATE_PAST_20XX scores on all mails dated 2010 or later" [High,Fix released] https://launchpad.net/bugs/502071 [16:30] ttx: what about this .... [16:30] ttx: the package installs a base /etc/eucalyptus/eucalyptus.conf (as it does now) [16:30] kirkland: if we can change it so that euca_conf can run as "eucalyptus" it's slightly less scary. [16:30]