Julius schreef:
> On Mon, 2008-12-01 at 10:50 +0100, Thomas Anders wrote:
>   
>> Julius wrote:
>>     
>>>>> Connection from UDP: [127.0.0.1]->[127.0.0.1]:-5226 REFUSED
>>>>> [...]
>>>>>           
>>> On Sun, 2008-11-30 at 18:23 +0100, Jan Houtsma wrote:
>>>       
>>>> Isn't that the same as the one i posted before ("Re: Fedora
>>>> 10+x86_64+snmpd gives segfault in libc-2.9.so at startup")?
>>>>
>>>> The first symptom of snmpd not starting is that you get connection
>>>> errors...... Are you on x86_64?
>>>>         
>>> Yes, its x86_64.
>>> heres a strace output from snmpd starting up: 
>>> http://www.reactos.org/paste/index.php/2451/
>>>
>>> contains a lot lines like this:
>>> close(344)                              = -1 EBADF (Bad file descriptor)
>>>
>>> how can i check if snmpd crashes on libc.so.x ?
>>>
>>> but i doubt that glibc/snmpd versions are a problem here, both were not
>>> updated in my archlinux distribution after the first working
>>> installation.
>>>       
>> A daemon that repeatedly logs
>>
>>   Connection from UDP: [127.0.0.1]->[127.0.0.1]:-5226 REFUSED
>>
>> is obviously running, i.e. has *not* crashed. Please check your tcp-wrapper 
>> configuration, i.e. /etc/hosts.allow and /etc/hosts.deny.
>>
>>
>> +Thomas

Lol. Yes of course. Then it's obviously another issue than i have. For
me the daemon simply crashes as soon as i start it. Also with default
config. Also my log file is completely empty.

Thanks, Jan


-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Net-snmp-users mailing list
[email protected]
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users

Reply via email to