Sponsored Content
Special Forums UNIX and Linux Applications Infrastructure Monitoring net-snmp - restarting too quickly issue Post 302351877 by seg on Wednesday 9th of September 2009 11:11:36 PM
Old 09-10-2009
"Stopping because process dumped core."

I honestly recommend reverting the SMF files back to normal and either writing a new one or using an rc script in rc3.d
 

7 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

net-snmp

Does anybody know where I can get net-snmp for compaq tru64 V4.0G? I am having a difficult time locating it. Can it run on tru64 V4.0G? (2 Replies)
Discussion started by: jalburger
2 Replies

2. Solaris

Net-snmp issue in Solaris 8

Hi there, I know this is a common question, but I have not found a satsifactory solution yet, so pardon me for posting similar questions. My problem is the log /var/adm/messages is filling up with this entry every few minutes Please refer below. Oct 4 21:39:46 host last message repeated 3... (5 Replies)
Discussion started by: sundar63
5 Replies

3. Solaris

Net-SNMP-5.4.2.1 issue on Sun Solaris

Hi, I am trying to compile the source code for Net-SNMP-5.4.2.1 using the gcc compiler-3.4.6 and 3.4.3 but I am getting the follwoing error with perl enabled: /bin/sh ../libtool --mode=link gcc -g -O2 -Usolaris2 -Dsolaris2=solaris2 -fno-strict-aliasing -pipe -Wdeclaration-after-statement... (2 Replies)
Discussion started by: tisha
2 Replies

4. Infrastructure Monitoring

net-snmp issue

When I run a script that polls a router I get the following error from net-snmp. I can not seem to find a straight answer. Could my mib files be corrupt? xxx-xxx:/etc/sma/snmp/mibs# perl /export/home/user/perl/test.pl Unlinked OID in SNMPv2-MIB: snmp ::= { mib-2 11 } Undefined identifier:... (2 Replies)
Discussion started by: mrlayance
2 Replies

5. Solaris

Service is restarting too quickly

Hi guys, one of my services in solaris 10 is in maintenance mode. When I checked why, the reason is that the service is "restarting too quickly." # svcs -x svc:/application/management/snmpdx:default svc:/application/management/snmpdx:default (Sun Solstice Enterprise Master Agent) State:... (2 Replies)
Discussion started by: cjashu
2 Replies

6. HP-UX

Net-snmp 5.7.2 on HP-UX 11.31

Hi All, I have an issue with net-snmp communication from a monitoring server to HP UX server. Following are the details HP - UX server : 172.16.184.34 Monitoring Server : 172.16.5.57 (Solarwinds Application)I'm running HP-UX's snmp on udp port 161 and net-snmp on udp 1161. ... (0 Replies)
Discussion started by: maverick_here
0 Replies

7. Solaris

SSH : Restarting too quickly, changing state to maintenance

Hi, I'm new to Solaris. I have an issue with ssh service. When I restart the service it exits with an exit status of 0 $svcadm restart svc:/network/ssh:default $echo $? 0 $ However, the service goes into maintenance mode after restart. I'm able to connect even though the service is in... (3 Replies)
Discussion started by: maverick_here
3 Replies
gcore(1)						      General Commands Manual							  gcore(1)

NAME
gcore - get core images of running processes SYNOPSIS
filename] process-id... DESCRIPTION
The command creates a core image of each specified process. By default, the name of the core image file for process-id will be The process information in the core file can be obtained by using debuggers. When the command creates a core image of each specified process, the process is temporarily stopped. Further, when the creation of core image is complete, the process continues to execute. Options Creates the core file with name of the file as If multiple process-id values are specified, filename will be common for all the core image files. See the section. Operands process-id The process ID for which a core image file will be created. RETURN VALUE
Upon completion, exits with one of the following values: A core file was successfully created. An error condition was encountered. In such a case, the creation of a core file is not guaranteed. The error conditions could be because of o A nonexistent or incorrect process ID was specified. o An invalid option was specified. o The current working directory of the process or directory from which was invoked had no write permissions. o The current working directory of the process was not accessible. o The file system is full. EXAMPLES
Example 1 Dump the core image of process 1030 in the file "core.1030". Example 2 Dump the core image of the process 1030 in the file "test.1030". Example 3 Dump the core image of the processes 1030, 1031, 1032, and 1033 in the files "core.1030", "core.1031", "core.1032", "core.1033". Example 4 Dump the core image of the processes 1030, 1031, 1032, and 1033 in the files FILES
Core image file for process-id. (Both where is invoked and the current working directory of the process.) AUTHOR
was developed by Chris Bertin (HP). SEE ALSO
adb(1), gdb(1), kill(1), ttrace(2), a.out(4), core(4). gcore(1)
All times are GMT -4. The time now is 11:59 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy