[vox-tech] smtp question - blocked ip
can someone give me a more useful description of the problem here? who is blocking whom? it sounds like my MTA rejected sending email to netease, but ORDB and tcp wrappers for exim (which i use) should block incoming mail from spammers, not outgoing mail to spammers. at least, i'm pretty sure about that... pete sorry for terse message, but i'm still on a 14.4. - Forwarded message from Mail Delivery System [EMAIL PROTECTED] - From: Mail Delivery System [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Mail delivery failed: returning message to sender Date: Fri, 03 Jan 2003 08:42:07 -0800 This message was created automatically by mail delivery software (Exim). A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed: [EMAIL PROTECTED] SMTP error from remote mailer after RCPT TO:[EMAIL PROTECTED]: host mx02.netease.net [64.7.232.14]: 554 adsl-64-164-47-8.dsl.scrm01.pacbell.net[64.164.47.8]: Client host rejected: ACL IP Blocked; (5.7.1) Policy Violation 1205 ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech
RE: [vox-tech] smtp question - blocked ip
The reciever is setup to use a block list by ip address. So, lookup your MX and/or IP Address in a lookup site. For all potential email block/spam problems, I turn to www.dnsstuff.com The MX for dirac.org is 'mail.dirac.org' The IP is 64.164.47.8' Looking up the IP Address at DNSStuff gets you http://www.dnsstuff.com/tools/ip4r.ch?ip=64.164.47.8 Your IP is listed in spambag.org's email blocklist http://www.spambag.org/cgi-bin/spambag?mailfrom=pacbell Pete, you spammer you. :) j/k Best of luck getting off of it seeing as it is a PacBell IP netblock. Your best hope is if 'netease.net' can whitelist your ip address. -sp -Original Message- From: Peter Jay Salzman [mailto:[EMAIL PROTECTED]] Sent: Friday, January 03, 2003 8:51 AM To: [EMAIL PROTECTED] Subject: [vox-tech] smtp question - blocked ip can someone give me a more useful description of the problem here? who is blocking whom? it sounds like my MTA rejected sending email to netease, but ORDB and tcp wrappers for exim (which i use) should block incoming mail from spammers, not outgoing mail to spammers. at least, i'm pretty sure about that... pete sorry for terse message, but i'm still on a 14.4. - Forwarded message from Mail Delivery System [EMAIL PROTECTED] - From: Mail Delivery System [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Mail delivery failed: returning message to sender Date: Fri, 03 Jan 2003 08:42:07 -0800 This message was created automatically by mail delivery software (Exim). A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed: [EMAIL PROTECTED] SMTP error from remote mailer after RCPT TO:[EMAIL PROTECTED]: host mx02.netease.net [64.7.232.14]: 554 adsl-64-164-47-8.dsl.scrm01.pacbell.net[64.164.47.8]: Client host rejected: ACL IP Blocked; (5.7.1) Policy Violation 1205 ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech
Re: [vox-tech] smtp question - blocked ip
---ORIGINAL MESSAGE--- Date: Fri, 3 Jan 2003 08:50:33 -0800 To: [EMAIL PROTECTED] From: Peter Jay Salzman [EMAIL PROTECTED] Subject: [vox-tech] smtp question - blocked ip Reply-To: [EMAIL PROTECTED] can someone give me a more useful description of the problem here? [SNIP] - Forwarded message from Mail Delivery System [EMAIL PROTECTED] - From: Mail Delivery System [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Mail delivery failed: returning message to sender Date: Fri, 03 Jan 2003 08:42:07 -0800 This message was created automatically by mail delivery software (Exim). A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed: [EMAIL PROTECTED] SMTP error from remote mailer after RCPT TO:[EMAIL PROTECTED]: host mx02.netease.net [64.7.232.14]: 554 adsl-64-164-47-8.dsl.scrm01.pacbell.net[64.164.47.8]: Client host rejected: ACL IP Blocked; (5.7.1) Policy Violation 1205 Your MTA tried to make an SMTP connection to theirs, and after sending the RCPT TO: line, it recieved back a status message from the server starting with 554 adsl... and ending with Policy Violation 1205 In other words, your MTA is passing on an error message from the remote server. Judging from what the error message said, perhaps they think you're a spammer. ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech
Re: [vox-tech] smtp question - blocked ip
They blacklisted Pac Bell? Now there's a nice example of spitting into the wind. :-) -- Rod http://www.sunsetsystems.com/ On Friday 03 January 2003 09:15 am, Steven Peck wrote: The reciever is setup to use a block list by ip address. So, lookup your MX and/or IP Address in a lookup site. For all potential email block/spam problems, I turn to www.dnsstuff.com The MX for dirac.org is 'mail.dirac.org' The IP is 64.164.47.8' Looking up the IP Address at DNSStuff gets you http://www.dnsstuff.com/tools/ip4r.ch?ip=64.164.47.8 Your IP is listed in spambag.org's email blocklist http://www.spambag.org/cgi-bin/spambag?mailfrom=pacbell Pete, you spammer you. :) j/k Best of luck getting off of it seeing as it is a PacBell IP netblock. Your best hope is if 'netease.net' can whitelist your ip address. -sp -Original Message- From: Peter Jay Salzman [mailto:[EMAIL PROTECTED]] Sent: Friday, January 03, 2003 8:51 AM To: [EMAIL PROTECTED] Subject: [vox-tech] smtp question - blocked ip can someone give me a more useful description of the problem here? who is blocking whom? it sounds like my MTA rejected sending email to netease, but ORDB and tcp wrappers for exim (which i use) should block incoming mail from spammers, not outgoing mail to spammers. at least, i'm pretty sure about that... pete sorry for terse message, but i'm still on a 14.4. - Forwarded message from Mail Delivery System [EMAIL PROTECTED] - From: Mail Delivery System [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Mail delivery failed: returning message to sender Date: Fri, 03 Jan 2003 08:42:07 -0800 This message was created automatically by mail delivery software (Exim). A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed: [EMAIL PROTECTED] SMTP error from remote mailer after RCPT TO:[EMAIL PROTECTED]: host mx02.netease.net [64.7.232.14]: 554 adsl-64-164-47-8.dsl.scrm01.pacbell.net[64.164.47.8]: Client host rejected: ACL IP Blocked; (5.7.1) Policy Violation 1205 ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech
RE: [vox-tech] smtp question - blocked ip
Yes well, it's enough to prevent Pete from emailing out. I like DNSStuff.com, it's a great resource. Spamhaus blocked Pacbell DSL ip addresses. Evidently they felt that PacBell has been ignoring there complaints regarding a few persistent spammers. If I thought I could get away with it here at work, I would probably block PacBell DSL too. I got 100,000 SPAM messages through my system at work over New Years Day from a PacBell dsl ip address. I average 150,000-200,000 a week from various open relays abroad, but the guy screws up periodically and leaves enough info to trace him to a PacBell ip address on occasion. It changes so he's probably pppoe. As we add reduncy to entry points on our email system and expand the scope to the Enterprise, I will prbably see a dramatic increase. The sad part is, a lot of it is to non existant email addresses. SO not only is the spammer irratating me, he is ripping off his customer. sigh -sp -Original Message- From: Rod Roark [mailto:[EMAIL PROTECTED]] Sent: Friday, January 03, 2003 9:35 AM To: [EMAIL PROTECTED] Subject: Re: [vox-tech] smtp question - blocked ip They blacklisted Pac Bell? Now there's a nice example of spitting into the wind. :-) -- Rod http://www.sunsetsystems.com/ On Friday 03 January 2003 09:15 am, Steven Peck wrote: The reciever is setup to use a block list by ip address. So, lookup your MX and/or IP Address in a lookup site. For all potential email block/spam problems, I turn to www.dnsstuff.com The MX for dirac.org is 'mail.dirac.org' The IP is 64.164.47.8' Looking up the IP Address at DNSStuff gets you http://www.dnsstuff.com/tools/ip4r.ch?ip=64.164.47.8 Your IP is listed in spambag.org's email blocklist http://www.spambag.org/cgi-bin/spambag?mailfrom=pacbell Pete, you spammer you. :) j/k Best of luck getting off of it seeing as it is a PacBell IP netblock. Your best hope is if 'netease.net' can whitelist your ip address. -sp -Original Message- From: Peter Jay Salzman [mailto:[EMAIL PROTECTED]] Sent: Friday, January 03, 2003 8:51 AM To: [EMAIL PROTECTED] Subject: [vox-tech] smtp question - blocked ip can someone give me a more useful description of the problem here? who is blocking whom? it sounds like my MTA rejected sending email to netease, but ORDB and tcp wrappers for exim (which i use) should block incoming mail from spammers, not outgoing mail to spammers. at least, i'm pretty sure about that... pete sorry for terse message, but i'm still on a 14.4. - Forwarded message from Mail Delivery System [EMAIL PROTECTED] - From: Mail Delivery System [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Mail delivery failed: returning message to sender Date: Fri, 03 Jan 2003 08:42:07 -0800 This message was created automatically by mail delivery software (Exim). A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed: [EMAIL PROTECTED] SMTP error from remote mailer after RCPT TO:[EMAIL PROTECTED]: host mx02.netease.net [64.7.232.14]: 554 adsl-64-164-47-8.dsl.scrm01.pacbell.net[64.164.47.8]: Client host rejected: ACL IP Blocked; (5.7.1) Policy Violation 1205 ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech
RE: [vox-tech] smtp question - blocked ip
Hm, my messages seem to be coming through all right... At 09:49 AM 1/3/2003, you wrote: Yes well, it's enough to prevent Pete from emailing out. I like DNSStuff.com, it's a great resource. Spamhaus blocked Pacbell DSL ip addresses. Evidently they felt that PacBell has been ignoring there complaints regarding a few persistent spammers. If I thought I could get away with it here at work, I would probably block PacBell DSL too. I got 100,000 SPAM messages through my system at work over New Years Day from a PacBell dsl ip address. I average 150,000-200,000 a week from various open relays abroad, but the guy screws up periodically and leaves enough info to trace him to a PacBell ip address on occasion. It changes so he's probably pppoe. As we add reduncy to entry points on our email system and expand the scope to the Enterprise, I will prbably see a dramatic increase. The sad part is, a lot of it is to non existant email addresses. SO not only is the spammer irratating me, he is ripping off his customer. sigh -sp -Original Message- From: Rod Roark [mailto:[EMAIL PROTECTED]] Sent: Friday, January 03, 2003 9:35 AM To: [EMAIL PROTECTED] Subject: Re: [vox-tech] smtp question - blocked ip They blacklisted Pac Bell? Now there's a nice example of spitting into the wind. :-) -- Rod http://www.sunsetsystems.com/ On Friday 03 January 2003 09:15 am, Steven Peck wrote: The reciever is setup to use a block list by ip address. So, lookup your MX and/or IP Address in a lookup site. For all potential email block/spam problems, I turn to www.dnsstuff.com The MX for dirac.org is 'mail.dirac.org' The IP is 64.164.47.8' Looking up the IP Address at DNSStuff gets you http://www.dnsstuff.com/tools/ip4r.ch?ip=64.164.47.8 Your IP is listed in spambag.org's email blocklist http://www.spambag.org/cgi-bin/spambag?mailfrom=pacbell Pete, you spammer you. :) j/k Best of luck getting off of it seeing as it is a PacBell IP netblock. Your best hope is if 'netease.net' can whitelist your ip address. -sp -Original Message- From: Peter Jay Salzman [mailto:[EMAIL PROTECTED]] Sent: Friday, January 03, 2003 8:51 AM To: [EMAIL PROTECTED] Subject: [vox-tech] smtp question - blocked ip can someone give me a more useful description of the problem here? who is blocking whom? it sounds like my MTA rejected sending email to netease, but ORDB and tcp wrappers for exim (which i use) should block incoming mail from spammers, not outgoing mail to spammers. at least, i'm pretty sure about that... pete sorry for terse message, but i'm still on a 14.4. - Forwarded message from Mail Delivery System [EMAIL PROTECTED] - From: Mail Delivery System [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Mail delivery failed: returning message to sender Date: Fri, 03 Jan 2003 08:42:07 -0800 This message was created automatically by mail delivery software (Exim). A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed: [EMAIL PROTECTED] SMTP error from remote mailer after RCPT TO:[EMAIL PROTECTED]: host mx02.netease.net [64.7.232.14]: 554 adsl-64-164-47-8.dsl.scrm01.pacbell.net[64.164.47.8]: Client host rejected: ACL IP Blocked; (5.7.1) Policy Violation 1205 ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech Sliante, Richard S. Crawford http://www.mossroot.com AIM: Buffalo2K ICQ: 11646404 Y!: rscrawford MSN: [EMAIL PROTECTED] It is only with the heart that we see rightly; what is essential is invisible to the eye. --Antoine de Saint Exupéry Push the button, Max! ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech
Re: [vox-tech] smtp question - blocked ip
On Fri, Jan 03, 2003 at 09:49:24AM -0800, Steven Peck wrote: will prbably see a dramatic increase. The sad part is, a lot of it is to non existant email addresses. SO not only is the spammer irratating me, he is ripping off his customer. So install a bounce handler that rejects originating IP's into your system. Set it to have a bounce/delivered ratio low enough that they only get 100 or so emails through per ip they abuse. I've recently set something similar to this up and it's all but stopped stupid spammers cold. -- Ted Deppner http://www.psyber.com/~ted/ ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech
RE: [vox-tech] smtp question - blocked ip
ummm...email at work is MS Exchange and that works well enough protected by an SMTP relay on the DMZ. Existing Enterprise smtp relay entry point is also a Win32 solution that is a cheap (cheap as in piece of crap) inflexible one at that. A Linux solution using Postfix or Sendmail has been proposed but is unlikely to be approved. It is still under review at this point. My existing SMTP relay is crap. -sp -Original Message- From: Ted Deppner [mailto:[EMAIL PROTECTED]] Sent: Friday, January 03, 2003 10:00 AM To: [EMAIL PROTECTED] Subject: Re: [vox-tech] smtp question - blocked ip On Fri, Jan 03, 2003 at 09:49:24AM -0800, Steven Peck wrote: will prbably see a dramatic increase. The sad part is, a lot of it is to non existant email addresses. SO not only is the spammer irratating me, he is ripping off his customer. So install a bounce handler that rejects originating IP's into your system. Set it to have a bounce/delivered ratio low enough that they only get 100 or so emails through per ip they abuse. I've recently set something similar to this up and it's all but stopped stupid spammers cold. -- Ted Deppner http://www.psyber.com/~ted/ ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech
RE: [vox-tech] smtp question - blocked ip
sorry, not spamhaus, spamblock. -Original Message- From: Richard S. Crawford [mailto:[EMAIL PROTECTED]] Sent: Friday, January 03, 2003 9:57 AM To: [EMAIL PROTECTED] Subject: RE: [vox-tech] smtp question - blocked ip Hm, my messages seem to be coming through all right... At 09:49 AM 1/3/2003, you wrote: Yes well, it's enough to prevent Pete from emailing out. I like DNSStuff.com, it's a great resource. Spamhaus blocked Pacbell DSL ip addresses. Evidently they felt that PacBell has been ignoring there complaints regarding a few persistent spammers. If I thought I could get away with it here at work, I would probably block PacBell DSL too. I got 100,000 SPAM messages through my system at work over New Years Day from a PacBell dsl ip address. I average 150,000-200,000 a week from various open relays abroad, but the guy screws up periodically and leaves enough info to trace him to a PacBell ip address on occasion. It changes so he's probably pppoe. As we add reduncy to entry points on our email system and expand the scope to the Enterprise, I will prbably see a dramatic increase. The sad part is, a lot of it is to non existant email addresses. SO not only is the spammer irratating me, he is ripping off his customer. sigh -sp -Original Message- From: Rod Roark [mailto:[EMAIL PROTECTED]] Sent: Friday, January 03, 2003 9:35 AM To: [EMAIL PROTECTED] Subject: Re: [vox-tech] smtp question - blocked ip They blacklisted Pac Bell? Now there's a nice example of spitting into the wind. :-) -- Rod http://www.sunsetsystems.com/ On Friday 03 January 2003 09:15 am, Steven Peck wrote: The reciever is setup to use a block list by ip address. So, lookup your MX and/or IP Address in a lookup site. For all potential email block/spam problems, I turn to www.dnsstuff.com The MX for dirac.org is 'mail.dirac.org' The IP is 64.164.47.8' Looking up the IP Address at DNSStuff gets you http://www.dnsstuff.com/tools/ip4r.ch?ip=64.164.47.8 Your IP is listed in spambag.org's email blocklist http://www.spambag.org/cgi-bin/spambag?mailfrom=pacbell Pete, you spammer you. :) j/k Best of luck getting off of it seeing as it is a PacBell IP netblock. Your best hope is if 'netease.net' can whitelist your ip address. -sp -Original Message- From: Peter Jay Salzman [mailto:[EMAIL PROTECTED]] Sent: Friday, January 03, 2003 8:51 AM To: [EMAIL PROTECTED] Subject: [vox-tech] smtp question - blocked ip can someone give me a more useful description of the problem here? who is blocking whom? it sounds like my MTA rejected sending email to netease, but ORDB and tcp wrappers for exim (which i use) should block incoming mail from spammers, not outgoing mail to spammers. at least, i'm pretty sure about that... pete sorry for terse message, but i'm still on a 14.4. - Forwarded message from Mail Delivery System [EMAIL PROTECTED] - From: Mail Delivery System [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Mail delivery failed: returning message to sender Date: Fri, 03 Jan 2003 08:42:07 -0800 This message was created automatically by mail delivery software (Exim). A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed: [EMAIL PROTECTED] SMTP error from remote mailer after RCPT TO:[EMAIL PROTECTED]: host mx02.netease.net [64.7.232.14]: 554 adsl-64-164-47-8.dsl.scrm01.pacbell.net[64.164.47.8]: Client host rejected: ACL IP Blocked; (5.7.1) Policy Violation 1205 ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech Sliante, Richard S. Crawford http://www.mossroot.com AIM: Buffalo2K ICQ: 11646404 Y!: rscrawford MSN: [EMAIL PROTECTED] It is only with the heart that we see rightly; what is essential is invisible to the eye. --Antoine de Saint Exupéry Push the button, Max! ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech
Re: [vox-tech] Segmentation Fault with RPM --rebuilddb
oh well, I thought that there might be something to the red-carpet rpm database vs the up2date rpm database. -- Andy --- Richard Crawford [EMAIL PROTECTED] wrote: I do indeed have Red Carpet on my system. I'm poking around Ximian's knowledge base now. I have a feeling it might have something to do with the python-popt packages. I dunno; all I remember is an error running Anaconda that related to python in some way (I was not able to save that error message, dammit). On Thu, 2003-01-02 at 18:29, andy wergedal wrote: Have you installed red-carpet? -- Andy --- Richard Crawford [EMAIL PROTECTED] wrote: I believe I've narrowed the problem down to some ugly Ximian packages that are on my system (I love Evolution, but I am seriously questioning my wisdom in putting the entire Ximian GNOME desktop onto my computer). I communicated with a fellow at Ximian who suggests downgrading all of my Ximian packages, being especially careful with glibc, and doing a package-by-package upgrade of the RPM's on my system. Grumble. I wonder if it would be easier to zark my Linux installation as it is, tarring up my home directory into my data partition, and reinstalling RH8.0 from scratch? Opinions? Suggestions? Advice? Offers to come and do it for me (newbie fear setting in -- I can handle most kernel panics and just about everything else that comes up on my system pretty much on my own now, thanks to the extraordinary patience of my brother-in-law and this awesome LUG, but OS installs always intimidate the bejeebers out of me, even when I'm just doing a Windows install)? Richard On Thu, 2003-01-02 at 13:53, Richard Crawford wrote: On Thu, 2003-01-02 at 11:58, ME wrote: Fail after a pwrite? Hmm. Would you mind running this again, but instead try: # strace -f rpm --rebuilddb ? The -f also does the strace on child processes spawned by the first. I am betting that rpm --rebuilddb actually calls a different program that is segfaulting and the strace is not contintuing to the next app being called. (Just guessing) If the output of the lines just preceeding the SIGSEGV is the same, you dont need to paste it in again, just let us know. If the output leading up to the Segfault is different, could you include the new run/output like you did this time? :-) I ran, # strace -f rpm --rebuilddb and got exactly the same output. Eerie. I should point out that other functions of rpm (-i, -e, -qa, etc.) function normally. It's when I run it with --rebuilddb that it bombs. On the topic of time. After you run the program, does it immediately return the message segfault or does it take a while and occur after lots of disk activity? It's immediate. There's no hard drive activity at all. -- Slainte, Richard S. Crawford mailto:[EMAIL PROTECTED] http://www.mossroot.com AIM: Buffalo2K ICQ: 11646404 Yahoo!: rscrawford MSN: [EMAIL PROTECTED] It is only with the heart that we see rightly; what is essential is invisible to the eye. --Antoine de Saint Exupery vi vi vi - the editor of the beast ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech __ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech -- Slainte, Richard S. Crawford mailto:[EMAIL PROTECTED]http://www.mossroot.com AIM: Buffalo2K ICQ: 11646404 Yahoo!: rscrawford MSN: [EMAIL PROTECTED] It is only with the heart that we see rightly; what is essential is invisible to the eye. --Antoine de Saint Exupery vi vi vi - the editor of the beast ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech __ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech
Re: [vox-tech] Segmentation Fault with RPM --rebuilddb
Sorry to re-note this, but did you try the suggestion made by iCharles Polisher/i (One of the things I mentioned was a possible file system problem with files, permissions, etc. A problem with these files could be it. If this suggestion clobbers the old db files which will be created again anyway, this may be the solution you were looking for.) Instead of rm you may want to consider just mv the files to /tmp or another location so as to no destroy them. Then you could mv them back and not lose data. ( On Thu, Jan 02, 2003 at 12:28:57AM -0800, Richard Crawford wrote: Trying to get my system ready for upgrading to RH8, I decided to run rpm --rebuilddb on my system. I got Segmentation fault. What does this mean? How can I repair the fault? -- Slainte, Richard S. Crawford Try: rm -f /var/lib/rpm/__db* That ought to do the trick. ) Original post: http://lugod.org/mailinglists/archives/vox-tech/2003-01/msg00017.html -ME -- -BEGIN GEEK CODE BLOCK- Version: 3.12 GCS/CM$/IT$/LS$/S/O$ !d--( ) !s !a (-) C $() U$( $) P $ L $( ) E W $( ) N o K w $ O-@ M $ V-$- !PS !PE Y PGP t@-( ) 5 @ X@ R- tv- b DID G--@ eh( ) r*? z? --END GEEK CODE BLOCK-- decode: http://www.ebb.org/ungeek/ about: http://www.geekcode.com/geek.html Campus IT(/OS Security): Operating Systems Support Specialist Assistant ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech
Re: [vox-tech] Segmentation Fault with RPM --rebuilddb
I did try it. No luck. *grumble* At 11:24 AM 1/3/2003, you wrote: Sorry to re-note this, but did you try the suggestion made by iCharles Polisher/i (One of the things I mentioned was a possible file system problem with files, permissions, etc. A problem with these files could be it. If this suggestion clobbers the old db files which will be created again anyway, this may be the solution you were looking for.) Instead of rm you may want to consider just mv the files to /tmp or another location so as to no destroy them. Then you could mv them back and not lose data. ( On Thu, Jan 02, 2003 at 12:28:57AM -0800, Richard Crawford wrote: Trying to get my system ready for upgrading to RH8, I decided to run rpm --rebuilddb on my system. I got Segmentation fault. What does this mean? How can I repair the fault? -- Slainte, Richard S. Crawford Try: rm -f /var/lib/rpm/__db* That ought to do the trick. ) Original post: http://lugod.org/mailinglists/archives/vox-tech/2003-01/msg00017.html -ME -- -BEGIN GEEK CODE BLOCK- Version: 3.12 GCS/CM$/IT$/LS$/S/O$ !d--( ) !s !a (-) C $() U$( $) P $ L $( ) E W $( ) N o K w $ O-@ M $ V-$- !PS !PE Y PGP t@-( ) 5 @ X@ R- tv- b DID G--@ eh( ) r*? z? --END GEEK CODE BLOCK-- decode: http://www.ebb.org/ungeek/ about: http://www.geekcode.com/geek.html Campus IT(/OS Security): Operating Systems Support Specialist Assistant ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech Sliante, Richard S. Crawford http://www.mossroot.com AIM: Buffalo2K ICQ: 11646404 Y!: rscrawford MSN: [EMAIL PROTECTED] It is only with the heart that we see rightly; what is essential is invisible to the eye. --Antoine de Saint Exupéry Push the button, Max! ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech
Re: [vox-tech] Segmentation Fault with RPM --rebuilddb
(Sorry, trying to get caught up on e-mail again) Richard Crawford said: On Thu, 2003-01-02 at 11:58, ME wrote: Fail after a pwrite? Hmm. Would you mind running this again, but instead try: # strace -f rpm --rebuilddb ? The -f also does the strace on child processes spawned by the first. I am betting that rpm --rebuilddb actually calls a different program that is segfaulting and the strace is not contintuing to the next app being called. (Just guessing) If the output of the lines just preceeding the SIGSEGV is the same, you dont need to paste it in again, just let us know. If the output leading up to the Segfault is different, could you include the new run/output like you did this time? :-) I ran, # strace -f rpm --rebuilddb and got exactly the same output. Eerie. I should point out that other functions of rpm (-i, -e, -qa, etc.) function normally. It's when I run it with --rebuilddb that it bombs. Well, assuming we are seeing sync-ed output, then there is a problem with the program as it is writing out its results. (more) On the topic of time. After you run the program, does it immediately return the message segfault or does it take a while and occur after lots of disk activity? It's immediate. There's no hard drive activity at all. Since it is immediate, and we see no other items in the trace, I would expect it is not a path issue with symlinks. It is sounding more and more like a file problem. Like there is an attempt to open a file (earlier) that is assumed to allready be open (no checking) and now, as we are getting to writing to the file descriptor, it is suddenly found to not be valid, or ? I guess it could be cause by a filesystem problem at the point on disk where one of the files it uses is stored (seems unlikely) The suggestion made by Charles Polisher is a good one, and puts you on what I would expect to be a good track. Try to find files used by this process of rpm --rebuilddb and move them (backup) to a different location. Then re-run the program to see if it segfaults. -ME -- -BEGIN GEEK CODE BLOCK- Version: 3.12 GCS/CM$/IT$/LS$/S/O$ !d--( ) !s !a (-) C $() U$( $) P $ L $( ) E W $( ) N o K w $ O-@ M $ V-$- !PS !PE Y PGP t@-( ) 5 @ X@ R- tv- b DID G--@ eh( ) r*? z? --END GEEK CODE BLOCK-- decode: http://www.ebb.org/ungeek/ about: http://www.geekcode.com/geek.html Campus IT(/OS Security): Operating Systems Support Specialist Assistant ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech
Re: [vox-tech] Segmentation Fault with RPM --rebuilddb
Some more odd questions: Are all of your filesystems mounts (rw)? (just run mount to see) Before the next time you run # rpm --rebuilddb Could you check the man page for it? Is there a way to increase the level of verbosity? Sometimes, apps will allow for a number like -d 100 to set debug level to 100 and show lots of extra information. Some will use -v or -vv or -vvv or -vvv... with more v being more verbose... Find the highest level of verbosity it can use, and specify that on the command line the next time you run it, like: # rpm --rebuilddb -v if it accepts that kind of format. Perhaps it will tell us Thanks! -ME Richard S. Crawford said: I did try it. No luck. *grumble* At 11:24 AM 1/3/2003, you wrote: Sorry to re-note this, but did you try the suggestion made by iCharles Polisher/i (One of the things I mentioned was a possible file system problem with files, permissions, etc. A problem with these files could be it. If this suggestion clobbers the old db files which will be created again anyway, this may be the solution you were looking for.) Instead of rm you may want to consider just mv the files to /tmp or another location so as to no destroy them. Then you could mv them back and not lose data. ( On Thu, Jan 02, 2003 at 12:28:57AM -0800, Richard Crawford wrote: Trying to get my system ready for upgrading to RH8, I decided to run rpm --rebuilddb on my system. I got Segmentation fault. What does this mean? How can I repair the fault? -- Slainte, Richard S. Crawford Try: rm -f /var/lib/rpm/__db* That ought to do the trick. ) Original post: http://lugod.org/mailinglists/archives/vox-tech/2003-01/msg00017.html -ME -- -BEGIN GEEK CODE BLOCK- Version: 3.12 GCS/CM$/IT$/LS$/S/O$ !d--( ) !s !a (-) C $() U$( $) P $ L $( ) E W $( ) N o K w $ O-@ M $ V-$- !PS !PE Y PGP t@-( ) 5 @ X@ R- tv- b DID G--@ eh( ) r*? z? --END GEEK CODE BLOCK-- decode: http://www.ebb.org/ungeek/ about: http://www.geekcode.com/geek.html Campus IT(/OS Security): Operating Systems Support Specialist Assistant ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech Sliante, Richard S. Crawford http://www.mossroot.com AIM: Buffalo2K ICQ: 11646404 Y!: rscrawford MSN: [EMAIL PROTECTED] It is only with the heart that we see rightly; what is essential is invisible to the eye. --Antoine de Saint Exupéry Push the button, Max! ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech
Re: [vox-tech] Segmentation Fault with RPM --rebuilddb
On Fri, 2003-01-03 at 11:56, ME wrote: Some more odd questions: Are all of your filesystems mounts (rw)? (just run mount to see) Ayuh. Every single one. Before the next time you run # rpm --rebuilddb Could you check the man page for it? Is there a way to increase the level of verbosity? Sometimes, apps will allow for a number like -d 100 to set debug level to 100 and show lots of extra information. Some will use -v or -vv or -vvv or -vvv... with more v being more verbose... Find the highest level of verbosity it can use, and specify that on the command line the next time you run it, like: # rpm --rebuilddb -v if it accepts that kind of format. Perhaps it will tell us rpm does indeed have a verbose option. Here ya go: === [root@mossroot rscrawford]# rpm --rebuilddb -vv D: rebuilding database /var/lib/rpm into /var/lib/rpmrebuilddb.1697 D: creating directory /var/lib/rpmrebuilddb.1697 D: opening old database with dbapi 3 D: opening db environment /var/lib/rpm/Packages create:mpool D: opening db index /var/lib/rpm/Packages rdonly mode=0x0 D: locked db index /var/lib/rpm/Packages D: opening new database with dbapi 3 D: opening db environment /var/lib/rpmrebuilddb.1697/Packages create:mpool D: opening db index /var/lib/rpmrebuilddb.1697/Packages create mode=0x42 D: +++ 1 libsigc++-devel-1.0.4-1.ximian.1 D: opening db environment /var/lib/rpmrebuilddb.1697/Name joinenv D: opening db index /var/lib/rpmrebuilddb.1697/Name create mode=0x42 D: adding libsigc++-devel to Name index. D: opening db environment /var/lib/rpmrebuilddb.1697/Basenames joinenv D: opening db index /var/lib/rpmrebuilddb.1697/Basenames create mode=0x42D: adding 40 entries to Basenames index. D: opening db environment /var/lib/rpmrebuilddb.1697/Group joinenv D: opening db index /var/lib/rpmrebuilddb.1697/Group create mode=0x42 D: adding Development/Libraries to Group index. D: opening db environment /var/lib/rpmrebuilddb.1697/Requirename joinenv D: opening db index /var/lib/rpmrebuilddb.1697/Requirename create mode=0x42 D: adding 4 entries to Requirename index. D: opening db environment /var/lib/rpmrebuilddb.1697/Providename joinenv D: opening db index /var/lib/rpmrebuilddb.1697/Providename create mode=0x42 D: adding 2 entries to Providename index. D: opening db environment /var/lib/rpmrebuilddb.1697/Dirnames joinenv D: opening db index /var/lib/rpmrebuilddb.1697/Dirnames create mode=0x42 D: adding 9 entries to Dirnames index. D: opening db environment /var/lib/rpmrebuilddb.1697/Requireversion joinenv D: opening db index /var/lib/rpmrebuilddb.1697/Requireversion create mode=0x42 D: adding 4 entries to Requireversion index. D: opening db environment /var/lib/rpmrebuilddb.1697/Provideversion joinenv D: opening db index /var/lib/rpmrebuilddb.1697/Provideversion create mode=0x42 D: adding 2 entries to Provideversion index. D: opening db environment /var/lib/rpmrebuilddb.1697/Installtid joinenv D: opening db index /var/lib/rpmrebuilddb.1697/Installtid create mode=0x42 D: adding 1 entries to Installtid index. D: opening db environment /var/lib/rpmrebuilddb.1697/Sigmd5 joinenv D: opening db index /var/lib/rpmrebuilddb.1697/Sigmd5 create mode=0x42 D: adding 16 entries to Sigmd5 index. Segmentation fault [root@mossroot rscrawford]# === Thanks! -ME No problem. :) -- Slainte, Richard S. Crawford mailto:[EMAIL PROTECTED] http://www.mossroot.com AIM: Buffalo2K ICQ: 11646404 Yahoo!: rscrawford MSN: [EMAIL PROTECTED] It is only with the heart that we see rightly; what is essential is invisible to the eye. --Antoine de Saint Exupery vi vi vi - the editor of the beast ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech
Re: [vox-tech] Segmentation Fault with RPM --rebuilddb
On Fri, 2003-01-03 at 11:34, ME wrote: Since it is immediate, and we see no other items in the trace, I would expect it is not a path issue with symlinks. It is sounding more and more like a file problem. Like there is an attempt to open a file (earlier) that is assumed to allready be open (no checking) and now, as we are getting to writing to the file descriptor, it is suddenly found to not be valid, or ? I guess it could be cause by a filesystem problem at the point on disk where one of the files it uses is stored (seems unlikely) That would be odd... I have seen no other indications of any problems. The suggestion made by Charles Polisher is a good one, and puts you on what I would expect to be a good track. Try to find files used by this process of rpm --rebuilddb and move them (backup) to a different location. Then re-run the program to see if it segfaults. I removed all of the /var/lib/rpm/__db* files, and moved all of the files under /var/lib/rpmrebuilddb.* directories to a backup directory. Still got a segmentation fault. I also tried moving all files in /var/lib/rpm to a backup directory, and got all sorts of interesting errors... before realizing that was the wrong thing to do and I replaced the files. ;-) -- Slainte, Richard S. Crawford mailto:[EMAIL PROTECTED] http://www.mossroot.com AIM: Buffalo2K ICQ: 11646404 Yahoo!: rscrawford MSN: [EMAIL PROTECTED] It is only with the heart that we see rightly; what is essential is invisible to the eye. --Antoine de Saint Exupery vi vi vi - the editor of the beast ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech
Re: [vox-tech] Segmentation Fault with RPM --rebuilddb
Richard Crawford said: rpm does indeed have a verbose option. Here ya go: === [root@mossroot rscrawford]# rpm --rebuilddb -vv D: rebuilding database /var/lib/rpm into /var/lib/rpmrebuilddb.1697 D: creating directory /var/lib/rpmrebuilddb.1697 D: opening old database with dbapi 3 D: opening db environment /var/lib/rpm/Packages create:mpool D: opening db index /var/lib/rpm/Packages rdonly mode=0x0 D: locked db index /var/lib/rpm/Packages D: opening new database with dbapi 3 D: opening db environment /var/lib/rpmrebuilddb.1697/Packages create:mpool D: opening db index /var/lib/rpmrebuilddb.1697/Packages create mode=0x42 D: +++ 1 libsigc++-devel-1.0.4-1.ximian.1 D: opening db environment /var/lib/rpmrebuilddb.1697/Name joinenv D: opening db index /var/lib/rpmrebuilddb.1697/Name create mode=0x42 D: adding libsigc++-devel to Name index. D: opening db environment /var/lib/rpmrebuilddb.1697/Basenames joinenv D: opening db index /var/lib/rpmrebuilddb.1697/Basenames create mode=0x42D: adding 40 entries to Basenames index. D: opening db environment /var/lib/rpmrebuilddb.1697/Group joinenv D: opening db index /var/lib/rpmrebuilddb.1697/Group create mode=0x42 D: adding Development/Libraries to Group index. D: opening db environment /var/lib/rpmrebuilddb.1697/Requirename joinenv D: opening db index /var/lib/rpmrebuilddb.1697/Requirename create mode=0x42 D: adding 4 entries to Requirename index. D: opening db environment /var/lib/rpmrebuilddb.1697/Providename joinenv D: opening db index /var/lib/rpmrebuilddb.1697/Providename create mode=0x42 D: adding 2 entries to Providename index. D: opening db environment /var/lib/rpmrebuilddb.1697/Dirnames joinenv D: opening db index /var/lib/rpmrebuilddb.1697/Dirnames create mode=0x42 D: adding 9 entries to Dirnames index. D: opening db environment /var/lib/rpmrebuilddb.1697/Requireversion joinenv D: opening db index /var/lib/rpmrebuilddb.1697/Requireversion create mode=0x42 D: adding 4 entries to Requireversion index. D: opening db environment /var/lib/rpmrebuilddb.1697/Provideversion joinenv D: opening db index /var/lib/rpmrebuilddb.1697/Provideversion create mode=0x42 D: adding 2 entries to Provideversion index. D: opening db environment /var/lib/rpmrebuilddb.1697/Installtid joinenv D: opening db index /var/lib/rpmrebuilddb.1697/Installtid create mode=0x42 D: adding 1 entries to Installtid index. D: opening db environment /var/lib/rpmrebuilddb.1697/Sigmd5 joinenv D: opening db index /var/lib/rpmrebuilddb.1697/Sigmd5 create mode=0x42 D: adding 16 entries to Sigmd5 index. Segmentation fault Perhaps others can see where I am going here, as I am not a RedHat guy, and help with methods to test it or make it work. It looks like it is trying to read what it can from your old rpm Packages list as stored in /var/lib/rpm/ and put a new copy into /var/lib/rpmrebuild.1697/ and then, if it comepletes, then replace the old one with this new one with a simple move. It appears to choke when it is building an MD5 Checksum (Sig) from the old data. Doing this on a write seems odd. The file appears to be open, and ready to accept data. It is possible that there is a field in one of the old DB's that is used for MD5 Checksum, and it has too many characters for a valid MD5. Another variable used as a ref, or pointer (perhaps) is being overwritten by the extra data and then a deref of the variable overwritten leads to a deref of an address not available. (Tihs is just a guess.) If we assume this is correct, then the next step would be to inspect the data being read for the Sigmd5 portion of this. Is there any way to examine the Packages files that it is reading from, to see if the rpm headers being read have an invalid MD5 field, or value? Is Sigmd5 actually a package, and not a section of the DB? If so, can it be upgraded? look to see if /var/lib/rpmrebuilddb.1697/Sigmd5 s still there. Is it? Is it zero length? Do you have a /var/lib/rpm/Sigmd5 file? what is its length? Do you know of any rpm applications that will check md5sums of packages and headers and verify the headers of the rpms are good ? -ME -- -BEGIN GEEK CODE BLOCK- Version: 3.12 GCS/CM$/IT$/LS$/S/O$ !d--( ) !s !a (-) C $() U$( $) P $ L $( ) E W $( ) N o K w $ O-@ M $ V-$- !PS !PE Y PGP t@-( ) 5 @ X@ R- tv- b DID G--@ eh( ) r*? z? --END GEEK CODE BLOCK-- decode: http://www.ebb.org/ungeek/ about: http://www.geekcode.com/geek.html Campus IT(/OS Security): Operating Systems Support Specialist Assistant ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech
Re: [vox-tech] Segmentation Fault with RPM --rebuilddb
I don't believe you've said what version of RedHat you're running. Also, specifically, what version of rpm are you running? rpm -q rpm would suffice. Assuming it's RedHat 7.x, see: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=73198 https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=56524 https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=78782 for clues and information. You should do a few other searches in bugzilla. The gist of these bug reports is: upgrade to rpm 4.1 and try that, re-install if you used ximian or redcarpet or some other unsupported thing, or file bug report---looks like the guy that's supporting rpm is pretty quick to respond and willing to look individually at your database. shawn. On Friday 03 January 2003 04:16 pm, Richard Crawford wrote: On Fri, 2003-01-03 at 11:34, ME wrote: Since it is immediate, and we see no other items in the trace, I would expect it is not a path issue with symlinks. It is sounding more and more like a file problem. Like there is an attempt to open a file (earlier) that is assumed to allready be open (no checking) and now, as we are getting to writing to the file descriptor, it is suddenly found to not be valid, or ? I guess it could be cause by a filesystem problem at the point on disk where one of the files it uses is stored (seems unlikely) That would be odd... I have seen no other indications of any problems. The suggestion made by Charles Polisher is a good one, and puts you on what I would expect to be a good track. Try to find files used by this process of rpm --rebuilddb and move them (backup) to a different location. Then re-run the program to see if it segfaults. I removed all of the /var/lib/rpm/__db* files, and moved all of the files under /var/lib/rpmrebuilddb.* directories to a backup directory. Still got a segmentation fault. I also tried moving all files in /var/lib/rpm to a backup directory, and got all sorts of interesting errors... before realizing that was the wrong thing to do and I replaced the files. ;-) ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech
Re: [vox-tech] Segmentation Fault with RPM --rebuilddb
Also see: http://www.rpm.org/hintskinks/repairdb/ ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech
Re: [vox-tech] Segmentation Fault with RPM --rebuilddb
lots of good tidbits and info there. On Friday 03 January 2003 09:35 pm, Charles Polisher wrote: Also see: http://www.rpm.org/hintskinks/repairdb/ ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech
