SNMP issue - URGENT

[craig.shrimpton]

Dear,
i am switching to cloudlinux, I did not encounter any significant problems,
its just that my SNMP is not normal.
if I run snmpwalk-v 1-c public localhost
I get an error:
TCP-MIB:: tcpInErrs.0 = Counter32: 0
TCP-MIB:: tcpOutRsts.0 = Counter32: 2771
Timeout: No Response from localhost

Ive been running SNMP, such as the above earlier.
[root@<pts/0>solo /root]$ ps aux|grep snmp
root 12607 0.1 0.1 156504 8636? Rl Dec14 0:45 /usr/sbin/snmpd-LSD-Lf /dev/null-p /var/run/snmpd.pid-a

and a glimpse of it as already running SNMP.
I run it again
[root @ <pts/0> solo / root] $ snmpwalk-v 1-c public localhost
SNMPv2-MIB:: sysDescr.0 = STRING: Linux 2.6.18-294.26.1.el5 solo.griyahosting.com
. lve0.7.45xen # 1 SMP Thu Nov 26 12:57:56 EET 2010 x86_64
SNMPv2-MIB:: sysObjectID.0 = OID: NET-SNMP-MIB:: netSnmpAgentOIDs.10
DISMAN-EVENT-MIB:: sysUpTimeInstance = Timeticks: (4315196) 11:59:11.96

but up to the line:

TCP-MIB:: tcpInErrs.0 = Counter32: 0
TCP-MIB:: tcpOutRsts.0 = Counter32: 35 921

After that get problem:

Timeout: No Response from localhost

Can you help me for this problem?
Because I see the results of snmpwalk report is incomplete.

Thanks before,
Ibanez

[ibanez]

effects of these problems: http://www.griyahosting.com/mrtg/solo.html, traffic graph looks down dramatically.

[iseletsk]

We knew about the problem with SNMP, but we didn have a chance to evaluate it/figure out what is causing it. Thanks a lot for your post -- it will save us some time trying to figure out where the issue is.

This is still low priority for us (just a few people are using that functionality, and they told us it is not critical for them), and might take 3-6 months before we fix it. If this is something critical for your -- please, tell us, and we will try to bump it up.

Sorry about that.

[ibanez]

can u help for fix thix ?
because i need this data.
Thanks

Regards,
Ibanez

[lkanter]

Could you please send your snmpd.conf to info at cloudlinux.com ? We also need strace logs of snmpd, please run "strace -ff -o /tmp/snmpd -s 4096 -p <snmpd.pid>" before running snmpwalk and then send us /tmp/snmpd too.

[ibanez]

[<pts/0> root@solo /root]$ cat /etc/snmp/snmpd.conf
com2sec local default public
#com2sec local localhost public
com2sec mynetwork 173.0.51.155/32 public
group MyROGroup v1 local
group MyROGroup v2c local
group MyROGroup usm local
group MyRWGroup v1 mynetwork
group MyRWGroup v2c mynetwork
group MyRWGroup usm mynetwork
view all included .1 80
access MyROGroup "" any noauth exact all none none
access MyRWGroup "" any noauth exact all all none
syslocation "CV. GRIYA DIGITAL PRATAMA - Jl. Lawu Perum Pelita A.14 Karanganyar"
syscontact Ibanez
#interface eth0
#agentaddress 184.107.139.106:161

Monday I will move to a dedicated server, Ill try again if the current cloud-linux running on a dedicated server.
Whether you can give me re-trial on our new dedicated server?

Regards,
Ibanez

[ibanez]

[<pts/0> root@solo /root]$ strace -ff -o /tmp/snmpd -s 4096 -p 10613
Process 10613 attached with 2 threads - interrupt to quit

[<pts/1> root@solo /root]$ ps aux |grep snmp
root 10613 0.2 0.1 158512 8396 ? Tl 16:32 0:08 /usr/sbin/snmpd -Lsd -Lf /dev/null -p /var/run/snmpd.pid -a
root 21267 19.2 0.0 4124 820 pts/0 R+ 17:38 0:31 strace -ff -o /tmp/snmpd -s 4096 -p 10613

X
TCP-MIB::tcpConnRemPort.184.107.139.110.80.175.106.17. 226.3740 = INTEGER: 3740
TCP-MIB::tcpConnRemPort.184.107.139.110.80.175.106.17. 226.3741 = INTEGER: 3741
TCP-MIB::tcpConnRemPort.184.107.139.110.80.175.106.17. 226.3742 = INTEGER: 3742
TCP-MIB::tcpConnRemPort.184.107.139.110.80.175.106.17. 226.3743 = INTEGER: 3743
TCP-MIB::tcpConnRemPort.184.107.139.110.80.204.45.64.2 50.49363 = INTEGER: 49363
TCP-MIB::tcpInErrs.0 = Counter32: 0
TCP-MIB::tcpOutRsts.0 = Counter32: 5632
Timeout: No Response from localhost
[<pts/1> root@solo /root]$

[ibanez]

[<pts/1> root@solo /root]$ cat /etc/issue
CloudLinux Server release 5.5
Kernel \r on an \m

[<pts/1> root@solo /root]$ uname -a
Linux solo.griyahosting.com 2.6.18-294.26.1.el5.lve0.7.49xen #1 SMP Tue Jan 4 17:16:38 EET 2011 x86_64 x86_64 x86_64 GNU/Linux
[<pts/1> root@solo /root]$

[ibanez]

on other server i still getting same error.

any update for this problem ?

Regards,
Ibanez

[iseletsk]

reboot into new kernel.

[iseletsk]

Sorry, wrong thread.
We worked with few customers who said that they had an issue, but at the end it was their settings on the server. After tweaking them it started to work fine.
If you have a problem -- plz, contact support, and we will try to help you.

[devon.michaels61]

I have no problem with this one but i just gave the graph a quick look and that looks like pretty messed up. I am sure that you will have an easier task to get the problem resolved. It is sad that that it would be ranked a low priority, but that is how the business goes. You have to give attention to where the majority lies and to which needs to be upgraded sooner.

[lkanter]

The problem problem with snmp described above could be fixed by adding following line:

view all excluded .1.3.6.1.2.1.6

to snmpd.conf.