Highlighted
Absent Member.
Absent Member.
1735 views

Satellite runs aut of disk space

Hello,

we are using ZCM 11 Sp1 and i installed an additional satellite server
(SLES11 Sp1) in one location. This satellite is configured for content
replication. There seems to be a problem with content replication on
this server. The content-repo on our primary servers (including images)
has a size of 132GB at this time. When the content is replicated to the
satellite this server runs out of disk space. This server has an overall
capacity of 180 GB (and no other apps except OS installed), so the
replication should work without disk-space-problems.
I looked on the satellite: In the tmp-dir (/tmp) there are some files
like "zen_1216813030237948860.tmp" which grow up to 2.4 GB. I'm not sure
why these files are created. How much disk space should be available for
content replication?
The problem started after i ticked "Included" for the pair
Satellite-Primary under "Configuration -> Satellite Server Replication
-> Satellite Server replication Status"
I did this because not all the required bundles were available on the
satellite.
Is the satellite server working correct or may be there something wrong?

Kind regards,
Thomas

Labels (2)
0 Likes
6 Replies
Highlighted
Absent Member.
Absent Member.

Thomas,

It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.

Has your problem been resolved? If not, you might try one of the following options:

- Visit http://support.novell.com and search the knowledgebase and/or check all
the other self support options and support programs available.
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://forums.novell.com)

Be sure to read the forum FAQ about what to expect in the way of responses:
http://forums.novell.com/faq.php

If this is a reply to a duplicate posting, please ignore and accept our apologies
and rest assured we will issue a stern reprimand to our posting bot.

Good luck!

Your Novell Product Support Forums Team
http://forums.novell.com/

0 Likes
Highlighted
Absent Member.
Absent Member.

>Is the satellite server working correct or may be there something wrong?
You are running on the close to maximum. But try asking what the the
Satellite thinks are the size of the content repo: ZAC CDI RS.

To see if files are waiting to be replicated, try: ZAC CDI SS.
If it's missing files, try: ZAC CDP.

Also go to the Content tab of the satelliet and check if nothing is
"Unavailable".

But overall, try running ZAC CVC once or twice every week. You might
find that it has lots of content that has been "left for dead".
This sholud clean out the trash.
If this command hangs, you might be having a stuck worker thread.
Reboot the machine.

Also, make shure you only replicate content at night (1 o'clock,
random 3 hours).

And cut the TFTP replication and use RSYNC in stead. Replicating that
much over TFTP is asking for trouble.

Generally, Windows satellites are more prone to running out of
diskspace, but you are running SLES I see. Make shure the satellite is
doing nothing but the satellite role. No OES, DSfW or other functions
like that.

Hope it helps.

//Mads
0 Likes
Highlighted
Absent Member.
Absent Member.

Mads,

thanks for you info. "ZAC CDI RS" says "Repository Size: 42.92 Gb" but
the Partition size is 170 Gb and still running out of disk space. I'll
check for dead content.

Regards,
Thomas

Am 30.11.2011 10:28, schrieb Mads Andersen:
>> Is the satellite server working correct or may be there something wrong?

> You are running on the close to maximum. But try asking what the the
> Satellite thinks are the size of the content repo: ZAC CDI RS.
>
> To see if files are waiting to be replicated, try: ZAC CDI SS.
> If it's missing files, try: ZAC CDP.
>
> Also go to the Content tab of the satelliet and check if nothing is
> "Unavailable".
>
> But overall, try running ZAC CVC once or twice every week. You might
> find that it has lots of content that has been "left for dead".
> This sholud clean out the trash.
> If this command hangs, you might be having a stuck worker thread.
> Reboot the machine.
>
> Also, make shure you only replicate content at night (1 o'clock,
> random 3 hours).
>
> And cut the TFTP replication and use RSYNC in stead. Replicating that
> much over TFTP is asking for trouble.
>
> Generally, Windows satellites are more prone to running out of
> diskspace, but you are running SLES I see. Make shure the satellite is
> doing nothing but the satellite role. No OES, DSfW or other functions
> like that.
>
> Hope it helps.
>
> //Mads


0 Likes
Highlighted
Absent Member.
Absent Member.

In the meantime i tried to delete the dead content with "ZAC CVC" and
started the replication again:

"zac cdi rs" gives me
Number of packages: 12,595
Repository Size: 39.56 Gb

"zac cdi ss" says:

Synchronization Status
Default: 565 file(s) remaining
Windows-Bundle: 0 file(s) remaining
Imaging: 0 file(s) remaining
12,595 of 13,160 files synchronized (95%)


Over the weekend the disk was running out of disk space again. Nearly
100 GB were created in \tmp and i don't know why.
When i calculate the missing files (5% of 40GB) there are only 2 GB missing.
I'm thinking of opening a SR, this would be the best. I don#t want to
switch to Syncing via rsync.

Regards,
Thomas

0 Likes
Highlighted
Absent Member.
Absent Member.

This issue was seen in ZCM 11 and was fixed (bug 610829). If your content size is huge and your replication time is small (eg., 10 Gb file size and 30 minute of replication time on a slow network), zenworks creates these tmp files to start off from where it left in the next replication schedule. But once all the content is replicated, there is no reason for them to be still lying around.
0 Likes
Highlighted
Absent Member.
Absent Member.

In the meantime i created an SR. The support guys told me change the
Content Replication settings. I changed the Duration to 360 minutes and
now it seems to work, no more tmp-Files are created.

Regards,
Thomas



Am 06.12.2011 05:06, schrieb kvallish:
>
> This issue was seen in ZCM 11 and was fixed (bug 610829). If your
> content size is huge and your replication time is small (eg., 10 Gb file
> size and 30 minute of replication time on a slow network), zenworks
> creates these tmp files to start off from where it left in the next
> replication schedule. But once all the content is replicated, there is
> no reason for them to be still lying around.
>
>


0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.