Messages in this thread |  | | Date | Sun, 8 Dec 1996 21:03:11 -0200 (EDT) | From | Rodrigo Feher <> | Subject | Re: Exeption w/ 2.1.14 |
| |
On Sun, 8 Dec 1996, Leigh Koven wrote:
Hi Leigh,
> I had been getting Exceptions at another address (very similar to > yours)... unfortunately my logs got trimmed overnight so I lost the exact > address.... anyhow, I found downgrading back to 2.1.13 cured the problem.
Yes, I think downgrading to 2.1.13 fix the problem. I never got an exception like that under < 2.1.14. BTW, I'll take a look at the 2.1.14 patch and try to figure what's causing this strange behavior.
> P.S. I've been getting another strange error about socket destry delayed > (which I mentioned in a previous mail) with 2.1.14 also. Again, going to > 2.1.13 fixed the problem.
Got this problem some time ago, but now (2.1.14) it seens to be fixed. Look:
Nov 16 19:32:08 inward dip[76]: ip_acct failed!! Nov 16 19:57:07 inward sendmail[354]: NOQUEUE: SYSERR(isiah): opendaemonsocket: cannot bind: Address already in use Nov 16 19:57:07 inward sendmail[354]: problem creating SMTP socket Nov 16 19:57:39 inward dip[291]: >>> Line disconnected Nov 16 19:59:32 inward sendmail[555]: NOQUEUE: SYSERR(isiah): opendaemonsocket: cannot bind: Address already in use Nov 16 19:59:32 inward sendmail[555]: problem creating SMTP socket Nov 16 20:02:48 inward kernel: Socket destroy delayed (r=0 w=2304) Nov 16 20:03:18 inward last message repeated 3 times Nov 16 20:04:18 inward last message repeated 6 times
I was running a lot of "sendmail -q" to deliver queued mail. When I lost the connection (slip) from my ISP got "socket destroy...".
- rf
|  |