Ubuntu
zoneminder package

smtp problems, zoneminder? cause of games crashing?

Asked by newmaniax

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_get_networks_cb(): error received: org.freedesktop.NetworkManagerInfo.NoNetworks - There are no wireless networks stored..
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_xioerror_handler: Fatal X error - Restarting :0
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_get_networks_cb(): error received: org.freedesktop.NetworkManagerInfo.NoNetworks - There are no wireless networks stored..
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(sudo:auth): authentication failure; logname= uid=0 euid=0 tty= ruser= rhost= user=newmaniax
Aug 2 12:39:24 newmaniax gnome-keyring-daemon[27339]: couldn't read 4 bytes from client:
Aug 2 12:39:34 newmaniax last message repeated 2 times
Aug 2 12:44:39 newmaniax gnome-keyring-daemon[27339]: couldn't read 4 bytes from client:
Aug 2 12:44:39 newmaniax gnome-keyring-daemon[27339]: couldn't read 4 bytes from client:
Aug 2 12:49:41 newmaniax gnome-keyring-daemon[27339]: couldn't read 4 bytes from client:
Aug 2 12:49:44 newmaniax last message repeated 3 times
Aug 2 12:54:34 newmaniax gnome-keyring-daemon[27339]: couldn't read 4 bytes from client:
Aug 2 12:54:34 newmaniax gnome-keyring-daemon[27339]: couldn't read 4 bytes from client:
Aug 2 12:59:33 newmaniax gnome-keyring-daemon[27339]: couldn't read 4 bytes from client:
Aug 2 12:59:33 newmaniax gnome-keyring-daemon[27339]: couldn't read 4 bytes from client:
Aug 2 13:04:33 newmaniax gnome-keyring-daemon[27339]: couldn't read 4 bytes from client:
Aug 2 13:04:33 newmaniax gnome-keyring-daemon[27339]: couldn't read 4 bytes from client:
Aug 2 13:09:01 newmaniax CRON[23019]: pam_unix(cron:session): session opened for user root by (uid=0)
Aug 2 13:09:01 newmaniax CRON[23019]: pam_unix(cron:session): session closed for user root
Aug 2 13:09:35 newmaniax gnome-keyring-daemon[27339]: couldn't read 4 bytes from client:
Aug 2 13:09:35 newmaniax gnome-keyring-daemon[27339]: couldn't read 4 bytes from client:
Aug 2 13:14:33 newmaniax gnome-keyring-daemon[27339]: couldn't read 4 bytes from client:

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/gnome-system-log
NonfreeKernelModules: nvidia
Package: gnome-utils 2.20.0.1-1ubuntu5
PackageArchitecture: amd64
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-utils
Uname: Linux 2.6.24-19-generic x86_64

Question information

Language:
English Edit question
Status:
Answered
For:
Ubuntu zoneminder Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
newmaniax (newmaniax) said : 		#1
Revision history for this message
Patrick Kilgore (patrick-kilgore) said : 		#2

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Thank you for having taken the time to report this bug to help make
Ubuntu better. You reported this bug a while ago and there hasn't been
any activity in it recently. We were wondering is this still an issue
for you? Can you try with latest Ubuntu release? Thanks in advance.

 subscribe
 status incomplete
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: http://getfiregpg.org

iEYEARECAAYFAkk/OwoACgkQZaGzTLr7X3WakwCcDsW8Y9vWXlEPGR2wIem9JJaG
gnEAnj8AyZ6SVUbGu61qFk8mcn/ILakX
=OhXG
-----END PGP SIGNATURE-----

Revision history for this message
Pedro Villavicencio (pedro) said : 		#3

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.

Revision history for this message
Notch-1 (n1-notch-1) said : 		#4

ubuntu jaunty, same issue, syslogd is filling my disk with nullmailer errors in /var/log/mail.* and /var/log/syslog:

Oct 23 19:14:17 ghost-server nullmailer[10599]: Sending failed: Host not found
Oct 23 19:14:17 ghost-server nullmailer[10599]: Starting delivery: protocol: smtp host: mail. file: 1256255101.23753
Oct 23 19:14:17 ghost-server nullmailer[1706]: smtp: Failed: Connect failed
Oct 23 19:14:17 ghost-server nullmailer[10599]: Sending failed: Host not found
Oct 23 19:14:17 ghost-server nullmailer[10599]: Starting delivery: protocol: smtp host: mail. file: 1256256002.25927
Oct 23 19:14:17 ghost-server nullmailer[1707]: smtp: Failed: Connect failed
Oct 23 19:14:17 ghost-server nullmailer[10599]: Sending failed: Host not found
Oct 23 19:14:17 ghost-server nullmailer[10599]: Starting delivery: protocol: smtp host: mail. file: 1256256901.28082

and i don't have a clue of wich process is tring to send this mails...

Revision history for this message
Notch-1 (n1-notch-1) said : 		#5

ok, it was cron, i disabled the "useful" auto-sending mail feature (please inform the user of that behavior, i founded a lot of desperate clueless people on many forums)
now i just get some errors from apt, like:

/etc/cron.daily/apt: could not lock the APT cache while performing daily cron job.
Is another package manager working?

how can i configure nullmailer to not make grow /var/spool/nullmailer/queue ? i don't want to sand any mail to my isp, of course...

Revision history for this message
Jonathan Gossage (jgossage) said : 		#6

The issues you describe here are all support issues so I will convert this bug report to a question and answer them in Launchpad Answers.

Revision history for this message
Notch-1 (n1-notch-1) said : 		#7

From my point of view any software that goes boom by itself (with the default configuration) have a bug, don't you think?
Anyway i finally found the right way to forbid cron from sending emails:
MAILTO=""
while other methods like MAILTO=NULL or redirecting the output of each command as somebody suggest, are not always working...
I suggest to set this by default, and send mails only if otherwise specified by the user (i.e MAILTO= not empty, like now, but without the need to add MAILTO="")
thanks

Revision history for this message
Jonathan Gossage (jgossage) said : 		#8

Nullmailer is designed as a simple light-weight relay that allows email messages generated by applications on your system to be delivered to someone who can check them to ensure that there are no problems that need to be addressed. It is not intended for discarding email messages.

The original problem with both posters was that Nullmailer was not configured with a valid relay address so, by design, it would keep trying to resend the messages, believing that the connection failure was a temporary condition whereas, in fact, it was due to an incorrect relay address.

Incidentally, Notch-1, while to have been able to suppress email messages from cron, there are other applications potentially installed on your system that could also generate emails and try to use nullmailer to send them so either you will have to track down each case individually and find a way to suppress the emails from that application or as I would recommend, configure nullmailer with a valid relay address and receive the emails via your ISP so that you will know about potential problems on your system.

Can you help with this problem?

Provide an answer of your own, or ask newmaniax for more information if necessary.

To post a message you must log in.