This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Console message on KLFIFO flowing

An ASL box at my clients site is spewing this message every three seconds:

Read on closed filehandle at /usr/sbin/psd-watch.pl line 129

Has to do with portscanning, but I'm lost. Can anyone explain what's going on and how to correct it? ASL is still running but it definitely feels quite unconfortable...

Thanks. /Jeroen [:S]

This thread was automatically locked due to age.

Parents

0 Biffa over 23 years ago

1. Make sure you don't have any network interfaces plugged into the same hub/switch. e.g. DON'T plug the LAN and DMZ interface into the same device.
Cancel
Vote Up 0 Vote Down

Cancel
0 Frank Flachenecker over 23 years ago in reply to Biffa

Since uprading from 2.016 to 2.023 we have the same problem. We use 3 nics (ext (eth1), int (eth0) and dmz (etc2)) each connected to a different switch.
Our dmz (eth2) uses two IP-Ranges:
  xx.xx.xx.224/255.255.255.240
  xx.xx.xx.240/255.255.255.248 (alias)
Everything works fine but we are flooded by that  console-messages. Any suggestions?
Cancel
Vote Up 0 Vote Down

Cancel
0 notice over 23 years ago in reply to Frank Flachenecker

Thanks Adam for your suggestion, but that's not the case.

Frank, yes, I think this came after an auto-update. Can't be specific when it started.

Any more suggestions please?
Cancel
Vote Up 0 Vote Down

Cancel

Reply

0 notice over 23 years ago in reply to Frank Flachenecker

Thanks Adam for your suggestion, but that's not the case.

Frank, yes, I think this came after an auto-update. Can't be specific when it started.

Any more suggestions please?
Cancel
Vote Up 0 Vote Down

Cancel

Children

0 Frank Flachenecker over 23 years ago in reply to notice

As we have analyzed, the problem is that the loging-process "/usr/sbin/psd-watch.pl" wants to read from /var/log/kernelpipe (fifo?).

But there is no "kernelpipe" anywhere in our asl-filesystem. Any ideas?

Frank
Cancel
Vote Up 0 Vote Down

Cancel
0 oliver.desch over 23 years ago in reply to Frank Flachenecker

Hi outhere,

the problem was related to an HDD error and
not due to an up2date - we do not delete kernelpipes

read you
o|iver
Cancel
Vote Up 0 Vote Down

Cancel
0 notice over 23 years ago in reply to oliver.desch

Problem went away after going to 2.. Thanks.
Cancel
Vote Up 0 Vote Down

Cancel