[collectd] Troubleshoot starting up collectd service

Pander pander at users.sourceforge.net
Wed Apr 20 21:32:15 CEST 2011


On 2011-04-20 20:16, Mark Moseley wrote:
> On Wed, Apr 20, 2011 at 10:05 AM, Pander <pander at users.sourceforge.net> wrote:
>> On 2011-04-20 18:22, Mark Moseley wrote:
>>> On Wed, Apr 20, 2011 at 8:39 AM, Pander <pander at users.sourceforge.net> wrote:
>>>> On 2011-04-20 17:33, Pander wrote:
>>>>> Hi all,
>>>>>
>>>>> I have installed collectd on Ubuntu server and would like to run its
>>>>> service for receiving data from clients.
>>>>>
>>>>> I have enabled network plugin and uncommented and changed this part:
>>>>>
>>>>>         <Listen "127.0.0.1" "25826">
>>>>>                 SecurityLevel Encrypt
>>>>>                 AuthFile "/etc/collectd/passwd"
>>>>>                 Interface "eth0"
>>>>>         </Listen>
>>>>>
>>>>> and created the passwd file with 'username: password' as contents.
>>>>
>>>> and /var/log/syslog says nothing interesting:
>>>>
>>>> Apr 20 17:34:12 hostname collectd[32172]: Exiting normally.
>>>> Apr 20 17:34:12 hostname collectd[32172]: collectd: Stopping 5 read threads.
>>>> Apr 20 17:34:12 hostname collectd[32172]: rrdtool plugin: Shutting down
>>>> the queue thread. This may take a while.
>>>> Apr 20 17:34:12 hostname collectd[32172]: network plugin: Stopping
>>>> receive thread.
>>>> Apr 20 17:34:12 hostname collectd[32172]: network plugin: Stopping
>>>> dispatch thread.
>>>> Apr 20 17:34:12 hostname collectdmon[32171]: Info: collectd terminated
>>>> with exit status 0
>>>> Apr 20 17:34:12 hostname collectdmon[32171]: Info: shutting down collectdmon
>>>> Apr 20 17:34:14 hostname collectd[5836]: Initialization complete,
>>>> entering read-loop.
>>>>
>>>> and I have checked the ports with nmap (tcp and udp).
>>>>
>>>>> After restarting collectd I don't see a service on port 25826. What
>>>>> should I do to find the problem?
>>>>>
>>>>> Thanks,
>>>
>>> It might not like that you've configured it to try to listen to
>>> 127.0.0.1 on eth0. Does it listen correctly if you change Interface to
>>> "lo"?
>>
>> OK, I will use eth0 because I'd like to accept connections from outside.
>> I have tried with its IP address and eth0.
>>
>> Is nmap the way to check if the port is open te receive connections?
>>
>> One thing has changed, syslog says:
>>
>> Apr 20 19:01:12 hostname collectd[6502]: Initialization complete,
>> entering read-loop.
>> Apr 20 19:02:48 hostname snmpd[1132]: Connection from UDP:
>> [83.96.x.y]:45511->[83.96.x.y]
>>
>> Does this mean it is able to receive?
> 
> Check: "netstat -ulpn" for that port, on the same box you're running
> collectd on. I can't say I've tried it with the SecurityLevel/AuthFile
> stuff turned on before though, so no idea if there are any
> complications there. If there is some other issue, you might want to
> turn LogLevel to debug.

# netstat -ulpn 25826
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address
State       PID/Program name
udp        0      0 0.0.0.0:32820           0.0.0.0:*
        1132/snmpd
udp        0      0 0.0.0.0:161             0.0.0.0:*
        1132/snmpd
udp        0      0 83.96.x.y:25826     0.0.0.0:*
    8226/collectd

Seems OK

> 
> _______________________________________________
> collectd mailing list
> collectd at verplant.org
> http://mailman.verplant.org/listinfo/collectd




More information about the collectd mailing list