You are not logged in.

#1 2006-04-06 21:11:10

Skyscraper
Member
Registered: 2005-06-20
Posts: 72

ULOGD problem after upgrade (cannot start the daemon)

Hello All,

Recently (Today wink) I've upgraded my Arch box to the Current state of packages (~400MB upgraded KDE, kernel = 1 version hop, ulogd and libs, etc) - my Arch was about 1-2 weeks old. And.... after reboot my firewall got crazy during start. It showed something like that

insmod: can't read 'ip_tables': No such file or direcotry

when it tried to load the module
and

iptables: Unknown error 4294967295
iptables: Unknown error 4294967295
iptables: Unknown error 4294967295
iptables: Unknown error 4294967295
iptables: Unknown error 4294967295
iptables: Unknown error 4294967295
iptables: Unknown error 4294967295

with rules in which I'm using ULOGD for logging.
I've discovered this

Thu Apr  6 22:03:42 2006 <8> ulogd.c:737 unable to create ipulogd handle
ERROR: Unable to bind netlink socket: No such file or directory

when I tried to start ULOGD...
hmmm.... before upgrade everything was right.

When I was working, i tired to start my firewall again and the first error with ip_tables didn't show.

Does Anybody have any ideas what these errors mean?
Thanks smile

Offline

#2 2006-04-06 21:23:19

Skyscraper
Member
Registered: 2005-06-20
Posts: 72

Re: ULOGD problem after upgrade (cannot start the daemon)

Ok I used MODPORBE instead of INSMOD and there is no more ip_tables error, but what about ulogd ?

Offline

Board footer

Powered by FluxBB