Need help getting Loadrunner to work with freeBSD system monitoring rstatd/rup/rsysinfo


Login or Register to Reply

 
Thread Tools Search this Thread
# 1  
Need help getting Loadrunner to work with freeBSD system monitoring rstatd/rup/rsysinfo

Hi there,

I'm trying to use loadrunner with freebsd system monitoring tools like rstatd/rup/rsysinfo, but I keep getting this error from loadrunner:

Code:
Monitor name :UNIX Resources. Internal rpc error (error code:4). Machine: 192.168.1.15. Hint: Check that RPC on this machine is up and running. Check that rstat daemon on this machine is up and running (use rpcinfo utility for this verification). Details: RPC: RPC call failed.
RPC-TCP: recv()/recvfrom() failed.
RPC-TCP: recv()/recvfrom() failed.
WinSock: Connection reset by peer. (entry point: Factory::CollectData).    [MsgId: MMSG-47197]

If i execute this command on my server$ rpcinfo -p
I get the following results:

Code:
   program vers proto   port  service
    100000    4   tcp    111  portmapper
    100000    3   tcp    111  portmapper
    100000    2   tcp    111  portmapper
    100000    4   udp    111  portmapper
    100000    3   udp    111  portmapper
    100000    2   udp    111  portmapper
    100003    2   tcp   2049  nfs
    100003    3   tcp   2049  nfs
    100003    4   tcp   2049  nfs
    100227    2   tcp   2049
    100227    3   tcp   2049
    100003    2   udp   2049  nfs
    100003    3   udp   2049  nfs
    100003    4   udp   2049  nfs
    100227    2   udp   2049
    100227    3   udp   2049
    100021    1   udp  42058  nlockmgr
    100021    3   udp  42058  nlockmgr
    100021    4   udp  42058  nlockmgr
    100021    1   tcp  44271  nlockmgr
    100021    3   tcp  44271  nlockmgr
    100021    4   tcp  44271  nlockmgr
    100005    1   udp  33224  mountd
    100005    1   tcp  36239  mountd
    100005    2   udp  44818  mountd
    100005    2   tcp  50094  mountd
    100005    3   udp  44239  mountd
    100005    3   tcp  39123  mountd
    100024    1   udp  38596  status
    100024    1   tcp  53582  status
    100001    5   udp    967  rstatd
    100001    3   udp    967  rstatd
    100001    2   udp    967  rstatd
    100001    1   udp    967  rstatd

Everything above looks fine, but if I execute this command on the server $ rup localhost

I get the following and no statistics:

Code:
rup: RPC: Success

I believe the problem is related to how I configure rstatd, I have checked multiple times to make sure it is the newest version and I am doing everything right, but I'm stuck and loadrunner can't connect to RCP on my server.

Anyone have any suggestions or recommendations? Smilie
Login or Register to Reply

|
Thread Tools Search this Thread
Search this Thread:
Advanced Search

More UNIX and Linux Forum Topics You Might Find Helpful
Changing script to work with freeBSD
robertkwild
hi all, i have made my machine a freeBSD machine instead of a centos machine and my script doesnt work anymore and i was wondering if anyone can help me into why, i thought the commands are the same, here it is - #!/bin/bash source=/vol/cha-work/_ARCHIVE/to_be_archived/audio...... Programming
9
Programming
freeBSD CPU monitoring using nagios
gsuwal
Hi all, I am not being able to monitor CPU of freeBSD machine from my CentOS server. I have used check_aix_cpu but always gives garbage value, seems wrong in scripting. i want to monitor CPU usage of my freeBSD machine from my centOS server. I am able to monitor many services of that machine...... Infrastructure Monitoring
0
Infrastructure Monitoring
output of command rup
kiranrasane
i have not understood the meaning of output of command rup. try to use this command $ rup <hostname> and then it gives output as given below hostname up 2 days, 7:19, load avarage : 0.02, 0.03, 0.02 does anybody kno about what is load avarage related to ?... UNIX for Advanced & Expert Users
1
UNIX for Advanced & Expert Users
rstatd does not work
toto2000ff
Hi, I'm working with Mercury tools: Loadrunner, and I'm trying to monitor a unix/linux box, the Loadrunner tool uses the rstatd, and I got next error: Mar 4 11:25:56 sacindt rpc.rstatd: incompatible to /proc. Could not read disk_io: data I'm trying to start that deamon, and I use the RUP to...... Linux
1
Linux
UNIX and Linux

Unix (trademarked as the UNIX certification mark) is a very mature family of multitasking, multiuser computer operating systems that evolved from the original AT&T Unix. Unix development starting in the 1970s by legendary Bell Labs programmers Ken Thompson, Dennis Ritchie, and others. Unix was first targeted for the Bell System and AT&T licensed Unix to outside parties. In the 1970s time period, this lead to a variety of for-profit as well as not-for-profit Unix variants.
In the early days, this included the University of California, Berkeley (BSD), Microsoft (Xenix), IBM (AIX), and Sun Microsystems (Solaris). In the early 1990s, AT&T sold their Unix rights to Novell. In 1995 Novell sold their Unix business to the Santa Cruz Operation (SCO). The UNIX trademark was passed to The Open Group, a "neutral" industry consortium. The Open Group promoted the use of the UNIX trademark for certified operating systems that comply with the Single UNIX Specification (SUS). In 2014 Apple's macOS became the Unix version with the largest global install base and macOS remains the largest Unix-user base today.
Linux is a family of open source Unix-like operating systems based on the Linux kernel. The Linux kernel is an operating system kernel first released by Linus Torvalds on 17 September 1991. Linux distributions include the Linux kernel, system software and libraries. Popular free open source Linux distributions include Debian, Fedora, and Ubuntu. Commercial Linux distributions include Red Hat Enterprise Linux and SUSE Linux Enterprise Server. Linux may be freely modified and redistributed. Anyone on the planet may create a Linux distribution for any purpose.
Please enjoy and help our forum community by "showing your work" and posting your code, even when your code is not working as expected. To help others help you, please wrap your code blocks, sample input, sample output, error messages, and other data in CODE tags and wrap your short commands and short data objects in ICODE tags. We were all beginners in the beginning. If you have any questions about how to register or how to post, please contact us in Live Chat. Thank you and enjoy this "forever free" technical support community for UNIX, Linux and computer information technology in general.