#apache #archlinux #asterisk #centos #debian #gentoo #haskell #kde #kubuntu #lisp #math #mysql #perl #python #ruby-lang #rubyonrails #suse #ubuntu #vim #wikipedia 0 1 2 3 4 5 6 7 8 9 10 11
Top Prev 1216 1217 1218 1219 1220 1221 1222 1223 1224 1225 1226 1227 1228 1229 1230 1231 1232 1233 1234 Next
#centos
<Zathrus-2> hal: exact same
<range> "hal23456: rpm -q --changelog | head -10" shows you the changes from 3.0.10-1.4.9
<range> Ermm.
<hal23456> and the same syntax is used for the version number, ie 3.0.10-1.4E.11
<range> hal23456: Yes.
<hal23456> thank you range and zathrus
<range> More on the fix: <https://rhn.redhat.com/errata/RHSA-2007-0060.html>
<entr0py> range: Bind to port 22 on 0.0.0.0 failed: Address already in use.
<entr0py> heh
<range> entr0py: Did you stop sshd first?
<entr0py> but there is nothing running on 22 because i stopped sshd
<Zathrus-2> entr0py: how did you stop sshd?
<entr0py> service sshd stop
<Zathrus-2> and how long was it before you tried starting the new process?
<entr0py> 30 seconds or so
<Zathrus-2> wait at least 2 minute
<range> entr0py: Yeah, you'll probably find some "AVC denied" in your logfiles now.
<range> Zathrus-2: Or SELinux doesn't allow him to do that.
<sw-> this "bind failed" error is normal and is due to ipv6
<entr0py> so, funny thing is, it says it can't bind, but it's on the port answering to a telnet port 22 to the vm
<range> sw-: ipv6 bind fails on 0.0.0.0?
<sw-> either you disable ipv6 or specify the listenaddress
<sw-> range : yeah go figure
<entr0py> sw-: ah, that makes sense
<range> Okay.
<hal23456> that is a cool command, range (changelog) - I didn't know htat
<hal23456> that
<range> entr0py: And you're seeing debugging output on your console?
<Zathrus-2> range: yes, but I'd be surprised if that was it, since he's not trying to use a strange port
<range> Zathrus-2: Yeah.
<entr0py> yes, last thing printed is: "debug1: rexec start in 4 out 4 newsock 4 pipe -1 sock 7" when I try to ssh to the vm
<range> Oh my god! There's a second one of him.
<Zathrus-2> range: usually the issue I see is that the TCP Timeout hasn't expired yet, so you can't bind
<Zathrus-2> no, my DSL is being flaky, so there's only one of me at the moment :/
<range> entr0py: That doesn't give me anymore ideas.
<range> Zathrus-2: I can reenable that account :)
<entr0py> i'm going to let it timeout and see if the server adds anymore messages
<Zathrus-2> range: I may bug you tomorrow if this continues :)
<range> Okay.
<hal23456> is it possible to downgrade to a previous version of a package using yum?
<range> No.
<hal23456> is this sensible to do?
<hal23456> ah, ok
<Zathrus-2> usually not.
<range> You can get the rpms and install them with "rpm -Uvh --oldpackage samba*.rpm"
<range> If you're sure that none of your users will use the broken smbd to run a denial of service attack against your server.
<hal23456> will yum still be able to manage them?
<hal23456> and can I run yum again to get back to my current version?
<range> Yes, it works on the same rpm database. And it will upgrade them again on the next run of "yum update".
<bleve> holy shit.
Previous Page Next Page