Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

bos.net.tcp.client in BROKEN state

207 views
Skip to first unread message

johan

unread,
Feb 2, 2000, 3:00:00 AM2/2/00
to
For some reason I got bos.net.tcp.client.4.3.3.10 in broken
state..
My experiences with packages in broken state is that to solve the
problem you have to install a newer version of the package.
But since 4.3.3.10 is the latest, I'm stuck.

Can someone give me a hint on what to do?!

/Johan


* Sent from RemarQ http://www.remarq.com The Internet's Discussion Network *
The fastest and easiest way to search and participate in Usenet - Free!


Connie L. Graff

unread,
Feb 2, 2000, 3:00:00 AM2/2/00
to

> /Johan

You can try to force install an earlier version. Deinstall may be an option,
but you are likely to get more filesets deinstalled than you want.

--
_/_/_/ _/_/_/ _/_/_/ / Connie L. Graff
_/ _/ _/ _/ _/___ / RS/6000 SP System Test
_/_/_/ _/_/_/ _/ / IBM Poughkeepsie (NY)
_/ _/ _/_/_/ / Internet: cgr...@us.ibm.com

jpa...@my-deja.com

unread,
Feb 2, 2000, 3:00:00 AM2/2/00
to
Connie L. Graff wrote:
> johan (mrplejful...@excite.com.invalid) wrote:
> > For some reason I got bos.net.tcp.client.4.3.3.10 in broken
> > state..
> > My experiences with packages in broken state is that to solve the
> > problem you have to install a newer version of the package.
> > But since 4.3.3.10 is the latest, I'm stuck.
>
> > Can someone give me a hint on what to do?!

>[snip]

> You can try to force install an earlier version. Deinstall may be an
option,
> but you are likely to get more filesets deinstalled than you want.

I was able to do this all but one of the broken filesets. Beucase
there's no method (that I know of anyways) to force an update, nor can
an update be removed. I had to reinstall the base level fileset which
removes all of the updates, then I able to apply the update again.

However, I am unable to force reinstall bos.rte.SRC. I'm assuming this
is because the logic is similar to not being able to remove a bos.rte
fileset? What is interesting is in the output below it thinks 4.3.2.0 is
an 'update' as opposed to a base level fileset. The same occurs if I
attempt to reinstall 4.3.3.0. This did not occur for the other broken
filesets I reinstalled (some X11 and bos.adt filesets).

Is the only solution to reinstall the entire base operating system and
reapply all updates?


Fileset Level Action Status Date
Time

----------------------------------------------------------------------------
Path: /usr/lib/objrepos
bos.rte.SRC
4.3.2.0 COMMIT COMPLETE 10/13/99
12:24:21
4.3.3.0 COMMIT COMPLETE 10/13/99
18:33:05
4.3.3.1 COMMIT COMPLETE 11/09/99
22:33:29
4.3.3.2 COMMIT COMPLETE 12/21/99
23:35:05
4.3.3.10 APPLY BROKEN 01/18/00
22:57:54

Path: /etc/objrepos
bos.rte.SRC
4.3.2.0 COMMIT COMPLETE 10/13/99
12:24:21
4.3.3.1 COMMIT COMPLETE 11/09/99
22:33:29
4.3.3.2 COMMIT COMPLETE 12/21/99
23:35:06


installp -acFNpQqvwX -d /dev/cd0 -V2 -e /var/adm/ras/nim.installp -f
File 2>&1

File:
bos.rte.SRC 4.3.2.0

*******************************************************************************
installp PREVIEW: installation will not actually occur.
*******************************************************************************

+-----------------------------------------------------------------------------+
Pre-installation Verification...
+-----------------------------------------------------------------------------+
Verifying selections...done
Verifying requisites...done
Results...

FAILURES
--------
Filesets listed in this section failed pre-installation verification
and will not be installed.

Force Apply Failures
--------------------
The following is a list of fileset updates. Updates cannot be
specified
from the command line when the force flag (-F) is used in combination
with the apply flag (-a).

bos.rte.SRC 4.3.2.0 # System Resource
Controller

<< End of Failure Section >>

FILESET STATISTICS
------------------
1 Selected to be installed, of which:
1 FAILED pre-installation verification
----
0 Total to be installed

******************************************************************************
End of installp PREVIEW. No apply operation has actually occurred.
******************************************************************************


Sent via Deja.com http://www.deja.com/
Before you buy.

Alex Robinson

unread,
Feb 2, 2000, 3:00:00 AM2/2/00
to
I too have had BROKEN filesets before. I can't remember the exact way I got
around it, but I seem to remember that the solution is in the error message
:

> Force Apply Failures
> --------------------
> The following is a list of fileset updates. Updates cannot be
> specified
> from the command line when the force flag (-F) is used in combination
> with the apply flag (-a).

Try to force (-F) a re-install with COMMIT (-c) rather than APPLY (-a). I
think this works. However, be warned, all filesets in the APPLY state will
be comitted!

Regards,
Alex Robinson

jpa...@my-deja.com

unread,
Feb 2, 2000, 3:00:00 AM2/2/00
to
Alex Robinson <a.rob...@siep.shell.com> wrote:
> I too have had BROKEN filesets before. I can't remember the exact way
I got
> around it, but I seem to remember that the solution is in the error
message
> :
>
> > Force Apply Failures
> > --------------------
> > The following is a list of fileset updates. Updates cannot be
> > specified
> > from the command line when the force flag (-F) is used in
combination
> > with the apply flag (-a).
>
> Try to force (-F) a re-install with COMMIT (-c) rather than APPLY
(-a).

I'm using the Websm GUI to install and the 'commit' option was checked.

"installp -acFNpQqvwX -d /dev/cd0 -V2 -e /var/adm/ras/nim.installp -f
File 2>&1"

Just for kicks I removed the 'apply' flag and tried it from the command
line:

# installp -cFNpQqvwX -d /dev/cd0 bos.rte.SRC 4.3.2.0
0503-416 installp: The -F and -c flags are mutually exclusive.
0503-402 installp: The NO SAVE (-N) option is invalid without
the COMMIT (-c) option.
0503-406 installp: The -d flag is incompatible as given.
0503-406 installp: The -q flag is incompatible as given.
Usage installp: Commit Applied Software Updates (-c):
installp -c [-e LogFile] [-V Number] [-bgpvwX] [-O{[r][s][u]}]
{ FileSet [Level] ... | -f ListFile | all }


Although bos.rte.SRC is the only fileset mentioned when I 'Verify All
Installed Software', I just noticed the following in the installation
history for bos.rte.install (the GUI shows the current version at
4.3.3.3 with an exclamation-point-inside-a-triangle icon. I beginning to
think parts of it are still broken even though 4.3.3.11 was committed.
Perhaps this is causing the problems above. Of course, it makes it
tought to reinstall anything else, like bos.rte.install :)


Fileset Level Action Status Date
Time

----------------------------------------------------------------------------
Path: /usr/lib/objrepos
bos.rte.install


4.3.2.0 COMMIT COMPLETE 10/13/99
12:24:21
4.3.3.0 COMMIT COMPLETE 10/13/99

14:11:26
4.3.3.1 COMMIT COMPLETE 10/13/99
14:47:52
4.3.3.2 COMMIT COMPLETE 12/22/99
23:07:55
4.3.3.3 APPLY BROKEN 01/18/00
22:47:10
4.3.3.10 APPLY BROKEN 01/19/00
20:31:39
4.3.3.11 COMMIT COMPLETE 01/19/00
21:35:44


> I
> think this works. However, be warned, all filesets in the APPLY state
will
> be comitted!
>
> Regards,
> Alex Robinson


Thanks for the reply Alex.

Regards,
Jon

0 new messages