Skip to content

Instantly share code, notes, and snippets.

William Herry williamherry

Block or report user

Report or block williamherry

Hide content and notifications from this user.

Learn more about blocking users

Contact Support about this user’s behavior.

Learn more about reporting abuse

Report abuse
View GitHub Profile
@williamherry
williamherry / chef-solr.log
Created Sep 11, 2012
chef-solr can't start
View chef-solr.log
[Tue, 11 Sep 2012 01:02:04 -0700] INFO: Daemonizing..
[Tue, 11 Sep 2012 01:02:04 -0700] INFO: Forked, in 4828. Priveleges: 0 0
[Tue, 11 Sep 2012 01:02:04 -0700] INFO: Starting Solr with java -Xmx256M -Xms256M -Dsolr.data.dir=/var/chef/solr/data -Dsolr.solr.home=/var/chef/solr -jar /var/chef/solr-jetty/start.jar
Error occurred during initialization of VM
java/lang/ClassNotFoundException: error in opening JAR file /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/jre/lib/rt.jar
View java-run-log
[root@localhost lib]# java
Error occurred during initialization of VM
java/lang/ClassNotFoundException: error in opening JAR file /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/jre/lib/rt.jar
@williamherry
williamherry / chef-server-log-about-solr
Created Sep 11, 2012
chef server's log about solr
View chef-server-log-about-solr
merb : chef-server (api) : worker (port 4000) ~ Net::HTTPFatalError: 500 "Severe_errors_in_solr_configuration__Check_your_log_files_for_more_detailed_information_on_what_may_be_wrong__If_you_want_solr_to_continue_after_configuration_errors_change____abortOnConfigurationErrorfalseabortOnConfigurationError__in_null___javalangRuntimeException_javalangExceptionInInitializerError__at_orgapachesolrcoreSolrCoregetSearcherSolrCorejava1068__at_orgapachesolrcoreSolrCoreinitSolrCorejava579__at_orgapachesolrcoreCoreContainer$InitializerinitializeCoreContainerjava137__at_orgapachesolrservletSolrDispatchFilterinitSolrDispatchFilterjava83__at_orgmortbayjettyservletFilterHolderdoStartFilterHolderjava99__at_orgmortbaycomponentAbstractLifeCyclestartAbstractLifeCyclejava40__at_orgmortbayjettyservletServletHandlerinitializeServletHandlerjava594__at_orgmortbayjettyservletContextstartContextContextjava139__at_orgmortbayjettywebappWebAppContextstartContextWebAppContextjava1218__at_orgmortbayjettyhandlerContextHandlerdoStartContextH
@williamherry
williamherry / chef-solr.rb
Created Sep 12, 2012
chef-solr can't start
View chef-solr.rb
[Tue, 11 Sep 2012 18:49:31 -0700] INFO: Starting Solr with java -Xmx256M -Xms256M -Dsolr.data.dir=/var/chef/solr/data -Dsolr.solr.home=/var/chef/solr -jar /var/chef/solr-jetty/start.jar
2012-09-11 18:49:32.364::INFO: Logging to STDERR via org.mortbay.log.StdErrLog
2012-09-11 18:49:32.858::INFO: jetty-6.1.3
2012-09-11 18:49:33.363::WARN: Could not generate SecureRandom for session-id randomness
java.security.NoSuchAlgorithmException: SHA1PRNG SecureRandom not available
at sun.security.jca.GetInstance.getInstance(GetInstance.java:159)
at java.security.SecureRandom.getInstance(SecureRandom.java:271)
at org.mortbay.jetty.servlet.HashSessionIdManager.doStart(HashSessionIdManager.java:118)
at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:40)
at org.mortbay.jetty.servlet.AbstractSessionManager.doStart(AbstractSessionManager.java:170)
View chef-client.log
[2012-09-20T05:03:43-07:00] INFO: Processing monitoring_metric[glance-registry-proc] action measure (glance::registry line 85)
[2012-09-20T05:03:43-07:00] INFO: Processing execute[glance-manage db_sync] action nothing (glance::registry line 93)
[2012-09-20T05:03:43-07:00] INFO: Processing execute[glance-manage version_control] action nothing (glance::registry line 101)
[2012-09-20T05:03:48-07:00] INFO: Processing file[/var/lib/glance/glance.sqlite] action delete (glance::registry line 108)
[2012-09-20T05:03:48-07:00] INFO: Processing keystone_register[Register Service Tenant] action create_tenant (glance::registry line 113)
================================================================================
Error executing action `create_tenant` on resource 'keystone_register[Register Service Tenant]'
================================================================================
View guestmount.log
===== Test starts here =====
LIBGUESTFS_DEBUG=1
TMPDIR=(not set)
libguestfs: new guestfs handle 0xaee700
library version: 1.16.19rhel=6,release=1.el6
guestfs_get_append: (null)
guestfs_get_attach_method: appliance
guestfs_get_autosync: 1
guestfs_get_direct: 0
guestfs_get_memsize: 500
View install-ruby-debug-fail.log
william@desktop:~$ gem install ruby-debug
WARNING: Error fetching data: SocketError: getaddrinfo: Name or service not known (http://rubygems.org/latest_specs.4.8.gz)
WARNING: Error fetching data: SocketError: getaddrinfo: Name or service not known (http://rubygems.org/specs.4.8.gz)
Building native extensions. This could take a while...
ERROR: Error installing ruby-debug:
ERROR: Failed to build gem native extension.
/home/william/.rvm/rubies/ruby-1.9.3-p194/bin/ruby extconf.rb
Can't handle 1.9.x yet
*** extconf.rb failed ***
View git-clone-fail.log
Initialized empty Git repository in /root/notes/.git/
(gnome-ssh-askpass:4841): Gtk-WARNING **: cannot open display:
@williamherry
williamherry / bridge.log
Created Oct 8, 2012
interface don't need to up when use bridge
View bridge.log
williamherry | odd things, interface(em2) not up, but bridge on it work fine, can some one know the reason, what's interface 'UP' means? │ aaket504
tje2 | williamherry .. I don't believe the interface has to be "up" to *bridge* (read: NOT route), but to route packets (such as via MASQ/NAT, etc) the interface │ AAYUSH
| would have to be "UP". │ abbaZaba
melacon | Mohsen_Hassani:Oh ok. What operating system are you running on your PC? │ abchirk_
tje2 | williamherry .. Familiar at all w/ Cisco devices and the UP/UP vs. DOWN/DOWN states of those ifaces? │ aboudreault
Mohsen_Hassani | melacon, The same as my Laptop, Debian Sid.
View vagrant
/home/william/.rvm/rubies/ruby-1.9.3-p286/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot load such file -- log4r (LoadError)
from /home/william/.rvm/rubies/ruby-1.9.3-p286/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
from /usr/bin/vagrant:2:in `<main>'
You can’t perform that action at this time.