Re: warning: trouble opening remote
Russell Nelson [EMAIL PROTECTED] wrote:
If you're running qmail configured as per
http://www.lifewithqmail.org, then the following commands will fix the
problem:
svc -dx /service/qmail
setlock /service/qmail/supervise/lock sh -c
'/var/qmail/queue/*/0/{348381,348335,348013}'
For LWQ, the service is /service/qmail-send, and I think that should
be ... sh -c 'rm /var/
-Dave
warning: trouble opening remote
My qmail log always say: Jun 14 08:24:16 seic8 qmail: 992478256.893320 warning: trouble opening remote/0/348381; will try again later Jun 14 08:24:16 seic8 qmail: 992478256.894017 warning: trouble opening remote/0/348335; will try again later Jun 14 08:24:16 seic8 qmail: 992478256.894706 warning: trouble opening remote/0/348013; will try again later Jun 14 08:28:24 seic8 qmail: 992478504.216842 warning: trouble opening remote/0/348381; will try again later Jun 14 08:28:24 seic8 qmail: 992478504.217542 warning: trouble opening remote/0/348335; will try again later Jun 14 08:28:24 seic8 qmail: 992478504.218230 warning: trouble opening remote/0/348013; will try again later ... When I enter /var/qmail/queue/remote/0/, I con not find file 348381,348335 and 348013, What I showld do to deal with this problem? thx!
Re: warning: trouble opening remote
dgrer writes:
Jun 14 08:28:24 seic8 qmail: 992478504.218230 warning: trouble opening
remote/0/348013; will try again later
...
When I enter /var/qmail/queue/remote/0/, I con not find file 348381,348335 and
348013,
What I showld do to deal with this problem? thx!
This might be a permission problem (except that you say that those
files really *don't* exist), or it might be that somebody deleted
files out of the queue while qmail-send was running. Qmail-send keeps
its own idea of what's in the queue while it's running, so if you
delete files, it gets confused. Stop qmail-send, delete
/var/qmail/queue/*/0/{348381,348335,348013} and restart qmail-send.
If you're running qmail configured as per
http://www.lifewithqmail.org, then the following commands will fix the
problem:
svc -dx /service/qmail
setlock /service/qmail/supervise/lock sh -c
'/var/qmail/queue/*/0/{348381,348335,348013}'
--
-russ nelson [EMAIL PROTECTED] http://russnelson.com
Crynwr sells support for free software | PGPok |
521 Pleasant Valley Rd. | +1 315 268 1925 voice | #exclude windows.h
Potsdam, NY 13676-3213 | +1 315 268 9201 FAX |
Re: warning: trouble opening remote/4/r
Dear Alex Pennace In that case, send SIGTERM to the qmail-send process. I have tried to do so. But can you tell me where I can find PID of qmail-send process? flint
Re: warning: trouble opening remote/4/r
On Mon, Feb 26, 2001 at 05:11:56PM +0800, flint wrote: Dear Alex Pennace In that case, send SIGTERM to the qmail-send process. I have tried to do so. But can you tell me where I can find PID of qmail-send process? Use ps.
Re: warning: trouble opening remote/4/r
Dear Charles Cazabon I take it that you are not the one that installed qmail on this system. There's a thousand ways to start/stop qmail. You don't have a svc command, so it's probably not running under svscan. If it's installed with a SysV-like startup script, try /etc/rc.d/init.d/qmail sto or /etc/init.d/qmail stop There are no such command. or possibly (some Lwq installs): /usr/local/bin/qmail stop It doesn't work. If none of those work, see if you have /var/qmail/bin/rc -- that tells you how qmail starts, and perhaps then you'll know how to stop it. I have seen the /var/qmail/rc , I still don't know how to stop it. It says: #!/bin/sh # Using splogger to send the log through syslog. # Using qmail-local to deliver messages to ~/Mailbox by default. exec env - PATH="/var/qmail/bin:$PATH" \ qmail-start ./Maildir/ splogger qmail flint
Re: warning: trouble opening remote/4/r
On Mon, Feb 26, 2001 at 01:30:17PM +0800, flint wrote: Dear Charles Cazabon I take it that you are not the one that installed qmail on this system. There's a thousand ways to start/stop qmail. [snip] If none of those work, see if you have /var/qmail/bin/rc -- that tells you how qmail starts, and perhaps then you'll know how to stop it. I have seen the /var/qmail/rc , I still don't know how to stop it. It says: #!/bin/sh # Using splogger to send the log through syslog. # Using qmail-local to deliver messages to ~/Mailbox by default. exec env - PATH="/var/qmail/bin:$PATH" \ qmail-start ./Maildir/ splogger qmail In that case, send SIGTERM to the qmail-send process.
Re: warning: trouble opening remote/4/r
Dear Charles Cazabon Your problem could be ident and DNS lookup timeouts from tcpserver. Investigate the possibility of turning off ident lookups, and either disabling DNS lookups or fixing your DNS resolver/content server. Charles Yes! It's really our DNS problem. Several days ago,we have changed DNS server. Today i check the DNS server carefully, I found it can resolve the names in our domain,but it doen't use it's own data,it always say:"Non-authoritative answer: ..". I have configure the Named again. It's ok now. But I have not fix the queue yet, because I don't know how to Shut down the qmail-send. I know it is really a very stupid question. I have seen many documents,some use "svc" command, there isn't "svc" command in our server, also I cann't find qmail-send.pid file in /var/run like some articles said. How could I do? I'm appreaciate for your warmheartedness and patience. flint
Re: warning: trouble opening remote/4/r
Dear Charles Cazabon Your problem could be ident and DNS lookup timeouts from tcpserver. Investigate the possibility of turning off ident lookups, and either disabling DNS lookups or fixing your DNS resolver/content server. Charles Yes! It's really our DNS problem. Several days ago,we have changed DNS server. Today i check the DNS server carefully, I found it can resolve the names in our domain,but it doen't use it's own data,it always say:"Non-authoritative answer: ..". I have configure the Named again. It's ok now. But I have not fix the queue yet, because I don't know how to Shut down the qmail-send. I know it is really a very stupid question. I have seen many documents,some use "svc" command, there isn't "svc" command in our server, also I cann't find qmail-send.pid file in /var/run like some articles said. How could I do? I'm appreaciate for your warmheartedness and patience. flint
Re: warning: trouble opening remote/4/r
flint [EMAIL PROTECTED] wrote: Your problem could be ident and DNS lookup timeouts from tcpserver. Investigate the possibility of turning off ident lookups, and either disabling DNS lookups or fixing your DNS resolver/content server. Yes! It's really our DNS problem. [...] But I have not fix the queue yet, because I don't know how to Shut down the qmail-send. I have seen many documents,some use "svc" command, there isn't "svc" command in our server, also I cann't find qmail-send.pid file in /var/run like some articles said. How could I do? I take it that you are not the one that installed qmail on this system. There's a thousand ways to start/stop qmail. You don't have a svc command, so it's probably not running under svscan. If it's installed with a SysV-like startup script, try /etc/rc.d/init.d/qmail stop or /etc/init.d/qmail stop or possibly (some Lwq installs): /usr/local/bin/qmail stop If none of those work, see if you have /var/qmail/bin/rc -- that tells you how qmail starts, and perhaps then you'll know how to stop it. Charles -- --- Charles Cazabon[EMAIL PROTECTED] GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ Any opinions expressed are just that -- my opinions. ---
Re: warning: trouble opening remote/4/r
flint [EMAIL PROTECTED] wrote: You can either use queue-fix to replace/fix the (non-existent?) queue, or restore from your backups and THEN use queue-fix to fix the queue. I have fix the queue using queue-fix. It unlinked some file under /var/qmail/queue/remote, but now I still can see the Warning messages in the maillog? Is there something wrong? Did you run queue-fix while qmail was running? That would be bad. Stop qmail, run queuefix, then re-start qmail. I have noticed for days,now it becomes more and more unbearable. That is,it is very slowly when we receive mails through POP3. The strange thing is that when you have received the mails then receive mails again immediately, it is very quickly. This was not a good reason to remove the queue. qmail-pop3d doesn't look for mail in the queue anyways; it looks in the user's mailstore (~/Maildir/ typically). Your problem could be ident and DNS lookup timeouts from tcpserver. Investigate the possibility of turning off ident lookups, and either disabling DNS lookups or fixing your DNS resolver/content server. Charles -- --- Charles Cazabon[EMAIL PROTECTED] GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ Any opinions expressed are just that -- my opinions. ---
Re: Fw: Re: warning: trouble opening remote/4/r
flint [EMAIL PROTECTED] wrote: Today,I saw there were many messages like this in the maillog: 982653149.920320 warning: trouble opening remote/4/r Your queue is corrupt. Did you manually remove any messages from the queue? Get qmail-queuefix from www.qmail.org to fix this. Thank you. I have really removed the queue. But i have backuped them. Now which is better,override the queue with the backed queue or using the queue-fix to fix them. You can either use queue-fix to replace/fix the (non-existent?) queue, or restore from your backups and THEN use queue-fix to fix the queue. You can't just restore from tape; files in the queue are named based on the inodes they reside on. Restoring from tape will completely mess this up. queue-fix will rename all the files to match properly. Charles -- --- Charles Cazabon[EMAIL PROTECTED] GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ Any opinions expressed are just that -- my opinions. ---
Re: warning: trouble opening remote/4/r
Dear Charles Cazabon You can either use queue-fix to replace/fix the (non-existent?) queue, or restore from your backups and THEN use queue-fix to fix the queue. You can't just restore from tape; files in the queue are named based on the inodes they reside on. Restoring from tape will completely mess this up. queue-fix will rename all the files to match properly. Charles I have fix the queue using queue-fix. It unlinked some file under /var/qmail/queue/remote, but now I still can see the Warning messages in the maillog? Is there something wrong? Another question(that is also why I removed the queue), I have noticed for days,now it becomes more and more unbearable. That is,it is very slowly when we receive mails through POP3. The strange thing is that when you have received the mails then receive mails again immediately, it is very quickly. These days this situation is very common. I'm not sure what's the problem. It the problem of our Mail System or the problem of the network. My mail system is: FreeBSD+qmail+vpopmail+sqwebmail.Thank you. flint
Re: warning: trouble opening remote/4/r
flint [EMAIL PROTECTED] wrote: Today,I saw there were many messages like this in the maillog: 982653149.920320 warning: trouble opening remote/4/r Your queue is corrupt. Did you manually remove any messages from the queue? Get qmail-queuefix from www.qmail.org to fix this. Charles -- --- Charles Cazabon[EMAIL PROTECTED] GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ Any opinions expressed are just that -- my opinions. ---
warning: trouble opening remote/4/r
Hi everybody, Today,I saw there were many messages like this in the maillog: 982653149.920320 warning: trouble opening remote/4/r Who can tell me what those mean? Thanks flint [EMAIL PROTECTED]
warning: trouble opening remote/4/r
Hi everybody, Today,I saw there were many messages like this in the maillog: 982653149.920320 warning: trouble opening remote/4/r Who can tell me what those mean? Thanks flint [EMAIL PROTECTED]
Muchos warning: trouble opening remote/local...
Hello! Would you please give me advice for some questions? - 1. Now I'm confused with following message in the maillog. "qmail: 962478354.405231 warning: trouble opening local/22/1105816; will try again later" Many massage like this are appearing in the log forever What is occurring and how to eliminate them? (Mail of id "1105816" is of when testing and should have been dead..) - 2. What means (#x.x.x) number in the maillog? I encounter it sometimes like.. "delivery 10: deferral: connected_to_aaa.bbb.ccc.ddd_but_connection_died._(#4.4.2)/" What means "(#4.4.2)" and where can I look up them? - 3. About IDENT processing from smtp I can see following header in a testing mail from my qmail server to another my account. "from host.mydoman (IDENT:[EMAIL PROTECTED] [a.b.c.d]) by host.destination (8.9.3/8.7.1) with SMTP id BAA for [EMAIL PROTECTED]; Wed, 5 Jul 2000 01:44:01 -0600" As shown above, I allow IDENT access to the server now, but I suspect it. because I don't see the header with IDENT in another mail not from my server. Essentially, qmail smtp daemon is necessary (mandatory) for IDENT connection? And if I prohibit it, what would happen? Thank you in advance. Jaime (^o^) -- Hajime Lucky Okada
Re: Muchos warning: trouble opening remote/local...
Hajime Lucky Okada [EMAIL PROTECTED] wrote: "qmail: 962478354.405231 warning: trouble opening local/22/1105816; will try again later" Many massage like this are appearing in the log forever What is occurring and how to eliminate them? Sounds like your queue is corrupt. Try running qmail-qsanity or queuefix from www.qmail.org. - 2. What means (#x.x.x) number in the maillog? I encounter it sometimes like.. "delivery 10: deferral: connected_to_aaa.bbb.ccc.ddd_but_connection_died._(#4.4.2)/" What means "(#4.4.2)" and where can I look up them? From RFC 1893, Enhanced mail system status codes. http://www.ietf.org/rfc/rfc1893.txt: 4.X.X Persistent Transient Failure X.4.X Network and Routing Status X.4.2 Bad connection - 3. About IDENT processing from smtp Essentially, qmail smtp daemon is necessary (mandatory) for IDENT connection? And if I prohibit it, what would happen? No, IDENT isn't mandatory. If you don't run a daemon, that information will be left out of the Received fields of messages that pass through your system. -Dave
