Michael D. Baldwin wrote:
Yup, all files are owned by root. In fact, all files in the qpsmtpd are owned by root except for the tmp/ directory where is owned by smtpd user. I don't know what to say, there should be no reason it can't "see" the files.
chown -R smtpd.nofiles qpsmtpd chown -R qmaill.nofiles qpsmtpd/log
Using the appropriate user names. -Bob
On 1/8/06, *Bob Dodds* <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> wrote: All of your files there are owned by root? That readproctitle item when you ps is telling you there is a location or perms problem in there. If it can read the run file then you would get detail concerning a line of the run file, but it gives the run file name as the error, as if it is not able to find the run file or see into it. -Bob Michael D. Baldwin wrote: > To Bob: > > I can't send email from [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> <mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>>, as thats > the lan/mailserver in question.. so I'm going to stick to the list, > just incase others have inputs from what is discussed. > > qmail-smtpd/run is present, as can be seen here: > -rwxr-xr-x 1 root root 217 Dec 10 15:29 > /service/qmail-smtpd/run* > > qmail-smtpd/log/run is also present as well, as can be seen here: > -rwxr-xr-x 1 root root 87 Nov 18 04:45 > /service/qmail-smtpd/log/run* > > qmail-smtpd/log/main is present (it was created automagically when > run* is ran): > bloated:/service/qmail-smtpd/supervise# lsa /service/qmail-smtpd/log/main/ > total 240k > -rw-r--r-- 1 root root 235k Jan 8 02:13 current > -rw------- 1 root root 0 Jan 7 19:26 lock > -rw-r--r-- 1 root root 0 Jan 7 19:26 state > bloated:/service/qmail-smtpd/supervise# > > Like I said, this configuration (along with all the files, > directories, etc) worked perfectly fine for months after upgrading to > 0.31.1, never had a single issue. It has just all of a sudden stop > accepting mail from the lan. When you telnet to the smtpd on its > external (internet-side) IP it will give you a greeting all day long, > but if you telnet to its internal (lan-side) IP it simply will not > give you a greeting in a timely manner... it won't give you a greeting > till some other remote mail (mail coming in on external IP) comes in. > I have no idea why this is, its extremely perplexing to me. > > Michael D. Baldwin wrote: > > It's definitely not zero length: > > -rw-r--r-- 1 root root 199k Jan 8 01:31 > > /var/qmail/qpsmtpd/log/main/current > > > > I just did a ps auxwww and I do see this: > > root 9475 0.0 0.0 1268 260 ? S Jan07 0:00 > > readproctitle service errors: ...arning: unable to open > > qmail-smtpd/supervise/status.new: file does not exist?supervise: > > warning: unable to open qmail-smtpd/supervise/status.new: file does > > not exist?supervise: warning: unable to open > > qmail-smtpd/supervise/status.new: file does not exist?supervise: > > fatal: unable to start qmail-smtpd/run: file does not exist?supervise: > > fatal: unable to start qmail-smtpd/run: file does not exist? > It can't find qmail-smtpd/run. > > Assuming ln -s /var/qpsmtpd /service/qmail-smtpd, then... > > You need a /service/qmail-smtpd/run and a /service/qmail-smtpd/log/run > if you have something like ln -s /var/qpsmtpd /service/qmail-smtpd > and you need a /service/qmail-smtpd/log/main/ for log files. > > -Bob > > > > What exactly does that mean and how would I attempt to fix it? Like I > > said, I simply haven't changed a thing in months from a working > > configuration. So I have no clue why these errors or anything like > > this would just suddenly happen. Here is some ls output, incase this > > will help you: > > > > bloated:/service/qmail-smtpd# lsa > > total 56k > > drwxr-xr-x 2 root root 4.0k Jan 7 18:59 config/ > > drwxr-xr-x 2 root root 4.0k Jan 7 19:00 config.sample/ > > drwxr-xr-x 4 root root 4.0k Jan 7 19:00 lib/ > > drwxr-xr-x 4 root root 4.0k Jan 7 19:26 log/ > > drwxr-xr-x 7 root root 4.0k Jan 7 19:01 plugins/ > > -rwxr-xr-x 1 root root 635 Nov 18 04:45 qpsmtpd* > > -rwxr-xr-x 1 root root 8.1k Nov 18 04:45 > > qpsmtpd-forkserver* > > -rwxr-xr-x 1 root root 555 Nov 18 04:45 qpsmtpd-server* > > -rwxr-xr-x 1 root root 217 Dec 10 15:29 run* > > drwx------ 2 root root 4.0k Jan 8 01:40 supervise/ > > drwxr-xr-x 4 root root 4.0k Jan 7 19:01 t/ > > drwx------ 2 smtpd smtpd 4.0k Jan 7 22:07 tmp/ > > bloated:/service/qmail-smtpd# > > > > bloated:/service/qmail-smtpd/supervise# lsa > > total 4.0k > > prw------- 1 root root 0 Jan 8 01:40 control| > > -rw------- 1 root root 0 Dec 10 14:58 lock > > prw------- 1 root root 0 Dec 10 14:58 ok| > > -rw-r--r-- 1 root root 18 Jan 8 01:40 status > > bloated:/service/qmail-smtpd/supervise# > > > > On 1/7/06, *Bob Dodds* < [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> <mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> <mailto: > [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> <mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>>>> wrote: > > > > Ask Bjørn Hansen wrote: > > > > > > On Jan 7, 2006, at 3:01 PM, Michael D. Baldwin wrote: > > > > > >> Just last night I was sending emails fine, this afternoon I > try to > > >> send an > > >> email from my lan and nothing. It just simply WILL NOT > > SEND. Absolutely > > >> nothing on my mailserver has changed. It's the same way right > > now as > > >> it was > > >> last night when mail worked fine. I turned the loglevel upto > 7 and > > >> watched > > >> the output. > > > > > > Do you see new output written to the log? > > > > > > If not, then the log writer probably got stuck and qpsmtpd is > > > blocking trying to add to the log. > > > > > > - ask > > Look for a zero length ./log/main/current file as one symptom. > > > > ps uw -A > > > > kill -9 [pid of qpsmtpd's multilog] > > > > Then you would see the "current" log file begin to grow > > in size, and qpsmtpd would start working, if multilog was > > the problem. > > > > "man multilog" tells us multilog will pause if it has a problem > > rotating the logs. > > > > You can kill -9 [pid of multilog] as many times as you like > > without hurting anything. Once would tell you if that > > was the block. > > > > I'm still having this problem myself because of some little > > path problem in my multilog !processor_script. I make a > > little change, wait a day for current file to roll over into > > a @*.s file, "ps uw -A", read "readproctitle" error message. > > I'm not complaining. I think multilog is a great tool. > > > > -Bob > > > > > > > > On 1/8/06, *Michael D. Baldwin* <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > <mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>>> wrote: > > It's definitely not zero length: > -rw-r--r-- 1 root root 199k Jan 8 01:31 > /var/qmail/qpsmtpd/log/main/current > > I just did a ps auxwww and I do see this: > root 9475 0.0 0.0 1268 260 ? S Jan07 0:00 > readproctitle service errors: ...arning: unable to open > qmail-smtpd/supervise/status.new: file does not exist?supervise: > warning: unable to open qmail-smtpd/supervise/status.new: file > does not exist?supervise: warning: unable to open > qmail-smtpd/supervise/status.new: file does not exist?supervise: > fatal: unable to start qmail-smtpd/run: file does not > exist?supervise: fatal: unable to start qmail-smtpd/run: file does > not exist? > > What exactly does that mean and how would I attempt to fix it? > Like I said, I simply haven't changed a thing in months from a > working configuration. So I have no clue why these errors or > anything like this would just suddenly happen. Here is some ls > output, incase this will help you: > > bloated:/service/qmail-smtpd# lsa > total 56k > drwxr-xr-x 2 root root 4.0k Jan 7 18:59 config/ > drwxr-xr-x 2 root root 4.0k Jan 7 19:00 config.sample/ > drwxr-xr-x 4 root root 4.0k Jan 7 19:00 lib/ > drwxr-xr-x 4 root root 4.0k Jan 7 19:26 log/ > drwxr-xr-x 7 root root 4.0k Jan 7 19:01 plugins/ > -rwxr-xr-x 1 root root 635 Nov 18 04:45 qpsmtpd* > -rwxr-xr-x 1 root root 8.1k Nov 18 04:45 > qpsmtpd-forkserver* > -rwxr-xr-x 1 root root 555 Nov 18 04:45 > qpsmtpd-server* > -rwxr-xr-x 1 root root 217 Dec 10 15:29 run* > drwx------ 2 root root 4.0k Jan 8 01:40 supervise/ > drwxr-xr-x 4 root root 4.0k Jan 7 19:01 t/ > drwx------ 2 smtpd smtpd 4.0k Jan 7 22:07 tmp/ > bloated:/service/qmail-smtpd# > > bloated:/service/qmail-smtpd/supervise# lsa > total 4.0k > prw------- 1 root root 0 Jan 8 01:40 control| > -rw------- 1 root root 0 Dec 10 14:58 lock > prw------- 1 root root 0 Dec 10 14:58 ok| > -rw-r--r-- 1 root root 18 Jan 8 01:40 status > bloated:/service/qmail-smtpd/supervise# > > > On 1/7/06, * Bob Dodds* < [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> <mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>>> wrote: > > Ask Bjørn Hansen wrote: > > > > On Jan 7, 2006, at 3:01 PM, Michael D. Baldwin wrote: > > > >> Just last night I was sending emails fine, this afternoon I > try to > >> send an > >> email from my lan and nothing. It just simply WILL NOT > SEND. Absolutely > >> nothing on my mailserver has changed. It's the same way > right now as > >> it was > >> last night when mail worked fine. I turned the loglevel upto > 7 and > >> watched > >> the output. > > > > Do you see new output written to the log? > > > > If not, then the log writer probably got stuck and qpsmtpd is > > blocking trying to add to the log. > > > > - ask > Look for a zero length ./log/main/current file as one symptom. > > ps uw -A > > kill -9 [pid of qpsmtpd's multilog] > > Then you would see the "current" log file begin to grow > in size, and qpsmtpd would start working, if multilog was > the problem. > > "man multilog" tells us multilog will pause if it has a problem > rotating the logs. > > You can kill -9 [pid of multilog] as many times as you like > without hurting anything. Once would tell you if that > was the block. > > I'm still having this problem myself because of some little > path problem in my multilog !processor_script. I make a > little change, wait a day for current file to roll over into > a @*.s file, "ps uw -A", read "readproctitle" error message. > I'm not complaining. I think multilog is a great tool. > > -Bob > > >
