Author Topic: Error messages  (Read 3130 times)

horzella

  • Zen Apprentice
  • *
  • Posts: 7
  • Karma: +0/-0
    • View Profile
Error messages
« on: April 06, 2010, 09:42:23 am »
Hello,

since a few days I get the following error messages. Could somebody help?

Code: [Select]
/etc/cron.daily/apt:
No value set for `/system/http_proxy/use_http_proxy'
No value set for `/system/http_proxy/host'
No value set for `/system/http_proxy/port'
/etc/cron.daily/ebox-ebackup-cron:
Backup module is disabled
/etc/cron.daily/ebox-software:

gzip: stdout: Broken pipe

gzip: stdout: Broken pipe

gzip: stdout: Broken pipe

gzip: stdout: Broken pipe

gzip: stdout: Broken pipe

gzip: stdout: Broken pipe

gzip: stdout: Broken pipe

gzip: stdin: unexpected end of file
parsechangelog/debian: warning:                    -(l0): found eof where expected first heading

gzip: stdout: Broken pipe

gzip: stdout: Broken pipe
tar: *changelog.Debian.gz: Not found in archive
tar: Error exit delayed from previous errors

gzip: stdin: unexpected end of file
parsechangelog/debian: warning:                    -(l0): found eof where expected first heading

gzip: stdout: Broken pipe

gzip: stdout: Broken pipe

gzip: stdout: Broken pipe
tar: *changelog.Debian.gz: Not found in archive
tar: Error exit delayed from previous errors

gzip: stdin: unexpected end of file
parsechangelog/debian: warning:                    -(l0): found eof where expected first heading

gzip: stdout: Broken pipe

gzip: stdout: Broken pipe

gzip: stdout: Broken pipe

gzip: stdout: Broken pipe
parsechangelog/debian: warning:                    -(l1): badly formatted heading line
LINE: 2008-01-24  Raphael Hertzog  <hertzog@debian.org>
parsechangelog/debian: warning:                    -(l2): found blank line where expected first heading
parsechangelog/debian: warning:                    -(l3): unrecognised line
LINE:   * configure.ac: Release 1.14.16.6.
parsechangelog/debian: warning:                    -(l4): found blank line where expected first heading
parsechangelog/debian: warning:                    -(l5): badly formatted heading line
LINE: 2008-01-26  Raphael Hertzog  <hertzog@debian.org>
parsechangelog/debian: warning:                    -(l6): found blank line where expected first heading
parsechangelog/debian: warning:                    -(l7): unrecognised line
LINE:   * scripts/dpkg-gensymbols: Don't scan directories which are
parsechangelog/debian: warning:                    -(l8): unrecognised line
LINE:   symlinks. They might point outside of the package build dir which
parsechangelog/debian: warning:                    -(l9): unrecognised line

...

sixstone

  • Zentyal Staff
  • Zen Hero
  • *****
  • Posts: 1417
  • Karma: +26/-0
    • View Profile
    • Sixstone's blog
Re: Error messages
« Reply #1 on: April 10, 2010, 01:29:26 am »
Hi,

The messages from ebox-software are harmless because they fail to parse a changelog which does not exist at all :).

Cheers,
My secret is my silence...

horzella

  • Zen Apprentice
  • *
  • Posts: 7
  • Karma: +0/-0
    • View Profile
Re: Error messages
« Reply #2 on: April 10, 2010, 07:41:11 am »
Thank you,

but how can I get rid of this messages, because I get an email everyday. (I have installed ssmtp to get emails from root.)

Sincerely

truddick

  • Zen Apprentice
  • *
  • Posts: 2
  • Karma: +0/-0
    • View Profile
Re: Error messages
« Reply #3 on: April 15, 2010, 05:42:25 pm »
Same here: I'm now getting an email every day due to these benign failures.

I realize it probably doesn't seem like a big deal, but noisy unwarranted mail from EBox makes it harder to see when there really is a problem.

Thanks!

sixstone

  • Zentyal Staff
  • Zen Hero
  • *****
  • Posts: 1417
  • Karma: +26/-0
    • View Profile
    • Sixstone's blog
Re: Error messages
« Reply #4 on: April 16, 2010, 10:06:16 am »
Hi all,

You could change the /etc/cron.daily/ebox-software behaviour to redirect the output to /dev/null.

Cheers,
My secret is my silence...

horzella

  • Zen Apprentice
  • *
  • Posts: 7
  • Karma: +0/-0
    • View Profile
Re: Error messages
« Reply #5 on: April 16, 2010, 12:33:36 pm »
Hello,

thank you for the answer. Can you tell me, what I have to do?

Thanks!

truddick

  • Zen Apprentice
  • *
  • Posts: 2
  • Karma: +0/-0
    • View Profile
Re: Error messages
« Reply #6 on: April 16, 2010, 07:20:23 pm »
Hi all,

You could change the /etc/cron.daily/ebox-software behaviour to redirect the output to /dev/null.

Cheers,

Sure, but what happens then if /etc/cron.daily/ebox-software legitimately has an error? I'd never hear about it. The right thing to do is to make the ebox-software script silent unless it has errors that the sysadmin needs to hear about.