You are not logged in.

#1 2012-03-02 02:55:05

silentsnake
Member
Registered: 2012-02-23
Posts: 57

Errors in error.log – possible fixes?

I have now completed my home server with arch linux, and get everything working like i wanted. :-)
Now i have found some messages within the error log i couldn't find a solution for. It looks like nothing important to me, they sound more like informations than actual errors, but maybe there is some configuration wrong and can be fixed to avoid these messages.

The first one

SP5100 TCO timer: mmio address 0xb8fe00 already in use

occurs during udev on each boot. (I'm running kernel 3.2.8-1-ARCH)

dhcpcd[553]: eth0: sendmsg: Cannot assign requested address

I configure the network via DHCP, and the router decides the ip according to a mac-address/ip-address-look-up-table. I think dhcpcd tries to decide the ip-address in the first place, and fails until the router sends the correct one.

/usr/sbin/crond[613]: (CRON) INFO (Syslog will be used instead of sendmail.): No such file or directory

This is obviously because I don't have sendmail installed. Can I configure cron to use Syslog instead of sendmail? So it doesn't checks for sendmail everytime it is started.

Thanks!

Last edited by silentsnake (2012-03-02 03:02:02)

Offline

#2 2012-03-02 06:57:14

Gcool
Member
Registered: 2011-08-16
Posts: 1,456

Re: Errors in error.log – possible fixes?

silentsnake wrote:
/usr/sbin/crond[613]: (CRON) INFO (Syslog will be used instead of sendmail.): No such file or directory

This is obviously because I don't have sendmail installed. Can I configure cron to use Syslog instead of sendmail? So it doesn't checks for sendmail everytime it is started.

You should be able to solve this by adding "-S" to the "ARGS" line in /etc/conf.d/crond


Burninate!

Offline

#3 2012-03-02 10:09:39

sonoran
Member
From: sonoran desert
Registered: 2009-01-12
Posts: 192

Re: Errors in error.log – possible fixes?

silentsnake wrote:

The first one

SP5100 TCO timer: mmio address 0xb8fe00 already in use

occurs during udev on each boot. (I'm running kernel 3.2.8-1-ARCH)

I get this error on every boot but decided not to worry about it. I have no stability issues, er, make that my computer has no stability issues.

According to this thread https://bbs.archlinux.org/viewtopic.php?id=125482 you can blacklist the offending module.

Last edited by sonoran (2012-03-02 10:10:18)

Offline

#4 2012-03-02 17:32:15

silentsnake
Member
Registered: 2012-02-23
Posts: 57

Re: Errors in error.log – possible fixes?

Thanks! Adding "-s" solved the crond error message. :-)

And if SP5100 doesn't make any troubles I will stay with it for now. Maybe it get fixed sometimes.

Offline

#5 2012-06-19 06:51:35

Mr_Kartoffelsalat
Member
Registered: 2012-04-17
Posts: 29

Re: Errors in error.log – possible fixes?

Gcool wrote:
silentsnake wrote:
/usr/sbin/crond[613]: (CRON) INFO (Syslog will be used instead of sendmail.): No such file or directory

This is obviously because I don't have sendmail installed. Can I configure cron to use Syslog instead of sendmail? So it doesn't checks for sendmail everytime it is started.

You should be able to solve this by adding "-S" to the "ARGS" line in /etc/conf.d/crond

Unfortunately for me that didn't solve the problem. Is there any other way handle the problem?

Offline

#6 2012-06-21 19:08:17

rwd
Member
Registered: 2009-02-08
Posts: 664

Re: Errors in error.log – possible fixes?

You could try this.

Offline

#7 2012-08-13 18:01:13

riccardo
Member
From: IT
Registered: 2012-08-05
Posts: 50

Re: Errors in error.log – possible fixes?

Mr_Kartoffelsalat wrote:
Gcool wrote:
silentsnake wrote:
/usr/sbin/crond[613]: (CRON) INFO (Syslog will be used instead of sendmail.): No such file or directory

This is obviously because I don't have sendmail installed. Can I configure cron to use Syslog instead of sendmail? So it doesn't checks for sendmail everytime it is started.

You should be able to solve this by adding "-S" to the "ARGS" line in /etc/conf.d/crond

Unfortunately for me that didn't solve the problem. Is there any other way handle the problem?

Hello,

also for me this doesn't solve the problem. I tried also to modify /etc/rc.d/crond from

[[ -z "$PID" ]] && /usr/sbin/crond $CRONDARGS &>/dev/null \

to

[[ -z "$PID" ]] && /usr/sbin/crond -s &>/dev/null \

but nothing, the problem persists.

Can someone help me (I also tried to use google)?


Thank you.
Riccardo


Arch Linux x86_64 | GNOME | Genuine Intel® CPU U7300 @ 1.30GHz × 2 | 3,7 GiB | Corsair Force 3 SSD 120 GiB

Offline

#8 2012-08-13 18:06:42

WonderWoofy
Member
From: Los Gatos, CA
Registered: 2012-05-19
Posts: 8,414

Re: Errors in error.log – possible fixes?

The TCO thing I think is the watchdog.  On my system, there are two modules that try to load themselves for that device, there is an iTCO-something, and then there was mei both competing for the same spot.  I ended up blacklisting mei, and all is well.  Some people noted that they noticed power regressions when they did this, but I have not noticed any sugh things.

Offline

#9 2012-08-13 23:29:23

cfr
Member
From: Cymru
Registered: 2011-11-27
Posts: 7,130

Re: Errors in error.log – possible fixes?

Did adding "-s" make no difference? I just tried this and restarted crond. Here's a comparison:

before:

Aug 14 00:01:03 localhost /USR/SBIN/CROND[22645]: (CRON) EXEC FAILED (/usr/sbin/sendmail): No such file or directory

after:

Aug 14 00:23:03 localhost /usr/sbin/crond[23865]: (CRON) INFO (Syslog will be used instead of sendmail.): No such file or directory

I'm not sure why it is still complaining about the lack of file/directory but it has changed from "EXEC FAILED" to "INFO" and is apparently promising to use the log rather than sendmail...


CLI Paste | How To Ask Questions

Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Wireless 8265/8275 | US keyboard w/ Euro | 512G NVMe INTEL SSDPEKKF512G7L

Offline

#10 2012-08-14 05:01:13

riccardo
Member
From: IT
Registered: 2012-08-05
Posts: 50

Re: Errors in error.log – possible fixes?

cfr wrote:

Did adding "-s" make no difference? I just tried this and restarted crond. Here's a comparison:

before:

Aug 14 00:01:03 localhost /USR/SBIN/CROND[22645]: (CRON) EXEC FAILED (/usr/sbin/sendmail): No such file or directory

after:

Aug 14 00:23:03 localhost /usr/sbin/crond[23865]: (CRON) INFO (Syslog will be used instead of sendmail.): No such file or directory

I'm not sure why it is still complaining about the lack of file/directory but it has changed from "EXEC FAILED" to "INFO" and is apparently promising to use the log rather than sendmail...

My log is the second one, but it has never changed, with or not the -s option. I know that with the -s this error, even if it is an info one, will completely desappear: is it true?


Thank you.
Riccardo

Last edited by riccardo (2012-08-14 05:02:03)


Arch Linux x86_64 | GNOME | Genuine Intel® CPU U7300 @ 1.30GHz × 2 | 3,7 GiB | Corsair Force 3 SSD 120 GiB

Offline

#11 2012-08-15 01:13:31

cfr
Member
From: Cymru
Registered: 2011-11-27
Posts: 7,130

Re: Errors in error.log – possible fixes?

Well, it didn't disappear for me but the second one is not reporting an error - "INFO" is, I assume, for "INFORMATION". There's no failure or error reported - except, rather oddly, for the continuing complaint about the lack of file/directory.

But without "-s", I get the "EXEC FAILED" i.e. a real error as it tries and fails to execute sendmail.

I don't know that this is how it is supposed to work. I'm just reported what happened on my machine.


CLI Paste | How To Ask Questions

Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Wireless 8265/8275 | US keyboard w/ Euro | 512G NVMe INTEL SSDPEKKF512G7L

Offline

#12 2012-08-15 10:24:43

riccardo
Member
From: IT
Registered: 2012-08-05
Posts: 50

Re: Errors in error.log – possible fixes?

cfr wrote:

Well, it didn't disappear for me but the second one is not reporting an error - "INFO" is, I assume, for "INFORMATION". There's no failure or error reported - except, rather oddly, for the continuing complaint about the lack of file/directory.

But without "-s", I get the "EXEC FAILED" i.e. a real error as it tries and fails to execute sendmail.

I don't know that this is how it is supposed to work. I'm just reported what happened on my machine.

You are right, this seems to be only an INFO, but this log appears in file errors.log under /var/log. Some users after the -s modification, has no more errors like this in errors.log.

I don't know how to solve.


Thank you.
Riccardo


Arch Linux x86_64 | GNOME | Genuine Intel® CPU U7300 @ 1.30GHz × 2 | 3,7 GiB | Corsair Force 3 SSD 120 GiB

Offline

#13 2012-08-15 10:33:43

skanky
Member
From: WAIS
Registered: 2009-10-23
Posts: 1,847

Re: Errors in error.log – possible fixes?

Firstly are you setting -s or -S? The second one is the one you want as -s has a different meaning.
-s sets the directory of system crontabs, and if you are using it and not pointing to a valid directory, it could give a no such file or directory error. I don't think that's it though.

Secondly, in /etc/conf.d/crond you can see that the log level is set to info. If you set this to a higher level, say warning, then the INFO messages should stop appearing (note, I haven't tried this).

Last edited by skanky (2012-08-15 10:34:38)


"...one cannot be angry when one looks at a penguin."  - John Ruskin
"Life in general is a bit shit, and so too is the internet. And that's all there is." - scepticisle

Offline

#14 2012-08-15 22:40:59

cfr
Member
From: Cymru
Registered: 2011-11-27
Posts: 7,130

Re: Errors in error.log – possible fixes?

That's not what the manual page for crond says. It doesn't mention -S at all but it says -s sends stuff to syslog rather than using sendmail.

Are you saying the manual page is buggy or are we talking about different things?!

Plus that wouldn't explain why the EXEC FAILED error disappears if you add "-s". I should just get an *additional* error in this case, shouldn't I?

Last edited by cfr (2012-08-15 22:43:25)


CLI Paste | How To Ask Questions

Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Wireless 8265/8275 | US keyboard w/ Euro | 512G NVMe INTEL SSDPEKKF512G7L

Offline

#15 2012-08-16 18:58:32

riccardo
Member
From: IT
Registered: 2012-08-05
Posts: 50

Re: Errors in error.log – possible fixes?

skanky wrote:

Firstly are you setting -s or -S? The second one is the one you want as -s has a different meaning.
-s sets the directory of system crontabs, and if you are using it and not pointing to a valid directory, it could give a no such file or directory error. I don't think that's it though.

Secondly, in /etc/conf.d/crond you can see that the log level is set to info. If you set this to a higher level, say warning, then the INFO messages should stop appearing (note, I haven't tried this).

With -s or -S the situatione is the same.

In /etc/conf.d/crond I don't have any log level.


Thank you.
Riccardo


Arch Linux x86_64 | GNOME | Genuine Intel® CPU U7300 @ 1.30GHz × 2 | 3,7 GiB | Corsair Force 3 SSD 120 GiB

Offline

#16 2012-08-16 19:49:06

skanky
Member
From: WAIS
Registered: 2009-10-23
Posts: 1,847

Re: Errors in error.log – possible fixes?

Try changing it to:

CROND_ARGS="-S -l warning"

The valid log levels are in the man page.
Note as I don't use cron, this is untested at my end.


"...one cannot be angry when one looks at a penguin."  - John Ruskin
"Life in general is a bit shit, and so too is the internet. And that's all there is." - scepticisle

Offline

#17 2012-08-17 01:21:33

cfr
Member
From: Cymru
Registered: 2011-11-27
Posts: 7,130

Re: Errors in error.log – possible fixes?

I do use cron and "-S" is *not* in the man page. The man page gives the option as "-s" and that gets rid of the EXEC FAILED option in my case.


CLI Paste | How To Ask Questions

Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Wireless 8265/8275 | US keyboard w/ Euro | 512G NVMe INTEL SSDPEKKF512G7L

Offline

#18 2012-08-20 20:54:36

riccardo
Member
From: IT
Registered: 2012-08-05
Posts: 50

Re: Errors in error.log – possible fixes?

skanky wrote:

Try changing it to:

CROND_ARGS="-S -l warning"

The valid log levels are in the man page.
Note as I don't use cron, this is untested at my end.

Is this the only way to change the log lever on arch? Any config file?


Thank you.
Riccardo


Arch Linux x86_64 | GNOME | Genuine Intel® CPU U7300 @ 1.30GHz × 2 | 3,7 GiB | Corsair Force 3 SSD 120 GiB

Offline

#19 2012-08-20 22:39:20

cfr
Member
From: Cymru
Registered: 2011-11-27
Posts: 7,130

Re: Errors in error.log – possible fixes?

Er... I thought we were talking about a config file. What do you mean?


CLI Paste | How To Ask Questions

Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Wireless 8265/8275 | US keyboard w/ Euro | 512G NVMe INTEL SSDPEKKF512G7L

Offline

#20 2012-08-21 10:22:34

riccardo
Member
From: IT
Registered: 2012-08-05
Posts: 50

Re: Errors in error.log – possible fixes?

cfr wrote:

Er... I thought we were talking about a config file. What do you mean?

If there is somewhere a config file to modify to change the log level on /var/log.


Thank you.
Riccardo


Arch Linux x86_64 | GNOME | Genuine Intel® CPU U7300 @ 1.30GHz × 2 | 3,7 GiB | Corsair Force 3 SSD 120 GiB

Offline

#21 2012-08-21 15:42:05

cfr
Member
From: Cymru
Registered: 2011-11-27
Posts: 7,130

Re: Errors in error.log – possible fixes?

/etc/syslog-ng.conf?

apropos syslog

CLI Paste | How To Ask Questions

Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Wireless 8265/8275 | US keyboard w/ Euro | 512G NVMe INTEL SSDPEKKF512G7L

Offline

#22 2012-08-21 20:24:34

riccardo
Member
From: IT
Registered: 2012-08-05
Posts: 50

Re: Errors in error.log – possible fixes?

cfr wrote:

/etc/syslog-ng.conf?

apropos syslog

yes smile

does this file "decide" all level log of the system?


thank you
riccardo


Arch Linux x86_64 | GNOME | Genuine Intel® CPU U7300 @ 1.30GHz × 2 | 3,7 GiB | Corsair Force 3 SSD 120 GiB

Offline

#23 2012-08-21 21:24:42

skanky
Member
From: WAIS
Registered: 2009-10-23
Posts: 1,847

Re: Errors in error.log – possible fixes?

cfr wrote:

I do use cron and "-S" is *not* in the man page. The man page gives the option as "-s" and that gets rid of the EXEC FAILED option in my case.

Interesting as both -s and -S are in my crond man page:

-s dir directory of system crontabs (defaults to /etc/cron.d)

-S     log  events  to  syslog,  using syslog facility LOG_CRON and identity `crond' (this is the default behavior).


"...one cannot be angry when one looks at a penguin."  - John Ruskin
"Life in general is a bit shit, and so too is the internet. And that's all there is." - scepticisle

Offline

#24 2012-08-21 22:03:21

cfr
Member
From: Cymru
Registered: 2011-11-27
Posts: 7,130

Re: Errors in error.log – possible fixes?

@skanky,

Is it possible that we are using different implementations? That is, I'm using cronie but dcron also provides crond.

From man crond:

SYNOPSIS
       crond [-n | -p | -s | -c | -m<mailcommand>]

       crond -x [ext,sch,proc,pars,load,misc,test,bit]

and:

OPTIONS
       -m     This option allows you to specify a shell command to use for sending Cron  mail  output  instead  of  using
              sendmail(8)  This  command  must accept a fully formatted mail message (with headers) on standard input and
              send it as a mail message to the recipients specified in the mail headers. Specifying the string off  (i.e.
              crond -m off) will disable the sending of mail.

       -n     Tells the daemon to run in the foreground. This can be useful when starting it out of init.

       -p     Allows Cron to accept any user set crontables.

       -c     This option enables clustering support, as described below.

       -s     This  option  will direct Cron to send the job output to the system log using syslog(3).  This is useful if
              your system does not have sendmail(8), installed or if mail is disabled.

       -x     This option allows you to set debug flags.

Last edited by cfr (2012-08-21 22:05:26)


CLI Paste | How To Ask Questions

Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Wireless 8265/8275 | US keyboard w/ Euro | 512G NVMe INTEL SSDPEKKF512G7L

Offline

#25 2012-08-21 22:05:59

cfr
Member
From: Cymru
Registered: 2011-11-27
Posts: 7,130

Re: Errors in error.log – possible fixes?

riccardo wrote:
cfr wrote:

/etc/syslog-ng.conf?

apropos syslog

yes smile

does this file "decide" all level log of the system?

apropos syslog

CLI Paste | How To Ask Questions

Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Wireless 8265/8275 | US keyboard w/ Euro | 512G NVMe INTEL SSDPEKKF512G7L

Offline

Board footer

Powered by FluxBB