Re: [OpenIndiana-discuss] Heads up: SSH has been updated to 8.9p1

[Gary Mills]

On Sun, Apr 10, 2022 at 09:15:00PM +0200, Andreas Wacknitz wrote:
> Am 10.04.22 um 20:53 schrieb Gary Mills:
> > Isn't there something in the P5M file that says that the
> > svc:/network/ssh:default service needs to be restarted after the
> > update?
> > 
> No, not yet. Feel free to add something.

I'll leave that change to somebody that actually uses ssh.  I don't.

I see plenty of examples.  Some of them add an attribute to a file,
like these:

database/couchdb-31/couchdb-service.p5m:file files/couchdb-31.xml 
path=lib/svc/manifest/application/couchdb-31.xml 
restart_fmri=svc:/system/manifest-import:default
database/pgadmin/pgadmin.p5m:file files/pgadmin3.desktop 
path=usr/share/applications/pgadmin3.desktop 
restart_fmri=svc:/application/desktop-cache/desktop-mime-cache:default

I suppose that if the P5M file updates the XML file, it must also
import it, and if the P5M file updates a cached file, it must also
re-cache it.

Some of them use a transform, which you might do if you needed to
add the attribute to multiple files.  Here are several examples,
including one that seems to have a typo:

desktop/compiz/compiz.p5m:  default 
restart_fmri svc:/application/desktop-cache/gconf-cache:default>
desktop/compiz/compiz.p5m:  
default restart_fmri svc:/application/desktop-cache/desktop-mime-cache:default>
virtualbox/virtualbox.p5m: 
default restart_fmri svc:/application/virtualbox/run-once:defaul>



-- 
-Gary Mills--refurb--Winnipeg, Manitoba, Canada-

___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] OI Hipster becomes unreachable over network after a certain length of uptime

[Judah Richardson]

OK. The Solaris documentation I linked to says that Solaris (and presumably
distros downstream of that codebase) expects the DHCP server to be another
Solaris machine, and so DHCP servers that don't behave like the latter can
result in unexpected behavior.

On Sun, Apr 10, 2022 at 3:13 PM Stephan Althaus <
stephan.alth...@duedinghausen.eu> wrote:

> On 4/10/22 22:10, Judah Richardson wrote:
> > On Sun, Apr 10, 2022 at 3:07 PM Stephan Althaus <
> > stephan.alth...@duedinghausen.eu> wrote:
> >
> >> On 4/10/22 19:56, Judah Richardson wrote:
> >>> Update: I still get the same 0.0.0.0 messages on reboot:
> >>>
> >>> $ dmesg | grep 0.0.0.0
> >>> Apr 10 12:36:58 DellOptiPlex390MT in.routed[562]: [ID 749644
> >> daemon.notice]
> >>> rge0 has a bad address 0.0.0.0
> >>> Apr 10 12:37:03 DellOptiPlex390MT in.routed[562]: [ID 464608
> >> daemon.error]
> >>> route 0.0.0.0/24 --> 0.0.0.0 nexthop is not directly connected
> >>>
> >>> But as before, the machine acquires the proper IP address once the DE
> >>> starts. We'll see if connectivity fails again ... usually takes 5 to 14
> >>> days to happen.
> >>>
> >>> On Sun, Apr 10, 2022 at 12:47 PM Judah Richardson <
> >> judahrichard...@gmail.com>
> >>> wrote:
> >>>
>  I do notice 0.0.0.0 error messages in the onscreen messages displayed
> at
>  boot, but when the DE launches the status bar popup shows a proper IP
>  address acquisition.
> 
>  Does your machine have a static IP address?
> 
>  FWIW I remembered a Reddit thread
>  <
> >>
> https://www.reddit.com/r/illumos/comments/fndxp7/openindiana_hipster_machine_responds_to_ip/
>  about a similar (related?) OI issue
>   I was having. Someone
>  replied
>  <
> >>
> https://www.reddit.com/r/illumos/comments/fndxp7/openindiana_hipster_machine_responds_to_ip/fl9bdoc/
>  with a solution
>  
> >> that
>  I'd totally forgotten to try because I'd been able to work around the
>  original issue. I implemented the suggested fix just now and did #
> >> reboot.
>  Fingers crossed.
> 
>  On Sun, Apr 10, 2022 at 7:57 AM Stephan Althaus <
>  stephan.alth...@duedinghausen.eu> wrote:
> 
> > On 4/10/22 09:38, Stephan Althaus wrote:
> >> On 4/10/22 04:13, Judah Richardson wrote:
> >>> Finally got around to looking into this ongoing issue.
> >>>
> >>> On Thu, Dec 23, 2021 at 2:28 PM Judah Richardson
> >>> 
> >>> wrote:
> >>>
>  On Thu, Dec 23, 2021 at 11:36 AM s...@pandora.be  >
>  wrote:
> 
> > Do you still have access to a console when the system is
> > 'unreachable'
> > over the network ?
> >
>  Yes, I do.
> 
> > If you still have a text console on the system which became
> > unreachable,
> > perhaps you could check before rebooting whether you can see any
> > errors on
> > the NIC.
> >
> > For example using:
> >
> > # dladm show-link -s rge0
> >
> > When I run the above command on system with a e1000g0 interface,
> it
> > prints IERRORS / OERRORS in the show-link -s e1000g0 output, so
> > hopefully
> > it also prints those statistics for rge0.
> >
>  Doesn't show any errors on this end.
> > Also maybe there are error messages in the /var/adm/messages
> > related to
> > rge0.
> >
>  No errors there either.
> >>> Seems to be a problem within the OS itself, perhaps in relation to
> >> that
> >>> particular NIC.
> >>>
> >>>
>  These are good ideas, thanks. I'll try them next time it happens
> and
>  then
>  report back.
> 
> > Regards,
> > David Stes
> >
> > - Op 22 dec 2021 om 8:56 schreef Judah Richardson
> > judahrichard...@gmail.com:
> >
> >> On Tue, Dec 21, 2021 at 2:06 AM Joshua M. Clulow <
> j...@sysmgr.org
> > wrote:
> >>> On Mon, 20 Dec 2021 at 22:26, Judah Richardson
> >>>  wrote:
>  On Tue, Dec 21, 2021 at 12:23 AM Joshua M. Clulow via
> >>> openindiana-discuss 
> wrote:
> >> Any logs or anything like that in particular I should take a
> > look
> > at?
> > What driver is in use?
>  How do I determine this?
> >>> What do you see in "ipadm show-addr"
> >> $ sudo ipadm show-addr
> >> Password:
> >> ADDROBJ   TYPE STATEADDR
> >> lo0/v4static   ok   127.0.0.1/8
> >> rge0/_b   dhcp ok   192.168.0.71/24
> >> lo0/v6static   ok   ::1/128
> >> rge0/_a   addrconf ok fe80::7a45:c4ff:fe14:10a4/10
> >>
> >> and "dladm 

Re: [OpenIndiana-discuss] OI Hipster becomes unreachable over network after a certain length of uptime

[Stephan Althaus]

On 4/10/22 22:10, Judah Richardson wrote:

On Sun, Apr 10, 2022 at 3:07 PM Stephan Althaus <
stephan.alth...@duedinghausen.eu> wrote:


On 4/10/22 19:56, Judah Richardson wrote:

Update: I still get the same 0.0.0.0 messages on reboot:

$ dmesg | grep 0.0.0.0
Apr 10 12:36:58 DellOptiPlex390MT in.routed[562]: [ID 749644

daemon.notice]

rge0 has a bad address 0.0.0.0
Apr 10 12:37:03 DellOptiPlex390MT in.routed[562]: [ID 464608

daemon.error]

route 0.0.0.0/24 --> 0.0.0.0 nexthop is not directly connected

But as before, the machine acquires the proper IP address once the DE
starts. We'll see if connectivity fails again ... usually takes 5 to 14
days to happen.

On Sun, Apr 10, 2022 at 12:47 PM Judah Richardson <

judahrichard...@gmail.com>

wrote:


I do notice 0.0.0.0 error messages in the onscreen messages displayed at
boot, but when the DE launches the status bar popup shows a proper IP
address acquisition.

Does your machine have a static IP address?

FWIW I remembered a Reddit thread
<

https://www.reddit.com/r/illumos/comments/fndxp7/openindiana_hipster_machine_responds_to_ip/

about a similar (related?) OI issue
 I was having. Someone
replied
<

https://www.reddit.com/r/illumos/comments/fndxp7/openindiana_hipster_machine_responds_to_ip/fl9bdoc/

with a solution


that

I'd totally forgotten to try because I'd been able to work around the
original issue. I implemented the suggested fix just now and did #

reboot.

Fingers crossed.

On Sun, Apr 10, 2022 at 7:57 AM Stephan Althaus <
stephan.alth...@duedinghausen.eu> wrote:


On 4/10/22 09:38, Stephan Althaus wrote:

On 4/10/22 04:13, Judah Richardson wrote:

Finally got around to looking into this ongoing issue.

On Thu, Dec 23, 2021 at 2:28 PM Judah Richardson

wrote:


On Thu, Dec 23, 2021 at 11:36 AM s...@pandora.be 
wrote:


Do you still have access to a console when the system is

'unreachable'

over the network ?


Yes, I do.


If you still have a text console on the system which became
unreachable,
perhaps you could check before rebooting whether you can see any
errors on
the NIC.

For example using:

# dladm show-link -s rge0

When I run the above command on system with a e1000g0 interface, it
prints IERRORS / OERRORS in the show-link -s e1000g0 output, so
hopefully
it also prints those statistics for rge0.


Doesn't show any errors on this end.

Also maybe there are error messages in the /var/adm/messages
related to
rge0.


No errors there either.

Seems to be a problem within the OS itself, perhaps in relation to

that

particular NIC.



These are good ideas, thanks. I'll try them next time it happens and
then
report back.


Regards,
David Stes

- Op 22 dec 2021 om 8:56 schreef Judah Richardson
judahrichard...@gmail.com:


On Tue, Dec 21, 2021 at 2:06 AM Joshua M. Clulow 
wrote:

On Mon, 20 Dec 2021 at 22:26, Judah Richardson
 wrote:

On Tue, Dec 21, 2021 at 12:23 AM Joshua M. Clulow via

openindiana-discuss  wrote:

Any logs or anything like that in particular I should take a

look

at?

What driver is in use?

How do I determine this?

What do you see in "ipadm show-addr"

$ sudo ipadm show-addr
Password:
ADDROBJ   TYPE STATEADDR
lo0/v4static   ok   127.0.0.1/8
rge0/_b   dhcp ok   192.168.0.71/24
lo0/v6static   ok   ::1/128
rge0/_a   addrconf ok fe80::7a45:c4ff:fe14:10a4/10

and "dladm show-ether"?

~$ sudo dladm show-ether
LINKPTYPESTATEAUTO  SPEED-DUPLEX
PAUSE
rge0current  up   no1G-f

none

By

default, NICs are named with the driver you're using; e.g.,
"bge0" is
an instance of the "bge" driver.


What model of NIC is it?

It's an onboard Realtek NIC.

If you "pkg install diagnostic/pci" you should be able to:

   /usr/lib/pci/pcieadm show-devs -o
bdf,vid,did,driver,vendor,device


$ sudo /usr/lib/pci/pcieadm show-devs -o

bdf,vid,did,driver,vendor,device

BDF VID   DID   DRIVER VENDORDEVICE
0/0/0   8086  100   -- Intel Corporation

  2nd

Generation Core Processor Family DRAM Controller
0/2/0   8086  102   i9150  Intel Corporation

  2nd

Generation Core Processor Family Integrated Graphics Controller
0/16/0  8086  1c3a  -- Intel Corporation 6
Series/C200 Series Chipset Family MEI Controller #1
0/1a/0  8086  1c2d  ehci0  Intel Corporation 6
Series/C200 Series Chipset Family USB Enhanced Host Controller #2
0/1b/0  8086  1c20  audiohd0   Intel Corporation 6
Series/C200 Series Chipset Family High Definition Audio Controller
0/1c/0  8086  1c10  -- Intel Corporation 6
Series/C200 Series Chipset Family PCI Express Root Port 1
0/1c/2  8086  1c14  pcieb1 Intel Corporation 6
Series/C200 Series Chipset Family PCI Express Root Port 3
0/1c/4  8086  

Re: [OpenIndiana-discuss] OI Hipster becomes unreachable over network after a certain length of uptime

[Judah Richardson]

On Sun, Apr 10, 2022 at 3:07 PM Stephan Althaus <
stephan.alth...@duedinghausen.eu> wrote:

> On 4/10/22 19:56, Judah Richardson wrote:
> > Update: I still get the same 0.0.0.0 messages on reboot:
> >
> > $ dmesg | grep 0.0.0.0
> > Apr 10 12:36:58 DellOptiPlex390MT in.routed[562]: [ID 749644
> daemon.notice]
> > rge0 has a bad address 0.0.0.0
> > Apr 10 12:37:03 DellOptiPlex390MT in.routed[562]: [ID 464608
> daemon.error]
> > route 0.0.0.0/24 --> 0.0.0.0 nexthop is not directly connected
> >
> > But as before, the machine acquires the proper IP address once the DE
> > starts. We'll see if connectivity fails again ... usually takes 5 to 14
> > days to happen.
> >
> > On Sun, Apr 10, 2022 at 12:47 PM Judah Richardson <
> judahrichard...@gmail.com>
> > wrote:
> >
> >> I do notice 0.0.0.0 error messages in the onscreen messages displayed at
> >> boot, but when the DE launches the status bar popup shows a proper IP
> >> address acquisition.
> >>
> >> Does your machine have a static IP address?
> >>
> >> FWIW I remembered a Reddit thread
> >> <
> https://www.reddit.com/r/illumos/comments/fndxp7/openindiana_hipster_machine_responds_to_ip/
> >
> >> about a similar (related?) OI issue
> >>  I was having. Someone
> >> replied
> >> <
> https://www.reddit.com/r/illumos/comments/fndxp7/openindiana_hipster_machine_responds_to_ip/fl9bdoc/
> >
> >> with a solution
> >> 
> that
> >> I'd totally forgotten to try because I'd been able to work around the
> >> original issue. I implemented the suggested fix just now and did #
> reboot.
> >> Fingers crossed.
> >>
> >> On Sun, Apr 10, 2022 at 7:57 AM Stephan Althaus <
> >> stephan.alth...@duedinghausen.eu> wrote:
> >>
> >>> On 4/10/22 09:38, Stephan Althaus wrote:
>  On 4/10/22 04:13, Judah Richardson wrote:
> > Finally got around to looking into this ongoing issue.
> >
> > On Thu, Dec 23, 2021 at 2:28 PM Judah Richardson
> > 
> > wrote:
> >
> >> On Thu, Dec 23, 2021 at 11:36 AM s...@pandora.be 
> >> wrote:
> >>
> >>> Do you still have access to a console when the system is
> >>> 'unreachable'
> >>> over the network ?
> >>>
> >> Yes, I do.
> >>
> >>> If you still have a text console on the system which became
> >>> unreachable,
> >>> perhaps you could check before rebooting whether you can see any
> >>> errors on
> >>> the NIC.
> >>>
> >>> For example using:
> >>>
> >>> # dladm show-link -s rge0
> >>>
> >>> When I run the above command on system with a e1000g0 interface, it
> >>> prints IERRORS / OERRORS in the show-link -s e1000g0 output, so
> >>> hopefully
> >>> it also prints those statistics for rge0.
> >>>
> >> Doesn't show any errors on this end.
> >>> Also maybe there are error messages in the /var/adm/messages
> >>> related to
> >>> rge0.
> >>>
> >> No errors there either.
> > Seems to be a problem within the OS itself, perhaps in relation to
> that
> > particular NIC.
> >
> >
> >> These are good ideas, thanks. I'll try them next time it happens and
> >> then
> >> report back.
> >>
> >>> Regards,
> >>> David Stes
> >>>
> >>> - Op 22 dec 2021 om 8:56 schreef Judah Richardson
> >>> judahrichard...@gmail.com:
> >>>
>  On Tue, Dec 21, 2021 at 2:06 AM Joshua M. Clulow  >
> >>> wrote:
> > On Mon, 20 Dec 2021 at 22:26, Judah Richardson
> >  wrote:
> >> On Tue, Dec 21, 2021 at 12:23 AM Joshua M. Clulow via
> > openindiana-discuss  wrote:
>  Any logs or anything like that in particular I should take a
> >>> look
> >>> at?
> >>> What driver is in use?
> >> How do I determine this?
> > What do you see in "ipadm show-addr"
>  $ sudo ipadm show-addr
>  Password:
>  ADDROBJ   TYPE STATEADDR
>  lo0/v4static   ok   127.0.0.1/8
>  rge0/_b   dhcp ok   192.168.0.71/24
>  lo0/v6static   ok   ::1/128
>  rge0/_a   addrconf ok fe80::7a45:c4ff:fe14:10a4/10
> 
>  and "dladm show-ether"?
> 
>  ~$ sudo dladm show-ether
>  LINKPTYPESTATEAUTO  SPEED-DUPLEX
>  PAUSE
>  rge0current  up   no1G-f
> >>> none
> By
> > default, NICs are named with the driver you're using; e.g.,
> > "bge0" is
> > an instance of the "bge" driver.
> >
> >>> What model of NIC is it?
> >> It's an onboard Realtek NIC.
> > If you "pkg install diagnostic/pci" you should be able to:
> >
> >   /usr/lib/pci/pcieadm show-devs -o
> > bdf,vid,did,driver,vendor,device
> >
>  $ sudo 

Re: [OpenIndiana-discuss] OI Hipster becomes unreachable over network after a certain length of uptime

[Stephan Althaus]

On 4/10/22 19:56, Judah Richardson wrote:

Update: I still get the same 0.0.0.0 messages on reboot:

$ dmesg | grep 0.0.0.0
Apr 10 12:36:58 DellOptiPlex390MT in.routed[562]: [ID 749644 daemon.notice]
rge0 has a bad address 0.0.0.0
Apr 10 12:37:03 DellOptiPlex390MT in.routed[562]: [ID 464608 daemon.error]
route 0.0.0.0/24 --> 0.0.0.0 nexthop is not directly connected

But as before, the machine acquires the proper IP address once the DE
starts. We'll see if connectivity fails again ... usually takes 5 to 14
days to happen.

On Sun, Apr 10, 2022 at 12:47 PM Judah Richardson 
wrote:


I do notice 0.0.0.0 error messages in the onscreen messages displayed at
boot, but when the DE launches the status bar popup shows a proper IP
address acquisition.

Does your machine have a static IP address?

FWIW I remembered a Reddit thread

about a similar (related?) OI issue
 I was having. Someone
replied

with a solution
 that
I'd totally forgotten to try because I'd been able to work around the
original issue. I implemented the suggested fix just now and did # reboot.
Fingers crossed.

On Sun, Apr 10, 2022 at 7:57 AM Stephan Althaus <
stephan.alth...@duedinghausen.eu> wrote:


On 4/10/22 09:38, Stephan Althaus wrote:

On 4/10/22 04:13, Judah Richardson wrote:

Finally got around to looking into this ongoing issue.

On Thu, Dec 23, 2021 at 2:28 PM Judah Richardson

wrote:


On Thu, Dec 23, 2021 at 11:36 AM s...@pandora.be 
wrote:


Do you still have access to a console when the system is

'unreachable'

over the network ?


Yes, I do.


If you still have a text console on the system which became
unreachable,
perhaps you could check before rebooting whether you can see any
errors on
the NIC.

For example using:

# dladm show-link -s rge0

When I run the above command on system with a e1000g0 interface, it
prints IERRORS / OERRORS in the show-link -s e1000g0 output, so
hopefully
it also prints those statistics for rge0.


Doesn't show any errors on this end.

Also maybe there are error messages in the /var/adm/messages
related to
rge0.


No errors there either.

Seems to be a problem within the OS itself, perhaps in relation to that
particular NIC.



These are good ideas, thanks. I'll try them next time it happens and
then
report back.


Regards,
David Stes

- Op 22 dec 2021 om 8:56 schreef Judah Richardson
judahrichard...@gmail.com:


On Tue, Dec 21, 2021 at 2:06 AM Joshua M. Clulow 

wrote:

On Mon, 20 Dec 2021 at 22:26, Judah Richardson
 wrote:

On Tue, Dec 21, 2021 at 12:23 AM Joshua M. Clulow via

openindiana-discuss  wrote:

Any logs or anything like that in particular I should take a

look

at?

What driver is in use?

How do I determine this?

What do you see in "ipadm show-addr"

$ sudo ipadm show-addr
Password:
ADDROBJ   TYPE STATEADDR
lo0/v4static   ok   127.0.0.1/8
rge0/_b   dhcp ok   192.168.0.71/24
lo0/v6static   ok   ::1/128
rge0/_a   addrconf ok fe80::7a45:c4ff:fe14:10a4/10

and "dladm show-ether"?

~$ sudo dladm show-ether
LINKPTYPESTATEAUTO  SPEED-DUPLEX
PAUSE
rge0current  up   no1G-f

none

   By

default, NICs are named with the driver you're using; e.g.,
"bge0" is
an instance of the "bge" driver.


What model of NIC is it?

It's an onboard Realtek NIC.

If you "pkg install diagnostic/pci" you should be able to:

  /usr/lib/pci/pcieadm show-devs -o
bdf,vid,did,driver,vendor,device


$ sudo /usr/lib/pci/pcieadm show-devs -o

bdf,vid,did,driver,vendor,device

BDF VID   DID   DRIVER VENDORDEVICE
0/0/0   8086  100   -- Intel Corporation 2nd
Generation Core Processor Family DRAM Controller
0/2/0   8086  102   i9150  Intel Corporation 2nd
Generation Core Processor Family Integrated Graphics Controller
0/16/0  8086  1c3a  -- Intel Corporation 6
Series/C200 Series Chipset Family MEI Controller #1
0/1a/0  8086  1c2d  ehci0  Intel Corporation 6
Series/C200 Series Chipset Family USB Enhanced Host Controller #2
0/1b/0  8086  1c20  audiohd0   Intel Corporation 6
Series/C200 Series Chipset Family High Definition Audio Controller
0/1c/0  8086  1c10  -- Intel Corporation 6
Series/C200 Series Chipset Family PCI Express Root Port 1
0/1c/2  8086  1c14  pcieb1 Intel Corporation 6
Series/C200 Series Chipset Family PCI Express Root Port 3
0/1c/4  8086  1c18  pcieb2 Intel Corporation 6
Series/C200 Series Chipset Family PCI Express Root Port 5
3/0/0   10ec  8168  rge0   Realtek 

Re: [OpenIndiana-discuss] can't install a new zone

[Stephan Althaus]

On 4/10/22 15:04, Andreas Wacknitz wrote:

Am 10.04.22 um 14:57 schrieb Stephan Althaus:

On 4/10/22 14:29, Andreas Wacknitz wrote:

Am 10.04.22 um 11:46 schrieb Andreas Wacknitz:

Am 10.04.22 um 11:23 schrieb Stephan Althaus:

On 4/10/22 11:12, Stephan Althaus wrote:

On 4/10/22 10:52, Andreas Wacknitz wrote:

Am 10.04.22 um 10:47 schrieb Stephan Althaus:

On 4/10/22 09:56, Andreas Wacknitz wrote:

Am 09.04.22 um 18:38 schrieb Maurilio Longo via
openindiana-discuss:

No problem Andreas,

it is at 15370

$ pkg info userland-incorporation
  Name: 
consolidation/userland/userland-incorporation

   Summary: userland consolidation incorporation
(consolidation/userland/userland-incorporation)
   Description: This incorporation constrains packages
from the
userland
    consolidation
  Category: Meta Packages/Incorporations
 State: Installed
 Publisher: openindiana.org
   Version: 0.5.11
    Branch: 2022.0.0.15370
    Packaging Date: Sat Apr  9 09:53:00 2022
Last Install Time: Sun Oct 31 19:39:21 2021
  Last Update Time: Sat Apr  9 12:01:18 2022
  Size: 0.00 B
  FMRI:
pkg://openindiana.org/consolidation/userland/userland-incorporation@0.5.11-2022.0.0.15370:20220409T095300Z 






Regards.

Maurilio

I have investigated further and found out that we have some 
actual

problems with old packages that have been replaced in the past.
The problems became imminent after illumos-gate has merged #14583
developer/opensolaris/osnet requirements cleanup and after
shrinking the
repository.
So far I have identified three:
    file/slocate
    runtime/java
    service/network/ftp
and replaced the fmri's with their replacements mlocate, openjdk8
and
proftpd.
There might be more outdated fmri's left that need to be fixed,
though.


___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss


Hi!


There are some packages mentioned that are not in "2022":
This should not be a problem. They just haven't been build this 
year

yet. But you need to make sure that they are still in the
repository,
though.
Eg. pkg info -r compress/bzip2@1.0.8-2020.0.1.0
and are in the userland-incorporation meta package.




# zoneadm -z bz-template install 2>&1 |grep 202|grep -v 2022

 Reject:
pkg://openindiana.org/compress/bzip2@1.0.8-2020.0.1.0:20200330T113433Z 




 Reject:
pkg://openindiana.org/compress/gzip@1.11-2020.0.1.0:20210903T182240Z 



 Reject:
pkg://openindiana.org/compress/unzip@6.0-2020.0.1.5:20200330T113517Z 



 Reject:
pkg://openindiana.org/compress/zip@3.0-2020.0.1.1:20200615T163122Z
 Reject:
pkg://openindiana.org/database/berkeleydb-5@5.3.28-2020.0.1.0:20200330T113744Z 





 Reject:
pkg://openindiana.org/database/lmdb@0.9.23-2020.0.1.0:20200330T113744Z 




 Reject:
pkg://openindiana.org/entire@0.5.11-2020.0.1.0:20200330T151713Z
 Reject:
pkg://openindiana.org/library/libedit@3.1.20181209-2020.0.1.2:20200330T122131Z 





 Reject:
pkg://openindiana.org/library/libxml2@2.9.9-2020.0.1.5:20210117T220316Z 





 Reject:
pkg://openindiana.org/library/pcre2@10.39-2020.0.1.0:2029T235734Z 



 Reject:
pkg://openindiana.org/network/ssh@8.1.0.1-2020.0.1.2:20200512T190142Z 



 Reject:
pkg://openindiana.org/runtime/perl-534@5.34.0-2021.0.0.0:20211229T151048Z 





 Reject:
pkg://openindiana.org/runtime/python-35@3.5.10-2020.0.1.0:20201014T142618Z 





 Reject:
pkg://openindiana.org/service/management/sysding@0.5.11-2020.0.1.33:20200521T214606Z 





 Reject:
pkg://openindiana.org/service/network/ssh@8.1.0.1-2020.0.1.2:20200512T190154Z 





 Reject:
pkg://openindiana.org/system/ca-certificates@0.0.1.20170919-2020.0.1.0:20200330T152439Z 





 Reject:
pkg://openindiana.org/system/library/gcc-7-runtime@7.5.0-2020.0.1.9:20210819T195607Z 






Thank you for having a look at it!

Stephan



___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss



___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss


Hmm...

gnu-tar is a pkg from 2020

$ pkg search -l -H -o pkg.fmri 'depend:require:compress/gzip'
pkg:/install/distribution-constructor@0.5.11-2022.0.0.1057:20220325T145842Z 





pkg:/metapackages/build-essential@1.0-2022.0.0.1:20220117T192224Z
pkg:/archiver/gnu-tar@1.34-2020.0.1.0:20210305T213236Z
pkg:/system/install@0.5.11-2022.0.0.1057:20220325T150012Z

From the manifest of gnu.tar: (source: pkg.openindiana.org/)
dependfmri=pkg:/compress/gzip@1.10-2020.0.1.0 type=require

Maybe this type of dependency is the reason why the zone install
fails, as that required old gzip package is no more available...
???
___

Re: [OpenIndiana-discuss] Heads up: SSH has been updated to 8.9p1

[Andreas Wacknitz]

Am 10.04.22 um 20:53 schrieb Gary Mills:

On Sun, Apr 10, 2022 at 08:10:56PM +0200, Andreas Wacknitz wrote:

As the subject says, I have recently integrated a new version of
openssh. You may need to reboot your machine in order to make the update
work.

Isn't there something in the P5M file that says that the
svc:/network/ssh:default service needs to be restarted after the
update?



No, not yet. Feel free to add something.

___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] Heads up: SSH has been updated to 8.9p1

[Gary Mills]

On Sun, Apr 10, 2022 at 08:10:56PM +0200, Andreas Wacknitz wrote:
> As the subject says, I have recently integrated a new version of
> openssh. You may need to reboot your machine in order to make the update
> work.

Isn't there something in the P5M file that says that the
svc:/network/ssh:default service needs to be restarted after the
update?


-- 
-Gary Mills--refurb--Winnipeg, Manitoba, Canada-

___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

[OpenIndiana-discuss] Heads up: SSH has been updated to 8.9p1

[Andreas Wacknitz]

As the subject says, I have recently integrated a new version of
openssh. You may need to reboot your machine in order to make the update
work.
Otherwise connection attempts may end in messages like this:

kex_exchange_identification: Connection closed by remote host
Connection closed by  port 22

Regards,
Andreas

___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] OI Hipster becomes unreachable over network after a certain length of uptime

[Judah Richardson]

Update: I still get the same 0.0.0.0 messages on reboot:

$ dmesg | grep 0.0.0.0
Apr 10 12:36:58 DellOptiPlex390MT in.routed[562]: [ID 749644 daemon.notice]
rge0 has a bad address 0.0.0.0
Apr 10 12:37:03 DellOptiPlex390MT in.routed[562]: [ID 464608 daemon.error]
route 0.0.0.0/24 --> 0.0.0.0 nexthop is not directly connected

But as before, the machine acquires the proper IP address once the DE
starts. We'll see if connectivity fails again ... usually takes 5 to 14
days to happen.

On Sun, Apr 10, 2022 at 12:47 PM Judah Richardson 
wrote:

> I do notice 0.0.0.0 error messages in the onscreen messages displayed at
> boot, but when the DE launches the status bar popup shows a proper IP
> address acquisition.
>
> Does your machine have a static IP address?
>
> FWIW I remembered a Reddit thread
> 
> about a similar (related?) OI issue
>  I was having. Someone
> replied
> 
> with a solution
>  that
> I'd totally forgotten to try because I'd been able to work around the
> original issue. I implemented the suggested fix just now and did # reboot.
> Fingers crossed.
>
> On Sun, Apr 10, 2022 at 7:57 AM Stephan Althaus <
> stephan.alth...@duedinghausen.eu> wrote:
>
>> On 4/10/22 09:38, Stephan Althaus wrote:
>> > On 4/10/22 04:13, Judah Richardson wrote:
>> >> Finally got around to looking into this ongoing issue.
>> >>
>> >> On Thu, Dec 23, 2021 at 2:28 PM Judah Richardson
>> >> 
>> >> wrote:
>> >>
>> >>>
>> >>> On Thu, Dec 23, 2021 at 11:36 AM s...@pandora.be 
>> >>> wrote:
>> >>>
>>  Do you still have access to a console when the system is
>> 'unreachable'
>>  over the network ?
>> 
>> >>> Yes, I do.
>> >>>
>>  If you still have a text console on the system which became
>>  unreachable,
>>  perhaps you could check before rebooting whether you can see any
>>  errors on
>>  the NIC.
>> 
>>  For example using:
>> 
>>  # dladm show-link -s rge0
>> 
>>  When I run the above command on system with a e1000g0 interface, it
>>  prints IERRORS / OERRORS in the show-link -s e1000g0 output, so
>>  hopefully
>>  it also prints those statistics for rge0.
>> 
>> >>> Doesn't show any errors on this end.
>>  Also maybe there are error messages in the /var/adm/messages
>>  related to
>>  rge0.
>> 
>> >>> No errors there either.
>> >> Seems to be a problem within the OS itself, perhaps in relation to that
>> >> particular NIC.
>> >>
>> >>
>> >>> These are good ideas, thanks. I'll try them next time it happens and
>> >>> then
>> >>> report back.
>> >>>
>> 
>>  Regards,
>>  David Stes
>> 
>>  - Op 22 dec 2021 om 8:56 schreef Judah Richardson
>>  judahrichard...@gmail.com:
>> 
>> > On Tue, Dec 21, 2021 at 2:06 AM Joshua M. Clulow 
>>  wrote:
>> >> On Mon, 20 Dec 2021 at 22:26, Judah Richardson
>> >>  wrote:
>> >>> On Tue, Dec 21, 2021 at 12:23 AM Joshua M. Clulow via
>> >> openindiana-discuss  wrote:
>> > Any logs or anything like that in particular I should take a
>> look
>>  at?
>>  What driver is in use?
>> >>> How do I determine this?
>> >> What do you see in "ipadm show-addr"
>> > $ sudo ipadm show-addr
>> > Password:
>> > ADDROBJ   TYPE STATEADDR
>> > lo0/v4static   ok   127.0.0.1/8
>> > rge0/_b   dhcp ok   192.168.0.71/24
>> > lo0/v6static   ok   ::1/128
>> > rge0/_a   addrconf ok fe80::7a45:c4ff:fe14:10a4/10
>> >
>> > and "dladm show-ether"?
>> >
>> > ~$ sudo dladm show-ether
>> > LINKPTYPESTATEAUTO  SPEED-DUPLEX
>> > PAUSE
>> > rge0current  up   no1G-f
>>  none
>> >   By
>> >> default, NICs are named with the driver you're using; e.g.,
>> >> "bge0" is
>> >> an instance of the "bge" driver.
>> >>
>>  What model of NIC is it?
>> >>> It's an onboard Realtek NIC.
>> >> If you "pkg install diagnostic/pci" you should be able to:
>> >>
>> >>  /usr/lib/pci/pcieadm show-devs -o
>> >> bdf,vid,did,driver,vendor,device
>> >>
>> > $ sudo /usr/lib/pci/pcieadm show-devs -o
>>  bdf,vid,did,driver,vendor,device
>> > BDF VID   DID   DRIVER VENDORDEVICE
>> > 0/0/0   8086  100   -- Intel Corporation 2nd
>> > Generation Core Processor Family DRAM Controller
>> > 0/2/0   8086  102   i9150  Intel Corporation 2nd
>> > Generation Core Processor Family Integrated Graphics Controller
>> > 0/16/0  8086  1c3a  -- Intel Corporation 

Re: [OpenIndiana-discuss] OI Hipster becomes unreachable over network after a certain length of uptime

[Judah Richardson]

I do notice 0.0.0.0 error messages in the onscreen messages displayed at
boot, but when the DE launches the status bar popup shows a proper IP
address acquisition.

Does your machine have a static IP address?

FWIW I remembered a Reddit thread

about a similar (related?) OI issue
 I was having. Someone replied

with a solution
 that
I'd totally forgotten to try because I'd been able to work around the
original issue. I implemented the suggested fix just now and did # reboot.
Fingers crossed.

On Sun, Apr 10, 2022 at 7:57 AM Stephan Althaus <
stephan.alth...@duedinghausen.eu> wrote:

> On 4/10/22 09:38, Stephan Althaus wrote:
> > On 4/10/22 04:13, Judah Richardson wrote:
> >> Finally got around to looking into this ongoing issue.
> >>
> >> On Thu, Dec 23, 2021 at 2:28 PM Judah Richardson
> >> 
> >> wrote:
> >>
> >>>
> >>> On Thu, Dec 23, 2021 at 11:36 AM s...@pandora.be 
> >>> wrote:
> >>>
>  Do you still have access to a console when the system is 'unreachable'
>  over the network ?
> 
> >>> Yes, I do.
> >>>
>  If you still have a text console on the system which became
>  unreachable,
>  perhaps you could check before rebooting whether you can see any
>  errors on
>  the NIC.
> 
>  For example using:
> 
>  # dladm show-link -s rge0
> 
>  When I run the above command on system with a e1000g0 interface, it
>  prints IERRORS / OERRORS in the show-link -s e1000g0 output, so
>  hopefully
>  it also prints those statistics for rge0.
> 
> >>> Doesn't show any errors on this end.
>  Also maybe there are error messages in the /var/adm/messages
>  related to
>  rge0.
> 
> >>> No errors there either.
> >> Seems to be a problem within the OS itself, perhaps in relation to that
> >> particular NIC.
> >>
> >>
> >>> These are good ideas, thanks. I'll try them next time it happens and
> >>> then
> >>> report back.
> >>>
> 
>  Regards,
>  David Stes
> 
>  - Op 22 dec 2021 om 8:56 schreef Judah Richardson
>  judahrichard...@gmail.com:
> 
> > On Tue, Dec 21, 2021 at 2:06 AM Joshua M. Clulow 
>  wrote:
> >> On Mon, 20 Dec 2021 at 22:26, Judah Richardson
> >>  wrote:
> >>> On Tue, Dec 21, 2021 at 12:23 AM Joshua M. Clulow via
> >> openindiana-discuss  wrote:
> > Any logs or anything like that in particular I should take a look
>  at?
>  What driver is in use?
> >>> How do I determine this?
> >> What do you see in "ipadm show-addr"
> > $ sudo ipadm show-addr
> > Password:
> > ADDROBJ   TYPE STATEADDR
> > lo0/v4static   ok   127.0.0.1/8
> > rge0/_b   dhcp ok   192.168.0.71/24
> > lo0/v6static   ok   ::1/128
> > rge0/_a   addrconf ok fe80::7a45:c4ff:fe14:10a4/10
> >
> > and "dladm show-ether"?
> >
> > ~$ sudo dladm show-ether
> > LINKPTYPESTATEAUTO  SPEED-DUPLEX
> > PAUSE
> > rge0current  up   no1G-f
>  none
> >   By
> >> default, NICs are named with the driver you're using; e.g.,
> >> "bge0" is
> >> an instance of the "bge" driver.
> >>
>  What model of NIC is it?
> >>> It's an onboard Realtek NIC.
> >> If you "pkg install diagnostic/pci" you should be able to:
> >>
> >>  /usr/lib/pci/pcieadm show-devs -o
> >> bdf,vid,did,driver,vendor,device
> >>
> > $ sudo /usr/lib/pci/pcieadm show-devs -o
>  bdf,vid,did,driver,vendor,device
> > BDF VID   DID   DRIVER VENDORDEVICE
> > 0/0/0   8086  100   -- Intel Corporation 2nd
> > Generation Core Processor Family DRAM Controller
> > 0/2/0   8086  102   i9150  Intel Corporation 2nd
> > Generation Core Processor Family Integrated Graphics Controller
> > 0/16/0  8086  1c3a  -- Intel Corporation 6
> > Series/C200 Series Chipset Family MEI Controller #1
> > 0/1a/0  8086  1c2d  ehci0  Intel Corporation 6
> > Series/C200 Series Chipset Family USB Enhanced Host Controller #2
> > 0/1b/0  8086  1c20  audiohd0   Intel Corporation 6
> > Series/C200 Series Chipset Family High Definition Audio Controller
> > 0/1c/0  8086  1c10  -- Intel Corporation 6
> > Series/C200 Series Chipset Family PCI Express Root Port 1
> > 0/1c/2  8086  1c14  pcieb1 Intel Corporation 6
> > Series/C200 Series Chipset Family PCI Express Root Port 3
> > 0/1c/4  8086  1c18  

Re: [OpenIndiana-discuss] can't install a new zone

[Andreas Wacknitz]

Am 10.04.22 um 14:57 schrieb Stephan Althaus:

On 4/10/22 14:29, Andreas Wacknitz wrote:

Am 10.04.22 um 11:46 schrieb Andreas Wacknitz:

Am 10.04.22 um 11:23 schrieb Stephan Althaus:

On 4/10/22 11:12, Stephan Althaus wrote:

On 4/10/22 10:52, Andreas Wacknitz wrote:

Am 10.04.22 um 10:47 schrieb Stephan Althaus:

On 4/10/22 09:56, Andreas Wacknitz wrote:

Am 09.04.22 um 18:38 schrieb Maurilio Longo via
openindiana-discuss:

No problem Andreas,

it is at 15370

$ pkg info userland-incorporation
  Name: consolidation/userland/userland-incorporation
   Summary: userland consolidation incorporation
(consolidation/userland/userland-incorporation)
   Description: This incorporation constrains packages
from the
userland
    consolidation
  Category: Meta Packages/Incorporations
 State: Installed
 Publisher: openindiana.org
   Version: 0.5.11
    Branch: 2022.0.0.15370
    Packaging Date: Sat Apr  9 09:53:00 2022
Last Install Time: Sun Oct 31 19:39:21 2021
  Last Update Time: Sat Apr  9 12:01:18 2022
  Size: 0.00 B
  FMRI:
pkg://openindiana.org/consolidation/userland/userland-incorporation@0.5.11-2022.0.0.15370:20220409T095300Z




Regards.

Maurilio


I have investigated further and found out that we have some actual
problems with old packages that have been replaced in the past.
The problems became imminent after illumos-gate has merged #14583
developer/opensolaris/osnet requirements cleanup and after
shrinking the
repository.
So far I have identified three:
    file/slocate
    runtime/java
    service/network/ftp
and replaced the fmri's with their replacements mlocate, openjdk8
and
proftpd.
There might be more outdated fmri's left that need to be fixed,
though.


___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss


Hi!


There are some packages mentioned that are not in "2022":

This should not be a problem. They just haven't been build this year
yet. But you need to make sure that they are still in the
repository,
though.
Eg. pkg info -r compress/bzip2@1.0.8-2020.0.1.0
and are in the userland-incorporation meta package.




# zoneadm -z bz-template install 2>&1 |grep 202|grep -v 2022

 Reject:
pkg://openindiana.org/compress/bzip2@1.0.8-2020.0.1.0:20200330T113433Z


 Reject:
pkg://openindiana.org/compress/gzip@1.11-2020.0.1.0:20210903T182240Z

 Reject:
pkg://openindiana.org/compress/unzip@6.0-2020.0.1.5:20200330T113517Z

 Reject:
pkg://openindiana.org/compress/zip@3.0-2020.0.1.1:20200615T163122Z
 Reject:
pkg://openindiana.org/database/berkeleydb-5@5.3.28-2020.0.1.0:20200330T113744Z



 Reject:
pkg://openindiana.org/database/lmdb@0.9.23-2020.0.1.0:20200330T113744Z


 Reject:
pkg://openindiana.org/entire@0.5.11-2020.0.1.0:20200330T151713Z
 Reject:
pkg://openindiana.org/library/libedit@3.1.20181209-2020.0.1.2:20200330T122131Z



 Reject:
pkg://openindiana.org/library/libxml2@2.9.9-2020.0.1.5:20210117T220316Z



 Reject:
pkg://openindiana.org/library/pcre2@10.39-2020.0.1.0:2029T235734Z

 Reject:
pkg://openindiana.org/network/ssh@8.1.0.1-2020.0.1.2:20200512T190142Z

 Reject:
pkg://openindiana.org/runtime/perl-534@5.34.0-2021.0.0.0:20211229T151048Z



 Reject:
pkg://openindiana.org/runtime/python-35@3.5.10-2020.0.1.0:20201014T142618Z



 Reject:
pkg://openindiana.org/service/management/sysding@0.5.11-2020.0.1.33:20200521T214606Z



 Reject:
pkg://openindiana.org/service/network/ssh@8.1.0.1-2020.0.1.2:20200512T190154Z



 Reject:
pkg://openindiana.org/system/ca-certificates@0.0.1.20170919-2020.0.1.0:20200330T152439Z



 Reject:
pkg://openindiana.org/system/library/gcc-7-runtime@7.5.0-2020.0.1.9:20210819T195607Z




Thank you for having a look at it!

Stephan



___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss



___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss


Hmm...

gnu-tar is a pkg from 2020

$ pkg search -l -H -o pkg.fmri 'depend:require:compress/gzip'
pkg:/install/distribution-constructor@0.5.11-2022.0.0.1057:20220325T145842Z



pkg:/metapackages/build-essential@1.0-2022.0.0.1:20220117T192224Z
pkg:/archiver/gnu-tar@1.34-2020.0.1.0:20210305T213236Z
pkg:/system/install@0.5.11-2022.0.0.1057:20220325T150012Z

From the manifest of gnu.tar: (source: pkg.openindiana.org/)
dependfmri=pkg:/compress/gzip@1.10-2020.0.1.0 type=require

Maybe this type of dependency is the reason why the zone install
fails, as that required old gzip package is no more available...
???
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org

Re: [OpenIndiana-discuss] can't install a new zone

[Stephan Althaus]

On 4/10/22 14:29, Andreas Wacknitz wrote:

Am 10.04.22 um 11:46 schrieb Andreas Wacknitz:

Am 10.04.22 um 11:23 schrieb Stephan Althaus:

On 4/10/22 11:12, Stephan Althaus wrote:

On 4/10/22 10:52, Andreas Wacknitz wrote:

Am 10.04.22 um 10:47 schrieb Stephan Althaus:

On 4/10/22 09:56, Andreas Wacknitz wrote:
Am 09.04.22 um 18:38 schrieb Maurilio Longo via 
openindiana-discuss:

No problem Andreas,

it is at 15370

$ pkg info userland-incorporation
  Name: consolidation/userland/userland-incorporation
   Summary: userland consolidation incorporation
(consolidation/userland/userland-incorporation)
   Description: This incorporation constrains packages from 
the

userland
    consolidation
  Category: Meta Packages/Incorporations
 State: Installed
 Publisher: openindiana.org
   Version: 0.5.11
    Branch: 2022.0.0.15370
    Packaging Date: Sat Apr  9 09:53:00 2022
Last Install Time: Sun Oct 31 19:39:21 2021
  Last Update Time: Sat Apr  9 12:01:18 2022
  Size: 0.00 B
  FMRI:
pkg://openindiana.org/consolidation/userland/userland-incorporation@0.5.11-2022.0.0.15370:20220409T095300Z 





Regards.

Maurilio


I have investigated further and found out that we have some actual
problems with old packages that have been replaced in the past.
The problems became imminent after illumos-gate has merged #14583
developer/opensolaris/osnet requirements cleanup and after
shrinking the
repository.
So far I have identified three:
    file/slocate
    runtime/java
    service/network/ftp
and replaced the fmri's with their replacements mlocate, openjdk8
and
proftpd.
There might be more outdated fmri's left that need to be fixed,
though.


___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss


Hi!


There are some packages mentioned that are not in "2022":

This should not be a problem. They just haven't been build this year
yet. But you need to make sure that they are still in the repository,
though.
Eg. pkg info -r compress/bzip2@1.0.8-2020.0.1.0
and are in the userland-incorporation meta package.




# zoneadm -z bz-template install 2>&1 |grep 202|grep -v 2022

 Reject:
pkg://openindiana.org/compress/bzip2@1.0.8-2020.0.1.0:20200330T113433Z 



 Reject:
pkg://openindiana.org/compress/gzip@1.11-2020.0.1.0:20210903T182240Z
 Reject:
pkg://openindiana.org/compress/unzip@6.0-2020.0.1.5:20200330T113517Z
 Reject:
pkg://openindiana.org/compress/zip@3.0-2020.0.1.1:20200615T163122Z
 Reject:
pkg://openindiana.org/database/berkeleydb-5@5.3.28-2020.0.1.0:20200330T113744Z 




 Reject:
pkg://openindiana.org/database/lmdb@0.9.23-2020.0.1.0:20200330T113744Z 



 Reject:
pkg://openindiana.org/entire@0.5.11-2020.0.1.0:20200330T151713Z
 Reject:
pkg://openindiana.org/library/libedit@3.1.20181209-2020.0.1.2:20200330T122131Z 




 Reject:
pkg://openindiana.org/library/libxml2@2.9.9-2020.0.1.5:20210117T220316Z 




 Reject:
pkg://openindiana.org/library/pcre2@10.39-2020.0.1.0:2029T235734Z 


 Reject:
pkg://openindiana.org/network/ssh@8.1.0.1-2020.0.1.2:20200512T190142Z 


 Reject:
pkg://openindiana.org/runtime/perl-534@5.34.0-2021.0.0.0:20211229T151048Z 




 Reject:
pkg://openindiana.org/runtime/python-35@3.5.10-2020.0.1.0:20201014T142618Z 




 Reject:
pkg://openindiana.org/service/management/sysding@0.5.11-2020.0.1.33:20200521T214606Z 




 Reject:
pkg://openindiana.org/service/network/ssh@8.1.0.1-2020.0.1.2:20200512T190154Z 




 Reject:
pkg://openindiana.org/system/ca-certificates@0.0.1.20170919-2020.0.1.0:20200330T152439Z 




 Reject:
pkg://openindiana.org/system/library/gcc-7-runtime@7.5.0-2020.0.1.9:20210819T195607Z 





Thank you for having a look at it!

Stephan



___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss



___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss


Hmm...

gnu-tar is a pkg from 2020

$ pkg search -l -H -o pkg.fmri 'depend:require:compress/gzip'
pkg:/install/distribution-constructor@0.5.11-2022.0.0.1057:20220325T145842Z 




pkg:/metapackages/build-essential@1.0-2022.0.0.1:20220117T192224Z
pkg:/archiver/gnu-tar@1.34-2020.0.1.0:20210305T213236Z
pkg:/system/install@0.5.11-2022.0.0.1057:20220325T150012Z

From the manifest of gnu.tar: (source: pkg.openindiana.org/)
dependfmri=pkg:/compress/gzip@1.10-2020.0.1.0  type=require

Maybe this type of dependency is the reason why the zone install
fails, as that required old gzip package is no more available...
???
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] OI Hipster becomes unreachable over network after a certain length of uptime

[Stephan Althaus]

On 4/10/22 09:38, Stephan Althaus wrote:

On 4/10/22 04:13, Judah Richardson wrote:

Finally got around to looking into this ongoing issue.

On Thu, Dec 23, 2021 at 2:28 PM Judah Richardson 


wrote:



On Thu, Dec 23, 2021 at 11:36 AM s...@pandora.be  
wrote:



Do you still have access to a console when the system is 'unreachable'
over the network ?


Yes, I do.

If you still have a text console on the system which became 
unreachable,
perhaps you could check before rebooting whether you can see any 
errors on

the NIC.

For example using:

# dladm show-link -s rge0

When I run the above command on system with a e1000g0 interface, it
prints IERRORS / OERRORS in the show-link -s e1000g0 output, so 
hopefully

it also prints those statistics for rge0.


Doesn't show any errors on this end.
Also maybe there are error messages in the /var/adm/messages 
related to

rge0.


No errors there either.

Seems to be a problem within the OS itself, perhaps in relation to that
particular NIC.


These are good ideas, thanks. I'll try them next time it happens and 
then

report back.



Regards,
David Stes

- Op 22 dec 2021 om 8:56 schreef Judah Richardson
judahrichard...@gmail.com:


On Tue, Dec 21, 2021 at 2:06 AM Joshua M. Clulow 

wrote:

On Mon, 20 Dec 2021 at 22:26, Judah Richardson
 wrote:

On Tue, Dec 21, 2021 at 12:23 AM Joshua M. Clulow via

openindiana-discuss  wrote:

Any logs or anything like that in particular I should take a look

at?

What driver is in use?

How do I determine this?

What do you see in "ipadm show-addr"

$ sudo ipadm show-addr
Password:
ADDROBJ   TYPE STATE    ADDR
lo0/v4    static   ok   127.0.0.1/8
rge0/_b   dhcp ok   192.168.0.71/24
lo0/v6    static   ok   ::1/128
rge0/_a   addrconf ok fe80::7a45:c4ff:fe14:10a4/10

and "dladm show-ether"?

~$ sudo dladm show-ether
LINK    PTYPE    STATE    AUTO  SPEED-DUPLEX
PAUSE
rge0    current  up   no    1G-f

none

  By
default, NICs are named with the driver you're using; e.g., 
"bge0" is

an instance of the "bge" driver.


What model of NIC is it?

It's an onboard Realtek NIC.

If you "pkg install diagnostic/pci" you should be able to:

 /usr/lib/pci/pcieadm show-devs -o 
bdf,vid,did,driver,vendor,device



$ sudo /usr/lib/pci/pcieadm show-devs -o

bdf,vid,did,driver,vendor,device

BDF VID   DID   DRIVER VENDOR    DEVICE
0/0/0   8086  100   -- Intel Corporation 2nd
Generation Core Processor Family DRAM Controller
0/2/0   8086  102   i9150  Intel Corporation 2nd
Generation Core Processor Family Integrated Graphics Controller
0/16/0  8086  1c3a  -- Intel Corporation 6
Series/C200 Series Chipset Family MEI Controller #1
0/1a/0  8086  1c2d  ehci0  Intel Corporation 6
Series/C200 Series Chipset Family USB Enhanced Host Controller #2
0/1b/0  8086  1c20  audiohd0   Intel Corporation 6
Series/C200 Series Chipset Family High Definition Audio Controller
0/1c/0  8086  1c10  -- Intel Corporation 6
Series/C200 Series Chipset Family PCI Express Root Port 1
0/1c/2  8086  1c14  pcieb1 Intel Corporation 6
Series/C200 Series Chipset Family PCI Express Root Port 3
0/1c/4  8086  1c18  pcieb2 Intel Corporation 6
Series/C200 Series Chipset Family PCI Express Root Port 5
3/0/0   10ec  8168  rge0   Realtek Semiconductor Co., Ltd.
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
0/1d/0  8086  1c26  ehci1  Intel Corporation 6
Series/C200 Series Chipset Family USB Enhanced Host Controller #1
0/1f/0  8086  1c5c  isa0   Intel Corporation H61
Express Chipset LPC Controller
0/1f/2  8086  1c00  pci-ide0   Intel Corporation 6
Series/C200 Series Chipset Family Desktop SATA Controller (IDE mode,

ports

0-3)
0/1f/3  8086  1c22  -- Intel Corporation 6
Series/C200 Series Chipset Family SMBus Controller
0/1f/5  8086  1c08  pci-ide1   Intel Corporation 6
Series/C200 Series Chipset Family Desktop SATA Controller (IDE mode,

ports

4-5)



e.g., I can see, on one of my systems:

    0/1f/6  8086  15b7  e1000g0    Intel Corporation
Ethernet Connection (2) I219-LM


Cheers.

--
Joshua M. Clulow
http://blog.sysmgr.org


___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss


___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss


Hi!

The last few weeks i had 

Re: [OpenIndiana-discuss] can't install a new zone

[Andreas Wacknitz]

Am 10.04.22 um 11:46 schrieb Andreas Wacknitz:

Am 10.04.22 um 11:23 schrieb Stephan Althaus:

On 4/10/22 11:12, Stephan Althaus wrote:

On 4/10/22 10:52, Andreas Wacknitz wrote:

Am 10.04.22 um 10:47 schrieb Stephan Althaus:

On 4/10/22 09:56, Andreas Wacknitz wrote:

Am 09.04.22 um 18:38 schrieb Maurilio Longo via openindiana-discuss:

No problem Andreas,

it is at 15370

$ pkg info userland-incorporation
  Name: consolidation/userland/userland-incorporation
   Summary: userland consolidation incorporation
(consolidation/userland/userland-incorporation)
   Description: This incorporation constrains packages from the
userland
    consolidation
  Category: Meta Packages/Incorporations
 State: Installed
 Publisher: openindiana.org
   Version: 0.5.11
    Branch: 2022.0.0.15370
    Packaging Date: Sat Apr  9 09:53:00 2022
Last Install Time: Sun Oct 31 19:39:21 2021
  Last Update Time: Sat Apr  9 12:01:18 2022
  Size: 0.00 B
  FMRI:
pkg://openindiana.org/consolidation/userland/userland-incorporation@0.5.11-2022.0.0.15370:20220409T095300Z



Regards.

Maurilio


I have investigated further and found out that we have some actual
problems with old packages that have been replaced in the past.
The problems became imminent after illumos-gate has merged #14583
developer/opensolaris/osnet requirements cleanup and after
shrinking the
repository.
So far I have identified three:
    file/slocate
    runtime/java
    service/network/ftp
and replaced the fmri's with their replacements mlocate, openjdk8
and
proftpd.
There might be more outdated fmri's left that need to be fixed,
though.


___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss


Hi!


There are some packages mentioned that are not in "2022":

This should not be a problem. They just haven't been build this year
yet. But you need to make sure that they are still in the repository,
though.
Eg. pkg info -r compress/bzip2@1.0.8-2020.0.1.0
and are in the userland-incorporation meta package.




# zoneadm -z bz-template install 2>&1 |grep 202|grep -v 2022

 Reject:
pkg://openindiana.org/compress/bzip2@1.0.8-2020.0.1.0:20200330T113433Z

 Reject:
pkg://openindiana.org/compress/gzip@1.11-2020.0.1.0:20210903T182240Z
 Reject:
pkg://openindiana.org/compress/unzip@6.0-2020.0.1.5:20200330T113517Z
 Reject:
pkg://openindiana.org/compress/zip@3.0-2020.0.1.1:20200615T163122Z
 Reject:
pkg://openindiana.org/database/berkeleydb-5@5.3.28-2020.0.1.0:20200330T113744Z


 Reject:
pkg://openindiana.org/database/lmdb@0.9.23-2020.0.1.0:20200330T113744Z

 Reject:
pkg://openindiana.org/entire@0.5.11-2020.0.1.0:20200330T151713Z
 Reject:
pkg://openindiana.org/library/libedit@3.1.20181209-2020.0.1.2:20200330T122131Z


 Reject:
pkg://openindiana.org/library/libxml2@2.9.9-2020.0.1.5:20210117T220316Z


 Reject:
pkg://openindiana.org/library/pcre2@10.39-2020.0.1.0:2029T235734Z
 Reject:
pkg://openindiana.org/network/ssh@8.1.0.1-2020.0.1.2:20200512T190142Z
 Reject:
pkg://openindiana.org/runtime/perl-534@5.34.0-2021.0.0.0:20211229T151048Z


 Reject:
pkg://openindiana.org/runtime/python-35@3.5.10-2020.0.1.0:20201014T142618Z


 Reject:
pkg://openindiana.org/service/management/sysding@0.5.11-2020.0.1.33:20200521T214606Z


 Reject:
pkg://openindiana.org/service/network/ssh@8.1.0.1-2020.0.1.2:20200512T190154Z


 Reject:
pkg://openindiana.org/system/ca-certificates@0.0.1.20170919-2020.0.1.0:20200330T152439Z


 Reject:
pkg://openindiana.org/system/library/gcc-7-runtime@7.5.0-2020.0.1.9:20210819T195607Z



Thank you for having a look at it!

Stephan



___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss



___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss


Hmm...

gnu-tar is a pkg from 2020

$ pkg search -l -H -o pkg.fmri 'depend:require:compress/gzip'
pkg:/install/distribution-constructor@0.5.11-2022.0.0.1057:20220325T145842Z


pkg:/metapackages/build-essential@1.0-2022.0.0.1:20220117T192224Z
pkg:/archiver/gnu-tar@1.34-2020.0.1.0:20210305T213236Z
pkg:/system/install@0.5.11-2022.0.0.1057:20220325T150012Z

From the manifest of gnu.tar: (source: pkg.openindiana.org/)
dependfmri=pkg:/compress/gzip@1.10-2020.0.1.0  type=require

Maybe this type of dependency is the reason why the zone install
fails, as that required old gzip package is no more available...
???
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss


Ah!

The dependency in gnu-tar is not correct, because the version of gzip
is mentioned:

Re: [OpenIndiana-discuss] what is this computer doing ?

[Stephan Althaus]

On 4/10/22 12:05, Marc Lobelle wrote:

Hello,

My openindiana server has 4 cores. On the system monitor, the average 
load of each core is around 60%, even when the machine does not do 
anything


Here is a snapshot of top. The top process is the gam-server (what 
does it do? I do not touch the disks)


and the two active processes, gam_server and imapd eat each around 
1/4th of a core


Does anybody understand what is happening ?

Thanks

Marc

load averages:  2.33,  2.55,  2.95;   up 27+03:51:14   
11:53:03

167 processes: 164 sleeping, 3 on cpu
CPU states: 43.0% idle, 49.7% user,  7.3% kernel,  0.0% iowait, 0.0% swap
Kernel: 3285 ctxsw, 382 trap, 3990 intr, 33085 syscall, 1 flt, 4 pgin
Memory: 32G phys mem, 8243M free mem, 4072M total swap, 2534M free swap
ARC:    12G Total, 9593M MRU, 1775M MFU, 1308K Anon, 193M Header, 494M 
Other

    10G Compressed, 11G Uncompressed, 1.11:1 Ratio, 1236M Overhead

   PID     USERNAME NLWP PRI NICE  SIZE       RES     STATE TIME      
CPU         COMMAND
  1423     ml      1       0    0       22M       19M cpu/2  
206.3H     24.95%     gam_server
  5144     ml      1       0    0     5320K     4184K cpu/0   
17.9H     23.62%     imapd
 10784    ml      5      11    0      137M     84M sleep 
652:51      3.92%   mate-system-mon
  2713     ml        231    11    0     4476M    2806M sleep 
17.8H      1.95%   thunderbird
   684  ml      3      21    0      126M      56M sleep   
35.5H      1.11%  Xorg



___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss


Hello!


The process is of the package

$ pkg search gam_server
INDEX  ACTION VALUE    PACKAGE
basename   file   usr/lib/amd64/gam_server 
pkg:/library/file-monitor/gamin@0.1.10-2022.0.0.2
basename   file   usr/lib/gam_server 
pkg:/library/file-monitor/gamin@0.1.10-2022.0.0.2


$ pkg info gamin
 Name: library/file-monitor/gamin
  Summary: Library providing the FAM File Alteration Monitor API
 Category: System/Libraries
    State: Installed
    Publisher: openindiana.org
  Version: 0.1.10
   Branch: 2022.0.0.2
   Packaging Date: January 31, 2022 at 09:06:08 PM
Last Install Time: January 26, 2020 at 07:57:07 PM
 Last Update Time: February  2, 2022 at 12:05:54 PM
 Size: 1.30 MB
 FMRI: 
pkg://openindiana.org/library/file-monitor/gamin@0.1.10-2022.0.0.2:20220131T210608Z



and i think it (re-)builds some file index ?

What packages require this?

$ pkg search -l -H -o pkg.fmri,action.raw 
'depend:require:library/file-monitor/gamin'
pkg:/library/gnome/gnome-vfs@2.24.4-2022.0.0.6:20220131T211410Z depend 
fmri=pkg:/library/file-monitor/gamin@0.1.10-2020.0.1.2 type=require
pkg:/library/python/gamin-27@0.1.10-2022.0.0.2:20220131T210554Z depend 
fmri=pkg:/library/file-monitor/gamin@0.1.10-2022.0.0.2 type=require
pkg:/library/glib2@2.70.0-2022.0.0.2:20220403T195653Z    depend 
fmri=pkg:/library/file-monitor/gamin@0.1.10-2022.0.0.2 type=require


..in the end i think its the mate desktop..

Greetings,

Stephan


___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] can't install a new zone

[Stephan Althaus]

On 4/10/22 11:46, Andreas Wacknitz wrote:

Am 10.04.22 um 11:23 schrieb Stephan Althaus:

On 4/10/22 11:12, Stephan Althaus wrote:

On 4/10/22 10:52, Andreas Wacknitz wrote:

Am 10.04.22 um 10:47 schrieb Stephan Althaus:

On 4/10/22 09:56, Andreas Wacknitz wrote:

Am 09.04.22 um 18:38 schrieb Maurilio Longo via openindiana-discuss:

No problem Andreas,

it is at 15370

$ pkg info userland-incorporation
  Name: consolidation/userland/userland-incorporation
   Summary: userland consolidation incorporation
(consolidation/userland/userland-incorporation)
   Description: This incorporation constrains packages from the
userland
    consolidation
  Category: Meta Packages/Incorporations
 State: Installed
 Publisher: openindiana.org
   Version: 0.5.11
    Branch: 2022.0.0.15370
    Packaging Date: Sat Apr  9 09:53:00 2022
Last Install Time: Sun Oct 31 19:39:21 2021
  Last Update Time: Sat Apr  9 12:01:18 2022
  Size: 0.00 B
  FMRI:
pkg://openindiana.org/consolidation/userland/userland-incorporation@0.5.11-2022.0.0.15370:20220409T095300Z 




Regards.

Maurilio


I have investigated further and found out that we have some actual
problems with old packages that have been replaced in the past.
The problems became imminent after illumos-gate has merged #14583
developer/opensolaris/osnet requirements cleanup and after
shrinking the
repository.
So far I have identified three:
    file/slocate
    runtime/java
    service/network/ftp
and replaced the fmri's with their replacements mlocate, openjdk8 
and

proftpd.
There might be more outdated fmri's left that need to be fixed,
though.


___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss


Hi!


There are some packages mentioned that are not in "2022":

This should not be a problem. They just haven't been build this year
yet. But you need to make sure that they are still in the repository,
though.
Eg. pkg info -r compress/bzip2@1.0.8-2020.0.1.0
and are in the userland-incorporation meta package.




# zoneadm -z bz-template install 2>&1 |grep 202|grep -v 2022

 Reject:
pkg://openindiana.org/compress/bzip2@1.0.8-2020.0.1.0:20200330T113433Z 


 Reject:
pkg://openindiana.org/compress/gzip@1.11-2020.0.1.0:20210903T182240Z
 Reject:
pkg://openindiana.org/compress/unzip@6.0-2020.0.1.5:20200330T113517Z
 Reject:
pkg://openindiana.org/compress/zip@3.0-2020.0.1.1:20200615T163122Z
 Reject:
pkg://openindiana.org/database/berkeleydb-5@5.3.28-2020.0.1.0:20200330T113744Z 



 Reject:
pkg://openindiana.org/database/lmdb@0.9.23-2020.0.1.0:20200330T113744Z 


 Reject:
pkg://openindiana.org/entire@0.5.11-2020.0.1.0:20200330T151713Z
 Reject:
pkg://openindiana.org/library/libedit@3.1.20181209-2020.0.1.2:20200330T122131Z 



 Reject:
pkg://openindiana.org/library/libxml2@2.9.9-2020.0.1.5:20210117T220316Z 



 Reject:
pkg://openindiana.org/library/pcre2@10.39-2020.0.1.0:2029T235734Z
 Reject:
pkg://openindiana.org/network/ssh@8.1.0.1-2020.0.1.2:20200512T190142Z
 Reject:
pkg://openindiana.org/runtime/perl-534@5.34.0-2021.0.0.0:20211229T151048Z 



 Reject:
pkg://openindiana.org/runtime/python-35@3.5.10-2020.0.1.0:20201014T142618Z 



 Reject:
pkg://openindiana.org/service/management/sysding@0.5.11-2020.0.1.33:20200521T214606Z 



 Reject:
pkg://openindiana.org/service/network/ssh@8.1.0.1-2020.0.1.2:20200512T190154Z 



 Reject:
pkg://openindiana.org/system/ca-certificates@0.0.1.20170919-2020.0.1.0:20200330T152439Z 



 Reject:
pkg://openindiana.org/system/library/gcc-7-runtime@7.5.0-2020.0.1.9:20210819T195607Z 




Thank you for having a look at it!

Stephan



___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss



___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss


Hmm...

gnu-tar is a pkg from 2020

$ pkg search -l -H -o pkg.fmri 'depend:require:compress/gzip'
pkg:/install/distribution-constructor@0.5.11-2022.0.0.1057:20220325T145842Z 



pkg:/metapackages/build-essential@1.0-2022.0.0.1:20220117T192224Z
pkg:/archiver/gnu-tar@1.34-2020.0.1.0:20210305T213236Z
pkg:/system/install@0.5.11-2022.0.0.1057:20220325T150012Z

From the manifest of gnu.tar: (source: pkg.openindiana.org/)
dependfmri=pkg:/compress/gzip@1.10-2020.0.1.0  type=require

Maybe this type of dependency is the reason why the zone install
fails, as that required old gzip package is no more available...
???
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss


Ah!

The dependency in gnu-tar is not correct, because the 

[OpenIndiana-discuss] what is this computer doing ?

[Marc Lobelle]

Hello,

My openindiana server has 4 cores. On the system monitor, the average 
load of each core is around 60%, even when the machine does not do anything


Here is a snapshot of top. The top process is the gam-server (what does 
it do? I do not touch the disks)


and the two active processes, gam_server and imapd eat each around 1/4th 
of a core


Does anybody understand what is happening ?

Thanks

Marc

load averages:  2.33,  2.55,  2.95;   up 27+03:51:14   
11:53:03

167 processes: 164 sleeping, 3 on cpu
CPU states: 43.0% idle, 49.7% user,  7.3% kernel,  0.0% iowait, 0.0% swap
Kernel: 3285 ctxsw, 382 trap, 3990 intr, 33085 syscall, 1 flt, 4 pgin
Memory: 32G phys mem, 8243M free mem, 4072M total swap, 2534M free swap
ARC:    12G Total, 9593M MRU, 1775M MFU, 1308K Anon, 193M Header, 494M Other
    10G Compressed, 11G Uncompressed, 1.11:1 Ratio, 1236M Overhead

   PID     USERNAME NLWP PRI NICE  SIZE       RES     STATE TIME      
CPU         COMMAND
  1423     ml      1       0    0       22M       19M cpu/2  
206.3H     24.95%     gam_server
  5144     ml      1       0    0     5320K     4184K cpu/0   
17.9H     23.62%     imapd
 10784    ml      5      11    0      137M     84M sleep  
652:51      3.92%   mate-system-mon
  2713     ml        231    11    0     4476M    2806M sleep 17.8H  
    1.95%   thunderbird
   684  ml      3      21    0      126M      56M sleep   
35.5H      1.11%  Xorg



___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] can't install a new zone

[Andreas Wacknitz]

Am 10.04.22 um 11:23 schrieb Stephan Althaus:

On 4/10/22 11:12, Stephan Althaus wrote:

On 4/10/22 10:52, Andreas Wacknitz wrote:

Am 10.04.22 um 10:47 schrieb Stephan Althaus:

On 4/10/22 09:56, Andreas Wacknitz wrote:

Am 09.04.22 um 18:38 schrieb Maurilio Longo via openindiana-discuss:

No problem Andreas,

it is at 15370

$ pkg info userland-incorporation
  Name: consolidation/userland/userland-incorporation
   Summary: userland consolidation incorporation
(consolidation/userland/userland-incorporation)
   Description: This incorporation constrains packages from the
userland
    consolidation
  Category: Meta Packages/Incorporations
 State: Installed
 Publisher: openindiana.org
   Version: 0.5.11
    Branch: 2022.0.0.15370
    Packaging Date: Sat Apr  9 09:53:00 2022
Last Install Time: Sun Oct 31 19:39:21 2021
  Last Update Time: Sat Apr  9 12:01:18 2022
  Size: 0.00 B
  FMRI:
pkg://openindiana.org/consolidation/userland/userland-incorporation@0.5.11-2022.0.0.15370:20220409T095300Z


Regards.

Maurilio


I have investigated further and found out that we have some actual
problems with old packages that have been replaced in the past.
The problems became imminent after illumos-gate has merged #14583
developer/opensolaris/osnet requirements cleanup and after
shrinking the
repository.
So far I have identified three:
    file/slocate
    runtime/java
    service/network/ftp
and replaced the fmri's with their replacements mlocate, openjdk8 and
proftpd.
There might be more outdated fmri's left that need to be fixed,
though.


___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss


Hi!


There are some packages mentioned that are not in "2022":

This should not be a problem. They just haven't been build this year
yet. But you need to make sure that they are still in the repository,
though.
Eg. pkg info -r compress/bzip2@1.0.8-2020.0.1.0
and are in the userland-incorporation meta package.




# zoneadm -z bz-template install 2>&1 |grep 202|grep -v 2022

 Reject:
pkg://openindiana.org/compress/bzip2@1.0.8-2020.0.1.0:20200330T113433Z
 Reject:
pkg://openindiana.org/compress/gzip@1.11-2020.0.1.0:20210903T182240Z
 Reject:
pkg://openindiana.org/compress/unzip@6.0-2020.0.1.5:20200330T113517Z
 Reject:
pkg://openindiana.org/compress/zip@3.0-2020.0.1.1:20200615T163122Z
 Reject:
pkg://openindiana.org/database/berkeleydb-5@5.3.28-2020.0.1.0:20200330T113744Z

 Reject:
pkg://openindiana.org/database/lmdb@0.9.23-2020.0.1.0:20200330T113744Z
 Reject:
pkg://openindiana.org/entire@0.5.11-2020.0.1.0:20200330T151713Z
 Reject:
pkg://openindiana.org/library/libedit@3.1.20181209-2020.0.1.2:20200330T122131Z

 Reject:
pkg://openindiana.org/library/libxml2@2.9.9-2020.0.1.5:20210117T220316Z

 Reject:
pkg://openindiana.org/library/pcre2@10.39-2020.0.1.0:2029T235734Z
 Reject:
pkg://openindiana.org/network/ssh@8.1.0.1-2020.0.1.2:20200512T190142Z
 Reject:
pkg://openindiana.org/runtime/perl-534@5.34.0-2021.0.0.0:20211229T151048Z

 Reject:
pkg://openindiana.org/runtime/python-35@3.5.10-2020.0.1.0:20201014T142618Z

 Reject:
pkg://openindiana.org/service/management/sysding@0.5.11-2020.0.1.33:20200521T214606Z

 Reject:
pkg://openindiana.org/service/network/ssh@8.1.0.1-2020.0.1.2:20200512T190154Z

 Reject:
pkg://openindiana.org/system/ca-certificates@0.0.1.20170919-2020.0.1.0:20200330T152439Z

 Reject:
pkg://openindiana.org/system/library/gcc-7-runtime@7.5.0-2020.0.1.9:20210819T195607Z


Thank you for having a look at it!

Stephan



___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss



___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss


Hmm...

gnu-tar is a pkg from 2020

$ pkg search -l -H -o pkg.fmri 'depend:require:compress/gzip'
pkg:/install/distribution-constructor@0.5.11-2022.0.0.1057:20220325T145842Z

pkg:/metapackages/build-essential@1.0-2022.0.0.1:20220117T192224Z
pkg:/archiver/gnu-tar@1.34-2020.0.1.0:20210305T213236Z
pkg:/system/install@0.5.11-2022.0.0.1057:20220325T150012Z

From the manifest of gnu.tar: (source: pkg.openindiana.org/)
dependfmri=pkg:/compress/gzip@1.10-2020.0.1.0  type=require

Maybe this type of dependency is the reason why the zone install
fails, as that required old gzip package is no more available...
???
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss


Ah!

The dependency in gnu-tar is not correct, because the version of gzip
is mentioned:

$ pkg search -l -H -o pkg.fmri,action.raw 

Re: [OpenIndiana-discuss] can't install a new zone

[Stephan Althaus]

On 4/10/22 11:12, Stephan Althaus wrote:

On 4/10/22 10:52, Andreas Wacknitz wrote:

Am 10.04.22 um 10:47 schrieb Stephan Althaus:

On 4/10/22 09:56, Andreas Wacknitz wrote:

Am 09.04.22 um 18:38 schrieb Maurilio Longo via openindiana-discuss:

No problem Andreas,

it is at 15370

$ pkg info userland-incorporation
  Name: consolidation/userland/userland-incorporation
   Summary: userland consolidation incorporation
(consolidation/userland/userland-incorporation)
   Description: This incorporation constrains packages from the
userland
    consolidation
  Category: Meta Packages/Incorporations
 State: Installed
 Publisher: openindiana.org
   Version: 0.5.11
    Branch: 2022.0.0.15370
    Packaging Date: Sat Apr  9 09:53:00 2022
Last Install Time: Sun Oct 31 19:39:21 2021
  Last Update Time: Sat Apr  9 12:01:18 2022
  Size: 0.00 B
  FMRI:
pkg://openindiana.org/consolidation/userland/userland-incorporation@0.5.11-2022.0.0.15370:20220409T095300Z 



Regards.

Maurilio


I have investigated further and found out that we have some actual
problems with old packages that have been replaced in the past.
The problems became imminent after illumos-gate has merged #14583
developer/opensolaris/osnet requirements cleanup and after 
shrinking the

repository.
So far I have identified three:
    file/slocate
    runtime/java
    service/network/ftp
and replaced the fmri's with their replacements mlocate, openjdk8 and
proftpd.
There might be more outdated fmri's left that need to be fixed, 
though.



___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss


Hi!


There are some packages mentioned that are not in "2022":

This should not be a problem. They just haven't been build this year
yet. But you need to make sure that they are still in the repository,
though.
Eg. pkg info -r compress/bzip2@1.0.8-2020.0.1.0
and are in the userland-incorporation meta package.




# zoneadm -z bz-template install 2>&1 |grep 202|grep -v 2022

 Reject:
pkg://openindiana.org/compress/bzip2@1.0.8-2020.0.1.0:20200330T113433Z
 Reject:
pkg://openindiana.org/compress/gzip@1.11-2020.0.1.0:20210903T182240Z
 Reject:
pkg://openindiana.org/compress/unzip@6.0-2020.0.1.5:20200330T113517Z
 Reject:
pkg://openindiana.org/compress/zip@3.0-2020.0.1.1:20200615T163122Z
 Reject:
pkg://openindiana.org/database/berkeleydb-5@5.3.28-2020.0.1.0:20200330T113744Z 


 Reject:
pkg://openindiana.org/database/lmdb@0.9.23-2020.0.1.0:20200330T113744Z
 Reject: 
pkg://openindiana.org/entire@0.5.11-2020.0.1.0:20200330T151713Z

 Reject:
pkg://openindiana.org/library/libedit@3.1.20181209-2020.0.1.2:20200330T122131Z 


 Reject:
pkg://openindiana.org/library/libxml2@2.9.9-2020.0.1.5:20210117T220316Z
 Reject:
pkg://openindiana.org/library/pcre2@10.39-2020.0.1.0:2029T235734Z
 Reject:
pkg://openindiana.org/network/ssh@8.1.0.1-2020.0.1.2:20200512T190142Z
 Reject:
pkg://openindiana.org/runtime/perl-534@5.34.0-2021.0.0.0:20211229T151048Z 


 Reject:
pkg://openindiana.org/runtime/python-35@3.5.10-2020.0.1.0:20201014T142618Z 


 Reject:
pkg://openindiana.org/service/management/sysding@0.5.11-2020.0.1.33:20200521T214606Z 


 Reject:
pkg://openindiana.org/service/network/ssh@8.1.0.1-2020.0.1.2:20200512T190154Z 


 Reject:
pkg://openindiana.org/system/ca-certificates@0.0.1.20170919-2020.0.1.0:20200330T152439Z 


 Reject:
pkg://openindiana.org/system/library/gcc-7-runtime@7.5.0-2020.0.1.9:20210819T195607Z 



Thank you for having a look at it!

Stephan



___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss



___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss


Hmm...

gnu-tar is a pkg from 2020

$ pkg search -l -H -o pkg.fmri 'depend:require:compress/gzip'
pkg:/install/distribution-constructor@0.5.11-2022.0.0.1057:20220325T145842Z 


pkg:/metapackages/build-essential@1.0-2022.0.0.1:20220117T192224Z
pkg:/archiver/gnu-tar@1.34-2020.0.1.0:20210305T213236Z
pkg:/system/install@0.5.11-2022.0.0.1057:20220325T150012Z

From the manifest of gnu.tar: (source: pkg.openindiana.org/)
dependfmri=pkg:/compress/gzip@1.10-2020.0.1.0  type=require

Maybe this type of dependency is the reason why the zone install 
fails, as that required old gzip package is no more available...

???
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss


Ah!

The dependency in gnu-tar is not correct, because the version of gzip is 
mentioned:


$ pkg search -l -H -o pkg.fmri,action.raw 'depend:require:compress/gzip'

Re: [OpenIndiana-discuss] can't install a new zone

[Stephan Althaus]

On 4/10/22 10:52, Andreas Wacknitz wrote:

Am 10.04.22 um 10:47 schrieb Stephan Althaus:

On 4/10/22 09:56, Andreas Wacknitz wrote:

Am 09.04.22 um 18:38 schrieb Maurilio Longo via openindiana-discuss:

No problem Andreas,

it is at 15370

$ pkg info userland-incorporation
  Name: consolidation/userland/userland-incorporation
   Summary: userland consolidation incorporation
(consolidation/userland/userland-incorporation)
   Description: This incorporation constrains packages from the
userland
    consolidation
  Category: Meta Packages/Incorporations
 State: Installed
 Publisher: openindiana.org
   Version: 0.5.11
    Branch: 2022.0.0.15370
    Packaging Date: Sat Apr  9 09:53:00 2022
Last Install Time: Sun Oct 31 19:39:21 2021
  Last Update Time: Sat Apr  9 12:01:18 2022
  Size: 0.00 B
  FMRI:
pkg://openindiana.org/consolidation/userland/userland-incorporation@0.5.11-2022.0.0.15370:20220409T095300Z 



Regards.

Maurilio


I have investigated further and found out that we have some actual
problems with old packages that have been replaced in the past.
The problems became imminent after illumos-gate has merged #14583
developer/opensolaris/osnet requirements cleanup and after shrinking 
the

repository.
So far I have identified three:
    file/slocate
    runtime/java
    service/network/ftp
and replaced the fmri's with their replacements mlocate, openjdk8 and
proftpd.
There might be more outdated fmri's left that need to be fixed, though.


___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss


Hi!


There are some packages mentioned that are not in "2022":

This should not be a problem. They just haven't been build this year
yet. But you need to make sure that they are still in the repository,
though.
Eg. pkg info -r compress/bzip2@1.0.8-2020.0.1.0
and are in the userland-incorporation meta package.




# zoneadm -z bz-template install 2>&1 |grep 202|grep -v 2022

 Reject:
pkg://openindiana.org/compress/bzip2@1.0.8-2020.0.1.0:20200330T113433Z
 Reject:
pkg://openindiana.org/compress/gzip@1.11-2020.0.1.0:20210903T182240Z
 Reject:
pkg://openindiana.org/compress/unzip@6.0-2020.0.1.5:20200330T113517Z
 Reject:
pkg://openindiana.org/compress/zip@3.0-2020.0.1.1:20200615T163122Z
 Reject:
pkg://openindiana.org/database/berkeleydb-5@5.3.28-2020.0.1.0:20200330T113744Z 


 Reject:
pkg://openindiana.org/database/lmdb@0.9.23-2020.0.1.0:20200330T113744Z
 Reject: pkg://openindiana.org/entire@0.5.11-2020.0.1.0:20200330T151713Z
 Reject:
pkg://openindiana.org/library/libedit@3.1.20181209-2020.0.1.2:20200330T122131Z 


 Reject:
pkg://openindiana.org/library/libxml2@2.9.9-2020.0.1.5:20210117T220316Z
 Reject:
pkg://openindiana.org/library/pcre2@10.39-2020.0.1.0:2029T235734Z
 Reject:
pkg://openindiana.org/network/ssh@8.1.0.1-2020.0.1.2:20200512T190142Z
 Reject:
pkg://openindiana.org/runtime/perl-534@5.34.0-2021.0.0.0:20211229T151048Z 


 Reject:
pkg://openindiana.org/runtime/python-35@3.5.10-2020.0.1.0:20201014T142618Z 


 Reject:
pkg://openindiana.org/service/management/sysding@0.5.11-2020.0.1.33:20200521T214606Z 


 Reject:
pkg://openindiana.org/service/network/ssh@8.1.0.1-2020.0.1.2:20200512T190154Z 


 Reject:
pkg://openindiana.org/system/ca-certificates@0.0.1.20170919-2020.0.1.0:20200330T152439Z 


 Reject:
pkg://openindiana.org/system/library/gcc-7-runtime@7.5.0-2020.0.1.9:20210819T195607Z 



Thank you for having a look at it!

Stephan



___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss



___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss


Hmm...

gnu-tar is a pkg from 2020

$ pkg search -l -H -o pkg.fmri 'depend:require:compress/gzip'
pkg:/install/distribution-constructor@0.5.11-2022.0.0.1057:20220325T145842Z
pkg:/metapackages/build-essential@1.0-2022.0.0.1:20220117T192224Z
pkg:/archiver/gnu-tar@1.34-2020.0.1.0:20210305T213236Z
pkg:/system/install@0.5.11-2022.0.0.1057:20220325T150012Z

From the manifest of gnu.tar: (source: pkg.openindiana.org/)
dependfmri=pkg:/compress/gzip@1.10-2020.0.1.0  type=require

Maybe this type of dependency is the reason why the zone install fails, as that 
required old gzip package is no more available...
???
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] can't install a new zone

[Andreas Wacknitz]

Am 10.04.22 um 10:47 schrieb Stephan Althaus:

On 4/10/22 09:56, Andreas Wacknitz wrote:

Am 09.04.22 um 18:38 schrieb Maurilio Longo via openindiana-discuss:

No problem Andreas,

it is at 15370

$ pkg info userland-incorporation
  Name: consolidation/userland/userland-incorporation
   Summary: userland consolidation incorporation
(consolidation/userland/userland-incorporation)
   Description: This incorporation constrains packages from the
userland
    consolidation
  Category: Meta Packages/Incorporations
 State: Installed
 Publisher: openindiana.org
   Version: 0.5.11
    Branch: 2022.0.0.15370
    Packaging Date: Sat Apr  9 09:53:00 2022
Last Install Time: Sun Oct 31 19:39:21 2021
  Last Update Time: Sat Apr  9 12:01:18 2022
  Size: 0.00 B
  FMRI:
pkg://openindiana.org/consolidation/userland/userland-incorporation@0.5.11-2022.0.0.15370:20220409T095300Z

Regards.

Maurilio


I have investigated further and found out that we have some actual
problems with old packages that have been replaced in the past.
The problems became imminent after illumos-gate has merged #14583
developer/opensolaris/osnet requirements cleanup and after shrinking the
repository.
So far I have identified three:
    file/slocate
    runtime/java
    service/network/ftp
and replaced the fmri's with their replacements mlocate, openjdk8 and
proftpd.
There might be more outdated fmri's left that need to be fixed, though.


___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss


Hi!


There are some packages mentioned that are not in "2022":

This should not be a problem. They just haven't been build this year
yet. But you need to make sure that they are still in the repository,
though.
Eg. pkg info -r compress/bzip2@1.0.8-2020.0.1.0
and are in the userland-incorporation meta package.




# zoneadm -z bz-template install 2>&1 |grep 202|grep -v 2022

 Reject:
pkg://openindiana.org/compress/bzip2@1.0.8-2020.0.1.0:20200330T113433Z
 Reject:
pkg://openindiana.org/compress/gzip@1.11-2020.0.1.0:20210903T182240Z
 Reject:
pkg://openindiana.org/compress/unzip@6.0-2020.0.1.5:20200330T113517Z
 Reject:
pkg://openindiana.org/compress/zip@3.0-2020.0.1.1:20200615T163122Z
 Reject:
pkg://openindiana.org/database/berkeleydb-5@5.3.28-2020.0.1.0:20200330T113744Z
 Reject:
pkg://openindiana.org/database/lmdb@0.9.23-2020.0.1.0:20200330T113744Z
 Reject: pkg://openindiana.org/entire@0.5.11-2020.0.1.0:20200330T151713Z
 Reject:
pkg://openindiana.org/library/libedit@3.1.20181209-2020.0.1.2:20200330T122131Z
 Reject:
pkg://openindiana.org/library/libxml2@2.9.9-2020.0.1.5:20210117T220316Z
 Reject:
pkg://openindiana.org/library/pcre2@10.39-2020.0.1.0:2029T235734Z
 Reject:
pkg://openindiana.org/network/ssh@8.1.0.1-2020.0.1.2:20200512T190142Z
 Reject:
pkg://openindiana.org/runtime/perl-534@5.34.0-2021.0.0.0:20211229T151048Z
 Reject:
pkg://openindiana.org/runtime/python-35@3.5.10-2020.0.1.0:20201014T142618Z
 Reject:
pkg://openindiana.org/service/management/sysding@0.5.11-2020.0.1.33:20200521T214606Z
 Reject:
pkg://openindiana.org/service/network/ssh@8.1.0.1-2020.0.1.2:20200512T190154Z
 Reject:
pkg://openindiana.org/system/ca-certificates@0.0.1.20170919-2020.0.1.0:20200330T152439Z
 Reject:
pkg://openindiana.org/system/library/gcc-7-runtime@7.5.0-2020.0.1.9:20210819T195607Z

Thank you for having a look at it!

Stephan



___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss



___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] can't install a new zone

[Stephan Althaus]

On 4/10/22 09:56, Andreas Wacknitz wrote:

Am 09.04.22 um 18:38 schrieb Maurilio Longo via openindiana-discuss:

No problem Andreas,

it is at 15370

$ pkg info userland-incorporation
  Name: consolidation/userland/userland-incorporation
   Summary: userland consolidation incorporation
(consolidation/userland/userland-incorporation)
   Description: This incorporation constrains packages from the 
userland

    consolidation
  Category: Meta Packages/Incorporations
 State: Installed
 Publisher: openindiana.org
   Version: 0.5.11
    Branch: 2022.0.0.15370
    Packaging Date: Sat Apr  9 09:53:00 2022
Last Install Time: Sun Oct 31 19:39:21 2021
  Last Update Time: Sat Apr  9 12:01:18 2022
  Size: 0.00 B
  FMRI: 
pkg://openindiana.org/consolidation/userland/userland-incorporation@0.5.11-2022.0.0.15370:20220409T095300Z


Regards.

Maurilio


I have investigated further and found out that we have some actual
problems with old packages that have been replaced in the past.
The problems became imminent after illumos-gate has merged #14583
developer/opensolaris/osnet requirements cleanup and after shrinking the
repository.
So far I have identified three:
    file/slocate
    runtime/java
    service/network/ftp
and replaced the fmri's with their replacements mlocate, openjdk8 and
proftpd.
There might be more outdated fmri's left that need to be fixed, though.


___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss


Hi!


There are some packages mentioned that are not in "2022":

# zoneadm -z bz-template install 2>&1 |grep 202|grep -v 2022

 Reject: 
pkg://openindiana.org/compress/bzip2@1.0.8-2020.0.1.0:20200330T113433Z
 Reject: 
pkg://openindiana.org/compress/gzip@1.11-2020.0.1.0:20210903T182240Z
 Reject: 
pkg://openindiana.org/compress/unzip@6.0-2020.0.1.5:20200330T113517Z

 Reject: pkg://openindiana.org/compress/zip@3.0-2020.0.1.1:20200615T163122Z
 Reject: 
pkg://openindiana.org/database/berkeleydb-5@5.3.28-2020.0.1.0:20200330T113744Z
 Reject: 
pkg://openindiana.org/database/lmdb@0.9.23-2020.0.1.0:20200330T113744Z

 Reject: pkg://openindiana.org/entire@0.5.11-2020.0.1.0:20200330T151713Z
 Reject: 
pkg://openindiana.org/library/libedit@3.1.20181209-2020.0.1.2:20200330T122131Z
 Reject: 
pkg://openindiana.org/library/libxml2@2.9.9-2020.0.1.5:20210117T220316Z
 Reject: 
pkg://openindiana.org/library/pcre2@10.39-2020.0.1.0:2029T235734Z
 Reject: 
pkg://openindiana.org/network/ssh@8.1.0.1-2020.0.1.2:20200512T190142Z
 Reject: 
pkg://openindiana.org/runtime/perl-534@5.34.0-2021.0.0.0:20211229T151048Z
 Reject: 
pkg://openindiana.org/runtime/python-35@3.5.10-2020.0.1.0:20201014T142618Z
 Reject: 
pkg://openindiana.org/service/management/sysding@0.5.11-2020.0.1.33:20200521T214606Z
 Reject: 
pkg://openindiana.org/service/network/ssh@8.1.0.1-2020.0.1.2:20200512T190154Z
 Reject: 
pkg://openindiana.org/system/ca-certificates@0.0.1.20170919-2020.0.1.0:20200330T152439Z
 Reject: 
pkg://openindiana.org/system/library/gcc-7-runtime@7.5.0-2020.0.1.9:20210819T195607Z


Thank you for having a look at it!

Stephan



___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] can't install a new zone

[Andreas Wacknitz]

Am 09.04.22 um 18:38 schrieb Maurilio Longo via openindiana-discuss:

No problem Andreas,

it is at 15370

$ pkg info userland-incorporation
  Name: consolidation/userland/userland-incorporation
   Summary: userland consolidation incorporation
(consolidation/userland/userland-incorporation)
   Description: This incorporation constrains packages from the userland
consolidation
  Category: Meta Packages/Incorporations
 State: Installed
 Publisher: openindiana.org
   Version: 0.5.11
Branch: 2022.0.0.15370
Packaging Date: Sat Apr  9 09:53:00 2022
Last Install Time: Sun Oct 31 19:39:21 2021
  Last Update Time: Sat Apr  9 12:01:18 2022
  Size: 0.00 B
  FMRI: 
pkg://openindiana.org/consolidation/userland/userland-incorporation@0.5.11-2022.0.0.15370:20220409T095300Z

Regards.

Maurilio


I have investigated further and found out that we have some actual
problems with old packages that have been replaced in the past.
The problems became imminent after illumos-gate has merged #14583
developer/opensolaris/osnet requirements cleanup and after shrinking the
repository.
So far I have identified three:
    file/slocate
    runtime/java
    service/network/ftp
and replaced the fmri's with their replacements mlocate, openjdk8 and
proftpd.
There might be more outdated fmri's left that need to be fixed, though.


___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] OI Hipster becomes unreachable over network after a certain length of uptime

[Stephan Althaus]

On 4/10/22 04:13, Judah Richardson wrote:

Finally got around to looking into this ongoing issue.

On Thu, Dec 23, 2021 at 2:28 PM Judah Richardson 
wrote:



On Thu, Dec 23, 2021 at 11:36 AM s...@pandora.be  wrote:


Do you still have access to a console when the system is 'unreachable'
over the network ?


Yes, I do.


If you still have a text console on the system which became unreachable,
perhaps you could check before rebooting whether you can see any errors on
the NIC.

For example using:

# dladm show-link -s rge0

When I run the above command on system with a e1000g0 interface, it
prints IERRORS / OERRORS in the show-link -s e1000g0 output, so hopefully
it also prints those statistics for rge0.


Doesn't show any errors on this end.

Also maybe there are error messages in the /var/adm/messages related to
rge0.


No errors there either.

Seems to be a problem within the OS itself, perhaps in relation to that
particular NIC.



These are good ideas, thanks. I'll try them next time it happens and then
report back.



Regards,
David Stes

- Op 22 dec 2021 om 8:56 schreef Judah Richardson
judahrichard...@gmail.com:


On Tue, Dec 21, 2021 at 2:06 AM Joshua M. Clulow 

wrote:

On Mon, 20 Dec 2021 at 22:26, Judah Richardson
 wrote:

On Tue, Dec 21, 2021 at 12:23 AM Joshua M. Clulow via

openindiana-discuss  wrote:

Any logs or anything like that in particular I should take a look

at?

What driver is in use?

How do I determine this?

What do you see in "ipadm show-addr"

$ sudo ipadm show-addr
Password:
ADDROBJ   TYPE STATEADDR
lo0/v4static   ok   127.0.0.1/8
rge0/_b   dhcp ok   192.168.0.71/24
lo0/v6static   ok   ::1/128
rge0/_a   addrconf ok   fe80::7a45:c4ff:fe14:10a4/10

and "dladm show-ether"?

~$ sudo dladm show-ether
LINKPTYPESTATEAUTO  SPEED-DUPLEX
PAUSE
rge0current  up   no1G-f

none

  By

default, NICs are named with the driver you're using; e.g., "bge0" is
an instance of the "bge" driver.


What model of NIC is it?

It's an onboard Realtek NIC.

If you "pkg install diagnostic/pci" you should be able to:

 /usr/lib/pci/pcieadm show-devs -o bdf,vid,did,driver,vendor,device


$ sudo /usr/lib/pci/pcieadm show-devs -o

bdf,vid,did,driver,vendor,device

BDF VID   DID   DRIVER VENDORDEVICE
0/0/0   8086  100   -- Intel Corporation 2nd
Generation Core Processor Family DRAM Controller
0/2/0   8086  102   i9150  Intel Corporation 2nd
Generation Core Processor Family Integrated Graphics Controller
0/16/0  8086  1c3a  -- Intel Corporation 6
Series/C200 Series Chipset Family MEI Controller #1
0/1a/0  8086  1c2d  ehci0  Intel Corporation 6
Series/C200 Series Chipset Family USB Enhanced Host Controller #2
0/1b/0  8086  1c20  audiohd0   Intel Corporation 6
Series/C200 Series Chipset Family High Definition Audio Controller
0/1c/0  8086  1c10  -- Intel Corporation 6
Series/C200 Series Chipset Family PCI Express Root Port 1
0/1c/2  8086  1c14  pcieb1 Intel Corporation 6
Series/C200 Series Chipset Family PCI Express Root Port 3
0/1c/4  8086  1c18  pcieb2 Intel Corporation 6
Series/C200 Series Chipset Family PCI Express Root Port 5
3/0/0   10ec  8168  rge0   Realtek Semiconductor Co., Ltd.
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
0/1d/0  8086  1c26  ehci1  Intel Corporation 6
Series/C200 Series Chipset Family USB Enhanced Host Controller #1
0/1f/0  8086  1c5c  isa0   Intel Corporation H61
Express Chipset LPC Controller
0/1f/2  8086  1c00  pci-ide0   Intel Corporation 6
Series/C200 Series Chipset Family Desktop SATA Controller (IDE mode,

ports

0-3)
0/1f/3  8086  1c22  -- Intel Corporation 6
Series/C200 Series Chipset Family SMBus Controller
0/1f/5  8086  1c08  pci-ide1   Intel Corporation 6
Series/C200 Series Chipset Family Desktop SATA Controller (IDE mode,

ports

4-5)



e.g., I can see, on one of my systems:

0/1f/6  8086  15b7  e1000g0Intel Corporation
Ethernet Connection (2) I219-LM


Cheers.

--
Joshua M. Clulow
http://blog.sysmgr.org


___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss


___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss


Hi!

The last few weeks i had some related symptom, that my