similar to: 0.24.0 won''t start

Hi all, As promised, 0.24.1 is out. Here''s the changelog: Updated vim filetype detection. (#900 and #963) Default resources like schedules no longer conflict with managed resources. (#965) Removing the ability to disable http keep-alive, since it didn''t really work anyway and it should no longer be necessary. Refactored http keep-alive so

I recently purchased a Tripp Lite OmniSV1500XL and I've had no luck getting nut to work. # lsusb Bus 001 Device 001: ID 0000:0000 Bus 006 Device 002: ID 05e3:0702 Genesys Logic, Inc. USB 2.0 IDE Adapter Bus 006 Device 001: ID 0000:0000 Bus 002 Device 001: ID 0000:0000 Bus 005 Device 001: ID 0000:0000 Bus 007 Device 001: ID 0000:0000 Bus 004 Device 009: ID 09ae:0001 Tripp Lite Bus 004 Device

Hi all, please forgive me for such a newbie question, but I thought it would best to tap the wealth of experience here. I''m a new Rails guy but I''m evaluating frameworks for use in an intranet at a back whose internal systems are Oracle on linux. For now all my data will be on a dedicated box but down the road I may need to make calls into other databases hosted on other

Just started a "pilot" puppet server for real after messing around in VMs for the past week or so... I used the 0.24.0 since it was available, and on the test run, got this: err: Could not prefetch package provider ''yum'': Execution of ''/usr/bin/python /usr/lib/ruby/site_ruby/1.8/puppet/provider/package/yumhelper.py'' returned 512: /usr/bin/python:

xf86-input-libinput 0.24.0 is now available. A couple of new features were added this cycle: * tablets now support a configurable pressure curve * tablets now have a 'area ratio' setting to be able to match the tablet aspect ratio with that of the screen * the mouse wheel's click angle now (correctly) affects how fast the scroll wheel triggers. In particular, if you have a wheel

Hi, I was managing a bunch of Centos 4.5 with Puppet until the ruby security patch bit me creating ssl problems. As I''m not able/willing to patch the installed version I tried upgrading to dlutter''s 0.24.0-2.el5 version. Unfortunately this didn''t help much. So I removed the server and client installation completely (making sure to manually remove the config, ssl, ...

I''ve now fixed all of the bugs I''m going to fix for 0.24.0/misspiggy. Please test that the current ''master'' branch in git works for you. I''ll probably release tomorrow, or maybe early on Thursday if I don''t hear of any show-stoppers. -- I don''t want any yes-men around me. I want everybody to tell me the truth even if it

Hi all, Hobbeswalsh on IRC has discovered a backward compatibility issue in 0.24.0, preventing 0.23.x clients working well with 0.24.0 servers. Specifically, you can''t specify relationships to builtin resources when the client is 0.23.x, although specifying relationships to defined resources still works. The problem is that prior to 0.24.0 there was no central class

I created ticket 961 "puppetd create too many/not closing TCP connections". I''m wondering if anyone else is seeing this? Depending on the client configuration a typical puppetd run will cause hunderds of simultaneous TCP connections to be opened to the puppet master. I''m gettting over 300 established connections for a single client in some cases. If the number of

I see in the changelog that: You now must specify an environment and you are required to specify the valid environments for your site. (#911) Does this mean that the puppetmaster has to be updated before clients work correctly? I ask because I''m testing out a client upgrade to 0.24.0 (server is still 0.23.2) and this is what I''m seeing: [~]% sudo /foo/bin/puppetd

At long last, 0.24.0 has been released. Look for your friendly packagers to package it up in the near future, but in the meantime you can download it: http://reductivelabs.com/downloads/puppet/puppet-0.24.0.tgz I''ll be walking the different release sites (RubyForge et al) and posting it there, too. Look for a related announcement later today on changes in development practices

Hi, I was wondering if there is any of getting the gem package provider to run non-interactively? When upgrading mongrel it fails because it gets prompted for which version to install: Attempting remote update of mongrel Select which gem to install for your platform (x86_64-linux) 1. mongrel 1.1.1 (ruby) 2. mongrel 1.1.1 (jruby) 3. mongrel 1.1.1 (mswin32) 4. mongrel 1.1 (mswin32) 5.

this time when I try to connect the first node: [root@qaagt20 ~]# /etc/init.d/puppet start Starting puppet: /usr/lib/ruby/1.8/net/http.rb:560:in `initialize'': No route to host - connect(2) (Errno::EHOSTUNREACH) from /usr/lib/ruby/1.8/net/http.rb:560:in `open'' from /usr/lib/ruby/1.8/net/http.rb:560:in `connect'' from

I have noticed that the image_tag helper method now appends a request parameter to the generated src attribute. With Rails 1.0/actionpack-1.11.2 I had <img src="/images/rss.gif" /> Now (1.1/1.12.1) I get <img alt="Rss" border="0" src="/images/rss.gif?1142366545" /> Is there any use for that number? Where does it come from? This is very far

Hi, I have noticed that in the conf directory of the puppet gem there are a bunch of files such as: - init.d scripts for starting/stopping puppetd - sysconfig files for redhat - logrotate files .. etc Is there some automatic way of using these files or are they just example config files that we can install ourselves. thanks, Iain. -- Iain Pople Systems Interface Technical Lead University

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi list, I have a charset problem. I'm using Debian unstable, 2.4.25 kernel (debian kernel-image) and samba 3.0.5. I want to mount a windows2000 share which contains chinese filenames. My locale is set to en_US.UTF-8. When I connect to the windows machine with smbclient, it can display the filenames correctly (chinese characters). So, I assume

We recently migrated our install from an ancient fedora 11 install of samba and openldap to a centos 6.3 setup with its openldap and samba. The domain has been totally recreated from scratch as the person that did the previous setup has not been employed here in many years. After fighting with shares for a while we mostly got them fixed and working. However the biggest issue now is when our GIS

Hello, since few days there are problems with the userdb lookup. The problem occur if the recipient user is unknown (here test at xtlv.cn) doveconf -n # 2.2.6 (f89e645cba90): /etc/dovecot/dovecot.conf # OS: Linux 3.2.45.stk32 i686 Debian jessie/sid ext3 auth_debug = yes auth_debug_passwords = yes auth_mechanisms = digest-md5 cram-md5 auth_username_translation = %Lu auth_verbose = yes

Apart from religious grounds (!), is there any pros or cons why I should choose one over the other for a new install of asterisk ? Julian

I have a reproducible intermittent error large site - "The specified network name is no longer available". This happens when copying large files. Below is part of log level 10 output & strace. Sorry for the long posting. I will probably need to put the loglevel 10 attached to a bugzilla - but thought I would try the lists initially. RHEL4 samba-3.0.25b-1.el4_6.4