robinbowes.com Report : Visit Site

Technical data of the robinbowes.com

Geo IP provides you such as latitude, longitude and ISP (Internet Service Provider) etc. informations. Our GeoIP service found where is host robinbowes.com. Currently, hosted in United Kingdom and its service provider is Plusnet Plc. .

thefretboard.co.uk 

HTTP Header Analysis

HTTP Header information is a part of HTTP protocol that a user's browser sends to called Apache/2.0.54 (Fedora) containing the details of what the browser wants and will accept back from the web server.

DNS

HtmlToText

-- robinbowes.com if a man speaks in a forest, and his wife's not there, is he still wrong? contribute advanced search site statistics directory calendar links polls contact details pulling information from puppet stored config db, part 2 robin monday, october 05 2009 @ 04:10 pm bst views: 10,589 in my previous post , i started exploring how to pull information from a puppet stored config db to use in capistrano, inspired by joe-mac's post . well, it seems that the query i used was overly complex. here's the simplified version: select h.name from hosts h join resources r on h.id = r.host_id where r.restype = 'class' and r.title = 'site::profile::dnscache::local' order by h.name; having established this, i then modified joe-mac's ruby script to look up based on class rather than facts. here's the modified script: #!/usr/bin/env ruby require 'getoptlong' require 'puppet' require 'rdoc/usage' activerecord::base.establish_connection( :adapter => 'mysql', :database => 'puppet', :host => 'localhost', :password => 'secret', :username => 'puppet' ) class hosts < puppet::rails::host; end opts = getoptlong.new( [ '--class', '-c', getoptlong::required_argument], [ '--help', '-h', getoptlong::no_argument ], [ '--print', '-p', getoptlong::required_argument] ) printtype = "name" opt_hash = hash.new() opts.each do |opt, arg| case opt when '--class' opt_hash['class'] = arg when '--help' rdoc::usage when '--print' printtype = arg end end query = "(resources.restype = \'class\' and resources.title = \'#{opt_hash['class']}\')" puts hosts.find(:all, :include => [ :resources ], :conditions => query ).map { |host| host.send(printtype) } next step: build this into my capistrano configuration as per joe-mac's example. trackbacks (0) comments (0) post a comment pulling information from puppet stored config db robin sunday, october 04 2009 @ 02:13 am bst views: 20,098 i recently enabled stored configs for my puppet installation. my primary aim for doing this was to use the collected infomation to dynamically generate lists of nodes to use with capistrano based on joe-mac's recent blog post. the concept is simple, but very powerful: run a query on the puppet stored config database to return a list of host names matching some criteria. in my case, i just need a list of hosts that have a specific puppet class applied. so, without further ado, here's the sql needed to produce just such a list: select h.name from hosts h join resources r on h.id = r.host_id join resource_tags rt on r.id = rt.resource_id join puppet_tags pt on rt.puppet_tag_id = pt.id where pt.name = 'class' and r.restype = 'class' and r.title = 'site::service::dnscache::local' order by h.name; this example returns a list of nodes that have a local dnscache service. to find all nodes running a mysql service i use the same query, replacing the class with site::service::mysql . i can also modify the query slightly to find all nodes that have apache installed: select h.name from hosts h join resources r on h.id = r.host_id join resource_tags rt on r.id = rt.resource_id join puppet_tags pt on rt.puppet_tag_id = pt.id where pt.name = 'class' and r.restype = 'package' and r.title = 'httpd' order by h.name; however, be aware that this does not actually tell me all nodes that have apache installed; it tells me all nodes that have the httpd package included in their puppet definitions. for example, on my lvs master node, i include the piranha package, which pulls in httpd and php as dependencies. the above query doesn't return the name of my lvs master node. more to follow... trackbacks (0) comments (0) post a comment centos rpmbuild macros robin friday, october 02 2009 @ 04:09 pm bst views: 8,382 when (re-)building rpms on centos, you need one of the buildsys-macros packages to be installed so the correct macros are defined: http://buildsys.fedoraproject.org/buildgroups/rhel5/x86_64 trackbacks (0) comments (0) post a comment finding running processes - use the right tool for the job! robin wednesday, september 23 2009 @ 05:50 pm bst views: 7,392 so, you want a list of sshd processes you have running? chances are, most people would do this: # ps -ef | grep sshd root 3223 1 0 sep18 ? 00:00:00 /usr/sbin/sshd root 9771 3223 0 17:27 ? 00:00:00 sshd: root@pts/2 root 9837 9773 0 17:28 pts/2 00:00:00 grep sshd you might even be clever enough to lose the grep process by doing something like: # ps -ef | grep '[s]shd' root 3223 1 0 sep18 ? 00:00:00 /usr/sbin/sshd root 9771 3223 0 17:27 ? 00:00:00 sshd: root@pts/2 suppose you're only interested in child processes, ie. you want to ignore the /usr/bin/sshd process spawned by init. hmmm, gets a bit tricky... something like this should do it: # ps -ef | grep '[s]shd' | grep @pts root 9771 3223 0 17:27 ? 00:00:00 sshd: root@pts/2 now, let's reduce that to a list of process ids so we can send a signal to them: # ps -ef | grep '[s]shd' | grep @pts | awk '{print $2}' 9771 but, this is all getting a bit long-winded. you're using the wrong tool for the job. enter: pgrep # pgrep -f sshd: 9771 what if you want a full process listing? simple: pass the list of process ids from pgrep to ps: ps -fp $(pgrep -d, -f sshd:) uid pid ppid c stime tty time cmd root 9771 3223 0 17:27 ? 00:00:00 sshd: root@pts/2 for the full process listing it's arguable which is the best approach, but that's sort of the point i'm making. you can use either approach depending on the job in hand. trackbacks (0) comments (0) post a comment adding mibs to net-snmp robin tuesday, september 22 2009 @ 03:56 pm bst views: 35,076 in a previous article i showed where to find snmp mibs for a fortinet fortigate firewall device. here's how to add a new mib to net-snmp so the toolset can use it. first, download the mib files and copy them to /usr/share/snmp/mibs look at the top of the file for a line like: your-mib-name definitions ::= begin " your-mib-name " is the name of the mib. edit /etc/snmp/snmp.conf (or /etc/snmp/snmp.local.conf ) and add the line: mibs + your-mib-name full details on the net-snmp site: http://www.net-snmp.org/wiki/index.php/tut:using_and_loading_mibs trackbacks (0) comments (0) post a comment fortinet snmp mibs robin tuesday, september 22 2009 @ 03:03 pm bst views: 15,817 i'm monitoring a fortinet fortigate 310b firewall device with opennms and needed the appropriate mibs. i found them here: ftp://support.fortinet.com/fortigate/ click your fortios version (v4.00 in my case) then the mibs directory. the full path is: ftp://support.fortinet.com/fortigate/v4.00/mibs/ now all i need to do is get snmpwalk to use them! trackbacks (0) comments (0) post a comment centos - nic bonding and bridging with xen robin monday, september 07 2009 @ 07:34 pm bst views: 8,982 we're in the process of rolling out a redundant switch configuration in the data centre. as a part of this, we're re-configuring all our servers with bonded nics. i ran into a bit of a problem with our xen machine in that i couldn't add a bonded interface to a bridge, which is required for xen networking. it turns out that a patch to the ifcfg-eth script fixes the issue by creating the bonded interface before creating the birdges. the patch is here: http://git.fedorahosted.org/git/?p=initscripts.git;a=commitdiff;h=f9cfaa365ee15b7cb4585f5220702ac5f39c2743 trackbacks (0) comments (0) post a comment installing a custom ca root certificate robin tuesday, september 01 2009 @ 11:24 pm bst views: 7,666 i recently followed this guide to create a custom ca root certificate: http://sial.org/howto/openssl/ca/ one thing that is missing is how to install the certificate on all client machines. the best i could come up with was to append the certificate to the ca bundle supplied with openssl: openssl x509 -in ca-cert.pem -text >> /etc/pki/tls/certs/ca-bundle.crt anyone got a better idea? trackbacks (0) comments (0) post a comment creating an encrypted lvm logical volume robin tuesday, september 01 2009 @ 05:49 pm bst views: 19,924 i wanted to

URL analysis for robinbowes.com

http://www.robinbowes.com/#top
http://www.robinbowes.com/#content-start
http://www.robinbowes.com/article.php/2009100402131050
newsrss.bbc.co.uk

Whois Information

Whois is a protocol that is access to registering information. You can reach when the website was registered, when it will be expire, what is contact details of the site with the following informations. In a nutshell, it includes these informations;

Domain Name: ROBINBOWES.COM
Registry Domain ID: 84767032_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.gandi.net
Registrar URL: http://www.gandi.net
Updated Date: 2017-09-09T20:13:13Z
Creation Date: 2002-03-22T19:07:45Z
Registry Expiry Date: 2022-03-22T18:07:45Z
Registrar: Gandi SAS
Registrar IANA ID: 81
Registrar Abuse Contact Email: [email protected]
Registrar Abuse Contact Phone: +33.170377661
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Name Server: NS1194.DNS.DYN.COM
Name Server: NS2187.DNS.DYN.COM
Name Server: NS3183.DNS.DYN.COM
Name Server: NS4129.DNS.DYN.COM
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2017-09-23T02:48:07Z <<<

For more information on Whois status codes, please visit https://icann.org/epp

NOTICE: The expiration date displayed in this record is the date the
registrar's sponsorship of the domain name registration in the registry is
currently set to expire. This date does not necessarily reflect the expiration
date of the domain name registrant's agreement with the sponsoring
registrar. Users may consult the sponsoring registrar's Whois database to
view the registrar's reported date of expiration for this registration.

TERMS OF USE: You are not authorized to access or query our Whois
database through the use of electronic processes that are high-volume and
automated except as reasonably necessary to register domain names or
modify existing registrations; the Data in VeriSign Global Registry
Services' ("VeriSign") Whois database is provided by VeriSign for
information purposes only, and to assist persons in obtaining information
about or related to a domain name registration record. VeriSign does not
guarantee its accuracy. By submitting a Whois query, you agree to abide
by the following terms of use: You agree that you may use this Data only
for lawful purposes and that under no circumstances will you use this Data
to: (1) allow, enable, or otherwise support the transmission of mass
unsolicited, commercial advertising or solicitations via e-mail, telephone,
or facsimile; or (2) enable high volume, automated, electronic processes
that apply to VeriSign (or its computer systems). The compilation,
repackaging, dissemination or other use of this Data is expressly
prohibited without the prior written consent of VeriSign. You agree not to
use electronic processes that are automated and high-volume to access or
query the Whois database except as reasonably necessary to register
domain names or modify existing registrations. VeriSign reserves the right
to restrict your access to the Whois database in its sole discretion to ensure
operational stability. VeriSign may restrict or terminate your access to the
Whois database for failure to abide by these terms of use. VeriSign
reserves the right to modify these terms at any time.

The Registry database contains ONLY .COM, .NET, .EDU domains and
Registrars.

  REGISTRAR Gandi SAS

SERVERS

  SERVER com.whois-servers.net

  ARGS domain =robinbowes.com

  PORT 43

  TYPE domain

DOMAIN

  NAME robinbowes.com

  CHANGED 2017-09-09

  CREATED 2002-03-22

STATUS
clientTransferProhibited https://icann.org/epp#clientTransferProhibited

NSERVER

  NS1194.DNS.DYN.COM 208.76.58.194

  NS2187.DNS.DYN.COM 208.76.59.187

  NS3183.DNS.DYN.COM 208.76.60.183

  NS4129.DNS.DYN.COM 208.76.61.129

  REGISTERED yes

Mistakes

The following list shows you to spelling mistakes possible of the internet users for the website searched .