search

kercre123 / wire-prod-pod

49 stars 9 forks source link

"Error logging in. The bot is likely unable to communicate with your wire-pod instance. Make sure you followed all of the steps and try again." #31

Closed ManicQuinn closed 1 year ago

ManicQuinn commented 1 year ago

Followed the steps to a T with a Raspberry Pi Zero 2 W, getting this error: Error logging in. The bot is likely unable to communicate with your wire-pod instance. Make sure you followed all of the steps and try again.

Could I get some help? This is my third time trying this with my vector, the first two were done on a Linux server PC, but that didn't work so I moved to the raspberry pi instead, still the same issue, I suspect a firewall issue or something but not sure.

ManicQuinn commented 1 year ago

To add to that, I did manage to go to http://escapepod:8080/ and set it up for the first time, adding all the API keys I wanted and what not, however, once I was done with it, I tested to see if vector could be activated, he could not, so I tried to go to http://escapepod:8080/ again, but this time I am getting a "connection refused" error, I've gotten the same thing on my linux PC, I'm honestly stumped..

ManicQuinn commented 1 year ago

Accidentally closed the issue, sorry

ManicQuinn commented 1 year ago

I also would like to add that my Vector MIGHT be a Dev/OSKR bot, but I have no idea of how to confirm this, he was a gift from my partner, but his box looks comercial so I doubt that he is, but all the errors are now making me doubt my presumption.

ManicQuinn commented 1 year ago

More updates, lowkey insightful, decided to check the wire-pod service to see if it was even running, this was what I found:

systemctl status wire-pod
● wire-pod.service - Wire Escape Pod (coqui)
     Loaded: loaded (/lib/systemd/system/wire-pod.service; enabled; vendor preset: enabled)
     Active: failed (Result: exit-code) since Tue 2023-02-07 08:09:00 GMT; 38min ago
    Process: 5640 ExecStart=/home/pi/wire-prod-pod/chipper/start.sh (code=exited, status=137)
   Main PID: 5640 (code=exited, status=137)
        CPU: 1min 51.669s

Feb 07 08:08:31 escapepod start.sh[5642]: creating useepod
Feb 07 08:08:31 escapepod start.sh[5642]: Initiating leopard voice processor with language en-US
Feb 07 08:08:31 escapepod start.sh[5642]: Initializing 3 Picovoice Instances...
Feb 07 08:08:31 escapepod start.sh[5642]: Initializing Picovoice Instance 0
Feb 07 08:08:42 escapepod start.sh[5642]: Initializing Picovoice Instance 1
Feb 07 08:08:53 escapepod start.sh[5642]: Initializing Picovoice Instance 2
Feb 07 08:09:00 escapepod start.sh[5640]: /home/pi/wire-prod-pod/chipper/start.sh: line 40:  5642 Killed   >
Feb 07 08:09:00 escapepod systemd[1]: wire-pod.service: Main process exited, code=exited, status=137/n/a
Feb 07 08:09:00 escapepod systemd[1]: wire-pod.service: Failed with result 'exit-code'.
Feb 07 08:09:00 escapepod systemd[1]: wire-pod.service: Consumed 1min 51.669s CPU time.

So somehow, it failed with some kind of 137 error code I presume? Not quite sure tbh, but makes sense why I can't connect to it now, I'd imagine the same happened on my other PC too

ManicQuinn commented 1 year ago

I'll also add the log file for the server:

journalctl -fe | grep start.sh
Feb 07 07:49:16 escapepod start.sh[5642]: Use the webserver to setup and start chipper.
Feb 07 07:49:16 escapepod start.sh[5642]: Starting webserver at port 8080 (http://localhost:8080)
Feb 07 07:49:16 escapepod start.sh[5642]: Starting SDK app
Feb 07 07:49:16 escapepod start.sh[5642]: Starting server at port 80 for connCheck
Feb 07 08:08:31 escapepod start.sh[5642]: creating useepod
Feb 07 08:08:31 escapepod start.sh[5642]: Initiating leopard voice processor with language en-US
Feb 07 08:08:31 escapepod start.sh[5642]: Initializing 3 Picovoice Instances...
Feb 07 08:08:31 escapepod start.sh[5642]: Initializing Picovoice Instance 0
Feb 07 08:08:42 escapepod start.sh[5642]: Initializing Picovoice Instance 1
Feb 07 08:08:53 escapepod start.sh[5642]: Initializing Picovoice Instance 2
Feb 07 08:09:00 escapepod kernel: [   5640]     0  5640     1674        0    36864       65             0 start.sh
Feb 07 08:09:00 escapepod start.sh[5640]: /home/pi/wire-prod-pod/chipper/start.sh: line 40:  5642 Killed                  ./chipper
ManicQuinn commented 1 year ago

Found a similar issue on here that was closed( #5 ), although I do not like the solution for security reasons, hope to get some input from the dev for a better solution, I will stop trying to figure it out for now and wait for a reply

ManicQuinn commented 1 year ago

Update 4: I reinstalled the Pi OS and wire-prod-pod, and somehow I've done it, the server works flawlessly and I was able to activate my vector, however, now I have a new issue. My vector, despite being activated, is stuck in a screen where a V on a phone screen is blinking/flashing, supposedly, it has been activated, and yet he is unresponsive. This is the log from the 8080 website:

2023.02.07 11:29:59: Adding 00802330 to bot info store
2023.02.07 11:29:59: App tokens jdoc not found for this bot, trying bots in TokenHashStore
2023.02.07 11:29:59: 00802330 sucessfully activated with wire-pod
2023.02.07 11:29:59: ReadJdocs: bot 00802330 matched with IP 192.168.1.6 in token store
2023.02.07 11:29:59: Removing 192.168.1.6 from temporary token-hash store
2023.02.07 11:29:59: Outputting session cert to /home/pi/.anki_vector/Vector-A9G3-00802330.cert
2023.02.07 11:29:59: Getting session cert from Anki server
2023.02.07 11:29:59: Jdocs: Incoming ReadDocs request, Robot ID: vic:00802330, Item(s) to return: 
2023.02.07 11:29:59: [doc_name:"vic.RobotSettings" doc_name:"vic.RobotLifetimeStats" doc_name:"vic.AccountSettings" doc_name:"vic.UserEntitlements"]
2023.02.07 11:30:00: Jdocs: Incoming WriteDoc request, Item to write: vic.RobotSettings, Robot ID: vic:00802330
2023.02.07 11:30:00: Jdocs: Incoming WriteDoc request, Item to write: vic.RobotLifetimeStats, Robot ID: vic:00802330
2023.02.07 11:30:00: Jdocs: Incoming WriteDoc request, Item to write: vic.AccountSettings, Robot ID: vic:00802330
2023.02.07 11:30:01: Jdocs: Incoming WriteDoc request, Item to write: vic.UserEntitlements, Robot ID: vic:00802330
2023.02.07 11:30:01: JSON to ini done
2023.02.07 11:30:01: Removing 192.168.1.6:36451 from cert-write store
2023.02.07 11:30:02: Starting jdocs pinger timer for 192.168.1.6:443
2023.02.07 11:30:02: Using GkUpL1ZPA0XGEl+xOA2ETQ==
2023.02.07 11:30:03: Using GkUpL1ZPA0XGEl+xOA2ETQ==
2023.02.07 11:30:04: Error pinging jdocs, likely unauthenticated
2023.02.07 11:32:43: Using GkUpL1ZPA0XGEl+xOA2ETQ==
2023.02.07 11:32:43: sdkApp: Initiating SDK with 00802330
2023.02.07 11:32:43: Failed to initiate SDK with normal GUID, trying global GUID
2023.02.07 11:32:43: Using GkUpL1ZPA0XGEl+xOA2ETQ==
2023.02.07 11:32:43: sdkApp: Initiating SDK with 00802330
2023.02.07 11:32:53: Using GkUpL1ZPA0XGEl+xOA2ETQ==
2023.02.07 11:32:53: sdkApp: Initiating SDK with 00802330
2023.02.07 11:32:53: Failed to initiate SDK with normal GUID, trying global GUID
2023.02.07 11:32:53: Using GkUpL1ZPA0XGEl+xOA2ETQ==
2023.02.07 11:32:53: sdkApp: Initiating SDK with 00802330

Sadly I barely understand the log, hope to have some help soon

ManicQuinn commented 1 year ago

Update 5: I got everything to work! Turns out I needed to tick the whole "allow DDL to send annonymous data to vector" for it to work

Bluepeltz commented 1 year ago

Update 5: I got everything to work! Turns out I needed to tick the whole "allow DDL to send annonymous data to vector" for it to work

Where do I do that? Having issues myself.