Octopkg problems?

[NeverSimple]

It seems that others have succes with using OctoPkg, but for me it doesn't seem to work.
See attached screenshot for the output errors.
If I click on one of the URL's shown in the screenshot, Firefox opens with more or less the same error: "The requested URL /GhostBSD-11/amd64/test/meta.txz: was not found on this server"
It looks like there is a colon at the end of the URL, that shouldn't be there. Don't know if it's part of the error message, or part of the URL. If I remove it within Firefox, it finds the correct URL.

Using GhostBSD 11.1 ALPHA1

EDIT: Nevermind... I have another machine updated to 11.1 BETA1 and there it works fine. So it's probably already fixed.

[ASX]

"no address record" usually means that there is a DNS issue, e.g. you have connectivity but the DNS is not set properly or is not working.

[NeverSimple]

"no address record" usually means that there is a DNS issue, e.g. you have connectivity but the DNS is not set properly or is not working.

Agreed. But it is consistent. Happens always, while mail or Firefox have no problems with address resolution. I do not assume that Octopkg has it's own resolver config, or something like that.
And if I copy that URL, paste it into Firefox (but remove the colon) it works immediately.

But, like I said, it seems to work in the current BETA release, so probably not an issue anymore.

[ASX]

Hmmm .... I have read some similar report in the past, and it turned out to be a problem IPv6 related.

you could try, for test, running the following two commands:

Code: Select all

pkg -4 update
pkg -6 update

the first will make use of IPv4, the second will use IPv6.
Apparently firefox is able to discriminate the right protocol itself, pkg is not.

I know that our pkg server is located on a IPv6 enabled datacenter, but is possible that the IPv6 DNS is not set, will check about that with ericbsd.

[NeverSimple]

Hmmm .... I have read some similar report in the past, and it turned out to be a problem IPv6 related.

You could be on to something...

Code: Select all

rherman@ghostbsd ~/Desktop> sudo pkg -4 update
Password:
Updating GhostBSD repository catalogue...
pkg: Repository GhostBSD load error: access repo file(/var/db/pkg/repo-GhostBSD.sqlite) failed: No such file or directory
Fetching meta.txz: 100%    260 B   0.3kB/s    00:01    
Fetching packagesite.txz: 100%    6 MiB   3.1MB/s    00:02    
Processing entries: 100%
GhostBSD repository update completed. 26939 packages processed.
All repositories are up to date.

rherman@ghostbsd ~/Desktop> sudo pkg -4 update
Updating GhostBSD repository catalogue...
GhostBSD repository is up to date.
All repositories are up to date.

rherman@ghostbsd ~/Desktop> sudo pkg -6 update
Updating GhostBSD repository catalogue...
pkg: http://pkg.GhostBSD.org/GhostBSD-11/amd64/test/meta.txz: No address record
repository GhostBSD has no meta file, using default settings
pkg: http://pkg.GhostBSD.org/GhostBSD-11/amd64/test/packagesite.txz: No address record
Unable to update repository GhostBSD
Error updating repositories!
rherman@ghostbsd ~/Desktop> 

Could also be that IPv6 networking is disabled for my NIC. Can't see an inet6 entry for it, only for my loopback device. But since 'pkg -4 update' works, that should be the fallback, shouldn't it?

[ASX]

Definitely something IPv4 vs. IPv6 related, however we need more info to understand what is going on.
Please post the complete output of the following commands:

Code: Select all

ifconfig

Code: Select all

cat /etc/resolv.conf

Code: Select all

ping -c 1 pkg.ghostbsd.org

Code: Select all

ping6 -c 1 pkg.ghostbsd.org

Code: Select all

netstat -rn4

Code: Select all

netstat -rn6

[NeverSimple]

Please post the complete output of the following commands:

Here you go:

#ifconfig

Code: Select all

em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
	options=4019b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,VLAN_HWTSO>
	ether xx:xx:xx:xx:xx:xx
	hwaddr xx:xx:xx:xx:xx:xx
	inet 192.168.28.35 netmask 0xffffff00 broadcast 192.168.28.255 
	nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
	media: Ethernet autoselect (1000baseT <full-duplex>)
	status: active
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
	options=600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6>
	inet6 ::1 prefixlen 128 
	inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2 
	inet 127.0.0.1 netmask 0xff000000 
	nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
	groups: lo 

# Generated by resolvconf

Code: Select all

search neversimple.nl
nameserver 192.168.28.1

#ping -c 1 pkg.ghostbsd.org

Code: Select all

PING pkg.ghostbsd.org (167.114.206.135): 56 data bytes
64 bytes from 167.114.206.135: icmp_seq=0 ttl=52 time=89.681 ms

--- pkg.ghostbsd.org ping statistics ---
1 packets transmitted, 1 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 89.681/89.681/89.681/0.000 ms
Routing tables

#ping6 -c 1 pkg.ghostbsd.org

Code: Select all

ping6: hostname nor servname provided, or not known

#netstat -rn4

Code: Select all

Internet:
Destination        Gateway            Flags     Netif Expire
default            192.168.28.1       UGS         em0
127.0.0.1          link#2             UH          lo0
192.168.28.0/24    link#1             U           em0
192.168.28.35      link#1             UHS         lo0
Routing tables

#netstat -rn6

Code: Select all

Internet6:
Destination                       Gateway                       Flags     Netif Expire
::/96                             ::1                           UGRS        lo0
::1                               link#2                        UH          lo0
::ffff:0.0.0.0/96                 ::1                           UGRS        lo0
fe80::/10                         ::1                           UGRS        lo0
fe80::%lo0/64                     link#2                        U           lo0
fe80::1%lo0                       link#2                        UHS         lo0
ff02::/16                         ::1                           UGRS        lo0

NOTE: ping6 also fails on another computer that's running GhostBSD 11.1-BETA1, where Octopkg runs fine. The other results are identical on that computer.

[ASX]

NOTE: ping6 also fails on another computer that's running GhostBSD 11.1-BETA1, where Octopkg runs fine. The other results are identical on that computer.

Thanks, this is a good info, but unfortunately it means the informations I requested are not enough to discriminate the issue.
Btw, your results looks fine are are quite similar to my own results, let aside the obvious difference.

Next question that come to my mind is: is that issue confined to octopkg or affect pkg too ?

please, try this:

Code: Select all

pkg update -f

then, because you have two similar systems available, one affactect from the issue and the other don't affected, you are in the best position to evaluate the differences.

You could compare them about services and packages, run on both system:

Code: Select all

service -e

Code: Select all

pkg leaf

Code: Select all

pkg -vv

For each of the above, please see what is different between the two systems.

[NeverSimple]

Next question that come to my mind is: is that issue confined to octopkg or affect pkg too ?

please, try this:

Code: Select all

pkg update -f

First time I ran the command:

Code: Select all

rherman@ghostbsd ~/Desktop> sudo pkg update -f
Password:
Updating GhostBSD repository catalogue...
pkg: Repository GhostBSD load error: access repo file(/var/db/pkg/repo-GhostBSD.sqlite) failed: No such file or directory
Fetching meta.txz: 100%    260 B   0.3kB/s    00:01    
Fetching packagesite.txz: 100%    6 MiB   3.1MB/s    00:02    
Processing entries: 100%
GhostBSD repository update completed. 26939 packages processed.
All repositories are up to date.

second time I ran the command:

Code: Select all

rherman@ghostbsd ~/Desktop> sudo pkg update -f
Updating GhostBSD repository catalogue...
Fetching meta.txz: 100%    260 B   0.3kB/s    00:01    
Fetching packagesite.txz: 100%    6 MiB   3.1MB/s    00:02    
Processing entries: 100%
GhostBSD repository update completed. 26939 packages processed.
All repositories are up to date.

You could compare them about services and packages, run on both system:

I send the output of all 3 below to a file on both computers and did a diff between them (diff 'file-from-11.1-ALPHA1' 'file-from-11.1-BETA1'. The results are less then spectaculair, I'm afraid...

Code: Select all

service -e

Code: Select all

4d3
< /usr/local/etc/rc.d/dbus
8d6
< /usr/local/etc/rc.d/webcamd
15c13,14
< /usr/local/etc/rc.d/xrdp
---
> /usr/local/etc/rc.d/dbus
> /usr/local/etc/rc.d/webcamd
25d23
< /etc/rc.d/sshd

Code: Select all

pkg leaf

Code: Select all

1d0
< cargo-0.19.0
48d46
< lftp-4.8.0
54d51
< nautilus-3.18.5
68d64
< smplayer-17.1.0_1
119a116
> xorg-fonts-7.7_1
123d119
< xrdp-0.6.2,1

Code: Select all

pkg -vv

There were no differences between the output of this on both computers.

For each of the above, please see what is different between the two systems.

Well, I would say, nothing note worthy

[ASX]

Well, I would say, nothing note worthy

I have to agree, but clearly something is different between the two system.

Also, I asked for "pkg leaf" and there I made an error, pkg leaf return only the packages that aren't a dependency, that list exclude all libs.

At least in one case I solved an issue because there was a conflict between a lib and some kde/qt---network related lib, but it was long ago and can't recall the details.

Instead of checking for 'leaf' better to compare all packages:
pkg origin is a good choice (don't know if that is defined in your system, I have it defined but could be I have added it manually),
please try:

Code: Select all

pkg origin

if that doesn't workk use the expanded command (origin is a pkg alias)

Code: Select all

pkg info -qo

sorry, missed that in the previous post.