Anonymous_User Absent Member.
Absent Member.
1529 views

Install Directory Action - Strange Replication Behavior

I'm trying to work with the "Install Directory" action that transfers all
the files around as one big package (for speed reasons). We tried playing
with this with SP1 first came out, and noticed similar issues. We're trying
again (different bundle this time), and still notice some strange behavior
when uploading files into a "Single Content" package.

What happens is this:

1. We create the install directory action, select a folder, and select
"Upload all files within the source directory as a single package". (About
85MB, 600 files)

2. No errors occur in ZCC when we do this.

3. We wait a few minutes, and publish the bundle.

4. We try to run the bundle on a device, and we get an error about content
not being cached. We try to verify, but it still fails.

5. We look at the "Primary Server Replication Status" under the Settings
tab of the bundle, and we see that the status is "Unavailable" on both of
our Primary servers.

6. We let it sit overnight, and our 1st primary server now has the bundle
content "available", but our second primary server does not. There's no
special settings that would limit this replication. This does not happen
for any other bundle we create either. It only seems to happen when we
upload content into a "single package".

Any suggestions? Any logs to look at?

Thanks!


Labels (2)
0 Likes
4 Replies
shaunpond Absent Member.
Absent Member.

Re: Install Directory Action - Strange Replication Behavior

Ryan,

what are your replication settings?

--

Shaun Pond


0 Likes
ukdtom Absent Member.
Absent Member.

Re: Install Directory Action - Strange Replication Behavior

To add a tad to Shaun.

When you upload a bunch of files for a bundle, that are supposed to be
compressed, it'll be uploaded into a tmp directory, and from there,
compressed.

Then after that, moved into the content-repo

Then after that, replication will start, and I beleave, that this is
done from the origen primary with a copy of the compressed file in yet
another temp dir

As such, could take some time, but nothing that justify 24 hours before
the initial bundle is ready for the origen primary.

As such, I suspect either lack of disk-space, or errors, so...

Anything in the logs ?

--
Tommy Mikkelsen
IT Quality A/S, Denmark
Novell Support Forums SYSOP / NKP

Sorry, but no support through email
Please join http://www.open-horizons.net


Ryan wrote:

> I'm trying to work with the "Install Directory" action that transfers
> all the files around as one big package (for speed reasons). We
> tried playing with this with SP1 first came out, and noticed similar
> issues. We're trying again (different bundle this time), and still
> notice some strange behavior when uploading files into a "Single
> Content" package.
>
> What happens is this:
>
> 1. We create the install directory action, select a folder, and
> select "Upload all files within the source directory as a single
> package". (About 85MB, 600 files)
>
> 2. No errors occur in ZCC when we do this.
>
> 3. We wait a few minutes, and publish the bundle.
>
> 4. We try to run the bundle on a device, and we get an error about
> content not being cached. We try to verify, but it still fails.
>
> 5. We look at the "Primary Server Replication Status" under the
> Settings tab of the bundle, and we see that the status is
> "Unavailable" on both of our Primary servers.
>
> 6. We let it sit overnight, and our 1st primary server now has the
> bundle content "available", but our second primary server does not.
> There's no special settings that would limit this replication. This
> does not happen for any other bundle we create either. It only seems
> to happen when we upload content into a "single package".
>
> Any suggestions? Any logs to look at?
>
> Thanks!


Best Regards Tommy Mikkelsen Denmark Please Report back any success or failure, That way we all learn Sorry, but no support through email "I hate bugs".......Tommy Lee Jones, MIB
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Install Directory Action - Strange Replication Behavior

I've went through all of the replication settings again and again. Then, I
performed some tests.

1. Upload a just a BIG exe file. Replication takes just a little while,
but happens rather quickly.

2. Upload a directory with no sub directories (not checking either box).
Replication happens rather quickly.

3. Upload the same directory, but create a sub-directory and move some of
the files in it (not checking either box). Replication happens rather
quickly.

4. Uploaded the same directory (with sub-directory), but check
single-content, and it would fail. In fact, it would fail over, and over
again.

5. Tried variations for destination directory (C:\windows\temp,
%windir%\temp, and with trailing backslashes).

6. Finally tried renaming the action from "Install Directory" to "Install
Directory Files". Oddly, then things started working.

Now............I can't manage to replicate the issue again. Maybe something
was stuck, somewhere? The logs weren't showing anything strange as I was
going through the initial troubeshooting either. I guess we'll see how this
plays out in the long run.

-Ryan


"Tommy Mikkelsen" <ukdtom@no-mx.forums.novell.com> wrote in message
news:V4Aqq.1057$Uz6.556@kovat.provo.novell.com...
> To add a tad to Shaun.
>
> When you upload a bunch of files for a bundle, that are supposed to be
> compressed, it'll be uploaded into a tmp directory, and from there,
> compressed.
>
> Then after that, moved into the content-repo
>
> Then after that, replication will start, and I beleave, that this is
> done from the origen primary with a copy of the compressed file in yet
> another temp dir
>
> As such, could take some time, but nothing that justify 24 hours before
> the initial bundle is ready for the origen primary.
>
> As such, I suspect either lack of disk-space, or errors, so...
>
> Anything in the logs ?
>
> --
> Tommy Mikkelsen
> IT Quality A/S, Denmark
> Novell Support Forums SYSOP / NKP
>
> Sorry, but no support through email
> Please join http://www.open-horizons.net
>
>
> Ryan wrote:
>
>> I'm trying to work with the "Install Directory" action that transfers
>> all the files around as one big package (for speed reasons). We
>> tried playing with this with SP1 first came out, and noticed similar
>> issues. We're trying again (different bundle this time), and still
>> notice some strange behavior when uploading files into a "Single
>> Content" package.
>>
>> What happens is this:
>>
>> 1. We create the install directory action, select a folder, and
>> select "Upload all files within the source directory as a single
>> package". (About 85MB, 600 files)
>>
>> 2. No errors occur in ZCC when we do this.
>>
>> 3. We wait a few minutes, and publish the bundle.
>>
>> 4. We try to run the bundle on a device, and we get an error about
>> content not being cached. We try to verify, but it still fails.
>>
>> 5. We look at the "Primary Server Replication Status" under the
>> Settings tab of the bundle, and we see that the status is
>> "Unavailable" on both of our Primary servers.
>>
>> 6. We let it sit overnight, and our 1st primary server now has the
>> bundle content "available", but our second primary server does not.
>> There's no special settings that would limit this replication. This
>> does not happen for any other bundle we create either. It only seems
>> to happen when we upload content into a "single package".
>>
>> Any suggestions? Any logs to look at?
>>
>> Thanks!

>



0 Likes
shaunpond Absent Member.
Absent Member.

Re: Install Directory Action - Strange Replication Behavior

Ryan,

> Maybe something
> was stuck, somewhere?


always possible - you'd need to go through the logs, or write it off to
experience 🙂

--

Shaun Pond


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.