to get the pub working again, one could uninstall peachpub via yunohost and then reinstall it -- I think this will work, and just give you a fresh install (with a new public key)
…
Cool, happy that this exercise had some value :)
and then the root:root issue that is just that while debugging we ran as root. so after the debugging process, we always need to run chown -R…
Are you willing and able to share the logfile?
/var/log/peachpub/peachpub-go-sbot.log
Then I can look through the full sequence of events.
Sure, how do you want it?
Okay, now I have hit the original problem maybe.
So after everything works, I open up patchwork on my machine, solpunk pub shows up as a connection, and it start indexing, the little green…
Now as to how these files both got root:root, I have no idea.
And whether the working dir should be changed, I'm not sure.
But if there is something I can do to help this not be a problem…
ahahahahaha, it works!
Ok, so I found out that go-ssb would make a new .ssb-go in any location it was run, so I figured that the systemd settings would point to the wrong dir somehow, so I went…
Ok I tried changing the peachoub ui DATABASE DIRECTORY
to the absolute path of /home/yunohost.app/peachpub/.ssb-go
but that fails to start with systemctl
also relative paths like ./
…
ok `systemctl start peachpub-go-sbot´ creates an inner .ssb-go ...
running go-sbot after repair works, and whoami works:
root@yunohost:/home/admin# /var/www/peachpub/sbotcli call…
ok after 30 minutes, my pipe was broken, and the go-sbot was stopped along with my ssh session.
now going back I can start the service, and get green status, but db is still unavailable and…
Ok that worked, now go-sbot is crunching!
So it seems that what happened was that when trying to run the repair command, I accidentally created a new .ssb-go folder, which messed things…
I wonder if the creation is an artifact of me running
SSB_CONFIG_FILE=/home/yunohost.app/peachpub/.ssb-go/config.toml /var/www/peachpub/go-sbot```
inside the `/home/yunohost.app/peachpu…
ps: sorry we don't have more streamlined tools for log reporting and debugging, but thanks for the patience. also still up for hopping on a call if this gets too messy
no worries, I love…
Ok, deleting new new inner .ssb-go, and running
SSB_CONFIG_FILE=/home/yunohost.app/peachpub/.ssb-go/config.toml /var/www/peachpub/go-sbot
creates a new inner .ssb-go ?!?
Okay, I tried repair and fsck again, and now I can't start it, and inner .ssb-go IS BACK.
running just sbot-go gives
root@yunohost:/home/yunohost.app/peachpub/.ssb-go# SSB_CONFIG_FI…
I messaged this to @abekonge on ssb, but switching to here, so its all in this thread.
yup I would echo what glyph said to compare .ssb-go/secret and .ssb-go/.ssb-go/secret and see which…
I'm not sure how to see which public key is the pub's?
This is an interesting problem. PeachCloud usually queries the sbot to find out the key and then displays it in the web interface.…
@notplants They are different!
I'm not sure how to see which public key is the pub's? The ui can't see it itself, in the profile view at least .... and I do not yet have a mental picture of…
Thanks for looking into it!
What do you see when you go to the Profile page of the PeachCloud UI?