Skip to content

Instantly share code, notes, and snippets.

View walderrama's full-sized avatar

Victor Valderrama walderrama

3 followers · 10 following
View GitHub Profile
@walderrama
walderrama / gist:d3fdd561ea80d3d0aea604c596ca1212
Created September 13, 2021 18:10
### Keybase proof
I hereby claim:
* I am walderrama on github.
* I am walderrama (https://keybase.io/walderrama) on keybase.
* I have a public key ASCMR9X7kg_7VKZn8hNMI1H5_raM9WJ9OWmU9cVMW7D1Kwo
To claim this, I am signing this object:
@walderrama
walderrama / gist:e5b586dcf593353b3c6b
Created February 29, 2016 15:35
here's what happends when pass the jmx options trough command line
vagrant@vagrant-ubuntu-trusty-64:/vagrant$ torquebox run -p 4000 -b 192.168.50.50 --jvm-options="-Djboss.modules.system.pkgs=org.jboss.logmanager -Djava.util.logging.manager=org.jboss.logmanager.LogManager -Djava.rmi.server.hostname=192.168.50.50 -Dcom.sun.management.jmxremote=true -Dcom.sun.management.jmxremote.port=5000 -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false -Xbootclasspath/p:/home/vagrant/.rvm/gems/jruby-1.7.13/gems/torquebox-server-3.1.2-java/jboss/modules/system/layers/base/org/jboss/logmanager/main/jboss-logmanager-1.4.0.Final.jar -Xbootclasspath/p:/home/vagrant/.rvm/gems/jruby-1.7.13/gems/torquebox-server-3.1.2-java/jboss/modules/system/layers/base/org/jboss/log4j/logmanager/main/log4j-jboss-logmanager-1.0.1.Final.jar -Xbootclasspath/p:/home/vagrant/.rvm/gems/jruby-1.7.13/gems/torquebox-server-3.1.2-java/jboss/modules/system/layers/base/org/apache/log4j/main/log4j-1.2.16.jar"
Booting AS7 from configuration /home/vagrant/.rvm/gems/jruby-1.7.19/ge
@walderrama
walderrama / gist:ad2d0a43bb661a7793e1
Created February 29, 2016 15:19
jboss jmx enabled conf
## -*- shell-script -*- ######################################################
## ##
## JBoss Bootstrap Script Configuration ##
## ##
##############################################################################
#
# This file is optional; it may be removed if not needed.
#
@walderrama
walderrama / gist:71360b4e4510c6c18370
Created February 26, 2016 13:40
torquebox error
=========================================================================
13:28:28,616 INFO [org.jboss.modules] (main) JBoss Modules version 1.2.0.CR1
13:28:28,812 INFO [org.jboss.msc] (main) JBoss MSC version 1.0.4.GA
13:28:29,507 INFO [org.torquebox.bootstrap] (ServerService Thread Pool -- 15) Bootstrapping TorqueBox
13:28:29,509 INFO [org.torquebox.bootstrap] (ServerService Thread Pool -- 15) Bootstrapping TorqueBox with a JRuby home of /home/vagrant/.rvm/rubies/jruby-1.7.19
13:28:29,895 INFO [org.torquebox.security.as] (ServerService Thread Pool -- 2) Initializing TorqueBox Auth Subsystem
13:28:29,895 INFO [org.torquebox.services.as] (ServerService Thread Pool -- 11) Initializing TorqueBox Services Subsystem
13:28:29,899 INFO [org.torquebox.stomp.as] (ServerService Thread Pool -- 8) Initializing TorqueBox STOMP Subsystem
13:28:29,903 INFO [org.torquebox.jobs.as] (ServerService Thread Pool -- 7) Initializing TorqueBox Jobs Subsystem
@walderrama
walderrama / gist:4720caf58ab8778b5b78
Created January 27, 2016 17:54
Failed to send results to Stackdriver
[27 Jan 2016 17:53:34] [pool-100-thread-1] 5940904 WARN (com.googlecode.jmxtrans.model.output.StackdriverWriter:328) - Failed to send results to Stackdriver server: responseCode=400 message=Bad Request
[27 Jan 2016 17:53:34] [pool-100-thread-1] 5940905 WARN (com.googlecode.jmxtrans.model.output.StackdriverWriter:343) - Error flushing http connection for one result, continuing
[27 Jan 2016 17:53:34] [pool-100-thread-1] 5940905 DEBUG (com.googlecode.jmxtrans.model.output.StackdriverWriter:344) - Stack trace for the http connection, usually a network timeout
java.io.IOException: Server returned HTTP response code: 400 for URL: https://jmx-gateway.stackdriver.com/v1/custom
@walderrama
walderrama / gist:6fab7e142b311b7446d9
Created December 18, 2014 14:55
first bootstrap with previous client
walderrama-mbp:chef-repo victor$ knife bootstrap --run-list "role[phpapp]" --json-attributes "{\"phpapp\": {\"server_name\": \"intro.hellofutu.re\"}}" --bootstrap-version 11.8 192.168.40.180 -x victor --sudo
Connecting to 192.168.40.180
Failed to authenticate victor - trying password auth
Enter your password:
192.168.40.180 knife sudo password:
192.168.40.180
192.168.40.180 Starting first Chef Client run...
192.168.40.180 Starting Chef Client, version 11.8.2
192.168.40.180 Creating a new client identity for sandbox3 using the validator key.
192.168.40.180 resolving cookbooks for run list: ["apt", "phpapp"]
@walderrama
walderrama / gist:c4fc2a7b9955921ce844
Created December 18, 2014 14:53
output of first bootstrap
walderrama-mbp:chef-repo victor$ knife bootstrap --run-list "role[phpapp]" --json-attributes "{\"phpapp\": {\"server_name\": \"intro.hellofutu.re\"}}" 192.168.40.210 -x victor --sudo
Connecting to 192.168.40.210
Failed to authenticate victor - trying password auth
Enter your password:
192.168.40.210 knife sudo password:
192.168.40.210
192.168.40.210 Installing Chef Client...
192.168.40.210 --2014-12-17 20:30:37-- https://www.opscode.com/chef/install.sh
192.168.40.210 Resolving www.opscode.com (www.opscode.com)... 184.106.28.91
192.168.40.210 Connecting to www.opscode.com (www.opscode.com)|184.106.28.91|:443... connected.