help with spray

[Kai Wang]

The statistics of the following spray command looks good, but the error message....?

Can somebody give a hint on this? hps1 is the machine where sprayd daemon is running.

Thanks a lot.


hpw2$ spray hps1
sending 1162 packets of lnth 86 to hps1 ...spray: send error RPC_CANT_SENDspray: send error RPC_CANT_SENDspray: send error RPC_CANT_SENDspray: send error RPC_CANT_SEND
in 0.1 seconds elapsed time,
4 packets (0.34%) dropped by hps1
Sent: 8687 packets/sec, 729.6K bytes/sec
Rcvd: 8658 packets/sec, 727.1K bytes/sec

[Shannon Petry]

Looks like hps1 is not configured properly for RPC! and make sure that sprayd is running from inetd by verifying /etc/inetd.conf! By default, the entry is commented out.


man 1m spray
man 1m sprayd

If spray is correctly running from inetd, then you have an RPC problem and not a spray problem.

Regards,
Shannon

[Kai Wang]

Thanks for the good suggestion.

It seems the server side (hps1) is working fine, and I feel the problem is still at the client side. When I use a smaller count number, the error message is gone, even with a larger packet length value.

Does this mean I need to change some parameter on the client?

hpw2$ spray hps1 -c 100 -l 500
sending 100 packets of lnth 502 to hps1 ...
in 0.0 seconds elapsed time,
no packets dropped by hps1
2167 packets/sec, 1062.5K bytes/sec

[Shannon Petry]

What happens if you just use the default?
hps2% spray hps1

I dont think that the RPC error is on the client. Most noticably, RPC errors are generated when the client can not talk to the server for some reason. This can be anything from an invalid request (which may be occuring if the HP-UX or spray do not match versions between the two seats), failure to receive reply(s), invalid responses from the server (which again could happen with version mis-matches). Really with spray, the host spraying just asks RPC if the packets got their and a bit of NFO about them.

Regards,
Shannon