On 02/08/2017 07:35 PM, Kenneth Porter wrote:
> --On Wednesday, February 08, 2017 7:25 PM -0800 Alice Wonder
> <alice(a)domblogger.net> wrote:
>
>> As far as I can tell PHP built against LibreSSL works just fine running
>> with the net-snmp bindings built against OpenSSL however there was a
>> warning in the system log from ld when I tried it.
>
> There should only be a problem if Net-SNMP depends on bugs in the
> OpenSSL implementation.
What I really worry about is bugs in makefiles - if I have openssl-devel
installed in /usr to satisfy the net-snmp-devel package, and I have
libressl-devel installed on /opt - what happens if a Makefile gets
confused when parsing the pkgconfig files or something and uses the
wrong header files for the libraries it is linking against.
That's why I want to make sure only one devel package for an API is
installed at a time, and that's easiest to do by always using /usr as
the prefix so that if dependencies are brought in by the mock build
system that result in two implementations of the same API, they will
conflict with each other and mock will exit.
For the runtime I'm not that worried, the shared libraries have
different versions.
It's building where bugs in Makefile systems could cause the wrong
headers being used.
On Tue, 2010-02-16 at 05:58 -0500, Alberto Garcia Gomez wrote:
> Did anyone know where can I find the MonoDevelop as RPM?
>
> I wonder if thereś any version under 2.2
>
http://monodevelop.com/
yum search mono ## have fun
mono-core.i386 : The Mono CIL runtime, suitable for running .NET code
mono-data.i386 : Database connectivity for Mono
mono-data-firebird.i386 : Firebird database connectivity for Mono
mono-data-oracle.i386 : Oracle database connectivity for Mono
mono-data-postgresql.i386 : Postgresql database connectivity for Mono
mono-data-sqlite.i386 : sqlite database connectivity for Mono
mono-data-sybase.i386 : Sybase database connectivity for Mono
mono-devel.i386 : Development tools for Mono
mono-extras.i386 : Provides the infrastructure for running and building
daemons and services with Mono as well as various stub assemblies
mono-jscript.i386 : JScript .NET support for Mono
mono-locale-extras.i386 : Extra locale information for Mono
mono-nunit.i386 : NUnit Testing Framework
mono-nunit-devel.i386 : pkgconfig for nunit
mono-web.i386 : ASP.NET, Remoting, and Web Services for Mono
mono-winforms.i386 : Windows Forms implementation for Mono
xsp.i386 : A small web server that hosts ASP.NET
xsp-devel.i386 : Development files for xsp
I have no idea what you mean by version 2.2 but any .Net 2.0 code will
run on mono and 1.1 with a lil work that is.
John
> If someone wants to send me a cheat sheet on how to run a command line
> version of bitorrent, I'll throw one up on a reasonably beefy machine
> at the datacenter that's got multiple gigE links to the net.
log in as a regular user.
$ wget http://www.rahul.net/dholmes/ctorrent/ctorrent-1.3.4-dnh3.tar.gz
$ tar xvzf ctorrent-1.3.4-dnh3.tar.gz
$ cd ctorrent-dnh3
$ ./configure && make
$ su
# make install
# exit
$ mkdir bt # on a volume with a lotta space for ISOs
$ cd bt
$ wget
http://altruistic.lbl.gov/mirrors/centos/5.0/isos/x86_64/CentOS-5.0-x86_64-…
$ ctorrent -D 250 -U 250 CentOS-5.0-x86_64-bin-DVD.torrent
....
replace the 250's with the max Kbyte/sec Download and Upload you'd like
to see it use (it WILL saturate your connection if allowed to). ? or
h to show runtime help, you can change these on the fly. use a
`screen` connection so you can disconnect and leave it running....
We installed BMR boot server version 6.0 on DELL server. This DELL server have CENTOS 3.7 in it. We got error message when we tried to use "bmrsrtadm". Anyone know how to fix it or work around? ./bmrsrtadm Select one of the following options: 1. Create a new Shared Resource Tree. 2. Create a new CD image based Shared Resource Tree. 3. Copy an existing Shared Resource Tree to a new location. 4. Modify an existing Shared Resource Tree. 5. Delete an existing Shared Resource Tree. 6. List Shared Resource Trees available on this server. 7. Quit. Enter your selection (1-7) [1] : 1 Enter the name of the SRT to create : centos35 Enter the description of the new SRT : blade V-128-312 Unsupported Linux release: CentOS release 3.7 (Final) V-128-312 Unsupported Linux release: CentOS release 3.7 (Final) Enter the directory in which to place the new SRT [/export/srt] : /usr/openv/net backup V-125-419
/usr/openv/netbackup/baremetal/server/data/createsrt.conf: internal er ror - failed to load SRT/BI contents for platform "i686-RHEL-" V-125-39 caught exception: runtime error in srtPlat.cpp:PackageInfo::PackageInfo () [Error] V-125-40 Platform initialization failed. Please review logs for addition al diagnostic information. Removing SRT "centos35" from server -- please stand by ... _________________________________________________________________
___________________________________________________
您的生活即時通 - 溝通、娛樂、生活、工作一次搞定!
http://messenger.yahoo.com.tw/
Hi, I am seeing frequent libvirtd hangs (clients not responding) after
last CentOS6-Xen update :
libvirt-libs-4.1.0-2.xen46.el6.x86_64
libvirt-daemon-4.1.0-2.xen46.el6.x86_64
libvirt-daemon-driver-network-4.1.0-2.xen46.el6.x86_64
libvirt-daemon-driver-nwfilter-4.1.0-2.xen46.el6.x86_64
libgcc-4.4.7-18.el6_9.2.x86_64
2:qemu-img-0.12.1.2-2.503.el6_9.5.x86_64
libvirt-daemon-driver-storage-core-4.1.0-2.xen46.el6.x86_64
libvirt-daemon-driver-secret-4.1.0-2.xen46.el6.x86_64
libvirt-daemon-driver-interface-4.1.0-2.xen46.el6.x86_64
libvirt-daemon-driver-nodedev-4.1.0-2.xen46.el6.x86_64
10:centos-release-xen-common-8-4.el6.x86_64
xen-licenses-4.6.6-12.el6.x86_64
xen-libs-4.6.6-12.el6.x86_64
libvirt-daemon-driver-libxl-4.1.0-2.xen46.el6.x86_64
libvirt-daemon-driver-xen-4.1.0-2.xen46.el6.x86_64
libvirt-daemon-driver-qemu-4.1.0-2.xen46.el6.x86_64
libvirt-daemon-driver-storage-gluster-4.1.0-2.xen46.el6.x86_64
libvirt-daemon-driver-storage-logical-4.1.0-2.xen46.el6.x86_64
libvirt-daemon-driver-storage-mpath-4.1.0-2.xen46.el6.x86_64
libvirt-daemon-driver-storage-disk-4.1.0-2.xen46.el6.x86_64
libvirt-daemon-driver-storage-scsi-4.1.0-2.xen46.el6.x86_64
libvirt-daemon-driver-storage-iscsi-4.1.0-2.xen46.el6.x86_64
libvirt-daemon-driver-storage-4.1.0-2.xen46.el6.x86_64
libstdc++-4.4.7-18.el6_9.2.x86_64
libvirt-daemon-config-nwfilter-4.1.0-2.xen46.el6.x86_64
libvirt-daemon-config-network-4.1.0-2.xen46.el6.x86_64
libvirt-daemon-driver-lxc-4.1.0-2.xen46.el6.x86_64
libvirt-client-4.1.0-2.xen46.el6.x86_64
linux-firmware-20171215-82.git2451bb22.el6.noarch
12:dhcp-common-4.1.1-53.P1.el6.centos.4.x86_64
12:dhclient-4.1.1-53.P1.el6.centos.4.x86_64
libvirt-4.1.0-2.xen46.el6.x86_64
10:centos-release-xen-46-8-4.el6.x86_64
10:centos-release-xen-44-8-4.el6.x86_64
tzdata-2018e-3.el6.noarch
libgomp-4.4.7-18.el6_9.2.x86_64
kernel-4.9.86-30.el6.x86_64
xen-hypervisor-4.6.6-12.el6.x86_64
xen-runtime-4.6.6-12.el6.x86_64
xen-4.6.6-12.el6.x86_64
libvirt-daemon-xen-4.1.0-2.xen46.el6.x86_64
Remedy is to kill -9 libvirtd and start again. Issue can be replicated
within few domU starts. Usually libvirtd hangs when domU is bringing up
xen drivers or something around udev, like:
xen_netfront: Initialising Xen virtual ethernet driver
I've been looking into libvirtd strace and debug logs, so far most
suspicious in libvirtd debug log is this:
libvirtd.log:2018-05-22 08:32:44.760+0000: 25455: debug :
udevRemoveOneDevice:1289 : Failed to find device to remove that has udev
name '/sys/devices/vif-24-0/net/vif24.0/queues/tx-7'
libvirtd.log:2018-05-22 08:32:44.761+0000: 25455: debug :
udevRemoveOneDevice:1289 : Failed to find device to remove that has udev
name '/sys/devices/vif-24-0/net/vif24.0/queues/tx-6'
libvirtd.log:2018-05-22 08:32:44.761+0000: 25455: debug :
udevRemoveOneDevice:1289 : Failed to find device to remove that has udev
name '/sys/devices/vif-24-0/net/vif24.0/queues/tx-4'
libvirtd.log:2018-05-22 08:32:44.762+0000: 25455: debug :
udevRemoveOneDevice:1289 : Failed to find device to remove that has udev
name '/sys/devices/vif-24-0/net/vif24.0/queues/tx-5'
libvirtd.log:2018-05-22 08:32:44.763+0000: 25455: debug :
udevRemoveOneDevice:1289 : Failed to find device to remove that has udev
name '/sys/devices/vif-24-0/net/vif24.0/queues/tx-2'
libvirtd.log:2018-05-22 08:32:44.764+0000: 25455: debug :
udevRemoveOneDevice:1289 : Failed to find device to remove that has udev
name '/sys/devices/vif-24-0/net/vif24.0/queues/tx-3'
libvirtd.log:2018-05-22 08:32:44.765+0000: 25455: debug :
udevRemoveOneDevice:1289 : Failed to find device to remove that has udev
name '/sys/devices/vif-24-0/net/vif24.0/queues/rx-6'
libvirtd.log:2018-05-22 08:32:44.766+0000: 25455: debug :
udevRemoveOneDevice:1289 : Failed to find device to remove that has udev
name '/sys/devices/vif-24-0/net/vif24.0/queues/rx-5'
libvirtd.log:2018-05-22 08:32:44.767+0000: 25455: debug :
udevRemoveOneDevice:1289 : Failed to find device to remove that has udev
name '/sys/devices/vif-24-0/net/vif24.0/queues/rx-4'
libvirtd.log:2018-05-22 08:32:44.767+0000: 25455: debug :
udevRemoveOneDevice:1289 : Failed to find device to remove that has udev
name '/sys/devices/vif-24-0/net/vif24.0/queues/rx-7'
libvirtd.log:2018-05-22 08:32:44.768+0000: 25455: debug :
udevRemoveOneDevice:1289 : Failed to find device to remove that has udev
name '/sys/devices/vif-24-0/net/vif24.0/queues/rx-2'
libvirtd.log:2018-05-22 08:32:44.769+0000: 25455: debug :
udevRemoveOneDevice:1289 : Failed to find device to remove that has udev
name '/sys/devices/vif-24-0/net/vif24.0/queues/rx-3'
I could not get rid of this by reducing amount of driver queues (not
sure if that applies to PV)
Is someone out there seeing similar issues? Anyone perhaps interested in
reviewing full debug log / strace ?
Cheers
Karel
Bump. Folks, any ideas?
Cheers
Karel
On 22.5.2018 11:33, Karel Hendrych wrote:
> Hi, I am seeing frequent libvirtd hangs (clients not responding) after
> last CentOS6-Xen update :
>
> libvirt-libs-4.1.0-2.xen46.el6.x86_64
> libvirt-daemon-4.1.0-2.xen46.el6.x86_64
> libvirt-daemon-driver-network-4.1.0-2.xen46.el6.x86_64
> libvirt-daemon-driver-nwfilter-4.1.0-2.xen46.el6.x86_64
> libgcc-4.4.7-18.el6_9.2.x86_64
> 2:qemu-img-0.12.1.2-2.503.el6_9.5.x86_64
> libvirt-daemon-driver-storage-core-4.1.0-2.xen46.el6.x86_64
> libvirt-daemon-driver-secret-4.1.0-2.xen46.el6.x86_64
> libvirt-daemon-driver-interface-4.1.0-2.xen46.el6.x86_64
> libvirt-daemon-driver-nodedev-4.1.0-2.xen46.el6.x86_64
> 10:centos-release-xen-common-8-4.el6.x86_64
> xen-licenses-4.6.6-12.el6.x86_64
> xen-libs-4.6.6-12.el6.x86_64
> libvirt-daemon-driver-libxl-4.1.0-2.xen46.el6.x86_64
> libvirt-daemon-driver-xen-4.1.0-2.xen46.el6.x86_64
> libvirt-daemon-driver-qemu-4.1.0-2.xen46.el6.x86_64
> libvirt-daemon-driver-storage-gluster-4.1.0-2.xen46.el6.x86_64
> libvirt-daemon-driver-storage-logical-4.1.0-2.xen46.el6.x86_64
> libvirt-daemon-driver-storage-mpath-4.1.0-2.xen46.el6.x86_64
> libvirt-daemon-driver-storage-disk-4.1.0-2.xen46.el6.x86_64
> libvirt-daemon-driver-storage-scsi-4.1.0-2.xen46.el6.x86_64
> libvirt-daemon-driver-storage-iscsi-4.1.0-2.xen46.el6.x86_64
> libvirt-daemon-driver-storage-4.1.0-2.xen46.el6.x86_64
> libstdc++-4.4.7-18.el6_9.2.x86_64
> libvirt-daemon-config-nwfilter-4.1.0-2.xen46.el6.x86_64
> libvirt-daemon-config-network-4.1.0-2.xen46.el6.x86_64
> libvirt-daemon-driver-lxc-4.1.0-2.xen46.el6.x86_64
> libvirt-client-4.1.0-2.xen46.el6.x86_64
> linux-firmware-20171215-82.git2451bb22.el6.noarch
> 12:dhcp-common-4.1.1-53.P1.el6.centos.4.x86_64
> 12:dhclient-4.1.1-53.P1.el6.centos.4.x86_64
> libvirt-4.1.0-2.xen46.el6.x86_64
> 10:centos-release-xen-46-8-4.el6.x86_64
> 10:centos-release-xen-44-8-4.el6.x86_64
> tzdata-2018e-3.el6.noarch
> libgomp-4.4.7-18.el6_9.2.x86_64
> kernel-4.9.86-30.el6.x86_64
> xen-hypervisor-4.6.6-12.el6.x86_64
> xen-runtime-4.6.6-12.el6.x86_64
> xen-4.6.6-12.el6.x86_64
> libvirt-daemon-xen-4.1.0-2.xen46.el6.x86_64
>
> Remedy is to kill -9 libvirtd and start again. Issue can be replicated
> within few domU starts. Usually libvirtd hangs when domU is bringing up
> xen drivers or something around udev, like:
>
> xen_netfront: Initialising Xen virtual ethernet driver
>
> I've been looking into libvirtd strace and debug logs, so far most
> suspicious in libvirtd debug log is this:
>
> libvirtd.log:2018-05-22 08:32:44.760+0000: 25455: debug :
> udevRemoveOneDevice:1289 : Failed to find device to remove that has udev
> name '/sys/devices/vif-24-0/net/vif24.0/queues/tx-7'
> libvirtd.log:2018-05-22 08:32:44.761+0000: 25455: debug :
> udevRemoveOneDevice:1289 : Failed to find device to remove that has udev
> name '/sys/devices/vif-24-0/net/vif24.0/queues/tx-6'
> libvirtd.log:2018-05-22 08:32:44.761+0000: 25455: debug :
> udevRemoveOneDevice:1289 : Failed to find device to remove that has udev
> name '/sys/devices/vif-24-0/net/vif24.0/queues/tx-4'
> libvirtd.log:2018-05-22 08:32:44.762+0000: 25455: debug :
> udevRemoveOneDevice:1289 : Failed to find device to remove that has udev
> name '/sys/devices/vif-24-0/net/vif24.0/queues/tx-5'
> libvirtd.log:2018-05-22 08:32:44.763+0000: 25455: debug :
> udevRemoveOneDevice:1289 : Failed to find device to remove that has udev
> name '/sys/devices/vif-24-0/net/vif24.0/queues/tx-2'
> libvirtd.log:2018-05-22 08:32:44.764+0000: 25455: debug :
> udevRemoveOneDevice:1289 : Failed to find device to remove that has udev
> name '/sys/devices/vif-24-0/net/vif24.0/queues/tx-3'
> libvirtd.log:2018-05-22 08:32:44.765+0000: 25455: debug :
> udevRemoveOneDevice:1289 : Failed to find device to remove that has udev
> name '/sys/devices/vif-24-0/net/vif24.0/queues/rx-6'
> libvirtd.log:2018-05-22 08:32:44.766+0000: 25455: debug :
> udevRemoveOneDevice:1289 : Failed to find device to remove that has udev
> name '/sys/devices/vif-24-0/net/vif24.0/queues/rx-5'
> libvirtd.log:2018-05-22 08:32:44.767+0000: 25455: debug :
> udevRemoveOneDevice:1289 : Failed to find device to remove that has udev
> name '/sys/devices/vif-24-0/net/vif24.0/queues/rx-4'
> libvirtd.log:2018-05-22 08:32:44.767+0000: 25455: debug :
> udevRemoveOneDevice:1289 : Failed to find device to remove that has udev
> name '/sys/devices/vif-24-0/net/vif24.0/queues/rx-7'
> libvirtd.log:2018-05-22 08:32:44.768+0000: 25455: debug :
> udevRemoveOneDevice:1289 : Failed to find device to remove that has udev
> name '/sys/devices/vif-24-0/net/vif24.0/queues/rx-2'
> libvirtd.log:2018-05-22 08:32:44.769+0000: 25455: debug :
> udevRemoveOneDevice:1289 : Failed to find device to remove that has udev
> name '/sys/devices/vif-24-0/net/vif24.0/queues/rx-3'
>
> I could not get rid of this by reducing amount of driver queues (not
> sure if that applies to PV)
>
> Is someone out there seeing similar issues? Anyone perhaps interested in
> reviewing full debug log / strace ?
>
> Cheers
> Karel
>
> _______________________________________________
> CentOS-virt mailing list
> CentOS-virt(a)centos.org
> https://lists.centos.org/mailman/listinfo/centos-virt
On Tue, Oct 18, 2016 at 09:49:30AM -0500, Jim Perrin wrote:
>
>
> On 10/18/2016 08:04 AM, Richard W.M. Jones wrote:
>
> > (3) The real reason I'm doing this now is because partners have asked
> > us to update the OCaml compiler in RHEL 7.4. This will be a binary
> > ABI break -- it's unfortunately unavoidable -- and will require all
> > OCaml-using programs to be recompiled, and of course that will affect
> > CentOS and any other RHEL derivatives.
>
>
> Thanks for the heads-up on this one.
It's not definite yet, but good for CentOS to be aware.
> Happen to have a rough estimate
> handy for the number of impacted packages?
In base RHEL we will be updating these packages:
ocaml
ocaml-calendar
ocaml-csv
ocaml-curses
ocaml-extlib
ocaml-fileutils
ocaml-findlib
ocaml-gettext
ocaml-libvirt
ocaml-ounit
ocaml-xml-light
hivex
graphviz
brlapi
libguestfs
In the extended CentOS/EPEL it will be anything returned by this
command:
repoquery --whatrequires ocaml-runtime --qf "%{name}" | sort -u
(That's binary packages, not source packages, but it's a good start).
This is assuming you don't want to rebuild packages which contain only
OCaml binaries. In fact you might want to do that because of a CVE
which came up last year (https://bugzilla.redhat.com/CVE-2015-8869)
In that case you need to look for any package which `BuildRequires: ocaml'.
I'm afraid my repoquery-fu is not good enough :-(
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-top is 'top' for virtual machines. Tiny program with many
powerful monitoring features, net stats, disk stats, logging, etc.
http://people.redhat.com/~rjones/virt-top