Re: [DNG] exim paniclog /var/log/exim4/paniclog has non-zero size
Den 2021-12-02 kl. 09:16, skrev Marc Shapiro via Dng:
No luck. I rebooted and got the paniclog error during the boot. After
booting, I stopped exim4, deleted the paniclog, and restarted exim4.
It created a paniclog containing the following:
Had you also executed
exim4 -qff -v
I think you would immediately had your paniclog back, you have
undelivered messages that fails when exim tries to deliver.
2021-12-02 00:06:49 1momA3-00054k-DE == m...@quixote.home R=local_user
T=mail_spool defer (-1): Tainted '/var/mail/marc' (file or directory
name for mail_spool transport) not permitted
How do I convince exim4 that /var/spool/marc is an acceptable file
name for mail_spool transport?
Exim no longer allows a sender to decide a name of a path component, in
this case 'marc'. Your config needs to agree on 'marc' being allowed.
This is done using a lookup locally.
From what I understand there was / is a discussion about a setting to
just warn about this tainted data but allow it, but I could not make it
work.
I think you already have a lookup in the default config that checks
/etc/aliases which would allow 'marc' in your path if you just add a line
marc: marc
to it, I cant promise because I also use another lookup to be able to
send mail.
Anyhow, after a successful lookup, the config variable ${local_part} can
be replaced by the new variable ${local_part_data} which will recieve
its value in the lookup you need to have.
Your config files under /etc/exim4/conf.d must not contain ${local_part}
anymore.
I have no idea what will happen if you try to reinstall exim to get a
new default config.
//PG
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] exim paniclog /var/log/exim4/paniclog has non-zero size
On 12/1/21 23:56, Marc Shapiro wrote: On 12/1/21 10:10, Ludovic Bellière via Dng wrote: If you do not need your mail system to talk to the world, then you should replace exim with something that is a lot simpler to use and configure. I would suggest msmtp (https://marlam.de/msmtp/) as its configuration is a lot more simpler to the neophyte. If you want to keep exim4, I would then suggest to nuke the existing configuration and start from scratch with `dpkg-reconfigure exim4-config'. Extended information should be available at https://wiki.debian.org/Exim Exim4 being a software designed to handle large amount of emails, it may be out of scope for your personal usage. While, as I said, msmtp is a lot more accessible through its minimalist approach: you only need a file with a dozen of lines for it to function properly. While I do use it, I wouldn't be able to help you with exim4, the software is way too large and complex for my own understanding. I mainly rely on dpkg-reconfigure and hope nothing breaks. And while msmtp is easier to understand, changing software can itself be a source of immeasurable pain. So, if in doubt, you should probably rely on dpkg-reconfigure. Cheers, Ludovic On Wed, 01 Dec 2021, Marc Shapiro via Dng wrote: This is very likely the problem, as I now have version 4.94.2-7 installed. I know virtually nothing, however, about how MTAs do their work. Where and how do I make these config changes. I use Thunderbird for mail coming from outside the local network. Exim is only used for local transport (such as e-mail from cron jobs). Marc I looked into some of the other options and I do not recall why I decided against them. It may have been when I thought that I was going to use the MTA for more than just local mail. In any case, I have run `dpkg-reconfigure exim4-config' using the defaults from when I set it up originally. I am hoping that doing so with the new exim4 installed will correct the configuration issues. When I ran `dpkg-reconfigure exim4-config' I got the error about the paniclog being non-zero size, but I expected that. I truncated the paniclog and ran `dpkg-reconfigure exim4-config' again, this time with no errors. I have sent myself an e-mail from 'root' but have not received it. I will probably try shutting down the system and rebooting, to see if that gets things back in order after the reconfig. No luck. I rebooted and got the paniclog error during the boot. After booting, I stopped exim4, deleted the paniclog, and restarted exim4. It created a paniclog containing the following: 2021-12-02 00:06:48 1mmEkA-9l-Jr == m...@quixote.home R=local_user T=mail_spool defer (-1): Tainted '/var/mail/marc' (file or directory name for mail_spool transport) not permitted 2021-12-02 00:06:48 1msgsb-0002NH-Cv == m...@quixote.home R=local_user T=mail_spool defer (-1): Tainted '/var/mail/marc' (file or directory name for mail_spool transport) not permitted 2021-12-02 00:06:49 1mrJnB-00026m-53 == m...@quixote.home R=local_user T=mail_spool defer (-1): Tainted '/var/mail/marc' (file or directory name for mail_spool transport) not permitted 2021-12-02 00:06:49 1msCJK-0007YK-Pi == m...@quixote.home R=local_user T=mail_spool defer (-1): Tainted '/var/mail/marc' (file or directory name for mail_spool transport) not permitted 2021-12-02 00:06:49 1momA3-00054k-DE == m...@quixote.home R=local_user T=mail_spool defer (-1): Tainted '/var/mail/marc' (file or directory name for mail_spool transport) not permitted How do I convince exim4 that /var/spool/marc is an acceptable file name for mail_spool transport? Marc ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] exim paniclog /var/log/exim4/paniclog has non-zero size
On 12/1/21 10:10, Ludovic Bellière via Dng wrote: If you do not need your mail system to talk to the world, then you should replace exim with something that is a lot simpler to use and configure. I would suggest msmtp (https://marlam.de/msmtp/) as its configuration is a lot more simpler to the neophyte. If you want to keep exim4, I would then suggest to nuke the existing configuration and start from scratch with `dpkg-reconfigure exim4-config'. Extended information should be available at https://wiki.debian.org/Exim Exim4 being a software designed to handle large amount of emails, it may be out of scope for your personal usage. While, as I said, msmtp is a lot more accessible through its minimalist approach: you only need a file with a dozen of lines for it to function properly. While I do use it, I wouldn't be able to help you with exim4, the software is way too large and complex for my own understanding. I mainly rely on dpkg-reconfigure and hope nothing breaks. And while msmtp is easier to understand, changing software can itself be a source of immeasurable pain. So, if in doubt, you should probably rely on dpkg-reconfigure. Cheers, Ludovic On Wed, 01 Dec 2021, Marc Shapiro via Dng wrote: This is very likely the problem, as I now have version 4.94.2-7 installed. I know virtually nothing, however, about how MTAs do their work. Where and how do I make these config changes. I use Thunderbird for mail coming from outside the local network. Exim is only used for local transport (such as e-mail from cron jobs). Marc I looked into some of the other options and I do not recall why I decided against them. It may have been when I thought that I was going to use the MTA for more than just local mail. In any case, I have run `dpkg-reconfigure exim4-config' using the defaults from when I set it up originally. I am hoping that doing so with the new exim4 installed will correct the configuration issues. When I ran `dpkg-reconfigure exim4-config' I got the error about the paniclog being non-zero size, but I expected that. I truncated the paniclog and ran `dpkg-reconfigure exim4-config' again, this time with no errors. I have sent myself an e-mail from 'root' but have not received it. I will probably try shutting down the system and rebooting, to see if that gets things back in order after the reconfig. Marc ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] exim paniclog /var/log/exim4/paniclog has non-zero size
If you do not need your mail system to talk to the world, then you should replace exim with something that is a lot simpler to use and configure. I would suggest msmtp (https://marlam.de/msmtp/) as its configuration is a lot more simpler to the neophyte. If you want to keep exim4, I would then suggest to nuke the existing configuration and start from scratch with `dpkg-reconfigure exim4-config'. Extended information should be available at https://wiki.debian.org/Exim Exim4 being a software designed to handle large amount of emails, it may be out of scope for your personal usage. While, as I said, msmtp is a lot more accessible through its minimalist approach: you only need a file with a dozen of lines for it to function properly. While I do use it, I wouldn't be able to help you with exim4, the software is way too large and complex for my own understanding. I mainly rely on dpkg-reconfigure and hope nothing breaks. And while msmtp is easier to understand, changing software can itself be a source of immeasurable pain. So, if in doubt, you should probably rely on dpkg-reconfigure. Cheers, Ludovic On Wed, 01 Dec 2021, Marc Shapiro via Dng wrote: This is very likely the problem, as I now have version 4.94.2-7 installed. I know virtually nothing, however, about how MTAs do their work. Where and how do I make these config changes. I use Thunderbird for mail coming from outside the local network. Exim is only used for local transport (such as e-mail from cron jobs). Marc signature.asc Description: PGP signature ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] exim paniclog /var/log/exim4/paniclog has non-zero size
This is very likely the problem, as I now have version 4.94.2-7 installed. I know virtually nothing, however, about how MTAs do their work. Where and how do I make these config changes. I use Thunderbird for mail coming from outside the local network. Exim is only used for local transport (such as e-mail from cron jobs). Marc On 11/30/21 18:56, Ludovic Bellière via Dng wrote: On Tue, 30 Nov 2021, Marc Shapiro via Dng wrote: I am getting e-mails like the one below all the time, now. I had this problem once before and I think that all I had to do was clear the paniclog with '> paniclog', but that does not seem to be working, now. I cleared it this morning, and when I just checked it was filling up again. It looks like I get three lines every half hour. This is preventing me from receiving e-mails sent by a cron job that runs a backup script. Any ideas on how to get rid of this and not have it come back would be greatly appreciated. Marc Make sure your exim configuration matches with the version of exim you have installed. Make sure there is no .dpkg-new laying around in /etc/exim4. Check /usr/share/doc/exim4-base/changelog.gz. Notably, in /usr/share/doc/exim4-base/README.UPDATING.gz: # Exim version 4.94 # - # # Some Transports now refuse to use tainted data in constructing their delivery # location; this WILL BREAK configurations which are not updated accordingly. # In particular: any Transport use of $local_part which has been relying upon # check_local_user far away in the Router to make it safe, should be updated to # replace $local_part with $local_part_data. Cheers, Ludovic ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] exim paniclog /var/log/exim4/paniclog has non-zero size
On Tue, 30 Nov 2021, Marc Shapiro via Dng wrote: I am getting e-mails like the one below all the time, now. I had this problem once before and I think that all I had to do was clear the paniclog with '> paniclog', but that does not seem to be working, now. I cleared it this morning, and when I just checked it was filling up again. It looks like I get three lines every half hour. This is preventing me from receiving e-mails sent by a cron job that runs a backup script. Any ideas on how to get rid of this and not have it come back would be greatly appreciated. Marc Make sure your exim configuration matches with the version of exim you have installed. Make sure there is no .dpkg-new laying around in /etc/exim4. Check /usr/share/doc/exim4-base/changelog.gz. Notably, in /usr/share/doc/exim4-base/README.UPDATING.gz: # Exim version 4.94 # - # # Some Transports now refuse to use tainted data in constructing their delivery # location; this WILL BREAK configurations which are not updated accordingly. # In particular: any Transport use of $local_part which has been relying upon # check_local_user far away in the Router to make it safe, should be updated to # replace $local_part with $local_part_data. Cheers, Ludovic signature.asc Description: PGP signature ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] exim paniclog /var/log/exim4/paniclog has non-zero size
Marc Shapiro via Dng wrote: > exim paniclog /var/log/exim4/paniclog on quixote.home has non-zero > size, mail system might be broken. Up to 10 lines are quoted below. > > 2021-11-30 06:00:19 1momA3-00054k-DE ==m...@quixote.home R=local_user > T=mail_spool defer (-1): Tainted '/var/mail/marc' (file or directory > name for mail_spool transport) not permitted One other link that may be of help (?) https://dev1galaxy.org/viewtopic.php?id=4379 ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] exim paniclog /var/log/exim4/paniclog has non-zero size
Marc Shapiro via Dng wrote: > I am getting e-mails like the one below all the time, now. I had this > problem once before and I think that all I had to do was clear the > paniclog with '> paniclog', but that does not seem to be working, > now. I cleared it this morning, and when I just checked it was > filling up again. It looks like I get three lines every half hour. > This is preventing me from receiving e-mails sent by a cron job that > runs a backup script. Any ideas on how to get rid of this and not > have it come back would be greatly appreciated. > > Marc > > e-mail showing paniclog: > > exim paniclog /var/log/exim4/paniclog on quixote.home has non-zero > size, mail system might be broken. Up to 10 lines are quoted below. > > 2021-11-30 06:00:19 1momA3-00054k-DE ==m...@quixote.home R=local_user > T=mail_spool defer (-1): Tainted '/var/mail/marc' (file or directory > name for mail_spool transport) not permitted > 2021-11-30 06:30:19 1mrJnB-00026m-53 ==m...@quixote.home R=local_user > T=mail_spool defer (-1): Tainted '/var/mail/marc' (file or directory > name for mail_spool transport) not permitted > 2021-11-30 06:30:20 1mmEkA-9l-Jr ==m...@quixote.home R=local_user > T=mail_spool defer (-1): Tainted '/var/mail/marc' (file or directory > name for mail_spool transport) not permitted > 2021-11-30 06:30:20 1momA3-00054k-DE ==m...@quixote.home R=local_user > T=mail_spool defer (-1): Tainted '/var/mail/marc' (file or directory > name for mail_spool transport) not permitted > 2021-11-30 07:00:19 1mrJnB-00026m-53 ==m...@quixote.home R=local_user > T=mail_spool defer (-1): Tainted '/var/mail/marc' (file or directory > name for mail_spool transport) not permitted > 2021-11-30 07:00:19 1mmEkA-9l-Jr ==m...@quixote.home R=local_user > T=mail_spool defer (-1): Tainted '/var/mail/marc' (file or directory > name for mail_spool transport) not permitted > 2021-11-30 07:00:19 1momA3-00054k-DE ==m...@quixote.home R=local_user > T=mail_spool defer (-1): Tainted '/var/mail/marc' (file or directory > name for mail_spool transport) not permitted > 2021-11-30 07:30:19 1mrJnB-00026m-53 ==m...@quixote.home R=local_user > T=mail_spool defer (-1): Tainted '/var/mail/marc' (file or directory > name for mail_spool transport) not permitted > 2021-11-30 07:30:20 1mmEkA-9l-Jr ==m...@quixote.home R=local_user > T=mail_spool defer (-1): Tainted '/var/mail/marc' (file or directory > name for mail_spool transport) not permitted > 2021-11-30 07:30:20 1momA3-00054k-DE ==m...@quixote.home R=local_user > T=mail_spool defer (-1): Tainted '/var/mail/marc' (file or directory > name for mail_spool transport) not permitted > > ___ > Dng mailing list > Dng@lists.dyne.org > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng Does this help? A dist-upgrade, thus upgrading exim, could cause breakage, requiring configuration update. I use postfix instead of exim, and don't know much about exim, just found this following link on a search. https://lists.archive.carbon60.com/exim/users/117441 ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] exim paniclog /var/log/exim4/paniclog has non-zero size
This is what is in /var/log/exim4. As you can see, thae paniclog still has the same ownership and rights as everything else in the directory. Marc root@quixote:/var/log/exim4# ls total 88 -rw-r- 1 Debian-exim adm 10728 Nov 30 15:13 mainlog -rw-r- 1 Debian-exim adm 31961 Nov 30 07:53 mainlog.1 -rw-r- 1 Debian-exim adm 1036 Nov 21 08:02 mainlog.10.gz -rw-r- 1 Debian-exim adm 1426 Nov 29 07:45 mainlog.2.gz -rw-r- 1 Debian-exim adm 1241 Nov 28 07:41 mainlog.3.gz -rw-r- 1 Debian-exim adm 1170 Nov 27 07:52 mainlog.4.gz -rw-r- 1 Debian-exim adm 1172 Nov 26 07:55 mainlog.5.gz -rw-r- 1 Debian-exim adm 1160 Nov 25 07:42 mainlog.6.gz -rw-r- 1 Debian-exim adm 1167 Nov 24 07:36 mainlog.7.gz -rw-r- 1 Debian-exim adm 1168 Nov 23 07:56 mainlog.8.gz -rw-r- 1 Debian-exim adm 1148 Nov 22 07:54 mainlog.9.gz -rw-r- 1 Debian-exim adm 740 Nov 30 15:13 paniclog -rw-r- 1 Debian-exim adm 0 Nov 9 23:14 rejectlog - On 11/30/21 15:07, d...@d404.nl wrote: On 01-12-2021 00:00, Marc Shapiro via Dng wrote: I am getting e-mails like the one below all the time, now. I had this problem once before and I think that all I had to do was clear the paniclog with '> paniclog', but that does not seem to be working, now. I cleared it this morning, and when I just checked it was filling up again. It looks like I get three lines every half hour. This is preventing me from receiving e-mails sent by a cron job that runs a backup script. Any ideas on how to get rid of this and not have it come back would be greatly appreciated. Marc e-mail showing paniclog: exim paniclog /var/log/exim4/paniclog on quixote.home has non-zero size, mail system might be broken. Up to 10 lines are quoted below. 2021-11-30 06:00:19 1momA3-00054k-DE ==m...@quixote.home R=local_user T=mail_spool defer (-1): Tainted '/var/mail/marc' (file or directory name for mail_spool transport) not permitted 2021-11-30 06:30:19 1mrJnB-00026m-53 ==m...@quixote.home R=local_user T=mail_spool defer (-1): Tainted '/var/mail/marc' (file or directory name for mail_spool transport) not permitted 2021-11-30 06:30:20 1mmEkA-9l-Jr ==m...@quixote.home R=local_user T=mail_spool defer (-1): Tainted '/var/mail/marc' (file or directory name for mail_spool transport) not permitted 2021-11-30 06:30:20 1momA3-00054k-DE ==m...@quixote.home R=local_user T=mail_spool defer (-1): Tainted '/var/mail/marc' (file or directory name for mail_spool transport) not permitted 2021-11-30 07:00:19 1mrJnB-00026m-53 ==m...@quixote.home R=local_user T=mail_spool defer (-1): Tainted '/var/mail/marc' (file or directory name for mail_spool transport) not permitted 2021-11-30 07:00:19 1mmEkA-9l-Jr ==m...@quixote.home R=local_user T=mail_spool defer (-1): Tainted '/var/mail/marc' (file or directory name for mail_spool transport) not permitted 2021-11-30 07:00:19 1momA3-00054k-DE ==m...@quixote.home R=local_user T=mail_spool defer (-1): Tainted '/var/mail/marc' (file or directory name for mail_spool transport) not permitted 2021-11-30 07:30:19 1mrJnB-00026m-53 ==m...@quixote.home R=local_user T=mail_spool defer (-1): Tainted '/var/mail/marc' (file or directory name for mail_spool transport) not permitted 2021-11-30 07:30:20 1mmEkA-9l-Jr ==m...@quixote.home R=local_user T=mail_spool defer (-1): Tainted '/var/mail/marc' (file or directory name for mail_spool transport) not permitted 2021-11-30 07:30:20 1momA3-00054k-DE ==m...@quixote.home R=local_user T=mail_spool defer (-1): Tainted '/var/mail/marc' (file or directory name for mail_spool transport) not permitted ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng You probably used a UID/GID to clear paniclog which exim cannot write to because different group or no group or other rights. Grtz Nick ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] exim paniclog /var/log/exim4/paniclog has non-zero size
root@quixote:/usr/local/bin# ls -al /var/mail/ total 396 drwxrwsr-x 2 root mail 4096 Nov 30 07:59 . drwxr-xr-x 13 root root 4096 Dec 3 2020 .. -rw-rw 1 marc mail 136846 Nov 30 07:53 marc -rw-r--r-- 1 marc mail 9864 Nov 30 15:15 marc.msf -rw-r--r-- 1 marc mail 25 Nov 25 23:36 msgFilterRules.dat -rw--- 1 root mail 0 Nov 14 2020 root -rw-r--r-- 1 marc mail 1622 Nov 25 23:36 root.msf -rw--- 1 marc mail 196494 Nov 30 08:05 Trash -rw-r--r-- 1 marc mail 26198 Nov 30 14:51 Trash.msf -rw--- 1 marc mail 0 Nov 25 23:35 Unsent Messages -rw-r--r-- 1 marc mail 1757 Nov 30 15:14 Unsent Messages.msf On 11/30/21 15:06, Antony Stone wrote: ls -al/var/mail/ ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] exim paniclog /var/log/exim4/paniclog has non-zero size
On 01-12-2021 00:00, Marc Shapiro via Dng wrote: I am getting e-mails like the one below all the time, now. I had this problem once before and I think that all I had to do was clear the paniclog with '> paniclog', but that does not seem to be working, now. I cleared it this morning, and when I just checked it was filling up again. It looks like I get three lines every half hour. This is preventing me from receiving e-mails sent by a cron job that runs a backup script. Any ideas on how to get rid of this and not have it come back would be greatly appreciated. Marc e-mail showing paniclog: exim paniclog /var/log/exim4/paniclog on quixote.home has non-zero size, mail system might be broken. Up to 10 lines are quoted below. 2021-11-30 06:00:19 1momA3-00054k-DE ==m...@quixote.home R=local_user T=mail_spool defer (-1): Tainted '/var/mail/marc' (file or directory name for mail_spool transport) not permitted 2021-11-30 06:30:19 1mrJnB-00026m-53 ==m...@quixote.home R=local_user T=mail_spool defer (-1): Tainted '/var/mail/marc' (file or directory name for mail_spool transport) not permitted 2021-11-30 06:30:20 1mmEkA-9l-Jr ==m...@quixote.home R=local_user T=mail_spool defer (-1): Tainted '/var/mail/marc' (file or directory name for mail_spool transport) not permitted 2021-11-30 06:30:20 1momA3-00054k-DE ==m...@quixote.home R=local_user T=mail_spool defer (-1): Tainted '/var/mail/marc' (file or directory name for mail_spool transport) not permitted 2021-11-30 07:00:19 1mrJnB-00026m-53 ==m...@quixote.home R=local_user T=mail_spool defer (-1): Tainted '/var/mail/marc' (file or directory name for mail_spool transport) not permitted 2021-11-30 07:00:19 1mmEkA-9l-Jr ==m...@quixote.home R=local_user T=mail_spool defer (-1): Tainted '/var/mail/marc' (file or directory name for mail_spool transport) not permitted 2021-11-30 07:00:19 1momA3-00054k-DE ==m...@quixote.home R=local_user T=mail_spool defer (-1): Tainted '/var/mail/marc' (file or directory name for mail_spool transport) not permitted 2021-11-30 07:30:19 1mrJnB-00026m-53 ==m...@quixote.home R=local_user T=mail_spool defer (-1): Tainted '/var/mail/marc' (file or directory name for mail_spool transport) not permitted 2021-11-30 07:30:20 1mmEkA-9l-Jr ==m...@quixote.home R=local_user T=mail_spool defer (-1): Tainted '/var/mail/marc' (file or directory name for mail_spool transport) not permitted 2021-11-30 07:30:20 1momA3-00054k-DE ==m...@quixote.home R=local_user T=mail_spool defer (-1): Tainted '/var/mail/marc' (file or directory name for mail_spool transport) not permitted ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng You probably used a UID/GID to clear paniclog which exim cannot write to because different group or no group or other rights. Grtz Nick ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] exim paniclog /var/log/exim4/paniclog has non-zero size
On Wednesday 01 December 2021 at 00:00:00, Marc Shapiro via Dng wrote: > I am getting e-mails like the one below all the time, now. > 2021-11-30 06:00:19 1momA3-00054k-DE ==m...@quixote.home R=local_user > T=mail_spool defer (-1): Tainted '/var/mail/marc' (file or directory name > for mail_spool transport) not permitted What do you get from: ls -al /var/mail/ Antony. -- In science, one tries to tell people in such a way as to be understood by everyone something that no-one ever knew before. In poetry, it is the exact opposite. - Paul Dirac Please reply to the list; please *don't* CC me. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] exim paniclog
On Tue, Jun 01, 2021 at 09:10:38AM +1000, wirelessduck--- via Dng wrote: >> On 1 Jun 2021, at 05:26, Marc Shapiro via Dng wrote: >> /var/log/exim4/paniclog on quixote.home has non-zero size, mail >> system might be broken. The last 10 lines are quoted below. >> >> 2021-05-29 19:35:47 daemon: fork of queue-runner process failed: >> Cannot allocate memory *SKIP* > Next time, before just powering down the system, you should try the > Magic SysRq keyboard shortcuts to see if the kernel is still > responding. > > https://www.kernel.org/doc/html/latest/admin-guide/sysrq.html (I found out this The Hard Way) If anyone is interested in resorting to The Magic SysRq in some unforseable future, then such person should check content of /proc/sys/kernel/sysrq now before it's too late. > I like to follow the example used on the Wikipedia page which lists > the Alt+SysRq+REISUB keys for doing a safer reboot than simply just > hitting the physical power button. Unfortunately, due to contents of above mentioned 'sysrq' I had no chance to verify, but may be SysRq+REIV could be enough. *CUT* -- Torvalds' goal for Linux is very simple: World Domination Stallman's goal for GNU is even simpler: Freedom ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] exim paniclog
> On 1 Jun 2021, at 05:26, Marc Shapiro via Dng wrote: > > I received this e-mail yesterday, and again today: > > - > exim paniclog /var/log/exim4/paniclog on quixote.home has non-zero size, mail > system might be broken. The last 10 lines are quoted below. > > 2021-05-29 19:35:47 daemon: fork of queue-runner process failed: Cannot > allocate memory > - > > I use Thunderbird for all non-local mail. > I am only using exim for local mail. > The only mail that I receive locally is a weekly e-mail from a cron job that > I have set up to do backups, and I did receive that e-mail yesterday, along > with the above e-mail. > > I'm not familiar with the workings of exim, or any MTA, so I don't really > know what the error message means, other than that there was some memory > issue. The one clue that I have is that something (I am fairly sure that it > was a Firefox tab) completely locked my system on Saturday night. Everything > started slowing down. Mousing became erratic. Then everything completely > stopped. I couldn't even switch to a terminal where I could kill Firefox. I > finally had to simply power down the system. (How I hate doing that!) Then > I rebooted, did a controlled shutdown and rebooted, again. After that, > everything seems to be running just fine. > > Is that likely the cause of the above message? If so, is deleting the > paniclog the proper way to stop receiving these e-mails? > > Marc > Next time, before just powering down the system, you should try the Magic SysRq keyboard shortcuts to see if the kernel is still responding. https://www.kernel.org/doc/html/latest/admin-guide/sysrq.html I like to follow the example used on the Wikipedia page which lists the Alt+SysRq+REISUB keys for doing a safer reboot than simply just hitting the physical power button. I try to leave a few of seconds at least in between key presses, to give time for each command to process completely. https://en.m.wikipedia.org/wiki/Magic_SysRq_key -- Tom___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] exim paniclog
On 5/31/21 1:10 PM, g4sra via Dng wrote: No, don't delete it, empty it, this should be the standard practice when manually manipulating daemon log files. I have emptied the paniclog, per you prior directions. Thanks. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] exim paniclog
On 5/31/21 12:36 PM, Antony Stone wrote: On Monday 31 May 2021 at 21:25:18, Marc Shapiro via Dng wrote: I couldn't even switch to a terminal where I could kill Firefox. I finally had to simply power down the system. (How I hate doing that!) Hint for the future - if you have sshd running on this machine, you may well find you can log in to it from elsewhere and tell it to "reboot". That will at least shut processes down cleanly (migth take a while) and unmount your file systems cleanly. Thanks for the tip. I have used sftp from my Android phone for transferring files to and from the phone, but had not tried ssh directly. I have installed an ssh app and it seems to work nicely. I hope I will not actually need to use it. Marc ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] exim paniclog
‐‐‐ Original Message ‐‐‐ On Monday, May 31, 2021 8:43 PM, Antony Stone wrote: > On Monday 31 May 2021 at 21:37:30, g4sra via Dng wrote: > > > > Is deleting the paniclog the proper way to stop receiving these e-mails? > > > > No, don't delete it, empty it, this should be the standard practice when > > manually manipulating daemon log files. > > Hm, why do you say that? Because I was taught to do it this way and the reasoning fits. > > Surely you want exim to open a new log file when it has something new to > report. To do that you would also need to to shut down and restart exim. > If you do not delete the log file but simply write "nothing" to it in order to > empty it, won't the daemon keep the current write position and then get > confused when the file is smaller? No. It actually appends the next write the the 'nothing' already in the file (the filepointer is moved by writing nothing, remember the OS filesystem holds the filepointer, exim holds a file descriptor). Historically, not all daemons will create their log files, they will silently omit logging if they do not pre-exist. Some daemons will not write to existing log files unless they have correct ownership and permissions (for security, plain text passwords in log files, or daemons that drop privileges). Deleting a file does not delete any file descriptors held by other processes those processes will continue to write to the original file (it is possible to recover an unintentionally deleted file providing a process is holding a file descriptor as until it does, the file space is not unallocated for reuse). Alternatively to my suggestion you could... stop exim delete /var/log/exim4/paniclog recreate /var/log/exim4/paniclog with the correct user/mode permissions start exim I am both 'Old School' and lazy. publickey - g4sra@protonmail.com - 0x42E94623.asc Description: application/pgp-keys signature.asc Description: OpenPGP digital signature ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] exim paniclog
On Mon, 31 May 2021 21:43:54 +0200 Antony Stone wrote: > On Monday 31 May 2021 at 21:37:30, g4sra via Dng wrote: > > > > Is deleting the paniclog the proper way to stop receiving these > > > e-mails? > > > > No, don't delete it, empty it, this should be the standard practice > > when manually manipulating daemon log files. > > Hm, why do you say that? > > Surely you want exim to open a new log file when it has something new > to report. > > If you do not delete the log file but simply write "nothing" to it in > order to empty it, won't the daemon keep the current write position > and then get confused when the file is smaller? > > > Antony. > Hi, wouldn't the daemon simply append to the end of the log file? Ciao, Tito ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] exim paniclog
On Monday 31 May 2021 at 21:37:30, g4sra via Dng wrote: > > Is deleting the paniclog the proper way to stop receiving these e-mails? > > No, don't delete it, empty it, this should be the standard practice when > manually manipulating daemon log files. Hm, why do you say that? Surely you want exim to open a new log file when it has something new to report. If you do not delete the log file but simply write "nothing" to it in order to empty it, won't the daemon keep the current write position and then get confused when the file is smaller? Antony. -- Software development can be quick, high quality, or low cost. The customer gets to pick any two out of three. Please reply to the list; please *don't* CC me. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] exim paniclog
‐‐‐ Original Message ‐‐‐ On Monday, May 31, 2021 8:25 PM, Marc Shapiro via Dng wrote: > I received this e-mail yesterday, and again today: > > --- > > exim paniclog /var/log/exim4/paniclog on quixote.home has non-zero size, mail > system might be broken. The last 10 lines are quoted below. > > 2021-05-29 19:35:47 daemon: fork of queue-runner process failed: Cannot > allocate memory > > --- > > I use Thunderbird for all non-local mail. > I am only using exim for local mail. > The only mail that I receive locally is a weekly e-mail from a cron job that > I have set up to do backups, and I did receive that e-mail yesterday, along > with the above e-mail. > > I'm not familiar with the workings of exim, or any MTA, so I don't really > know what the error message means, other than that there was some memory > issue. The one clue that I have is that something (I am fairly sure that it > was a Firefox tab) completely locked my system on Saturday night. Everything > started slowing down. Mousing became erratic. Then everything completely > stopped. I couldn't even switch to a terminal where I could kill Firefox. I > finally had to simply power down the system. (How I hate doing that!) Then I > rebooted, did a controlled shutdown and rebooted, again. After that, > everything seems to be running just fine. > > Is that likely the cause of the above message? Yes > If so, is deleting the paniclog the proper way to stop receiving these > e-mails? No, don't delete it, empty it, this should be the standard practice when manually manipulating daemon log files. The easiest way, with root permissions to literally redirect nothing to the log file (omit the double-quotes). ">/var/log/exim4/paniclog" > > Marc > > Dng mailing list > Dng@lists.dyne.org > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng publickey - g4sra@protonmail.com - 0x42E94623.asc Description: application/pgp-keys signature.asc Description: OpenPGP digital signature ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] exim paniclog
On Monday 31 May 2021 at 21:25:18, Marc Shapiro via Dng wrote: > I received this e-mail yesterday, and again today: > > - > exim paniclog /var/log/exim4/paniclog on quixote.home has non-zero size, > mail system might be broken. The last 10 lines are quoted below. > > 2021-05-29 19:35:47 daemon: fork of queue-runner process failed: Cannot > allocate memory > - > The one clue that I have is that something (I am fairly sure that it was a > Firefox tab) completely locked my system on Saturday night. Everything > started slowing down. Mousing became erratic. Then everything completely > stopped. That certainly sounds like Firefox eating all memory (and probably going through the swap space too). > I couldn't even switch to a terminal where I could kill Firefox. I finally > had to simply power down the system. (How I hate doing that!) Hint for the future - if you have sshd running on this machine, you may well find you can log in to it from elsewhere and tell it to "reboot". That will at least shut processes down cleanly (migth take a while) and unmount your file systems cleanly. > Is that likely the cause of the above message? If so, is deleting the > paniclog the proper way to stop receiving these e-mails? I would say yes to both. Aside from anything else, unless you get further problems, you don't want to be continually reminded about something that happened on the 29th May. Antony. -- Salad is what food eats. Please reply to the list; please *don't* CC me. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
