I am trying to install SNMP package in SUSE Linux enterprise server 11. I downloaded net-snmp-5.6.1-3.3.x86_64.rpm and installed with the below command
UKGBDCESRPL048:/opt/packages # rpm -ivh --nodeps net-snmp-5.6.1-3.3.x86_64.rpm
warning: net-snmp-5.6.1-3.3.x86_64.rpm: Header V3 RSA/SHA256 signature: NOKEY, key ID 3dbdc284
Preparing...
##################################### [100%]
1:net-snmp
##################################### [100%]
Updating /etc/sysconfig/net-snmp...
But when I try to start snmpd service, I am getting an error below:
UKGBDCESRPL048:/opt/packages # /etc/init.d/snmpd start
Starting snmpd/usr/sbin/snmpd: error while loading shared libraries: libnetsnmpagent.so.25: cannot open shared object file: No such file or directory
startproc: exit status of parent of /usr/sbin/snmpd: 127
Please help me to properly install SNMP package.
Why are you trying to install the RPM with --nodeps? This breaks your RPM dependencies! Please remove the package again and try to install it without that option. This should fail with a list of additionally required RPM's.
You'll have to install them, too. BTW, I'm sure that at least the RPM libsnmp15 is missing, because libnetsnmpagent.so.25 is in there.
You could also configure SLES to use one or more (online) repositories after registering your machine with a license key. After that, a simple
zypper in net-snmp
should solve all dependencies automatically.
One more thing: net-snmp-5.6.1-3.3.x86_64.rpm doesn't seem to be a valid SLES 11 package. Latest version (even SP4) is 5.4.2.1-8.12.24.1. Where did you get the RPM from? Just wondering...
Related
So I'm trying to install yasm on Windows 11 with Chocolatey, but an error occurs, does anyone know how to solve this error?
PS C:\WINDOWS\system32> choco install yasm
Chocolatey v1.2.0
Installing the following packages:
yasm
By installing, you accept licenses for the packages.
Progress: Downloading yasm 1.2.0... 100%
yasm v1.2.0
yasm package files install completed. Performing other installation steps.
The package yasm wants to run 'chocolateyInstall.ps1'.
Note: If you don't run this script, the installation will fail.
Note: To confirm automatically next time, use '-y' or consider:
choco feature enable -n allowGlobalConfirmation
Do you want to run the script?([Y]es/[A]ll - yes to all/[N]o/[P]rint): Y
WARNING: Url has SSL/TLS available, switching to HTTPS for download
Downloading yasm 64 bit
from 'https://www.tortall.net/projects/yasm/releases/yasm-1.2.0-win64.exe'
Progress: 100% - Completed download of C:\ProgramData\chocolatey\lib\yasm\tools\yasm.exe (779.5 KB).
Download of yasm.exe (779.5 KB) completed.
C:\ProgramData\chocolatey\lib\yasm\tools\yasm.exe
ERROR: The term 'Write-ChocolateyFailure' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
The install of yasm was NOT successful.
Error while running 'C:\ProgramData\chocolatey\lib\yasm\tools\chocolateyInstall.ps1'.
See log for details.
Chocolatey installed 0/1 packages. 1 packages failed.
See the log for details (C:\ProgramData\chocolatey\logs\chocolatey.log).
Failures
- yasm (exited -1) - Error while running 'C:\ProgramData\chocolatey\lib\yasm\tools\chocolateyInstall.ps1'.
See log for details.
I couldn't find a solution on the internet, so I asked here.
The package uses helpers (Write-Chocolatey-Failure) that have been deprecated for some time and subsequently removed. To restore the functionality you can use the chocolatey-compatibility.extension package.
However, two things:
The package is trying to write a failure message, so something is likely broken with the package.
The package was last updated in 2013 so YMMV with the software it's downloading working at all.
This happens because you are trying to install a package that still uses a syntax that is no longer supported in Chocolatey CLI. You have two options to resolve this issue.
The first and best option is to try contacting the package's maintainer and ask them to update the package to follow modern standards of how a package should be written.
The second option that will fix your current issue is to install a compatibility package to reintroduce removed helpers that are no longer supported.
You can install this package by running: choco install chocolatey-compatibility.extension and then try installing the yasm package again.
We are facing issue while installing Websphere MQClient v9.0.0.1 on linux machine.at the time of rpm packages installation we are getting below error.
Note: And it is Multi-installation setup,we have a MQClient version 8.0.0.4 in different file system which is Installation1 file system is /Informatica/app/MQClient.
Installed packages on server.
MQSeriesMan-8.0.0-4.x86_64
MQSeriesGSKit-9.0.0-1.x86_64
MQSeriesGSKit-8.0.0-4.x86_64
MQSeriesSamples-8.0.0-4.x86_64
MQSeriesSDK-9.0.0-1.x86_64
MQSeriesClient-9.0.0-1.x86_64
MQSeriesClient-8.0.0-4.x86_64
MQSeriesSDK-8.0.0-4.x86_64
MQSeriesJava-9.0.0-1.x86_64
MQSeriesMan-9.0.0-1.x86_64
MQSeriesRuntime-8.0.0-4.x86_64
MQSeriesJava-8.0.0-4.x86_64
MQSeriesRuntime-9.0.0-1.x86_64
MQSeriesJRE-9.0.0-1.x86_64
MQSeriesJRE-8.0.0-4.x86_64
MQSeriesSamples-9.0.0-1.x86_64
We could see the libmqmr_r.so file in below location
/infaicc/app/MQClient/lib/libmqmr_r.so
We have set the environment variableby using below command
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/infaicc/app/MQClient/lib64
but still we are facing same error.
rpm -ivh --prefix /infaicc/app/MQClient MQSeriesRuntime-9.0.0-1.x86_64.rpm
Preparing... ################################# [100%]
Updating / installing...
1:MQSeriesRuntime-8.0.0-0 ################################# [100%]
ERROR: dspmqver: error while loading shared libraries: libmqmcs_r.so: cannot open shared object file: No such file or directory
rpm -ivh --prefix /infaicc/app/MQClient MQSeriesClient-9.0.0-7.x86_64.rpm
Preparing... ################################# [100%]
Updating / installing...
1:MQSeriesRuntime-8.0.0-0 ################################# [100%]
ERROR: dspmqver: error while loading shared libraries: libmqmcs_r.so: cannot open shared object file: No such file or directory
[root#XXXX-as-0037 bin]# ./dspmqver
./dspmqver: error while loading shared libraries: libmqmcs_r.so: cannot open shared object file: No such file or directory
[root#XXXX-as-0037 bin]#
Please let us know is it mandatory to run this crtmqpkg suffix in multiple installation scenario, if yes kindly confirm from which location I need to run this ( means from installation1 ) command.
Our existing setup is working fine without any issue. If we run crtmqpkg suffix command is there any impact on my existing version.
Before installation should we stop the all existing MQ process?
#Roger/Josh: Thanks for update,we are getting below error while executing ./crtmqpkg 2. kindly help on this issue.
[root#xxxx_xxx_xx_ mqclient]# ./crtmqpkg 1
ERROR: Unable to execute "/usr/bin/rpmbuild" - required for packaging.
Check that you have the "rpm-build" package installed on your system,
or which ever package provides "rpmbuild" on your Linux distribution.
#Josh: we have installed the rpm-build packages and run the ./crtmqpkg 2 command it got succeed but while installing websphere MQ rpm packages getting below error.We followed the given IBM tech-notes still facing error.
[root#XXXX_XXX_XX MQClient]# rpm --prefix /infaicc/app/MQClient -ivh /infaicc/app/MQClient_Binary/2/x86_64/MQSeriesRuntime_2-9.0.0-1.x86_64.rpm
Preparing... ########################################### [100%]
1:MQSeriesRuntime_2 ########################################### [100%]
ERROR: Return code "127" from amqicdir for "-i -f", output is:
/infaicc/app/MQClient/bin/amqicdir: error while loading shared libraries: libmqmcs_r.so: cannot open shared object file: No such file or directory
ERROR: Return code "127" from crtmqinst for "-p /infaicc/app/MQClient ", output is:
/infaicc/app/MQClient/bin/crtmqinst: error while loading shared libraries: libmqmcs_r.so: cannot open shared object file: No such file or directory
ERROR: Return code "127" from amqicdir for "-s -f", output is:
/infaicc/app/MQClient/bin/amqicdir: error while loading shared libraries: libmqmcs_r.so: cannot open shared object file: No such file or directory
ERROR: Return code "127" from setmqinst for "-r -p /infaicc/app/MQClient", output is:
/infaicc/app/MQClient/bin/setmqinst: error while loading shared libraries: libmqmcs_r.so: cannot open shared object file: No such file or directory
Did you follow the MQ instructions here or here because I don't see any mention of creating the install package. Also, you need to set your installation but I don't see anything about it either.
As Roger pointed out the following IBM MQ Knowledge Center page provided details: IBM MQ 9.0.x>IBM MQ>Installing and uninstalling>Installing and uninstalling IBM MQ on Linux>Installing IBM MQ on Linux using rpm>Installing IBM MQ server on Linux
First this page answers your first question:
Note
The crtmqpkg command is required only if this is not the first
installation of IBM MQ on the system. If you have earlier versions of
IBM MQ installed on your system, then installing the latest version
works correctly if you install it in a different location.
Given that it appears you already have MQ v8.0.0.4 installed you will need to perform the required steps to create a MQ v9.0.0.7 set of rpms with a new suffix.
The reason this is required is because you can not install two rpms with the same base package name. By creating a new RPM with a suffix is giving the rpm a different base name.
Actually running the crtmqpkg command will not cause any issues with your existing installation since it is just creating new rpm files on the file system. When you install it as long as you specify a different installation location it will not cause any problem for your existing installation either.
Roger provided the second link to the IBM MQ Knowledge Center page that provides details specific to the MQ client packages: IBM MQ 9.0.x>IBM MQ>Installing and uninstalling>Installing and uninstalling IBM MQ on Linux>Installing IBM MQ on Linux using rpm>Installing an IBM MQ client on Linux
If you have multiple installations on this system, you must run crtmqpkg to create a unique set of packages to install on the system:
a. Enter the following command:
./crtmqpkg suffix
where suffix is a name of your choosing, that will uniquely identify the installation packages on the system. suffix is not the
same as an installation name, although the names can be identical.
suffix is limited to 16 characters in the ranges A-Z, a-z, and 0-9.
b. Set your current directory to the location specified when the
crtmqpkg command completes. This directory is a sub-directory of /var/tmp/mq_rpms, in which the unique set of packages is created. The
packages have the suffix value contained within the filename.
Because the installation of the new package is not going into the same location there is No requirement to stop existing IBM MQ processes.
I have installed apt onto a system built by BitBake by adding the apt package to the IMAGE_INSTALL variable in my recipe.
apt-get and apt-cache now execute on the built system, but if I try to do anything useful with them (such as apt-get update or apt-cache search), I get the following error:
E: Could not open file /var/lib/dpkg/status - open (2: No such file or directory)
E: The package lists or status file could not be parsed or opened
After some preliminary searching, I found this exchange on the Yocto Project mailing list:
Hi,
I have some requirement with apt-get in yocto genearted rootfs.
I built the yocto source code with enabling the apt package.
But after booting the image on my machine and run the "apt-get" command for installing some package it gives the following error.
Could not open the file /var/lib/dpkg/status open(2: no such a file or directory).
The package lists or status files could not be parsed or opened.
This error is because you need to add package-management to EXTRA_IMAGE_FEATURES in local.conf,
PACKAGE_CLASSES ?= "package_deb"
EXTRA_IMAGE_FEATURES = "debug-tweaks package-management"
I've added package-management but don't see any different output.
After a touch /var/lib/dpkg/status, apt-get update returns the following:
Reading package lists...Done
How can I get apt into a functioning state through the use of BitBake metadata?
I have found a similar thread from the NXP website.
You would need to set up your own web server and provide all those packages and add the server URL to the source list. SourceList
In addition, you have to update the package manifest by running bitbake package-index and add PACKAGE_CLASSES ?= " package_deb" to conf/local.conf
I have successfully set up OPKG before. The steps are similar, you can find it here
I am trying to compile the i3 window manager from source, which requires a header file from libsn (#include ).
I cannot find libsn's source package from anywhere and would like help locating it.
Fourth result from typing "libsn" into Google gives this. It's not a "package", but in order to find a package, we'd have to know what kind of package you need - RPM, DEB, tar.gz, ....
You need to locate a current version of the package: startup-notification-devel
I was trying to build i3 on CentOS 7, which includes startup-notification but not startup-notification-devel. My compilation was successful by using the package from RepoForge for CentOS 6. Exact commands will depend on your distribution, but here are the general steps.
Install RPMforge: http://wiki.centos.org/AdditionalResources/Repositories/RPMForge
Quick reference for CentOS 6/7 x86_64:
wget http://pkgs.repoforge.org/rpmforge-release/rpmforge-release-0.5.3-1.el6.rf.x86_64.rpm
rpm --import http://apt.sw.be/RPM-GPG-KEY.dag.txt
rpm -i rpmforge-release-0.5.3-1.el6.rf.*.rpm
Install the package:
yum install --enablerepo=rpmforge-extras startup-notification-devel
If you're not using RHEL/CentOS then you may want to download the source:
http://www.freedesktop.org/software/startup-notification/releases
Instructions to compile the libraries are available at the Linux From Scratch project:
http://www.linuxfromscratch.org/blfs/view/svn/x/startup-notification.html
Kernel version: 2.6.32-042stab057.1
rpm -qa | grep -i kernel result:
vzkernel-headers-2.6.32-042stab057.1.i686
libreport-plugin-kerneloops-2.0.9-5.el6.centos.i686
vzkernel-firmware-2.6.32-042stab057.1.noarch
abrt-addon-kerneloops-2.0.8-6.el6.centos.i686
vzkernel-devel-2.6.32-042stab057.1.i686
when i send the command make i get this error:
You do not appear to have the sources for the 2.6.32-042stab057.1 kernel installed.
OS: Centos 6.3 Final
I am not very familiar with OpenVZ, but from your provided information, looks like you don't have kernel source. You have kernel-devel and kernel-headers, but not the kernel itself.
You may download kernel here:
http://download.openvz.org/kernel/branches/rhel6-2.6.32/042stab057.1/vzkernel-2.6.32-042stab057.1.i686.rpm
And then: rpm -ivh vzkernel-2.6.32-042stab057.1.i686.rpm
I had the same issue compiling it on my new VPS. I was able to get it all to install from the files found at http://wiki.openvz.org/Download/kernel/rhel6/042stab057.1
Download/install those RPMs and you'll be good to go.
You need
have access to main node, compile asterisk on it
forward dahdi device to container(via container config)
copy from main node kernel-devel package, compile dahdi in container.
Read this
http://openvz.org/Asterisk_from_source