openSUSE Forums > Programming/Scripting » failed cron jobs send "attachment.pcx"?

Go Back   openSUSE Forums > Programming/Scripting
Forums FAQ Members List Search Today's Posts Mark Forums Read


Programming/Scripting Questions about programming, bash scripts, perl, php, cron jobs, ruby, python, etc.

Reply
 
LinkBack Thread Tools Display Modes
  #1 (permalink)  
Old 07-May-2009, 12:04
bci bci is offline
Puzzled Penguin
 
Join Date: Mar 2009
Posts: 14
bci hasn't been rated much yet
Question failed cron jobs send "attachment.pcx"?

Dear fellows,

running openSuSE 11.1, we're getting strange error mails from cron. The automatic update cron job sends an empty mail with a strange attachment called "attachment.pcx". As it turns out, this isn't an image, but rather the output of the YOU/zypper command:
Code:
running weekly cronjob scripts

SCRIPT: opensuse.org-online_update exited with RETURNCODE = 103.
SCRIPT: output (stdout && stderr) follows


The following packages are going to be upgraded:
  libqdialogsolver1   libzypp   python-satsolver   satsolver-tools   yast2-pkg-bindings   yast2-qt-pkg   zypper 

The following NEW patch is going to be installed:
  softwaremgmt 

Continue? [YES/no]: yes
Warning: One of installed patches affects the package manager itself. Run this command once more to install any other needed patches.
SCRIPT: opensuse.org-online_update
------- END OF OUTPUT
The only idea I have is that the strange character before [2K is causing postfix to quarantine the text into an attachment, wildly guessing it as being a PCX image...

Other ideas or solutions on how to avoid this...?
Reply With Quote
  #2 (permalink)  
Old 07-May-2009, 13:04
hcvv's Avatar
Wise Penguin
 
Join Date: Jun 2008
Location: Netherlands
Posts: 1,891
hcvv 's reputation will be famous soon enoughhcvv 's reputation will be famous soon enoughhcvv 's reputation will be famous soon enough
Default Re: failed cron jobs send "attachment.pcx"?

IMHO it asks for an answer Yes/No. So it thinks this is an interactiv session allthough it is run in the batch.
It seems that it tells you that the updater itself is involved in the update. Thus it will run this first and it tries to tell you that is has to run a second time to do the normal updates after that.

You better run this at least once interactive (e.g. by using YaST), to get past this answer.
__________________
Henk van Velden
Reply With Quote
  #3 (permalink)  
Old 07-May-2009, 18:30
Flux Capacitor Penguin
 
Join Date: Jun 2008
Location: GMT+10
Posts: 5,200
ken_yap has a reputation to be proud ofken_yap has a reputation to be proud ofken_yap has a reputation to be proud ofken_yap has a reputation to be proud ofken_yap has a reputation to be proud ofken_yap has a reputation to be proud ofken_yap has a reputation to be proud ofken_yap has a reputation to be proud ofken_yap has a reputation to be proud ofken_yap has a reputation to be proud of
Default Re: failed cron jobs send "attachment.pcx"?

Alternatively edit the auto updater policy in YaST to not skip interactive jobs.
Reply With Quote
  #4 (permalink)  
Old 13-May-2009, 02:28
bci bci is offline
Puzzled Penguin
 
Join Date: Mar 2009
Posts: 14
bci hasn't been rated much yet
Thumbs up Solved: failed cron jobs send "attachment.pcx"?

Thanks for the tips!
Interactively running zypper will clear this, of course (the latter idea is too dangerous for us as also kernel updates would then be done silently).

The question remaining is if it is correct behaviour for postfix to treat a file with just one non-printable character as a PCX attachment, rather than sending it as-is...
But this may better be posted in the Applications forum, I guess.

Thanks and "closed".
Reply With Quote
Reply

Bookmarks

Tags
attachment.pcx, failed cron job


Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On




 

Search Engine Friendly URLs by vBSEO 3.3.0 RC2