Postagens

Mostrando postagens de julho, 2020

ValueError: unsupported hash type shaXXX error when try to run yum to install package on AIX

When try to use yum on AIX you may face the following error: As you can see is something related to hash. After checking the system with the command rpm -qa I noticed that a very old version of openssl, from 2002, was installed, so I just removed it, no impact for the system as all is to use the native ssl version installed on AIX: [root@server1]/mnt/> rpm -e openssl-0.9.6b-3.ppc openssl-doc-0.9.6b-3.ppc warning: /var/ssl/openssl.cnf saved as /var/ssl/openssl.cnf.rpmsave [root@server1]/mnt/> Remember to recreate the file /var/ssl/openssl.cnf.rpmsave to avoid any issues cp -p /var/ssl/openssl.cnf.rpmsave /var/ssl/openssl.cnf

OSError: [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: To fix, just create the needed file with touch command: root@server::/var/lib/rpm> ls -ltra /var/lib/rpm/Packages ls: 0653-341 The file /var/lib/rpm/Packages does not exist. root@server::/var/lib/rpm> touch /var/lib/rpm/Packages     

Please wait...error: line 10: Dependency tokens must begin with alpha-numeric

On 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: .nfs0BF6 I 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 in a folder scanned by the command. If you check the command, it is a script, you will see the following part: Packager: auto-generated" # Check for local shared libraries /usr/bin/lslpp -Ou -qfc | /usr/bin/cut -d':' -f3 | /usr/bin/cut -d' ' -f1 |\   /usr/opt/rpm/lib/rpm/find-provides | while read shobj do    echo "Provides: $shobj" done This specific part: /usr/bin/lslpp -Ou -qfc You can run it on the terminal is responsible for the first part of the scan, is where that bad fille was showing. To temporally fix the issue I just edited the command,

How to use viosecure to tunning vios

viosecure 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.xml Check 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 high, be in mind that certain things can stop working. So to easy things you can starting apply only some set of rules that you consider important. Below is the content of a customized file that you can start using to apply the minim history size for example: <?xml version="1.0" encoding="UTF-8"?> <!--     @(#)45    1.2.1.12  src/bos/usr/lib/security/aixpert/scripts/viosecureall.xml, aixpert, bos72Q, q2019_31A8 7/30/19 10:35:04        COMPONENT_NAME:   (AIXPERT) aixpertall.xml     FUNCTIONS:     ORIGINS: 27                --> <!--    RuleType HLS represents H

DB2 and disk block size of 4096 on AIX

Be 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 not possible to change. Cause DB2 up to v10.5: only supports file system or devices with Block and Sector Sizes of 512 bytes DB2 v11.1 M4 FP4: Technical preview for 4KB sector size for non-production systems via DB2 registry variable DB2_4K_DEVICE_SUPPORT DB2 v11.5: Supports 4KB sector size Click here for more information from IBM.

mount: 1831-011 access denied for - NIM IP and Folder

mount: 1831-011 access denied for xx.xx.xx.xx:/nim/mksyb mount: 1831-008 giving up on: XX.XX.XX.XX:/nim/folder The file access permissions do not allow the specified action. If you get the error above on AIX, try to use the server name to mount instead the IP address. I faced this strange situation on AIX, besides was working fine on another server with another nim, in others I was unable to mount the remove folder using the IP address. /etc/exports was ok, equal the other NIM. client and server can see each other. So the solution was put the NIM server name and IP on the /etc/hosts and try again.

How 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 you can have errors messages if you try to install yum. As part of the installation of the rpm.rte, it runs as well the updtvpkg command to update the rpm database that have reference for new libs on the system that are used when you try to install new packages. wget -c https://public.dhe.ibm.com/aix/freeSoftware/aixtoolbox/ezinstall/ppc/yum_bundle.tar try to install using the command rpm -Uvh *.rpm Sometimes the command will fail due readline and glib packages, you can exclude them, sometimes you will already have some packages installed, you can exclude them using: rpm -Uvh $(ls *

su: warning: cannot change directory to /home/user: Permission denied

su: warning: cannot change directory to /home/user: Permission denied su: failed to execute /bin/bash: Permission denied After some verification I noticed that the problem was due the execution permission removed from the / (root) dir, just a chmod 755 / or chmod o+x fixed the issue.