sort: fflush failed: standard output: Broken pipe

[Matt Zimmerman]

Binary package hint: checksecurity

Recently (the past two days) on my Intrepid system, checksecurity has started to produce an error each night when run from cron.daily:

> Subject: Anacron job 'cron.daily' on mizar

> /etc/cron.daily/checksecurity:
> sort: fflush failed: standard output: Broken pipe
> sort: write error

There are two places where sort(1) is called:

/usr/share/checksecurity/check-setuid: sort -k 12 >$TMPSETUID
/usr/share/checksecurity/check-sockets:/usr/bin/lsof -i -n -P | egrep 'UDP|TCP.*LISTEN' | egrep -v 'UDP.*->.*' |sed 's/....[0-9]u IP.* / /' | sed 's/ FD TYPE DEVICE SIZE NODE NAME/PROTO PORT/' | sed 's/ [0-9][0-9]* / /'|sed 's/ PID / /'| sed -e 's/[ \t]\+/ /g' | sort -u | >>$TMPSOCKET

but I can't reproduce the problem by invoking check-setuid or check-sockets manually.

[Pedro Fragoso (ember)]

Does this happens everytime? Is anyone else able to reproduce this?

lsof -i -n -P | egrep 'UDP|TCP.*LISTEN' | egrep -v 'UDP.*->.*' |sed 's/....[0-9]u IP.* / /' | sed 's/ FD TYPE DEVICE SIZE NODE NAME/PROTO PORT/' | sed 's/ [0-9][0-9]* / /'|sed 's/ PID / /'| sed -e 's/[ \t]\+/ /g' | sort -u

Outputs something?

[Victor Vargas (kamus)]

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!