Re: [SLUG] error processing ndtpd .. {& rampant syslog ?}
Steve Kowalik wrote: >On Thu, 26 May 2005 16:13:10 +1200, Adam Bogacki uttered > > >>I've attached the output below. I'm also getting a lot of syslog >>messages appearing in gnome-terminal together >>with beeping and a red light flashing on the midi-tower. >> >> >> >I daresay that syslogd is badly miconfigured on your machine. With the >syslog messages going to console as wall messages, and the fact that >the command that failed is "syslog-facility set info >/var/log/ndtpd.log". > >Cheers, > > Thanks, that explains it. I thought I had fixed it (man 'psad'). I'll have to sleep on it. Adam. [EMAIL PROTECTED] -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
Re: [SLUG] error processing ndtpd .. {& rampant syslog ?}
On Thu, 26 May 2005 16:13:10 +1200, Adam Bogacki uttered >> I've attached the output below. I'm also getting a lot of syslog >> messages appearing in gnome-terminal together >> with beeping and a red light flashing on the midi-tower. >> I daresay that syslogd is badly miconfigured on your machine. With the syslog messages going to console as wall messages, and the fact that the command that failed is "syslog-facility set info /var/log/ndtpd.log". Cheers, Thanks Steve, that explains a few things. I thought I'd fixed it. For the moment I think I'll sleep on it. Adam Bogacki, [EMAIL PROTECTED] signature.asc Description: Digital signature -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
Re: [SLUG] error processing ndtpd .. {& rampant syslog ?}
On Thu, 26 May 2005 16:13:10 +1200, Adam Bogacki uttered > I've attached the output below. I'm also getting a lot of syslog > messages appearing in gnome-terminal together > with beeping and a red light flashing on the midi-tower. > I daresay that syslogd is badly miconfigured on your machine. With the syslog messages going to console as wall messages, and the fact that the command that failed is "syslog-facility set info /var/log/ndtpd.log". Cheers, -- Steve "Why does everyone say 'Relax' when they're about to do something terrible?" - Ensign Harry Kim, USS Voyager -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
Re: [SLUG] error processing ndtpd .. {& rampant syslog ?}
Steve Kowalik wrote: >On Thu, 26 May 2005 14:46:16 +1200, Adam Bogacki uttered > > >>Apparently it's an apostrophe out of place .. but which one ? >> >> >> >No, it isn't an apostrophe out of place. Post install scripts need to >be called with 2 or 3 arguments. I'd suggest you edit >/var/lib/dpkg/info/ndtpd.postinst and change "set -e" to "set -xe" and >see what it outputs when you run "dpkg --configure -a" > >Cheers, > > Thanks Steve, I've attached the output below. I'm also getting a lot of syslog messages appearing in gnome-terminal together with beeping and a red light flashing on the midi-tower. Adam. [EMAIL PROTECTED] > Tux:~# dpkg --configure -a > Setting up ndtpd (3.1.5-6.3) ... > + . /usr/share/debconf/confmodule > ++ '[' '!' '' ']' > ++ PERL_DL_NONLAZY=1 > ++ export PERL_DL_NONLAZY > ++ exec /usr/share/debconf/frontend /var/lib/dpkg/info/ndtpd.postinst > configure 3.1.5-6 > + . /usr/share/debconf/confmodule > ++ '[' '!' 1 ']' > ++ '[' -z '' ']' > ++ exec > ++ DEBCONF_REDIR=1 > ++ export DEBCONF_REDIR > + case "$1" in > + grep -q ndtpd /etc/inetd.conf > > Message from [EMAIL PROTECTED] at Thu May 26 16:05:19 2005 ... > tux kernel: New not syn:IN=eth0 OUT= > MAC=00:a0:cc:d9:e2:48:00:b0:8e:42:76:80:08:00 SRC=66.150.96.111 > DST=203.79.110.81 LEN=40 TOS=0x00 PREC=0x00 TTL=61 ID=5213 PROTO=TCP > SPT=80 DPT=36112 WINDOW=16384 RES=0x00 ACK RST URGP=0 > + syslog-facility set info /var/log/ndtpd.log > dpkg: error processing ndtpd (--configure): > subprocess post-installation script returned error exit status 1 > Errors were encountered while processing: > ndtpd > Tux:~# > Message from [EMAIL PROTECTED] at Thu May 26 16:05:41 2005 ... > tux kernel: IPT OUTPUT packet died: IN= OUT=eth0 SRC=203.79.110.81 > DST=203.79.110.255 LEN=262 TOS=0x00 PREC=0x00 TTL=64 ID=81 DF > PROTO=UDP SPT=138 DPT=138 LEN=242 > > Message from [EMAIL PROTECTED] at Thu May 26 16:05:42 2005 ... > tux kernel: IPT OUTPUT packet died: IN= OUT=eth0 SRC=203.79.110.81 > DST=203.79.110.255 LEN=232 TOS=0x00 PREC=0x00 TTL=64 ID=82 DF > PROTO=UDP SPT=138 DPT=138 LEN=212 > > Message from [EMAIL PROTECTED] at Thu May 26 16:05:42 2005 ... > tux kernel: IPT OUTPUT packet died: IN= OUT=eth0 SRC=203.79.110.81 > DST=203.96.152.4 LEN=63 TOS=0x00 PREC=0x00 TTL=64 ID=9449 DF PROTO=UDP > SPT=35615 DPT=53 LEN=43 > > Message from [EMAIL PROTECTED] at Thu May 26 16:06:42 2005 ... > tux kernel: IPT OUTPUT packet died: IN= OUT=eth0 SRC=203.79.110.81 > DST=203.96.152.4 LEN=63 TOS=0x00 PREC=0x00 TTL=64 ID=3924 DF PROTO=UDP > SPT=35616 DPT=53 LEN=43 > > Message from [EMAIL PROTECTED] at Thu May 26 16:06:42 2005 ... > tux kernel: IPT OUTPUT packet died: IN= OUT=eth0 SRC=203.79.110.81 > DST=203.96.152.12 LEN=63 TOS=0x00 PREC=0x00 TTL=64 ID=3924 DF > PROTO=UDP SPT=35616 DPT=53 LEN=43 > > Message from [EMAIL PROTECTED] at Thu May 26 16:06:42 2005 ... > tux kernel: IPT OUTPUT packet died: IN= OUT=eth0 SRC=203.79.110.81 > DST=203.96.152.4 LEN=63 TOS=0x00 PREC=0x00 TTL=64 ID=3924 DF PROTO=UDP > SPT=35616 DPT=53 LEN=43 > -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
