You are not logged in.
Hello:
... doesn't fix all of it unfortunately.
Indeed ...
It only fixes (not a fix, just a way of avoiding it) the having screwed things up by using CSE in the first place.
There are so many things they could be dedicating time to fix.
But no, skinny bars and CSE it is.
--> Seems they have their own Poeterings at xfce HQ's.
O.
Hello:
More GTK3 ...
... intractable CSD ...
... skinny bars ...
... less usable and fuglier cluster ...
Quite so ...
... IMO ...
And also mine.
I opine that it should not be the default for Devuan.
O.
Hello:
... on the condition that this project does not "die".
If you are referring to Devuan, I doubt it will die.
What is dead to me and (from what I have read) quite a few xfce users is xfce in any form after 4.12.2.
The path the developers have taken, the useless bloat and all the unfixed issues (compositor leading the way) made me decide not to upgrade further.
Not to mention the Poetteringesque attitude from the developers.
https://forum.xfce.org/viewtopic.php?pid=56141#p56141
https://forum.xfce.org/viewtopic.php?pid=56143#p56143
https://forum.xfce.org/viewtopic.php?pid=56144#p56144
Still have to decide what to use, the strongest/more suitable option I see being Openbox if and when I upgrade to Chimaera.
I think it should be the default Devuan desktop from Chimaera onwards.
ie: with a desktop as similar as possible to what Philip Newborough's CrunchBang project was.
Unfortunately, CrunchBang developement was ended by it's developer back in 02/2015. It was (YMMV) one of the best distributions at the time.
Best,
A.
Hello:
OMG I hope not.
+1
Best,
A.
Hello:
... from installing debian on a day to day laptop and over a dozen eee ...
The same stuff I have.
A Sun Ultra24 and an Asus 1000HE with 2Gb RAM and 500Gb HDD.
Gnome keyring optionally protects you from lazy login security risk on regular laptop.
I see.
Please excuse my ignorance in this specific matter (there are others but I digress ...)
I have gnome-keyring in my U24's Devuan installation but I see that I also have a few other keyrings.
debian-archive-keyring
devuan-keyring
python-keyring
python-keyrings.alt
python3-keyring
python3-keyrings.altUntil my issues with Back-in-Time, all this keyring thing had always been transparent to me, to the extent that I don't really know what it does.
The cron job running BiT sends a warning every so often (can't reproduce) but the job gets done with no problems and that is why I'm looking at gnome-keyring now.
I have read that BiT has to see at least one of these is installed: python-keyring-kwallet, python-secretstorage and python-gnomekeyring.
Of those three, my installation has python-secretstorage but has a problem if gnome-keyring is not there.
Maybe I should purge gnome-keyring and install python-gnomekeyring?
If gnome-keyring bothers you, remove it ...
Not really bother, just that with the exception of gnome-disks which I use every so often, I am sort of allergic to gnome so I'd rather avoid it.
But gnome-disks does not depend on gnome-keyring.
Thank you for your input.
Best,
A.
Hello:
Any ideas as to how I can troubleshoot this?
I rolled back and reinstalled gnome-keyring.
The same gnome-keyring that, along with gvfs-backends is a recommends of pcmanfm.
And that fixed it:
groucho@devuan:~$ keyring get system username
groucho@devuan:~$ keyring get system username opens up a window asking for a PW.
Edit:
The window name is Unlock Login Keyring and the contents reads:
------
Enter password to unlock your login keyring
The login keyring did not get unlocked when you logged in to your computer.
Password: . .
------
I had previously tried using the gnome-disks application without gnome-keyring installed and it worked perfectly well: I was asked for a PW to mount a drive.
There were no problems with gnome-keyring not being installed.
But why is this so?
Anyone has a clue about this?
Why isn't gnome-keyring a dependency if it is needed?
Which would beg the question: why is gnome-keyring needed if there are a few other keyrings installed?
debian-archive-keyring
devuan-keyring
python-keyring
python-keyrings.alt
python3-keyring
python3-keyrings.altI searched yet some more and found a lead here:
... realized that the problem was not limited just to Docker, any services using libsecret were broken. As I use KeePassXC with libsecret integration I took a look in the settings and it turns out the integration was disabled. I purged the gnome-keyring package again, killed the gnome-keyring service and enabled the KeePassXC integration and it all worked as usual.
I'd appreciate some insight on this.
ie: why must I have gnome-keyring installed.
Thanks in advance.
Best,
A.
Hello:
Logging in automatically to desktop ...
No, not for me.
... asks for login password when launching google-chrome.
Don't use that one, at least for the time being.
Thanks for your input.
Best,
A.
Hello:
I'll post back if I get another message or in a fortnight, whatever comes first.
BiT is apparently working properly and cron has not sent me any mails.
But to check, I ran it manually and this is what I got:
user@devuan:~$ backintime backup
Gkr-Message: 08:42:53.971: secret service operation failed: The name org.freedesktop.secrets was not provided by any .service files
Back In Time
Version: 1.1.24
Back In Time comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to redistribute it
under certain conditions; type `backintime --license' for details.
INFO: Lock
WARNING: Inhibit Suspend failed.
WARNING: import keyring failed
INFO: Take a new snapshot. Profile: 1 Main profile
INFO: [qt4systrayicon] begin loop
INFO: Call rsync to take the snapshot
INFO: Save config file
INFO: Create info file
INFO: Remove backups older than: 20220117-000000
INFO: Keep min free disk space: 40960 MiB
INFO: Keep min 5% free inodes
INFO: Unlock
user@devuan:~$ INFO: [qt4systrayicon] end loopThe terminal output shows the import keyring failed warning is still there.
ie: whether gnome-keyring is installed or not, so it does not seem to be the what causes the BiT problem.
Then I tried checking the keyring:
user@devuan:~$ keyring get system username
Gkr-Message: 09:17:24.950: secret service operation failed: The name org.freedesktop.secrets was not provided by any .service files
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/dbus/bus.py", line 175, in activate_name_owner
return self.get_name_owner(bus_name)
File "/usr/lib/python3/dist-packages/dbus/bus.py", line 361, in get_name_owner
's', (bus_name,), **keywords)
File "/usr/lib/python3/dist-packages/dbus/connection.py", line 651, in call_blocking
message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NameHasNoOwner: Could not get owner of name 'org.freedesktop.secrets': no such name
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/secretstorage/util.py", line 55, in bus_get_object
return bus.get_object(name, object_path, introspect=False)
File "/usr/lib/python3/dist-packages/dbus/bus.py", line 241, in get_object
follow_name_owner_changes=follow_name_owner_changes)
File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 248, in __init__
self._named_service = conn.activate_name_owner(bus_name)
File "/usr/lib/python3/dist-packages/dbus/bus.py", line 180, in activate_name_owner
self.start_service_by_name(bus_name)
File "/usr/lib/python3/dist-packages/dbus/bus.py", line 278, in start_service_by_name
'su', (bus_name, flags)))
File "/usr/lib/python3/dist-packages/dbus/connection.py", line 651, in call_blocking
message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.secrets was not provided by any .service files
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/keyring/backends/SecretService.py", line 35, in priority
list(secretstorage.get_all_collections(bus))
File "/usr/lib/python3/dist-packages/secretstorage/collection.py", line 144, in get_all_collections
service_obj = bus_get_object(bus, SS_PATH)
File "/usr/lib/python3/dist-packages/secretstorage/util.py", line 59, in bus_get_object
raise SecretServiceNotAvailableException(e.get_dbus_message())
secretstorage.exceptions.SecretServiceNotAvailableException: The name org.freedesktop.secrets was not provided by any .service files
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/bin/keyring", line 11, in <module>
load_entry_point('keyring==17.1.1', 'console_scripts', 'keyring')()
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 489, in load_entry_point
return get_distribution(dist).load_entry_point(group, name)
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2793, in load_entry_point
return ep.load()
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2411, in load
return self.resolve()
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2417, in resolve
module = __import__(self.module_name, fromlist=['__name__'], level=0)
File "/usr/lib/python3/dist-packages/keyring/__init__.py", line 3, in <module>
from .core import (
File "/usr/lib/python3/dist-packages/keyring/core.py", line 189, in <module>
init_backend()
File "/usr/lib/python3/dist-packages/keyring/core.py", line 97, in init_backend
or load_config()
File "/usr/lib/python3/dist-packages/keyring/core.py", line 176, in load_config
return load_keyring(keyring_name)
File "/usr/lib/python3/dist-packages/keyring/core.py", line 137, in load_keyring
class_.priority
File "/usr/lib/python3/dist-packages/keyring/util/properties.py", line 26, in __get__
return self.fget.__get__(None, owner)()
File "/usr/lib/python3/dist-packages/keyring/backends/SecretService.py", line 38, in priority
"Unable to initialize SecretService: %s" % e)
RuntimeError: Unable to initialize SecretService: The name org.freedesktop.secrets was not provided by any .service files
user@devuan:~$ What the ...
Not expected.
But if I check as root I get this:
[root@devuan ~]# keyring get system username
[root@devuan ~]# It seems the keyring has some sort of issue with my user or vice-versa.
But not with root.
Looking up the first error ie: org.freedesktop.DBus.Error.NameHasNoOwner here just gets me a rather obvious answer:
Description
In addition to the error names user programs define, D-Bus knows a number of generic, standardized error names that are listed below.
In addition to this list, in sd-bus, the special error namespace "System.Error." is used to map arbitrary Linux system errors (as defined by errno(3)) to D-Bus errors and back. For example, the error EUCLEAN is mapped to "System.Error.EUCLEAN" and back.
--- snip ---
SD_BUS_ERROR_NAME_HAS_NO_OWNER
The specified bus service name currently has no owner.
--- snip ---
That this does not happen as root makes sense as root owns the rig/OS and everything that goes on in it.
Is this a permissions issue for my user?
Is it a phython script problem?
eg: File "/usr/lib/python3/dist-packages/dbus/bus.py", line 175, in activate_name_owner
Any ideas as to how I can troubleshoot this?
Thanks in advance.
Best,
A.
Hello:
... look into that some more.
I have thought about it and have not found reason (save the pcmanfm recomends) for having gnome-keyring installed.
Same for gvfs-backends for that matter.
ie: my basic reasoning is that they are not dependencies, just pcmanfm recommends.
And I have seen that recommends can sometimes be silently problematic.
On a hunch, I wondered if this problem isn't being caused by having too many ***-keyring instances?
user@devuan:~$ apt list | grep installed | grep keyring
--- snip ---
debian-archive-keyring/oldstable,oldstable,now 2019.1+deb10u1 all [installed]
devuan-keyring/oldstable,oldstable,now 2022.09.04 all [installed]
gir1.2-gnomekeyring-1.0/now 3.12.0-1+b2 amd64 [installed,local]
libgnome-keyring-common/now 3.12.0-1 all [installed,local]
libgnome-keyring0/now 3.12.0-1+b2 amd64 [installed,local]
python-keyring/oldstable,oldstable,now 17.1.1-1 all [installed,automatic]
python-keyrings.alt/oldstable,oldstable,now 3.1.1-1 all [installed,automatic]
python3-keyring/oldstable,oldstable,now 17.1.1-1 all [installed,automatic]
python3-keyrings.alt/oldstable,oldstable,now 3.1.1-1 all [installed,automatic]
user@devuan:~$ There's one sure way to find out: purge both gnome-keyring and gvfs-backends, which I did at noon today.
I have observed no ill effects after three or four reboots, mounting/unmounting of Palm T|Xs, external USB HDs and six hours uptime.
Now I'll just wait to see if I get any more mail in my mbox regarding BiT or whatever keyring.
Any suggestions?
Tests to do?
I'll post back if I get another message or in a fortnight, whatever comes first.
Best,
A.
Hello:
... gvfs-* packages are useful for the mounting features ...
I see.
Yes, I have pcmanfm installed.
Not strictly needed, but quite handy.
It is only suggested by pcmanfm and not a dependency.
But I do depend on cron and backintime to work properly.
I'll have to look into that some more.
Thanks for your input.
Best,
A.
Hello:
I am still dealing with an issue already reported upstream and with BackinTime.
https://dev1galaxy.org/viewtopic.php?pid=30374
Unsurprisingly, no news from upstream but it is now being worked on by the BiT people.
Under new management (so to speak) as the package's maintainance had been severely neglected/abandoned for more than a couple of years.
I have recently come across a post which would apparently suggest that gnome-keyring could be having something to do with it.
Can't find it now. 8^/
It happens that I do have gnome-keyring installed ...
[root@devuan ~]# apt list | grep keyring | grep gnome | grep installed
--- snip ---
gir1.2-gnomekeyring-1.0/now 3.12.0-1+b2 amd64 [installed,local]
gnome-keyring-pkcs11/oldstable,now 3.28.2-5 amd64 [installed,automatic]
gnome-keyring/oldstable,now 3.28.2-5 amd64 [installed,automatic]
libgnome-keyring-common/now 3.12.0-1 all [installed,local]
libgnome-keyring0/now 3.12.0-1+b2 amd64 [installed,local]
libpam-gnome-keyring/oldstable,now 3.28.2-5 amd64 [installed,automatic]
[root@devuan ~]# ... and when I ask aptitude I get this:
[root@devuan ~]# aptitude why gnome-keyring
i pcmanfm Recommends gvfs-backends
i A gvfs-backends Recommends gnome-keyring
[root@devuan ~]# So I also asked about gvfs-backends:
[root@devuan ~]# aptitude why gvfs-backends
i pcmanfm Recommends gvfs-backends
[root@devuan ~]# Does not seem like I need one or the other.
Does it?
Q: can I safely get rid of both gnome-keyring and gvfs-backends without screwing up something else?
Thanks in advance.
Best,
A.
Edit: format, spelling.
Hello:
I'll try it out and see how it goes.
Unfortunately, adding the string had no effect whatsoever.
Any other idea?
Maybe different sting?
Thanks in advance.
Best,
A.
Hello:
Fringe browser labels Devuan ...
It is the chaps at Pi-Hole that consider Devuan a fringe OS.
The Discourse chaps have PaleMoon as unsupported.
... you can probably cheat by just changing your user-agent...
... add a string in about:config, eg :
preference name : general.useragent.override.discourse.pi-hole.net
value : Mozilla/5.0 (Windows NT 6.1; rv:42.0) Gecko/20100101 Firefox/91.0
Thanks to both for the input. 8^)
I'll try it out and see how it goes.
Best,
A.
Hello:
I use PaleMoon and today I found that yet another (the first one was the Pi-Hole forum) that will not accept it as it is considered an unsupported browser.
Knowing about their stance on Devuan (labelled by one of their mods as a fringe OS) I first thought it was just <i>their</i> thing.
But no.
The OpenWRT forum also considers PaleMoon an unsupported browser.
A link on their web site takes you to https://www.discourse.org/about#browser.
What are the minimum browser requirements?
Discourse is designed for the next 10 years of the Internet, so the minimum browser requirements are high.
Discourse supports the latest, stable releases of all major browsers and platforms:Microsoft Edge
Google Chrome
Mozilla Firefox
Apple SafariAdditionally, we aim to support Safari on iOS 12.5+ until January 2023 (Discourse 3.0).
What a load of BS.
If anything, using one of the listed browsers is a real pain the the ass.
Is there anything that can be done to cheat Discourse's check?
Thanks in advance.
Best,
A.
Hello:
... tried plugging the card reader into the Asus 1000HE ...
Yes.
Right before I ripped it open to see the contacts in bad shape.
I wanted to recover the quality cable/ferrite filter/USB plug combo I rescued from an old Palm IV base and grafted on to it when the original cable went bad.
It is USB 1.1 or 2.0 but worth keeping, it is like new.
They really don't make stuff like they used to. 8^|
Best,
A.
Hello:
... a new sdcard reader; perhaps that the card is EXFAT formatted and the reader can't handle that.
But it always did.
I've had the reader working without much ado for the longest while.
But you are quite right ....
I can confirm that the SD card can be read perfectly well on my Asus 1000HE's on-board port.
I think the thingy finally gave up the ghost, must be 5/6 years old.
I'll mark this thread as solved and get myself a new reader tomorrow.
Thanks for your input.
Best,
A.
Hello:
Looks like it doesn't have a partition table ...
Can you mount it manually?
Hmm ...
Not the last time I tried.
Let's see now.
Plugged it into the erader and the reader into the socket.
dmesg says:
[ 347.180602] usb 5-5: new high-speed USB device number 5 using ehci-pci
[ 347.337732] usb 5-5: New USB device found, idVendor=14cd, idProduct=125a, bcdDevice= 2.00
[ 347.337737] usb 5-5: New USB device strings: Mfr=1, Product=3, SerialNumber=2
[ 347.337740] usb 5-5: Product: Mass Storage Device
[ 347.337742] usb 5-5: Manufacturer: Generic
[ 347.337745] usb 5-5: SerialNumber: 812520090519
[ 347.338023] usb-storage 5-5:1.0: USB Mass Storage device detected
[ 347.338187] scsi host7: usb-storage 5-5:1.0
[ 348.369261] scsi 7:0:0:0: Direct-Access USB Mass Storage Device PQ: 0 ANSI: 0 CCS
[ 348.369596] sd 7:0:0:0: Attached scsi generic sg2 type 0
[ 348.371680] sd 7:0:0:0: [sdc] 3842048 512-byte logical blocks: (1.97 GB/1.83 GiB)
[ 348.372368] sd 7:0:0:0: [sdc] Write Protect is off
[ 348.372372] sd 7:0:0:0: [sdc] Mode Sense: 03 00 00 00
[ 348.372994] sd 7:0:0:0: [sdc] No Caching mode page found
[ 348.372999] sd 7:0:0:0: [sdc] Assuming drive cache: write through
[ 348.434000] sd 7:0:0:0: [sdc] Attached SCSI removable disk
~$ But, as before, it is not seen in the file manager.
~$ sudo mount /dev/sdc /mnt
[sudo] password for groucho:
mount: /mnt: wrong fs type, bad option, bad superblock on /dev/sdc, missing codepage or helper program, or other error.
~$ Hmmm ...
Rather ambiguous.
ie: this, that or any other. 8^D
groucho@devuan:~$ sudo findmnt /mnt
groucho@devuan:~$ The SD card is healthy as far as the camera it is used on concerns: I can se the contents and write to the card.
I think the FS is FAT16.
Thanks for your input.
Best,
A.
Hello:
For the longest while I have had this problem in a sort of on/off way.
ie: does not happen all the time, but always happens when I need to see the SD's contents.
eg:
I plug in the SD card into the reader and the reader into one of the my box's USB sockets.
I then open the file manager PCManFM 1.3.1 but the SD card has not been mounted.
So I check dmesg:
~$ sudo dmesg
--- snip ---
[ 3029.553100] usb 5-5: new high-speed USB device number 4 using ehci-pci
[ 3029.710237] usb 5-5: New USB device found, idVendor=14cd, idProduct=125a, bcdDevice= 2.00
[ 3029.710241] usb 5-5: New USB device strings: Mfr=1, Product=3, SerialNumber=2
[ 3029.710244] usb 5-5: Product: Mass Storage Device
[ 3029.710246] usb 5-5: Manufacturer: Generic
[ 3029.710249] usb 5-5: SerialNumber: 812520090519
[ 3029.739442] usb-storage 5-5:1.0: USB Mass Storage device detected
[ 3029.739977] scsi host8: usb-storage 5-5:1.0
[ 3029.740084] usbcore: registered new interface driver usb-storage
[ 3029.743230] usbcore: registered new interface driver uas
[ 3030.765763] scsi 8:0:0:0: Direct-Access USB Mass Storage Device PQ: 0 ANSI: 0 CCS
[ 3030.766106] sd 8:0:0:0: Attached scsi generic sg6 type 0
[ 3030.767372] sd 8:0:0:0: [sdg] 3842048 512-byte logical blocks: (1.97 GB/1.83 GiB) <---- here it is
[ 3030.768873] sd 8:0:0:0: [sdg] Write Protect is off
[ 3030.768878] sd 8:0:0:0: [sdg] Mode Sense: 03 00 00 00
[ 3030.769496] sd 8:0:0:0: [sdg] No Caching mode page found
[ 3030.769501] sd 8:0:0:0: [sdg] Assuming drive cache: write through
[ 3030.822495] sd 8:0:0:0: [sdg] Attached SCSI removable disk
~$ Sure enough, there it is: sdg
Then I check with lsblk:
groucho@devuan:~$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 465.8G 0 disk
`-sda1 8:1 0 465.8G 0 part /run/timeshift/backup
sdb 8:16 0 111.8G 0 disk
|-sdb1 8:17 0 28.9G 0 part /
|-sdb2 8:18 0 1K 0 part
|-sdb3 8:19 0 4.1G 0 part [SWAP]
|-sdb5 8:21 0 750M 0 part /var/log
`-sdb6 8:22 0 78.1G 0 part /home
sdc 8:32 0 279.4G 0 disk
`-sdc1 8:33 0 279.4G 0 part
sdd 8:48 0 279.4G 0 disk
`-sdd1 8:49 0 279.4G 0 part /media/storage
sde 8:64 0 68.4G 0 disk
|-sde1 8:65 0 18.6G 0 part
|-sde2 8:66 0 1K 0 part
|-sde3 8:67 0 7.5G 0 part
|-sde5 8:69 0 1.9G 0 part
`-sde6 8:70 0 40.4G 0 part
sdf 8:80 0 279.4G 0 disk
`-sdf1 8:81 0 279.4G 0 part
sdg 8:96 1 1.9G 0 disk <--- no mount point
groucho@devuan:~$ Sure enough, there it is: sdg but it is not mounted.
usbView 2.0 sees it:
Mass Storage Device
Manufacturer: Generic
Serial Number: 812520090519
Speed: 480Mb/s (high)
Bus: 5
Address: 4
USB Version: 2.00
The disks application sees it but states unknown content.
gparted sees it but says unallocated.
And if I put it back in my Minolta Dimage X31, it mounts the SD card and shows me the content and writes new files to it with no problems whatsoever.
Unfortunately, I have not been able to reproduce this problem, so I am at a loss as to how to fix it.
Any ideas?
Thanks in advance.
Best,
A.
Hello:
... was hoping another process (the old pihole?) was holding on to that port.
... can't connect, because the service is not running.
Exactly ...
Would you mind trying this ...
Of course:
root@chimaera:~# cat /etc/pihole/setupVars.conf
WEBPASSWORD=688cee6d6cc168f344644ff376482d3cd6894b5d294962dd41a514887f8972b2
BLOCKING_ENABLED=true
DNSSEC=false
REV_SERVER=false
PIHOLE_INTERFACE=eth0
PIHOLE_DNS_1=127.0.0.1#5335
PIHOLE_DNS_2=
IPV6_ADDRESS=
QUERY_LOGGING=true
INSTALL_WEB_SERVER=true
INSTALL_WEB_INTERFACE=true
LIGHTTPD_ENABLED=true
CACHE_SIZE=10000
DNS_FQDN_REQUIRED=true
DNS_BOGUS_PRIV=true
DNSMASQ_LISTENING=local
root@chimaera:~# root@chimaera:~# service pihole-FTL start
Not running
FTL started!
root@chimaera:~#root@chimaera:~# service pihole-FTL status
[ ] pihole-FTL is not running
root@chimaera:~# It was doing this before.
... check /var/log/pihole/FTL.log for other clues.
These are the last six lines in the log:
[2022-08-20 22:04:12.618 1362M] Successfully accessed setupVars.conf
[2022-08-20 22:04:12.620 1362M] listening on 0.0.0.0 port 53
[2022-08-20 22:04:12.641 1362M] listening on :: port 53
[2022-08-20 22:04:12.655 1366M] PID of FTL process: 1366
[2022-08-20 22:04:12.657 1366M] Listening on port 4711 for incoming IPv4 telnet connections
[2022-08-20 22:04:12.668 1366M] Error opening IPv6 telnet socket: Address family not supported by protocol (97) <------ the only error... a section "Pi-hole diagnosis" ...
It has always read *No issues found*.
... nuke it (including configs) and re-install.
Yes.
Not too fond of that but as I was in a hurry, I did it.
Brings bad memories of Win95/98 ... 8^°
So ...
Been there, done that.
Full nuke, clean install.
No dice, same story.
I am convinced that the problem lies with port 4711 not being accessible to Pi-Hole.
---> BREAKING NEWS <----
Check this:
https://discourse.pi-hole.net/t/ftl-v5- … e/57181/17
Caveat:
The web site does not work with Pale Moon, to them it is an unsupported browser. 8^|
We found the reason why it's failing when no IPv6 is available. We'll prepare a fix for this.
root@chimaera:~# pihole checkout ftl fix/no_telnet_is_okay
Please note that changing branches severely alters your Pi-hole subsystems
Features that work on the master branch, may not on a development branch
This feature is NOT supported unless a Pi-hole developer explicitly asks!
Have you read and understood this? [y/N] y
[✓] Branch fix/no_telnet_is_okay exists
[i] Switching to branch: "fix/no_telnet_is_okay" from "master"
[✓] Downloading and Installing FTL
[✓] Restarting pihole-FTL service...
[✓] Enabling pihole-FTL service to start on reboot...
root@chimaera:~# That fixed it, seems you were on the right track. 8^)
Fortunately they move fast.
Once again, thank you very much for your efforts.
Best,
A.
Hello:
Sorry for the delay ...
... can you open the pihole web admin page?
Yes, no problem with that.
Up at the top left I have this data:
Status
DNS service not running
Load: 0 0 0
Memory usage: 3.1 %
Once I log in, the four screens (green, blue, ochre and red) have no information, just 'NaN'.
If I go to the 'Settings' page, I get the error message I mentioned in previously at the top:
Error
There was a problem applying your settings.
Debugging information:
PHP error (2): fsockopen(): unable to connect to 127.0.0.1:4711 (Connection refused) in /var/www/html/admin/scripts/pi-hole/php/FTL.php:44
The system tab reads:
FTL Information
The FTL service is offline!
re: /etc/pihole/setupVars.conf
... same as mine, except for PIHOLE_DNS_1=127.0.0.1#5335
This might be valid ...
It is.
I have Pi-Hole runninng as a recursive DNS server in a Chimaera headless VM inside my box.
So I use my own DNS server.
--- note start --->
If you want to check on how it is done, check this video: https://www.youtube.com/watch?v=FnFtWsZ8IP0
There are also a couple of web pages: here: https://opensourcelibs.com/lib/pihole-unbound and here: https://medium.com/nerd-for-tech/recurs … a766d4f703
<--- note end ---
My pihole goes out to other DNS servers ...
Mine goes to 192.168.1.3 which is the IP of the Chimaera VM.
This setup was working perfectly well until the last upgrade to Pi-hole v5.11.4 FTL v5.16.2 Web Interface v5.13. 8^°
Maybe it was a combination of that and some Devuan update?
Did we have a Devuan update involving access to port 4711? No idea ...
what happens when you run these ...
I think I tried this one the other day.
[root@devuan ~]# ss -tnlp | grep 4711
[root@devuan ~]# Nothing.
Same as if I try to telnet to the VM from my box:
[root@devuan ~]# telnet 192.168.1.3 4711
Trying 192.168.1.3...
telnet: Unable to connect to remote host: Connection refused
[root@devuan ~]# root@devuan:/etc/pihole# ss -tnlp | grep 4711
No ...
Can't do that.
Pi-hole is not installed up in my box, it is installed in the VM.
So it would be this:
root@chimaera:/etc/pihole# ss -tnlp | grep 4711
root@chimaera:/etc/pihole# Again, nothing.
root@chimaera:/etc/pihole# telnet 127.0.0.1 4711
Trying 127.0.0.1...
telnet: Unable to connect to remote host: Connection refused <----- this is it. But why?
root@chimaera:/etc/pihole# Thank you very much for your efforts.
Much appreciated.
Best,
A.
Hello:
What is the output of:
service lighttpd status
Here it is:
root@chimaera:~# service lighttpd status
lighttpd is running.
root@chimaera:~# FYI, my (very-old) FTL.php contains this:
function connectFTL($address, $port=4711) { if($address == "127.0.0.1") { // Read port $portfile = file_get_contents("/var/run/pihole-FTL.port"); if(is_numeric($portfile)) $port = intval($portfile); } // Open Internet socket connection $socket = @fsockopen($address, $port, $errno, $errstr, 1.0); return $socket; }
I think that whatever is going on has been caused by some change in the Pi-Hole configuration.
... next place to look would be /etc/pihole/setupVars.conf... check if anything looks off in there.
Here it is:
root@chimaera:~# cat /etc/pihole/setupVars.conf
WEBPASSWORD=688cee6d6cc168f344644ff376482d3cd6894b5d294962dd41a514887f8972b2
BLOCKING_ENABLED=true
DNSSEC=false
REV_SERVER=false
PIHOLE_INTERFACE=eth0
PIHOLE_DNS_1=127.0.0.1#5335
PIHOLE_DNS_2=
QUERY_LOGGING=true
INSTALL_WEB_SERVER=true
INSTALL_WEB_INTERFACE=true
LIGHTTPD_ENABLED=true
CACHE_SIZE=10000
DNS_FQDN_REQUIRED=true
DNS_BOGUS_PRIV=true
DNSMASQ_LISTENING=local
root@chimaera:~# At first sight it 'looks' OK.
Not that I'd have much idea ... 8^/
... don't forget the log files: /var/log/pihole/FTL.log and /var/log/pihole/pihole.log
These are the last two lines in /var/log/pihole/FTL.log:
[2022-08-19 18:05:28.675 1140M] Listening on port 4711 for incoming IPv4 telnet connections
[2022-08-19 18:05:28.696 1140M] Error opening IPv6 telnet socket: Address family not supported by protocol (97)As you can see, port 4711 is mentioned.
Surely related to this line in the debugging info:
PHP error (2): fsockopen(): unable to connect to 127.0.0.1:4711 (Connection refused) in /var/www/html/admin/scripts/pi-hole/php/FTL.php:44
/var/log/pihole/pihole.log is empty.
If fsockopen gets refused trying to connect to 127.0.0.1:4711, then there is a permissions problem with port 4711.
How do I troubleshoot that, specifically?
eg:
I cannot reach port 4711 on the VM from my box:
user@devuan:~$ telnet 192.168.1.3 4711
Trying 192.168.1.3...
telnet: Unable to connect to remote host: Connection refused
user@devuan:~$ [root@devuan ~]# telnet 192.168.1.3 4711
Trying 192.168.1.3...
telnet: Unable to connect to remote host: Connection refused
[root@devuan ~]# ^^^ This ^^^ means that it is closed to outside access.
pihole-FTL uses port 67 ( DHCP ) IPv4 UDP
pihole-FTL uses port 547 ( DHCPv6 ) IPv6 UDP
lighttpd uses port 80 ( HTTP ) TCP
pihole-FTL 4711 TCP
But if pi-hole needs to use it for whatever, it should be able to.
ie: part of the installation (?) to make that happen.
FTL is our API engine and uses port 4711 on the localhost interface. This port should not be accessible from any other interface.
See https://docs.pi-hole.net/main/prerequisites/
Thanks for your input.
Best,
A.
Hello:
Hello:
It would seem like I am the only one ... 8^°
Said I because a search for 'pi-hole' or 'pihole' got me where it is mentioned but they were all mine. 8^°
Devuan is not a supported OS for Pi-Hole (but Debian is) so it's hard to figure things out when something goes wrong.
In any case, I have narrowed down the cause of a problem I am having.
After the last update, the DNS server is not starting and it looks like a permissions issue:
There was a problem applying your settings.
Debugging information:PHP error (2): fsockopen(): unable to connect to 127.0.0.1:4711 (Connection refused) in /var/www/html/admin/scripts/pi-hole/php/FTL.php:44
Here is what is happens after I get this:
I opne a terminal on the VM where Pi-Hole is running and start pihole-FTL.
As it was stopped, it says so and then starts it:
root@chimaera:~# service pihole-FTL restart
Not running
FTL started!
root@chimaera:~#I then immediately query the pihole-FTL status to check if this is so ...
root@chimaera:~# service pihole-FTL status
[ ] pihole-FTL is not running
root@chimaera:~# ... but no.
As you can see it reports as 'not running'.
Here are lines 28 to 47 from the FTL.php script mentioned in the debug output:
...
28 }
29
30 function connectFTL($address, $port) {
31 if ($address == DEFAULT_FTL_IP) {
32 $config = piholeFTLConfig();
33 // Read port
34 $portfileName = isset($config['PORTFILE']) ? $config['PORTFILE'] : DEFAULT_FTL_PORTFILE;
35 if ($portfileName != '') {
36 $portfileContents = file_get_contents($portfileName);
37 if (is_numeric($portfileContents)) {
38 $port = intval($portfileContents);
39 }
40 }
41 }
42
43 // Open Internet socket connection <-------
44 $socket = @fsockopen($address, $port, $errno, $errstr, 1.0); <------
45
46 return $socket;
47 }
...How can I troubleshoot / find the cause of this problem?
ie: unable to connect to 127.0.0.1:4711 (Connection refused)
Thanks in advance.
Best,
A.
Hello:
Has anyone here at Dev1 installed/run Pi-Hole?
It would seem like I am the only one ... 8^°
Thanks in advance.
Best,
A.
Hello AP:
... they recommend the 32-bit builds by Steve Pusser.
... don't know if the latest Pale Moon will work better ...
I only had Fixefox installed due to the lack of a 32-bit PM.
I don't really like FF but could not find anything else at the time.
Fortunately, I've solved the issue with the ADSL.
Some DH at the telco did a remote firmware upgrade (the usual), changing my customer ID/PW for the service and setting up a hard wired admin PW.
All this without informing me or anyone else, not even the techs who came to see what was going on.
So I'll put the PM 32-bit thing on the back burner for the moment, I now have a severe problem with with my Pi-Hole configuration.
Thank you very much for the heads-up and the link to the 32-bit PM. 8^D
Best,
A.
Hello:
rbit wrote:Have you run apt update recently?
^ This.
I mentioned that earlier in my previous post:
... but I run updates regularly, atb least once every fortnight.
Check the pinning with
apt policy firefox-esr
Here it is:
~$ apt policy firefox-esr
firefox-esr:
Installed: 78.15.0esr-1~deb10u1
Candidate: 78.15.0esr-1~deb10u1
Version table:
*** 78.15.0esr-1~deb10u1 500
500 http://deb.devuan.org/merged beowulf-security/main i386 Packages
100 /var/lib/dpkg/status
78.14.0esr-1~deb10u1 500
500 http://deb.devuan.org/merged beowulf/main i386 Packages
~$ And /apt/preferences.d is empty.
Thank you both for your input.
Best,
A.