smtp problems, zoneminder? cause of games crashing?
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nullmailer (Debian) |
Confirmed
|
Unknown
|
|||
nullmailer (Ubuntu) |
Triaged
|
Low
|
Unassigned |
Bug Description
These errors are renewed constantly, ie, every minute or so. Please advice
From
Mail.log
Aug 2 13:11:03 newmaniax nullmailer[23056]: smtp: Failed: Connect failed
Aug 2 13:11:03 newmaniax nullmailer[5326]: Sending failed: Host not found
Aug 2 13:11:03 newmaniax nullmailer[5326]: Delivery complete, 9 message(s) remain.
Mail.warn
Aug 2 13:12:14 newmaniax nullmailer[23068]: smtp: Failed: Connect failed
Aug 2 13:12:14 newmaniax nullmailer[5326]: Sending failed: Host not found
Syslog
Aug 2 13:13:14 newmaniax nullmailer[5326]: Rescanning queue.
Aug 2 13:13:14 newmaniax nullmailer[5326]: Starting delivery, 9 message(s) in queue.
Aug 2 13:13:14 newmaniax nullmailer[5326]: Starting delivery: protocol: smtp host: mail. file: 1217000086.8337
Aug 2 13:13:16 newmaniax nullmailer[23069]: smtp: Failed: Connect failed
Aug 2 13:13:16 newmaniax nullmailer[5326]: Sending failed: Host not found
Aug 2 13:13:16 newmaniax nullmailer[5326]: Starting delivery: protocol: smtp host: mail. file: 1217255446.5386
Aug 2 13:13:22 newmaniax nullmailer[23071]: smtp: Failed: Connect failed
Aug 2 13:13:22 newmaniax nullmailer[5326]: Sending failed: Host not found
Aug 2 13:13:22 newmaniax nullmailer[5326]: Starting delivery: protocol: smtp host: mail. file: 1217088773.7787
Aug 2 13:13:23 newmaniax nullmailer[23072]: smtp: Failed: Connect failed
Aug 2 13:13:23 newmaniax nullmailer[5326]: Sending failed: Host not found
Aug 2 13:13:23 newmaniax nullmailer[5326]: Starting delivery: protocol: smtp host: mail. file: 1217628236.20741
Aug 2 13:13:24 newmaniax nullmailer[23073]: smtp: Failed: Connect failed
Aug 2 13:13:24 newmaniax nullmailer[5326]: Sending failed: Host not found
Aug 2 13:13:24 newmaniax nullmailer[5326]: Starting delivery: protocol: smtp host: mail. file: 1217256622.8269
Aug 2 13:13:26 newmaniax nullmailer[23074]: smtp: Failed: Connect failed
Aug 2 13:13:26 newmaniax nullmailer[5326]: Sending failed: Host not found
Aug 2 13:13:26 newmaniax nullmailer[5326]: Starting delivery: protocol: smtp host: mail. file: 1217430094.7321
Aug 2 13:13:27 newmaniax nullmailer[23075]: smtp: Failed: Connect failed
Aug 2 13:13:27 newmaniax nullmailer[5326]: Sending failed: Host not found
Aug 2 13:13:27 newmaniax nullmailer[5326]: Starting delivery: protocol: smtp host: mail. file: 1217368956.5922
Aug 2 13:13:28 newmaniax nullmailer[23076]: smtp: Failed: Connect failed
Aug 2 13:13:28 newmaniax nullmailer[5326]: Sending failed: Host not found
Aug 2 13:13:28 newmaniax nullmailer[5326]: Starting delivery: protocol: smtp host: mail. file: 1217540693.11258
Aug 2 13:13:30 newmaniax nullmailer[23077]: smtp: Failed: Connect failed
Aug 2 13:13:30 newmaniax nullmailer[5326]: Sending failed: Host not found
Aug 2 13:13:30 newmaniax nullmailer[5326]: Starting delivery: protocol: smtp host: mail. file: 1217194524.22425
Aug 2 13:13:31 newmaniax nullmailer[23078]: smtp: Failed: Connect failed
Aug 2 13:13:31 newmaniax nullmailer[5326]: Sending failed: Host not found
Aug 2 13:13:31 newmaniax nullmailer[5326]: Delivery complete, 9 message(s) remain.
Daemon.log
Aug 2 12:12:03 newmaniax NetworkManager: <WARN> nm_dbus_
Aug 2 12:36:23 newmaniax dhclient: DHCPREQUEST of <null address> on eth0 to 10.20.234.29 port 67
Aug 2 12:36:23 newmaniax dhclient: DHCPACK of 10.20.234.30 from 10.20.234.29
Aug 2 12:36:23 newmaniax NetworkManager: <info> DHCP daemon state is now 3 (renew) for interface eth0
Aug 2 12:36:23 newmaniax dhclient: bound to 10.20.234.30 -- renewal in 3520 seconds.
Aug 2 12:39:07 newmaniax gdm[26717]: WARNING: gdm_slave_
Aug 2 12:39:22 newmaniax hcid[5679]: Default passkey agent (:1.233, /org/bluez/passkey) registered
Aug 2 12:39:22 newmaniax hcid[5679]: Default authorization agent (:1.233, /org/bluez/auth) registered
Aug 2 12:39:23 newmaniax NetworkManager: <info> Updating allowed wireless network lists.
Aug 2 12:39:23 newmaniax NetworkManager: <WARN> nm_dbus_
Aug 2 12:57:50 newmaniax ntpd[6359]: no servers reachable
Aug 2 13:02:06 newmaniax ntpd[6359]: synchronized to 91.189.94.4, stratum 2
Auth.log
Aug 2 12:39:22 newmaniax sudo: pam_unix(
Aug 2 12:39:24 newmaniax gnome-keyring-
Aug 2 12:39:34 newmaniax last message repeated 2 times
Aug 2 12:44:39 newmaniax gnome-keyring-
Aug 2 12:44:39 newmaniax gnome-keyring-
Aug 2 12:49:41 newmaniax gnome-keyring-
Aug 2 12:49:44 newmaniax last message repeated 3 times
Aug 2 12:54:34 newmaniax gnome-keyring-
Aug 2 12:54:34 newmaniax gnome-keyring-
Aug 2 12:59:33 newmaniax gnome-keyring-
Aug 2 12:59:33 newmaniax gnome-keyring-
Aug 2 13:04:33 newmaniax gnome-keyring-
Aug 2 13:04:33 newmaniax gnome-keyring-
Aug 2 13:09:01 newmaniax CRON[23019]: pam_unix(
Aug 2 13:09:01 newmaniax CRON[23019]: pam_unix(
Aug 2 13:09:35 newmaniax gnome-keyring-
Aug 2 13:09:35 newmaniax gnome-keyring-
Aug 2 13:14:33 newmaniax gnome-keyring-
Also some full screen games, specifically sauerbraten, crash every five minutes or so, requiring a reboot via Cntl+Alt+Backspace, which is the only key that will work. Is this related to above?
I have tried stopping ZoneMinder, Evolution, and Skype, but System Log continues on the same, clocking up errors every other minute, and Sauerbraten still crashs the system.
I am suspect these messages come from zoneminder, but have no idea how to stop them, and cannot find the specified files or references to them within the computer.
My system is as follows:
OS: Ubuntu 8.04 - the Hardy Heron
PC: AMD Athlon(tm) 64 X2 Dual Core Processor 4000+
m/c: MS-7309 (version 1.0)
Also I have found these errors occur often, not just in my system but in two other Ubuntu pc's I'm aware of.
Evolution is intermittent about how it starts. ie, I have set in sessions "altray evolution" but often evolution starts not in the tray at all and just simply maximized. It tends to be better after a Cntl+Alt+Backspace, but not so often after a full shutdown.
The same is true of the panels. I and my friends set them such that they are both on the bottom. However which one is at the very bottom seems to alternate often after a full shutdown, and not so much after a Cntl+Alt+Backspace reboot. Seems to be a bit better after a recent update, but still not quite right.
Thank you for your assistance, you people are great!
ProblemType: Bug
Architecture: amd64
Date: Sat Aug 2 13:07:10 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/
NonfreeKernelMo
Package: gnome-utils 2.20.0.1-1ubuntu5
PackageArchitec
ProcEnviron:
PATH=/
LANG=en_AU.UTF-8
SHELL=/bin/bash
SourcePackage: gnome-utils
Uname: Linux 2.6.24-19-generic x86_64
Changed in ubuntu: | |
status: | New → Invalid |
Changed in ubuntu: | |
status: | Invalid → Confirmed |
Changed in nullmailer (Debian): | |
status: | Unknown → Confirmed |
Nullmailer retries unsuccessful deliveries forever. As a result, the queue
directory can become very large over time. Since no delivery status
notification is sent for failures, a user who accidentally misenters an
address will have a tough time figuring out what went wrong. Since the
output of mailq doesn't include the envelope addresses of the queued
messages, this problem becomes particularly troublesome to debug for users
without administrative access.
For temporary failures, some code needs to be added to check the age of the /queuelifetime) , the temporary failure should be treated as
queue file. If the queue file is older than a week (perhaps configurable in
/etc/nullmailer
permanent.
For permanent failures, nullmailer should queue a bounce message from the /doublebounceho st and /etc/nullmailer /doublebounceto ).
null envelope sender to the failed message's envelope sender. Once the
bounce has been successfully queued, nullmailer should delete the original
message be deleted from the queue. If queueing of the bounce message fails
for any reason, the original message must not be removed - to do so would
cause mail to be lost silently. As a special case, if the envelope sender of
the failed message is null, nullmailer should give the option to either move
the message from the queue to a special double bounce directory, or to
override the envelope sender of the bounce message to the special address
<#@[]> and the recipient to an administrative address (perhaps configured
using /etc/nullmailer
In the case of a grave misconfiguration where delivery of a message with the
special envelope sender <#@[]> fails, nullmailer should log an error and
delete the message from the queue.
--
Brian Ristuccia
<email address hidden>