Re: FTP-SSL
Rick Moen wrote: > sftp is really an odd beast, which is part of why it's used so little. > If you can get mileage out of "many features of ssh" within it, you're > doing better than anyone else I know of. sftp is of value if only because it lets you use lftp fish:// , so you get a kick-ass ftp client interface with ssh encrypted goodness in the backend. -- see shy jo pgpLpBfP61WGt.pgp Description: PGP signature
Re: FTP-SSL
Rick Moen wrote: > sftp is really an odd beast, which is part of why it's used so little. > If you can get mileage out of "many features of ssh" within it, you're > doing better than anyone else I know of. sftp is of value if only because it lets you use lftp fish:// , so you get a kick-ass ftp client interface with ssh encrypted goodness in the backend. -- see shy jo msg08308/pgp0.pgp Description: PGP signature
Re: Bind9 stopped after 34 days of uptime
On Wed, 25 Dec 2002, J.Reilink wrote: > I've had exactly the same on our corperate primary nameserver (Slackware > with bind 9.2.1), because there was no logging I couldn't find out why > bind stopped working. Take a look at memory usage when Bind stop's working and monitor for some time how much memory Bind is using. If that amount is growing, Bind probably got a memory leak. ( isn't the first time :( ) Greetings, Richard. Paul Vixie in an interview with Sendmail.net: Now that the Internet has the full spectrum of humanity as users, the technology is showing its weakness: it was designed to be used by friendly, smart people. Spammers, as an example of a class, are neither friendly nor smart.
Re: Bind9 stopped after 34 days of uptime
On Wed, 25 Dec 2002, J.Reilink wrote: > I've had exactly the same on our corperate primary nameserver (Slackware > with bind 9.2.1), because there was no logging I couldn't find out why > bind stopped working. Take a look at memory usage when Bind stop's working and monitor for some time how much memory Bind is using. If that amount is growing, Bind probably got a memory leak. ( isn't the first time :( ) Greetings, Richard. Paul Vixie in an interview with Sendmail.net: Now that the Internet has the full spectrum of humanity as users, the technology is showing its weakness: it was designed to be used by friendly, smart people. Spammers, as an example of a class, are neither friendly nor smart. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bind9 stopped after 34 days of uptime
- Original message - On Wed, 25 Dec 2002 15:03:19 +0100 InfoEmergencias - Luis Gomez <[EMAIL PROTECTED]> wrote in message<[EMAIL PROTECTED]>: > Hi all > > I've been running my company's server with Linux in the same computer > for about six months. Tonight, when I arrived home (my company is in > my house) at about 6 a.m., I noticed I could not browse any website, > and noticed that the DNS server (bind 9) was stopped. It was up when I > left at 15.30h. I restarted the service and everything is OK now. > I've had exactly the same on our corperate primary nameserver (Slackware with bind 9.2.1), because there was no logging I couldn't find out why bind stopped working. Paranoid: Perhaps there is something with bind 9 we don't know about (yet...)? :-) No, I honestly don't know yet. > Well, if anyone has ever had a problem like this and can lend me a > hand or give me some advice, I'll be very happy to hear you :-) > Can't help you on this one right now, but I certainly will watch this thread closely :) Merry Christmas everyone. Regards, Jan -- /"\ ASCII Ribbon Campaign \ / No HTML in mail or news! X / \ DSINet: http://www.dsinet.org
Re: Bind9 stopped after 34 days of uptime
Hi, Domonkos Thank you very much for your advice. However, I think this is not my case: [EMAIL PROTECTED]:~$ free total used free sharedbuffers cached Mem:248880 243912 4968 0 3744 155060 -/+ buffers/cache: 85108 163772 Swap: 530136 2680 527456 Also, my logfiles ARE rotating. However, I guess I'll wait until bind fails again, and then (before restartint it) I'll try to figure out what's happening. In addition, I have just remembered that I'm running kernel 2.4.20-rc1. A big fault, mea culpa. The reason for running this kernel is that some time ago we had a lot of problems, we were using 2.4.19 and I wanted to update to a newer kernel ASAP (finally those problems were due to a faulty RAM module, and that's already solved). As soon as I can, I'll update to 2.4.20. Again, thanks a lot for your help! Regards, Pope El Mié 25 Dic 2002 15:23, escribió: > Hello, > > I have the same problem recently. I've deleted the needless users and > groups from the group and passwd files, but because of some reason the utmp > grp is needed by logrotate (why ? :)). Because of this problem, the > logrotate didn't run daily and logfiles were bigger and bigger. Some days > ago I received an alert from netsaint that my shiny new bind9 stopped > running. I started to investigate it and I was surprised that i have 2 > megabytes of free ram :/ I figured out that if some of the log files are so > big (around 100Mb) syslog-ng ate up all of my 256Mb ram. So i compresssed > those log files, restarted syslog-ng and bamm i have 181 Mb of free ram. So > you should check this as well :) > > Best Regards, > Domonkos Czinke > > > -Original Message- > From: InfoEmergencias - Luis Gomez [mailto:[EMAIL PROTECTED] > Sent: Wednesday, December 25, 2002 3:03 PM > To: Debian security > Subject: Bind9 stopped after 34 days of uptime > > > Hi all > > I've been running my company's server with Linux in the same computer for > about six months. Tonight, when I arrived home (my company is in my house) > at about 6 a.m., I noticed I could not browse any website, and noticed that > the DNS server (bind 9) was stopped. It was up when I left at 15.30h. I > restarted the service and everything is OK now. > > We currently have an uptime of 34 days, and this had never happened before. > The computer is running Woody, upgraded every night (via cron.daily). I've > been looking at my logs, trying to determine at what exact time the dns > server failed, but I cannot figure out. We never lost connection from the > Internet, as we use a secondary name server provided by our name registrant > (gandi.net), so as far as I can tell our name did not stop being resolvable > from the outside (that explains why I didn't stop receiving mails, I > think). > > Well, if anyone has ever had a problem like this and can lend me a hand or > give me some advice, I'll be very happy to hear you :-) > > TIA > > Pope -- Luis Gomez Miralles InfoEmergencias - Technical Department Phone (+34) 654 24 01 34 Fax (+34) 963 49 31 80 [EMAIL PROTECTED] PGP Public Key available at http://www.infoemergencias.com/lgomez.asc
RE: Bind9 stopped after 34 days of uptime
Hello, I have the same problem recently. I've deleted the needless users and groups from the group and passwd files, but because of some reason the utmp grp is needed by logrotate (why ? :)). Because of this problem, the logrotate didn't run daily and logfiles were bigger and bigger. Some days ago I received an alert from netsaint that my shiny new bind9 stopped running. I started to investigate it and I was surprised that i have 2 megabytes of free ram :/ I figured out that if some of the log files are so big (around 100Mb) syslog-ng ate up all of my 256Mb ram. So i compresssed those log files, restarted syslog-ng and bamm i have 181 Mb of free ram. So you should check this as well :) Best Regards, Domonkos Czinke -Original Message- From: InfoEmergencias - Luis Gomez [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 25, 2002 3:03 PM To: Debian security Subject: Bind9 stopped after 34 days of uptime Hi all I've been running my company's server with Linux in the same computer for about six months. Tonight, when I arrived home (my company is in my house) at about 6 a.m., I noticed I could not browse any website, and noticed that the DNS server (bind 9) was stopped. It was up when I left at 15.30h. I restarted the service and everything is OK now. We currently have an uptime of 34 days, and this had never happened before. The computer is running Woody, upgraded every night (via cron.daily). I've been looking at my logs, trying to determine at what exact time the dns server failed, but I cannot figure out. We never lost connection from the Internet, as we use a secondary name server provided by our name registrant (gandi.net), so as far as I can tell our name did not stop being resolvable from the outside (that explains why I didn't stop receiving mails, I think). Well, if anyone has ever had a problem like this and can lend me a hand or give me some advice, I'll be very happy to hear you :-) TIA Pope -- Luis Gomez Miralles InfoEmergencias - Technical Department Phone (+34) 654 24 01 34 Fax (+34) 963 49 31 80 [EMAIL PROTECTED] PGP Public Key available at http://www.infoemergencias.com/lgomez.asc -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bind9 stopped after 34 days of uptime
Hi all I've been running my company's server with Linux in the same computer for about six months. Tonight, when I arrived home (my company is in my house) at about 6 a.m., I noticed I could not browse any website, and noticed that the DNS server (bind 9) was stopped. It was up when I left at 15.30h. I restarted the service and everything is OK now. We currently have an uptime of 34 days, and this had never happened before. The computer is running Woody, upgraded every night (via cron.daily). I've been looking at my logs, trying to determine at what exact time the dns server failed, but I cannot figure out. We never lost connection from the Internet, as we use a secondary name server provided by our name registrant (gandi.net), so as far as I can tell our name did not stop being resolvable from the outside (that explains why I didn't stop receiving mails, I think). Well, if anyone has ever had a problem like this and can lend me a hand or give me some advice, I'll be very happy to hear you :-) TIA Pope -- Luis Gomez Miralles InfoEmergencias - Technical Department Phone (+34) 654 24 01 34 Fax (+34) 963 49 31 80 [EMAIL PROTECTED] PGP Public Key available at http://www.infoemergencias.com/lgomez.asc
Re: Bind9 stopped after 34 days of uptime
- Original message - On Wed, 25 Dec 2002 15:03:19 +0100 InfoEmergencias - Luis Gomez <[EMAIL PROTECTED]> wrote in message<[EMAIL PROTECTED]>: > Hi all > > I've been running my company's server with Linux in the same computer > for about six months. Tonight, when I arrived home (my company is in > my house) at about 6 a.m., I noticed I could not browse any website, > and noticed that the DNS server (bind 9) was stopped. It was up when I > left at 15.30h. I restarted the service and everything is OK now. > I've had exactly the same on our corperate primary nameserver (Slackware with bind 9.2.1), because there was no logging I couldn't find out why bind stopped working. Paranoid: Perhaps there is something with bind 9 we don't know about (yet...)? :-) No, I honestly don't know yet. > Well, if anyone has ever had a problem like this and can lend me a > hand or give me some advice, I'll be very happy to hear you :-) > Can't help you on this one right now, but I certainly will watch this thread closely :) Merry Christmas everyone. Regards, Jan -- /"\ ASCII Ribbon Campaign \ / No HTML in mail or news! X / \ DSINet: http://www.dsinet.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bind9 stopped after 34 days of uptime
Hi, Domonkos Thank you very much for your advice. However, I think this is not my case: pope@marianela:~$ free total used free sharedbuffers cached Mem:248880 243912 4968 0 3744 155060 -/+ buffers/cache: 85108 163772 Swap: 530136 2680 527456 Also, my logfiles ARE rotating. However, I guess I'll wait until bind fails again, and then (before restartint it) I'll try to figure out what's happening. In addition, I have just remembered that I'm running kernel 2.4.20-rc1. A big fault, mea culpa. The reason for running this kernel is that some time ago we had a lot of problems, we were using 2.4.19 and I wanted to update to a newer kernel ASAP (finally those problems were due to a faulty RAM module, and that's already solved). As soon as I can, I'll update to 2.4.20. Again, thanks a lot for your help! Regards, Pope El Mié 25 Dic 2002 15:23, escribió: > Hello, > > I have the same problem recently. I've deleted the needless users and > groups from the group and passwd files, but because of some reason the utmp > grp is needed by logrotate (why ? :)). Because of this problem, the > logrotate didn't run daily and logfiles were bigger and bigger. Some days > ago I received an alert from netsaint that my shiny new bind9 stopped > running. I started to investigate it and I was surprised that i have 2 > megabytes of free ram :/ I figured out that if some of the log files are so > big (around 100Mb) syslog-ng ate up all of my 256Mb ram. So i compresssed > those log files, restarted syslog-ng and bamm i have 181 Mb of free ram. So > you should check this as well :) > > Best Regards, > Domonkos Czinke > > > -Original Message- > From: InfoEmergencias - Luis Gomez [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, December 25, 2002 3:03 PM > To: Debian security > Subject: Bind9 stopped after 34 days of uptime > > > Hi all > > I've been running my company's server with Linux in the same computer for > about six months. Tonight, when I arrived home (my company is in my house) > at about 6 a.m., I noticed I could not browse any website, and noticed that > the DNS server (bind 9) was stopped. It was up when I left at 15.30h. I > restarted the service and everything is OK now. > > We currently have an uptime of 34 days, and this had never happened before. > The computer is running Woody, upgraded every night (via cron.daily). I've > been looking at my logs, trying to determine at what exact time the dns > server failed, but I cannot figure out. We never lost connection from the > Internet, as we use a secondary name server provided by our name registrant > (gandi.net), so as far as I can tell our name did not stop being resolvable > from the outside (that explains why I didn't stop receiving mails, I > think). > > Well, if anyone has ever had a problem like this and can lend me a hand or > give me some advice, I'll be very happy to hear you :-) > > TIA > > Pope -- Luis Gomez Miralles InfoEmergencias - Technical Department Phone (+34) 654 24 01 34 Fax (+34) 963 49 31 80 [EMAIL PROTECTED] PGP Public Key available at http://www.infoemergencias.com/lgomez.asc -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RE: Bind9 stopped after 34 days of uptime
Hello, I have the same problem recently. I've deleted the needless users and groups from the group and passwd files, but because of some reason the utmp grp is needed by logrotate (why ? :)). Because of this problem, the logrotate didn't run daily and logfiles were bigger and bigger. Some days ago I received an alert from netsaint that my shiny new bind9 stopped running. I started to investigate it and I was surprised that i have 2 megabytes of free ram :/ I figured out that if some of the log files are so big (around 100Mb) syslog-ng ate up all of my 256Mb ram. So i compresssed those log files, restarted syslog-ng and bamm i have 181 Mb of free ram. So you should check this as well :) Best Regards, Domonkos Czinke -Original Message- From: InfoEmergencias - Luis Gomez [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 25, 2002 3:03 PM To: Debian security Subject: Bind9 stopped after 34 days of uptime Hi all I've been running my company's server with Linux in the same computer for about six months. Tonight, when I arrived home (my company is in my house) at about 6 a.m., I noticed I could not browse any website, and noticed that the DNS server (bind 9) was stopped. It was up when I left at 15.30h. I restarted the service and everything is OK now. We currently have an uptime of 34 days, and this had never happened before. The computer is running Woody, upgraded every night (via cron.daily). I've been looking at my logs, trying to determine at what exact time the dns server failed, but I cannot figure out. We never lost connection from the Internet, as we use a secondary name server provided by our name registrant (gandi.net), so as far as I can tell our name did not stop being resolvable from the outside (that explains why I didn't stop receiving mails, I think). Well, if anyone has ever had a problem like this and can lend me a hand or give me some advice, I'll be very happy to hear you :-) TIA Pope -- Luis Gomez Miralles InfoEmergencias - Technical Department Phone (+34) 654 24 01 34 Fax (+34) 963 49 31 80 [EMAIL PROTECTED] PGP Public Key available at http://www.infoemergencias.com/lgomez.asc -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bind9 stopped after 34 days of uptime
Hi all I've been running my company's server with Linux in the same computer for about six months. Tonight, when I arrived home (my company is in my house) at about 6 a.m., I noticed I could not browse any website, and noticed that the DNS server (bind 9) was stopped. It was up when I left at 15.30h. I restarted the service and everything is OK now. We currently have an uptime of 34 days, and this had never happened before. The computer is running Woody, upgraded every night (via cron.daily). I've been looking at my logs, trying to determine at what exact time the dns server failed, but I cannot figure out. We never lost connection from the Internet, as we use a secondary name server provided by our name registrant (gandi.net), so as far as I can tell our name did not stop being resolvable from the outside (that explains why I didn't stop receiving mails, I think). Well, if anyone has ever had a problem like this and can lend me a hand or give me some advice, I'll be very happy to hear you :-) TIA Pope -- Luis Gomez Miralles InfoEmergencias - Technical Department Phone (+34) 654 24 01 34 Fax (+34) 963 49 31 80 [EMAIL PROTECTED] PGP Public Key available at http://www.infoemergencias.com/lgomez.asc -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
