Main

related bits

0

processing priority

4

site type

3 (personal blog or private political site, e.g. Blogspot, Substack, also small blogs on own domains)

review version

11

html import

20 (imported)

Events

first seen date

2025-01-13 23:44:15

expired found date

-

created at

2025-01-13 23:44:15

updated at

2026-01-11 19:36:56

Domain name statistics

length

29

crc

9638

tld

2211

nm parts

0

nm random digits

0

nm rare letters

0

Connections

is subdomain of id

13642151 (wordpress.com)

previous id

0

replaced with id

0

related id

-

dns primary id

0

dns alternative id

0

lifecycle status

0 (unclassified, or currently active)

Subdomains and pages

deleted subdomains

0

page imported products

0

page imported random

0

page imported parking

0

Error counters

count skipped due to recent timeouts on the same server IP

0

count content received but rejected due to 11-799

0

count dns errors

0

count cert errors

0

count timeouts

0

count http 429

0

count http 404

0

count http 403

0

count http 5xx

0

next operation date

-

Server

server bits

server ip

-

Mainpage statistics

mp import status

20

mp rejected date

-

mp saved date

-

mp size orig

113552

mp size raw text

11952

mp inner links count

4

mp inner links status

20 (imported)

Open Graph

title

Roberto Trujillo

description

reflexiones de tecnologia

image

site name

Roberto Trujillo

author

updated

2026-01-07 06:14:28

raw text

Roberto Trujillo – reflexiones de tecnologia Saltar al contenido Roberto Trujillo reflexiones de tecnologia Menú Openshift 3.11 nodo worker NotReady May 19, 2020 ~ robertotrujillo ~ Deja un comentario Despues de casi un año funcionando, uno de los nodos workers del cluster no inicia,  al utilizar el comando oc describe node «nombre», el mensaje mostrado es: «Trying to send a message larger than max» Solución: En mi caso, el cluter creo demasiadas replicas de un pod en particular (aun desconozco la razón) en el nodo afectado, al ejecutar «docker container ls -a», tengo:     Simplemente borrando algunos de estos containers con: Docker rm «containerid»   y luego reiniciando el nodo, todo vuelve a funcionar con normalidad. Machine learning en ElasticSearch: Bueno pero no suficiente. octubre 9, 2019 ~ robertotrujillo ~ Deja un comentario He estado utilizando elasticsearch en elastic cloud durante casi todo este año, estas so...

Text analysis

redirect type

0 (-)

block type

0 (no issues)

detected language

8 (Spanish)

category id

Zastosowania AI (149)

index version

2025123101

spam phrases

0

Text statistics

text nonlatin

0

text cyrillic

0

text characters

9240

text words

1873

text unique words

716

text lines

136

text sentences

48

text paragraphs

31

text words per sentence

39

text matched phrases

4

text matched dictionaries

4

RSS

rss status

32 (unknown)

rss found date

2025-01-13 23:44:17

rss size orig

7157

rss items

4

rss spam phrases

0

rss detected language

8 (Spanish)

inbefore feed id

-

inbefore status

0 (new)

Sitemap

sitemap status

40 (completed successful import of reports.txt file to table in_pages)

sitemap review version

2

sitemap urls count

5

sitemap urls adult

0

sitemap filtered products

0

sitemap filtered videos

0

sitemap found date

2025-01-13 23:44:15

sitemap process date

2025-03-23 23:06:14

sitemap first import date

-

sitemap last import date

2025-07-27 10:09:22