Menu
▾
▴
etch-users — General discussion and questions about using etch
You can subscribe to this list here.
| 2008 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(3) |
Dec
(1) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2009 |
Jan
(1) |
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
(9) |
Nov
(10) |
Dec
(5) |
| 2010 |
Jan
(10) |
Feb
|
Mar
|
Apr
|
May
(4) |
Jun
(2) |
Jul
|
Aug
(5) |
Sep
(2) |
Oct
(2) |
Nov
|
Dec
(1) |
| 2011 |
Jan
(1) |
Feb
|
Mar
|
Apr
(1) |
May
(29) |
Jun
(9) |
Jul
(4) |
Aug
(8) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2012 |
Jan
|
Feb
(1) |
Mar
(13) |
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
| 2014 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
| 2021 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
|
From: Johnston, N. <Nat...@ca...> - 2011-05-16 17:02:40
|
Is there any support for an external script to output the equivalent to the nodegroups.xml file? --N. On May 16, 2011, at 12:59 PM, Jason Heiss wrote: The output from nodegrouper is plain text, one group name per line. I.e.: % nodegrouper host1.example.com<http://host1.example.com> group1 group2 othergroup On May 16, 2011, at 9:49 AM, Johnston, Nathaniel wrote: I am not using nVentory, so I am unable to grok the provided example script for externally based "nodegrouper". If I am fashioning my own "nodegrouper" script, will the output be XML? Can you give me an example of what the output would look like? Thanks much! --N. --N. ---- Nate Johnston "You are what you automate." Nat...@ca...<mailto:Nat...@ca...> ph:703-939-8521 |
|
From: Jason H. <jh...@ap...> - 2011-05-16 16:59:49
|
The output from nodegrouper is plain text, one group name per line. I.e.: % nodegrouper host1.example.com group1 group2 othergroup On May 16, 2011, at 9:49 AM, Johnston, Nathaniel wrote: > I am not using nVentory, so I am unable to grok the provided example script for externally based "nodegrouper". If I am fashioning my own "nodegrouper" script, will the output be XML? Can you give me an example of what the output would look like? > > Thanks much! > > --N. |
|
From: Johnston, N. <Nat...@ca...> - 2011-05-16 16:49:35
|
I am not using nVentory, so I am unable to grok the provided example script for externally based "nodegrouper". If I am fashioning my own "nodegrouper" script, will the output be XML? Can you give me an example of what the output would look like? Thanks much! --N. |
|
From: Spyda <web...@gm...> - 2011-05-16 16:37:02
|
Thanks a mill for your response, I cant even get to the unicorn start because I get stuck just installing the gems :( I have reinstalled all the deb packages, even installed the rubygems from the tgz package and managed to upgrade gem from 1.8.1 to 1.8.2 I am running Debian Squeeze (just upgraded from lenny) Here is the info you were looking for: server# dpkg --list |grep ruby ii libruby1.8 1.8.7.302-2 Libraries necessary to run Ruby 1.8 ii ruby 4.5 An interpreter of object-oriented scripting language Ruby ii ruby-dev 4.5 Header files for compiling extension modules for Ruby ii ruby1.8 1.8.7.302-2 Interpreter of object-oriented scripting language Ruby 1.8 ii ruby1.8-dev 1.8.7.302-2 Header files for compiling extension modules for the Ruby 1.8 ii rubygems 1.3.7-3 package management framework for Ruby libraries/applications ii rubygems1.8 1.3.7-3 package management framework for Ruby libraries/applications server# gem -v 1.8.2 server# rake gems:install --trace (in /opt/etch-3.19.0/server) DEPRECATION WARNING: Rake tasks in vendor/plugins/open_flash_chart/tasks are deprecated. Use lib/tasks instead. (called from /usr/lib/ruby/gems/1.8/gems/rails-2.3.11/lib/tasks/rails.rb:10) ** Invoke gems:install (first_time) ** Invoke gems:base (first_time) ** Execute gems:base ** Invoke environment (first_time) ** Execute environment rake aborted! undefined method `name' for "actionmailer":String /usr/lib/ruby/gems/1.8/gems/rails-2.3.11/lib/rails/gem_dependency.rb:277:in `==' /usr/local/lib/site_ruby/1.8/rubygems/dependency.rb:217:in `===' /usr/local/lib/site_ruby/1.8/rubygems/dependency.rb:217:in `matching_specs' /usr/local/lib/site_ruby/1.8/rubygems/custom_require.rb:36:in `find_all' /usr/local/lib/site_ruby/1.8/rubygems/specification.rb:403:in `each' /usr/local/lib/site_ruby/1.8/rubygems/specification.rb:402:in `each' /usr/local/lib/site_ruby/1.8/rubygems/dependency.rb:216:in `find_all' /usr/local/lib/site_ruby/1.8/rubygems/dependency.rb:216:in `matching_specs' /usr/local/lib/site_ruby/1.8/rubygems/dependency.rb:238:in `to_specs' /usr/local/lib/site_ruby/1.8/rubygems/dependency.rb:256:in `to_spec' /usr/local/lib/site_ruby/1.8/rubygems.rb:1182:in `gem' /usr/lib/ruby/gems/1.8/gems/rails-2.3.11/lib/rails/gem_dependency.rb:75:in `add_load_paths' /usr/lib/ruby/gems/1.8/gems/rails-2.3.11/lib/initializer.rb:301:in `add_gem_load_paths' /usr/lib/ruby/gems/1.8/gems/rails-2.3.11/lib/initializer.rb:301:in `each' /usr/lib/ruby/gems/1.8/gems/rails-2.3.11/lib/initializer.rb:301:in `add_gem_load_paths' /usr/lib/ruby/gems/1.8/gems/rails-2.3.11/lib/initializer.rb:132:in `process' /usr/lib/ruby/gems/1.8/gems/rails-2.3.11/lib/initializer.rb:113:in `send' /usr/lib/ruby/gems/1.8/gems/rails-2.3.11/lib/initializer.rb:113:in `run' /opt/etch-3.19.0/server/config/environment.rb:13 /usr/local/lib/site_ruby/1.8/rubygems/custom_require.rb:36:in `gem_original_require' /usr/local/lib/site_ruby/1.8/rubygems/custom_require.rb:36:in `require' /usr/lib/ruby/gems/1.8/gems/activesupport-2.3.11/lib/active_support/dependencies.rb:182:in `require' /usr/lib/ruby/gems/1.8/gems/activesupport-2.3.11/lib/active_support/dependencies.rb:547:in `new_constants_in' /usr/lib/ruby/gems/1.8/gems/activesupport-2.3.11/lib/active_support/dependencies.rb:182:in `require' /usr/lib/ruby/gems/1.8/gems/rails-2.3.11/lib/tasks/misc.rake:4 /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:636:in `call' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:636:in `execute' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:631:in `each' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:631:in `execute' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:597:in `invoke_with_call_chain' /usr/lib/ruby/1.8/monitor.rb:242:in `synchronize' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:590:in `invoke_with_call_chain' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:583:in `invoke' /usr/lib/ruby/gems/1.8/gems/rails-2.3.11/lib/tasks/gems.rake:17 /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:636:in `call' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:636:in `execute' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:631:in `each' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:631:in `execute' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:597:in `invoke_with_call_chain' /usr/lib/ruby/1.8/monitor.rb:242:in `synchronize' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:590:in `invoke_with_call_chain' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:607:in `invoke_prerequisites' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:604:in `each' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:604:in `invoke_prerequisites' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:596:in `invoke_with_call_chain' /usr/lib/ruby/1.8/monitor.rb:242:in `synchronize' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:590:in `invoke_with_call_chain' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:583:in `invoke' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2051:in `invoke_task' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2029:in `top_level' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2029:in `each' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2029:in `top_level' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2068:in `standard_exception_handling' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2023:in `top_level' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2001:in `run' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2068:in `standard_exception_handling' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:1998:in `run' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/bin/rake:31 /usr/bin/rake:19:in `load' /usr/bin/rake:19 ---------------------------------- Thank you for your time. Gareth On 16 May 2011 17:21, Jason Heiss <jh...@ap...> wrote: > Rails is somehow failing to assemble itself, but that particular error is a > new one on me. Google turned up a few other folks with the same error > message, but no obvious solution. > > A couple of thoughts though. I don't know if any of these will help narrow > down the problem. > > If you're trying to set up a production install you'll want to set your > RAILS_ENV environment variable to "production" before running any commands. > Otherwise rails will default to the "development" database configuration in > config/database.yml. Eventually you'll want an init script or similar that > sets RAILS_ENV before firing up unicorn, but for the rake commands to > install gems and setup the database it's easiest to just set it manually. > > What version of rubygems do you have? (gem -v) It's possible you have an > old version that isn't compatible with newer versions of rails. You can > update with "sudo gem update --system" and see if that changes anything. > > Jason > > On May 16, 2011, at 2:25 AM, Gareth Greener wrote: > > > Hi, > > > > I am quite new to Ruby and I have etch working on a test machine, but > really struggling to install it in my production environment. > > I have followed all the steps to install but I get an error on the below: > > > > server# rake gems:install > > (in /opt/etch-3.19.0/server) > > DEPRECATION WARNING: Rake tasks in vendor/plugins/open_flash_chart/tasks > are deprecated. Use lib/tasks instead. (called from > /usr/lib/ruby/gems/1.8/gems/rails-2.3.11/lib/tasks/rails.rb:10) > > rake aborted! > > undefined method `name' for "actionmailer":String > > > > (See full trace by running task with --trace) > > > > *** LOCAL GEMS *** > > > > actionmailer (2.3.11, 2.3.8) > > actionpack (2.3.11, 2.3.8) > > activerecord (2.3.11, 2.3.8) > > activeresource (2.3.11, 2.3.8) > > activesupport (2.3.11, 2.3.8) > > etch (3.19.0) > > facter (1.5.8) > > kgio (2.4.0) > > libxml-ruby (1.1.2) > > rack (1.1.2) > > rails (2.3.11, 2.3.8) > > rake (0.8.7) > > sqlite3 (1.3.3) > > sqlite3-ruby (1.3.3) > > unicorn (3.6.2) > > > > > > ------------------------------ > > Thanks for your time. > > > > Gareth > > > > > ------------------------------------------------------------------------------ > > Achieve unprecedented app performance and reliability > > What every C/C++ and Fortran developer should know. > > Learn how Intel has extended the reach of its next-generation tools > > to help boost performance applications - inlcuding clusters. > > > http://p.sf.net/sfu/intel-dev2devmay_______________________________________________ > > etch-users mailing list > > etc...@li... > > https://lists.sourceforge.net/lists/listinfo/etch-users > > |
|
From: Jason H. <jh...@ap...> - 2011-05-16 16:22:06
|
Rails is somehow failing to assemble itself, but that particular error is a new one on me. Google turned up a few other folks with the same error message, but no obvious solution. A couple of thoughts though. I don't know if any of these will help narrow down the problem. If you're trying to set up a production install you'll want to set your RAILS_ENV environment variable to "production" before running any commands. Otherwise rails will default to the "development" database configuration in config/database.yml. Eventually you'll want an init script or similar that sets RAILS_ENV before firing up unicorn, but for the rake commands to install gems and setup the database it's easiest to just set it manually. What version of rubygems do you have? (gem -v) It's possible you have an old version that isn't compatible with newer versions of rails. You can update with "sudo gem update --system" and see if that changes anything. Jason On May 16, 2011, at 2:25 AM, Gareth Greener wrote: > Hi, > > I am quite new to Ruby and I have etch working on a test machine, but really struggling to install it in my production environment. > I have followed all the steps to install but I get an error on the below: > > server# rake gems:install > (in /opt/etch-3.19.0/server) > DEPRECATION WARNING: Rake tasks in vendor/plugins/open_flash_chart/tasks are deprecated. Use lib/tasks instead. (called from /usr/lib/ruby/gems/1.8/gems/rails-2.3.11/lib/tasks/rails.rb:10) > rake aborted! > undefined method `name' for "actionmailer":String > > (See full trace by running task with --trace) > > *** LOCAL GEMS *** > > actionmailer (2.3.11, 2.3.8) > actionpack (2.3.11, 2.3.8) > activerecord (2.3.11, 2.3.8) > activeresource (2.3.11, 2.3.8) > activesupport (2.3.11, 2.3.8) > etch (3.19.0) > facter (1.5.8) > kgio (2.4.0) > libxml-ruby (1.1.2) > rack (1.1.2) > rails (2.3.11, 2.3.8) > rake (0.8.7) > sqlite3 (1.3.3) > sqlite3-ruby (1.3.3) > unicorn (3.6.2) > > > ------------------------------ > Thanks for your time. > > Gareth > > ------------------------------------------------------------------------------ > Achieve unprecedented app performance and reliability > What every C/C++ and Fortran developer should know. > Learn how Intel has extended the reach of its next-generation tools > to help boost performance applications - inlcuding clusters. > http://p.sf.net/sfu/intel-dev2devmay_______________________________________________ > etch-users mailing list > etc...@li... > https://lists.sourceforge.net/lists/listinfo/etch-users |
|
From: Gareth G. <gar...@gm...> - 2011-05-16 09:26:00
|
Hi, I am quite new to Ruby and I have etch working on a test machine, but really struggling to install it in my production environment. I have followed all the steps to install but I get an error on the below: server# rake gems:install (in /opt/etch-3.19.0/server) DEPRECATION WARNING: Rake tasks in vendor/plugins/open_flash_chart/tasks are deprecated. Use lib/tasks instead. (called from /usr/lib/ruby/gems/1.8/gems/rails-2.3.11/lib/tasks/rails.rb:10) rake aborted! undefined method `name' for "actionmailer":String (See full trace by running task with --trace) *** LOCAL GEMS *** actionmailer (2.3.11, 2.3.8) actionpack (2.3.11, 2.3.8) activerecord (2.3.11, 2.3.8) activeresource (2.3.11, 2.3.8) activesupport (2.3.11, 2.3.8) etch (3.19.0) facter (1.5.8) kgio (2.4.0) libxml-ruby (1.1.2) rack (1.1.2) rails (2.3.11, 2.3.8) rake (0.8.7) sqlite3 (1.3.3) sqlite3-ruby (1.3.3) unicorn (3.6.2) ------------------------------ Thanks for your time. Gareth |
|
From: Pat O'B. <obr...@gm...> - 2011-05-16 04:50:50
|
> We have our 6 etch servers independently pulling from subversion once an hour using the repo_update script included in the distribution. > > It works fine for normal distribution, but is somewhat suboptimal when you want to push something out in a hurry because you have to manually go to each server and run repo_update. > > It also means that there's no quick way to deploy the killswitch (https://sourceforge.net/apps/trac/etch/wiki/ControlledDeployment). In my previous job I set up a separate once a minute cronjob to just update the killswitch so that at least that file was synced quickly without thrashing the subversion servers too much. > > So I'm also curious if there are any ideas out there about how to improve this. It seems like there should be a better approach, but it isn't something I've spent much time pondering. > > Jason We just have a cronjob that runs every five minutes on both servers which updates trunk from SVN rather than updating it manually or waiting an hour if we have to quickly push a change. -pat |
|
From: Jason H. <jh...@ap...> - 2011-05-13 21:19:23
|
On May 13, 2011, at 1:36 PM, Kenneth Williams wrote: > I've started moving my rails apps from a single server to a cluster. I'm curious how other etch users are handling syncing /etc/etchserver/source across multiple servers. I've thought of designating a master and using NFS, or rsync. I've also thought about using subversion and running a periodic checkout from each node in the cluster. I'm curious how other users are doing this to see if there are other options, or if anyone has used the three above and have any thoughts? Thanks! We have our 6 etch servers independently pulling from subversion once an hour using the repo_update script included in the distribution. It works fine for normal distribution, but is somewhat suboptimal when you want to push something out in a hurry because you have to manually go to each server and run repo_update. It also means that there's no quick way to deploy the killswitch (https://sourceforge.net/apps/trac/etch/wiki/ControlledDeployment). In my previous job I set up a separate once a minute cronjob to just update the killswitch so that at least that file was synced quickly without thrashing the subversion servers too much. So I'm also curious if there are any ideas out there about how to improve this. It seems like there should be a better approach, but it isn't something I've spent much time pondering. Jason |
|
From: Kenneth W. <hap...@gm...> - 2011-05-13 20:36:41
|
I've started moving my rails apps from a single server to a cluster. I'm curious how other etch users are handling syncing /etc/etchserver/source across multiple servers. I've thought of designating a master and using NFS, or rsync. I've also thought about using subversion and running a periodic checkout from each node in the cluster. I'm curious how other users are doing this to see if there are other options, or if anyone has used the three above and have any thoughts? Thanks! -- Kenneth Williams |
|
From: Jason H. <jh...@ap...> - 2011-05-12 20:29:29
|
On May 12, 2011, at 9:48 AM, Johnston, Nathaniel wrote: > It appears that there might be a discrepancy in the documentation. According to the GettingStarted page on the Etch Wiki, we should run "gem install rails -v 2.3.8". > > Yet when I run unicorn_rails, I get a version error: > >> RubyGem version error: rails(2.3.8 not = 2.3.11) > > Do we have other gems that need to be tied to specific versions? Or does the documentation need to change to update the rails version? Sorry, I forgot to update the wiki. Rails 2.3.11 is the version used in the latest etch release. I've now updated the wiki to match. Jason |
|
From: Johnston, N. <Nat...@ca...> - 2011-05-12 16:48:14
|
It appears that there might be a discrepancy in the documentation. According to the GettingStarted page on the Etch Wiki, we should run "gem install rails -v 2.3.8". We have installed the gems as specified: # gem list *** LOCAL GEMS *** actionmailer (2.3.8) actionpack (2.3.8) activerecord (2.3.8) activeresource (2.3.8) activesupport (2.3.8) bundler (1.0.13) etch (3.19.0) facter (1.5.8) gem2rpm (0.6.0) kgio (2.4.0) libxml-ruby (1.1.2) rack (1.2.2, 1.1.2) rails (2.3.8) rake (0.8.7) sqlite3-ruby (1.2.5) unicorn (3.6.2) Yet when I run unicorn_rails, I get a version error: RubyGem version error: rails(2.3.8 not = 2.3.11) Do we have other gems that need to be tied to specific versions? Or does the documentation need to change to update the rails version? Thanks in advance for all the help, --N. |
|
From: Kenneth W. <hap...@gm...> - 2011-05-06 22:09:58
|
Very cool. This method fixed the issue, thanks!
On Fri, May 6, 2011 at 2:39 PM, Jason Heiss <jh...@ap...> wrote:
> You can stick with just using config.xml, although it gets messy if your
> configuration gets much more complicated than the "if X else" case:
>
> <config>
> <file>
> <source>
> <plain group="!vertica-prod">limits.conf.default</plain>
> <plain group="vertica-prod">limits.conf.vertica-prod</plain>
> </source>
> </file>
> </config>
>
> Or you can switch to a script and express more complicated logic:
>
> <config>
> <file>
> <source>
> <script>limits.conf.script</script>
> </source>
> </file>
> </config>
>
> limits.conf.script:
>
> if @groups.include?('vertica-prod')
> @contents << File.read('limits.conf.vertica-prod')
> elsif @groups.include?('vertica-dev')
> @contents << File.read('limits.conf.vertica-dev')
> else
> @contents << File.read('limits.conf.default')
> end
>
> On May 6, 2011, at 1:26 PM, Kenneth Williams wrote:
>
> Oddly enough this is the first time I've encountered this. I have a default
> limits.conf file that goes to all servers, but now I want to add one more
> for just a specific group. My config.xml looks like this;
>
> *<config>
> <file>
> <source>
> <plain>limits.conf.default</plain>
> <plain group="vertica-prod">limits.conf.vertica-prod</plain>
> </source>
> </file>
> </config>
> *
>
> But this returns a 500 error on the client.
>
> *Inconsistent 'plain' entries for /etc/security/limits.conf
> 500 "Internal Server Error"
> *
>
> Is there a way around this without having to specify each group for the
> "default" file? Thanks!
>
> --
> Kenneth Williams
>
> ------------------------------------------------------------------------------
> WhatsUp Gold - Download Free Network Management Software
> The most intuitive, comprehensive, and cost-effective network
> management toolset available today. Delivers lowest initial
> acquisition cost and overall TCO of any competing solution.
>
> http://p.sf.net/sfu/whatsupgold-sd_______________________________________________
> etch-users mailing list
> etc...@li...
> https://lists.sourceforge.net/lists/listinfo/etch-users
>
>
>
--
Kenneth Williams
|
|
From: Jason H. <jh...@ap...> - 2011-05-06 21:40:09
|
You can stick with just using config.xml, although it gets messy if your configuration gets much more complicated than the "if X else" case:
<config>
<file>
<source>
<plain group="!vertica-prod">limits.conf.default</plain>
<plain group="vertica-prod">limits.conf.vertica-prod</plain>
</source>
</file>
</config>
Or you can switch to a script and express more complicated logic:
<config>
<file>
<source>
<script>limits.conf.script</script>
</source>
</file>
</config>
limits.conf.script:
if @groups.include?('vertica-prod')
@contents << File.read('limits.conf.vertica-prod')
elsif @groups.include?('vertica-dev')
@contents << File.read('limits.conf.vertica-dev')
else
@contents << File.read('limits.conf.default')
end
On May 6, 2011, at 1:26 PM, Kenneth Williams wrote:
> Oddly enough this is the first time I've encountered this. I have a default limits.conf file that goes to all servers, but now I want to add one more for just a specific group. My config.xml looks like this;
>
> <config>
> <file>
> <source>
> <plain>limits.conf.default</plain>
> <plain group="vertica-prod">limits.conf.vertica-prod</plain>
> </source>
> </file>
> </config>
>
> But this returns a 500 error on the client.
>
> Inconsistent 'plain' entries for /etc/security/limits.conf
> 500 "Internal Server Error"
>
> Is there a way around this without having to specify each group for the "default" file? Thanks!
>
> --
> Kenneth Williams
> ------------------------------------------------------------------------------
> WhatsUp Gold - Download Free Network Management Software
> The most intuitive, comprehensive, and cost-effective network
> management toolset available today. Delivers lowest initial
> acquisition cost and overall TCO of any competing solution.
> http://p.sf.net/sfu/whatsupgold-sd_______________________________________________
> etch-users mailing list
> etc...@li...
> https://lists.sourceforge.net/lists/listinfo/etch-users
|
|
From: Kenneth W. <hap...@gm...> - 2011-05-06 20:26:36
|
Oddly enough this is the first time I've encountered this. I have a default
limits.conf file that goes to all servers, but now I want to add one more
for just a specific group. My config.xml looks like this;
*<config>
<file>
<source>
<plain>limits.conf.default</plain>
<plain group="vertica-prod">limits.conf.vertica-prod</plain>
</source>
</file>
</config>
*
But this returns a 500 error on the client.
*Inconsistent 'plain' entries for /etc/security/limits.conf
500 "Internal Server Error"
*
Is there a way around this without having to specify each group for the
"default" file? Thanks!
--
Kenneth Williams
|
|
From: Jason H. <jh...@ap...> - 2011-05-05 03:59:36
|
Interesting. I set up the 3.19.0 server release on a new box and copied the contents of the etchserver-demo directory from the distribution to /etc/etchserver, which looks to be what you did. In my case it fails on line etch.rb:209 (rather than etch.rb:173 in your case). That's because /etc/etchserver/source/ exists, but /etc/etchserver/commands/ does not. That problem only occurs under ruby 1.9, and will be fixed in the next release. So, the question remains why it fails on etch.rb:173 in your case, failing to find the sourcebase. Can you run the client with the --debug flag, and then look for lines in log/etchdebug.log in the server directory that looks like: Using /etc/etchserver as config base for node etchruby19.example.com Tag for node etchruby19.example.com from external node tagger: '' Using /etc/etchserver/ as tagged base for node etchruby19.example.com The server appends a "source" directory to that final "tagged base" path, and in your case that directory doesn't seem to exist. I'd assumed you had the standard nodetagger script that always returns an empty string, but now I'm guessing your nodetagger is returning something else. Jason On May 4, 2011, at 2:33 PM, Johnston, Nathaniel wrote: > Jason, > > First, thanks for taking a look at my issue. I really appreciate it! > > Second, I doublechecked to be sure, and I do indeed have an /etc/etchserver/source tree that is a copy of the etchserver-demo. In this case, Etch is running as root, so permissions issues are not an issue. > > [root@jumphost-1p ~]# find /etc/etchserver/source/ > /etc/etchserver/source/ > /etc/etchserver/source/tmp > /etc/etchserver/source/tmp/etchdemo > /etc/etchserver/source/tmp/etchdemo/directory > /etc/etchserver/source/tmp/etchdemo/directory/config.xml > /etc/etchserver/source/tmp/etchdemo/scriptfile > /etc/etchserver/source/tmp/etchdemo/scriptfile/config.xml > /etc/etchserver/source/tmp/etchdemo/scriptfile/addition > /etc/etchserver/source/tmp/etchdemo/scriptfile/scriptfile.script > /etc/etchserver/source/tmp/etchdemo/scriptfile/main > /etc/etchserver/source/tmp/etchdemo/link > /etc/etchserver/source/tmp/etchdemo/link/config.xml > /etc/etchserver/source/tmp/etchdemo/plainfile > /etc/etchserver/source/tmp/etchdemo/plainfile/config.xml > /etc/etchserver/source/tmp/etchdemo/plainfile/plainfile2 > /etc/etchserver/source/tmp/etchdemo/plainfile/plainfile > > Also, I wanted to verify with you that I have the right versions of all of the gems. This host is only being used for the etch server at this point, so the only reason for these gems is to support Etch: > > [root@jumphost-1p ~]# gem list > > *** LOCAL GEMS *** > > abstract (1.0.0) > actionmailer (3.0.7, 2.3.11, 2.3.8) > actionpack (3.0.7, 2.3.11, 2.3.8) > activemodel (3.0.7) > activerecord (3.0.7, 2.3.11, 2.3.8) > activeresource (3.0.7, 2.3.11, 2.3.8) > activesupport (3.0.7, 2.3.11, 2.3.8) > arel (2.1.0, 2.0.9) > builder (3.0.0, 2.1.2) > bundler (1.0.12) > columnize (0.3.2) > erubis (2.7.0, 2.6.6) > facter (1.5.8) > i18n (0.5.0) > kgio (2.3.3) > libxml-ruby (2.0.4, 1.1.2) > mail (2.3.0, 2.2.19) > memcache-client (1.8.5) > mime-types (1.16) > minitest (2.1.0, 1.6.0) > polyglot (0.3.1) > rack (1.1.0) > rack-mount (0.7.2, 0.6.14) > rack-test (0.5.7) > rails (3.0.7, 2.3.11, 2.3.8) > railties (3.0.7) > rake (0.8.7) > rdoc (3.5.3, 2.5.8) > searchlogic (2.5.5) > sqlite3 (1.3.3) > sqlite3-ruby (1.3.3) > thor (0.14.6) > treetop (1.4.9) > tzinfo (0.3.27) > unicorn (3.6.2) > will_paginate (2.3.15) > > Thanks, > > Nate > > > On May 4, 2011, at 12:33 AM, Jason Heiss wrote: > >> Looking at line etch.rb:173 it looks like /etc/etchserver/source doesn't exist. That's the directory where configuration for files that you want etch to manage would live. I.e. if you want etch to manage /etc/motd then the configuration for that would live in /etc/etchserver/source/etc/motd/ >> >> If you want you can copy etchserver-demo or etchserver-samples from the distribution to /etc/etchserver to get a basic structure populated. >> >> I'll add a check into etch so that in the future this results in a clear error message rather than an exception and backtrace. >> >> Thanks, >> >> Jason >> >> On May 3, 2011, at 12:20 PM, Johnston, Nathaniel wrote: >> >>> Etch Meister(s), >>> >>> I am a new user of Etch, and I am trying to get it working on a couple internal systems as an experiment. Right now I have only a single client pointed at a single server. When I run etch (as "./etch --debug --generate-all --server "http://jumphost-1p.internal:8080") I get a long stack trace (included below), and in the Etch Dashboard the server comes up as "broken". I would appreciate any insight you might have as to what is the issue, or what tack I should use to track down the issue. >>> >>> For full disclosure, I am a professional sysadmin, and have only dabbled in Ruby. >>> >>> Thanks, >>> >>> Nate >>> >>> This is from the server side's development.log: >>> >>> [Multiple fact loads precede this point] >>> Fact Load (0.1ms) SELECT * FROM "facts" WHERE ("facts"."client_id" = 2 AND "facts"."key" = 'uptime') LIMIT 1 >>> Fact Load (0.1ms) SELECT * FROM "facts" WHERE ("facts"."client_id" = 2 AND "facts"."key" = 'interfaces') LIMIT 1 >>> Fact Load (0.1ms) SELECT * FROM "facts" WHERE ("facts"."client_id" = 2 AND "facts"."key" = 'ipaddress_eth0') LIMIT 1 >>> Fact Load (0.1ms) SELECT * FROM "facts" WHERE ("facts"."client_id" = 2 AND "facts"."key" = 'macaddress_eth0') LIMIT 1 >>> Fact Load (0.1ms) SELECT * FROM "facts" WHERE ("facts"."client_id" = 2 AND "facts"."key" = 'netmask_eth0') LIMIT 1 >>> Fact Load (0.1ms) SELECT * FROM "facts" WHERE ("facts"."client_id" = 2 AND "facts"."key" = 'hardwaremodel') LIMIT 1 >>> Fact Load (0.1ms) SELECT * FROM "facts" WHERE ("facts"."client_id" = 2 AND "facts"."key" = 'facterversion') LIMIT 1 >>> Fact Load (0.8ms) SELECT * FROM "facts" WHERE ("facts"."client_id" = 2) >>> No such file or directory >>> /opt/ruby/ruby-1.9.2-p180/lib/ruby/1.9.1/find.rb:38:in `block in find' >>> /opt/ruby/ruby-1.9.2-p180/lib/ruby/1.9.1/find.rb:38:in `collect!' >>> /opt/ruby/ruby-1.9.2-p180/lib/ruby/1.9.1/find.rb:38:in `find' >>> /etc/etchserver/lib/etch.rb:173:in `generate' >>> /etc/etchserver/lib/etchserver.rb:348:in `generate' >>> /etc/etchserver/app/controllers/files_controller.rb:24:in `create' >>> /opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/actionpack-2.3.11/lib/action_controller/base.rb:1333:in `perform_action' >>> /opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/actionpack-2.3.11/lib/action_controller/filters.rb:617:in `call_filters' >>> /opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/actionpack-2.3.11/lib/action_controller/filters.rb:610:in `perform_action_with_filters' >>> /opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/actionpack-2.3.11/lib/action_controller/benchmarking.rb:68:in `block in perform_action_with_benchmark' >>> /opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/activesupport-2.3.11/lib/active_support/core_ext/benchmark.rb:17:in `block in ms' >>> /opt/ruby/ruby-1.9.2-p180/lib/ruby/1.9.1/benchmark.rb:309:in `realtime' >>> /opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/activesupport-2.3.11/lib/active_support/core_ext/benchmark.rb:17:in `ms' >>> /opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/actionpack-2.3.11/lib/action_controller/benchmarking.rb:68:in `perform_action_with_benchmark' >>> /opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/actionpack-2.3.11/lib/action_controller/rescue.rb:160:in `perform_action_with_rescue' >>> /opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/actionpack-2.3.11/lib/action_controller/flash.rb:151:in `perform_action_with_flash' >>> /opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/actionpack-2.3.11/lib/action_controller/base.rb:532:in `process' >>> /opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/actionpack-2.3.11/lib/action_controller/filters.rb:606:in `process_with_filters' >>> /opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/actionpack-2.3.11/lib/action_controller/base.rb:391:in `process' >>> /opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/actionpack-2.3.11/lib/action_controller/base.rb:386:in `call' >>> /opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/actionpack-2.3.11/lib/action_controller/routing/route_set.rb:438:in `call' >>> /opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/actionpack-2.3.11/lib/action_controller/dispatcher.rb:87:in `dispatch' >>> /opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/actionpack-2.3.11/lib/action_controller/dispatcher.rb:121:in `_call' >>> /opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/actionpack-2.3.11/lib/action_controller/dispatcher.rb:130:in `block in build_middleware_stack' >>> /opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/activerecord-2.3.11/lib/active_record/query_cache.rb:29:in `call' >>> /opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/activerecord-2.3.11/lib/active_record/query_cache.rb:29:in `block in call' >>> /opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/activerecord-2.3.11/lib/active_record/connection_adapters/abstract/query_cache.rb:34:in `cache' >>> /opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/activerecord-2.3.11/lib/active_record/query_cache.rb:9:in `cache' >>> /opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/activerecord-2.3.11/lib/active_record/query_cache.rb:28:in `call' >>> /opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/activerecord-2.3.11/lib/active_record/connection_adapters/abstract/connection_pool.rb:361:in `call' >>> /opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/actionpack-2.3.11/lib/action_controller/string_coercion.rb:25:in `call' >>> /opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/rack-1.1.0/lib/rack/head.rb:9:in `call' >>> /opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/rack-1.1.0/lib/rack/methodoverride.rb:24:in `call' >>> /opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/actionpack-2.3.11/lib/action_controller/params_parser.rb:15:in `call' >>> /opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/actionpack-2.3.11/lib/action_controller/session/cookie_store.rb:99:in `call' >>> /opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/actionpack-2.3.11/lib/action_controller/failsafe.rb:26:in `call' >>> /opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/rack-1.1.0/lib/rack/lock.rb:11:in `block in call' >>> <internal:prelude>:10:in `synchronize' >>> /opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/rack-1.1.0/lib/rack/lock.rb:11:in `call' >>> /opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/actionpack-2.3.11/lib/action_controller/dispatcher.rb:114:in `block in call' >>> /opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/actionpack-2.3.11/lib/action_controller/reloader.rb:34:in `run' >>> /opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/actionpack-2.3.11/lib/action_controller/dispatcher.rb:108:in `call' >>> /opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/rails-2.3.11/lib/rails/rack/static.rb:31:in `call' >>> /opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/rack-1.1.0/lib/rack/urlmap.rb:47:in `block in call' >>> /opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/rack-1.1.0/lib/rack/urlmap.rb:41:in `each' >>> /opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/rack-1.1.0/lib/rack/urlmap.rb:41:in `call' >>> /opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/rails-2.3.11/lib/rails/rack/log_tailer.rb:17:in `call' >>> /opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/unicorn-3.6.2/lib/unicorn/http_server.rb:545:in `process_client' >>> /opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/unicorn-3.6.2/lib/unicorn/http_server.rb:623:in `block in worker_loop' >>> /opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/unicorn-3.6.2/lib/unicorn/http_server.rb:621:in `each' >>> /opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/unicorn-3.6.2/lib/unicorn/http_server.rb:621:in `worker_loop' >>> /opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/unicorn-3.6.2/lib/unicorn/http_server.rb:509:in `block (2 levels) in spawn_missing_workers' >>> /opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/unicorn-3.6.2/lib/unicorn/http_server.rb:507:in `fork' >>> /opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/unicorn-3.6.2/lib/unicorn/http_server.rb:507:in `block in spawn_missing_workers' >>> /opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/unicorn-3.6.2/lib/unicorn/http_server.rb:503:in `each' >>> /opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/unicorn-3.6.2/lib/unicorn/http_server.rb:503:in `spawn_missing_workers' >>> /opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/unicorn-3.6.2/lib/unicorn/http_server.rb:516:in `maintain_worker_count' >>> /opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/unicorn-3.6.2/lib/unicorn/http_server.rb:166:in `start' >>> /opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/unicorn-3.6.2/lib/unicorn.rb:30:in `run' >>> /opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/unicorn-3.6.2/bin/unicorn_rails:208:in `<top (required)>' >>> /opt/ruby/current/bin/unicorn_rails:19:in `load' >>> /opt/ruby/current/bin/unicorn_rails:19:in `<main>' >>> Completed in 47ms (View: 1, DB: 6) | 500 Internal Server Error [http://jumphost-1p.internal/files] >>> >>> >>> Processing ResultsController#create (for 10.253.91.169 at 2011-05-03 18:40:41) [POST] >>> Parameters: {"fqdn"=>"etch-testhost.internal", "status"=>"1", "message"=>"500 \"Internal Server Error\"/opt/ruby/ruby-1.9.2-p180/lib/ruby/1.9.1/net/http.rb:2303:in `error!'\n/etc/etchclient/etchclient.rb:343:in `block (2 levels) in process_until_done'\n/etc/etchclient/etchclient.rb:312:in `times'\n/etc/etchclient/etchclient.rb:312:in `block in process_until_done'\n/etc/etchclient/etchclient.rb:240:in `catch'\n/etc/etchclient/etchclient.rb:240:in `process_until_done'\n/etc/etchclient/etch:109:in `<main>'", "timestamp"=>"2011-05-03 18:39:51 +0000"} >>> Client Load (0.1ms) SELECT * FROM "clients" WHERE ("clients"."name" = 'etch-testhost.internal') LIMIT 1 >>> Client Load (0.1ms) SELECT "clients".id FROM "clients" WHERE ("clients"."name" = 'etch-testhost.internal' AND "clients".id <> 2) LIMIT 1 >>> Client Update (0.2ms) UPDATE "clients" SET "updated_at" = '2011-05-03 18:40:41' WHERE "id" = 2 >>> Completed in 14ms (View: 0, DB: 0) | 200 OK [http://jumphost-1p.internal/results] >>> ------------------------------------------------------------------------------ >>> WhatsUp Gold - Download Free Network Management Software >>> The most intuitive, comprehensive, and cost-effective network >>> management toolset available today. Delivers lowest initial >>> acquisition cost and overall TCO of any competing solution. >>> http://p.sf.net/sfu/whatsupgold-sd_______________________________________________ >>> etch-users mailing list >>> etc...@li... >>> https://lists.sourceforge.net/lists/listinfo/etch-users >> > > > > > |
|
From: Johnston, N. <Nat...@ca...> - 2011-05-04 21:33:53
|
Jason,
First, thanks for taking a look at my issue. I really appreciate it!
Second, I doublechecked to be sure, and I do indeed have an /etc/etchserver/source tree that is a copy of the etchserver-demo. In this case, Etch is running as root, so permissions issues are not an issue.
[root@jumphost-1p ~]# find /etc/etchserver/source/
/etc/etchserver/source/
/etc/etchserver/source/tmp
/etc/etchserver/source/tmp/etchdemo
/etc/etchserver/source/tmp/etchdemo/directory
/etc/etchserver/source/tmp/etchdemo/directory/config.xml
/etc/etchserver/source/tmp/etchdemo/scriptfile
/etc/etchserver/source/tmp/etchdemo/scriptfile/config.xml
/etc/etchserver/source/tmp/etchdemo/scriptfile/addition
/etc/etchserver/source/tmp/etchdemo/scriptfile/scriptfile.script
/etc/etchserver/source/tmp/etchdemo/scriptfile/main
/etc/etchserver/source/tmp/etchdemo/link
/etc/etchserver/source/tmp/etchdemo/link/config.xml
/etc/etchserver/source/tmp/etchdemo/plainfile
/etc/etchserver/source/tmp/etchdemo/plainfile/config.xml
/etc/etchserver/source/tmp/etchdemo/plainfile/plainfile2
/etc/etchserver/source/tmp/etchdemo/plainfile/plainfile
Also, I wanted to verify with you that I have the right versions of all of the gems. This host is only being used for the etch server at this point, so the only reason for these gems is to support Etch:
[root@jumphost-1p ~]# gem list
*** LOCAL GEMS ***
abstract (1.0.0)
actionmailer (3.0.7, 2.3.11, 2.3.8)
actionpack (3.0.7, 2.3.11, 2.3.8)
activemodel (3.0.7)
activerecord (3.0.7, 2.3.11, 2.3.8)
activeresource (3.0.7, 2.3.11, 2.3.8)
activesupport (3.0.7, 2.3.11, 2.3.8)
arel (2.1.0, 2.0.9)
builder (3.0.0, 2.1.2)
bundler (1.0.12)
columnize (0.3.2)
erubis (2.7.0, 2.6.6)
facter (1.5.8)
i18n (0.5.0)
kgio (2.3.3)
libxml-ruby (2.0.4, 1.1.2)
mail (2.3.0, 2.2.19)
memcache-client (1.8.5)
mime-types (1.16)
minitest (2.1.0, 1.6.0)
polyglot (0.3.1)
rack (1.1.0)
rack-mount (0.7.2, 0.6.14)
rack-test (0.5.7)
rails (3.0.7, 2.3.11, 2.3.8)
railties (3.0.7)
rake (0.8.7)
rdoc (3.5.3, 2.5.8)
searchlogic (2.5.5)
sqlite3 (1.3.3)
sqlite3-ruby (1.3.3)
thor (0.14.6)
treetop (1.4.9)
tzinfo (0.3.27)
unicorn (3.6.2)
will_paginate (2.3.15)
Thanks,
Nate
On May 4, 2011, at 12:33 AM, Jason Heiss wrote:
Looking at line etch.rb:173 it looks like /etc/etchserver/source doesn't exist. That's the directory where configuration for files that you want etch to manage would live. I.e. if you want etch to manage /etc/motd then the configuration for that would live in /etc/etchserver/source/etc/motd/
If you want you can copy etchserver-demo or etchserver-samples from the distribution to /etc/etchserver to get a basic structure populated.
I'll add a check into etch so that in the future this results in a clear error message rather than an exception and backtrace.
Thanks,
Jason
On May 3, 2011, at 12:20 PM, Johnston, Nathaniel wrote:
Etch Meister(s),
I am a new user of Etch, and I am trying to get it working on a couple internal systems as an experiment. Right now I have only a single client pointed at a single server. When I run etch (as "./etch --debug --generate-all --server "http://jumphost-1p.internal:8080<http://jumphost-1p.internal:8080/>") I get a long stack trace (included below), and in the Etch Dashboard the server comes up as "broken". I would appreciate any insight you might have as to what is the issue, or what tack I should use to track down the issue.
For full disclosure, I am a professional sysadmin, and have only dabbled in Ruby.
Thanks,
Nate
This is from the server side's development.log:
[Multiple fact loads precede this point]
Fact Load (0.1ms) SELECT * FROM "facts" WHERE ("facts"."client_id" = 2 AND "facts"."key" = 'uptime') LIMIT 1
Fact Load (0.1ms) SELECT * FROM "facts" WHERE ("facts"."client_id" = 2 AND "facts"."key" = 'interfaces') LIMIT 1
Fact Load (0.1ms) SELECT * FROM "facts" WHERE ("facts"."client_id" = 2 AND "facts"."key" = 'ipaddress_eth0') LIMIT 1
Fact Load (0.1ms) SELECT * FROM "facts" WHERE ("facts"."client_id" = 2 AND "facts"."key" = 'macaddress_eth0') LIMIT 1
Fact Load (0.1ms) SELECT * FROM "facts" WHERE ("facts"."client_id" = 2 AND "facts"."key" = 'netmask_eth0') LIMIT 1
Fact Load (0.1ms) SELECT * FROM "facts" WHERE ("facts"."client_id" = 2 AND "facts"."key" = 'hardwaremodel') LIMIT 1
Fact Load (0.1ms) SELECT * FROM "facts" WHERE ("facts"."client_id" = 2 AND "facts"."key" = 'facterversion') LIMIT 1
Fact Load (0.8ms) SELECT * FROM "facts" WHERE ("facts"."client_id" = 2)
No such file or directory
/opt/ruby/ruby-1.9.2-p180/lib/ruby/1.9.1/find.rb:38:in `block in find'
/opt/ruby/ruby-1.9.2-p180/lib/ruby/1.9.1/find.rb:38:in `collect!'
/opt/ruby/ruby-1.9.2-p180/lib/ruby/1.9.1/find.rb:38:in `find'
/etc/etchserver/lib/etch.rb:173:in `generate'
/etc/etchserver/lib/etchserver.rb:348:in `generate'
/etc/etchserver/app/controllers/files_controller.rb:24:in `create'
/opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/actionpack-2.3.11/lib/action_controller/base.rb:1333:in `perform_action'
/opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/actionpack-2.3.11/lib/action_controller/filters.rb:617:in `call_filters'
/opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/actionpack-2.3.11/lib/action_controller/filters.rb:610:in `perform_action_with_filters'
/opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/actionpack-2.3.11/lib/action_controller/benchmarking.rb:68:in `block in perform_action_with_benchmark'
/opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/activesupport-2.3.11/lib/active_support/core_ext/benchmark.rb:17:in `block in ms'
/opt/ruby/ruby-1.9.2-p180/lib/ruby/1.9.1/benchmark.rb:309:in `realtime'
/opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/activesupport-2.3.11/lib/active_support/core_ext/benchmark.rb:17:in `ms'
/opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/actionpack-2.3.11/lib/action_controller/benchmarking.rb:68:in `perform_action_with_benchmark'
/opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/actionpack-2.3.11/lib/action_controller/rescue.rb:160:in `perform_action_with_rescue'
/opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/actionpack-2.3.11/lib/action_controller/flash.rb:151:in `perform_action_with_flash'
/opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/actionpack-2.3.11/lib/action_controller/base.rb:532:in `process'
/opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/actionpack-2.3.11/lib/action_controller/filters.rb:606:in `process_with_filters'
/opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/actionpack-2.3.11/lib/action_controller/base.rb:391:in `process'
/opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/actionpack-2.3.11/lib/action_controller/base.rb:386:in `call'
/opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/actionpack-2.3.11/lib/action_controller/routing/route_set.rb:438:in `call'
/opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/actionpack-2.3.11/lib/action_controller/dispatcher.rb:87:in `dispatch'
/opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/actionpack-2.3.11/lib/action_controller/dispatcher.rb:121:in `_call'
/opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/actionpack-2.3.11/lib/action_controller/dispatcher.rb:130:in `block in build_middleware_stack'
/opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/activerecord-2.3.11/lib/active_record/query_cache.rb:29:in `call'
/opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/activerecord-2.3.11/lib/active_record/query_cache.rb:29:in `block in call'
/opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/activerecord-2.3.11/lib/active_record/connection_adapters/abstract/query_cache.rb:34:in `cache'
/opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/activerecord-2.3.11/lib/active_record/query_cache.rb:9:in `cache'
/opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/activerecord-2.3.11/lib/active_record/query_cache.rb:28:in `call'
/opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/activerecord-2.3.11/lib/active_record/connection_adapters/abstract/connection_pool.rb:361:in `call'
/opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/actionpack-2.3.11/lib/action_controller/string_coercion.rb:25:in `call'
/opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/rack-1.1.0/lib/rack/head.rb:9:in `call'
/opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/rack-1.1.0/lib/rack/methodoverride.rb:24:in `call'
/opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/actionpack-2.3.11/lib/action_controller/params_parser.rb:15:in `call'
/opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/actionpack-2.3.11/lib/action_controller/session/cookie_store.rb:99:in `call'
/opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/actionpack-2.3.11/lib/action_controller/failsafe.rb:26:in `call'
/opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/rack-1.1.0/lib/rack/lock.rb:11:in `block in call'
<internal:prelude>:10:in `synchronize'
/opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/rack-1.1.0/lib/rack/lock.rb:11:in `call'
/opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/actionpack-2.3.11/lib/action_controller/dispatcher.rb:114:in `block in call'
/opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/actionpack-2.3.11/lib/action_controller/reloader.rb:34:in `run'
/opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/actionpack-2.3.11/lib/action_controller/dispatcher.rb:108:in `call'
/opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/rails-2.3.11/lib/rails/rack/static.rb:31:in `call'
/opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/rack-1.1.0/lib/rack/urlmap.rb:47:in `block in call'
/opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/rack-1.1.0/lib/rack/urlmap.rb:41:in `each'
/opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/rack-1.1.0/lib/rack/urlmap.rb:41:in `call'
/opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/rails-2.3.11/lib/rails/rack/log_tailer.rb:17:in `call'
/opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/unicorn-3.6.2/lib/unicorn/http_server.rb:545:in `process_client'
/opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/unicorn-3.6.2/lib/unicorn/http_server.rb:623:in `block in worker_loop'
/opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/unicorn-3.6.2/lib/unicorn/http_server.rb:621:in `each'
/opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/unicorn-3.6.2/lib/unicorn/http_server.rb:621:in `worker_loop'
/opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/unicorn-3.6.2/lib/unicorn/http_server.rb:509:in `block (2 levels) in spawn_missing_workers'
/opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/unicorn-3.6.2/lib/unicorn/http_server.rb:507:in `fork'
/opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/unicorn-3.6.2/lib/unicorn/http_server.rb:507:in `block in spawn_missing_workers'
/opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/unicorn-3.6.2/lib/unicorn/http_server.rb:503:in `each'
/opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/unicorn-3.6.2/lib/unicorn/http_server.rb:503:in `spawn_missing_workers'
/opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/unicorn-3.6.2/lib/unicorn/http_server.rb:516:in `maintain_worker_count'
/opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/unicorn-3.6.2/lib/unicorn/http_server.rb:166:in `start'
/opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/unicorn-3.6.2/lib/unicorn.rb:30:in `run'
/opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/unicorn-3.6.2/bin/unicorn_rails:208:in `<top (required)>'
/opt/ruby/current/bin/unicorn_rails:19:in `load'
/opt/ruby/current/bin/unicorn_rails:19:in `<main>'
Completed in 47ms (View: 1, DB: 6) | 500 Internal Server Error [http://jumphost-1p.internal/files]
Processing ResultsController#create (for 10.253.91.169 at 2011-05-03 18:40:41) [POST]
Parameters: {"fqdn"=>"etch-testhost.internal", "status"=>"1", "message"=>"500 \"Internal Server Error\"/opt/ruby/ruby-1.9.2-p180/lib/ruby/1.9.1/net/http.rb:2303:in `error!'\n/etc/etchclient/etchclient.rb:343:in `block (2 levels) in process_until_done'\n/etc/etchclient/etchclient.rb:312:in `times'\n/etc/etchclient/etchclient.rb:312:in `block in process_until_done'\n/etc/etchclient/etchclient.rb:240:in `catch'\n/etc/etchclient/etchclient.rb:240:in `process_until_done'\n/etc/etchclient/etch:109:in `<main>'", "timestamp"=>"2011-05-03 18:39:51 +0000"}
Client Load (0.1ms) SELECT * FROM "clients" WHERE ("clients"."name" = 'etch-testhost.internal') LIMIT 1
Client Load (0.1ms) SELECT "clients".id FROM "clients" WHERE ("clients"."name" = 'etch-testhost.internal' AND "clients".id <> 2) LIMIT 1
Client Update (0.2ms) UPDATE "clients" SET "updated_at" = '2011-05-03 18:40:41' WHERE "id" = 2
Completed in 14ms (View: 0, DB: 0) | 200 OK [http://jumphost-1p.internal/results]
------------------------------------------------------------------------------
WhatsUp Gold - Download Free Network Management Software
The most intuitive, comprehensive, and cost-effective network
management toolset available today. Delivers lowest initial
acquisition cost and overall TCO of any competing solution.
http://p.sf.net/sfu/whatsupgold-sd_______________________________________________
etch-users mailing list
etc...@li...<mailto:etc...@li...>
https://lists.sourceforge.net/lists/listinfo/etch-users
|
|
From: Jason H. <jh...@ap...> - 2011-05-04 05:35:47
|
A follow-up note: I noticed that you're running under ruby 1.9. That's the reason you're the first to stumble upon this issue, as Find.find in ruby 1.8 doesn't complain if you ask it to look at a directory that doesn't exist. To be honest I had not yet tested etch under ruby 1.9, but you've just reminded me that I needed to do so. The first pass resulted in 5 errors from the etch test suite. None look terribly fatal for normal operations, so you're probably fine. There are some ugly warnings from some of the gems and libraries that etch uses, I'll hide those in the next release. Jason On May 3, 2011, at 9:33 PM, Jason Heiss wrote: > Looking at line etch.rb:173 it looks like /etc/etchserver/source doesn't exist. That's the directory where configuration for files that you want etch to manage would live. I.e. if you want etch to manage /etc/motd then the configuration for that would live in /etc/etchserver/source/etc/motd/ > > On May 3, 2011, at 12:20 PM, Johnston, Nathaniel wrote: > >> /opt/ruby/ruby-1.9.2-p180/lib/ruby/1.9.1/find.rb:38:in `block in find' |
|
From: Jason H. <jh...@ap...> - 2011-05-04 04:33:39
|
Looking at line etch.rb:173 it looks like /etc/etchserver/source doesn't exist. That's the directory where configuration for files that you want etch to manage would live. I.e. if you want etch to manage /etc/motd then the configuration for that would live in /etc/etchserver/source/etc/motd/
If you want you can copy etchserver-demo or etchserver-samples from the distribution to /etc/etchserver to get a basic structure populated.
I'll add a check into etch so that in the future this results in a clear error message rather than an exception and backtrace.
Thanks,
Jason
On May 3, 2011, at 12:20 PM, Johnston, Nathaniel wrote:
> Etch Meister(s),
>
> I am a new user of Etch, and I am trying to get it working on a couple internal systems as an experiment. Right now I have only a single client pointed at a single server. When I run etch (as "./etch --debug --generate-all --server "http://jumphost-1p.internal:8080") I get a long stack trace (included below), and in the Etch Dashboard the server comes up as "broken". I would appreciate any insight you might have as to what is the issue, or what tack I should use to track down the issue.
>
> For full disclosure, I am a professional sysadmin, and have only dabbled in Ruby.
>
> Thanks,
>
> Nate
>
> This is from the server side's development.log:
>
> [Multiple fact loads precede this point]
> Fact Load (0.1ms) SELECT * FROM "facts" WHERE ("facts"."client_id" = 2 AND "facts"."key" = 'uptime') LIMIT 1
> Fact Load (0.1ms) SELECT * FROM "facts" WHERE ("facts"."client_id" = 2 AND "facts"."key" = 'interfaces') LIMIT 1
> Fact Load (0.1ms) SELECT * FROM "facts" WHERE ("facts"."client_id" = 2 AND "facts"."key" = 'ipaddress_eth0') LIMIT 1
> Fact Load (0.1ms) SELECT * FROM "facts" WHERE ("facts"."client_id" = 2 AND "facts"."key" = 'macaddress_eth0') LIMIT 1
> Fact Load (0.1ms) SELECT * FROM "facts" WHERE ("facts"."client_id" = 2 AND "facts"."key" = 'netmask_eth0') LIMIT 1
> Fact Load (0.1ms) SELECT * FROM "facts" WHERE ("facts"."client_id" = 2 AND "facts"."key" = 'hardwaremodel') LIMIT 1
> Fact Load (0.1ms) SELECT * FROM "facts" WHERE ("facts"."client_id" = 2 AND "facts"."key" = 'facterversion') LIMIT 1
> Fact Load (0.8ms) SELECT * FROM "facts" WHERE ("facts"."client_id" = 2)
> No such file or directory
> /opt/ruby/ruby-1.9.2-p180/lib/ruby/1.9.1/find.rb:38:in `block in find'
> /opt/ruby/ruby-1.9.2-p180/lib/ruby/1.9.1/find.rb:38:in `collect!'
> /opt/ruby/ruby-1.9.2-p180/lib/ruby/1.9.1/find.rb:38:in `find'
> /etc/etchserver/lib/etch.rb:173:in `generate'
> /etc/etchserver/lib/etchserver.rb:348:in `generate'
> /etc/etchserver/app/controllers/files_controller.rb:24:in `create'
> /opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/actionpack-2.3.11/lib/action_controller/base.rb:1333:in `perform_action'
> /opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/actionpack-2.3.11/lib/action_controller/filters.rb:617:in `call_filters'
> /opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/actionpack-2.3.11/lib/action_controller/filters.rb:610:in `perform_action_with_filters'
> /opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/actionpack-2.3.11/lib/action_controller/benchmarking.rb:68:in `block in perform_action_with_benchmark'
> /opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/activesupport-2.3.11/lib/active_support/core_ext/benchmark.rb:17:in `block in ms'
> /opt/ruby/ruby-1.9.2-p180/lib/ruby/1.9.1/benchmark.rb:309:in `realtime'
> /opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/activesupport-2.3.11/lib/active_support/core_ext/benchmark.rb:17:in `ms'
> /opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/actionpack-2.3.11/lib/action_controller/benchmarking.rb:68:in `perform_action_with_benchmark'
> /opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/actionpack-2.3.11/lib/action_controller/rescue.rb:160:in `perform_action_with_rescue'
> /opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/actionpack-2.3.11/lib/action_controller/flash.rb:151:in `perform_action_with_flash'
> /opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/actionpack-2.3.11/lib/action_controller/base.rb:532:in `process'
> /opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/actionpack-2.3.11/lib/action_controller/filters.rb:606:in `process_with_filters'
> /opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/actionpack-2.3.11/lib/action_controller/base.rb:391:in `process'
> /opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/actionpack-2.3.11/lib/action_controller/base.rb:386:in `call'
> /opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/actionpack-2.3.11/lib/action_controller/routing/route_set.rb:438:in `call'
> /opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/actionpack-2.3.11/lib/action_controller/dispatcher.rb:87:in `dispatch'
> /opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/actionpack-2.3.11/lib/action_controller/dispatcher.rb:121:in `_call'
> /opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/actionpack-2.3.11/lib/action_controller/dispatcher.rb:130:in `block in build_middleware_stack'
> /opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/activerecord-2.3.11/lib/active_record/query_cache.rb:29:in `call'
> /opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/activerecord-2.3.11/lib/active_record/query_cache.rb:29:in `block in call'
> /opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/activerecord-2.3.11/lib/active_record/connection_adapters/abstract/query_cache.rb:34:in `cache'
> /opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/activerecord-2.3.11/lib/active_record/query_cache.rb:9:in `cache'
> /opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/activerecord-2.3.11/lib/active_record/query_cache.rb:28:in `call'
> /opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/activerecord-2.3.11/lib/active_record/connection_adapters/abstract/connection_pool.rb:361:in `call'
> /opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/actionpack-2.3.11/lib/action_controller/string_coercion.rb:25:in `call'
> /opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/rack-1.1.0/lib/rack/head.rb:9:in `call'
> /opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/rack-1.1.0/lib/rack/methodoverride.rb:24:in `call'
> /opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/actionpack-2.3.11/lib/action_controller/params_parser.rb:15:in `call'
> /opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/actionpack-2.3.11/lib/action_controller/session/cookie_store.rb:99:in `call'
> /opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/actionpack-2.3.11/lib/action_controller/failsafe.rb:26:in `call'
> /opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/rack-1.1.0/lib/rack/lock.rb:11:in `block in call'
> <internal:prelude>:10:in `synchronize'
> /opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/rack-1.1.0/lib/rack/lock.rb:11:in `call'
> /opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/actionpack-2.3.11/lib/action_controller/dispatcher.rb:114:in `block in call'
> /opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/actionpack-2.3.11/lib/action_controller/reloader.rb:34:in `run'
> /opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/actionpack-2.3.11/lib/action_controller/dispatcher.rb:108:in `call'
> /opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/rails-2.3.11/lib/rails/rack/static.rb:31:in `call'
> /opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/rack-1.1.0/lib/rack/urlmap.rb:47:in `block in call'
> /opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/rack-1.1.0/lib/rack/urlmap.rb:41:in `each'
> /opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/rack-1.1.0/lib/rack/urlmap.rb:41:in `call'
> /opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/rails-2.3.11/lib/rails/rack/log_tailer.rb:17:in `call'
> /opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/unicorn-3.6.2/lib/unicorn/http_server.rb:545:in `process_client'
> /opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/unicorn-3.6.2/lib/unicorn/http_server.rb:623:in `block in worker_loop'
> /opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/unicorn-3.6.2/lib/unicorn/http_server.rb:621:in `each'
> /opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/unicorn-3.6.2/lib/unicorn/http_server.rb:621:in `worker_loop'
> /opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/unicorn-3.6.2/lib/unicorn/http_server.rb:509:in `block (2 levels) in spawn_missing_workers'
> /opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/unicorn-3.6.2/lib/unicorn/http_server.rb:507:in `fork'
> /opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/unicorn-3.6.2/lib/unicorn/http_server.rb:507:in `block in spawn_missing_workers'
> /opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/unicorn-3.6.2/lib/unicorn/http_server.rb:503:in `each'
> /opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/unicorn-3.6.2/lib/unicorn/http_server.rb:503:in `spawn_missing_workers'
> /opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/unicorn-3.6.2/lib/unicorn/http_server.rb:516:in `maintain_worker_count'
> /opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/unicorn-3.6.2/lib/unicorn/http_server.rb:166:in `start'
> /opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/unicorn-3.6.2/lib/unicorn.rb:30:in `run'
> /opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/unicorn-3.6.2/bin/unicorn_rails:208:in `<top (required)>'
> /opt/ruby/current/bin/unicorn_rails:19:in `load'
> /opt/ruby/current/bin/unicorn_rails:19:in `<main>'
> Completed in 47ms (View: 1, DB: 6) | 500 Internal Server Error [http://jumphost-1p.internal/files]
>
>
> Processing ResultsController#create (for 10.253.91.169 at 2011-05-03 18:40:41) [POST]
> Parameters: {"fqdn"=>"etch-testhost.internal", "status"=>"1", "message"=>"500 \"Internal Server Error\"/opt/ruby/ruby-1.9.2-p180/lib/ruby/1.9.1/net/http.rb:2303:in `error!'\n/etc/etchclient/etchclient.rb:343:in `block (2 levels) in process_until_done'\n/etc/etchclient/etchclient.rb:312:in `times'\n/etc/etchclient/etchclient.rb:312:in `block in process_until_done'\n/etc/etchclient/etchclient.rb:240:in `catch'\n/etc/etchclient/etchclient.rb:240:in `process_until_done'\n/etc/etchclient/etch:109:in `<main>'", "timestamp"=>"2011-05-03 18:39:51 +0000"}
> Client Load (0.1ms) SELECT * FROM "clients" WHERE ("clients"."name" = 'etch-testhost.internal') LIMIT 1
> Client Load (0.1ms) SELECT "clients".id FROM "clients" WHERE ("clients"."name" = 'etch-testhost.internal' AND "clients".id <> 2) LIMIT 1
> Client Update (0.2ms) UPDATE "clients" SET "updated_at" = '2011-05-03 18:40:41' WHERE "id" = 2
> Completed in 14ms (View: 0, DB: 0) | 200 OK [http://jumphost-1p.internal/results]
> ------------------------------------------------------------------------------
> WhatsUp Gold - Download Free Network Management Software
> The most intuitive, comprehensive, and cost-effective network
> management toolset available today. Delivers lowest initial
> acquisition cost and overall TCO of any competing solution.
> http://p.sf.net/sfu/whatsupgold-sd_______________________________________________
> etch-users mailing list
> etc...@li...
> https://lists.sourceforge.net/lists/listinfo/etch-users
|
|
From: Johnston, N. <Nat...@ca...> - 2011-05-03 19:21:09
|
Etch Meister(s),
I am a new user of Etch, and I am trying to get it working on a couple internal systems as an experiment. Right now I have only a single client pointed at a single server. When I run etch (as "./etch --debug --generate-all --server "http://jumphost-1p.internal:8080<http://jumphost-1p.internal:8080/>") I get a long stack trace (included below), and in the Etch Dashboard the server comes up as "broken". I would appreciate any insight you might have as to what is the issue, or what tack I should use to track down the issue.
For full disclosure, I am a professional sysadmin, and have only dabbled in Ruby.
Thanks,
Nate
This is from the server side's development.log:
[Multiple fact loads precede this point]
Fact Load (0.1ms) SELECT * FROM "facts" WHERE ("facts"."client_id" = 2 AND "facts"."key" = 'uptime') LIMIT 1
Fact Load (0.1ms) SELECT * FROM "facts" WHERE ("facts"."client_id" = 2 AND "facts"."key" = 'interfaces') LIMIT 1
Fact Load (0.1ms) SELECT * FROM "facts" WHERE ("facts"."client_id" = 2 AND "facts"."key" = 'ipaddress_eth0') LIMIT 1
Fact Load (0.1ms) SELECT * FROM "facts" WHERE ("facts"."client_id" = 2 AND "facts"."key" = 'macaddress_eth0') LIMIT 1
Fact Load (0.1ms) SELECT * FROM "facts" WHERE ("facts"."client_id" = 2 AND "facts"."key" = 'netmask_eth0') LIMIT 1
Fact Load (0.1ms) SELECT * FROM "facts" WHERE ("facts"."client_id" = 2 AND "facts"."key" = 'hardwaremodel') LIMIT 1
Fact Load (0.1ms) SELECT * FROM "facts" WHERE ("facts"."client_id" = 2 AND "facts"."key" = 'facterversion') LIMIT 1
Fact Load (0.8ms) SELECT * FROM "facts" WHERE ("facts"."client_id" = 2)
No such file or directory
/opt/ruby/ruby-1.9.2-p180/lib/ruby/1.9.1/find.rb:38:in `block in find'
/opt/ruby/ruby-1.9.2-p180/lib/ruby/1.9.1/find.rb:38:in `collect!'
/opt/ruby/ruby-1.9.2-p180/lib/ruby/1.9.1/find.rb:38:in `find'
/etc/etchserver/lib/etch.rb:173:in `generate'
/etc/etchserver/lib/etchserver.rb:348:in `generate'
/etc/etchserver/app/controllers/files_controller.rb:24:in `create'
/opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/actionpack-2.3.11/lib/action_controller/base.rb:1333:in `perform_action'
/opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/actionpack-2.3.11/lib/action_controller/filters.rb:617:in `call_filters'
/opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/actionpack-2.3.11/lib/action_controller/filters.rb:610:in `perform_action_with_filters'
/opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/actionpack-2.3.11/lib/action_controller/benchmarking.rb:68:in `block in perform_action_with_benchmark'
/opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/activesupport-2.3.11/lib/active_support/core_ext/benchmark.rb:17:in `block in ms'
/opt/ruby/ruby-1.9.2-p180/lib/ruby/1.9.1/benchmark.rb:309:in `realtime'
/opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/activesupport-2.3.11/lib/active_support/core_ext/benchmark.rb:17:in `ms'
/opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/actionpack-2.3.11/lib/action_controller/benchmarking.rb:68:in `perform_action_with_benchmark'
/opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/actionpack-2.3.11/lib/action_controller/rescue.rb:160:in `perform_action_with_rescue'
/opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/actionpack-2.3.11/lib/action_controller/flash.rb:151:in `perform_action_with_flash'
/opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/actionpack-2.3.11/lib/action_controller/base.rb:532:in `process'
/opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/actionpack-2.3.11/lib/action_controller/filters.rb:606:in `process_with_filters'
/opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/actionpack-2.3.11/lib/action_controller/base.rb:391:in `process'
/opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/actionpack-2.3.11/lib/action_controller/base.rb:386:in `call'
/opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/actionpack-2.3.11/lib/action_controller/routing/route_set.rb:438:in `call'
/opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/actionpack-2.3.11/lib/action_controller/dispatcher.rb:87:in `dispatch'
/opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/actionpack-2.3.11/lib/action_controller/dispatcher.rb:121:in `_call'
/opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/actionpack-2.3.11/lib/action_controller/dispatcher.rb:130:in `block in build_middleware_stack'
/opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/activerecord-2.3.11/lib/active_record/query_cache.rb:29:in `call'
/opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/activerecord-2.3.11/lib/active_record/query_cache.rb:29:in `block in call'
/opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/activerecord-2.3.11/lib/active_record/connection_adapters/abstract/query_cache.rb:34:in `cache'
/opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/activerecord-2.3.11/lib/active_record/query_cache.rb:9:in `cache'
/opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/activerecord-2.3.11/lib/active_record/query_cache.rb:28:in `call'
/opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/activerecord-2.3.11/lib/active_record/connection_adapters/abstract/connection_pool.rb:361:in `call'
/opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/actionpack-2.3.11/lib/action_controller/string_coercion.rb:25:in `call'
/opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/rack-1.1.0/lib/rack/head.rb:9:in `call'
/opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/rack-1.1.0/lib/rack/methodoverride.rb:24:in `call'
/opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/actionpack-2.3.11/lib/action_controller/params_parser.rb:15:in `call'
/opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/actionpack-2.3.11/lib/action_controller/session/cookie_store.rb:99:in `call'
/opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/actionpack-2.3.11/lib/action_controller/failsafe.rb:26:in `call'
/opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/rack-1.1.0/lib/rack/lock.rb:11:in `block in call'
<internal:prelude>:10:in `synchronize'
/opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/rack-1.1.0/lib/rack/lock.rb:11:in `call'
/opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/actionpack-2.3.11/lib/action_controller/dispatcher.rb:114:in `block in call'
/opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/actionpack-2.3.11/lib/action_controller/reloader.rb:34:in `run'
/opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/actionpack-2.3.11/lib/action_controller/dispatcher.rb:108:in `call'
/opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/rails-2.3.11/lib/rails/rack/static.rb:31:in `call'
/opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/rack-1.1.0/lib/rack/urlmap.rb:47:in `block in call'
/opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/rack-1.1.0/lib/rack/urlmap.rb:41:in `each'
/opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/rack-1.1.0/lib/rack/urlmap.rb:41:in `call'
/opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/rails-2.3.11/lib/rails/rack/log_tailer.rb:17:in `call'
/opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/unicorn-3.6.2/lib/unicorn/http_server.rb:545:in `process_client'
/opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/unicorn-3.6.2/lib/unicorn/http_server.rb:623:in `block in worker_loop'
/opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/unicorn-3.6.2/lib/unicorn/http_server.rb:621:in `each'
/opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/unicorn-3.6.2/lib/unicorn/http_server.rb:621:in `worker_loop'
/opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/unicorn-3.6.2/lib/unicorn/http_server.rb:509:in `block (2 levels) in spawn_missing_workers'
/opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/unicorn-3.6.2/lib/unicorn/http_server.rb:507:in `fork'
/opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/unicorn-3.6.2/lib/unicorn/http_server.rb:507:in `block in spawn_missing_workers'
/opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/unicorn-3.6.2/lib/unicorn/http_server.rb:503:in `each'
/opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/unicorn-3.6.2/lib/unicorn/http_server.rb:503:in `spawn_missing_workers'
/opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/unicorn-3.6.2/lib/unicorn/http_server.rb:516:in `maintain_worker_count'
/opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/unicorn-3.6.2/lib/unicorn/http_server.rb:166:in `start'
/opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/unicorn-3.6.2/lib/unicorn.rb:30:in `run'
/opt/ruby/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/unicorn-3.6.2/bin/unicorn_rails:208:in `<top (required)>'
/opt/ruby/current/bin/unicorn_rails:19:in `load'
/opt/ruby/current/bin/unicorn_rails:19:in `<main>'
Completed in 47ms (View: 1, DB: 6) | 500 Internal Server Error [http://jumphost-1p.internal/files]
Processing ResultsController#create (for 10.253.91.169 at 2011-05-03 18:40:41) [POST]
Parameters: {"fqdn"=>"etch-testhost.internal", "status"=>"1", "message"=>"500 \"Internal Server Error\"/opt/ruby/ruby-1.9.2-p180/lib/ruby/1.9.1/net/http.rb:2303:in `error!'\n/etc/etchclient/etchclient.rb:343:in `block (2 levels) in process_until_done'\n/etc/etchclient/etchclient.rb:312:in `times'\n/etc/etchclient/etchclient.rb:312:in `block in process_until_done'\n/etc/etchclient/etchclient.rb:240:in `catch'\n/etc/etchclient/etchclient.rb:240:in `process_until_done'\n/etc/etchclient/etch:109:in `<main>'", "timestamp"=>"2011-05-03 18:39:51 +0000"}
Client Load (0.1ms) SELECT * FROM "clients" WHERE ("clients"."name" = 'etch-testhost.internal') LIMIT 1
Client Load (0.1ms) SELECT "clients".id FROM "clients" WHERE ("clients"."name" = 'etch-testhost.internal' AND "clients".id <> 2) LIMIT 1
Client Update (0.2ms) UPDATE "clients" SET "updated_at" = '2011-05-03 18:40:41' WHERE "id" = 2
Completed in 14ms (View: 0, DB: 0) | 200 OK [http://jumphost-1p.internal/results]
|
|
From: Jason H. <jh...@ap...> - 2011-04-12 07:13:24
|
Significant changes: * Add support for nokogiri as a choice of XML libraries in addition to the existing support for libxml and rexml. * Switch server to rails 2.3.11 (from 2.3.10) We're seeing a lot of ruby segfaults on our etch servers, which I believe are related to the libxml gem. I've added support for the newer nokogiri gem for XML parsing. It is based on the same robust libxml2 native library, but looks to be better written than the libxml-ruby gem. I'll report back on how it holds up to load. For now libxml remains the default with a fallback to rexml (the slow native Ruby XML parser) if libxml is not found. As before you can set the "xmllib" environment variable before starting the etch server to force the usage of a particular library. If nokogiri proves stable I'll make it the default in a future release. The update to rails 2.3.11 is just to keep up with the latest rails security fixes. I'll try to get etch moved to rails 3 in a future release. Other changes: * Update etch_to_trunk so that user can specify where the nVentory server is running (contributed by Darren Dao) * Client interactive mode now defaults to previous selection (contributed by Pat O'Brien) * Add documentation of detailed_results setting in etch.conf to etch man page * Distribution tarball no longer contains development logs and databases * Fix handling of etch configuration scripts that call return. |
|
From: Jason H. <jh...@ap...> - 2011-01-18 00:40:38
|
Add support for a detailed_results setting in the client config file, allowing users to log detailed results to a local file in addition to or instead of sending them to the server. In our environment with a few thousand clients the detailed results are generating more data and logging on our etch servers than we care to throw hardware at. So this will allow us to log those results locally on the clients instead. ticket:9 Add --list-files option to client. And a few other misc. bug fixes. |
|
From: Jason H. <jh...@ap...> - 2010-12-22 20:41:17
|
Client ------ ticket:8 Add support for an /etc/etch.conf config file to the client. This allows users to set the etch server, the directory to use for local configuration (if desired instead of using a server), and the SSH key permanently. These were previously only configurable on the command line. The config file also allows the user to set a PATH that will be in force for any commands etch runs. The PATH was previously hard-coded in the client. Change the worker_processes setting from 20 to 8 in the unicorn.rb config file included with the server. 20 workers was proving too much for our dedicated etch servers with 8 GB of RAM and thus seemed an inappropriate default for general usage. We've changed our servers to 16. Increase the sqlite timeout in the production section of the server's database.yml config file from 5s to 20s. Users reported sqlite timeouts under heavy load at the 5s setting. Since usage is primarily not interactive a higher timeout allows more clients to be served from a given server. Update the example nodetagger and nodegrouper scripts in the etchserver-samples/nventory/ directory to include a number of enhancements. Enhance etch_to_trunk script with additional options including the ability to specify the username and timezone. Set the postinstall/postremove scripts to be executable when building the Solaris packages. Update dependencies for Debian package. These were copied from the tpkg Debian package which is more widely used, and seem appropriate for etch as well. Server ------ NOTE: The server now requires the searchlogic gem and rails 2.3.10 Add searchlogic searching to the controllers in the server that didn't have search functionality. The clients and results controllers still have their homegrown search functionality that will need to be migrated to searchlogic at some point. Update to rails 2.3.10. Apparently 2.3.8 is incompatible with newer versions of the i18n gem and I started running into that incompatibility. That incompatibility was fixed in 2.3.9. Added basic views in the server for the models that didn't have any views. ticket:10 Fix the etch home link in the upper left of the web UI so that it obeys RAILS_RELATIVE_URL_ROOT. |
|
From: Jason H. <jh...@ap...> - 2010-10-06 19:07:55
|
Hmm, that's not come up before. You could figure out which files etch managed at one point in time by inspecting /var/etch/orig or /var/etch/history (history would be a bit simpler). However, getting a list of the files that the server is _currently_ telling the client to manage would be a bit more difficult. In theory, if you sent a properly formed request to the server you could parse the XML response to get a list. However, the way the client does this means that it may get the configuration in a couple of batches. Anyway, you could parse the output from --debug. If you'd like the client to provide a clean list via a command line option you can open a ticket, it shouldn't be too hard for me to add. Jason On Oct 6, 2010, at 9:52 AM, Darren Dao wrote: > Is it possible? > |
|
From: Darren D. <Dar...@eh...> - 2010-10-06 16:52:57
|
Is it possible? |
|
From: Jason H. <jh...@ap...> - 2010-09-14 00:22:40
|
Etch will error out. I thought I'd documented this but it seems I did not, sorry about that.[1] Anyway, you have to give etch consistent instructions of what to do. I.e. after filtering all of the sources have to agree. Typically in a case like what you are describing you would just have a single script (instead of myscript1, myscript2, etc.) and put appropriate logic in the script to handle the combinations of groups as appropriate. I.e.
if @groups.include?('group1')
@contents << 'blah'
elsif @groups.include?('group2')
@contents << 'foo'
end
Jason
[1] It is now documented in https://sourceforge.net/apps/trac/etch/wiki/ConfigurationManual
On Sep 13, 2010, at 3:31 PM, Darren Dao wrote:
> Supposed my node belongs to all three groups (group1, group2, and group3). What would happens if I have the following attribute filtering in my config.xml?
>
> Will myscript1.script be picked? or myscript3.script? or all 3 will get picked? If all 3 get picked, does the resulting content be the combined result from the 3 script? or will it just be the result of the last script that is run, which is myscript3 in this case.
>
> <config>
> <file>
> <warning_file/>
> <!--
> By default files will be owned by root,
> but you can change that. If this user or
> group doesn't exist UID 0 and GID 0 will
> be used as a faillback.
> <owner>demouser</owner>
> <group>demogroup</group>
> -->
> <perms>400</perms>
> <source>
> <script group="group1">myscript1.script</script>
> <script group="group2">myscript2.script</script>
> <script group="group3">myscript3.script</script>
> </source>
> </file>
> </config>
|
