tag:blogger.com,1999:blog-40364987955806146912024-03-15T22:10:21.406-03:00De tudo mais um poucolordtuxhttp://www.blogger.com/profile/16697900975244199498noreply@blogger.comBlogger197125tag:blogger.com,1999:blog-4036498795580614691.post-75070424239181561102024-01-24T12:30:00.003-03:002024-01-24T12:30:32.652-03:00Windows 11 não conecta na rede 5G do synology router. Introdução:Navegar pelas águas turbulentas da tecnologia Wi-Fi pode ser um desafio. Recentemente, encontrei um problema intrigante que muitos usuários de Wi-Fi podem enfrentar, especialmente ao lidar com as frequências mais recentes e rápidas, como a 5GHz. Neste post, vou compartilhar minha experiência pessoal de como eu resolvi um problema de conexão persistente com a rede Wi-Fi 5GHz no meu lordtuxhttp://www.blogger.com/profile/16697900975244199498noreply@blogger.com0tag:blogger.com,1999:blog-4036498795580614691.post-14866800380136992262023-12-19T15:20:00.004-03:002023-12-19T15:20:41.723-03:00error: exec plugin: invalid apiVersion "client.authentication.k8s.io/v1alpha1"Got this error after installing a EKS cluster on AWS. I already had the aws cli installed using apt on ubuntu 22. After some search, the solution that solved was installing manually the aws cli.
curl "https://awscli.amazonaws.com/awscli-exe-linux-x86_64.zip" -o "awscliv2.zip"unzip awscliv2.zipsudo ./aws/installlordtuxhttp://www.blogger.com/profile/16697900975244199498noreply@blogger.com0tag:blogger.com,1999:blog-4036498795580614691.post-85226330677396925202023-12-12T10:43:00.001-03:002023-12-12T10:43:15.551-03:00Kubernetes - apiserver advertise address<!--
google_ad_client = "ca-pub-3021803715878426";
/* lordpinguimPost */
google_ad_slot = "9468077813";
google_ad_width = 300;
google_ad_height = 250;
//-->
On vagrant I built a kubernetes cluster with ansible and noticed that the kubeadm init was not using the private interface created on vagrant. So to avoid that, ti changed the command with the parameter --apiserver-advertise-address to use lordtuxhttp://www.blogger.com/profile/16697900975244199498noreply@blogger.com0tag:blogger.com,1999:blog-4036498795580614691.post-14129056459315061252023-12-12T10:02:00.000-03:002023-12-12T10:02:00.867-03:00Kubernetes - memcache.go:265] couldn't get current server API group listFacing the error below on Ubuntu 22.04 on vagrant. Error showing after halting and powering up the vms again. Checking the journal logs and tested was just a matter to disable swap on ubuntu.
root@master:/etc/kubernetes# kubectl get podsE1212 12:55:53.292062 1865 memcache.go:265] couldn't get current server API group list: Get "https://192.168.122.200:6443/api?timeout=32s": dial tcp lordtuxhttp://www.blogger.com/profile/16697900975244199498noreply@blogger.com0tag:blogger.com,1999:blog-4036498795580614691.post-13075789599747661302023-08-05T14:09:00.005-03:002023-08-05T14:09:59.423-03:00GPG error: https://packages.cloud.google.com/apt kubernetes-xenial InRelease: The following signatures couldn't be verified because the public key is not availableTrying to install Kubernetes on Ubuntu 22.04 and I have the error below:ubuntu@test-vm-1:/etc/apt/sources.list.d$ sudo apt updateHit:1 https://download.docker.com/linux/ubuntu jammy InReleaseHit:3 http://archive.ubuntu.com/ubuntu jammy InRelease Hit:4 http://security.ubuntu.com/ubuntu jammy-security InReleaseHit:5 http://lordtuxhttp://www.blogger.com/profile/16697900975244199498noreply@blogger.com0tag:blogger.com,1999:blog-4036498795580614691.post-15123243736923050282023-07-30T19:15:00.002-03:002023-07-30T19:16:04.500-03:00Proxmox -> TrueNAS Scale - Your CPU does not support KVM extensions - como resolverBom, tive o erro do titulo, estou testando o TrueNAS Scale no proxmox no meu homelab.
Fazendo a verificação direto no shell do node do proxmox, a extensão svm de virtualização da cpu AMD que estou usando estava ativa, então não era necessário ativar nada na BIOS.Foi então que pesquisando melhor encontrei esse excelente tutorial:https://ostechnix.com/enable-nested-virtualization-in-proxmox/Tem lordtuxhttp://www.blogger.com/profile/16697900975244199498noreply@blogger.com0tag:blogger.com,1999:blog-4036498795580614691.post-54582707446899672242023-07-30T10:03:00.004-03:002023-07-30T22:07:56.727-03:00Pfsense - qemu agent on proxmoxOk, will just leave this here.
Was trying to get qemu agent running on pfsense 2.7.Just follow the commands on the script on github:https://github.com/Weehooey/pfSense-scripts/blob/main/install-qemu-guest-agent.shAnd here the discussion about the issue:https://forum.netgate.com/topic/162083/pfsense-vm-on-proxmox-qemu-agent-installation/12EDIT: Very important detail.Perform the settings as on the lordtuxhttp://www.blogger.com/profile/16697900975244199498noreply@blogger.com0tag:blogger.com,1999:blog-4036498795580614691.post-33465876475821203602023-07-19T00:11:00.001-03:002023-07-19T00:11:16.689-03:00Philco 4K 288PL6 Faixas escurasBom, chegou o dia, meu monitor 4K que comprei um tempo atrás da Philco está com faixas escuras.
Acabei comprando um LG 32UL750-W.Uma pena que estamos bem carentes de opção. Ia tentar pegar um MSI G281UV mas além do Display Port ser 1.2 e não 1.4 como no LG não tem como regular a altura e não tem alto falante. No Philco o alto falante quebra um galho, posso apenas redirecionar o lordtuxhttp://www.blogger.com/profile/16697900975244199498noreply@blogger.com0tag:blogger.com,1999:blog-4036498795580614691.post-12630956116299717782023-04-27T19:52:00.001-03:002023-04-27T19:52:18.073-03:00React slow on wsl on windowsFound a reason here why is almost impossible deal with a react app on wsl.
My repo is located in a windows folder, everything is slow, even using npx. If you need things fast, move your folder for inside a native folder on the wsl, a linux filesystem. If I try npx create-react-app app In a windows folder, it takes ages to complete and npm start after that is very, very lordtuxhttp://www.blogger.com/profile/16697900975244199498noreply@blogger.com0tag:blogger.com,1999:blog-4036498795580614691.post-8242318355855748472022-03-28T10:53:00.002-03:002022-03-28T10:53:27.124-03:00Fast Note: SSH and too many connectionsIf you trying to login in a server using ssh with user and password and is crazy with messages about too many connections.
Check the .ssh folder if yu have many id_rsa key files, ssh when connect try to use each file that it found on the folder.I had this issue here, after remove the file, connection went fine.lordtuxhttp://www.blogger.com/profile/16697900975244199498noreply@blogger.com0tag:blogger.com,1999:blog-4036498795580614691.post-49201276883170670712020-11-12T16:33:00.005-03:002020-11-12T16:33:52.857-03:00Increase disk size for Pfsense on VmwareThis was done on the Pfsense 2.4.5.Check disk size:[2.4.5-RELEASE][root@server1]/root: gpart show=> 63 104857537 da0 MBR (50G) 63 1 - free - (512B) &lordtuxhttp://www.blogger.com/profile/16697900975244199498noreply@blogger.com0tag:blogger.com,1999:blog-4036498795580614691.post-7138244340077502362020-11-12T16:14:00.002-03:002020-11-12T16:14:13.547-03:00Change IP address of Frames attached on HMCI have a situation where:Frames attached on HMC using the dhcp range 192.128But due network requirements it was necessary change the range.To avoid any problem, I opened a ticket with IBM Support and they give me the following solution:Is not need power off hte lpars on the frame.Is not need power off the frames.Not need to ask a onsite support to remove frames from power and power on again.Just lordtuxhttp://www.blogger.com/profile/16697900975244199498noreply@blogger.com0tag:blogger.com,1999:blog-4036498795580614691.post-12039109478951302632020-09-06T13:32:00.003-03:002020-09-06T13:32:30.268-03:00Syncronize GitHub repository with AWX/Ansible Tower To configure a project on AWX/Ansible Tower to sync with a github repo you need have:token that permit you access the repoFirst lets see the credential.You just need create one:Select Source Control as type.use the username git and on password you put your github token.Just click save. Now create a project.As showed below on the image:Past the https link of you repo, select the credential lordtuxhttp://www.blogger.com/profile/16697900975244199498noreply@blogger.com0tag:blogger.com,1999:blog-4036498795580614691.post-37676505374075444712020-08-18T15:24:00.010-03:002020-08-18T15:25:58.217-03:00Test NIM ports on AIX to see if are opened trhought firewallI faced a situation where I needed test if I was able to reach a NIM server ports for the NIM service, problem is that is not so easy test all the ports, the hard way for example if you need test if would be possible resotre a machine is start the mksysb restore on the NIM and on the client, boot the server on the SMS services and see if will start normally hte installation.As per the lordtuxhttp://www.blogger.com/profile/16697900975244199498noreply@blogger.com0tag:blogger.com,1999:blog-4036498795580614691.post-21028265300863496092020-08-12T23:57:00.000-03:002020-08-12T23:57:08.430-03:00Redhat 8.2 - pam tunning using authselectSome notes about tunning pam on RedHat 8.2# Some tunning options got wrong, so I used the command below to restore the default configruation to be able to start again:[root@server1 pam.d]# authselect select sssd --forceProfile "sssd" was selected.The following nsswitch maps are overwritten by the profile:- passwd- group- netgroup- automount- servicesMake sure that SSSD service is configured and lordtuxhttp://www.blogger.com/profile/16697900975244199498noreply@blogger.com0tag:blogger.com,1999:blog-4036498795580614691.post-57461997494324407502020-08-12T23:35:00.002-03:002020-08-12T23:35:22.237-03:00Kernel Panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)Got the error, after update on Ubuntu 18.04:Kernel Panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)To solve reboot the server and on the grub menu choose advanced options to choos the old kernel.Get the Linux kernel exaclty version from grub running:grep -A100 submenu /boot/grub/grub.cfg |grep menuentryGot the entry:menuentry 'Ubuntu, with Linux 4.15.0-112-generic' -lordtuxhttp://www.blogger.com/profile/16697900975244199498noreply@blogger.com0tag:blogger.com,1999:blog-4036498795580614691.post-49959002260603250142020-07-29T18:33:00.000-03:002020-07-29T18:33:00.744-03:00ValueError: unsupported hash type shaXXX error when try to run yum to install package on AIXWhen try to use yum on AIX you may face the following error:<!--
google_ad_client = "ca-pub-3021803715878426";
/* lordpinguimPost */
google_ad_slot = "9468077813";
google_ad_width = 300;
google_ad_height = 250;
//-->
<!--
google_ad_client = "ca-pub-3021803715878426";
/* lordpinguimPost */
google_ad_slot = "9468077813";
google_ad_width = 300;
google_ad_height = 250;
//-->
<!--
google_ad_client = "lordtuxhttp://www.blogger.com/profile/16697900975244199498noreply@blogger.com0tag:blogger.com,1999:blog-4036498795580614691.post-38580232635394681002020-07-29T18:29:00.001-03:002020-07-29T18:33:18.850-03:00OSError: [Errno 2] A file or directory in the path name does not exist.: '//var/lib/rpm/Packages'When try to use yum on AIX you may face the following error:<!--
google_ad_client = "ca-pub-3021803715878426";
/* lordpinguimPost */
google_ad_slot = "9468077813";
google_ad_width = 300;
google_ad_height = 250;
//-->
<!--
google_ad_client = "ca-pub-3021803715878426";
/* lordpinguimPost */
google_ad_slot = "9468077813";
google_ad_width = 300;
google_ad_height = 250;
//-->
To fix, just create the lordtuxhttp://www.blogger.com/profile/16697900975244199498noreply@blogger.com0tag:blogger.com,1999:blog-4036498795580614691.post-5130928178856242502020-07-29T18:27:00.000-03:002020-07-29T18:27:24.086-03:00Please wait...error: line 10: Dependency tokens must begin with alpha-numericOn AIX if you run the command updtvpkg to update the rpm database you can have a error like:Please wait...error: line 10: Dependency tokens must begin with alpha-numeric, '_' or '/': Provides: .nfs0BF6I dont have much time to digg more deeper on this problem but from what I found is happens because the updtvpkg try to calculate the library dependency and happens to find the file above .nfs0BF6 inlordtuxhttp://www.blogger.com/profile/16697900975244199498noreply@blogger.com0tag:blogger.com,1999:blog-4036498795580614691.post-53969085236968587342020-07-28T17:34:00.002-03:002020-07-28T17:34:44.181-03:00How to use viosecure to tunning viosviosecure command can be a problem if you apply the high level of hardening on a system.If you wish you can apply only a set of values on your environment.First thing that you need to do is get the file /etc/security/aixpert/core/viosecureall.xmlCheck the xml file and you can see that on the file you will have all the set of harderning rules for high, medium and low.If you decide to apply the lordtuxhttp://www.blogger.com/profile/16697900975244199498noreply@blogger.com1tag:blogger.com,1999:blog-4036498795580614691.post-40583574484904719702020-07-23T16:12:00.001-03:002020-07-23T16:12:25.988-03:00DB2 and disk block size of 4096 on AIXBe careful if you are planning to migrate a db2 system from one server to another with different disks on AIX.DB2 v10 only support block disk sizes of 512, not possible to change.Only DB2 v11.5 support, so you either will need disks with blocks of 512 or you will need upgrade to this new version.On AIX if you have a RAID system with 4K disk it will create a final disk with 4K block size, is notlordtuxhttp://www.blogger.com/profile/16697900975244199498noreply@blogger.com0tag:blogger.com,1999:blog-4036498795580614691.post-76350890140106213382020-07-22T10:14:00.001-03:002020-07-22T10:14:47.622-03:00mount: 1831-011 access denied for - NIM IP and Foldermount: 1831-011 access denied for xx.xx.xx.xx:/nim/mksybmount: 1831-008 giving up on:XX.XX.XX.XX:/nim/folderThe file access permissions do not allow the specified action.<!--
google_ad_client = "ca-pub-3021803715878426";
/* lordpinguimPost */
google_ad_slot = "9468077813";
google_ad_width = 300;
google_ad_height = 250;
//-->
If you get the error above on AIX, try to use the server name to mount lordtuxhttp://www.blogger.com/profile/16697900975244199498noreply@blogger.com0tag:blogger.com,1999:blog-4036498795580614691.post-58794008330400978212020-07-15T12:12:00.000-03:002020-07-15T12:12:16.339-03:00How to install YUM and other rpm packages on VIOs and AIX manually
[Download rpm.rte]
Download the rpm.rte from ibm site and update it.
https://ftp.software.ibm.com/aix/freeSoftware/aixtoolbox/INSTALLP/ppc/rpm.rte.4.9.1.3
installp -acgXYd rpm.rte
or use smitty update_all
[Download the yum_bundle.tar]
This file have all the necessary packages to install yum in a AIX
system.
NOTE: is very import to update the rpm.rte first, if you not update it
first lordtuxhttp://www.blogger.com/profile/16697900975244199498noreply@blogger.com0tag:blogger.com,1999:blog-4036498795580614691.post-13090075554951835932020-07-10T12:15:00.000-03:002020-07-10T12:15:42.087-03:00su: warning: cannot change directory to /home/user: Permission deniedsu: warning: cannot change directory to /home/user: Permission deniedsu: failed to execute /bin/bash: Permission denied<!--
google_ad_client = "ca-pub-3021803715878426";
/* lordpinguimPost */
google_ad_slot = "9468077813";
google_ad_width = 300;
google_ad_height = 250;
//-->
<!--
google_ad_client = "ca-pub-3021803715878426";
/* lordpinguimPost */
google_ad_slot = "9468077813";
google_ad_width = lordtuxhttp://www.blogger.com/profile/16697900975244199498noreply@blogger.com0tag:blogger.com,1999:blog-4036498795580614691.post-81633201636110608422020-06-25T18:41:00.001-03:002020-06-25T19:10:40.361-03:00DO NOT UPGRADE FOR VIOS 3.1 FROM 2.2 BEFORE READ THISRight, if you read my last post about how to overcome a problem with VIOs upgrade I have bad news for you.<!--
google_ad_client = "ca-pub-3021803715878426";
/* lordpinguimPost */
google_ad_slot = "9468077813";
google_ad_width = 300;
google_ad_height = 250;
//-->
Like I showed in the last post, the update will fail because the fileset bos.alt_disk_install.boot_images, the fileset installed in yourlordtuxhttp://www.blogger.com/profile/16697900975244199498noreply@blogger.com0