Tag Archives: exported

error parsing HTTP 413 response body: invalid character ‘<' looking for beginning of value:

title: “error parsing HTTP 413 response body: invalid character ‘<‘ looking for beginning of value:”
date: 2018-11-21T12:51:41
slug: error-parsing-http-413-response-body-invalid-character

Add “nginx.ingress.kubernetes.io/proxy-body-size: 50m” to values.yaml

ingress:
 enabled: true
 path: /
 # Used to create an Ingress record.
 hosts:
 - registry.k8s
 annotations:
 kubernetes.io/ingress.class: nginx
 nginx.ingress.kubernetes.io/proxy-body-size: 100m
 # kubernetes.io/tls-acme: "true"
 tls:

Modify Setting from an index

title: “Modify Setting from an index”
date: 2018-11-12T09:50:57
slug: modify-setting-from-an-index

PUT filebeat-2018.11.02/\_settings
{
 "index": {
 "routing": {
 "allocation": {
 "include": {
 "\_name": ""
 },
 "exclude": {
 "\_name": ""
 },
 "require": {
 "\_name": ""
 }
 }
 }
 }
}

Move a shard to another node

title: “Move a shard to another node”
date: 2018-11-12T09:29:35
slug: move-a-shard-to-another-node

curl -X POST "localhost:9200/\_cluster/reroute" -H 'Content-Type: application/json' -d'
{
 "commands" : [
 {
 "move" : {
 "index" : "filebeat-2018.11.03", "shard" : 0,
 "from\_node" : "elasticsearch01.mgm.muc01.fti.int", "to\_node" : "elasticsearch02.mgm.muc01.fti.int"
 }
 },
 {
 "allocate\_replica" : {
 "index" : "filebeat-2018.11.03", "shard" : 1,
 "node" : "elasticsearch03.mgm.muc01.fti.int"
 }
 }
 ]
}
'

dvbsnoop

title: “dvbsnoop”
date: 2018-11-07T08:37:17
slug: dvbsnoop

Pidscan

dvbsnoop -s pidscan -pd 1

Get SID and map PID from current transponder:

dvbsnoop -n 10 -nph 0x0000

Events auslesen:

dvbsnoop -n 1200 -nph 0x0012

dvbsnoop -n 1200 -nph 0x0012 | grep event\_name:

docker with gui

title: “docker with gui”
date: 2018-10-29T09:59:48
slug: docker-with-gui

docker run -ti --rm -e DISPLAY -v /tmp/.X11-unix:/tmp/.X11-unix -v $HOME/.Xauthority:/root/.Xauthority --net=host debian

kubelet config

title: “kubelet config”
date: 2018-10-21T16:26:21
slug: kubelet-config

Environment="KUBELET_KUBECONFIG_ARGS=--bootstrap-kubeconfig=/etc/kubernetes/bootstrap-kubelet.conf --kubeconfig=/etc/kubernetes/kubelet.conf --eviction-hard=memory.available<500Mi,nodefs.available<1Gi,imagefs.available<1Gi"

LVM Verschlüsselte Partition kopieren

title: “LVM Verschlüsselte Partition kopieren”
date: 2018-10-15T09:07:14
slug: lvm-verschlusselte-partition-kopieren

Verschlüsselte Partition öffnen und neue Partition anlegen

sudo cryptsetup luksOpen /dev/sdc5 crypt
sudo vgcreate crypt-lvm /dev/mapper/crypt
sudo lvcreate -l100%FREE -nroot crypt-lvm

mount: unknown filesystem type LVM2_member

9 December, 2016

So I’m planning on making a series, “mount: unknown file-system type $TYPE”. I already have how to mount a ntfs partition, also how to mount a nfs on proxmox, now to be continued by another fun file-system. I was going through old disks, so I came across one that had LVM2_member.

  • root@svennd:~# mount /dev/sdd2 /mnt/disk

  • mount: unknown filesystem type ‘LVM2_member’

The fdisk -l already told me its a LVM :

  • root@svennd:~# fdisk -l /dev/sdd

  • Disk /dev/sdd: 233.8 GiB, 251000193024 bytes, 490234752 sectors

  • Units: sectors of 1 * 512 = 512 bytes

  • Sector size (logical/physical): 512 bytes / 512 bytes

  • I/O size (minimum/optimal): 512 bytes / 512 bytes

  • Disklabel type: dos

  • Disk identifier: 0x0009345d

  • Device Boot Start End Sectors Size Id Type

  • /dev/sdd1 * 63 208844 208782 102M 83 Linux

  • /dev/sdd2 208845 488247479 488038635 232.7G 8e Linux LVM

*(/dev/sdi1 is /boot partition, /dev/sdi2 is where the /home data resides)
*

Seems lvm2 tools also provide a way to check if its lvm or not, using lvmdiskscan(/dev/sdd2 here)

  • root@svennd:~# lvmdiskscan

  • /dev/sdb1 [ 1.82 TiB]

  • /dev/sdc2 [ 149.04 GiB]

  • /dev/sdd1 [ 101.94 MiB]

  • /dev/sdd2 [ 232.71 GiB] LVM physical volume

  • 0 disks

  • 4 partitions

  • 0 LVM physical volume whole disks

  • 1 LVM physical volume

Fine, now lets scan what lv’s are to be found using lvscan

  • root@svennd:~# lvscan

  • inactive ‘/dev/VolGroup00/LogVol00’ [230.75 GiB] inherit

  • inactive ‘/dev/VolGroup00/LogVol01’ [1.94 GiB] inherit

Since this is a old disk in an enclosure, its not activated on system boot. So we need to “activate” this lvm volume.

  • root@svennd:~# vgchange -ay

  • 2 logical volume(s) in volume group “VolGroup00” now active

and bam, ready to mount :

  • root@svennd:~# lvscan

  • ACTIVE ‘/dev/VolGroup00/LogVol00’ [230.75 GiB] inherit

  • ACTIVE ‘/dev/VolGroup00/LogVol01’ [1.94 GiB] inherit

now to mount :

  • mount /dev/VolGroup00/LogVol00 /mnt/disk

succes !

joda-time

title: “joda-time”
date: 2018-10-09T09:34:51
slug: joda-time

The pattern letters are:

Symbol Meaning Presentation Examples
------ ------- ------------ -------
G era text AD
C century of era (>=0) number 20
Y year of era (>=0) year 1996
x weekyear year 1996
w week of weekyear number 27
e day of week number 2
E day of week text Tuesday; Tue
y year year 1996
D day of year number 189
M month of year month July; Jul; 07
d day of month number 10
a halfday of day text PM
K hour of halfday (0~11) number 0
h clockhour of halfday (1~12) number 12
H hour of day (0~23) number 0
k clockhour of day (1~24) number 24
m minute of hour number 30
s second of minute number 55
S fraction of second number 978
z time zone text Pacific Standard Time; PST
Z time zone offset/id zone -0800; -08:00; America/Los\_Angeles
' escape for text delimiter
'' single quote literal '

The count of pattern letters determine the format.