Re: /etc/cron.daily/spamassassin - Update failed, exiting with code 4

2016-05-14 Thread Reindl Harald
Am 14.05.2016 um 21:42 schrieb Bill Keenan: Bob, the chown fixed the problem. Reindl, your answer seems to be describing a very different installation from 'sudo apt install spamassassin’. Am I correctly understanding the changes you are recommending? it has not to do anything with the

Re: /etc/cron.daily/spamassassin - Update failed, exiting with code 4

2016-05-14 Thread Bill Keenan
Bob, the chown fixed the problem. Reindl, your answer seems to be describing a very different installation from 'sudo apt install spamassassin’. Am I correctly understanding the changes you are recommending? > On May 14, 2016, at 11:31 AM, Reindl Harald wrote: > > >

Re: /etc/cron.daily/spamassassin - Update failed, exiting with code 4

2016-05-14 Thread Reindl Harald
Am 14.05.2016 um 20:09 schrieb Bob Proulx: I see start-stop-daemon and so assume you are running either Debian or Ubuntu where the process runs as a non-root user. As can be seen the --chuid debian-spamd:debian-spamd option runs the process as a non-root user. But very commonly people

Re: /etc/cron.daily/spamassassin - Update failed, exiting with code 4

2016-05-14 Thread Bob Proulx
Bill Keenan wrote: > > > env -i LANG="$LANG" PATH="$PATH" start-stop-daemon \ > > > --chuid debian-spamd:debian-spamd --start \ > > > --exec /usr/bin/sa-update -- -v \ > > > --gpghomedir /var/lib/spamassassin/sa-update-keys 2>&1 > > RW wrote: > > 23 Write error. Curl couldn't write

Re: /etc/cron.daily/spamassassin - Update failed, exiting with code 4

2016-05-14 Thread Bill Keenan
John, the errors I showed were from adding a -v to the /bin/sh and doing sudo spamassissin. RW, thanks for looking up the cURL error. I was so focused on googling, I failed to RTM. I don’t know why, but I have something to focus my investigation on. > On May 14, 2016, at 4:18 AM, RW

Re: /etc/cron.daily/spamassassin - Update failed, exiting with code 4

2016-05-14 Thread RW
On Fri, 13 May 2016 14:57:02 -0700 Bill Keenan wrote: > Googling this turns up some speculation…are the 4 curls failing > because of a mirror problem? Shame on me for not watching…I do not > know when this error started to occur. If there is a fix, where is it > documented? > > Bill > >

Re: /etc/cron.daily/spamassassin - Update failed, exiting with code 4

2016-05-13 Thread John Hardin
On Fri, 13 May 2016, Bill Keenan wrote: Googling this turns up some speculation…are the 4 curls failing because of a mirror problem? Shame on me for not watching…I do not know when this error started to occur. If there is a fix, where is it documented? Bill SpamAssassin version 3.4.1

/etc/cron.daily/spamassassin - Update failed, exiting with code 4

2016-05-13 Thread Bill Keenan
Googling this turns up some speculation…are the 4 curls failing because of a mirror problem? Shame on me for not watching…I do not know when this error started to occur. If there is a fix, where is it documented? Bill SpamAssassin version 3.4.1 running on Perl version 5.20.2 # Update umask