![]() ![]() ![]() That way you always have the dependencies you need through rebuilds, upgrades, etc. Then in your shell command ssh into the ssh addon and run your command there. The safer way to do what you’re trying to do is to follow my guide above to set up ssh from shell commands. You can do that but you’ll have to build in your own redundancy and error handling for when your apks go missing.ĮDIT: realized I kind of rained on your parade without actually presenting an alternative. SQLite cheat sheet lists the most common SQLite statements that help you work with SQLite more quickly and effectively. Hence why you had to go find a particular addon, turn off protection mode and ignore warnings to do it. Get the service running again immediately and then review what went wrong after when nothing is down.Īdding apks to the container isn’t a supported use case though. It’s the docker way, if something is wrong just shoot it and rebuild it. It is trivially easy to rebuild the container from scratch at any time and get it running again. The infrastructure is effectively stateless. I understand, hass.io is meant to be robust and self-healing. ![]() I installed it like this (which I found on an HA community thread about fixing db’s) It seems the bottom line problem is that sqlite3 just cannot be accessed by the shell command. I’ve tried doing an ‘ls > temp.txt’ in the shell command to make sure my files show up in the directory listing (they do) I’ve tried putting full paths and relative paths on each item Here’s my current try, which like all others produces error 127 shell_command:Įxport_badsensors: sqlite3 /config/home-assistant_v2.db /config/www/badsensors.html It seems as though the shell command just simply cannot access sqlite3 and does not know what it is. I’ve tried every suggestion I could find in any interwebs post and still no joy. But any time I’ve tried to run it via an HA shell command in the config.yaml, I get an error 127. I have the query written and working and I’m able to run it from the terminal add on and produce the proper file. When I run the command in cygwin it never enters the shell it appears to hang up and I have to CTRL + C to kill it and return back to the bash command prompt.I am trying to automate a sqlite3 query that I wrote that will return an HTML table with a list of any sensors not updated in the last 30 minutes. This is what I should see: C:\Users\jmquigley\workspace\\sqlite>sqlite3Įnter SQL statements terminated with a " " GNU bash, version 4.1.9(3)-release (i686-pc-cygwin)Ĭopyright (C) 2009 Free Software Foundation, Inc.ĮDIT: When I run the program from the windows command line the program works. Below are the versions of some of the relevant software. nullvalue 'text' set text string for NULL values separator 'x' set output field separator (|) Usage: C:\Windows\sqlite3.exe FILENAME įILENAME is the name of an SQLite database. Has anyone else had this issue before and if so how did you fix it? TIA. This document provides a brief introduction on how to use the sqlite3 sqlite3sqlite3 program will then prompt you to enter SQL. It's as if it stops writing to the terminal when I run the shell. Command Line Shell For SQLite The SQLite library includes a simple command-line utility named sqlite3sqlite3.exe on windows) that allows the user to manually enter and execute SQL commands against an SQLite database. I can see the parameters and the version. When I try to use it from the cygwin mintty terminal it seems like the program hangs. I tried the program from a windows command prompt and it works. I'm trying to use sqlite3.exe command shell with a mintty terminal in cygwin. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |