similar to: yum --import of RPMforge

Hi All, I had some health issues for a few months and I barely recall dealing with Heartbleed ... it's all just a blur. Now I'm getting back up to speed, but I have a pair of CentOS 6.6 x86_64 + Virtualmin 4.13 GPL servers which no longer seem to be picking up available updates. 'yum check' ran for about 25 minutes this evening on one of them and returned nothing useful. rpm -qa

Hi, On Tue, Apr 28, 2015 at 10:37 AM, <carlh04426 at gmail.com> wrote: > Hi All, > > I had some health issues for a few months and I barely recall dealing > with Heartbleed ... it's all just a blur. Now I'm getting back up to > speed, but I have a pair of CentOS 6.6 x86_64 + Virtualmin 4.13 GPL > servers which no longer seem to be picking up available updates.

Alle, I'm running CentOS 4.8. I just started seeing these errors during RPM operations: error: rpmdbAdd: skipping h# 990 Header V3 DSA signature: BAD, key ID 443e1821 error: rpmdbNextIterator: skipping h# 969 Header V3 DSA signature: BAD, key ID 443e1821 I've cleared out the __db.* files and tried to rebuild the DB with no luck. I've also tried this:

On 1/4/19 8:22 AM, Daniel Walsh wrote: > On 1/3/19 10:19 PM, H wrote: >> I recently updated docker to version 18.09 and I seem to have lost the container id in the command prompt when I exec into a running container, a very useful feature in the previous version I was running. I have not found any information in the Docker General Forum. >> >> Has anyone else seen this?

Got a problem with one workstation. What I'm seeing, from a yum update (saw it with make whatis first): <snip> Running rpm_check_debug error: rpmdbNextIterator: skipping h# 1211 hdr SHA1: BAD, not hex <repeated many times> <snip> ERROR with rpm_check_debug vs depsolve: libicui18n.so.36 is needed by boost-1.33.1-10.el5_7.3.i386 libicuuc.so.36 is needed by

On 01/04/2019 09:16 PM, H wrote: > On 01/04/2019 08:27 AM, Daniel Walsh wrote: >> On 1/4/19 8:22 AM, Daniel Walsh wrote: >>> On 1/3/19 10:19 PM, H wrote: >>>> I recently updated docker to version 18.09 and I seem to have lost the container id in the command prompt when I exec into a running container, a very useful feature in the previous version I was running. I have

I have a system (Centos 4.4 all packages uptodate) where almost every rpm or yum operation fails with a message like e.g.: error: %preun(a2ps-4.13b-41.i386) scriptlet failed, exit status 255 some times the error is on %post() the last few lines of output from rpm -e -vv a2ps are D: ========== --- a2ps-4.13b-41 i386-linux 0x1 D: erase: a2ps-4.13b-41 has 316 files, test = 0 D: opening db

I recently updated docker to version 18.09 and I seem to have lost the container id in the command prompt when I exec into a running container, a very useful feature in the previous version I was running. I have not found any information in the Docker General Forum. Has anyone else seen this?

Trying to apply the latest updates to an Athalon base fully updated CentOS 4.2. In the past used the update process kicked off by clicking the hand-dandy red icon. This failed, so I tried yum. Somewhere in the process, it complained that there was no GPG key for the lame libraries (IIRC, everything's a little hazy after all the Googling trying to fix this). Anyway, tried "yum

[root at host ~]# yum clean all Loaded plugins: fastestmirror, protectbase Cleaning up Everything Cleaning up list of fastest mirrors [root at ost ~]# yum search libcli Loaded plugins: fastestmirror, protectbase Determining fastest mirrors * base: centos-distro.cavecreek.net * elrepo: elrepo.imt-systems.com * extras: ftp.ussg.iu.edu * rpmforge: apt.sw.be * updates: mirror.nandomedia.com base

Hi, I've encountered the following problem at a client. The problem results in one or more of the smbd processing continuously grabbing more and more memory until the system runs out of memory or just becomes unusable due to a low memory condition. This error is extremely serious as the entire server is eventually brought down by one error. After debugging this error at the

I'm attempting to install Hobbit 4.2.1 on CentOS 4.3. When attempting to "configure -server", I get: : : Checking for RRDtool ... RRDtool include- or library-files not found. These are REQUIRED for hobbitd RRDtool can be found at http://people.ee.ethz.ch/~oetiker/webtools/rrdtool/ If you have RRDtool installed, use the "--rrdinclude DIR" and "--rrdlib DIR"

Hello, I am using "shorewall add" and "shorewall delete" for dynamically adding and removing users to VPN chains when connecting to a VPN gateway. But ''shorewall delete'' has a little problem to delete the correct rules. When issuing "shorewall delete iface:host zone", shorewall tries to execute rules like: iptables -D source_chain -s host1 -o

On 1/3/19 10:19 PM, H wrote: > I recently updated docker to version 18.09 and I seem to have lost the container id in the command prompt when I exec into a running container, a very useful feature in the previous version I was running. I have not found any information in the Docker General Forum. > > Has anyone else seen this? > > _______________________________________________ >

On 01/04/2019 08:27 AM, Daniel Walsh wrote: > On 1/4/19 8:22 AM, Daniel Walsh wrote: >> On 1/3/19 10:19 PM, H wrote: >>> I recently updated docker to version 18.09 and I seem to have lost the container id in the command prompt when I exec into a running container, a very useful feature in the previous version I was running. I have not found any information in the Docker General

On 1/4/19 9:50 PM, H wrote: > On 01/04/2019 09:16 PM, H wrote: >> On 01/04/2019 08:27 AM, Daniel Walsh wrote: >>> On 1/4/19 8:22 AM, Daniel Walsh wrote: >>>> On 1/3/19 10:19 PM, H wrote: >>>>> I recently updated docker to version 18.09 and I seem to have lost the container id in the command prompt when I exec into a running container, a very useful

On 18.06.24 13:36, Stuart Henderson wrote: > Not sure whether anything should be done with it, but I noticed so > thought I'd mention: if you pass ssh-keygen -R a known_hosts file with > DSA sigs, you get "invalid line" warnings. Out of interest, did you, perchance, try running an ssh-keygen -l on a DSA-infested file? (I added a bit of extra IDS to our monitoring that

I was running a rpm -qa --qf "%{vendor} \t\t%{name}\n" |sort|grep -v CentOS looking for packages from other vendors installed on a machine and noticed a curious sight: Fujitsu Limited crash-trace-command It appears I am not the only one who has crash-trace-command from Fujitsu Limited https://www.centos.org/forums/viewtopic.php?f=13&t=1081&start=0#p6688 That

Hi, is there a particular reason why this feature is "user" based and not "user-pubkey" based? What I mean is that it works for installation with small number of pubkeys per user. But imagine i.e. a GitHub scale - all users logging in as user "git". On each auth request all the keys from database would be fetched and feeded to OpenSSH. Now I am only asking this out

Hello. I once read somewhere that it's possible to limit SSH pubkeys to 'tunnel-only'. I can't seem to find any information about this in any of the usual places. I'm going to be deploying a few servers in a couple of days and I'd like them to log to a central server over an SSH tunnel (using syslog-ng) however I'd like to prevent actual logins (hence