We have discovered that when the Solaris 10 Hobbit client sends its data to the server the file size of the client data/host data is fairly large. Is there a way to chuck the data into pieces, or to compress the data on the client side, prior to sending, and uncompress on the server side, to parse it in? Dave
-- David S. Morgan CISSP, CCNP aka: captkras at gmail.com
"When the Winds of Change Blow Hard Enough, the Most trivial of things can turn into deadly projectiles"
Can you quantify 'large'? Do these Solaris hosts have a large number of processes running? The process list is probably the culprit. If 'top' (or the solaris equivalent) is being used on the client, then the process list is essentially being duplicated. I usually turn it off at the client end.
Dave Morgan wrote:
We have discovered that when the Solaris 10 Hobbit client sends its data to the server the file size of the client data/host data is fairly large. Is there a way to chuck the data into pieces, or to compress the data on the client side, prior to sending, and uncompress on the server side, to parse it in?
Dave
-- David S. Morgan CISSP, CCNP aka: captkras at gmail.com <mailto:captkras at gmail.com>
"When the Winds of Change Blow Hard Enough, the Most trivial of things can turn into deadly projectiles"
-- Rich Smrcina VM Assist, Inc. Phone: 414-491-6001 Ans Service: 360-715-2467 rich.smrcina at vmassist.com http://www.linkedin.com/in/richsmrcina
Catch the WAVV! http://www.wavv.org WAVV 2009 - Orlando, FL - May 15-19, 2009
Our files are between 20 - 40 MB for the hobbit client data files from Solaris. Under the CPU check, it only shows the uptime, total processes running (about 200) and load. There is no top for this information. Dave
On Mon, Sep 22, 2008 at 11:39 AM, Rich Smrcina <rsmrcina at wi.rr.com> wrote:
Can you quantify 'large'? Do these Solaris hosts have a large number of processes running? The process list is probably the culprit. If 'top' (or the solaris equivalent) is being used on the client, then the process list is essentially being duplicated. I usually turn it off at the client end.
Dave Morgan wrote:
We have discovered that when the Solaris 10 Hobbit client sends its data to the server the file size of the client data/host data is fairly large. Is there a way to chuck the data into pieces, or to compress the data on the client side, prior to sending, and uncompress on the server side, to parse it in?
Dave
-- David S. Morgan CISSP, CCNP aka: captkras at gmail.com <mailto:captkras at gmail.com>
"When the Winds of Change Blow Hard Enough, the Most trivial of things can turn into deadly projectiles"
-- Rich Smrcina VM Assist, Inc. Phone: 414-491-6001 Ans Service: 360-715-2467 rich.smrcina at vmassist.com http://www.linkedin.com/in/richsmrcina
Catch the WAVV! http://www.wavv.org WAVV 2009 - Orlando, FL - May 15-19, 2009
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
-- David S. Morgan CISSP, CCNP aka: captkras at gmail.com
"When the Winds of Change Blow Hard Enough, the Most trivial of things can turn into deadly projectiles"
Anyone have any suggestions on our issue? This seems to be happening only on our Solaris systems. Dave
On Mon, Sep 22, 2008 at 11:50 AM, Dave Morgan <captkras at gmail.com> wrote:
Our files are between 20 - 40 MB for the hobbit client data files from Solaris. Under the CPU check, it only shows the uptime, total processes running (about 200) and load. There is no top for this information. Dave
On Mon, Sep 22, 2008 at 11:39 AM, Rich Smrcina <rsmrcina at wi.rr.com> wrote:
Can you quantify 'large'? Do these Solaris hosts have a large number of processes running? The process list is probably the culprit. If 'top' (or the solaris equivalent) is being used on the client, then the process list is essentially being duplicated. I usually turn it off at the client end.
Dave Morgan wrote:
We have discovered that when the Solaris 10 Hobbit client sends its data to the server the file size of the client data/host data is fairly large. Is there a way to chuck the data into pieces, or to compress the data on the client side, prior to sending, and uncompress on the server side, to parse it in?
Dave
-- David S. Morgan CISSP, CCNP aka: captkras at gmail.com <mailto:captkras at gmail.com>
"When the Winds of Change Blow Hard Enough, the Most trivial of things can turn into deadly projectiles"
-- Rich Smrcina VM Assist, Inc. Phone: 414-491-6001 Ans Service: 360-715-2467 rich.smrcina at vmassist.com http://www.linkedin.com/in/richsmrcina
Catch the WAVV! http://www.wavv.org WAVV 2009 - Orlando, FL - May 15-19, 2009
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
-- David S. Morgan CISSP, CCNP aka: captkras at gmail.com
"When the Winds of Change Blow Hard Enough, the Most trivial of things can turn into deadly projectiles"
-- David S. Morgan CISSP, CCNP aka: captkras at gmail.com
"When the Winds of Change Blow Hard Enough, the Most trivial of things can turn into deadly projectiles"
Dave,
Is this box heavily utilized for network processes...
Mike
From: Dave Morgan [mailto:captkras at gmail.com] Sent: 29 September 2008 17:19 To: hobbit at hswn.dk Subject: Re: [hobbit] Solaris 10
Anyone have any suggestions on our issue? This seems to be happening only on our Solaris systems.
Dave
On Mon, Sep 22, 2008 at 11:50 AM, Dave Morgan <captkras at gmail.com> wrote:
Our files are between 20 - 40 MB for the hobbit client data files from Solaris. Under the CPU check, it only shows the uptime, total processes running (about 200) and load. There is no top for this information.
Dave
On Mon, Sep 22, 2008 at 11:39 AM, Rich Smrcina <rsmrcina at wi.rr.com> wrote:
Can you quantify 'large'? Do these Solaris hosts have a large number of processes running? The process list is probably the culprit. If 'top' (or the solaris equivalent) is being used on the client, then the process list is essentially being duplicated. I usually turn it off at the client end.
Dave Morgan wrote:
We have discovered that when the Solaris 10 Hobbit client sends its data to the server the file size of the client data/host data is fairly large. Is there a way to chuck the data into pieces, or to compress the data on the client side, prior to sending, and uncompress on the server side, to parse it in?
Dave
-- David S. Morgan CISSP, CCNP
aka: captkras at gmail.com <mailto:captkras at gmail.com>
"When the Winds of Change Blow Hard Enough, the Most trivial of things can turn into deadly projectiles"
-- Rich Smrcina VM Assist, Inc. Phone: 414-491-6001 Ans Service: 360-715-2467 rich.smrcina at vmassist.com http://www.linkedin.com/in/richsmrcina
Catch the WAVV! http://www.wavv.org WAVV 2009 - Orlando, FL - May 15-19, 2009
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
-- David S. Morgan CISSP, CCNP aka: captkras at gmail.com
"When the Winds of Change Blow Hard Enough, the Most trivial of things can turn into deadly projectiles"
-- David S. Morgan CISSP, CCNP aka: captkras at gmail.com
"When the Winds of Change Blow Hard Enough, the Most trivial of things can turn into deadly projectiles"
This email has been scanned for all viruses by the MessageLabs service.
This email has been scanned for all viruses by the MessageLabs service.
On Mon, Sep 29, 2008 at 17:19, Dave Morgan <captkras at gmail.com> wrote:
Anyone have any suggestions on our issue? This seems to be happening only on our Solaris systems.
Check the output of the relevant ps command. I had one system that was running a web environment, including java. The resulting ps output was many tens of MBs.
If that isn't it, take a look at the output of the hobbit client and see if anything obvious appears.
-- Please keep list traffic on the list.
Rob MacGregor Whoever fights monsters should see to it that in the process he doesn't become a monster. Friedrich Nietzsche
It looks like it's specific to your system(s) as I run the Hobbit client on a number of Solaris 10 zones, containers and stand-alone servers with no issues. Picking a server at random it delivers a 77Kb packet so you need to look at what the client is actually transferring back.
|\/|
-----Original Message-----
From: Dave Morgan [mailto:captkras at gmail.com]
Sent: 29 September 2008 17:19
To: hobbit at hswn.dk
Subject: Re: [hobbit] Solaris 10
Anyone have any suggestions on our issue? This seems to behappening only on our Solaris systems.
Dave
On Mon, Sep 22, 2008 at 11:50 AM, Dave Morgan<captkras at gmail.com> wrote:
Our files are between 20 - 40 MB for the hobbit clientdata files from Solaris. Under the CPU check, it only shows the uptime, total processes running (about 200) and load. There is no top for this information.
Dave
On Mon, Sep 22, 2008 at 11:39 AM, Rich Smrcina<rsmrcina at wi.rr.com> wrote:
Can you quantify 'large'? Do these Solarishosts have a large number of processes running? The process list is probably the culprit. If 'top' (or the solaris equivalent) is being used on the client, then the process list is essentially being duplicated. I usually turn it off at the client end. Dave Morgan wrote:
We have discovered that when the Solaris10 Hobbit client sends its data to the server the file size of the client data/host data is fairly large. Is there a way to chuck the data into pieces, or to compress the data on the client side, prior to sending, and uncompress on the server side, to parse it in? Dave -- David S. Morgan CISSP, CCNP aka: captkras at gmail.com <mailto:captkras at gmail.com>
"When the Winds of Change Blow HardEnough, the Most trivial of things can turn into deadly projectiles"
--
Rich Smrcina
VM Assist, Inc.
Phone: 414-491-6001
Ans Service: 360-715-2467
rich.smrcina at vmassist.com
http://www.linkedin.com/in/richsmrcina
Catch the WAVV! http://www.wavv.org
WAVV 2009 - Orlando, FL - May 15-19, 2009
To unsubscribe from the hobbit list, send ane-mail to hobbit-unsubscribe at hswn.dk
--
David S. Morgan CISSP, CCNP
aka: captkras at gmail.com
"When the Winds of Change Blow Hard Enough,
the Most trivial of things can turn into deadlyprojectiles"
--
David S. Morgan CISSP, CCNP
aka: captkras at gmail.com
"When the Winds of Change Blow Hard Enough,
the Most trivial of things can turn into deadly projectiles"The message is intended for the named addressee only and may not be disclosed to or used by anyone else, nor may it be copied in any way.
The contents of this message and its attachments are confidential and may also be subject to legal privilege. If you are not the named addressee and/or have received this message in error, please advise us by e-mailing security at colt.net and delete the message and any attachments without retaining any copies.
Internet communications are not secure and COLT does not accept responsibility for this message, its contents nor responsibility for any viruses.
No contracts can be created or varied on behalf of COLT Telecommunications, its subsidiaries or affiliates ("COLT") and any other party by email Communications unless expressly agreed in writing with such other party.
Please note that incoming emails will be automatically scanned to eliminate potential viruses and unsolicited promotional emails. For more information refer to www.colt.net or contact us on +44(0)20 7390 3900.
In <205395ec0809220850w5517cdck61eeae197651fc53 at mail.gmail.com> "Dave Morgan" <captkras at gmail.com> writes:
Our files are between 20 - 40 MB for the hobbit client data files from Solaris. Under the CPU check, it only shows the uptime, total processes running (about 200) and load. There is no top for this information. Dave
Which section of the ~hobbit/tmp/msg.HOSTNAME.txt is that large ? It's usually the "ps" or "ports" listings, but 20-40 MB is really huge (and Hobbit will probably truncate them when they are being received at the Hobbit server).
Henrik
participants (6)
-
captkras＠gmail.com
-
henrik＠hswn.dk
-
Martin.Ward＠colt.net
-
Mike.Rowell＠Rightmove.co.uk
-
rob.macgregor＠gmail.com
-
rsmrcina＠wi.rr.com